You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Hiram Chirino (JIRA)" <ji...@apache.org> on 2008/02/20 23:04:15 UTC
[jira] Created: (AMQ-1591) When using a JDBC based database locker
in an Master/Slave configuration, the lock is not updated.
When using a JDBC based database locker in an Master/Slave configuration, the lock is not updated.
--------------------------------------------------------------------------------------------------
Key: AMQ-1591
URL: https://issues.apache.org/activemq/browse/AMQ-1591
Project: ActiveMQ
Issue Type: Bug
Components: Broker
Affects Versions: 5.0.0
Reporter: Hiram Chirino
Assignee: Hiram Chirino
Fix For: 5.1.0
The lockKeepAlivePeriod field was intialized to 0 and no accessors are provided to initialize it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (AMQ-1591) When using a JDBC based database locker
in an Master/Slave configuration, the lock is not updated.
Posted by "Dave Stanley (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dave Stanley resolved AMQ-1591.
-------------------------------
Resolution: Fixed
The DB lock is getting refreshed correctly now.
One symptom of this bug was that when using a mySQL backed store, the lock would expire (due to inactivity) after about 12 hours. If the broker was setup as a master-slave, the slave would try and become the master but this would fail as the master was still listening ...
{code}
INFO DefaultDatabaseLocker - Attempting to acquire the exclusive lock
to become the Master broker
INFO DefaultDatabaseLocker - Becoming the master on dataSource: org.ap
ache.commons.dbcp.BasicDataSource@16917ee
ERROR BrokerService - Failed to start ActiveMQ JMS Message Brok
er. Reason: java.io.IOException: Transport Connector could not be registered in
JMX: Failed to bind to server socket: tcp://localhost:61616 due to: java.net.Bin
dException: Address already in use
java.io.IOException: Transport Connector could not be registered in JMX: Failed
to bind to server socket: tcp://localhost:61616 due to: java.net.BindException:
Address already in use
at org.apache.activemq.util.IOExceptionSupport.create(IOExceptionSupport
.java:27)
at org.apache.activemq.broker.BrokerService.registerConnectorMBean(Broke
rService.java:1298)
at org.apache.activemq.broker.BrokerService.startTransportConnector(Brok
erService.java:1744)
at org.apache.activemq.broker.BrokerService.startAllConnectors(BrokerSer
vice.java:1695)
at org.apache.activemq.broker.BrokerService.start(BrokerService.java:439
)
{code}
/Dave
> When using a JDBC based database locker in an Master/Slave configuration, the lock is not updated.
> --------------------------------------------------------------------------------------------------
>
> Key: AMQ-1591
> URL: https://issues.apache.org/activemq/browse/AMQ-1591
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.0.0
> Reporter: Hiram Chirino
> Assignee: Hiram Chirino
> Fix For: 5.1.0
>
>
> The lockKeepAlivePeriod field was intialized to 0 and no accessors are provided to initialize it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1591) When using a JDBC based database
locker in an Master/Slave configuration, the lock is not updated.
Posted by "Hiram Chirino (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=41346#action_41346 ]
Hiram Chirino commented on AMQ-1591:
------------------------------------
The lockKeepAlivePeriod is now initialized to 30 seconds and accessors have been added so this can now be configured.
> When using a JDBC based database locker in an Master/Slave configuration, the lock is not updated.
> --------------------------------------------------------------------------------------------------
>
> Key: AMQ-1591
> URL: https://issues.apache.org/activemq/browse/AMQ-1591
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.0.0
> Reporter: Hiram Chirino
> Assignee: Hiram Chirino
> Fix For: 5.1.0
>
>
> The lockKeepAlivePeriod field was intialized to 0 and no accessors are provided to initialize it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.