It should be so. I use MINA 1.1.7 and never expirienced such problem. try this version.
On Fri, Sep 5, 2008 at 8:57 PM, Tasneem Yusuf <[EMAIL PROTECTED]>wrote: > I do have a log in the exceptionCaught() method of the adapter. That does > not get invoked.So I guess client is not closing the connection.I am also > sure that client is not closing the connection because I wrote a small > program on my side that connects to this client using JAVA's Socket. That > connection stays alive until my program explicitly does not close the > connection. > Does MINA 1.1.0 ensure that unless an explicit session.close() is called in > the handler , the session will not get closed ? > > > > On Fri, Sep 5, 2008 at 1:28 PM, Zlatko Josic <[EMAIL PROTECTED]> > wrote: > > > I'm not shure for the parameter. You can check if client close > connection. > > In your IoHandlerAdapter class override method > > > > public void exceptionCaught(IoSession session, Throwable cause) throws > > Exception ; > > > > and put some log in it. > > > > if client close connection this method should be invoked so you will know > > does client close connection or not. > > > > > > On Fri, Sep 5, 2008 at 8:05 PM, Tasneem Yusuf <[EMAIL PROTECTED] > > >wrote: > > > > > The session is not going idle because the close happens immediately > after > > > the session.write().join() finishes. Also I'm told that the client is > not > > > closing the session. Is there any parameter that I can set in my > filters > > to > > > ensure that the session does not get closed. > > > Thanks, > > > Tasneem > > > > > > On Fri, Sep 5, 2008 at 12:46 PM, Zlatko Josic <[EMAIL PROTECTED] > > > >wrote: > > > > > > > maybe client close session or session rich time out, gets idle. > > > > > > > > On Fri, Sep 5, 2008 at 7:38 PM, Tasneem Yusuf < > [EMAIL PROTECTED] > > > > >wrote: > > > > > > > > > Hi, I am writing to this thread , as I have a similar problem. > In > > my > > > > > case > > > > > I have a server using Mina 1.1.0 jar. However, even though in my > > > request > > > > > handler I do not do a session.close() explicitly , the session gets > > > > closed. > > > > > I have logging statements in one of the filters that I have added. > So > > > > when > > > > > the server sends some data to the client the session.close method > of > > > that > > > > > adapter gets called (where I have logging statements) . I want the > > > > session > > > > > to stay alive after the write message and keep listening on the > port > > > for > > > > > data from the client. > > > > > > > > > > On Fri, Sep 5, 2008 at 11:11 AM, Tuure Laurinolli < > > > > > [EMAIL PROTECTED]> wrote: > > > > > > > > > > > Zlatko Josic wrote: > > > > > > > > > > > >> Yes, you figure out very well what I've asked. My english > > knowledge > > > is > > > > > not > > > > > >> so good so I had to aks for listener :) > > > > > >> > > > > > >> We use some tool for monitoring traffic, sniffer, and it shows > > that > > > a > > > > > >> terminal does not get all data but detect > > > > > >> connection close. Maybe there is bug in terminal software, we > will > > > > check > > > > > >> it. > > > > > >> > > > > > > > > > > > > Does the connection get terminated with an RST or a FIN/ACK > > sequence? > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > Tasneem Yusuf > > > > > > > > > > Face the sun and the shadow will fall behind u. > > > > > > > > > > > > > > > > > > > > > -- > > > Tasneem Yusuf > > > > > > Face the sun and the shadow will fall behind u. > > > > > > > > > -- > Tasneem Yusuf > > Face the sun and the shadow will fall behind u. >
