E1: QUEUE: Troubleshooting Guide for MQSeries Transactions
(Doc ID 625378.1)
Last updated on DECEMBER 27, 2022
Applies to:
JD Edwards EnterpriseOne Tools - Version 9.1 and laterInformation in this document applies to any platform.
Symptoms
Troubleshooting Guide for MQSeries Transactions
------------------------------------------------------
INBOUND
INBOUND ISSUE 1. The XML response message goes to ERROR.Q instead of SUCCESS.Q
INBOUND ISSUE 2. Message stays in the INBOUND.Q forever.
OUTBOUND
OUTBOUND ISSUE 1. OW didn't call AddTransactionToSystemQueue (by looking at jdedebug.log)
OUTBOUND ISSUE 2. R00460 was not able to find a record in F986113, and transaction failed (No message in OUTBOUND.Q)
OUTBOUND ISSUE 3. R00460 found a record in F986113, but there is no message in the OUTBOUND.Q
OUTBOUND ISSUE 4. R00460 Log shows that it called libmqnotify.so successfully by "CallVendorSpecificFunctionOut" (Return value is 0), but there is no message in OUTBOUND.Q
KERNEL
KERNEL ISSUE 1: This problem appeared in UNIX and NT. The jde log for the MQSeries kernel keeps saying (repeatedly) as if its happening every time INBOUND.Q is polled by the kernel.
ISSUE 5: Slow Performance.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| INBOUND |
| OUTBOUND |
| KERNEL |
| Changes |
| Cause |
| Solution |