On 22 Nov, 21:15, markspace <nos...@nowhere.com> wrote:
My first try at this would not involve the mapping at all. I would run
the program under Eclipse in debug mode,
Patricia makes a good point. The first step in most debugging
investigations is to reproduce the problem. Poking at the live server
is likely to be difficult at best, with the restrictions placed on you
to not actually disturb the production environment and what not.
Playing with threads and debugging can vary with the actual container
used, which you didn't mention. Are you using JBoss? Tomcat?
Websphere? What version?
We are using Glassfish 2.1.1
I can't reproduce it in debugging environment, since it happens very
rarely (once every two months or so) after a lot of load on the
application server (it's a production server after all)
It could even be that it's not an "application" thread (i.e. a thread
serving web requests) but a thread which is internal to the
application server itself.
I hoped that matching java thread-IDs to native linux PIDs was
easier...