Unable to Login to Agile PLM Java Client with Error "Failed to initialize JNDI context" when One of the Managed Server Is Down on WebLogic Clustered Environment
(Doc ID 2951645.1)
Last updated on JANUARY 24, 2024
Applies to:
Oracle Agile PLM Framework - Version 9.3.6.0 and laterInformation in this document applies to any platform.
Symptoms
Failover is not working for Java Client running on Agile clustered instance. When the Managed Server 1 is down, unable to login to Agile Product Lifecycle Management (PLM) Java Client with below error:
Error
Failed to initialize JNDI context, tried 2 time or times totally, the interval of
each time is 0ms..
t3://{managed_server1}.{domain_name}:{port}:Destination:xx.x.x.xxx,
{port} unreachable; nested exception is:
java.net.ConnectException: Connection
refused; connect; No available router to destination; nested exception is;
java.rmi.ConnectException:
No available router to destination.
Environmental Detail
- Agile is running on WebLogic clustered instance with two managed server nodes like below:
- Server1: Admin Server and Managed Server 1
- Server2: Managed Server 2 - Web Proxy is running, and Java Client is configured to access from Web Proxy URL.
Steps
The issue can be reproduced at will with the following steps:
- Login to WebLogic admin console, and stop Managed Server 1
- Access to Java Client URL: http(s)://{proxy_server}.{domain_name}.{port}/JavaClient.html
- Launch
- Give Username and password, and OK
- See the error message pops up
Changes
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 |