WAS for z/OS Liberty reconnects to RRS when RRS is terminated and restarted.

Backgrounds

Customer is planning to migrate from WAS for z/OS traditional to WAS for z/OS Liberty and is validating whether or not there are some incompatibility, and also there are no problem through the extensive testing. When customer conducted RRS failure test scenario, they found that WAS for z/OS Liberty continues running without ABENDing after RRS failure. In case of WAS for z/OS traditional, it terminates with ABENDing and reconnects successfully to RRS after both the server and RRS are restarted, allowing transaction processing to continue normally.

Problem description

In case of WAS for z/OS Liberty, it continues running after RRS failure, but doesn’t reconnect to RRS. Currently we have to restart WAS for z/OS Liberty server to reconnect to RRS, which mean an interruption is required manually or by automation products and the transaction processing cannot be performed until server is restarted. It will take some time to restart if a large number of servers are running. Ideally WAS for z/OS Liberty should reconnect to RRS automatically when RRS is restarted so that transaction processing can continue normally, equivalent to Db2 and MQ. If automatic reconnect to RRS is not feasible, then next idea is to restart WAS for z/OS Liberty server automatically when RRS failure, equivalent to WAS for z/OS traditional.