Implement a function to detect hanging MDB applications and interrupt their execution.

Backgrounds
Customer is migrating from WAS for z/OS traditional to WAS for z/OS Liberty. During the migration, many incompatibilities have been identified between WAS for z/OS traditional and WAS for z/OS Liberty. We understand that WAS for z/OS traditional and WAS for z/OS Liberty are different products; however, from the customer’s perspective, IBM recommends migration to WAS for z/OS Liberty, nevertheless mandatory functions are not implemented in WAS for z/OS Liberty, which is considered a functional regression by the customer. In particular, customer places the highest priority on the ability to detect hanging MDB applications.

Problem
WAS for z/OS Liberty don’t have a capability to detect hanging MDB application. If hanging MDB application is not detected, there is no way to manage the hanging application. This is not allowed for mission critical banking online system. In case of WAS for z/OS traditional, it has the capability to detect the hanging MDB application, then it goes to MDB timeout. 
WAS for z/OS Liberty itself implements the function of “requestTiming” to detect a hang and interrupt the execution, but as of today, MDB is not subject to the requestTiming.

Customer Request
The customer requests IBM to implement a function to detect hanging MDB applications and interrupt their execution, identical or similar to the interruptHungRequests function in requestTiming. For example, in case of requestTiming in Servlet, CANCEL THREAD LOCAL is executed in Db2 for z/OS JDBC. Customer believes that similar behavior should be applicable to MDB applications, not only Servlet applications.