Sometimes, Security Director policy push, Template or configlet will fail intermittently. This article explains how to identify and fix the issue.
You will find the below error in server.log:
2024-11-20 07:25:19,155 ERROR [org.jboss.as.ejb3.invocation] (JobThread1507733) WFLYEJB0034: EJB Invocation failed on component DeviceServiceEJB for method public abstract net.juniper.jmp.cmp.deviceConnectivity.ChannelCommandResponse net.juniper
.jmp.cmp.deviceManager.DeviceServiceItf.sendRpc(int,int,int,java.lang.String,java.lang.String,int,int): javax.ejb.EJBException: java.nio.channels.ClosedChannelException
at org.jboss.ejb.protocol.remote.EJBClientChannel$MethodInvocation.handleClosed(EJBClientChannel.java:1269) [jboss-ejb-client-4.0.37.Final-jmp.jar:4.0.37.Final-jmp]
at org.jboss.remoting3.util.InvocationTracker.connectionClosed(InvocationTracker.java:222) [jboss-remoting-5.0.20.Final.jar:5.0.20.Final]
at org.jboss.remoting3.util.InvocationTracker.lambda$new$0(InvocationTracker.java:70) [jboss-remoting-5.0.20.Final.jar:5.0.20.Final]
at org.jboss.remoting3.spi.SpiUtils.safeHandleClose(SpiUtils.java:50) [jboss-remoting-5.0.20.Final.jar:5.0.20.Final]
at org.jboss.remoting3.spi.AbstractHandleableCloseable$CloseHandlerTask.run(AbstractHandleableCloseable.java:520) [jboss-remoting-5.0.20.Final.jar:5.0.20.Final]
at org.jboss.remoting3.spi.AbstractHandleableCloseable.runCloseTask(AbstractHandleableCloseable.java:425) [jboss-remoting-5.0.20.Final.jar:5.0.20.Final]
at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeComplete(AbstractHandleableCloseable.java:286) [jboss-remoting-5.0.20.Final.jar:5.0.20.Final]
at org.jboss.remoting3.remote.RemoteConnectionChannel.closeAction(RemoteConnectionChannel.java:508) [jboss-remoting-5.0.20.Final.jar:5.0.20.Final]
at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeAsync(AbstractHandleableCloseable.java:368) [jboss-remoting-5.0.20.Final.jar:5.0.20.Final]
at org.jboss.remoting3.remote.RemoteConnectionHandler.closeAllChannels(RemoteConnectionHandler.java:619) [jboss-remoting-5.0.20.Final.jar:5.0.20.Final]
at org.jboss.remoting3.remote.RemoteConnectionHandler.receiveCloseRequest(RemoteConnectionHandler.java:222) [jboss-remoting-5.0.20.Final.jar:5.0.20.Final]
at org.jboss.remoting3.remote.RemoteReadListener.handleEvent(RemoteReadListener.java:93) [jboss-remoting-5.0.20.Final.jar:5.0.20.Final]
at org.jboss.remoting3.remote.RemoteReadListener.handleEvent(RemoteReadListener.java:49) [jboss-remoting-5.0.20.Final.jar:5.0.20.Final]
at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) [xnio-api-3.8.4.Final.jar:3.8.4.Final]
at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66) [xnio-api-3.8.4.Final.jar:3.8.4.Final]
at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89)
at org.xnio.nio.WorkerThread.run(WorkerThread.java:591)
Caused by: java.nio.channels.ClosedChannelException
The issue reported in the below PR:
https://prsearch.juniper.net/problemreport/PR1697264
And the issue was fixed in Space 23.1 hotpatchv3