PQ98003: EJB LOOKUP() FAILS FROM SERVLET INIT() METHOD BEFORE APPLICATION SERVER IS FULLY INITIALIZED. | |||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description An EJB lookup from the servlet init() method fails before the WebSphere application server is open for e-business. This is because Naming is not initialized unless the JVM completes initialization. This apar fixes this problem.Local fix Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V5.0 for z/OS * **************************************************************** * PROBLEM DESCRIPTION: org.omg.CORBA.INTERNAL: minor code: * * C9C2110F completed: No; in WebSphere * * Controller while processing an EJB * * lookup request from it's Servant during * * application startup. * **************************************************************** * RECOMMENDATION: * **************************************************************** org.omg.CORBA.INTERNAL: minor code: C9C2110F completed: No occurs in WebSphere Controller while processing an EJB lookup request from it's Servant during application startup. Problem occurs on WebSphere Servers that are clustered. An attempt is being made to narrow the object to a Naming Context when it is not necessary. With Event trace active the following stack trace will be present for this error. org.omg.CORBA.INTERNAL: minor code: C9C2110F completed: No at java.lang.Class.newInstance0(Native Method) at java.lang.Class.newInstance(Class.java(Compiled Code)) at com.ibm.rmi.util.Utility.readSystemException (Utility.java:1534) at com.ibm.ws390.orb.ClientDelegate.invoke (ClientDelegate.java:823) at com.ibm.ws390.orb.ClientDelegate.is_a (ClientDelegate.java:470) at org.omg.CORBA.portable.ObjectImpl._is_a(ObjectImpl.java:82) at org.omg.CosNaming.NamingContextHelper.narrow (NamingContextHelper.java:66) at com.ibm.ws.naming.cosbase.WsnOptimizedNamingImplBase. .narrowToNC(WsnOptimizedNamingImplBase.java:2808) at com.ibm.ws.naming.ipcos.WsnOptimizedNamingImpl .resolveUnresolvedBinding(WsnOptimizedNamingImpl.java:1881) at com.ibm.ws.naming.ipcos.WsnOptimizedNamingImpl .resolve_binding(WsnOptimizedNamingImpl.java:1598) at com.ibm.ws.naming.ipcos.WsnOptimizedNamingImpl .do_resolve_complete_info(WsnOptimizedNamingImpl.java:1025) at com.ibm.ws.naming.cosbase.WsnOptimizedNamingImplBase .resolve_complete_info(WsnOptimizedNamingImplBase.java:1402) at com.ibm.WsnOptimizedNaming._NamingContextImplBase ._invoke(Unknown Source) at com.ibm.ws390.orb.CommonBridge.CORBAinvoke(CommonBridge.java: 1040) at com.ibm.ws390.orb.ORBEJSBridge.CORBAinvoke(ORBEJSBridge.java: 434)Problem conclusion WebSphere naming code was updated to determine if the object is a Naming Context before the narrow is attempted. APAR PQ98003 is associated with SERVICE LEVEL W502021 of WebSphere Application Server V5.0 for z/OS.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: PQ98007 Modules/Macros
Publications Referenced
|
Document Information |
Current web document: swg1PQ98003.html
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server for z/OS
Operating system(s):
Software version: 500
Software edition:
Reference #: PQ98003
IBM Group: Software Group
Modified date: Feb 16, 2005
(C) Copyright IBM Corporation 2000, 2009. All Rights Reserved.