We recently released a web application (tomcat 5.5.x web application) and started showing weird behavior today. We do not see this behavior in any development or pre-production environment.
Our only view of the production system at runtime is registration. Although they can tell us what happened, they cannot help us diagnose why this is happening.
We had to reload the context twice to solve the problem.
I was considering starting a tomcat server with active jpda. This would allow me to connect the debugger to the application if the problem arose again (after removing tomcat from the pool of servers serving user requests).
You obviously pay a performance penalty with jpda when connecting a debugger. However, I was wondering what “cost” is when the debugger was not connected? I suspect that the overhead associated with listening to the debugger may be minimal. Before I spend several hours on performance measurements, I was hoping someone could point me to documentation that could clarify this?
java version "1.5.0_17" Java (TM) 2 runtime, standard version (build 1.5.0_17-b04) Java HotSpot (TM) 64-bit server VM (build 1.5.0_17-b04, mixed mode)
on RHEL 5.3
Thanks!
Carlos
source
share