Symptoms

Customer tried to get into CCP but was prompted with error: "The operation you are trying to perform requires interaction with a component, which is presently unavailable. Please try again later."

In poa-ui.log, we could see below exception:

   Caused by: org.omg.CORBA.COMM_FAILURE: Cannot connect to host 'osscore/192.168.50.209', port 8444 (java.net.ConnectException:
   Connection refused)  vmcid: 0x444f7000
     minor code: 266  completed: No
        at org.openorb.orb.iiop.IIOPTransport.open(IIOPTransport.java:188)
        at org.openorb.orb.iiop.SocketQueue.open(SocketQueue.java:164)
        at org.openorb.orb.iiop.IIOPClientChannel.request_open(IIOPClientChannel.java:463)
        at org.openorb.orb.iiop.IIOPClientChannel.begin_marshal(IIOPClientChannel.java:976)
        at org.openorb.orb.iiop.IIOPClientRequest.begin_marshal(IIOPClientRequest.java:349)
        at org.openorb.orb.core.Delegate.request(Delegate.java:948)
        ... 152 more

   Caused by: java.net.ConnectException: Connection refused
        at java.net.PlainSocketImpl.socketConnect(Native Method)
        at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
        at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
        at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
        at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
        at java.net.Socket.connect(Socket.java:579)
        at org.openorb.orb.net.ConfiguredSocketFactory$ConfiguredSocket.configConnectedSocket(Unknown Source)
        at org.openorb.orb.net.ConfiguredSocketFactory$ConfiguredSocket.<init>(Unknown Source)
        at org.openorb.orb.net.ConfiguredSocketFactory.createSocket(Unknown Source)
        at org.openorb.orb.iiop.IIOPTransport.createSocket(IIOPTransport.java:215)
        at org.openorb.orb.iiop.IIOPTransport.open(IIOPTransport.java:164)

Restart of pemui service does not fix the problem.

And a crash dump is getting generated every time in /usr/local/pem/var/cores on POA core

This may also happen once a particular task is run.

Cause

Due to APS-15380, a Soloader crashes

Resolution

Check the /var/log/poa.debug.log for task invoking taskExecuteWorkflowProvisionAPS1x, it should be canceled.

Please also consider updating to POA 5.5.5 as APS-15380 was fixed there. In case 5.5.5 is installed, and problem still happens, please contact Parallels technical support.

Internal content