APAR status
Closed as program error.
Error description
If the trace level is set to finest the system applications throw FileNotFoundException s for what would be their deployment.xml but the system seems to be working OK. Example error output... =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- [3/28/07 11:21:36:953 CEST] 0000000a SystemOut O java.io.FileNotFoundException: C:\Program Files\IBM\SDP70\runtimes\base_v6\profiles\default\config\cells\i bm-c6a04c007e1Node01Cell\applications\ManagementEJB.ear\deployme nts\ManagementEJB\deployment.xml (The system cannot find the path specified) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.<init>(FileInputStream.java:129) at org.eclipse.emf.ecore.resource.impl.URIConverterImpl.createF ileInputStream(URIConverterImpl.java:423) at org.eclipse.emf.ecore.resource.impl.URIConverterImpl.createI nputStream(URIConverterImpl.java:394) at org.eclipse.emf.ecore.resource.impl.ResourceImpl.load(Resour ceImpl.java:738) at com.ibm.wtp.emf.resource.CompatibilityXMIResourceImpl.load(C ompatibilityXMIResourceImpl.java:76) at com.ibm.websphere.resource.WASResourceImpl.load(WASResourceI mpl.java:60) at org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.demandLo ad(ResourceSetImpl.java:247) at org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.demandLo adHelper(ResourceSetImpl.java:262) at org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.getResou rce(ResourceSetImpl.java(Compiled Code)) at com.ibm.websphere.resource.WASResourceSetImpl.getResource(WA SResourceSetImpl.java:92) at com.ibm.ws.runtime.service.ConfigRootImpl.getResource(Config RootImpl.java:316) at com.ibm.ws.runtime.service.ConfigRootImpl.getResource(Config RootImpl.java:289) at com.ibm.ws.runtime.service.ConfigRootImpl.getResource(Config RootImpl.java:270) at com.ibm.ws.odc.cell.TreeBuilder.readApplication(TreeBuilder. java:1079) at com.ibm.ws.odc.cell.TreeBuilder.obtainAppNode(TreeBuilder.ja va:1680) at com.ibm.ws.odc.cell.TreeBuilder.stateChanged(TreeBuilder.jav a:406) at com.ibm.ws.runtime.component.ApplicationMgrImpl.stateChanged (ApplicationMgrImpl.java:1180) at com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDep loyedObjectEvent(DeployedApplicationImpl.java:1050) at com.ibm.ws.runtime.component.DeployedApplicationImpl.setStat e(DeployedApplicationImpl.java:210) at com.ibm.ws.runtime.component.DeployedApplicationImpl.start(D eployedApplicationImpl.java:737) at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplica tion(ApplicationMgrImpl.java:892) at com.ibm.ws.runtime.component.ApplicationMgrImpl$AppInitializ er.run(ApplicationMgrImpl.java:2003) at com.ibm.ws.runtime.component.ComponentImpl.runAsynchronousIn itializer(ComponentImpl.java:159) at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplica tions(ApplicationMgrImpl.java:745) at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(Applic ationMgrImpl.java:524) at com.ibm.ws.runtime.component.ContainerImpl.startComponents(C ontainerImpl.java:820) at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerIm pl.java:649) at com.ibm.ws.runtime.component.ApplicationServerImpl.start(App licationServerImpl.java:149) at com.ibm.ws.runtime.component.ContainerImpl.startComponents(C ontainerImpl.java:820) at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerIm pl.java:649) at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.jav a:408) at com.ibm.ws.runtime.WsServerImpl.bootServerContainer(WsServer Impl.java:187) at com.ibm.ws.runtime.WsServerImpl.start(WsServerImpl.java:133) at com.ibm.ws.runtime.WsServerImpl.main(WsServerImpl.java:387) at com.ibm.ws.runtime.WsServer.main(WsServer.java:53) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:85) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:58) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:60) at java.lang.reflect.Method.invoke(Method.java:391) at com.ibm.ws.bootstrap.WSLauncher.run(WSLauncher.java:219) at java.lang.Thread.run(Thread.java:570) =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Local fix
Do not turn trace on at the finest level
Problem summary
**************************************************************** * USERS AFFECTED: WebSphere Application Server version 6.0.2 * * users * **************************************************************** * PROBLEM DESCRIPTION: FileNotFoundException is thrown when * * trace is enabled. * * * **************************************************************** * RECOMMENDATION: * **************************************************************** When a trace level of fine is enabled, a deployment descriptor not found (FileNotFoundException) exception is thrown by the server.
Problem conclusion
Code has been modified to only throw the exception when it affects operation. This fix is included in PK41100 insteading of releasing multiple APARs that would then require the customer to install more than one APAR to resolve problem. The fix for this APAR is currently targeted for inclusion in fixpacks 6.0.2.21 and 6.1.0.9. Please refer to the recommended updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PK44564
Reported component name
WEBSPH APP SERV
Reported component ID
5724J0800
Reported release
60W
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2007-05-04
Closed date
2007-05-21
Last modified date
2007-07-23
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WEBSPH APP SERV
Fixed component ID
5724J0800
Applicable component levels
R60W PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
10 February 2022