Community
Participate
Working Groups
Build Identifier: 20100917-0705 I have an application which has survived a migration throught all of the Eclipse versions since 3.1. On helios all of the launch configurations on my workspace take 60+ seconds and they all get stuck in "Verifying Launch Attributes" Reproducible: Always Steps to Reproduce: 1. Open a project in the working 2. Click Run As - Java Application on a main class 3. Wait for 60+ seconds to see the application lauchn 4. Open a WTP Project 5. Run As -> Server Application 6. Wait for 60+ seconds to see the application lauchn.
Move to JDT/Debug
(In reply to comment #0) > 1. Open a project in the working > 2. Click Run As - Java Application on a main class > 3. Wait for 60+ seconds to see the application lauchn There isn't much that can be done with just this information. Do you get this problem with a console hello world? Perhaps some thread dumps will help determine where it's stuck on? http://wiki.eclipse.org/index.php/How_to_report_a_deadlock
Hello, +1: 1. What build of Eclipse you are using (see Help > About) -> 20090621-0832 as well as 20100917-0705 2. What VM you are using (version and vendor). Use "java -version" to find out version information. -> java version "1.6.0_22" Java(TM) SE Runtime Environment (build 1.6.0_22-b04-307-10M3261) Java HotSpot(TM) 64-Bit Server VM (build 17.1-b03-307, mixed mode) 3. What you were doing at the time of the deadlock (what dialog, wizard, editor, etc) -> Launching a JUnit4 test. Progressbar kept stuck at "Verifying launch attributes ... (57%)" 4. Whether it is reproducible; if so, provide steps -> See report 5.Once the bug report is created, attach a stack trace (also known as thread dump), using the "Create a New Attachment" link in bugzilla. -> Will do in a minute
Created attachment 188452 [details] Heapdump while waiting
Can you please check whether IPv6 is enabled? If so, can you disable it and try again?
(In reply to comment #4) > Created attachment 188452 [details] > Heapdump while waiting Can you re-attaching a heap dump (in plain text), this one cannot be read - file opens and is all garbled.
I have not noticed any significant delays launching Java applications, without an updated Heap dump I am marking this worksforme.
In my machine, this often happens when IPv6 is enabled but somehow not configured correctly. When IPv6 is enabled, Eclipse will try to talk to the new JUnit runner Java process via IPv6 and if that doesn't work, it will fall back to IPv4 after a 60 second timeout. If you have this problem, add this line -Djava.net.preferIPv4Stack=true to eclipse.ini after the -vmargs line.
(In reply to comment #8) > In my machine, this often happens when IPv6 is enabled but somehow not > configured correctly. > > When IPv6 is enabled, Eclipse will try to talk to the new JUnit runner Java > process via IPv6 and if that doesn't work, it will fall back to IPv4 after a > 60 second timeout. > > If you have this problem, add this line > > -Djava.net.preferIPv4Stack=true > > to eclipse.ini after the -vmargs line. Thanks for the tip Aaron!
Check solution in this issue: https://bugs.eclipse.org/bugs/show_bug.cgi?id=481417
