Bug 131204 - [JUnit] JUnit Test Runner Hangs with JMX Remote vmarg
Summary: [JUnit] JUnit Test Runner Hangs with JMX Remote vmarg
Status: RESOLVED INVALID
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2006-03-09 16:12 EST by Ron Bodkin CLA
Modified: 2009-08-30 02:07 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ron Bodkin CLA 2006-03-09 16:12:47 EST 
If I include -Dcom.sun.management.jmxremote in the vmargs used to launch Eclipse, I find that my JUnit test runner is hanging then eventually errors out without running tests:

Could not connect to:  : 1191                
 java.net.ConnectException: Connection refused: connect
<stack trace>

If I remove the -D argument, it all works. I am running with Eclipse 3.2 M5a and a Sun 1.5.0_06 VM.

Working launch command:
C:\eclipse\3.2\eclipse.exe -vm C:\java\jdk1.5.0_06\bin\javaw.exe -showLocation -vmargs -Xmx512m

Failing launch command:
C:\eclipse\3.2\eclipse.exe -vm C:\java\jdk1.5.0_06\bin\javaw.exe -showLocation -vmargs -Xmx512m -Dcom.sun.management.jmxremote
Comment 1 Olivier Thomann CLA 2006-03-09 16:37:24 EST 
JUnit is handled by JDT/UI.
Move to JDT/UI
Comment 2 Martin Aeschlimann CLA 2006-03-12 18:06:51 EST 
Markus, maybe you have an idea.
Comment 3 Markus Keller CLA 2006-04-03 10:34:36 EDT 
I could not reproduce. Ron, is this only a problem when running JUnit Plug-in Tests or does it also occur when you run an Eclipse Application?

And, could you please append the stacktrace?
Comment 4 Markus Keller CLA 2006-06-06 12:46:46 EDT 
Setting to remind - waiting for more information.
Comment 5 Denis Roy CLA 2009-08-30 02:07:06 EDT 
As of now 'LATER' and 'REMIND' resolutions are no longer supported.
Please reopen this bug if it is still valid for you.