Thanks Kristian
I used the Thread-View of visualvm, where I could see the states of
DRDAConnectionThreads. This showed me, that my bugfix had improved the
situation, but a small problem still remained.
I also filed an improvement request:
https://issues.apache.org/jira/browse/DERBY-4769
Greets
Damian
Am 11.08.10 11:31, schrieb Kristian Waagan:
On 11.08.10 10:42, Damian Hofmann wrote:
Hi Derby Community
Short question: Are disconnects supposed get logged if the option
"derby.drda.logConnections" is enabled? If not, how can I see if the
connections get properly closed?
Hi Damian,
I don't think disconnects are logged. I see two things you can do with
Derby currently:
o enable client side logging
o use JMX and look at the information provided by NetworkServer MBean
[1]
I'm thinking the JMX approach is the easiest way to get a picture of
the situation in your network server (could use jconsole or visualvm).
If you would like to see logging of disconnects to derby.log, you
should file a request in Jira [2]. I expect the required changes to be
small, perhaps only adding tracing code to either
DRDAConnThread.closeSession() or Session.close().
Regards,
