Message WorkWrapper caught exception

Recently I got this below error

Issue:
User weblogic
Thread ID Thread-141
ECID 0000JIbKdOmFg4WFLzuHOA1F0y0G00001D
Message WorkWrapper caught exception: 

When I checked the opmnctl status , I can see the OBI Server is down.

Reason:

 When opmnctl is up and running and any of the services is failing. Then this is an issue with

1.  Configuration files like instanceconfig, NQSConfig  
2.  Check the RPD once. Might be an issue with RPD credentials

Solution:

1.  Try restarting the particular services in command line  like opmnctl startproc ias-component=coreappliaton_obis1 
2.  If the above step doesn't help check the log files and double-check your configuration files
3.  If this is an issue with RPD, Try re-deploying the RPD from the em url. And Restart all services.

After this, your OBI should be up & kicking now...... 

OPMNCTL: Commands ,Usage, Attributes

OPMNCTL is used to start & stop the services .

Opmnctl can be located at the following location in your BI Installed directory:

         <OBIHome>\instances\instance1\bin

To Check how an opmnctl command works give the below in a command line :

Opmnctl usage <command>

Ex:

opmnctl usage startall

Here is a list of attribute which can be used with OPMNCTL.

Attribute Name	Attribute Values
ias-component	Value should be the same as the value for the id attribute for the <ias-component> element in the opmn.xml file.
process-type	Value should be the same as the value for the id attribute for the <process-type> element in the opmn.xml file.
process-set	Value should be the same as the value for the id attribute for the <process-set> element in the opmn.xml file.
mode	Value can either be sync or async. The default value is "sync, meaning that this request operates synchronously, and waits for the operation to complete before returning. "async indicates that the request returns immediately, while OPMN continues to perform the request until the operation finishes.
timeout	This can only be specified in sync mode. The value is in seconds. After this timeout expires, OPMN does not continue to perform the request forstartproc operations. The request does continue for restartproc and stopproc operations.
uniqueid	This value is assigned by OPMN after starting up. You can use this value when you execute the opmnctl restartproc and opmnctl stopproccommands.

For more about OPMNCTL check the link below:

Oracle Process Managerand Notification Server Administrator's Guide 

Ping failed in Ready callback for proc:

Ping failed in Ready callback for proc

The reason might be the any or all of the following : 

1) Windows hosts file - Improper IP Configuration
2) Orphan OPMN Services

Ping failed in Ready callback for proc might happen even during OBI 11g installation.
In such case check for both the issues

Solution:

1) Windows hosts file fix:
   Please make sure there is only one entry for each ip-address in the windows hosts file.
2) Orphan OPMN Services: 

   
   Follow the steps to rectify this issue: 

1. Stop all BI Services & also OPMN service
2. Under <MW_HOME>/instances/instance1/config/OPMN/Opmn/states.Check whether any file is present in this folder. This folder contains the running state of the OPMN & BI services. 
3. After closing all BI & OPMN services, if any file is present in the 'STATES' folder. Remove them. And double check whether the OPMN service is closed. 
4. Re-Start the OPMN Services. 

This should fix the issue.