High Availability For REIM Batch (Doc ID 2939258.1)

Last updated on SEPTEMBER 04, 2024

Applies to:

Symptoms

 SSO is enabled and cluster server setup for REIM managed servers. However, ReIM batch job is configured to connect to single node managed server instead of the cluster. Thus, when one of the managed server is down, the below errors happens:

javax.naming.CommunicationException: Failed to initialize JNDI context, tried 2 time or times totally, the interval of each time is 0ms.
t3://:9010: Destination , 9010 unreachable.; nested exception is:
java.net.ConnectException: Connection refused (Connection refused); No available router to destination.; nested exception is:

Please let us know on how we can implement high availability for these reim batch jobs. Thank you.

ERROR
-----------------------
avax.naming.CommunicationException: Failed to initialize JNDI context, tried 2 time or times totally, the interval of each time is 0ms.
t3://:9010: Destination , 9010 unreachable.; nested exception is:
java.net.ConnectException: Connection refused (Connection refused); No available router to destination.; nested exception is:

Cause

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