You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Use of Liberty's HTTP AccessLogging mechanism prevents CICS JVM's from terminating.
In the AccessLogger class, a Timer instance field is initialised when the class is loaded, this causes creation of a non-daemon thread that can prevent the JVM from terminating gracefully.
Observed in the field during JVM termination in environments like z/OS.
It also appears to be unused throughout the class, leading to unnecessary resource allocation.
Steps to Reproduce
Issue a STOP to the server in environments like z/OS, taking a JAVADUMP would reveal non-daemon Timer Thread, which remains active and block a graceful termination of JVM
Expected behavior
A non-daemon thread shouldn't be spawned so that the JVM can be terminated gracefully.
Diagnostic information:
OpenLiberty Version: 24.0.0.9
Affected feature(s) accessLogging
Java Version: NA
The text was updated successfully, but these errors were encountered:
Describe the bug
Use of Liberty's HTTP AccessLogging mechanism prevents CICS JVM's from terminating.
In the AccessLogger class, a Timer instance field is initialised when the class is loaded, this causes creation of a non-daemon thread that can prevent the JVM from terminating gracefully.
Observed in the field during JVM termination in environments like z/OS.
It also appears to be unused throughout the class, leading to unnecessary resource allocation.
Steps to Reproduce
Issue a STOP to the server in environments like z/OS, taking a JAVADUMP would reveal non-daemon Timer Thread, which remains active and block a graceful termination of JVM
Expected behavior
A non-daemon thread shouldn't be spawned so that the JVM can be terminated gracefully.
Diagnostic information:
The text was updated successfully, but these errors were encountered: