HI, In continuation to further analysis I did for this issue here is my observation:
1. Client 1 opens a session and processes a request. Response is sent back to the client but for some reason client does not disconnect the socket. Let us name thread used for this as pool-6-thread-6634. 2. Now the same thread (pool-6-thread-6634) is assigned to a new request from a client 2 and it also completes the processing and writes back the response. 3. After few seconds both the sessions are closed and use the same thread id (pool-6-thread-6634) for disconnecting the socket. In my production environment, I could see upto 6 active sessions linked with the same thread ID. And then all sessions closing with a matter of few seconds. Is this scenario in line with the implementation of MINA or is this a bug. Below is an example from the production logs. Any help in this regard will be highly appreciated. (2012-07-03 18:00:56,340)(pool-6-thread-10260)(INFO)(CentralMessageHandler.java)(messageReceived)(94)--IsoMessage written...Tue Jul 03 18:00:56 IST 2012 (2012-07-03 18:00:58,211)(pool-6-thread-10260)(INFO)(CentralMessageHandler.java)(messageReceived)(94)--IsoMessage written...Tue Jul 03 18:00:58 IST 2012 (2012-07-03 18:01:01,170)(pool-6-thread-10260)(INFO)(CentralMessageHandler.java)(messageReceived)(94)--IsoMessage written...Tue Jul 03 18:01:01 IST 2012 (2012-07-03 18:01:06,299)(pool-6-thread-10260)(INFO)(CentralMessageHandler.java)(messageReceived)(94)--IsoMessage written...Tue Jul 03 18:01:06 IST 2012 (2012-07-03 18:01:06,613)(pool-6-thread-10260)(INFO)(CentralMessageHandler.java)(messageReceived)(94)--IsoMessage written...Tue Jul 03 18:01:06 IST 2012 (2012-07-03 18:01:11,768)(pool-6-thread-10260)(INFO)(CentralMessageHandler.java)(messageReceived)(94)--IsoMessage written...Tue Jul 03 18:01:11 IST 2012 (2012-07-03 18:01:12,037)(pool-6-thread-10260)(ERROR)(CentralMessageHandler.java)(sessionClosed)(117)--session closed (2012-07-03 18:01:15,482)(pool-6-thread-10260)(ERROR)(CentralMessageHandler.java)(sessionClosed)(117)--session closed (2012-07-03 18:01:17,613)(pool-6-thread-10260)(ERROR)(CentralMessageHandler.java)(sessionClosed)(117)--session closed (2012-07-03 18:01:19,474)(pool-6-thread-10260)(ERROR)(CentralMessageHandler.java)(sessionClosed)(117)--session closed (2012-07-03 18:01:21,381)(pool-6-thread-10260)(ERROR)(CentralMessageHandler.java)(sessionClosed)(117)--session closed (2012-07-03 18:01:21,975)(pool-6-thread-10260)(ERROR)(CentralMessageHandler.java)(sessionClosed)(117)--session closed Thanks and Regards, Rajiv -----Original Message----- From: Emmanuel Lécharny [mailto:[email protected]] Sent: Friday, June 29, 2012 12:04 PM To: [email protected] Subject: Re: sessionClosed called twice Le 6/29/12 8:00 AM, Rajiv Kasera a écrit : > I am using MINA for transaction processing and can see sessionClosed > being invoked twice by the framework after the message has been > written successfully. Is this a bug in MINA? Log snippet are pasted > below Difficult to tell with so little context. Which version of MINA are you using ? > > > > (2012-06-28 > 17:38:04,816)(pool-6-thread-6634)(INFO)(CentralMessageHandler.java)(me > ssageR eceived)(94)--IsoMessage written...Thu Jun 28 17:38:04 IST 2012 > > (2012-06-28 > 17:38:06,051)(pool-6-thread-6634)(ERROR)(CentralMessageHandler.java)(s > ession > Closed)(117)--session closed > > (2012-06-28 > 17:38:06,119)(pool-6-thread-6634)(ERROR)(CentralMessageHandler.java)(s > ession > Closed)(117)--session closed > > > > -Rajiv > > -- Regards, Cordialement, Emmanuel Lécharny www.iktek.com
