Hi Trustin Since teh 5/14, a lot of things happen, and the most important one was that I have MY bug and fixed it.
After hard investigation, I have found that the CLOSE_WAIT problem occurs because my server SocketAcceptorIoProcessor threads are stcuked in a deadlock due to using a write lock while holding a read lock. THE PROBLEM IS AND WAS NOT RELATED TO MINA. I moved back to MINA 1.1.0 using 64 bit JVM on linux and up to now, everything is working fine. MINA is a great product, and it holds our server's entire communications layer. Sorry for the trouble Ran. Trustin Lee wrote: > > On 5/14/07, Rankorn <[EMAIL PROTECTED]> wrote: >> >> I have the same problem when moving from MINA 1.0.1 to MINA 1.1.0 on a >> server >> running linux 64bit. >> >> The application worked great with 1.0.1 and with 1.1.0 on 32 bit, but >> when >> moved to the 64 bit server, it stop responding. >> I have noticed that I do not get the session open event, even though a >> socket is opened. >> >> The solution was to stay with 1.0.1 > > What about 1.0.3? Does it introduce the same issue? > > Trustin > -- > what we call human nature is actually human habit > -- > http://gleamynode.net/ > -- > PGP Key ID: 0x0255ECA6 > > -- View this message in context: http://www.nabble.com/-jira--Created%3A-%28DIRMINA-344%29-Maybe-I-met-a-deadlock.-tf3134420.html#a10714672 Sent from the mina dev mailing list archive at Nabble.com.
