Fixes are available
Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR10 Cumulative Fix for WebSphere Application Server
6.1.0.31: Java SDK 1.5 SR11 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
6.1.0.29: Java SDK 1.5 SR11 Cumulative Fix for WebSphere Application Server
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
APAR status
Closed as program error.
Error description
Problem is seen updating an application. The field "Relative path to module" allows the value to begin with a slash (/). When this value is used the application.xml becomes invalid and any additional updates to the application results in the error: MBeanHelper E Could not invoke an operation on object: WebSphere:platform=proxy, cell=cellname,version=6.0.2.17,name=AppManagement, mbeanIdentifier=AppManagement,type=AppManagement, node=nodename,process=dmgr because of an mbean exception: com.ibm.websphere.management.exception.AdminException: - Here are the steps to recreate the problem: 1. From Admin Console, Applications > Enterprise Applications 2. select application, click Update 3. select "single Module" radio button 4. In "Relative path to module" filed enter a new file with a slash in the beginning, such as: /Increment.jar 5. Fill out the rest of the panel and click next. 6. Complete the update process 7. Click save. A Save Conflict error is seen. Click to save the changes that were made. 8. reviewing the application.xml file you will see this update was made: <module> <ejb>/Increment.jar</ejb> </module> 9. Attempting the update again the following errors are seen: In the Systemout.log: MBeanHelper E Could not invoke an operation on object: WebSphere:platform=proxy,cell=cellname,version=6.0.2.17, name=AppManagement,mbeanIdentifier=AppManagement, type=AppManagement,node=nodename,process=dmgr because of an mbean exception: com.ibm.websphere.management.exception.AdminException: - In the trace.log: SystemErr R com.ibm.etools.j2ee.commonarchivecore.exception. NoModuleFileException: A file does not exist for module element having uri: /Increment.jar SystemErr R Caused by:com.ibm.etools.j2ee.commonarchivecore.exception. DeploymentDescriptorLoadException: IWAE0022E Exception occurred loading deployment descriptor for module "/Increment.jar" in EAR file "C:\WASV6\WebSphere\AppServer\profiles\profname\wstemp \0\workspace\cells\cellname\applications\ DefaultApplication.ear\deployments\DefaultApplication" - The admin console should be changed to not allow a "Relative path to module" value that begins with /.
Local fix
To clean up the problem: 1. Stop the app server 2. Find the Ear file in the config\cells\cellname\applications folder 3. Open APP.ear\deployments\APP\META-INF\application.xml 4. Remove the extraneous <module> and <ejb> tags, <module> <ejb>/JARNAME.jar</ejb> </module> 5. Make the same change in the EAR file under the installapps directory. 6. Restart the app server 7. Now you can do the update again. - Search Keywords: jar ear war app installedapps applications /
Problem summary
**************************************************************** * USERS AFFECTED: Users of Websphere Application Server * * version 6.0.2 and 6.1 * **************************************************************** * PROBLEM DESCRIPTION: Problem in Administrative Console when * * accepting a "/" for the jar name in * * the "Relative path to module" field. * **************************************************************** * RECOMMENDATION: * **************************************************************** When customer does a Single module Update, the Administrative Console accepts a preceding slash "/" in the jar name in the "Relative path to module" field. Once the update is done and configuration is saved, they are not able to update the application further. A Null error in the Administrative console is seen when performing subsequent single module updates.
Problem conclusion
Code Changes are made such that a warning is issued to prevent customer from entering a value beginning with "/" . The fix for this APAR is currently targeted for inclusion in fixpacks 6.0.2.29 and 6.1.0.17. 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
PK54446
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
60S
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2007-10-10
Closed date
2008-02-18
Last modified date
2008-02-18
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
ADMIN
Fix information
Fixed component name
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R60A PSY
UP
R60H PSY
UP
R60I PSY
UP
R60P PSY
UP
R60S PSY
UP
R60W PSY
UP
R60Z PSY
UP
R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
Document Information
Modified date:
29 December 2021