[DIRMINA-725] why long connect is sessionClosed automaticly when client is not close initiatively?

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 1.1.7
• Fix Version/s: 1.1.8
• Environment: windows+ MyEclipse
• Assignee: Unassigned
• Reporter: yujun zhu
• Created: 06/Jul/09 08:38
• Updated: 05/Sep/14 09:38
• Resolved: 05/Sep/14 09:38

Description

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?