Error "javax.naming.CommunicationException: Failed to initialize JNDI context" when Accessing Java Client Application via F5 Load Balancer
(Doc ID 2708069.1)
Last updated on MAY 26, 2023
Applies to:Oracle WebLogic Server - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
While accessing Java client application via F5 load balancer, which 'subscribes' to the JMS Topics and accesses the messages available in JMS Topics, it fails with the below errors:
Complete setup is as below:
- A SOA project hosted on Weblogic which feeds persistent messages into the Weblogic JMS Topics.
- An external Java application 'subscribes' to these JMS Topics and accesses the messages available in JMS Topics.
- The java application uses t3 protocol to subscriber to these JMS Topics.
- A new F5 load balancer introduced in this setup so that all the traffic goes via F5.
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