RTE port mapping, the wrong and right way

Interoperability is becoming more and more important and RTE is a great way of getting events out of JDE and into other systems.

Are you finding JDE locking up when RTE messages are being sent out of the system?

When configuring RTE, please remember:

• The WLS listen port is the port that external systems will come in a pull messages off the queue.  This is NOT the port that JD Edwards talks to.  This is NOT the port that you configure in OCM for the active RTE service record.
• The JDENET Listen port must be the SAME as the port you put in the OCM’s for the RTE

Note that you may get lucky and messages will be delivered, but this is because they are “pulled” by the RTE code from F90710, not pushed by the network kernels via the call object kernels.

Note also that you’ll see things like this in your error log for jdenet_n:

1400/9228 MAIN_THREAD                      
Thu Jul 23 13:27:58.282000
NETFLOW.C1032
1400 (pid) in routeOutgoingQueue(), unable to send message: sd=-1, msgId=72066, msgHost=10.200.11.121, msgPort=8085, sendingHost=10.200.11.15, msgType=15501, msgRange=28, krnlName=APP SERVER KERNEL, reqNet=0, resNet=0, reqKrnl=14008, resKrnl=0, msgFlags=0.

1400/9228 MAIN_THREAD                      
Thu Jul 23 13:30:57.621000
NETFLOW.C1032
1400 (pid) in routeOutgoingQueue(), unable to send message: sd=-1, msgId=72132, msgHost=10.200.11.121, msgPort=8085, sendingHost=10.200.11.15, msgType=15501, msgRange=28, krnlName=APP SERVER KERNEL, reqNet=0, resNet=0, reqKrnl=14008, resKrnl=0, msgFlags=0.

1400/9228 MAIN_THREAD                      
Thu Jul 23 13:32:10.052000
NETFLOW.C1032
1400 (pid) in routeOutgoingQueue(), unable to send message: sd=-1, msgId=72193, msgHost=10.200.11.121, msgPort=8085, sendingHost=10.200.11.15, msgType=15501, msgRange=28, krnlName=APP SERVER KERNEL, reqNet=0, resNet=0, reqKrnl=14008, resKrnl=0, msgFlags=0.

1400/9228 MAIN_THREAD                      
Thu Jul 23 13:36:37.048000
NETFLOW.C1032
1400 (pid) in routeOutgoingQueue(), unable to send message: sd=-1, msgId=72264, msgHost=10.200.11.121, msgPort=8085, sendingHost=10.200.11.15, msgType=15501, msgRange=28, krnlName=APP SERVER KERNEL, reqNet=0, resNet=0, reqKrnl=14008, resKrnl=0, msgFlags=0.

1400/9228 MAIN_THREAD                      
Thu Jul 23 14:28:20.298000
NETFLOW.C1032
1400 (pid) in routeOutgoingQueue(), unable to send message: sd=-1, msgId=72624, msgHost=10.200.11.121, msgPort=8085, sendingHost=10.200.11.15, msgType=15501, msgRange=28, krnlName=APP SERVER KERNEL, reqNet=0, resNet=0, reqKrnl=14008, resKrnl=0, msgFlags=0.

1400/9228 MAIN_THREAD                      
Thu Jul 23 14:29:42.775000
NETFLOW.C1032
1400 (pid) in routeOutgoingQueue(), unable to send message: sd=-1, msgId=72687, msgHost=10.200.11.121, msgPort=8085, sendingHost=10.200.11.15, msgType=15501, msgRange=28, krnlName=APP SERVER KERNEL, reqNet=0, resNet=0, reqKrnl=14008, resKrnl=0, msgFlags=0.

One crazy thing is that this causes a FULL SYSTEM lockup.  While the jdenet kernel is waiting for the TCP confirmation – everything stops!!!  Crykie – that’s not good.

Please be careful with your port specifications when using RTE!