mina-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Lecharny (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DIRMINA-760) Client fails to detect disconnection
Date Tue, 16 Aug 2016 18:45:22 GMT

    [ https://issues.apache.org/jira/browse/DIRMINA-760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15423213#comment-15423213
] 

Emmanuel Lecharny commented on DIRMINA-760:
-------------------------------------------

Ok I reused the chat server as a test, and had a client sending 100 000 messages, and killed
the server in the middle of it. Here is the stackTrace I get on the client :

{noformat}
[20:37:48] NioProcessor-2 INFO  [] [localhost/127.0.0.1:1234] [org.apache.mina.filter.logging.LoggingFilter]
- SENT: BROADCAST abcd22401
[20:37:48] NioProcessor-2 INFO  [] [localhost/127.0.0.1:1234] [org.apache.mina.filter.logging.LoggingFilter]
- SENT: BROADCAST abcd22402
[20:37:48] NioProcessor-2 WARN  [] [localhost/127.0.0.1:1234] [org.apache.mina.filter.logging.LoggingFilter]
- EXCEPTION :
org.apache.mina.core.write.WriteToClosedSessionException
	at org.apache.mina.core.polling.AbstractPollingIoProcessor.clearWriteRequestQueue(AbstractPollingIoProcessor.java:625)
	at org.apache.mina.core.polling.AbstractPollingIoProcessor.removeNow(AbstractPollingIoProcessor.java:568)
	at org.apache.mina.core.polling.AbstractPollingIoProcessor.writeBuffer(AbstractPollingIoProcessor.java:915)
	at org.apache.mina.core.polling.AbstractPollingIoProcessor.flushNow(AbstractPollingIoProcessor.java:835)
	at org.apache.mina.core.polling.AbstractPollingIoProcessor.flush(AbstractPollingIoProcessor.java:762)
	at org.apache.mina.core.polling.AbstractPollingIoProcessor.access$700(AbstractPollingIoProcessor.java:68)
	at org.apache.mina.core.polling.AbstractPollingIoProcessor$Processor.run(AbstractPollingIoProcessor.java:1108)
	at org.apache.mina.util.NamePreservingRunnable.run(NamePreservingRunnable.java:64)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:745)
[20:37:48] NioProcessor-2 WARN  [] [localhost/127.0.0.1:1234] [org.apache.mina.core.service.IoHandlerAdapter]
- EXCEPTION, please implement org.apache.mina.example.chat.client.SwingChatClientHandler.exceptionCaught()
for proper handling:
org.apache.mina.core.write.WriteToClosedSessionException
	at org.apache.mina.core.polling.AbstractPollingIoProcessor.clearWriteRequestQueue(AbstractPollingIoProcessor.java:625)
	at org.apache.mina.core.polling.AbstractPollingIoProcessor.removeNow(AbstractPollingIoProcessor.java:568)
	at org.apache.mina.core.polling.AbstractPollingIoProcessor.writeBuffer(AbstractPollingIoProcessor.java:915)
	at org.apache.mina.core.polling.AbstractPollingIoProcessor.flushNow(AbstractPollingIoProcessor.java:835)
	at org.apache.mina.core.polling.AbstractPollingIoProcessor.flush(AbstractPollingIoProcessor.java:762)
	at org.apache.mina.core.polling.AbstractPollingIoProcessor.access$700(AbstractPollingIoProcessor.java:68)
	at org.apache.mina.core.polling.AbstractPollingIoProcessor$Processor.run(AbstractPollingIoProcessor.java:1108)
	at org.apache.mina.util.NamePreservingRunnable.run(NamePreservingRunnable.java:64)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:745)
[20:37:48] NioProcessor-2 INFO  [] [localhost/127.0.0.1:1234] [org.apache.mina.filter.logging.LoggingFilter]
- CLOSED
{noformat}

Seems like it does what expected (at least in the version I'm currently working on).

> Client fails to detect disconnection
> ------------------------------------
>
>                 Key: DIRMINA-760
>                 URL: https://issues.apache.org/jira/browse/DIRMINA-760
>             Project: MINA
>          Issue Type: Bug
>          Components: Core
>            Reporter: Omry Yadan
>             Fix For: 2.0.8
>
>
> Tested against revision 901694 (which is a bit after 2.0.0-RC1)
> My client need to maintain an open connection to the server.
> If I kill the server right before calling session.write(), the client does not detect
that the server is gone.
> there is no exceptionCaught event, and messageSent is actually called (which suggests
successful delivery).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message