Uploaded image for project: 'JBoss Remoting (3+)'
  1. JBoss Remoting (3+)
  2. REM3-123

Channel's CloseHandler is not invoked on the server side if the client side channel disconnects

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 3.2.0.Beta3
    • 3.2.0.Beta2
    • None

    Description

      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:

      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]

      Attachments

        Issue Links

          blocks

          Feature Request - Feature requests from customers and/or users AS7-2101 Make it impossible to register 2 slave HCs with the same name

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Feature Request - Feature requests from customers and/or users AS7-336 Detect crashed DC slave in protocol to avoid errors when restarting crashed slave

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. AS7-1094 Get rid of the ping hack used my DomainModelControllerService to detect crashed slaves

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              dlloyd@redhat.com David Lloyd
              jaikiran Jaikiran Pai (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: