db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kristian Waagan <kristian.waa...@oracle.com>
Subject Re: Log connects and disconnects
Date Thu, 12 Aug 2010 09:11:15 GMT
On 12.08.10 10:44, Damian Hofmann wrote:
> 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 see.
You might also find the attributes AccumulatedConnectionCount and 
ActiveConnectionCount useful (these are published by the NetworkServer 
MBean). If the active count equals the accumulated count after keeping 
the application running for a while, the connections aren't closed. Even 
though sockets will be closed for instance when the JVM exits, it is 
better (and recommended) to close them sooner if you know the connection 
won't be used again.

There are more connection counts exposed by the MBean, and they're 
slightly confusing unless you know about the derby.drda.maxThreads and 
derby.drda.timeSlice properties...

> 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,

View raw message