Fixes are available
8.5.5.2: WebSphere Application Server V8.5.5 Fix Pack 2
8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
APAR status
Closed as program error.
Error description
An exception may occur when reading an EAR file. When this happens the WVE application routing rules will not recognize all URIs and modules that exist in the application. This stack is showing at the point of the error: at org.eclipse.jst.j2ee.commonarchivecore.internal.impl. CommonarchiveFactoryImpl.openEJBJarFile(CommonarchiveFactory Impl.java:1631) at org.eclipse.jst.j2ee.commonarchivecore.internal.impl.EARFile Impl.openNestedArchive(EARFileImpl.java:1452) at org.eclipse.jst.j2ee.commonarchivecore.internal.impl.EARFile Impl.openNestedArchive(EARFileImpl.java:1388) at org.eclipse.jst.j2ee.commonarchivecore.internal.strategy. LoadStr ategyImpl.openNestedArchive(LoadStrategyImpl.java:1461) at org.eclipse.jst.j2ee.commonarchivecore.internal.strategy. LoadStrategyImpl.createFile(LoadStrategyImpl.java:492) at org.eclipse.jst.j2ee.commonarchivecore.internal.strategy. DirectoryLoadStrategyImpl.addFile(DirectoryLoadStrategyImpl. java :665) at org.eclipse.jst.j2ee.commonarchivecore.internal.strategy. DirectoryLoadStrategyImpl.addFiles(DirectoryLoadStrategyImpl. java:738) at org.eclipse.jst.j2ee.commonarchivecore.internal.strategy. DirectoryLoadStrategyImpl.addFiles(DirectoryLoadStrategyImpl. java:677) at org.eclipse.jst.j2ee.commonarchivecore.internal.strategy. DirectoryLoadStrategyImpl.getFiles(DirectoryLoadStrategyImpl. java:935) at org.eclipse.jst.j2ee.commonarchivecore.internal.strategy. LoadStrategyImpl.collectFiles(LoadStrategyImpl.java:961) at org.eclipse.jst.j2ee.commonarchivecore.internal.impl.Container Impl.getFiles(ContainerImpl.java:443) at org.eclipse.jst.j2ee.commonarchivecore.internal.impl.EARFile Impl.getFiles(EARFileImpl.java:2693) at org.eclipse.jst.j2ee.commonarchivecore.internal.impl.EARFile Impl.getModuleFiles(EARFileImpl.java:1110) at com.ibm.ws.xd.config.workclass.util.ApplicationUtil.listWeb ServiceModuleNames(ApplicationUtil.java:854) at com.ibm.ws.xd.config.workclass.util.ApplicationUtil.listWeb ServiceModuleNames(ApplicationUtil.java:819) at com.ibm.ws.xd.config.operationalpolicy.appmgmt.XDInstall ApplicationTaskHandler.getAllWebServicesModuleNames(XDInstall ApplicationTaskHand ler.java:616) at com.ibm.ws.xd.config.operationalpolicy.appmgmt.XDInstall ApplicationTaskHandler.createDefaultWC(XDInstallApplication TaskHandler.java:325) at com.ibm.ws.xd.config.operationalpolicy.appmgmt.XDInstall ApplicationTaskHandler.performNewTask(XDInstallApplication TaskHandler.java:272) at com.ibm.ws.xd.config.operationalpolicy.appmgmt.XDInstall ApplicationTaskHandler.performTask(XDInstallApplication TaskHandler.java:100) at com.ibm.ws.management.application.SchedulerImpl.run(Scheduler Impl.java:315) at java.lang.Thread.run(Thread.java:772)
Local fix
n/a
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V8.5 * **************************************************************** * PROBLEM DESCRIPTION: When attempting to set routing rules * * for an application, modules are not * * shown. * **************************************************************** * RECOMMENDATION: * **************************************************************** An application has been installed; however, when attempting to set a routing rule via the administrative console, none of the modules are shown as available.
Problem conclusion
The code was updated to properly find all modules and show then as required. The fix for this APAR is currently targeted for inclusion in fix pack 8.5.5.2. 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
PM95560
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-08-21
Closed date
2013-12-04
Last modified date
2013-12-04
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
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R850 PSY
UP
Document Information
Modified date:
27 April 2022