Fixes are available
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
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.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
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.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
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.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
The problem is seen on Websphere Application Server Version 7.0.0.39. The problem only happens when an application is mapped to an application server and a web server. Here are the steps to recreate the issue: 1. Upgrade to 7.0.0.39 2. Map an application to an app server and a web server. 3. Start the application. No issues. 4. Stop the application from the administrative console. 5. The messages on the administrative console are: The application cannot be started on server webservernew on Node01. Verify that application server webservernew on Node01 has been started. Application DefaultApplication.ear on server server1 and node Node01 stopped successfully. 6. The DMGR's logs do not show any errors. 7. The server1's logs shows the application has been stopped.
Local fix
Ignore the error about the web server. - Keywords: console adminconsole webserver
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server who try to stop an application * * that is mapped to both an application * * server and a web server. * **************************************************************** * PROBLEM DESCRIPTION: You were prompted with an extraneous * * error message when stopping an * * application that is mapped to an app * * server and a web server. * **************************************************************** * RECOMMENDATION: * **************************************************************** If you try to stop an application that is mapped to both an application server and a web server, an extraneous message is shown. This happens because it is considering the status of the web server in the situation, which it should not. Only the status (stopped/started) of the application server should affect whether the application can be started or stopped.
Problem conclusion
Code has been changed to only consider the status of the web server in this situation. The fix for this APAR is currently targeted for inclusion in fix packs 7.0.0.41, 8.0.0.13, and 8.5.5.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
PI54236
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-12-15
Closed date
2016-02-17
Last modified date
2016-02-17
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
R700 PSY
UP
R800 PSY
UP
R850 PSY
UP
Document Information
Modified date:
27 April 2022