I am currently pursuing a course on Advanced Java. While learning to create JSP Files, I am using Tomcat server and Eclipse IDE. The two connected perfectly well. However, while running the file 'helloworld.jsp' the option 'Run on Server' is available only for one time. After which the option disappears and also the error is detected "The selection did not contain any resources that may run on a server".
How should I proceed with this? I even have tried with several troubleshooting like addition and deletion of the server. But nothing seems to work well.
Did you add server from Window >> Show View >> Server >> Servers?
I think it maybe cause for appearing only once "Run on Server".
When run the project second time, can the previous JFrame closed before open the new one ?
So I no need to close the JFrame when trying to run the project second time.
Is it possible to open only one JFrame?
Eclipse has the possibility of terminating the launched program before starting the new one:
It is called Terminate and Relaunch (see the Documentation).
You can bind this to any shortcut you like (Window -> Preferences -> General -> Keys).
Apparently, eclipse offers some special options to get what you want.
For other people who might be using a different editor: it's possible, but you'd need some kind of communication between the processes.
What you can do is this, make a server application that runs independently and have it open before you start your regular application. When you run your regular application, connect to the server. This server now messages the other application that was running to close down.
If running a server application is too much trouble, you can run both the server and the client in the same application. When you start the application, check if the designated port is busy, if not, create a server. If it is busy, connect to the server and tell it to shut down. After that, open the server socket in the new application.
Select the Terminate and Relaunch command [ Terminate and Relaunch ] to first terminate the selected debug target and secondly, relaunch it.
Once a launch is terminated it can be automatically removed from the Debug View. To change this setting use the Opens the Launching preference page Run/Debug > Launching preference page.
you may find relaunch-plugin for eclipse useful for your case.
I don't know about eclipse but i usually run two or more JFrame applications in (IntelliJ idea) belonging to different classes at a time. The previous one will not be closed. One more thing i would like to suggest you to use IntelliJ Idea from Jetbrains company as the UI,shortcuts and all other stuff are same as in Android Developer kit(studio) which is also sponsored and developed by Jetbrains!..
You can check the JFrame applications running simultaneously in this image.
Hope this answer is somewhat informative.......
!>...
Want to improve this post? Provide detailed answers to this question, including citations and an explanation of why your answer is correct. Answers without enough detail may be edited or deleted.
I have suddenly begun getting this weird error when I try to debug any of my projects on Eclipse. I don't remember changing anything for this problem to start so suddenly.
'Launching <my program name>' has encountered a problem.
Cannot connect to VM.
Details of the error:
Cannot connect to VM
com.sun.jdi.connect.TransportTimeoutException
Further, in the console I get the following error:
FATAL ERROR in native method: JDWP No transports initialized,
jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
ERROR: transport error 202: connect failed: Connection timed out
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized
[../../../src/share/back/debugInit.c:750]
Please tell me how to solve this problem. I have searched the whole web for an answer but to no luck.
I tried the following solutions which worked for other people:
Restarted Eclipse, restarted computer.
Change hosts file in etc\ - Remove the comments (#) sign before 2 lines namely,
127.0.0.1 localhost
::1 localhost
and restarted.
Turned off all firewalls, restarted Eclipse and retried. Still no luck.
Somebody please help me, I'm going crazy.
Thanks
Sousa
I just found this: Avast! 2014 I have it, and so it fits. If you do as well, then that is probably your problem.
I am using Mac and I ran into similar issue. I made the changes to /etc/hosts file earlier, which I have reverted now to make it as below :-
127.0.0.1 localhost
And restarted the system and fixed my issue.
After much stress and a lot of time, the problem is now resolved. Albeit in a very freaky way which does not amuse me as I can't figure out the rationale behind it. Anyways, here is what happened and maybe someone can throw some more light on what could have been the root cause of the problem.
I uninstalled Eclipse and Java completely from my system.
I then re-installed the latest version of Java (I had this same version previously too).
But this time I installed it in the standard directory and not the custom directory that I was using before (Probably something here was wrong the first time).
I then re-installed Eclipse (latest version again).
And just like that, it all started working normally again, Debug mode and everything!
What immediately comes to my mind is that the system environment variables could have got changed somehow. But I don't understand how this could have happened without me touching anything.
I think the problem is because you have set the wrong path to jre .try right click on your project and click run configuration and set jre correct path. Could you please elaborate more about the issue.
I ran into the same problem. It turned out that I have changed my /etc/hosts file where the ip address 127.0.1.1 was commented out. After uncommented it, it started to work again.
disable windows firewall and it's OK.
TESTED.
Simply restart your PC, it sounds silly but works most of the times.,
I don't have avast in my PC, but still ran into this problem.
Just restarted my PC and debug worked, I'm not sure what might be the problem exactly though.
Sometimes when you try to debug your application, you will get the error like
Cannot connect to VM
com.sun.jdi.connect.TransportTimeoutException
FATAL:----------
ERROR:------------
ERROR:----------
WARN:-------------
I suggest you to turn-off your AVAST! FIREWALL and restart your system and then try debug your application. It will work fine.
Thanks
Lokesh
For me I had this issue when starting up the jetty-server and McAfee Antivirus Protection software was installed in my Windows 7 64 bit PC and as other mentioned I diabled the Firewall option and restarted eclipse workspace and started the server again. It worked!!!
Listening for transport dt_socket at address: 9000
I doubt there is a way to enable the port without disabling the firewall or maybe whitelist the specific port to be allowed by my antivirus softwares since this wont change often. Will post an update if I find one.
I had a similar problem, when working with scrapbook. Fireval was in game mode. Then I turned off Fireval and scrapbook began to work.
Same symptoms appeared quite suddenly after my setup had worked nocely for long time. The reason appeared one invalid line in my /etc/hosts file (I had added virtual NIC's ip there with translation to 'localhost'). Removing that line fixed it.
For someone with C background it is bit surprising that Eclipse reads /etc/hosts when you are debugging local Java application, but that appears to be the case.
If you use a Windows OS, maybe this command can help you:
netsh winsock reset
I got this:
Unable to launch scrapbook VM
com.sun.jdi.connect.TimoutException
I shut down Eclipse, disabled the Avast! firewall (as recommended but only for for 10 minutes), restarted Eclipse at which point I got a message from the Windows firewall about having blocked some Eclipse features.
I checked the "public networks" checkbox (I'm on an employer provided network through wifi), restarted Eclipse and "voila", it is working again.
Windows Firewall Notification - Screen grab
In my case, it was a matter of running Eclipse as Administrator. Once I did that, problem solved.
In my case on a Mac, the "debug attach" block in launch.json was set to port 0.
I simply changed it to something else (8899), and it worked.
My debugger was timing out before the test connected to the JRE.
I increased my java/debug 'debuggger timeout' setting and was able to run the test.
Reference:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=123118
I fixed it by increasing these settings
In my case it worked just by disabling the word wrap setting on the eclipse console
when i try to debug the java programe , it says "Cannot find a free socket for the debugger in eclipse".Could you explain how to resolve the error ?
I have found the solution (at least in my case).
Eclipse was installed on a company share drive once I moved it to my local C drive everything worked fine.
As in this thread, you might want to explicitly mention the path of the JVM you are using to execute eclipse.
See this eclipse.ini as an example.
bug 12132 mentioned incorrect socks proxy information.
bug 27654 refered to a configuration problem (firewall, antivirus?)
The usual checks (some are Windows specifics) are:
switch off the vista firewall (it wasn't activated, to be precise)
add a firewall rule for java.exe/javaw.exe/eclipse.exe and reactivated it (just to be sure it didn't interfere although it was deactivated)
deactivated my antivirus tool (avira antivir)
ran eclipse as administrator
disabled UAC
activated/deactivated wired and wireless network interfaces
changed priorities of the network interfaces
used different jvms (1.6 and 1.7)
created an entirely new workspace
I encountered this error message when migrating to a virtual Win10 machine (Eclipse 2019-09) as of November 2019.
My solution was as follows:
First, like Dan above, make sure you do not start eclipse.exe from a network drive, but from C:...\eclipse-dir.
After I did this, Windows Defender Firewall came up with a dialogue informing me that it had 'blocked some features of this app' (eclipse.exe). After I pressed the 'Allow access'-Button, I was able to debug as I had been used to.
It appears that you have to add eclipse.exe to the applications that can communicate through Windows Defender Firewall. If you need to do this manually, go to Control Panel -> System and Security -> Windows Defender Firewall and choose Allowed apps. Press 'Change settings' and 'Allow another app...' to navigate to your eclipse.exe using the file picker dialogue.
I am trying to run a Java webstart application which is launched from a html page. While loading I get an alert with the message "Automation server can't create object" a couple of times after which the applications starts and works fine. The alerts come up only on one of the workstations. Any pointers on where I should look?
Regards,
Dutch
try the following IE setting: "Initialize and script ActiveX control not marked as safe."
May or may not apply to your case, but there are reported problems with the JScript Runtime throwing up errors when starting up Applets or Java WebStart applications when you have specific network settings.
Every now and again, there's a Windows Update that generates such a bug and another one that follows to fix it and you'll see some of these errors. Yours might be one of these.
Usually the workaround in-between is to either:
go to IE's Network Settings and uncheck "auto detect settings" or any PAC file setting
or go to the Java control panel's Network Settings and disable "Use browser settings" or other settings to use a direct connection instead.
Obviously, that workaround is only valid if you do not have to go through a proxy...