The following JMS error gets logged into the BusinessWorks logs by the iProcess Service Agent.

BW-iPROCESS-000026 BusinessWorks iProcess Service Agent is unable to retrieve JMS request message.  Exception occurred while retriving the JMS request message.  The content of the BWCTool.cfg(e.g [i1160o!mario01]) is invalid. Please re-generate it again.
The content of the BWCTool.cfg(e.g [i1160o!mario01]) is invalid. Please re-generate it again.
    at com.tibco.plugin.staffware.ServiceAgentEventHandler.buildStaffwareControlDAO(ServiceAgentEventHandler.java:252)
    at com.tibco.plugin.staffware.ServiceAgentEventHandler.getRequestMessage(ServiceAgentEventHandler.java:350)
    at com.tibco.plugin.staffware.ServiceAgentEventHandler.start(ServiceAgentEventHandler.java:682)
    at com.tibco.plugin.staffware.ServiceAgentEventSourceContext.newEvent(ServiceAgentEventSourceContext.java:88)
    at com.tibco.plugin.share.jms.impl.Processor4EventSourceContext.processMessage(Unknown Source)
    at com.tibco.plugin.share.jms.impl.JMSReceiver$SessionController.run(Unknown Source)
    

TIBCO iProcess Technology Plug-ins (11.6.0)

The above error is due to mismatch in the <NodeName>!<MachineName> entry between iProcess and the BWCTool.cfg file. Keeping the same value in BWCTool.cfg as in TIBCO iProcess Engine will resolve the issue.

Looking into the eaijava DEBUG logs in SWDIR/logs directory, the following entry will be logged 

[DEBUG] SWBWTransport - NodeName:i1160o!mario01

where, TIBCO iProcess Nodename is : i1160o
Machine name hosting TIBCO iProcess: mario01

Now, if you review the BWCTool.cfg file 

in Windows
BW_HOME\bw\plugins\iprocess\bin

in UNIX
$BW_HOME/bw/plugins/lib/palettes 

it will be [i1160o!mario01]

The format for above entry is like <NodeName>!<MachineName>
 

Troubleshooting BW-iPROCESS-000026 BusinessWorks iProcess Service Agent is unable to retrieve JMS request message.

BWCTool.cfg, NodeName, BW-iPROCESS-000026