[
https://issues.apache.org/jira/browse/AMQ-4882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13821452#comment-13821452
]
Shipper commented on AMQ-4882:
------------------------------
I’m experiencing the same error using the latest 5.10-SNAPSHOT build and
LevelDB Replicated datastore. My testing used non-transaction clients. Test
scenario procedure was to stop and restart 5.10 repeatedly, forcing recovery to
other Replicated instances. Linux RHEL 5, Java 1.7
2013-11-12 20:00:53,552 | INFO | Promoted to master |
org.apache.activemq.leveldb.replicated.MasterElector | main-EventThread
2013-11-12 20:00:53,568 | INFO | Using the pure java LevelDB implementation. |
org.apache.activemq.leveldb.LevelDBClient | ActiveMQ
BrokerService[replicating-broker] Task-3
2013-11-12 20:00:55,564 | INFO | Master started: tcp://tmi00091:55201 |
org.apache.activemq.leveldb.replicated.MasterElector | ActiveMQ
BrokerService[replicating-broker] Task-4
r.java:258)
at
org.apache.activemq.broker.region.cursors.AbstractStoreCursor.reset(AbstractStoreCursor.java:108)
at
org.apache.activemq.broker.region.cursors.StoreQueueCursor.reset(StoreQueueCursor.java:157)
at
org.apache.activemq.broker.region.Queue.doPageInForDispatch(Queue.java:1875)
at
org.apache.activemq.broker.region.Queue.pageInMessages(Queue.java:2086)
at org.apache.activemq.broker.region.Queue.doBrowse(Queue.java:1096)
at
org.apache.activemq.broker.region.Queue.expireMessages(Queue.java:905)
at org.apache.activemq.broker.region.Queue.access$100(Queue.java:79)
at org.apache.activemq.broker.region.Queue$2.run(Queue.java:120)
at
org.apache.activemq.thread.SchedulerTimerTask.run(SchedulerTimerTask.java:33)
at java.util.TimerThread.mainLoop(Timer.java:555)
at java.util.TimerThread.run(Timer.java:505)
Caused by: java.lang.NullPointerException
at
org.apache.activemq.leveldb.LevelDBClient$$anonfun$queueCursor$1.apply(LevelDBClient.scala:1243)
at
org.apache.activemq.leveldb.LevelDBClient$$anonfun$queueCursor$1.apply(LevelDBClient.scala:1239)
at
org.apache.activemq.leveldb.LevelDBClient$$anonfun$collectionCursor$1$$anonfun$apply$mcV$sp$12.apply(LevelDBClient.scala:1317)
at
org.apache.activemq.leveldb.LevelDBClient$$anonfun$collectionCursor$1$$anonfun$apply$mcV$sp$12.apply(LevelDBClient.scala:1316)
at
org.apache.activemq.leveldb.LevelDBClient$RichDB.check$4(LevelDBClient.scala:326)
at
org.apache.activemq.leveldb.LevelDBClient$RichDB.cursorRange(LevelDBClient.scala:328)
at
org.apache.activemq.leveldb.LevelDBClient$$anonfun$collectionCursor$1.apply$mcV$sp(LevelDBClient.scala:1316)
at
org.apache.activemq.leveldb.LevelDBClient$$anonfun$collectionCursor$1.apply(LevelDBClient.scala:1316)
at
org.apache.activemq.leveldb.LevelDBClient$$anonfun$collectionCursor$1.apply(LevelDBClient.scala:1316)
at
org.apache.activemq.leveldb.LevelDBClient.usingIndex(LevelDBClient.scala:1013)
at
org.apache.activemq.leveldb.LevelDBClient$$anonfun$might_fail_using_index$1.apply(LevelDBClient.scala:1019)
at
org.apache.activemq.leveldb.LevelDBClient.might_fail(LevelDBClient.scala:551)
... 18 more
2013-11-12 20:00:50,252 | INFO | Apache ActiveMQ 5.10-SNAPSHOT
(replicating-broker, ID:tmi00092-40602-1384286419875-0:1) is shutting down |
org.apache.activemq.broker.BrokerService | IOExceptionHandler: stopping
BrokerService[replicating-broker]
> LevelDB can get to a corrupt state
> ----------------------------------
>
> Key: AMQ-4882
> URL: https://issues.apache.org/jira/browse/AMQ-4882
> Project: ActiveMQ
> Issue Type: Bug
> Components: activemq-leveldb-store
> Affects Versions: 5.9.0
> Reporter: Remo Gloor
> Priority: Critical
> Attachments: TestClient.zip, activemq.log
>
>
> A consumer/producer with failover transport is connected to AMQ and processes
> messages in XA Transactions. When AMQ is restarted is can happen that LevelDB
> gets to a corrupt state so that AMQ can not be started anymore without
> deletind the database.
> Reproduction:
> - Configure AMQ with LevelDB
> - Run the attached TestClient
> - Restart AMQ several times. At some time it won't start anymore and produced
> the exception in the attached log file.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
