ActiveMQ
  1. ActiveMQ
  2. AMQ-1310

[JDBCPersistenceAdapter] lockKeepAlivePeriod cannot be modified

    Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 4.1.0
    • Fix Version/s: 5.2.0
    • Component/s: Message Store
    • Labels:
      None

      Description

      The lockKeepAlivePeriod property in JDBCPersistenceAdapter is initialised to zero, and cannot be modified, so lock keep-alives can never be performed.

      It needs a setter method to configure this property via the spring file.

        Activity

        Hide
        Martin Murphy added a comment -

        I think this issue should be closed? Looking at the source today on the trunk:
        https://svn.apache.org/repos/asf/activemq/trunk/activemq-core/src/main/java/org/apache/activemq/store/jdbc/JDBCPersistenceAdapter.java
        I can see that this is initialised to 30 seconds and the setter method is there.

        Show
        Martin Murphy added a comment - I think this issue should be closed? Looking at the source today on the trunk: https://svn.apache.org/repos/asf/activemq/trunk/activemq-core/src/main/java/org/apache/activemq/store/jdbc/JDBCPersistenceAdapter.java I can see that this is initialised to 30 seconds and the setter method is there.
        Hide
        Gary Tully added a comment -

        fixed in 5.2

        Show
        Gary Tully added a comment - fixed in 5.2

          People

          • Assignee:
            Gary Tully
            Reporter:
            Kenny MacLeod
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development