Re: [389-users] slapd didn't close connection and get into CLOSE_WAIT state

2010-03-11 Thread Chun Tat David Chu
Thank you Rich, I will definitely help testing the alpha release once it is available. On Thu, Mar 11, 2010 at 9:24 AM, Rich Megginson wrote: > Chun Tat David Chu wrote: > > Hi Rich, > > > > Thanks for your explanation. > > > > I know that #567429 is a low priority bug, but is there a time frame

Re: [389-users] slapd didn't close connection and get into CLOSE_WAIT state

2010-03-11 Thread Rich Megginson
Chun Tat David Chu wrote: > Hi Rich, > > Thanks for your explanation. > > I know that #567429 is a low priority bug, but is there a time frame > or which version of 389-DS will have a fix for this bug? Probably 1.2.6 or 1.2.7 final release. Should show up in an alpha release in a few weeks. > >

[389-users] slapd didn't close connection and get into CLOSE_WAIT state

2010-02-18 Thread Chun Tat David Chu
Hi All, I am running 389 DS version 1.2.5, build number 2010.012.2034 on RHEL 5.2. I have a problem that slapd didn't close a connection and eventually get into a CLOSE_WAIT state after my JAVA application exit. The scenario only happen when my application registers a NamingListener via the JAVA