Yes, 2.0.7 I've checked that closing sessions isn't enough to free all underlying resources and I need to execute dispose() method on SocketConnector object I've see that I only execute session.close() , there is a waiting JVM thread what never ends
2013/10/4 Bugra Cakir <bug...@mobiliz.com.tr>: > > > But we don't get this problem. We are using Mina 2.0.7 ? Isn't it strange ? > > Bugra > > > 4 Eki 2013 tarihinde 15:10 saatinde, Jose María Zaragoza > <demablo...@gmail.com> > şunları yazdı: > >> OK >> I think that I found the cause of the problem >> >> >> I need to perform >> >> SocketConnector.dispose() >> >> I only was closing session with session.close() >> >> >> What is the right way to finish a communitcation immediately? >> >> session.close(): >> socket.dispose(); >> ? >> >> or is it only enough to perfom socket.dispose(); ? >> >> >> Thanks >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> 2013/10/4 Jose María Zaragoza <demablo...@gmail.com>: >>> I'm closing the same resources with MINA 2.x and MINA 1.1.x. >>> Maybe there are new resources in MINA 2.x which should be close and I >>> don't know them >>> >>> I'm going to start standalone tests because I had to downgrade from >>> 2.0.7 to 1.1.7 because the application is running on production >>> enviroment and I couldn't do many tests >>> >>> >>> >>> 2013/10/4 Emmanuel Lécharny <elecha...@gmail.com>: >>>> Le 10/4/13 9:06 AM, Jose María Zaragoza a écrit : >>>>> OK. >>>>> I'm going to debug that issue and I will tell you my conclusions >>>>> >>>>> So far, I only can know that the same code running on Tomcat but with >>>>> lastest MINA release creates a lot of FIFO file descriptors, but 1.1.7 >>>>> doesn't, >>>> >>>> You most certainly have some opened streams that need to be closed. The >>>> way MINA 1 works is very different from MINA 2, so be sure you always >>>> cleanup whatever resource you use in your code. >>>> >>>> >>>> -- >>>> Regards, >>>> Cordialement, >>>> Emmanuel Lécharny >>>> www.iktek.com >>>> >
