Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <37040857.1209479743595.JavaMail.jira@brutus>
Date: Tue, 29 Apr 2008 07:35:43 -0700 (PDT)
From: "Martin Murphy (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Commented: (AMQ-1310) [JDBCPersistenceAdapter]
 lockKeepAlivePeriod cannot be modified
In-Reply-To: <27333579.1183549472922.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/activemq/browse/AMQ-1310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=42492#action_42492 ] 

Martin Murphy commented on AMQ-1310:
------------------------------------

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.

> [JDBCPersistenceAdapter] lockKeepAlivePeriod cannot be modified
> ---------------------------------------------------------------
>
>                 Key: AMQ-1310
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1310
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Message Store
>    Affects Versions: 4.1.0
>            Reporter: Kenny MacLeod
>            Priority: Minor
>             Fix For: 5.2.0
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.