Flash Builder debugger failed to connect to the running application with tomcat - actionscript-3

I had look into similar question in the stack overflow and tried all the solutions given there, but nothing works for me.
I have a Flex Web application running in localhost with tomcat, i have used Mongrel plugin in Flash Builder to run tomcat.
I am using Firefox browser.
When I try to debug my application it is throwing below error :
The Flash Builder debugger failed to connect to the running
application.
Ensure that:
For in-browser applications, you are running the debugger version of Flash Player.
For network debugging on a mobile device, you have a reliable network connection to the device, and port 7935 is open on your
machine's firewall.
Device connection help
link : error screenshot
I did check with netstat for port 7935 and there is no service running on this port.
I also added the solutions in catalina.properties file as suggested by others in related question but it did not worked out.
kindly help me fix this problem.
Thanks in advance!

The tomcat application is probably not serving the debuggable swf from flashbuilder project. What I have in a (I believe) similar setup is: also change the output directory from your flex project to the webcontent folder of the tomcat application.
Flashbuilder generally doesn't create index.html from the template but ${project.name}.html instead. Make sure you use that when trying to debug.
{workspace}/flexapp/src/MyApplication.mxml
{workspace}/webapp/WebContent/bin-debug <-- oupput folder of flexapp
If you start the tomcat application from Flashbuilder now it will include the debuggable SWF from the flex project.
The flex output URL should then point to http://localhost:8080/myapplication/bind-debug/MyApplication.html?Authorised=true&debug=true

Related

VS Code 2017 "Localhost refused to connect" HTML file

This is a simple index.Html file, when i click on run i get the attached screen.
I have included the Json configuration.
The previous posts did not resolve my issue, and i did restart the machine as well as running VS Code as an admin. VS Code Error
installed Extensions
This happening because of your firewall setting restriction. please
Try Live Server Extension AND check for Firewall Settings.
Plain HTML/CSS can be opened as a file, no need to run them through a web server.
And if these procedures didn't work tell me about your browser.

Primefaces Fileupload Listener not invoked

I am using the Prime faces file upload in advanced mode where it works fine in local system ,but in UAT the listener is not being called.why?
i tried many suggestions ,still the same issue exists.please help me.
UAT(Linux) i am using the tomee server
Local(Windows) tomcat server
primefaces 5.3
enter code here
The reason why the listener is not called is ,there is an firewall restriction to the UAT server where the server is not accepting any file uploads from other domains,only people who are in their domain can access it ,and it is working for them.

Remote Debugging won't connect

I sort of make shift followed this guide on how to setup remote debugging. Since I am using Adobe Animate to compile my app I assume it has done the majority of the build steps already as I get a similar screen described.
I don't understand though. Here I have port forwarding up on my router so that it goes to my PC. I have TCP port 7935 up and open. Windows firewall on or off doesn't seem to make difference. Windows firewall even prompted me to allow or deny fdb after I ran it. I can't get my phone to connect via remote debugging. I want to be able to send this to my client who is having issue with the app so I can see what's going on under the hood instead of relying on a giant sum of try/catch statements and screenshots. Any help?
I tried a dummy domain and it seems to know that it can't connect to it. When I try mine or my IPv4 it doesn't let me connect. It just freezes up the app.
I don't know whether it works or not in Animate CC, but it works via Flash Builder. I'm using Android real device and I have Android SDK tools installed on my PC
Yes, I have followed that tuts from official Adobe docs, but that doesn't work
First: Simply connect your device to your PC
Actually , you can debug your app remotely as long as your device has been connected with your PC. This step, doesn't necessarily requires FDB.
In my case , all I need was things like
adb connect 192.168.xx.xx:port
this will connect your Android device with your PC on your default network .
Second, set debug setting over network
You've done it in Animate CC, with addition you might want to check "install application on the connected device'
Third, just debug as usual
You can get all those debugging stuff including traces

Error after build AIR for desktop

Is there a way to debug a application after it´s build?
It works perfectly in the IDE (Flash), when I build and execute, it just stop during the execution.
If you check the Permit Debugging option in the Publish Settings then you should be able to connect to the Flash debugger while running the app.
When you start the app you should see a message that it's trying to connect to the debugger in Flash go to Debug > Begin Remote Debug Session and it should connect to the app.

Examples can't connect to electroserver

I have recently downloaded Electro Server 5.4.1 from Electrotank, I have started the SAFEMODE.exe and I can see the console, I then log on to the server using the adobe AIR program, I then go and start the ChatLogger and it can't connect, has anyone got any ideas on why this isn't working?
Canvas
extra tags ElectroServer, ElectroTank
I know this is an old question, and odds are you already got an answer to it on the Electrotank forums. Just in case somebody else has a similar problem: the ChatLogger code example requires the ChatLogger extension to be deployed.
You should also check that you can connect using one of the SimpleChat code examples which do not need any extension. If the Unity client works but AS3 doesn't, then you need to set your Flash global security settings to allow socket connections from that area of your hard drive.