After you migrate to IBM Business Process Manager V8.5 system from WebSphere Process Server, you might see a XJMS0021E error in the SystemOut.log file of the AppTarget cluster member.
The SystemOut.log file might have a message similar to this text:
[6/23/14 14:26:28:103 EDT] 0000015d JMSClassifica W XJMS0021E: Unable to map destination and bus to workclass. Aborting the xd classification filter for the current request. Request context information is com.ibm.ws.xd.jms.proxy.impl.AsynchJMSServiceContextImpl@d13b8c78<bus=BPM.BPM_DEV.Bus,destination=BPEIntQueue_WPS.AppTarget>.
The XJMS0021E message indicates a work class for the Java™ Message Service (JMS) does not exist. This message just means that the work cannot be classified under a service policy and it will be done at the priority of the default work class.
Resolving The Problem
You can safely ignore this message unless there is an impact for the IBM Business Process Manager runtime.
If you want to get rid of the message, you need to set a work class for JMS. For more information, see the Defining a service policy topic in the WebSphere Application Server product documentation. In that document, the "To create a work class for your service policy" topic has detailed information about this configuration change.
Was this topic helpful?
15 June 2018