E1: OUTBND: After Upgrade to TR 9.2.6.x (64bit), the Transaction Server Instance with the MSMQ Subscriber is Showing High CPU and Failed Server Status
(Doc ID 2882202.1)
Last updated on NOVEMBER 22, 2022
Applies to:
JD Edwards EnterpriseOne Tools - Version 9.2 and laterInformation in this document applies to any platform.
Symptoms
After upgrading to TR 9.2.6.3, issue starts to appear with Real Time Events where the CPU hits 100% causing the Transaction server to fail and needs to be restarted. It was found that in a 64 bit environment with only 1 subscriber, thousands of sessions are being created causing a spike in CPU and GC. This was not happening in 32bit environment, only 64 bit with no other changes.
STEPS TO REPRODUCE
1. Set up MSMQ (com connector) to receive jms messages
2. Set up 1 subscriber to that queue
3. Initiate an event to be sent into the queue
4. Monitor the CPU and see spiking to 100%
5. View the debug logs and see 1000's of session create messages
Changes
Upgrade to TR 9.2.6.3 64bit
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 |
| Changes |
| Cause |
| Solution |
| References |