Search Engine: Elastic

Article ID: 133183, created on Sep 17, 2018, last review on Mar 14, 2019

  • Applies to:
  • Operations Automation 7.4

Symptoms

OSS Core services have been restarted per the usual instructions.

After the restart, the CP is not available.

The following pattern appears in /var/log/pa/pui/pui.log on UI node for each login attempt:

15:05:28.096 [default task-175] INFO  EJB - LicenseManagerRemote::isPA >>> entry
15:05:28.096 [default task-175] INFO  EJB - LicenseManagerRemote::isPA <<< exit [0 ms]
15:05:28.097 [default task-175] DEBUG c.p.p2.turbine.modules.ModuleFinder - Exit: screens pcp.PLogin:build by exception:java.lang.reflect.InvocationTargetException
15:05:28.097 [default task-175] DEBUG c.p.p2.turbine.modules.ModuleFinder - Exit: layouts pcp.PrimaryLayout:build by exception:java.lang.reflect.InvocationTargetException
15:05:28.101 [default task-175] WARN  c.p.p.c.c.p.m.pages.PDefaultPage - Exception during screen execution
java.lang.reflect.InvocationTargetException: null
...
Caused by: javax.ejb.NoSuchEJBException: EJBCLIENT000079: Unable to discover destination for request for EJB StatelessEJBLocator for "core-ear/licensing-ejb/LicenseManager", view is interface com.parallels.pa.service.license.api.LicenseManagerRemote, affinity is Cluster "ejb"
        at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:567)
        at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:503)
        at org.jboss.ejb.protocol.remote.RemotingEJBClientInterceptor.handleInvocationResult(RemotingEJBClientInterceptor.java:56)
...
        Suppressed: org.jboss.remoting3.ProtocolException: Too many channels open
                at org.jboss.remoting3.remote.RemoteConnectionHandler.handleOutboundChannelOpen(RemoteConnectionHandler.java:194)
                at org.jboss.remoting3.remote.RemoteConnectionHandler.open(RemoteConnectionHandler.java:335)
                at org.jboss.remoting3.ConnectionImpl.openChannel(ConnectionImpl.java:109)
                at org.jboss.remoting3.ClientServiceHandle.getClientService(ClientServiceHandle.java:80)
                at org.jboss.ejb.protocol.remote.RemotingEJBDiscoveryProvider$DiscoveryAttempt$1.handleDone(RemotingEJBDiscoveryProvider.java:354)
                at org.jboss.ejb.protocol.remote.RemotingEJBDiscoveryProvider$DiscoveryAttempt$1.handleDone(RemotingEJBDiscoveryProvider.java:342)
                at org.xnio.IoFuture$HandlingNotifier.notify(IoFuture.java:208)
                at org.xnio.AbstractIoFuture$NotifierRunnable.run(AbstractIoFuture.java:720)
                at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:926)
                ... 3 common frames omitted

During the time of the OSS services restart there are also the following exceptions on UI node:

Caused by: javax.ejb.NoSuchEJBException: EJBCLIENT000079: Unable to discover destination for request for EJB StatelessEJBLocator for "core-ear/licensing-ejb/LicenseManager", view is interface com.parallels.pa.se
rvice.license.api.LicenseManagerRemote, affinity is Cluster "ejb"
at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:567)
....
Suppressed: org.jboss.remoting3.ServiceOpenException: Unknown service name

Cause

Under certain circumstances, the open connections between OSS and UI during OSS services restart may exhaust the Wildfly threads on UI node and lead to service unavailability.

The behavior is planned to be improved in scope of request FND-124.

Resolution

Restart the UI services additionally as per the KB:

How to restart OA system services: UI, Management Node, Agents.

Please use the aforementioned ID to follow up status of the request with your Technical Account Manager or Pooled Technical Associates team pta@cloudblue.com

5356b422f65bdad1c3e9edca5d74a1ae 8fc71f07abe5b233fea1ae0377cd5e3d 55fe109b4b4fe3fbb893f22dbb85a41a 1941880841f714e458ae4dc3d9f3062d

Email subscription for changes to this article
Save as PDF