My Oracle Support Banner

E1: OUTBND RTE Server Can't Be Started - It Tries to Start For 20 Minutes And Fails. (Doc ID 2345829.1)

Last updated on JANUARY 05, 2018

Applies to:

JD Edwards EnterpriseOne Tools - Version 9.1 and later
Information in this document applies to any platform.


When attempting to start the RTE instance from SM or WLS Console, the following error occurs.

its status remains in "Starting" (as per WLS Console it is "Not reachable"

In the WLS RTE instance *.out log: 


<Jan 2, 2018 4:00:20 PM GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING.>
<Jan 2, 2018 4:00:20 PM GMT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool.>
<Jan 2, 2018 4:00:20 PM GMT> <Info> <WorkManager> <BEA-002942> <CMM memory level becomes 0. Setting standby thread pool size to 256.>
<Jan 2, 2018 4:00:21 PM GMT> <Notice> <Log Management> <BEA-170019> <The server log file D:\Oracle\Middleware\Weblogic_12.1.3\user_projects\domains\JDE_RTE\servers\RTE\logs\RTE.log is opened. All server side log events will be written to this file.>
<Jan 2, 2018 4:20:53 PM GMT> <INFO> <NodeManager> <The server 'RTE' with process id 968 is no longer alive; waiting for the process to die.>
<Jan 2, 2018 4:20:53 PM GMT> <FINEST> <NodeManager> <Process died.>
<Jan 2, 2018 4:20:53 PM GMT> <FINEST> <NodeManager> <Process is killed 968 with Server was killed>
<Jan 2, 2018 4:20:53 PM GMT> <INFO> <NodeManager> <Server was killed>
<Jan 2, 2018 4:20:53 PM GMT> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
<Jan 2, 2018 4:20:53 PM GMT> <FINEST> <NodeManager> <Finished killing process>


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.