J2EE Bad Practices: Use of System.exit()

Calling System.exit() from within a deployed J2EE application is a dangerous anti-pattern. It grants a single application the power to shut down the shared container, crashing every other application and service running on the same server. This creates a severe reliability issue and an immediate vector for Denial-of-Service (DoS) attacks, as even an unprivileged user might trigger a code path that calls this method. Instead of using System.exit(), applications should manage their lifecycle gracefully through the container's administrative interfaces. Error conditions should be handled using exception mechanisms that log the issue and return an appropriate error response to the user, allowing the container and other co-hosted applications to continue running normally. This approach maintains system stability and aligns with the managed, multi-application environment that J2EE containers are designed to provide.