CNC, DB and Operating System - JDE1 (MOSC)

MOSC Banner

UBE R33815 getting submitted to wrong port randomly

edited Mar 12, 2021 9:24AM in CNC, DB and Operating System - JDE1 (MOSC) 1 commentAnswered

We are facing a strange issue where one fo the MFG UBE version, R3382_CRI0001 which has a report interconnect call to R33815_XJDE0001 gets randomly submitted to one of the ports (6003) which does not exist on our Enteprise Server.

The behaviour ois not consistent and happens only for this particualr version of the parent UBE - R3382_CRI0001. The result of this is that R33815_XJDE0001 errors out and keeps the R3382_CRI0001 in processing state forever. 

We tried to find a root cause why the UBE would get submitted to port 6003 which does not exist in any INI config files or anywhere. We even checked the jdeinterop.ini (because 6003 is the default interop port in JDE) but this UBE does not use interoperability. The ER code of both the UBE's does not have any hardconding of th eport either. Moreover this happens randomly and we are unable to establish a trend or a pattern when it submits to 6003.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

E1 CNC/DBOS Tags

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center