Home / Messaging / Fix ActiveMQ JDBC Lock Expired

Messaging

Fix ActiveMQ JDBC Lock Expired

Resolve ActiveMQ JDBC lock expired errors by configuring lock keepalive, database connection settings, and failover handling.

Published: Apr 3, 20267 min readBy FixWikiHub Editorial Team

Abstract illustration for a troubleshooting knowledge base category.

Introduction

ActiveMQ uses JDBC master-slave replication where one broker holds a database lock. If the lock renewal fails or the lease expires, the broker loses its master status, potentially causing split-brain or failover issues.

Symptoms

Lock expired:

```bash $ tail -f /var/log/activemq/activemq.log

[ERROR] Failed to renew database lock: Lock has been held by another broker [WARN] Master broker lost lock, becoming slave [ERROR] org.apache.activemq.store.jdbc.JDBCPersistenceAdapter - Lock keepalive failed ```

Database connection error:

bash

[ERROR] Cannot acquire database lock: Connection refused to database
[ERROR] java.sql.SQLException: Connection is closed

Split-brain warning:

bash

[WARN] Multiple brokers claiming master status detected
[ERROR] Network partition detected: both brokers claiming lock ownership

Common Causes

1.Lock keepalive timeout too short - Broker can't renew lock fast enough
2.Database connection issues - Connection dropped before renewal
3.Database overloaded - Slow response prevents lock renewal
4.Network latency - High latency causes renewal delays
5.Lock acquired by another broker - Another broker stole the lock
6.JDBC driver issues - Driver connection pooling problems

Step-by-Step Fix

Step 1: Check Lock Status

```bash # Check if broker is master curl -u admin:admin http://localhost:8161/api/jolokia/read/org.apache.activemq:type=Broker,brokerName=localhost/MasterBroker

# Check lock table in database # MySQL: mysql -u activemq -p -e "SELECT * FROM activemq.ACTIVEMQ_LOCK;"

# PostgreSQL: psql -U activemq -d activemq -c "SELECT * FROM activemq_lock;"

# Oracle: sqlplus activemq@activemq "SELECT * FROM ACTIVEMQ_LOCK;"

# Check lock acquisition time # In activemq.log: grep -i "acquired lock|lost lock" /var/log/activemq/activemq.log | tail -20 ```

Step 2: Configure Lock Keepalive

```xml  <persistenceAdapter> <jdbcPersistenceAdapter dataSource="#mysql-ds" lockKeepAlivePeriod="5000" lockAcquireSleepInterval="10000" createTablesOnStartup="false"> <locker> <databaseLocker lockAcquireSleepInterval="10000"/> </locker> </jdbcPersistenceAdapter> </persistenceAdapter>

<jdbcPersistenceAdapter dataSource="#mysql-ds" lockKeepAlivePeriod="10000"/> ```

Step 3: Configure Database Connection Pool

```xml  <bean id="mysql-ds" class="org.apache.commons.dbcp2.BasicDataSource" destroy-method="close"> <property name="driverClassName" value="com.mysql.jdbc.Driver"/> <property name="url" value="jdbc:mysql://localhost:3306/activemq?autoReconnect=true"/> <property name="username" value="activemq"/> <property name="password" value="password"/> <property name="maxTotal" value="20"/> <property name="maxIdle" value="10"/> <property name="minIdle" value="5"/> <property name="validationQuery" value="SELECT 1"/> <property name="testOnBorrow" value="true"/> <property name="testWhileIdle" value="true"/> <property name="timeBetweenEvictionRunsMillis" value="30000"/> <property name="minEvictableIdleTimeMillis" value="60000"/> </bean>

<property name="url" value="jdbc:mysql://localhost:3306/activemq?autoReconnect=true&connectTimeout=5000&socketTimeout=30000"/> ```

Step 4: Check Database Connectivity

```bash # Test database connection mysql -h db-host -u activemq -p activemq -e "SELECT 1;"

# Check database response time mysql -h db-host -u activemq -p -e "SELECT BENCHMARK(1000000, SHA1('test'));"

# Check database status mysqladmin -h db-host status

# Check for connection limits mysql -h db-host -u activemq -p -e "SHOW VARIABLES LIKE 'max_connections';" mysql -h db-host -u activemq -p -e "SHOW STATUS LIKE 'Threads_connected';"

# Check network latency to database ping db-host traceroute db-host ```

Step 5: Handle Lock Acquisition Failures

```bash # If lock was stolen by another broker # Check which broker has the lock curl -u admin:admin http://localhost:8161/api/jolokia/read/org.apache.activemq:type=Broker,brokerName=*/MasterBroker

# Stop broker that shouldn't be master systemctl stop activemq

# Clear lock table manually (emergency only) mysql -u activemq -p -e "DELETE FROM activemq.ACTIVEMQ_LOCK;"

# Restart broker that should be master systemctl start activemq

# Watch lock acquisition tail -f /var/log/activemq/activemq.log | grep -i "lock" ```

Step 6: Use Lease Database Locker

```xml  <persistenceAdapter> <jdbcPersistenceAdapter dataSource="#mysql-ds"> <locker> <lease-databaseLocker lockAcquireSleepInterval="10000" leaseHolderId="broker-1" leaseKeepAlivePeriod="5000" leaseExpirationTime="60000"/> </locker> </jdbcPersistenceAdapter> </persistenceAdapter>

```

Step 7: Configure Network Timeout

```xml  <bean id="mysql-ds" class="org.apache.commons.dbcp2.BasicDataSource"> <property name="url" value="jdbc:mysql://db-host:3306/activemq?connectTimeout=10000&socketTimeout=60000&autoReconnect=true"/> </bean>

<property name="url" value="jdbc:postgresql://db-host:5432/activemq?connectTimeout=10&socketTimeout=60&loginTimeout=10"/>

<property name="url" value="jdbc:oracle:thin:@db-host:1521:activemq?connectTimeout=10000"/> ```

Step 8: Monitor Lock Health

```bash # Check lock renewal in logs grep -i "renewed lock|keepalive" /var/log/activemq/activemq.log | tail -50

# Enable lock logging # In logging.properties: log4j.logger.org.apache.activemq.store.jdbc=DEBUG log4j.logger.org.apache.activemq.store.jdbc.locker=DEBUG

# Monitor via JMX curl -u admin:admin http://localhost:8161/api/jolokia/read/org.apache.activemq:type=Broker,brokerName=localhost/PersistenceAdapter/lockTime

# Set up alerting for lock failures grep -i "lost lock|failed to renew" /var/log/activemq/activemq.log ```

Step 9: Handle Split-Brain Scenario

```bash # If multiple brokers claiming master status # Stop all brokers systemctl stop activemq

# Check lock table mysql -u activemq -p -e "SELECT * FROM activemq.ACTIVEMQ_LOCK;"

# Clear lock table mysql -u activemq -p -e "DELETE FROM activemq.ACTIVEMQ_LOCK;"

# Start designated master first # On master broker: systemctl start activemq

# Wait for lock acquisition tail -f /var/log/activemq/activemq.log | grep -i "acquired lock"

# Start slave brokers # On slave brokers: systemctl start activemq

# Verify only one master curl -u admin:admin http://localhost:8161/api/jolokia/read/org.apache.activemq:type=Broker,brokerName=*/MasterBroker ```

Step 10: Configure Failover URL

```java // Configure clients with failover URL ConnectionFactory factory = new ActiveMQConnectionFactory( "failover:(tcp://master:61616,tcp://slave:61616)?randomize=false&priorityBackup=true&timeout=5000" );

// Client detects master change and reconnects // Failover parameters: // randomize=false: Always try master first // priorityBackup=true: Prefer master // timeout: Max wait time for connection ```

JDBC Lock Settings

Setting	Default	Recommended
lockKeepAlivePeriod	30000ms	5000-10000ms
lockAcquireSleepInterval	10000ms	5000-10000ms
connectTimeout	0 (infinite)	10000ms
socketTimeout	0 (infinite)	60000ms

Verification

```bash # After configuration changes # Restart ActiveMQ systemctl restart activemq

# Check lock acquisition tail -f /var/log/activemq/activemq.log | grep -i "lock"

# Should see: "Acquired lock" and regular "Renewed lock"

# Verify master status curl -u admin:admin http://localhost:8161/api/jolokia/read/org.apache.activemq:type=Broker,brokerName=localhost/MasterBroker

# Should return true for master broker

# Check database lock table mysql -u activemq -p -e "SELECT * FROM activemq.ACTIVEMQ_LOCK;"

# Monitor for lock renewals grep -c "renewed lock" /var/log/activemq/activemq.log ```

Prevention

To prevent ActiveMQ JDBC lock expired issues from recurring, implement these proactive measures:

1. Monitor Lock Status

yaml

groups:
- name: activemq-ha
  rules:
  - alert: ActiveMQJDBCLockExpired
    expr: |
      activemq_jdbc_lock_expired > 0
    for: 1m
    labels:
      severity: critical
    annotations:
      summary: "ActiveMQ JDBC lock expired"

2. Configure Proper Lock Settings

```xml  <persistenceAdapter> <jdbcPersistenceAdapter dataDirectory="${activemq.data}" dataSource="#mysql-ds" lockKeepAlivePeriod="5000" lockAcquireSleepInterval="5000"/> </persistenceAdapter>

<bean id="mysql-ds" class="org.apache.commons.dbcp2.BasicDataSource"> <property name="url" value="jdbc:mysql://mysql-host:3306/activemq"/> <property name="username" value="activemq"/> <property name="password" value="password"/> <property name="maxTotal" value="20"/> <property name="maxIdle" value="10"/> <property name="connectionProperties" value="connectTimeout=10000;socketTimeout=60000"/> </bean> ```

3. Monitor Database Connectivity

```bash # Regular connectivity test cat << 'EOF' > /usr/local/bin/check_activemq_db.sh #!/bin/bash mysql -u activemq -p$ACTIVEMQ_DB_PASS -e "SELECT 1" activemq if [ $? -ne 0 ]; then echo "Database connectivity issue" systemctl restart activemq fi EOF

chmod +x /usr/local/bin/check_activemq_db.sh echo "*/5 * * * * root /usr/local/bin/check_activemq_db.sh" > /etc/cron.d/activemq-db-check ```

Best Practices Checklist

[ ] Monitor lock status with alerts
[ ] Configure proper lock keep-alive
[ ] Monitor database connectivity
[ ] Set appropriate timeouts
[ ] Use connection pooling
[ ] Test failover regularly

[Fix ActiveMQ Master Slave Failover](/articles/fix-activemq-master-slave-failover)
[Fix ActiveMQ Destination Full](/articles/fix-activemq-destination-full)
[Fix MySQL Connection Refused](/articles/fix-mysql-connection-refused)

[Fix Fix Activemq Broker Down Issue in Messaging](fix-activemq-broker-down)
[Fix ActiveMQ Destination Full](fix-activemq-destination-full)
[Fix ActiveMQ Kaha PIndex Corrupted](fix-activemq-kaha-pindex-corrupted)
[Fix ActiveMQ Master Slave Failover](fix-activemq-master-slave-failover)
[Fix ActiveMQ Slow Consumer](fix-activemq-slow-consumer)

Was this guide helpful?

Related search paths

People also search for

If the symptom is close but not identical, these search paths usually surface the right neighboring fixes faster than scrolling the full archive.

ActiveMQ JDBC Lock Expired ActiveMQ JDBC Lock Expired Messaging ActiveMQ JDBC Lock Expired troubleshooting ActiveMQ JDBC Lock Expired fix Resolve ActiveMQ JDBC lock expired errors by configuring lock keepalive, database connection settings, and failover handling Messaging Resolve ActiveMQ JDBC lock expired errors by configuring lock keepalive, database connection settings, and failover handling

Explore Related Topics

Browse Guides from Other Categories

Discover troubleshooting guides from related categories to expand your knowledge.

FAQ

Messaging Troubleshooting FAQs

Common questions about troubleshooting and preventing similar issues

How do I know if this messaging-errors troubleshooting guide applies to my situation?

This guide is designed for messaging-errors issues. If you're experiencing similar symptoms described in the article, follow the step-by-step instructions. Start with the most common causes and work through the diagnostic process.

Is it safe to follow these messaging-errors troubleshooting steps?

Yes, all steps are designed to be safe and non-destructive. We recommend creating backups before making significant changes and testing each step before proceeding to the next.

How long does it typically take to resolve this type of messaging-errors issue?

Most messaging-errors issues can be resolved within 30 minutes to 2 hours, depending on the complexity and root cause. Follow the troubleshooting flow to identify and fix the problem efficiently.

How can I prevent this messaging-errors issue from happening again?

Regular maintenance, monitoring, and following best practices for messaging-errors configuration can help prevent recurrence. Consider implementing automated checks and alerts for early detection.

Written by

FixWikiHub Editorial Team

Our editorial team consists of experienced DevOps engineers, systems administrators, and cloud architects with hands-on experience in production environments across AWS, Azure, GCP, and on-premises infrastructure.

Every guide undergoes technical review for accuracy and is updated when software versions, commands, or best practices change.

Last updated: Apr 3, 2026

About our team

Important Notice

Disclaimer & Safety Guidelines

The troubleshooting steps in this guide are provided for educational and informational purposes. Before applying any changes to production systems:

Test in a staging environment first — Always verify commands and configurations in a non-production environment before deploying to live systems.
Create backups — Ensure you have current backups of databases, configurations, and critical files before making changes.
Understand the impact — Review how each step may affect your specific environment, dependencies, and users.
Consult official documentation — This guide supplements, but does not replace, official vendor documentation and best practices.

FixWikiHub is not responsible for any damages arising from the use of this content. See our Terms of Use for more information.

Resources

Official Documentation & Further Reading

For authoritative information, consult the official documentation for the technologies discussed in this guide. Our troubleshooting content supplements, but does not replace, vendor documentation.

AWS Documentation — Official Amazon Web Services guides and API references
Kubernetes Documentation — Official Kubernetes documentation
Nginx Documentation — Official Nginx web server documentation
Apache Documentation — Official Apache HTTP Server documentation
Docker Documentation — Official Docker container documentation

Fix ActiveMQ JDBC Lock Expired

Introduction

Symptoms

Common Causes

Step-by-Step Fix

Step 1: Check Lock Status

Step 2: Configure Lock Keepalive

Step 3: Configure Database Connection Pool

Step 4: Check Database Connectivity

Step 5: Handle Lock Acquisition Failures

Step 6: Use Lease Database Locker

Step 7: Configure Network Timeout

Step 8: Monitor Lock Health

Step 9: Handle Split-Brain Scenario

Step 10: Configure Failover URL

JDBC Lock Settings

Verification

Prevention

1. Monitor Lock Status

2. Configure Proper Lock Settings

3. Monitor Database Connectivity

Best Practices Checklist

People also search for

Browse Guides from Other Categories

WordPress

SSL

DNS

Messaging Troubleshooting FAQs

FixWikiHub Editorial Team

Disclaimer & Safety Guidelines

Official Documentation & Further Reading

Fix ActiveMQ JDBC Lock Expired

Introduction

Symptoms

Common Causes

Step-by-Step Fix

Step 1: Check Lock Status

Step 2: Configure Lock Keepalive

Step 3: Configure Database Connection Pool

Step 4: Check Database Connectivity

Step 5: Handle Lock Acquisition Failures

Step 6: Use Lease Database Locker

Step 7: Configure Network Timeout

Step 8: Monitor Lock Health

Step 9: Handle Split-Brain Scenario

Step 10: Configure Failover URL

JDBC Lock Settings

Verification

Prevention

1. Monitor Lock Status

2. Configure Proper Lock Settings

3. Monitor Database Connectivity

Best Practices Checklist

Related Issues

Related Articles

People also search for

Share this guide

More Messaging Troubleshooting Guides

Browse Guides from Other Categories

Messaging Troubleshooting FAQs

FixWikiHub Editorial Team

Disclaimer & Safety Guidelines

Official Documentation & Further Reading