activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (AMQ-1931) Externalize the 'sleepTime' field in the DefaultDatabaseLocker class.
Date Tue, 09 Sep 2008 12:39:52 GMT

     [ https://issues.apache.org/activemq/browse/AMQ-1931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Gary Tully resolved AMQ-1931.
-----------------------------

    Resolution: Fixed

exposed lockAcquireSleepInterval attribute on JDBCPersistenceAdapter and DefaultDatabaseLocker
revision: 693449.

>  Externalize the 'sleepTime' field in the DefaultDatabaseLocker class.
> ----------------------------------------------------------------------
>
>                 Key: AMQ-1931
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1931
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Broker
>    Affects Versions: 5.1.0
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>             Fix For: 5.3.0
>
>
> user quote:
> ??We need the 'sleepTime' field of the DefaultDatabaseLocker class to be externalized.
We're using a custom (non-blocking) lock create statement and we need to make the sleepTime
a bit longer.
> Currently there's no mechanism to change the value of this field. 1000 ms is the default
and only possible value for 'sleepTime'.
> We need to have this value externalized to the JDBCPersistenceAdapter. There should be
a setter in the JDBCPersistenceAdapter, so that we are able to provide a custom value for
this field in our Spring context. This value should be then copied from JDBCPersistenceAdapter
to the DefaultDatabaseLocker when an instance of the DefaultDatabaseLocker is created.??

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


Mime
View raw message