[
https://issues.apache.org/jira/browse/ARTEMIS-761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15556505#comment-15556505
]
ASF subversion and git services commented on ARTEMIS-761:
---------------------------------------------------------
Commit c47a9a5f802888443638c3bbb9aec769a6bf2e1d in activemq-artemis's branch
refs/heads/master from jbertram
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=c47a9a5 ]
ARTEMIS-761 fix possible dup journal record ID
> Caused by: java.lang.IllegalStateException: Cannot find add info 2148856738
> ---------------------------------------------------------------------------
>
> Key: ARTEMIS-761
> URL: https://issues.apache.org/jira/browse/ARTEMIS-761
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Affects Versions: 1.4.0
> Environment: Linux and Windows
> Reporter: Damien Hollis
> Assignee: Justin Bertram
> Fix For: 1.5.0
>
> Attachments: EmbeddedExample.java
>
>
> I added a comment on https://issues.apache.org/jira/browse/ARTEMIS-390 but
> you may not have seen it as it is closed.
> From time to time we get an issue when starting up Artemis (embedded in a web
> application). However, on restarting the server, the problem disappears.
> {noformat}
> Caused by: java.lang.IllegalStateException: Cannot find add info 2148856738
> at
> org.apache.activemq.artemis.core.journal.impl.JournalImpl.appendDeleteRecord(JournalImpl.java:793)
> at
> org.apache.activemq.artemis.core.journal.impl.JournalBase.appendDeleteRecord(JournalBase.java:206)
> at
> org.apache.activemq.artemis.core.journal.impl.JournalImpl.appendDeleteRecord(JournalImpl.java:79)
> at
> org.apache.activemq.artemis.core.persistence.impl.journal.AbstractJournalStorageManager.deleteAddressSetting(AbstractJournalStorageManager.java:826)
> at
> org.apache.activemq.artemis.core.management.impl.ActiveMQServerControlImpl.removeAddressSettings(ActiveMQServerControlImpl.java:1756)
> {noformat}
> We also had a similar problem when we upgraded from Artemis 1.3.0 to 1.4.0
> but in that case our only option was to delete the data directories - luckily
> we were just testing and this was not a big issue for us but it would be in
> production.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
