PQ55362: WHEN JAVA CLIENT USES MULTIPLE ORBS AND THREADS TO ACCESS WAS, IT RECEIVES COMMUNCIATION EXCEPTION FROM NAMING & CORBA COMPS | |||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||
APAR status Closed as program error. Error description Java client starts multiple EJB client threads (each doing a JNDI Lookup), it seems there is a threshold (for example, 6 on Linux, 30-40 on Windows 2000). Beyond which the java client get the following exception: [java] javax.naming.CommunicationException: Caught CORBA.COMM_FAILURE when resolving initial reference=WsnNameService. Root exception is org.omg.CORBA.COMM_FAILURE: minor code: 3 completed: No [java] Test3: SimpleSessionClient general exception: Caught CORBA.COMM_FAILURE when resolving initial reference=WsnNameServicenNameServiceLocal fix Problem summary **************************************************************** * USERS AFFECTED: All WebSphere Application Server users of * * multiple JNDI lookups in a single process * * to a naming server. * **************************************************************** * PROBLEM DESCRIPTION: Instantiating multiple initial_context * * objects in a single process to do * * JNDI lookup on a naming server. * **************************************************************** * RECOMMENDATION: * **************************************************************** An application, such as EJB client, instantiates multiple initial_context objects to do bootstrap and JNDI lookup toward a same WebSphere naming service. By doing so, client application implicitly create a new instance of ORB by instantiating an intial_context object each time, and eventually end up with multiple ORB instances in a single JVM. Multiple ORB instances run concurrently in a single JVM is not supported. The support configuration is one ORB per JVM.Problem conclusion When a client application accidently instantiates multiple initial_context objects in a single client process to do bootstraping and JNDI lookup to a naming service. We guarentee there will be only one ORB instance used at all time.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ55362
IBM Group: Software Group
Modified date: Jan 21, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.