You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Gary Tully (JIRA)" <ji...@apache.org> on 2008/09/09 12:09:59 UTC
[jira] Created: (AMQ-1931) Externalize the 'sleepTime' field in
the DefaultDatabaseLocker class.
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.
[jira] Updated: (AMQ-1931) Externalize the 'sleepTime' field in
the DefaultDatabaseLocker class.
Posted by "Gary Tully (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Tully updated AMQ-1931:
----------------------------
Description:
user quote:
{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.{quote}
was:
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.??
tidy comment. the fix is as requested, attribute name is no longer sleepTime, now lockAcquireSleepInterval
Simpler constructor to DefaultDatabaseLocker that takes just a JDBCPersistenceAdapter, makes it easier to create for injection via spring.
> 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:
> {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.{quote}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (AMQ-1931) Externalize the 'sleepTime' field in
the DefaultDatabaseLocker class.
Posted by "Gary Tully (JIRA)" <ji...@apache.org>.
[ 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.