PQ71247: APPLICATION SERVER DOES NOT START AFTER INSTALLING THE EMBEDDED MESSAGING SUPPORT AFTER AN INSTALL OF WAS 5.0 | |||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||
APAR status Closed as fixed if next. Error description Customer installs WAS 5.0, then does a custom install to install the embedded messaging. After the messaging is installed the a pplication server does not start. The following errors are gene rated: W WSVR0307W: Invalid namespace, resources.jms.internalmessaging at line 7 W WSVR0303W: Invalid element tagname, connectionPool, at line 8 W WSVR0303W: Invalid element tagname, sessionPool, at line 9 W WSVR0307W: Invalid namespace, resources.jms.internalmessaging, at line 11 Also, java.lang.NullPointerException at com.ibm.ws.runtime.component.ResourceMgrImpl.installResources (ResourceMgrImpl.java:519) at com.ibm.ws.runtime.component.ResourceMgrImpl.loadResources (ResourceMgrImpl.java:413) at com.ibm.ws.runtime.component.ResourceMgrImpl.start (ResourceMgrImpl.java:362) at com.ibm.ws.runtime.component.ContainerImpl.startComponents (ContainerImpl.java:343) at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImp . The problem is due to the xml namespace resources.jms.internalme ssaging has not been defined. This happens when the plant sampl e is installedLocal fix Add the following as an attribute to the xmi:XMI tag in the resources.xml file xmlns:resources.jms.internalmessaging= "http://www.ibm.com/websphere/appserver/schemas/ 5.0/resources.jms.internalmessaging.xmi"Problem summary **************************************************************** * USERS AFFECTED: Users installing WebSphere Application * * Serverv 5.0 Base and Network Deployment * * (without Embedded Messaging) first and then * * later on installing Embedded Messaging * * on top of the Base and Network * * Deployment install. * **************************************************************** * PROBLEM DESCRIPTION: After installing the Embedded * * Messaging component, users will see * * errors in the SystemOut.log file * * when starting server1 : * * * * Config Error I WSVR0300I: Problems * * found in WebSphere_Home/config/cells/ * * cell_name/nodes/node_name/ * * resources.xml. * **************************************************************** * RECOMMENDATION: * **************************************************************** This APAR is being closed FIN with concurrence from the submitting customer. This means that a fix to this APAR is expected to be delivered from IBM in a release which is being developed at the time that the APAR was closed. The latest release of the product to exit development at the time this APAR was closed was: WebSphere Application Server 5.0 **************************************** The resources.xml file is not being updated during installation. Suggested Workaround: Need to add the following as an attribute to the xmi:XMI tag in the resources.xml file: xmlns:resources.jms.internalmessaging="http://www.ibm.com/ websphere/appserver/schemas/5.0/ resources.jms.internalmessaging.xmi"Problem conclusion 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 Publications Referenced
|
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 00S
Software edition:
Reference #: PQ71247
IBM Group: Software Group
Modified date: Jul 30, 2003
(C) Copyright IBM Corporation 2000, 2008. All Rights Reserved.