E1: OUTBND: MSMQ JDEComConnector2.exe Crashes When it Delivers A Message to a Remote Queue
(Doc ID 2732479.1)
Last updated on DECEMBER 24, 2020
Applies to:
JD Edwards EnterpriseOne Tools - Version 9.2 and laterInformation in this document applies to any platform.
Symptoms
The JDECOMConnector2 works fine when it delivers a message to a Local private MSMQ queue that resides on the same server as the JDECOMConnector2.exe (It works on both non-Enterprise Server or Enterprise Server). However, when it tries to send the message to a remote queue (non JDEComconnector server), then the JDECOMConnector crashes.
Reference solution - E1: OUTBND: MSMQ How to deliver a Message To A Remote Queue (Different Server than JDECOMConnector2) (Doc ID 2676493.1)
Changes
- MSMQ must be added as a server role.
- The error handling on the JDEComconnector needs to be enhanced.
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 |