Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-21580

[GSS](7.4.z) REM3-377 - Use safeClose() in ClientServiceHandle.close()

    XMLWordPrintable

Details

    Description

      When shutting down the server, this exception gets raised: 

      11:33:04,028 INFO  [org.jboss.as.server] (Thread-2) WFLYSRV0220: Server shutdown has been requested via an OS signal
11:33:04,032 ERROR [org.jboss.ejb.client] (MSC service thread 1-3) EJBCLIENT000513: Exception occurred when trying to close the transport provider: java.lang.NullPointerException
	at org.jboss.remoting3.ClientServiceHandle.closeChannel(ClientServiceHandle.java:144)
	at org.jboss.ejb.protocol.remote.RemoteEJBReceiver.close(RemoteEJBReceiver.java:211)
	at org.jboss.ejb.protocol.remote.RemoteTransportProvider.close(RemoteTransportProvider.java:89)
	at org.jboss.ejb.client.EJBClientContext.close(EJBClientContext.java:630)
	at org.jboss.as.ejb3.remote.EJBClientContextService.stop(EJBClientContextService.java:181)
	at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:1795)
	at org.jboss.msc.service.ServiceControllerImpl$StopTask.execute(ServiceControllerImpl.java:1764)
	at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
	at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
	at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
	at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
	at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1363)
	at java.lang.Thread.run(Thread.java:748)

      The ClientServiceHandle.close() method needs to use safeClose() in case the channel variable has not been initialized, which can happen if the service creation is cancelled or raises an exception.

      Attachments

        Issue Links

          blocks

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-21285 [GSS](7.4.z) EJBCLIENT-347 / REM3-350 - Remoting outbound channels are not closed

          • 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.
          • Verified
          clones

          Bug - A problem that impairs or prevents the functions of the product. REM3-377 Use safeClose() in ClientServiceHandle.close()

          • 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
          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-21581 (7.3.z) REM3-377 - Use safeClose() in ClientServiceHandle.close()

          • 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.
          • Verified
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-21961 [GSS](7.4.z) Upgrade remoting from 5.0.20.SP1-redhat-00001 to 5.0.23.SP1-redhat-00001

          • 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

              spyrkob Bartosz Spyrko-Smietanko
              spyrkob Bartosz Spyrko-Smietanko
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: