1980
IAPJMS Message receipt (Receipt) invalid. MsgID (MessageID) returned receipt value (ReceiptValue)
Description
If the JMS delivery method is synchronous, when the message is sent, a receipt is requested. The BG process waits until the IAPJMS process has confirmed the message has been published. If the message that has been received is invalid, this error is reported where:
| • | Receipt is a unique ID. |
| • | MessageID is the unique ID of the message. |
| • | ReceiptValue is one of the following: |
| — | 01 = Failed to initialize sender. This means that the IAPJMS process failed to initialize. |
| — | 02 = Mismatched message. This means that your JMS delivery method is synchronous and you have received a receipt message for the wrong message. |
This means that the message has failed. Whether or not the failed message transaction is rolled back depends on how you have configured your IAPJMS_ROLLBACK process attribute. See "IAPJMS_ROLLBACK" in TIBCO iProcess Engine Administrator’s Guide for more information.
Appears In
SWDIR\logs\sw_warn
Severity
3 (Warning)
Action
To resolve the problem:
| 1. | If you are using UNIX, check the $SWDIR\logs\std_err.log file for errors. |
| 2. | Check that the JMS service is running. |
| 3. | Check that the IAPJMS process is running. |
| 4. | Check that the JMS server is running. |
| 5. | Check the properties are specified correctly in the SWDIR\etc\IAPJMS.properties file. |
| 6. | Check the Java .jar files are specified correctly in the CLASSPATH variable. Look in the IAPJMS.classpath file to see which Java .jar files you should specify. |
| 7. | Set Java debug using Log4J logging facility. Information about Log4J can be found at: |
https://logging.apache.org/log4j.
See Also
For more information about administering activity monitoring, see "Administering Activity Monitoring" in TIBCO iProcess Engine Administrator’s Guide.