activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mlange <>
Subject ActiveMQ ReplicatedLevelDB corruption
Date Fri, 23 Sep 2016 11:39:33 GMT
Recently I installed Apache ActiveMQ in a few different ways. One of those is
using ReplicatedLevelDB for a master/slave/slave setup. 

Yesterday I did a bit of loadtesting: sending 100.000 messages with 100
threads producing the messages (used jmeter for that) (so each thread
produced 1000 messages); I had another process moving the messages from one
broker to another and back again (the queues had the same names across each
broker, so that was easy moving) and then went about processing the messages
which caused the messages to flow across various queues.

All seemed fine, everything looked okay... until I stopped the active
broker. (this is hours after the last message was consumed and procsesed):

Then I notice a few bouncing brokers, one comes up but crashes on an
EOFException; a bit later the other broker does the same. 

In the log I see many messages like this:

2016-09-23 13:38:52,950 | WARN  | No reader available for position: 0,
| org.apache.activemq.leveldb.RecordLog | Thread-1039

Then I see messages like this:
2016-09-23 13:38:46,324 | WARN  | Invalid log position: 11409726550 |
org.apache.activemq.leveldb.LevelDBClient | ActiveMQ BrokerService[broker1]

After that, the broker starts and logs a few messages like this:
2016-09-23 13:40:49,041 | WARN  | Invalid log position: 0 |
org.apache.activemq.leveldb.LevelDBClient | Thread-1040

and then we get exception:
2016-09-23 13:41:09,748 | INFO  | Stopping BrokerService[broker1] due to
exception, File
'/data/activemq/broker1-db/000000030702cf12.log' offset: 110647192 |
org.apache.activemq.util.DefaultIOExceptionHandler | LevelDB IOException
handler. File '/data/activemq/broker1-db/000000030702cf12.log'
offset: 110647192

This is a rince and repeat situation; both living brokers are now
alternating this sequence.

It seems like the load I generated caused corruption on the database; but
this should not be possible... What information can I provide to see how
this situation can be avoided?

View this message in context:
Sent from the ActiveMQ - User mailing list archive at

View raw message