Fixes are available
9.0.0.2: WebSphere Application Server traditional V9.0 Fix Pack 2
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
9.0.0.3: WebSphere Application Server traditional V9.0 Fix Pack 3
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
9.0.0.4: WebSphere Application Server traditional V9.0 Fix Pack 4
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
9.0.0.5: WebSphere Application Server traditional V9.0 Fix Pack 5
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
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
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11
Obtain the fix for this APAR.
APAR status
Closed as program error.
Error description
Customer used AdminApp.isAppReady and AdminApp.getDeployStatus to check the status of their applications in their wsadmin scripts. In this case, when they updated their applications, the expansion failed (due to running out of space in the zFS). But, they found AdminApp.isAppReady returned true and AdminApp.getDeployStatus showed distribution=true,expansion=notprocessing In this case, the expansion failed in webservices code and this doesn't set the exception correctly for the scripts to be notified of this error. Node agent joblog shows the error happens here: Trace: 2015/10/12 09:38:41.743 01 t=8C3580 c=UNK key=S2 (13007002) ThreadId: 0000033b FunctionName: com.ibm.ws.websvcs.wsdl.WASWSDLGenerator SourceId: com.ibm.ws.websvcs.wsdl.WASWSDLGenerator Category: SEVERE ExtendedMessage: BBOO0220E: WSWS7054E: The Web Services Description Language (WSDL) file could not be generated for the Web service implementation class because of the following error: java.lang.Exception: A WSDL Definition could not be generated for the implementation class This message shows the expansion failed: Trace: 2015/10/12 09:38:42.142 01 t=8C3580 c=UNK key=S2 (13007002) ThreadId: 0000033b FunctionName: com.ibm.ws.management.application.sync.AppDataMgr SourceId: com.ibm.ws.management.application.sync.AppDataMgr Category: AUDIT ExtendedMessage: BBOO0222I: ADMA7101E: An unexpected error occurred for the EAR expansion process. The enterprise archive (EAR) file is not extracted in the following paths
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server * **************************************************************** * PROBLEM DESCRIPTION: An application might fail to deploy * * but wsadmin functions isAppReady and * * getDeployStatus indicate success. * **************************************************************** * RECOMMENDATION: * **************************************************************** An application might fail to deploy but wsadmin functions isAppReady and getDeployStatus indicate success. This is due to wsdl generation code not notifying these admin functions that an exception has occurred.
Problem conclusion
Code is updated so an exception during WSDL generation will be correctly propagated back to the wsadmin code APAR PI54081 is currently targeted for inclusion in Fix Packs 7.0.0.43, 8.0.0.13, 8.5.5.11, and 9.0.0.3 of WebSphere Application Server. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 In addition, please refer to URL: http://www.ibm.com/support/docview.wss?rs=404&uid=swg27006970 for Fix Pack PTF information.
Temporary fix
Comments
APAR Information
APAR number
PI54081
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-12-14
Closed date
2016-09-22
Last modified date
2017-05-01
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
WEBSPHERE FOR Z
Fixed component ID
5655I3500
Applicable component levels
R700 PSY UI46199
UP17/04/24 P F704
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
Document Information
Modified date:
03 May 2022