activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Remo Gloor (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMQ-4882) LevelDB can get to a corrupt state
Date Wed, 13 Nov 2013 14:45:44 GMT

     [ https://issues.apache.org/jira/browse/AMQ-4882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Remo Gloor updated AMQ-4882:
----------------------------

    Description: 
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.

  was: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.


> 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)

Mime
View raw message