If something does not work as expected, check the following:
Is the JMS Adapter installed properly? Check the bpserver.log file for errors. If the adapter is not installed properly, you may get a "ClassNotFoundException" error message.
Is the JMS Adapter configured correctly? You may have not specified the mode correctly–selecting Send makes your adapter continue without waiting for a reply. Check the JMS queue name–is the JNDI name correct?
Is the Wait for adapter to complete before processing check box set correctly? Failing to clear this checkbox causes your workstep to complete immediately after the message is sent and the R_ProcessID, R_Name, and R_Price dataslots are not updated from the response message.
If the previous suggestions do not resolve your problem, check the OEBPS_HOME\managedadapters\managedadapter.log file. Additional tracking information about the adapter operation may be available there. Depending on the debug level you selected during the JMS Adapter installation, this file can contain a complete record for all sent and received messages. Use this record to figure out which step of the message delivery is failing.
Is the JMS Adapter installed properly? Check the bpserver.log file for errors. If the adapter is not installed properly, you may get a "ClassNotFoundException" error message.