Troubleshooting
Problem
The following details the position of WebSphere Application Server Support regarding the usage of java.lang.System.exit() from within an application deployed to a WebSphere Application Server.
Symptom
The usage of System.exit() in application code can result in a number of different problematic scenarios for the application server and any other applications that may be running on the application server.
Some of these symptoms include:
- Termination of all other applications after an application calls System.exit()
- Application server hangs after an application calls System.exit()
- Application server exits without a footprint after an application calls System.exit()
- ...
This list of symptoms is by no means exhaustive.
[{"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Component":"Not Applicable","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"},{"code":"PF027","label":"Solaris"}],"Version":"9.0;8.5.5;8.5;8.0;7.0","Edition":"","Line of Business":{"code":"LOB77","label":"Automation Platform"}}]
Log InLog in to view more of this document
This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.
Was this topic helpful?
Document Information
Modified date:
03 March 2025
UID
swg21640794