-
Bug
-
Resolution: Won't Do
-
Major
-
None
-
7.3.x
-
3
-
False
-
False
-
-
-
-
-
-
Undefined
-
https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_application_platform/7.3/html/configuring_messaging/configuring_persistence states "journal-jdbc-lock-expiration: The time a JDBC lock is considered valid without keeping it alive. The default value is 20000 milliseconds. " which is correct BUT given that the unit we use in EAP to configure this is SECONDS it should be updated to journal-jdbc-lock-expiration: The time a JDBC lock is considered valid without keeping it alive. The default value is {{20 }}seconds. "