test error:JDWP No transports: /home/Support/LabKey Support Forum

test error:JDWP No transports

LabKey Support Forum (Inactive)

View Message

test error:JDWP No transports

wnels2

2008-04-01 12:52

Status: Closed

Sometimes if I stop the drt tests before they have finished I will get the following error when I start the next batch:

FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=JVMTI_ERROR_INTERNAL(113)
ERROR: transport error 202: bind failed: Address already in use ["transport.c",L41]
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510) ["debugInit.c",L500]
JDWP exit error JVMTI_ERROR_INTERNAL(113): No transports initialized
C:\CPAS\server\test\build.xml:641: Java returned: 1
    at org.apache.tools.ant.taskdefs.Java.execute(Java.java:107)
    at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
    at sun.reflect.GeneratedMethodAccessor13.invoke(Unknown Source)
.
.
.
I can't figure out how to stop the process that must be already using it without rebooting my PC. Does anyone know an easier/quicker way?

Thanks,
Bill

jeckels responded:	2008-04-01 14:37
Bill, I haven't seen that error in a long time but I did run into it periodically at a previous job. The only way to clear it was to reboot, as you've experienced. If you want to defer the reboot, you can make a quick edit to the build.xml so that it uses a different port (other than 5005) to list for debugger connections. 5005 is still locked up until you reboot, but if the test's VM is pointing to 5006, it doesn't matter. I'm not sure which version of Java you're running, but it's possible that this bug is fixed in JDK 1.6. I don't think I've seen it since I switched. Josh