I have a local application running in local Wildfly that is configured using eclipse. I also have IntelliJ running in local. Now I want to run the application in Eclipse and connect remote debugger to it from my IntelliJ which is also running in the same machine. How do I do that?
In eclipse, I can see that the checkbox of Attach remote debugger is ticked and the port is 8787.
I try remote configuration in IntelliJ with Host as localhost and Port as 8787, I get error Error running 'Eclipse': Unable to open debugger port (localhost:8787): java.net.ConnectException "Connection refused: connect"
Can some one help me with this?
Why I need this setup:
I have this application that is been setup on Eclipse since ages. As I am used to IntelliJ, I don't want to use eclipse. It will take some time for me to identify how to migrate it to intellij, so for now going with this work around.
Ah, never mind. I added -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=8787 to launch configuration and it worked. I thought it appends these arguments automatically. But that is only when we use the bat file to start. Doesn't seem to be the way with eclipse.
PN: I am not deleting this post as there may be others who would have similar requirement.
Server Tomcat v7.0 Server at localhost was unable to start within 101 seconds. If the server requires more time, try increasing the timeout in the server editor.
This is my error. I changed time from 45 secs to 101 secs, but the problem remains. I removed eclipse and tomcat and I re-installed again but the same problem occurs; how can I fix this?
Try remove all breakpoints.Also you can increase start up time.
Open the Servers view -> double click tomcat -> drop down the Timeouts section
I got the solution for your requirement.
I'm also getting the same error in my eclipse Luna.
Go to Window -> Preferences.
Then General -> Network Connections.
Then select the Active Provider as Manual.
Then restart the tomcat and run. It will work.
Hope it will help you.
Open servers view, open Timeouts and set up Start
Open the Servers view -> double click tomcat -> drop down the Timeouts section
you can increase the startup time for each particular server. like 45 to 450
I know it's a bit late, but I've tried everything above and nothing worked. The real problem was that I'm using hibernate, so it was trying to connect to mysql but was not able, thats why it showed time out.
Just to let u guys know, I'm using RDS(Amazon), so just to make a test I changed to my local mysql and it worked perfectly.
Hope that this answer helps somebody.
Thanks.
In my case I was using spring+hibernate and forgot to run my MYSQL server due to which hibernate was not getting loaded and thus was throwing error
Disabling my antivirus does the trick for me ...
I also had the issue of the Eclipse Tomcat Server timing out and tried every suggestion including:
increasing timeout seconds
deleting various .metadata files in workspace directory
deleting the server instance in Eclipse along with the Run Config
Nothing worked until I read a comment on a related issue and realized that I had added a breakpoint in an interceptor class after a big code change and had forgotten to toggle it off. I removed it and all other breakpoints and Tomcat started right up as it usually did.
Just go with below points.
Open Eclipse Windows -> show View -> server -> double click tomcat/press Fn + F3 -> Timeouts -> increase start time
Save setting and Restart eclipse also delete .metadata folder from work space if you don't need
Check Now... All The Best
Folks, I had this same problem and tried raising the timeout, deleting the server and creating again and did not work. I was running Eclipse Kepler in Linux. The solution proposed by #Phoenix is what worked for me:
Window -> Preferences -> General -> Network Connections
Set Active Providers in manual and then configure or not the proxy. I had this option in "Native".
Then I realized I had the variable http_proxy set. It was set in the ~/.bashrc file. This environment variable is the culprit of many problems.
Once I set http_proxy to empty
export http_proxy=
to check it:
echo $http_proxy
I was able to leave option "Active Provider" in "Native" and solve the timeout problem. This is useful because Eclipse adopts the native configuration, in case you change it often.
In my case, where I had configured http_proxy in ~./bashrc, I had to close Eclipse and even log out and log in again.
Below worked for me.
Removed all Breakpoints. Then did a clean on server as below.
Right click on server-->Click clean.
I had tried increasing the Server Start up time for tomcat server, removed server and created new server, removed server and changed run-time environment configurations. Those thing didn't work for me. At last, i found deployment descriptor(url pattern of servlet-mapping) is the one that making the trouble.
Just remove or delete the server from eclipse and reconfigure it or add it again to Eclipse.
I had the same problem I deleted the server from the server tab, and also the server folder under your eclipse workspace, restarted eclipse, set up a new server, and it appears to be running OK now.
Just for knowledge..
Also had the same issue and solved it stopping and starting again the mysql service... I think that was some conflict between mysql-service and tomcat.
Good Luck
If some one had the same issue like me about the timeout of the server where you can found it. This response can help you.
Click on window > Show View > Server.
When you are on the server, you will see the server that you have configured before.
After that, right click on your server configuration, go to Properties > General and click on Switch Location.
After you clicking on "Switch Location", the server configuration will be appear on the Package Explorer of eclipse.
Then Double click on the server file in the package explorer you will see where the timeout located.
Thank you.
None of the above worked for me but this -
1. Remove any project if configured already while installing Tomcat.
2. Right click on configured server -> clean and -> Clean tomcat working directory
Did couple of times and the issue resolved.
Thanks.
In my case tomcat was configured to start not on localhost(guess it came from servers.xml connector entry) so Eclipse fails to find it running after start. Changed Host name on Servers tab to my 192.168.xxx.yyy ip.
Had the same error message, though tomcat did start sucessfully, but then Eclipse shuts it down.
try clean Tomcat working directory,it works for me
Well, I tried all the solutions:
increasing timeout seconds;
deleting the server instance in Eclipse along with the Run Config.
None of them worked.
And:
there was no breakpoint in my code;
I don't use any antivirus.
I realized that some people - who had the same problem - were using Eclipse Helios (so was I).
I switched to Eclipse Kepler and it worked perfectly.
Maybe it can be a solution. I wanted to use Helios, but Kepler is okay.
I was too facing similar issue and here I found another solution for it.
I have just started Eclipse Luna and not developed/deployed any project yet. I tried adding Tomcat v7.0 Server and got same error.
In order to resolve the issue I went to Server Perspective (it's actually server tab next to the console tab located below Project code). Double click on Server which is added to Eclipse. It will open up Overview page. Look for Server Location and select Use workspace metadata(does not modify Tomcat location). Now restart the Server and error will go away.
Server > (double click) Tomcat v7.0 Server at localhost > (Overview page) Server Location > Select -- Use workspace metadata(does not modify Tomcat location).
URL pattern of <servlet-mapping>:
Check project explorer → Deployment descriptor → Servlet Mapping → check that all mapping present in controller package. ref. image as below:
if there is any mapping not available, Then remove that <servlet> and <servlet-mapping> tag in web.xml.
Is your browser making calls to the server while it is starting? if yes, you probably should close it
e.g. if your browser is currently set to http://localhost, close it before attempting to start the server.
If you are trying to debug the application on server, just check out the breakpoints. You might had include the whole class as breakpoint. So remove that breakpoint.
This thing worked in my case when i was trying to debug.
Nothing of the above helped me but setting:
-Djava.net.preferIPv4Stack=true
as VM Argument in the VM Arguments tab of the Tomcat Server Debug Configuration Settings
solved the problem.
(Tomcat 8, Windows 10, Eclipse Mars)
Tomcat Server not starting with in 45 seconds
right click on the configured server go to properties->select monitoring -> Add ->HTTP protocol 8080
after run server it will deploy.
I stoped the tomcat on the computer and started the service (tomcat) using the eclipse IDE.
Turns out that MySQL wasn't running in my case. I've started MySQL service, and it worked.
Timeouts:
Start: 200
Stop: 45
..and then Window → Preferences → General → Network Connection.
Set "Active Provider" = Manual (to mark all the checkboxes).
If you are running into this on Mac and you installed Tomcat using brew, one good way to get round that is to install Tomcat using a zip file instead.
Go here, download a zip file, unzip it, and in Eclipse, create a new server and specify "Tomcat installation directory" as the unzipped file.
When I open the Servers view in Eclipse (Galileo), I have a localhost instance of WLS with a "[Stopped]" indicator on it. When I attempt to start the supposedly stopped instance, I get these errors:
ERROR: transport error 202: bind failed: Address already in use
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:690]
The "Address already in use" part clued me in that WLS was already running.
How can I stop/view the output of the currently running instance?
I normally run WLS through the command line (Windows) separately but I'm starting to fiddle around with running WLS right inside of Eclipse.
I've been searching for a good guide on setting Eclipse up to interact with WLS but haven't found one yet. If any of you can recommend one I would appreciate that as well.
the message you see means that java debugger cannot bind to the specified port, and not (yet) that weblogic cannot bind to its listen address.
This, can be due to an existing running weblogic instance (running with debugger enabled and on the same port) as you say, but may also mean that another Java program has been started with JDWP enabled on the same port.
So in the second case, please search if there is such a process (netstat -a will help) or just change debugger port you are trying to start weblogic with
If instead you really have a running weblogic instance, there are three cases:
1) it is a windows service (strange that you run weblogic as a service with JDWP activated), thus you can search and stop it through windows services ui
2) you started it through the command line, but in this case you would easily find the command line window you used to start it.
3) it is started by eclipse and you cannot see it for any reason, which is quite strange since it means that eclipse would have started two weblogic instances and one is failing. You can search in eclipse console view if you find a running instance (many consoles can be used at the same time). IF you don't find it just try to quit eclipse, WLS must die together with eclipse and you will see it in weblogic logs or through WLS process disappearing from task manager.
Are you using Oracle Enterprise Pack for Eclipse for running weblogic there? If yes I think this is a good introduction:
http://www.oracle.com/webfolder/technetwork/tutorials/obe/jdev/obe11jdev/11/oepe11g/introeclipseide.htm
So I created a Websphere Application Server in Eclipse and pointed it at my WAS_HOME and the profile I created. Whenever I try to start the server, it starts fine and according to the log I see...
[2/22/12 14:16:25:037 EST] 00000000 WsServerImpl A WSVR0001I: Server server1 open for e-business
However, Eclipse says it is still waiting to start, typically it sticks at 23%. Eventually it times out saying it couldn't start, however, the instance is still up and running fine.
How do I get it to recognize the running instance?
Your workspace folder/name could be the issue.
or for me it was the WAS installation itself. When I moved it to C:\was8 everything started to work properly. The default puts it into c:\Program Files... and that was hanging at 23%
a. Please use websphere jre to replace sun hotspot vm to launch the eclipse, like below setting in the eclipse.ini
-vm
D:/IBM/WebSphere/AppServer/java/bin/javaw.exe
b. Please make sure there is not a specail character (like 23%) in the websphere path or eclipse workpsace.
Recently, I've got the same problem with Eclipse Luna and Websphere Developer Tools... The problem was the eclipse proxy configuration
Increase the initial and max heap sizes of the VM that is loading Eclipse.
I'm trying to get a webapp up and running - for debugging - within a Tomcat instance configured in Eclipse (to keep my work flow as automatic as possible). I'm trying to get remote debugging enabled within the Tomcat JVM, and I've read about two sets of VM arguments:
-agentlib:jdwp=transport=dt_socket,address=8000,server=y,suspend=n
or..
-Xdebug
-Xrunjdwp:transport=dt_socket,address=8000,server=y,suspend=n
But whenever I attempt to use either of these, I get an error message in my console:
Error occurred during initialization of VM
agent library failed to init: jdwp
ERROR: Cannot load this JVM TI agent twice, check your java command line for duplicate jdwp options.
I don't know where I should be looking for these other - supposedly duplicate - jdwp options. Where are these configured? How can I get this working?
If you've correctly setup Tomcat to be started and stopped inside an Eclipse instance, then you should not have to manually setup the debug options for the server to debug your application from inside of Eclipse. When you start Tomcat in debug mode from within Eclipse, the debug options are automatically added to the startup process. By manually configuring them in the launch configuration you are causing a duplication of the settings, thus the error response.
To verify that you have setup the server correctly, here are some steps to setup Tomcat in the Helios release:
If your Servers view is not open, go to Window->Show View->Servers
Right-click the servers window and select New->Server
In the 'Select the server type' window select the Tomcat version you are setting up
Select next (if already configured the server runtime environment, then 'Finish' button will be available)
Enter server name and installation directory for your environment
select 'Finish'
At this point, you should be able to see your newly setup Tomcat instance in your Servers window. At this point you can deploy your application to the newly setup server. To start the server in debug mode, you can select the debug botton available from the Servers window. Once the server starts the IDE will be automatically connected to allow for debugging your deployed application.