[jboss-remoting-issues] [JBoss JIRA] (JBREM-1303) Channel's CloseHandler is not invoked on the server side if the client side channel disconnects

[jaikiran pai (Commented) (JIRA)]

    [ https://issues.jboss.org/browse/JBREM-1303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634657#comment-12634657 ] 

jaikiran pai commented on JBREM-1303:
-------------------------------------

Thanks Ron, wasn't aware about that. I filed https://issues.jboss.org/browse/REM3-123.

                
> Channel's CloseHandler is not invoked on the server side if the client side channel disconnects
> -----------------------------------------------------------------------------------------------
>
>                 Key: JBREM-1303
>                 URL: https://issues.jboss.org/browse/JBREM-1303
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: jaikiran pai
>
> If a client side Channel disconnects (ex: the client program terminates) the server side Channel's CloseHandler(s) are not invoked. As a result, if the server side Channel is later used for writing out messages it runs into a Channel closed exception:
> {code}
> org.jboss.remoting3.NotOpenException: JBREM00206: Channel is not open
> 	at org.jboss.remoting3.remote.RemoteLogger_$logger.channelNotOpen(RemoteLogger_$logger.java:97) [jboss-remoting-3.2.0.Beta2.jar:3.2.0.Beta2]
> 	at org.jboss.remoting3.remote.RemoteConnectionChannel.writeMessage(RemoteConnectionChannel.java:86) [jboss-remoting-3.2.0.Beta2.jar:3.2.0.Beta2]
> 	at org.jboss.as.ejb3.remote.protocol.versionone.VersionOneProtocolChannelReceiver.sendModuleAvailability(VersionOneProtocolChannelReceiver.java:183) [jboss-as-ejb3-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
> 	at org.jboss.as.ejb3.remote.protocol.versionone.VersionOneProtocolChannelReceiver.deploymentAvailable(VersionOneProtocolChannelReceiver.java:161) [jboss-as-ejb3-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
> 	at org.jboss.as.ejb3.deployment.DeploymentRepository.add(DeploymentRepository.java:57) [jboss-as-ejb3-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
> 	at org.jboss.as.ejb3.deployment.ModuleDeployment.start(ModuleDeployment.java:49) [jboss-as-ejb3-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
> 	at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
> 	at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_21]
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_21]
> 	at java.lang.Thread.run(Thread.java:619) [:1.6.0_21]
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira