tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gregor Schneider" <>
Subject Strange behaviour of JPDA within Tomcat 5.5
Date Tue, 01 Jul 2008 14:24:28 GMT
Hi guys,

today we faced a problem on on of our production-servers,
unfortunateley,we were not able to replay it on our test-servers.

Therefore, we decided to use remote-debugging (JPDA) to track down the error.

While fiddling out the ports with our firewall-guys, we tested wether
we could reach Tomcat's JPDA-port (i.e. 8787) via Telnet and entered
some dummy-stuff over Telnet.

The result:

Tomcat crashed!

That means, if somebody is running Tomcat 5.5 in JPDA-mode, it's a
peace of cake to crash the instance.

I'm not sure wether this is a JPDA-architecture-bug, a Tomcat 5.5-bug
or just meant by design, anyways, I thought you'd like to know.

This is the result Tomcat sent to catalina.out before crashing:

ERROR: transport error 202: handshake failed - received >?
< - excepted >JDWP-Handshake< ["transport.c",L41]
JDWP exit error JVMTI_ERROR_NONE(0): could not connect, timeout or
fatal errorListening for transport dt_socket at address: 8787

My question:

Does one of you know a solution to limit JPDA to accept a connection
from a dedicated IP-adress only or tunnel JPDA via ssh? Anybody here
who has done something similar already?



what's puzzlin' you, is the nature of my game
gpgp-fp: 79A84FA526807026795E4209D3B3FE028B3170B2
gpgp-key available @

To start a new topic, e-mail:
To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message