Fixes are available
APAR status
Closed as program error.
Error description
When adding application to server in RAD 7 studio or issuing run on server, binary JAR file in EAR causes the error of "cannot open nested JAR file" to be displayed in console view of the server.
Local fix
NA
Problem summary
**************************************************************** * USERS AFFECTED: All Rational Application Developer v7.0 * * and WebSphere Application Server Toolkit * * v6.1 users publishing applications to a * * version 6.x WebSphere Application Server * **************************************************************** * PROBLEM DESCRIPTION: When publishing an application to a * * v6.x WebSphere Application Server, * * binary JAR files residing in the * * Enterprise Application project or the * * WEB-INF\lib folder of a Web project * * are being included on the * * looseconfig.xml file causing an * * OpenFailureException when the * * application is published to WebSphere * * Application Server. * **************************************************************** * RECOMMENDATION: * **************************************************************** When publishing an application to a v6.x WebSphere Application Server, binary JAR files residing in the Enterprise Application project or the WEB-INF\lib folder of a Web project are being included on the looseconfig.xml file causing an OpenFailureException when the application is published to WebSphere Application Server. An example exception in the console is: *** ERROR ***: Mon Apr 16 20:29:56 EDT 2007 org.eclipse.jst.j2ee.commonarchivecore.internal.exception .OpenFailureException: IWAE0034E Could not open the nested archive "test.jar" in "D:\workspace\MyEAR" at org.eclipse.jst.j2ee.commonarchivecore.internal.impl. CommonarchiveFactoryImpl.openNestedArchive (CommonarchiveFactoryImpl.java:705) at org.eclipse.jst.j2ee.commonarchivecore.internal.impl. ArchiveImpl.openNestedArchive(ArchiveImpl.java:1096) at org.eclipse.jst.j2ee.commonarchivecore.internal.impl. EARFileImpl.openNestedArchive(EARFileImpl.java:636) at org.eclipse.jst.j2ee.commonarchivecore.internal.strategy. LoadStrategyImpl.openNestedArchive(LoadStrategyImpl.java:466) at org.eclipse.jst.j2ee.commonarchivecore.internal.strategy. LoadStrategyImpl.collectFilesFromLooseArchives (LoadStrategyImpl.java:300) at org.eclipse.jst.j2ee.commonarchivecore.internal.strategy. LoadStrategyImpl.collectFiles(LoadStrategyImpl.java:280)
Problem conclusion
Static binary JAR files will no longer be included in the generated looseconfig.xmi file when publishing an application from Rational Application Developer v7.0 or WebSphere Application Server Toolkit v6.1 and the WebSphere Application Server runtime can locate them without the need of the looseconfig entry. The fix for this APAR is currently targeted for inclusion in Rational Application Developer v7.0.0.4 and WebSphere Application Server Toolkit v6.1.1.4. Please refer to the Recommended Updates page for WebSphere Application Server Toolkit delivery information: http://www.ibm.com/support/docview.wss?uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PK43743
Reported component name
WEBAPP SERVER A
Reported component ID
5724J0820
Reported release
610
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2007-04-20
Closed date
2007-04-24
Last modified date
2007-04-24
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
WEBAPP SERVER A
Fixed component ID
5724J0820
Applicable component levels
R610 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
19 October 2021