Some crash recovery scenarios on MsSQL DB with JTS ends with locked table. This is not a regression against EAP 7.4. This is related with locking mechanism that should be described in JBEAP-26548, but locking itself may be caused by wrong server behaviour because:

• But if I check the table after the scenario (EAP server is properly shut-downed), the table is accessible (not locked for reading)
• If I kill the server right after recovery, the table is not readable even after the test ends
• So is it possible that some connection to DB is not properly ended after recovery or once server is killed, but is properly ended during proper server shutdown?

I also tried to change lock timeout value in DB server and adds some waiting in tests, but it didn't help:

SET LOCK_TIMEOUT 1800;
SELECT @@LOCK_TIMEOUT AS [Lock Timeout];
GO

Long sleep (1h+) doesn't help as well.