PQ58724: NAMINGEXCEPTION ON STARTUP OF AE (AND AES WITHIN WSAD) | |||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description CMVC Defect 117813 Another IBM group (customer of WSAD product) has just recently moved up from WSAD v4.0 (which contains WAS AEs v4.0.1) to WSAD v4.0.2 (which contains WAS AEs v4.0.2). Upon migrating to the newer version, and making no modifications to the user workspace/configuration, the customer discovered that none of their EJB projects would startup in the server. Upon investigating further, we discovered that they were trying to use the default datasource that was configured in the server for their EJB module/beans - hence they did not want to bind a datasource JNDI name to each individual module. If the module is explicitly bound with a datasource JNDI name, the server will start successfully. To rule out that this was a WSAD problem, I created a simple EAR project and deployed it to a WAS AE v4.0.2 server and I got the same results. The exception is: [1/18/02 15:47:00:590 EST] 221bc413 Helpers W NMSV0610I: A NamingException is being thrown from a javax.naming.Context implementation. Details follow: Context implementation: com.ibm.ejs.ns.jndi.CNContextImpl Context method: lookup Context name: domainRoots/UnspecifiedDomainName/legacyRoot Target name: local:jdbc/jdbc/db2eclipse Other data: Exception stack trace: javax.naming.ConfigurationException: NamingManager.getURLContext can not find the factory for this scheme: local . The customer says that they had no problems getting the server to start in v4.0.1 without having to explicitly specify a datasource JNDI name for each module (that is, using the server's default datasource).Local fix Problem summary **************************************************************** * USERS AFFECTED: WebSphere Application Server 4.0.2 users of * * EJB projects. * **************************************************************** * PROBLEM DESCRIPTION: After 4.0.2, the default datasource * * configured in the server for the EJB * * module/beans was being used, causing no * * EJB projects to startup in the server. * **************************************************************** * RECOMMENDATION: * **************************************************************** Code added in 4.0.2 to correct a problem WebSphere Commerce Suite was seeing had to be undone (defect 113007.1). This original problem has now been corrected, but requires another APAR to be applied as a pre-req. The needed APAR number is PQ57046. Note, this is a AE pre-req only, AEs users only need this fix.Problem conclusion Changes were made in the following runtime classes to correct this problem: ResourceBinder.java Server.javaTemporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
SRLS
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ58724
IBM Group: Software Group
Modified date: Mar 21, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.