Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-21997

Avoid confusion on configuring journal-jdbc-lock-expiration

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Major
    • None
    • 7.3.x
    • Documentation
    • 3
    • False
    • False
    • Undefined

    Description

      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. "

      Attachments

        Activity

          People

            Unassigned Unassigned
            ehugonne1@redhat.com Emmanuel Hugonnet
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: