[
https://issues.apache.org/jira/browse/DIRMINA-725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12729125#action_12729125
]
yujun zhu commented on DIRMINA-725:
-----------------------------------
Hello,My dear:
I want to ask you a question.
It is mina 1.1.7 in my project.
My issue is : the server can call fuction of sessionOpened but can not call
fuction of messageReceived. In othe words, the server can open from the client
IP but can not receive the message from the client. Specially,It happens in
long- connection.
I have change the mina to 2.0.0 release,but the problem also exist.
In addition, I want to show the situation:
session open for /127.0.0.1:40480
[session closed from /127.0.0.1:40480
session open for /117.81.142.14:3074
session open for /202.120.50.236:3356
session open for /122.238.35.32:63615
session closed from /202.120.50.236:3356
session open for /59.62.200.48:2617
session closed from /122.238.35.32:63615
session closed from /59.62.200.48:2617
so the server can't receive any message from the client. but I am sure the
client sends the message to the server .
I look forward to its answer. Thanks!
> 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.
