1979
IAPJMS Failed to send audit message for Case: (CaseNum) Event: (EventName) Reason: (ReturnCode)
Description
When the activity occurred, the message that should have been output has not been sent where:
| • | CaseNum is the number of the case. |
| • | EventName is the name of the activity. |
| • | ReturnCode is an internal return code from the software. |
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_error
Severity
2 (Severe)
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.