EJBCLIENT-98 - RejectedExecutionException from org.jboss.ejb.client.EJBClientContext in JBoss EAP 6.2

Solution Verified - Updated -

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 6.3.0
    • 6.2.x
    • 6.1.x
    • 6.0.x

Issue

  • Currently we are experiencing the bug described in the following JIRA: https://issues.jboss.org/browse/EJBCLIENT-98
ERROR [org.jboss.remoting.handler-errors] (ajp-xljbot00337/10.100.52.67:10079-5) Close handler threw an exception: java.util.concurrent.RejectedExecutionException: Task java.util.concurrent.FutureTask@369a184f rejected from java.util.concurrent.ThreadPoolExecutor@3eb2068a[Shutting down, pool size = 1, active threads = 0, queued tasks = 0, completed tasks = 1]
at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2048) [rt.jar:1.7.0_51]
at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:821) [rt.jar:1.7.0_51]
at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1372) [rt.jar:1.7.0_51]
at java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:110) [rt.jar:1.7.0_51]
at org.jboss.ejb.client.EJBClientContext.unregisterEJBReceiver(EJBClientContext.java:432)
at org.jboss.ejb.client.EJBReceiverContext.close(EJBReceiverContext.java:59)
at org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver$1$1.handleClose(RemotingConnectionEJBReceiver.java:152)
at org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver$1$1.handleClose(RemotingConnectionEJBReceiver.java:149)
at org.jboss.remoting3.spi.SpiUtils.safeHandleClose(SpiUtils.java:54)
at org.jboss.remoting3.spi.AbstractHandleableCloseable$CloseHandlerTask.run(AbstractHandleableCloseable.java:501)
at org.jboss.remoting3.spi.AbstractHandleableCloseable.runCloseTask(AbstractHandleableCloseable.java:406)
at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeComplete(AbstractHandleableCloseable.java:277)
at org.jboss.remoting3.remote.RemoteConnectionChannel.closeAction(RemoteConnectionChannel.java:515)
at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeAsync(AbstractHandleableCloseable.java:359)
at org.jboss.remoting3.remote.RemoteConnectionHandler.closeAllChannels(RemoteConnectionHandler.java:390)
at org.jboss.remoting3.remote.RemoteConnectionHandler.sendCloseRequest(RemoteConnectionHandler.java:231)
at org.jboss.remoting3.remote.RemoteConnectionHandler.closeAction(RemoteConnectionHandler.java:376)
at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeAsync(AbstractHandleableCloseable.java:359)
at org.jboss.remoting3.ConnectionImpl.closeAction(ConnectionImpl.java:52)
at org.jboss.remoting3.spi.AbstractHandleableCloseable.close(AbstractHandleableCloseable.java:153)
at org.jboss.naming.remote.client.HaRemoteNamingStore.close(HaRemoteNamingStore.java:372)
at org.jboss.naming.remote.client.NamingStoreCache.release(NamingStoreCache.java:115)
at org.jboss.naming.remote.client.NamingStoreCache$1.close(NamingStoreCache.java:98)
at org.jboss.naming.remote.client.RemoteContext.close(RemoteContext.java:191)
...

Resolution

The issue has been fixed in 6.3 with CP1.
Install JBoss EAP 6.3 and apply Cumulative patch 1 (or later), or even better use the latest available EAP version.

Note: this exception occurs when remote-naming is used to call a remote EJB, which is not the recommended way of calling a remote EJB. The recommended way is to use ejb-client as described in How to configure an EJB client in JBoss EAP 6

Also, this error can occur when ejb-client scoped context is used as well. These are resolved by the cumulative patch.

Root Cause

EJBCLIENT-98 - java.util.concurrent.RejectedExecutionException if a remote-naming InitialContext should be closed
java.util.concurrent.RejectedExecutionException if a remote-naming InitialContext should be closed

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Comments