Troubleshooting
Problem
In WebSphere Application Server, a Deployment Manager or Application Server JVM will not start. No SystemOut.log entries are produced. Only the startServer.log for the failing JVM is updated with the stack trace documented below.
Symptom
The <WAS_HOME>/profiles/<PROFILE_NAME>/logs/<SERVER_NAME>/startServer.log will show an error similar to this:
************* End Display Current Environment *************
[10/16/13 17:41:20:255 BST] 0000000a ManagerAdmin I TRAS0017I: The startup trace state is *=info.
[10/16/13 17:41:20:511 BST] 0000000a AdminTool A ADMU0128I: Starting tool with the Dmgr01 profile
[10/16/13 17:41:20:516 BST] 0000000a AdminTool A ADMU3100I: Reading configuration for server: dmgr
[10/16/13 17:47:53:111 BST] 0000000a WsServerLaunc E ADMU3002E: Exception attempting to process server dmgr
[10/16/13 17:47:53:115 BST] 0000000a WsServerLaunc E ADMU3007E: Exception org.eclipse.emf.ecore.xmi.PackageNotFoundException: Package with uri 'http://www.ibm.com/websphere/appserver/schemas/6.0/sibresources.xmi' not found. (file:/opt/WebSphere/AppServer/profiles/Dmgr01/config/cells/TestCell/nodes/TestNode/servers/dmgr/server.xml, 65, 137)
at org.eclipse.emf.ecore.xmi.impl.XMLHandler.getPackageForURI(XMLHandler.java:2332)
at org.eclipse.emf.ecore.xmi.impl.XMLHandler.getFactoryForPrefix(XMLHandler.java:2170)
at org.eclipse.emf.ecore.xmi.impl.XMLHandler.createObjectFromTypeName(XMLHandler.java:1828)
at org.eclipse.emf.ecore.xmi.impl.XMLHandler.createObject(XMLHandler.java:1787)
at org.eclipse.emf.ecore.xmi.impl.XMLHandler.handleFeature(XMLHandler.java:1595)
at org.eclipse.emf.ecore.xmi.impl.XMLHandler.processElement(XMLHandler.java:888)
at org.eclipse.emf.ecore.xmi.impl.XMIHandler.processElement(XMIHandler.java:82)
at org.eclipse.emf.ecore.xmi.impl.XMLHandler.startElement(XMLHandler.java:867)
at org.eclipse.emf.ecore.xmi.impl.SAXWrapper.startElement(SAXWrapper.java:90)
at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
at org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl.parse(Unknown Source)
at org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load(XMLLoadImpl.java:179)
at org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.doLoad(XMLResourceImpl.java:179)
at org.eclipse.wst.common.internal.emf.resource.CompatibilityXMIResourceImpl.basicDoLoad(CompatibilityXMIResourceImpl.java:180)
at org.eclipse.wst.common.internal.emf.resource.CompatibilityXMIResourceImpl.doLoad(CompatibilityXMIResourceImpl.java:173)
at org.eclipse.emf.ecore.resource.impl.ResourceImpl.load(ResourceImpl.java:1094)
at org.eclipse.emf.ecore.resource.impl.ResourceImpl.load(ResourceImpl.java:900)
at org.eclipse.wst.common.internal.emf.resource.CompatibilityXMIResourceImpl.load(CompatibilityXMIResourceImpl.java:259)
at com.ibm.websphere.resource.WASResourceImpl.load(WASResourceImpl.java:61)
at org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.demandLoad(ResourceSetImpl.java:249)
at org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.demandLoadHelper(ResourceSetImpl.java:264)
at org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.getResource(ResourceSetImpl.java:390)
at com.ibm.websphere.resource.WASResourceSetImpl.getResource(WASResourceSetImpl.java:158)
at com.ibm.websphere.resource.WASResourceSetImpl.getResource(WASResourceSetImpl.java:143)
at com.ibm.ws.runtime.service.ConfigRootImpl.getResource(ConfigRootImpl.java:326)
at com.ibm.ws.runtime.service.ConfigRootImpl.getResource(ConfigRootImpl.java:299)
at com.ibm.ws.runtime.service.ConfigRootImpl.getResource(ConfigRootImpl.java:275)
at com.ibm.ws.management.tools.WsServerLauncher.initializeRepositoryAndLauncher(WsServerLauncher.java:397)
at com.ibm.ws.management.tools.WsServerLauncher.runTool(WsServerLauncher.java:265)
at com.ibm.ws.management.tools.AdminTool.executeUtility(AdminTool.java:264)
at com.ibm.ws.management.tools.WsServerLauncher.main(WsServerLauncher.java:120)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:592)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:263)
Cause
The most likely cause of this error is the presence of jar files in the <WAS_HOME>/lib directory which do not belong there.
Resolving The Problem
To resolve the problem, check the <WAS_HOME>/lib directory for jar files which were added after the initial installation was completed. This is the list of jar files which should normally be there:
.eclipseproduct
activation-impl.jar
aspectjrt.jar
base.jar
bootstrap.jar
bsf-engines.jar
commandlineutils.jar
EJBCommandTarget.jar
ffdcSupport.jar
htmlshell.jar
installver.jar
installxml.jar
iscdeploy.jar
ivblogbr.jar
IVTClient.jar
j2ee.jar
jacl.jar
launchclient.jar
lmproxy.jar
mail-impl.jar
marshall.jar
nif.jar
pc-appext.jar
physicalrep.jar
pmirm4arm.jar
rrd-appext.jar
rsadbutils.jar
rsahelpers.jar
serviceadapter.jar
sib.api.jmsra.rar
sib.ra.rar
sljc.jar
spy-sl.jar
spy.jar
sqlserver.jar
startup.jar
tcljava.jar
urlprotocols.jar
util.jar
wsatlib.jar
wsif-compatb.jar
You can compare your list of jar files against the list above or compare the list of jars from another working system in your environment.
In many cases, we found that the <WAS_HOME>/lib directory contained one or both of the following files which should NOT be placed there:
- com.ibm.ws.admin.client_6.1.0.jar
com.ibm.ws.webservices.thinclient_6.1.0.jar
Once the <WAS_HOME>/lib directory contains only the list of jars above, try to start the failing JVM again and see if the problem is resolved.
If the problem is not resolved, then you will need to contact IBM support for additional debugging assistance.
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21653536