You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Arthur Naseef (JIRA)" <ji...@apache.org> on 2014/01/10 04:04:55 UTC

[jira] [Commented] (AMQ-4882) LevelDB can get to a corrupt state when using XA transactions

    [ https://issues.apache.org/jira/browse/AMQ-4882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13867458#comment-13867458 ] 

Arthur Naseef commented on AMQ-4882:
------------------------------------

I attached a small test program that attempts to reproduce the problem.  With this program, I failed to reproduce the problem.

Can you give this a try and let me know what you find?  If it does not reproduce the problem for you, please provide more details of the environment and clients.  Such as the numbers of producers and consumers, destinations used, and flow of messages.

> LevelDB can get to a corrupt state when using XA transactions
> -------------------------------------------------------------
>
>                 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: AMQ4882Test.zip, 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.5#6160)