On 8/9/06, Frederic Soulier <[EMAIL PROTECTED]> wrote:
Hi Trustin
Here is the full thread dump.
<snip/>
On Wed, 2006-08-09 at 16:41 +0900, Trustin Lee wrote:
> On 8/9/06, Frederic Soulier <[EMAIL PROTECTED]> wrote:
> >
> > When a mobile phone is used as a client and is connected to the
> > SocketAcceptor on the server we can send some messages and all seems
> > fine.
> > If the battery of the phone is removed (hence terminating the client
> > application), we have a process that scans for sessions without activity
> > for more than 30 seconds. If such a session is found we call:
> > ioSession.close().join();
> >
> > At that point the socketAcceptor doesn't accept any connections at all.
> > Our only way to get it back is to kill it and restart it.
>
>
> This is weird because SocketAcceptor thread doesn't take care of closing a
> session. SocketIoProcessor does it instead. That is, SocketAcceptor thread
> shouldn't get affected by any I/O after acceptance of a channel. Could you
> post a full thread dump for us?
Full thread dump Java HotSpot(TM) Server VM (1.5.0_07-b03 mixed mode):
<snip/>
I'm facing a vaguely similar problem. The scenario is thus -
1. Server has a few hundred concurrent connections
2. Clients abruptly disconnect due to network failure or some other reason
3. Server processes disconnects
4. Client reconnects
5. Server accepts connection
6. Client writes message
7. messageReceived() is never fired
Currently trying to find out what exactly is causing this.
Regards,
Vinod.
