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

Emmanuel Lecharny commented on DIRMINA-725:
-------------------------------------------

Ok, now :
- is that output you get from your handler ?
- if so, it's very likely that the messages are stuck in the codec you are 
using, waiting for some terminaison character (for instance, if you are 
expecting some RC/LF and not receiving any, the handler won't receive the 
MessageReceived event).

Please check that.

> why long connect  is sessionClosed automaticly when client is not close 
> initiatively?
> -------------------------------------------------------------------------------------
>
>                 Key: DIRMINA-725
>                 URL: https://issues.apache.org/jira/browse/DIRMINA-725
>             Project: MINA
>          Issue Type: Bug
>    Affects Versions: 1.1.7
>         Environment: windows+ MyEclipse
>            Reporter: yujun zhu
>             Fix For: 1.1.7
>
>
> 2516 [NioProcessor-1] INFO org.apache.mina.filter.logging.LoggingFilter - 
> CREATED
> 2516 [NioProcessor-1] INFO org.apache.mina.filter.logging.LoggingFilter - 
> OPENED
> session open for /127.0.0.1:3096
> 2532 [NioProcessor-1] INFO org.apache.mina.filter.logging.LoggingFilter - 
> RECEIVED: 
> 2828 [NioProcessor-1] INFO org.apache.mina.filter.logging.LoggingFilter - SENT
> 3453 [NioProcessor-2] INFO org.apache.mina.filter.logging.LoggingFilter - 
> CREATED
> 3453 [NioProcessor-2] INFO org.apache.mina.filter.logging.LoggingFilter - 
> OPENED
> session open for /127.0.0.1:3097
> 3453 [NioProcessor-2] INFO org.apache.mina.filter.logging.LoggingFilter - 
> RECEIVED
> 3469 [NioProcessor-2] INFO org.apache.mina.filter.logging.LoggingFilter - SENT
> 4469 [NioProcessor-3] INFO org.apache.mina.filter.logging.LoggingFilter - SENT
> .....
> 10453 [NioProcessor-3] INFO org.apache.mina.filter.logging.LoggingFilter - 
> CREATED
> 10453 [NioProcessor-3] INFO org.apache.mina.filter.logging.LoggingFilter - 
> OPENED
> session open for /127.0.0.1:3104
> 10469 [NioProcessor-2] INFO org.apache.mina.filter.logging.LoggingFilter - 
> CLOSED
> session closed from /127.0.0.1:3103
> 10469 [NioProcessor-1] INFO org.apache.mina.filter.logging.LoggingFilter - 
> CLOSED
> 10469 [NioProcessor-3] INFO org.apache.mina.filter.logging.LoggingFilter - 
> CLOSED
> 10469 [NioProcessor-3] INFO org.apache.mina.filter.logging.LoggingFilter - 
> RECEIVED
> 10469 [NioProcessor-1] INFO org.apache.mina.filter.logging.LoggingFilter - 
> CLOSED
> session closed from /127.0.0.1:3102
> why long connect  is sessionClosed automaticly when client is not close 
> initiatively?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to