[jira] [Commented] (ARTEMIS-355) Duplex bridges
[ https://issues.apache.org/jira/browse/ARTEMIS-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17014251#comment-17014251 ] masc commented on ARTEMIS-355: -- federation looks good functionally but presumably still requires each broker to be actively reachable via socket connection, while using duplex bridges does not. > Duplex bridges > -- > > Key: ARTEMIS-355 > URL: https://issues.apache.org/jira/browse/ARTEMIS-355 > Project: ActiveMQ Artemis > Issue Type: New Feature > Components: Broker >Affects Versions: 1.2.0 >Reporter: Mike Hearn >Priority: Major > Fix For: unscheduled > > > I can't find any way to make an embedded artemis A connect to an embedded > artemis B such that B can send messages to A without connectivity at the TCP > level, e.g. due to firewall traversal. It'd be convenient if there was no > need for me to implement firewall punching myself. Apparently ActiveMQ can do > this using some sort of "duplex" attribute, but it's not in Artemis. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (AMQ-6831) Broker fails to start complaining about missing/corrupt journal files
[
https://issues.apache.org/jira/browse/AMQ-6831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16984566#comment-16984566
]
masc commented on AMQ-6831:
---
good call, no we don't set this and I double checked that
`CallerDataFileAppender` is actually not used / instantiated in our build.
still can't believe seeing this several times in a row on orderly restart with
5.15.11 and then not at all with 5.15.10 could be coincidence.
I marked this TODO for more in-depth tests / isolation but it could take a
while until I come up with sth.
> Broker fails to start complaining about missing/corrupt journal files
> -
>
> Key: AMQ-6831
> URL: https://issues.apache.org/jira/browse/AMQ-6831
> Project: ActiveMQ
> Issue Type: Bug
>Affects Versions: 5.15.1
>Reporter: masc
>Assignee: Gary Tully
>Priority: Critical
> Fix For: 5.16.0, 5.15.2
>
> Attachments: kahadb.zip
>
>
> {code}
> 2017-10-09 12:29:36.802 ERROR 4197 --- [pool-3-thread-1]
> org.deku.leoz.node.Application : java.io.IOException: Detected
> missing/corrupt journal files referenced by:[0:ActiveMQ.DLQ] 3 messages
> affected.
> java.lang.Error: java.io.IOException: Detected missing/corrupt journal files
> referenced by:[0:ActiveMQ.DLQ] 3 messages affected.
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1148)
> ~[na:1.8.0_131]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> ~[na:1.8.0_131]
> at java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_131]
> Caused by: java.io.IOException: Detected missing/corrupt journal files
> referenced by:[0:ActiveMQ.DLQ] 3 messages affected.
> at
> org.apache.activemq.store.kahadb.MessageDatabase.recoverIndex(MessageDatabase.java:965)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.MessageDatabase$5.execute(MessageDatabase.java:717)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.disk.page.Transaction.execute(Transaction.java:779)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.MessageDatabase.recover(MessageDatabase.java:714)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.MessageDatabase.open(MessageDatabase.java:473)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:493)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.MessageDatabase.doStart(MessageDatabase.java:297)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.KahaDBStore.doStart(KahaDBStore.java:219)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:55)
> ~[activemq-client-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.KahaDBPersistenceAdapter.doStart(KahaDBPersistenceAdapter.java:232)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> {code}
> Downgrading to 5.15.0 resolves the problem.
> This is an embedded broker setup, using
> {code:none}
> val pa = brokerService.persistenceAdapter as KahaDBPersistenceAdapter
> pa.isCheckForCorruptJournalFiles = true
> pa.isIgnoreMissingJournalfiles = false
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (AMQ-6831) Broker fails to start complaining about missing/corrupt journal files
[
https://issues.apache.org/jira/browse/AMQ-6831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16984496#comment-16984496
]
masc commented on AMQ-6831:
---
[~robbie] depends how you look at it. functionally and referring to description
and stack trace this is totally a regression.
if you require separate jira issues in order to group your commits, that's up
to you.
you're now aware of the issue, feel free to spawn as many issues as you prefer.
> Broker fails to start complaining about missing/corrupt journal files
> -
>
> Key: AMQ-6831
> URL: https://issues.apache.org/jira/browse/AMQ-6831
> Project: ActiveMQ
> Issue Type: Bug
>Affects Versions: 5.15.1
>Reporter: masc
>Assignee: Gary Tully
>Priority: Critical
> Fix For: 5.16.0, 5.15.2
>
> Attachments: kahadb.zip
>
>
> {code}
> 2017-10-09 12:29:36.802 ERROR 4197 --- [pool-3-thread-1]
> org.deku.leoz.node.Application : java.io.IOException: Detected
> missing/corrupt journal files referenced by:[0:ActiveMQ.DLQ] 3 messages
> affected.
> java.lang.Error: java.io.IOException: Detected missing/corrupt journal files
> referenced by:[0:ActiveMQ.DLQ] 3 messages affected.
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1148)
> ~[na:1.8.0_131]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> ~[na:1.8.0_131]
> at java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_131]
> Caused by: java.io.IOException: Detected missing/corrupt journal files
> referenced by:[0:ActiveMQ.DLQ] 3 messages affected.
> at
> org.apache.activemq.store.kahadb.MessageDatabase.recoverIndex(MessageDatabase.java:965)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.MessageDatabase$5.execute(MessageDatabase.java:717)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.disk.page.Transaction.execute(Transaction.java:779)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.MessageDatabase.recover(MessageDatabase.java:714)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.MessageDatabase.open(MessageDatabase.java:473)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:493)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.MessageDatabase.doStart(MessageDatabase.java:297)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.KahaDBStore.doStart(KahaDBStore.java:219)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:55)
> ~[activemq-client-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.KahaDBPersistenceAdapter.doStart(KahaDBPersistenceAdapter.java:232)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> {code}
> Downgrading to 5.15.0 resolves the problem.
> This is an embedded broker setup, using
> {code:none}
> val pa = brokerService.persistenceAdapter as KahaDBPersistenceAdapter
> pa.isCheckForCorruptJournalFiles = true
> pa.isIgnoreMissingJournalfiles = false
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (AMQ-6831) Broker fails to start complaining about missing/corrupt journal files
[
https://issues.apache.org/jira/browse/AMQ-6831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16984409#comment-16984409
]
masc edited comment on AMQ-6831 at 11/28/19 1:39 PM:
-
`CallerBufferingDataFileAppender` of kahadb was actually touched in 5.15.11.
Im quite positive yes, I could replicate this in productive environment 100% on
half a dozen restarts while this issue was never seen before (since 5.15.1) and
downgrading resolves it instantly.
was (Author: masc3d):
`CallerBufferingDataFileAppender` of kahadb was actually touched in 5.15.11.
Im quite positive yes, I could replicate this in productive environment 100% on
half a dozen restarts while this issue was never seen before and downgrading
resolves it instantly.
> Broker fails to start complaining about missing/corrupt journal files
> -
>
> Key: AMQ-6831
> URL: https://issues.apache.org/jira/browse/AMQ-6831
> Project: ActiveMQ
> Issue Type: Bug
>Affects Versions: 5.15.1, 5.15.11
>Reporter: masc
>Assignee: Gary Tully
>Priority: Critical
> Fix For: 5.16.0, 5.15.2
>
> Attachments: kahadb.zip
>
>
> {code}
> 2017-10-09 12:29:36.802 ERROR 4197 --- [pool-3-thread-1]
> org.deku.leoz.node.Application : java.io.IOException: Detected
> missing/corrupt journal files referenced by:[0:ActiveMQ.DLQ] 3 messages
> affected.
> java.lang.Error: java.io.IOException: Detected missing/corrupt journal files
> referenced by:[0:ActiveMQ.DLQ] 3 messages affected.
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1148)
> ~[na:1.8.0_131]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> ~[na:1.8.0_131]
> at java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_131]
> Caused by: java.io.IOException: Detected missing/corrupt journal files
> referenced by:[0:ActiveMQ.DLQ] 3 messages affected.
> at
> org.apache.activemq.store.kahadb.MessageDatabase.recoverIndex(MessageDatabase.java:965)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.MessageDatabase$5.execute(MessageDatabase.java:717)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.disk.page.Transaction.execute(Transaction.java:779)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.MessageDatabase.recover(MessageDatabase.java:714)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.MessageDatabase.open(MessageDatabase.java:473)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:493)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.MessageDatabase.doStart(MessageDatabase.java:297)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.KahaDBStore.doStart(KahaDBStore.java:219)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:55)
> ~[activemq-client-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.KahaDBPersistenceAdapter.doStart(KahaDBPersistenceAdapter.java:232)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> {code}
> Downgrading to 5.15.0 resolves the problem.
> This is an embedded broker setup, using
> {code:none}
> val pa = brokerService.persistenceAdapter as KahaDBPersistenceAdapter
> pa.isCheckForCorruptJournalFiles = true
> pa.isIgnoreMissingJournalfiles = false
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (AMQ-6831) Broker fails to start complaining about missing/corrupt journal files
[
https://issues.apache.org/jira/browse/AMQ-6831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16984409#comment-16984409
]
masc commented on AMQ-6831:
---
`CallerBufferingDataFileAppender` of kahadb was actually touched in 5.15.11.
Im quite positive yes, I could replicate this in productive environment 100% on
half a dozen restarts while this issue was never seen before and downgrading
resolves it instantly.
> Broker fails to start complaining about missing/corrupt journal files
> -
>
> Key: AMQ-6831
> URL: https://issues.apache.org/jira/browse/AMQ-6831
> Project: ActiveMQ
> Issue Type: Bug
>Affects Versions: 5.15.1, 5.15.11
>Reporter: masc
>Assignee: Gary Tully
>Priority: Critical
> Fix For: 5.16.0, 5.15.2
>
> Attachments: kahadb.zip
>
>
> {code}
> 2017-10-09 12:29:36.802 ERROR 4197 --- [pool-3-thread-1]
> org.deku.leoz.node.Application : java.io.IOException: Detected
> missing/corrupt journal files referenced by:[0:ActiveMQ.DLQ] 3 messages
> affected.
> java.lang.Error: java.io.IOException: Detected missing/corrupt journal files
> referenced by:[0:ActiveMQ.DLQ] 3 messages affected.
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1148)
> ~[na:1.8.0_131]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> ~[na:1.8.0_131]
> at java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_131]
> Caused by: java.io.IOException: Detected missing/corrupt journal files
> referenced by:[0:ActiveMQ.DLQ] 3 messages affected.
> at
> org.apache.activemq.store.kahadb.MessageDatabase.recoverIndex(MessageDatabase.java:965)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.MessageDatabase$5.execute(MessageDatabase.java:717)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.disk.page.Transaction.execute(Transaction.java:779)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.MessageDatabase.recover(MessageDatabase.java:714)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.MessageDatabase.open(MessageDatabase.java:473)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:493)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.MessageDatabase.doStart(MessageDatabase.java:297)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.KahaDBStore.doStart(KahaDBStore.java:219)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:55)
> ~[activemq-client-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.KahaDBPersistenceAdapter.doStart(KahaDBPersistenceAdapter.java:232)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> {code}
> Downgrading to 5.15.0 resolves the problem.
> This is an embedded broker setup, using
> {code:none}
> val pa = brokerService.persistenceAdapter as KahaDBPersistenceAdapter
> pa.isCheckForCorruptJournalFiles = true
> pa.isIgnoreMissingJournalfiles = false
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (AMQ-6831) Broker fails to start complaining about missing/corrupt journal files
[
https://issues.apache.org/jira/browse/AMQ-6831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
masc updated AMQ-6831:
--
Summary: Broker fails to start complaining about missing/corrupt journal
files (was: Broker fails to start complaining about missing/corrupt journal
files after upgrading to 5.15.1)
> Broker fails to start complaining about missing/corrupt journal files
> -
>
> Key: AMQ-6831
> URL: https://issues.apache.org/jira/browse/AMQ-6831
> Project: ActiveMQ
> Issue Type: Bug
>Affects Versions: 5.15.1, 5.15.11
>Reporter: masc
>Assignee: Gary Tully
>Priority: Critical
> Fix For: 5.16.0, 5.15.2
>
> Attachments: kahadb.zip
>
>
> {code}
> 2017-10-09 12:29:36.802 ERROR 4197 --- [pool-3-thread-1]
> org.deku.leoz.node.Application : java.io.IOException: Detected
> missing/corrupt journal files referenced by:[0:ActiveMQ.DLQ] 3 messages
> affected.
> java.lang.Error: java.io.IOException: Detected missing/corrupt journal files
> referenced by:[0:ActiveMQ.DLQ] 3 messages affected.
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1148)
> ~[na:1.8.0_131]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> ~[na:1.8.0_131]
> at java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_131]
> Caused by: java.io.IOException: Detected missing/corrupt journal files
> referenced by:[0:ActiveMQ.DLQ] 3 messages affected.
> at
> org.apache.activemq.store.kahadb.MessageDatabase.recoverIndex(MessageDatabase.java:965)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.MessageDatabase$5.execute(MessageDatabase.java:717)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.disk.page.Transaction.execute(Transaction.java:779)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.MessageDatabase.recover(MessageDatabase.java:714)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.MessageDatabase.open(MessageDatabase.java:473)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:493)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.MessageDatabase.doStart(MessageDatabase.java:297)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.KahaDBStore.doStart(KahaDBStore.java:219)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:55)
> ~[activemq-client-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.KahaDBPersistenceAdapter.doStart(KahaDBPersistenceAdapter.java:232)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> {code}
> Downgrading to 5.15.0 resolves the problem.
> This is an embedded broker setup, using
> {code:none}
> val pa = brokerService.persistenceAdapter as KahaDBPersistenceAdapter
> pa.isCheckForCorruptJournalFiles = true
> pa.isIgnoreMissingJournalfiles = false
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (AMQ-6831) Broker fails to start complaining about missing/corrupt journal files after upgrading to 5.15.1
[
https://issues.apache.org/jira/browse/AMQ-6831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
masc updated AMQ-6831:
--
Affects Version/s: 5.15.11
> Broker fails to start complaining about missing/corrupt journal files after
> upgrading to 5.15.1
> ---
>
> Key: AMQ-6831
> URL: https://issues.apache.org/jira/browse/AMQ-6831
> Project: ActiveMQ
> Issue Type: Bug
>Affects Versions: 5.15.1, 5.15.11
>Reporter: masc
>Assignee: Gary Tully
>Priority: Critical
> Fix For: 5.16.0, 5.15.2
>
> Attachments: kahadb.zip
>
>
> {code}
> 2017-10-09 12:29:36.802 ERROR 4197 --- [pool-3-thread-1]
> org.deku.leoz.node.Application : java.io.IOException: Detected
> missing/corrupt journal files referenced by:[0:ActiveMQ.DLQ] 3 messages
> affected.
> java.lang.Error: java.io.IOException: Detected missing/corrupt journal files
> referenced by:[0:ActiveMQ.DLQ] 3 messages affected.
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1148)
> ~[na:1.8.0_131]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> ~[na:1.8.0_131]
> at java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_131]
> Caused by: java.io.IOException: Detected missing/corrupt journal files
> referenced by:[0:ActiveMQ.DLQ] 3 messages affected.
> at
> org.apache.activemq.store.kahadb.MessageDatabase.recoverIndex(MessageDatabase.java:965)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.MessageDatabase$5.execute(MessageDatabase.java:717)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.disk.page.Transaction.execute(Transaction.java:779)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.MessageDatabase.recover(MessageDatabase.java:714)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.MessageDatabase.open(MessageDatabase.java:473)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:493)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.MessageDatabase.doStart(MessageDatabase.java:297)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.KahaDBStore.doStart(KahaDBStore.java:219)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:55)
> ~[activemq-client-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.KahaDBPersistenceAdapter.doStart(KahaDBPersistenceAdapter.java:232)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> {code}
> Downgrading to 5.15.0 resolves the problem.
> This is an embedded broker setup, using
> {code:none}
> val pa = brokerService.persistenceAdapter as KahaDBPersistenceAdapter
> pa.isCheckForCorruptJournalFiles = true
> pa.isIgnoreMissingJournalfiles = false
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Reopened] (AMQ-6831) Broker fails to start complaining about missing/corrupt journal files after upgrading to 5.15.1
[
https://issues.apache.org/jira/browse/AMQ-6831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
masc reopened AMQ-6831:
---
regression 5.15.10 -> 5.15.11
> Broker fails to start complaining about missing/corrupt journal files after
> upgrading to 5.15.1
> ---
>
> Key: AMQ-6831
> URL: https://issues.apache.org/jira/browse/AMQ-6831
> Project: ActiveMQ
> Issue Type: Bug
>Affects Versions: 5.15.1
>Reporter: masc
>Assignee: Gary Tully
>Priority: Critical
> Fix For: 5.16.0, 5.15.2
>
> Attachments: kahadb.zip
>
>
> {code}
> 2017-10-09 12:29:36.802 ERROR 4197 --- [pool-3-thread-1]
> org.deku.leoz.node.Application : java.io.IOException: Detected
> missing/corrupt journal files referenced by:[0:ActiveMQ.DLQ] 3 messages
> affected.
> java.lang.Error: java.io.IOException: Detected missing/corrupt journal files
> referenced by:[0:ActiveMQ.DLQ] 3 messages affected.
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1148)
> ~[na:1.8.0_131]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> ~[na:1.8.0_131]
> at java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_131]
> Caused by: java.io.IOException: Detected missing/corrupt journal files
> referenced by:[0:ActiveMQ.DLQ] 3 messages affected.
> at
> org.apache.activemq.store.kahadb.MessageDatabase.recoverIndex(MessageDatabase.java:965)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.MessageDatabase$5.execute(MessageDatabase.java:717)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.disk.page.Transaction.execute(Transaction.java:779)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.MessageDatabase.recover(MessageDatabase.java:714)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.MessageDatabase.open(MessageDatabase.java:473)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:493)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.MessageDatabase.doStart(MessageDatabase.java:297)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.KahaDBStore.doStart(KahaDBStore.java:219)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:55)
> ~[activemq-client-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.KahaDBPersistenceAdapter.doStart(KahaDBPersistenceAdapter.java:232)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> {code}
> Downgrading to 5.15.0 resolves the problem.
> This is an embedded broker setup, using
> {code:none}
> val pa = brokerService.persistenceAdapter as KahaDBPersistenceAdapter
> pa.isCheckForCorruptJournalFiles = true
> pa.isIgnoreMissingJournalfiles = false
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (AMQ-6831) Broker fails to start complaining about missing/corrupt journal files after upgrading to 5.15.1
[
https://issues.apache.org/jira/browse/AMQ-6831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16984370#comment-16984370
]
masc commented on AMQ-6831:
---
This issue is apparently regressing in 5.15.11.
After upgrading from 5.15.10 to 5.15.11 broker complains about missing /
corrupt journal files on every restart.
Downgrading to 5.15.10 resolves the issue.
> Broker fails to start complaining about missing/corrupt journal files after
> upgrading to 5.15.1
> ---
>
> Key: AMQ-6831
> URL: https://issues.apache.org/jira/browse/AMQ-6831
> Project: ActiveMQ
> Issue Type: Bug
>Affects Versions: 5.15.1
>Reporter: masc
>Assignee: Gary Tully
>Priority: Critical
> Fix For: 5.16.0, 5.15.2
>
> Attachments: kahadb.zip
>
>
> {code}
> 2017-10-09 12:29:36.802 ERROR 4197 --- [pool-3-thread-1]
> org.deku.leoz.node.Application : java.io.IOException: Detected
> missing/corrupt journal files referenced by:[0:ActiveMQ.DLQ] 3 messages
> affected.
> java.lang.Error: java.io.IOException: Detected missing/corrupt journal files
> referenced by:[0:ActiveMQ.DLQ] 3 messages affected.
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1148)
> ~[na:1.8.0_131]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> ~[na:1.8.0_131]
> at java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_131]
> Caused by: java.io.IOException: Detected missing/corrupt journal files
> referenced by:[0:ActiveMQ.DLQ] 3 messages affected.
> at
> org.apache.activemq.store.kahadb.MessageDatabase.recoverIndex(MessageDatabase.java:965)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.MessageDatabase$5.execute(MessageDatabase.java:717)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.disk.page.Transaction.execute(Transaction.java:779)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.MessageDatabase.recover(MessageDatabase.java:714)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.MessageDatabase.open(MessageDatabase.java:473)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:493)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.MessageDatabase.doStart(MessageDatabase.java:297)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.KahaDBStore.doStart(KahaDBStore.java:219)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:55)
> ~[activemq-client-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.KahaDBPersistenceAdapter.doStart(KahaDBPersistenceAdapter.java:232)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> {code}
> Downgrading to 5.15.0 resolves the problem.
> This is an embedded broker setup, using
> {code:none}
> val pa = brokerService.persistenceAdapter as KahaDBPersistenceAdapter
> pa.isCheckForCorruptJournalFiles = true
> pa.isIgnoreMissingJournalfiles = false
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ARTEMIS-838) Support full duplex cluster-connections
[ https://issues.apache.org/jira/browse/ARTEMIS-838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16834239#comment-16834239 ] masc commented on ARTEMIS-838: -- duplicate of https://issues.apache.org/jira/browse/ARTEMIS-355? > Support full duplex cluster-connections > --- > > Key: ARTEMIS-838 > URL: https://issues.apache.org/jira/browse/ARTEMIS-838 > Project: ActiveMQ Artemis > Issue Type: New Feature > Components: Broker >Reporter: Matt Pavlovich >Priority: Major > > Artemis should support a feature where cluster-connections between brokers > can handle producer and consumer side actions with a single outbound > connection. > There are two core use cases for this feature: > 1. Secure networks where brokers from one-side are able to create outbound > connections, but the remote broker is not allowed to make inbound connections. > 2. Retail store / kiosk use case where a new endpoint comes online to connect > to a centralized broker to avoid any server-side configuration to support low > to moderate 2-way traffic across a single connection -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMQ-6831) Broker fails to start complaining about missing/corrupt journal files after upgrading to 5.15.1
[
https://issues.apache.org/jira/browse/AMQ-6831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16197690#comment-16197690
]
masc commented on AMQ-6831:
---
yes sorry, checked again and replaced the archive with the full kahadb folder
> Broker fails to start complaining about missing/corrupt journal files after
> upgrading to 5.15.1
> ---
>
> Key: AMQ-6831
> URL: https://issues.apache.org/jira/browse/AMQ-6831
> Project: ActiveMQ
> Issue Type: Bug
>Affects Versions: 5.15.1
>Reporter: masc
> Attachments: kahadb.zip
>
>
> {code}
> 2017-10-09 12:29:36.802 ERROR 4197 --- [pool-3-thread-1]
> org.deku.leoz.node.Application : java.io.IOException: Detected
> missing/corrupt journal files referenced by:[0:ActiveMQ.DLQ] 3 messages
> affected.
> java.lang.Error: java.io.IOException: Detected missing/corrupt journal files
> referenced by:[0:ActiveMQ.DLQ] 3 messages affected.
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1148)
> ~[na:1.8.0_131]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> ~[na:1.8.0_131]
> at java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_131]
> Caused by: java.io.IOException: Detected missing/corrupt journal files
> referenced by:[0:ActiveMQ.DLQ] 3 messages affected.
> at
> org.apache.activemq.store.kahadb.MessageDatabase.recoverIndex(MessageDatabase.java:965)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.MessageDatabase$5.execute(MessageDatabase.java:717)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.disk.page.Transaction.execute(Transaction.java:779)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.MessageDatabase.recover(MessageDatabase.java:714)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.MessageDatabase.open(MessageDatabase.java:473)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:493)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.MessageDatabase.doStart(MessageDatabase.java:297)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.KahaDBStore.doStart(KahaDBStore.java:219)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:55)
> ~[activemq-client-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.KahaDBPersistenceAdapter.doStart(KahaDBPersistenceAdapter.java:232)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> {code}
> Downgrading to 5.15.0 resolves the problem.
> This is an embedded broker setup, using
> {code:none}
> val pa = brokerService.persistenceAdapter as KahaDBPersistenceAdapter
> pa.isCheckForCorruptJournalFiles = true
> pa.isIgnoreMissingJournalfiles = false
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMQ-6831) Broker fails to start complaining about missing/corrupt journal files after upgrading to 5.15.1
[
https://issues.apache.org/jira/browse/AMQ-6831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
masc updated AMQ-6831:
--
Attachment: kahadb.zip
> Broker fails to start complaining about missing/corrupt journal files after
> upgrading to 5.15.1
> ---
>
> Key: AMQ-6831
> URL: https://issues.apache.org/jira/browse/AMQ-6831
> Project: ActiveMQ
> Issue Type: Bug
>Affects Versions: 5.15.1
>Reporter: masc
> Attachments: kahadb.zip
>
>
> {code}
> 2017-10-09 12:29:36.802 ERROR 4197 --- [pool-3-thread-1]
> org.deku.leoz.node.Application : java.io.IOException: Detected
> missing/corrupt journal files referenced by:[0:ActiveMQ.DLQ] 3 messages
> affected.
> java.lang.Error: java.io.IOException: Detected missing/corrupt journal files
> referenced by:[0:ActiveMQ.DLQ] 3 messages affected.
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1148)
> ~[na:1.8.0_131]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> ~[na:1.8.0_131]
> at java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_131]
> Caused by: java.io.IOException: Detected missing/corrupt journal files
> referenced by:[0:ActiveMQ.DLQ] 3 messages affected.
> at
> org.apache.activemq.store.kahadb.MessageDatabase.recoverIndex(MessageDatabase.java:965)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.MessageDatabase$5.execute(MessageDatabase.java:717)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.disk.page.Transaction.execute(Transaction.java:779)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.MessageDatabase.recover(MessageDatabase.java:714)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.MessageDatabase.open(MessageDatabase.java:473)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:493)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.MessageDatabase.doStart(MessageDatabase.java:297)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.KahaDBStore.doStart(KahaDBStore.java:219)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:55)
> ~[activemq-client-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.KahaDBPersistenceAdapter.doStart(KahaDBPersistenceAdapter.java:232)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> {code}
> Downgrading to 5.15.0 resolves the problem.
> This is an embedded broker setup, using
> {code:none}
> val pa = brokerService.persistenceAdapter as KahaDBPersistenceAdapter
> pa.isCheckForCorruptJournalFiles = true
> pa.isIgnoreMissingJournalfiles = false
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMQ-6831) Broker fails to start complaining about missing/corrupt journal files after upgrading to 5.15.1
[
https://issues.apache.org/jira/browse/AMQ-6831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
masc updated AMQ-6831:
--
Attachment: (was: kahadb.zip)
> Broker fails to start complaining about missing/corrupt journal files after
> upgrading to 5.15.1
> ---
>
> Key: AMQ-6831
> URL: https://issues.apache.org/jira/browse/AMQ-6831
> Project: ActiveMQ
> Issue Type: Bug
>Affects Versions: 5.15.1
>Reporter: masc
>
> {code}
> 2017-10-09 12:29:36.802 ERROR 4197 --- [pool-3-thread-1]
> org.deku.leoz.node.Application : java.io.IOException: Detected
> missing/corrupt journal files referenced by:[0:ActiveMQ.DLQ] 3 messages
> affected.
> java.lang.Error: java.io.IOException: Detected missing/corrupt journal files
> referenced by:[0:ActiveMQ.DLQ] 3 messages affected.
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1148)
> ~[na:1.8.0_131]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> ~[na:1.8.0_131]
> at java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_131]
> Caused by: java.io.IOException: Detected missing/corrupt journal files
> referenced by:[0:ActiveMQ.DLQ] 3 messages affected.
> at
> org.apache.activemq.store.kahadb.MessageDatabase.recoverIndex(MessageDatabase.java:965)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.MessageDatabase$5.execute(MessageDatabase.java:717)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.disk.page.Transaction.execute(Transaction.java:779)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.MessageDatabase.recover(MessageDatabase.java:714)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.MessageDatabase.open(MessageDatabase.java:473)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:493)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.MessageDatabase.doStart(MessageDatabase.java:297)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.KahaDBStore.doStart(KahaDBStore.java:219)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:55)
> ~[activemq-client-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.KahaDBPersistenceAdapter.doStart(KahaDBPersistenceAdapter.java:232)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> {code}
> Downgrading to 5.15.0 resolves the problem.
> This is an embedded broker setup, using
> {code:none}
> val pa = brokerService.persistenceAdapter as KahaDBPersistenceAdapter
> pa.isCheckForCorruptJournalFiles = true
> pa.isIgnoreMissingJournalfiles = false
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (AMQ-6831) Broker fails to start complaining about missing/corrupt journal files after upgrading to 5.15.1
[
https://issues.apache.org/jira/browse/AMQ-6831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16197268#comment-16197268
]
masc edited comment on AMQ-6831 at 10/9/17 4:45 PM:
yes, that would be possible, as it's my local dev db, it shouldn't contain
anything sensitive.
I also found that this issue is related to the preallocation kahadb settings:
{code}
pa.preallocationScope =
Journal.PreallocationScope.ENTIRE_JOURNAL_ASYNC.name
pa.preallocationStrategy = Journal.PreallocationStrategy.ZEROS.name
{code}
which I enabled for performance reasons.
Disabling preallocation will yield both
{code}
2017-10-09 18:34:57.512 WARN 10617 --- [pool-3-thread-1]
o.a.a.store.kahadb.MessageDatabase : Cannot recover message audit
java.io.IOException: Invalid location size: 1:28, size: 0
at
org.apache.activemq.store.kahadb.disk.journal.DataFileAccessor.readRecord(DataFileAccessor.java:88)
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.disk.journal.Journal.read(Journal.java:936)
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:1151)
[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.MessageDatabase.recoverProducerAudit(MessageDatabase.java:784)
[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.MessageDatabase.recover(MessageDatabase.java:674)
[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.MessageDatabase.open(MessageDatabase.java:473)
[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:493)
[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.MessageDatabase.doStart(MessageDatabase.java:297)
[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.KahaDBStore.doStart(KahaDBStore.java:219)
[activemq-kahadb-store-5.15.1.jar:5.15.1]
{code}
and subsequently
{code}
2017-10-09 18:34:57.513 WARN 10617 --- [pool-3-thread-1]
o.a.a.store.kahadb.MessageDatabase : Cannot recover ackMessageFileMap
java.io.IOException: Invalid location size: 1:431, size: 0
at
org.apache.activemq.store.kahadb.disk.journal.DataFileAccessor.readRecord(DataFileAccessor.java:88)
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.disk.journal.Journal.read(Journal.java:936)
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:1151)
[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.MessageDatabase.recoverAckMessageFileMap(MessageDatabase.java:805)
[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.MessageDatabase.recover(MessageDatabase.java:675)
[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.MessageDatabase.open(MessageDatabase.java:473)
[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:493)
[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.MessageDatabase.doStart(MessageDatabase.java:297)
[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.KahaDBStore.doStart(KahaDBStore.java:219)
[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:55)
[activemq-client-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.KahaDBPersistenceAdapter.doStart(KahaDBPersistenceAdapter.java:232)
[activemq-kahadb-store-5.15.1.jar:5.15.1]
{code}
but the broker will at least start.
was (Author: masc3d):
yes, that would be possible, as it's my local dev db, it shouldn't contain
anything sensitive.
I also found that this issue is related to the preallocation kahadb settings:
{code}
pa.preallocationScope =
Journal.PreallocationScope.ENTIRE_JOURNAL_ASYNC.name
pa.preallocationStrategy = Journal.PreallocationStrategy.ZEROS.name
{code}
which I enabled for performance reasons.
Disabling preallocation will yield both
{code}
java.io.IOException: Invalid location size: 1:28, size: 0
at
org.apache.activemq.store.kahadb.disk.journal.DataFileAccessor.readRecord(DataFileAccessor.java:88)
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.disk.journal.Journal.read(Journal.java:936)
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:1151)
[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.MessageDatabase.recoverProducerAudit(Messa
[jira] [Updated] (AMQ-6831) Broker fails to start complaining about missing/corrupt journal files after upgrading to 5.15.1
[
https://issues.apache.org/jira/browse/AMQ-6831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
masc updated AMQ-6831:
--
Attachment: kahadb.zip
> Broker fails to start complaining about missing/corrupt journal files after
> upgrading to 5.15.1
> ---
>
> Key: AMQ-6831
> URL: https://issues.apache.org/jira/browse/AMQ-6831
> Project: ActiveMQ
> Issue Type: Bug
>Affects Versions: 5.15.1
>Reporter: masc
> Attachments: kahadb.zip
>
>
> {code}
> 2017-10-09 12:29:36.802 ERROR 4197 --- [pool-3-thread-1]
> org.deku.leoz.node.Application : java.io.IOException: Detected
> missing/corrupt journal files referenced by:[0:ActiveMQ.DLQ] 3 messages
> affected.
> java.lang.Error: java.io.IOException: Detected missing/corrupt journal files
> referenced by:[0:ActiveMQ.DLQ] 3 messages affected.
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1148)
> ~[na:1.8.0_131]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> ~[na:1.8.0_131]
> at java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_131]
> Caused by: java.io.IOException: Detected missing/corrupt journal files
> referenced by:[0:ActiveMQ.DLQ] 3 messages affected.
> at
> org.apache.activemq.store.kahadb.MessageDatabase.recoverIndex(MessageDatabase.java:965)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.MessageDatabase$5.execute(MessageDatabase.java:717)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.disk.page.Transaction.execute(Transaction.java:779)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.MessageDatabase.recover(MessageDatabase.java:714)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.MessageDatabase.open(MessageDatabase.java:473)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:493)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.MessageDatabase.doStart(MessageDatabase.java:297)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.KahaDBStore.doStart(KahaDBStore.java:219)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:55)
> ~[activemq-client-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.KahaDBPersistenceAdapter.doStart(KahaDBPersistenceAdapter.java:232)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> {code}
> Downgrading to 5.15.0 resolves the problem.
> This is an embedded broker setup, using
> {code:none}
> val pa = brokerService.persistenceAdapter as KahaDBPersistenceAdapter
> pa.isCheckForCorruptJournalFiles = true
> pa.isIgnoreMissingJournalfiles = false
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (AMQ-6831) Broker fails to start complaining about missing/corrupt journal files after upgrading to 5.15.1
[
https://issues.apache.org/jira/browse/AMQ-6831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16197268#comment-16197268
]
masc edited comment on AMQ-6831 at 10/9/17 4:42 PM:
yes, that would be possible, as it's my local dev db, it shouldn't contain
anything sensitive.
I also found that this issue is related to the preallocation kahadb settings:
{code}
pa.preallocationScope =
Journal.PreallocationScope.ENTIRE_JOURNAL_ASYNC.name
pa.preallocationStrategy = Journal.PreallocationStrategy.ZEROS.name
{code}
which I enabled for performance reasons.
Disabling preallocation will yield both
{code}
java.io.IOException: Invalid location size: 1:28, size: 0
at
org.apache.activemq.store.kahadb.disk.journal.DataFileAccessor.readRecord(DataFileAccessor.java:88)
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.disk.journal.Journal.read(Journal.java:936)
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:1151)
[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.MessageDatabase.recoverProducerAudit(MessageDatabase.java:784)
[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.MessageDatabase.recover(MessageDatabase.java:674)
[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.MessageDatabase.open(MessageDatabase.java:473)
[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:493)
[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.MessageDatabase.doStart(MessageDatabase.java:297)
[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.KahaDBStore.doStart(KahaDBStore.java:219)
[activemq-kahadb-store-5.15.1.jar:5.15.1]
{code}
and subsequently
{code}
2017-10-09 18:34:57.513 WARN 10617 --- [pool-3-thread-1]
o.a.a.store.kahadb.MessageDatabase : Cannot recover ackMessageFileMap
java.io.IOException: Invalid location size: 1:431, size: 0
at
org.apache.activemq.store.kahadb.disk.journal.DataFileAccessor.readRecord(DataFileAccessor.java:88)
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.disk.journal.Journal.read(Journal.java:936)
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:1151)
[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.MessageDatabase.recoverAckMessageFileMap(MessageDatabase.java:805)
[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.MessageDatabase.recover(MessageDatabase.java:675)
[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.MessageDatabase.open(MessageDatabase.java:473)
[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:493)
[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.MessageDatabase.doStart(MessageDatabase.java:297)
[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.KahaDBStore.doStart(KahaDBStore.java:219)
[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:55)
[activemq-client-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.KahaDBPersistenceAdapter.doStart(KahaDBPersistenceAdapter.java:232)
[activemq-kahadb-store-5.15.1.jar:5.15.1]
{code}
but the broker will at least start.
was (Author: masc3d):
yes, that would be possible, as it's my local dev db, it shouldn't contain
anything sensitive.
I also found that this issue is related to the preallocation kahadb settings:
{code}
pa.preallocationScope =
Journal.PreallocationScope.ENTIRE_JOURNAL_ASYNC.name
pa.preallocationStrategy = Journal.PreallocationStrategy.ZEROS.name
{code}
which I enabled for performance reasons.
Disabling preallocation will both
{code}
java.io.IOException: Invalid location size: 1:28, size: 0
at
org.apache.activemq.store.kahadb.disk.journal.DataFileAccessor.readRecord(DataFileAccessor.java:88)
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.disk.journal.Journal.read(Journal.java:936)
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:1151)
[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.MessageDatabase.recoverProducerAudit(MessageDatabase.java:784)
[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.MessageDatabase.recover(Messa
[jira] [Commented] (AMQ-6831) Broker fails to start complaining about missing/corrupt journal files after upgrading to 5.15.1
[
https://issues.apache.org/jira/browse/AMQ-6831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16197268#comment-16197268
]
masc commented on AMQ-6831:
---
yes, that would be possible, as it's my local dev db, it shouldn't contain
anything sensitive.
I also found that this issue is related to the preallocation kahadb settings:
{code}
pa.preallocationScope =
Journal.PreallocationScope.ENTIRE_JOURNAL_ASYNC.name
pa.preallocationStrategy = Journal.PreallocationStrategy.ZEROS.name
{code}
which I enabled for performance reasons.
Disabling preallocation will both
{code}
java.io.IOException: Invalid location size: 1:28, size: 0
at
org.apache.activemq.store.kahadb.disk.journal.DataFileAccessor.readRecord(DataFileAccessor.java:88)
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.disk.journal.Journal.read(Journal.java:936)
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:1151)
[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.MessageDatabase.recoverProducerAudit(MessageDatabase.java:784)
[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.MessageDatabase.recover(MessageDatabase.java:674)
[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.MessageDatabase.open(MessageDatabase.java:473)
[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:493)
[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.MessageDatabase.doStart(MessageDatabase.java:297)
[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.KahaDBStore.doStart(KahaDBStore.java:219)
[activemq-kahadb-store-5.15.1.jar:5.15.1]
{code}
and subsequently
{code}
2017-10-09 18:34:57.513 WARN 10617 --- [pool-3-thread-1]
o.a.a.store.kahadb.MessageDatabase : Cannot recover ackMessageFileMap
java.io.IOException: Invalid location size: 1:431, size: 0
at
org.apache.activemq.store.kahadb.disk.journal.DataFileAccessor.readRecord(DataFileAccessor.java:88)
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.disk.journal.Journal.read(Journal.java:936)
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:1151)
[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.MessageDatabase.recoverAckMessageFileMap(MessageDatabase.java:805)
[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.MessageDatabase.recover(MessageDatabase.java:675)
[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.MessageDatabase.open(MessageDatabase.java:473)
[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:493)
[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.MessageDatabase.doStart(MessageDatabase.java:297)
[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.KahaDBStore.doStart(KahaDBStore.java:219)
[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:55)
[activemq-client-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.KahaDBPersistenceAdapter.doStart(KahaDBPersistenceAdapter.java:232)
[activemq-kahadb-store-5.15.1.jar:5.15.1]
{code}
but the broker will at least start.
> Broker fails to start complaining about missing/corrupt journal files after
> upgrading to 5.15.1
> ---
>
> Key: AMQ-6831
> URL: https://issues.apache.org/jira/browse/AMQ-6831
> Project: ActiveMQ
> Issue Type: Bug
>Affects Versions: 5.15.1
>Reporter: masc
>
> {code}
> 2017-10-09 12:29:36.802 ERROR 4197 --- [pool-3-thread-1]
> org.deku.leoz.node.Application : java.io.IOException: Detected
> missing/corrupt journal files referenced by:[0:ActiveMQ.DLQ] 3 messages
> affected.
> java.lang.Error: java.io.IOException: Detected missing/corrupt journal files
> referenced by:[0:ActiveMQ.DLQ] 3 messages affected.
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1148)
> ~[na:1.8.0_131]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> ~[na:1.8.0_131]
> at java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_131]
> Caused by: java.io.IOException: Detected missing/corrupt journal files
> referenced by:[0:ActiveMQ.DLQ] 3 messages affected.
> at
>
[jira] [Updated] (AMQ-6831) Broker fails to start complaining about missing/corrupt journal files after upgrading to 5.15.1
[
https://issues.apache.org/jira/browse/AMQ-6831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
masc updated AMQ-6831:
--
Description:
{code}
2017-10-09 12:29:36.802 ERROR 4197 --- [pool-3-thread-1]
org.deku.leoz.node.Application : java.io.IOException: Detected
missing/corrupt journal files referenced by:[0:ActiveMQ.DLQ] 3 messages
affected.
java.lang.Error: java.io.IOException: Detected missing/corrupt journal files
referenced by:[0:ActiveMQ.DLQ] 3 messages affected.
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1148)
~[na:1.8.0_131]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
~[na:1.8.0_131]
at java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_131]
Caused by: java.io.IOException: Detected missing/corrupt journal files
referenced by:[0:ActiveMQ.DLQ] 3 messages affected.
at
org.apache.activemq.store.kahadb.MessageDatabase.recoverIndex(MessageDatabase.java:965)
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.MessageDatabase$5.execute(MessageDatabase.java:717)
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.disk.page.Transaction.execute(Transaction.java:779)
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.MessageDatabase.recover(MessageDatabase.java:714)
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.MessageDatabase.open(MessageDatabase.java:473)
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:493)
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.MessageDatabase.doStart(MessageDatabase.java:297)
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.KahaDBStore.doStart(KahaDBStore.java:219)
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:55)
~[activemq-client-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.KahaDBPersistenceAdapter.doStart(KahaDBPersistenceAdapter.java:232)
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
{code}
Downgrading to 5.15.0 resolves the problem.
This is an embedded broker setup, using
{code:none}
val pa = brokerService.persistenceAdapter as KahaDBPersistenceAdapter
pa.isCheckForCorruptJournalFiles = true
pa.isIgnoreMissingJournalfiles = false
{code}
was:
{code}
2017-10-09 12:29:36.802 ERROR 4197 --- [pool-3-thread-1]
org.deku.leoz.node.Application : java.io.IOException: Detected
missing/corrupt journal files referenced by:[0:ActiveMQ.DLQ] 3 messages
affected.
java.lang.Error: java.io.IOException: Detected missing/corrupt journal files
referenced by:[0:ActiveMQ.DLQ] 3 messages affected.
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1148)
~[na:1.8.0_131]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
~[na:1.8.0_131]
at java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_131]
Caused by: java.io.IOException: Detected missing/corrupt journal files
referenced by:[0:ActiveMQ.DLQ] 3 messages affected.
at
org.apache.activemq.store.kahadb.MessageDatabase.recoverIndex(MessageDatabase.java:965)
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.MessageDatabase$5.execute(MessageDatabase.java:717)
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.disk.page.Transaction.execute(Transaction.java:779)
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.MessageDatabase.recover(MessageDatabase.java:714)
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.MessageDatabase.open(MessageDatabase.java:473)
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:493)
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.MessageDatabase.doStart(MessageDatabase.java:297)
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.KahaDBStore.doStart(KahaDBStore.java:219)
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:55)
~[activemq-client-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.KahaDBPersistenceAdapter.doStart(KahaDBPersistenceAdapter.java:232)
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
{code}
Downgrading to 5.15.0 resolves the problem.
This is an embedded broker setup, using
{code:kotlin}
val pa = brokerService.persistenceAdapter as KahaDBPersistenceAdapter
pa.isCheckForCorruptJournalFiles =
[jira] [Updated] (AMQ-6831) Broker fails to start complaining about missing/corrupt journal files after upgrading to 5.15.1
[
https://issues.apache.org/jira/browse/AMQ-6831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
masc updated AMQ-6831:
--
Description:
{code}
2017-10-09 12:29:36.802 ERROR 4197 --- [pool-3-thread-1]
org.deku.leoz.node.Application : java.io.IOException: Detected
missing/corrupt journal files referenced by:[0:ActiveMQ.DLQ] 3 messages
affected.
java.lang.Error: java.io.IOException: Detected missing/corrupt journal files
referenced by:[0:ActiveMQ.DLQ] 3 messages affected.
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1148)
~[na:1.8.0_131]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
~[na:1.8.0_131]
at java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_131]
Caused by: java.io.IOException: Detected missing/corrupt journal files
referenced by:[0:ActiveMQ.DLQ] 3 messages affected.
at
org.apache.activemq.store.kahadb.MessageDatabase.recoverIndex(MessageDatabase.java:965)
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.MessageDatabase$5.execute(MessageDatabase.java:717)
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.disk.page.Transaction.execute(Transaction.java:779)
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.MessageDatabase.recover(MessageDatabase.java:714)
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.MessageDatabase.open(MessageDatabase.java:473)
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:493)
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.MessageDatabase.doStart(MessageDatabase.java:297)
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.KahaDBStore.doStart(KahaDBStore.java:219)
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:55)
~[activemq-client-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.KahaDBPersistenceAdapter.doStart(KahaDBPersistenceAdapter.java:232)
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
{code}
Downgrading to 5.15.0 resolves the problem.
This is an embedded broker setup, using
{code:kotlin}
val pa = brokerService.persistenceAdapter as KahaDBPersistenceAdapter
pa.isCheckForCorruptJournalFiles = true
pa.isIgnoreMissingJournalfiles = false
{code}
was:
```2017-10-09 12:29:36.802 ERROR 4197 --- [pool-3-thread-1]
org.deku.leoz.node.Application : java.io.IOException: Detected
missing/corrupt journal files referenced by:[0:ActiveMQ.DLQ] 3 messages
affected.
java.lang.Error: java.io.IOException: Detected missing/corrupt journal files
referenced by:[0:ActiveMQ.DLQ] 3 messages affected.
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1148)
~[na:1.8.0_131]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
~[na:1.8.0_131]
at java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_131]
Caused by: java.io.IOException: Detected missing/corrupt journal files
referenced by:[0:ActiveMQ.DLQ] 3 messages affected.
at
org.apache.activemq.store.kahadb.MessageDatabase.recoverIndex(MessageDatabase.java:965)
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.MessageDatabase$5.execute(MessageDatabase.java:717)
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.disk.page.Transaction.execute(Transaction.java:779)
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.MessageDatabase.recover(MessageDatabase.java:714)
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.MessageDatabase.open(MessageDatabase.java:473)
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:493)
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.MessageDatabase.doStart(MessageDatabase.java:297)
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.KahaDBStore.doStart(KahaDBStore.java:219)
~[activemq-kahadb-store-5.15.1.jar:5.15.1]
at
org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:55)
~[activemq-client-5.15.1.jar:5.15.1]
at
org.apache.activemq.store.kahadb.KahaDBPersistenceAdapter.doStart(KahaDBPersistenceAdapter.java:232)
~[activemq-kahadb-store-5.15.1.jar:5.15.1]```
Downgrading to 5.15.0 resolves the problem.
This is an embedded broker setup, using
```
val pa = brokerService.persistenceAdapter as KahaDBPersistenceAdapter
pa.isCheckForCorruptJournalFiles = true
pa.
[jira] [Created] (AMQ-6831) Broker fails to start complaining about missing/corrupt journal files after upgrading to 5.15.1
masc created AMQ-6831: - Summary: Broker fails to start complaining about missing/corrupt journal files after upgrading to 5.15.1 Key: AMQ-6831 URL: https://issues.apache.org/jira/browse/AMQ-6831 Project: ActiveMQ Issue Type: Bug Affects Versions: 5.15.1 Reporter: masc ```2017-10-09 12:29:36.802 ERROR 4197 --- [pool-3-thread-1] org.deku.leoz.node.Application : java.io.IOException: Detected missing/corrupt journal files referenced by:[0:ActiveMQ.DLQ] 3 messages affected. java.lang.Error: java.io.IOException: Detected missing/corrupt journal files referenced by:[0:ActiveMQ.DLQ] 3 messages affected. at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1148) ~[na:1.8.0_131] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) ~[na:1.8.0_131] at java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_131] Caused by: java.io.IOException: Detected missing/corrupt journal files referenced by:[0:ActiveMQ.DLQ] 3 messages affected. at org.apache.activemq.store.kahadb.MessageDatabase.recoverIndex(MessageDatabase.java:965) ~[activemq-kahadb-store-5.15.1.jar:5.15.1] at org.apache.activemq.store.kahadb.MessageDatabase$5.execute(MessageDatabase.java:717) ~[activemq-kahadb-store-5.15.1.jar:5.15.1] at org.apache.activemq.store.kahadb.disk.page.Transaction.execute(Transaction.java:779) ~[activemq-kahadb-store-5.15.1.jar:5.15.1] at org.apache.activemq.store.kahadb.MessageDatabase.recover(MessageDatabase.java:714) ~[activemq-kahadb-store-5.15.1.jar:5.15.1] at org.apache.activemq.store.kahadb.MessageDatabase.open(MessageDatabase.java:473) ~[activemq-kahadb-store-5.15.1.jar:5.15.1] at org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:493) ~[activemq-kahadb-store-5.15.1.jar:5.15.1] at org.apache.activemq.store.kahadb.MessageDatabase.doStart(MessageDatabase.java:297) ~[activemq-kahadb-store-5.15.1.jar:5.15.1] at org.apache.activemq.store.kahadb.KahaDBStore.doStart(KahaDBStore.java:219) ~[activemq-kahadb-store-5.15.1.jar:5.15.1] at org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:55) ~[activemq-client-5.15.1.jar:5.15.1] at org.apache.activemq.store.kahadb.KahaDBPersistenceAdapter.doStart(KahaDBPersistenceAdapter.java:232) ~[activemq-kahadb-store-5.15.1.jar:5.15.1]``` Downgrading to 5.15.0 resolves the problem. This is an embedded broker setup, using ``` val pa = brokerService.persistenceAdapter as KahaDBPersistenceAdapter pa.isCheckForCorruptJournalFiles = true pa.isIgnoreMissingJournalfiles = false ``` -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (ARTEMIS-355) Duplex bridges
[ https://issues.apache.org/jira/browse/ARTEMIS-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15785610#comment-15785610 ] masc edited comment on ARTEMIS-355 at 12/29/16 4:17 PM: As I understand the documentation a single JMS bridge is closely tied to a single source/target destination pair. Just to make sure I understand you correctly. Are JMS bridges really a viable temporary solution if you need seamless duplex connectivity for all JMS destinations across all nodes of a broker network? was (Author: masc3d): As I understand the documentation JMS bridges are closely tied to a single source/target destination pair. Just to make sure I understand you correctly. Are JMS bridges really a viable temporary solution if you need seamless duplex connectivity for all JMS destinations across all nodes of a broker network? > Duplex bridges > -- > > Key: ARTEMIS-355 > URL: https://issues.apache.org/jira/browse/ARTEMIS-355 > Project: ActiveMQ Artemis > Issue Type: New Feature > Components: Broker >Affects Versions: 1.2.0 >Reporter: Mike Hearn >Assignee: Martyn Taylor > Fix For: 2.0.0 > > > I can't find any way to make an embedded artemis A connect to an embedded > artemis B such that B can send messages to A without connectivity at the TCP > level, e.g. due to firewall traversal. It'd be convenient if there was no > need for me to implement firewall punching myself. Apparently ActiveMQ can do > this using some sort of "duplex" attribute, but it's not in Artemis. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ARTEMIS-355) Duplex bridges
[ https://issues.apache.org/jira/browse/ARTEMIS-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15785610#comment-15785610 ] masc commented on ARTEMIS-355: -- As I understand the documentation JMS bridges are closely tied to a single source/target destination pair. Just to make sure I understand you correctly. Are JMS bridges really a viable temporary solution if you need seamless duplex connectivity for all JMS destinations across all nodes of a broker network? > Duplex bridges > -- > > Key: ARTEMIS-355 > URL: https://issues.apache.org/jira/browse/ARTEMIS-355 > Project: ActiveMQ Artemis > Issue Type: New Feature > Components: Broker >Affects Versions: 1.2.0 >Reporter: Mike Hearn >Assignee: Martyn Taylor > Fix For: 2.0.0 > > > I can't find any way to make an embedded artemis A connect to an embedded > artemis B such that B can send messages to A without connectivity at the TCP > level, e.g. due to firewall traversal. It'd be convenient if there was no > need for me to implement firewall punching myself. Apparently ActiveMQ can do > this using some sort of "duplex" attribute, but it's not in Artemis. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ARTEMIS-355) Duplex bridges
[ https://issues.apache.org/jira/browse/ARTEMIS-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15637021#comment-15637021 ] masc commented on ARTEMIS-355: -- A bit sad to see this postponed all the time, as it's currently the only issue blocking us from migrating from ActiveMQ to Artemis. > Duplex bridges > -- > > Key: ARTEMIS-355 > URL: https://issues.apache.org/jira/browse/ARTEMIS-355 > Project: ActiveMQ Artemis > Issue Type: New Feature > Components: Broker >Affects Versions: 1.2.0 >Reporter: Mike Hearn >Assignee: Martyn Taylor > Fix For: 1.6.0 > > > I can't find any way to make an embedded artemis A connect to an embedded > artemis B such that B can send messages to A without connectivity at the TCP > level, e.g. due to firewall traversal. It'd be convenient if there was no > need for me to implement firewall punching myself. Apparently ActiveMQ can do > this using some sort of "duplex" attribute, but it's not in Artemis. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMQ-6155) Spurious InvalidDestinationException publishing to a temp queue from a new connection
[ https://issues.apache.org/jira/browse/AMQ-6155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15151536#comment-15151536 ] masc commented on AMQ-6155: --- Yes. Without topic advisories it works fine. Here's some interesting log entries from the receiver. The queue seems to be created prior to send. Version is 5.13.1 ... 2016-02-18 01:15:22,683 131622 ActiveMQ VMTransport: vm://leoz-aq-86c3ca5c3a347577744055d910d00c6fa9811a53#3-3 org.apache.activemq.broker.region.AbstractRegion DEBUG - leoz-aq-86c3ca5c3a347577744055d910d00c6fa9811a53 adding destination: temp-queue://ID:agnus.o81.5-57628-1455753254297-7:1:99 2016-02-18 01:15:22,683 131622 DefaultMessageListenerContainer-1 org.deku.leoz.node.data.sync.EntityPublisher ERROR - Cannot publish to a deleted Destination: temp-queue://ID:agnus.o81.5-57628-1455753254297-7:1:99 javax.jms.InvalidDestinationException: Cannot publish to a deleted Destination: temp-queue://ID:agnus.o81.5-57628-1455753254297-7:1:99 at org.apache.activemq.ActiveMQSession.send(ActiveMQSession.java:1904) at org.apache.activemq.ActiveMQMessageProducer.send(ActiveMQMessageProducer.java:288) at org.apache.activemq.ActiveMQMessageProducer.send(ActiveMQMessageProducer.java:223) at org.apache.activemq.jms.pool.PooledProducer.send(PooledProducer.java:95) at org.apache.activemq.jms.pool.PooledProducer.send(PooledProducer.java:66) at org.deku.leoz.node.data.sync.EntityPublisher.onMessage(EntityPublisher.kt:99) at sx.jms.listeners.SpringJmsListener.access$onMessage(SpringJmsListener.kt:18) at sx.jms.listeners.SpringJmsListener$start$1.onMessage(SpringJmsListener.kt:55) ... 2016-02-18 01:15:27,699 136638 ActiveMQ VMTransport: vm://leoz-aq-86c3ca5c3a347577744055d910d00c6fa9811a53#3-4 org.apache.activemq.broker.region.AbstractRegion DEBUG - leoz-aq-86c3ca5c3a347577744055d910d00c6fa9811a53 removing destination: temp-queue://ID:agnus.o81.5-57628-1455753254297-7:1:99 ... > Spurious InvalidDestinationException publishing to a temp queue from a new > connection > - > > Key: AMQ-6155 > URL: https://issues.apache.org/jira/browse/AMQ-6155 > Project: ActiveMQ > Issue Type: Bug > Components: JMS client >Affects Versions: 5.10.2, 5.13.0 > Environment: Windows, OS X >Reporter: Kevin Bowman > Attachments: AmqTempRaceConditionMinimalTest.java > > > When a new connection is opened for the purpose of sending a message to a > temporary queue it sometimes fails with the following exception (stack trace > is from v5.13.0): > javax.jms.InvalidDestinationException: Cannot publish to a deleted > Destination: temp-queue://ID:Potomac.local-59943-1454448412194-1:1:96 > at org.apache.activemq.ActiveMQSession.send(ActiveMQSession.java:1904) > at > org.apache.activemq.ActiveMQMessageProducer.send(ActiveMQMessageProducer.java:288) > at > org.apache.activemq.ActiveMQMessageProducer.send(ActiveMQMessageProducer.java:223) > at > org.apache.activemq.ActiveMQMessageProducerSupport.send(ActiveMQMessageProducerSupport.java:241) > The actual problem appears to be in ActiveMQConnection.isDeleted(). Because > the connection being used to send to the temp queue is not the connection > under which the temp queue was created, it's dependent on AdvisoryConsumer to > populate the activeTempDestinations map before the send() call is made. The > AdvisoryConsumer gets called in a separate thread, asynchronous with the main > thread, so this constitutes a race condition. If the send() call is made > before AdvisoryConsumer can notify the new connection of all existing temp > queues then it will throw an InvalidDestinationException even though the temp > queue does actually exist. > Calling setWatchTopicAdvisories(false) on the sending connection's factory > alleviates the problem and the program can run indefinitely with no errors. > Also, adding a delay before the MessageProducer.send() call can alleviate the > error somewhat, but with a small enough delay it will still happen eventually. > I noticed this first in an environment I don't have full control over. It > happened the first time, every time, for reasons I still don't quite > understand. I have written a small test program that reproduces the error > outside of the original environment, but it runs in a loop and it takes a few > hundred iterations for it to occur. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMQ-6155) Spurious InvalidDestinationException publishing to a temp queue from a new connection
[ https://issues.apache.org/jira/browse/AMQ-6155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15151462#comment-15151462 ] masc commented on AMQ-6155: --- I'm seeing the same issue with a single connection creating a temporary queue and sending a request/response to a network of brokers. The message is sporadically delivered before the temporary queue is available in the remote broker, resulting in the same error/stacktrace when sending the reply. Should the issue be reopened? > Spurious InvalidDestinationException publishing to a temp queue from a new > connection > - > > Key: AMQ-6155 > URL: https://issues.apache.org/jira/browse/AMQ-6155 > Project: ActiveMQ > Issue Type: Bug > Components: JMS client >Affects Versions: 5.10.2, 5.13.0 > Environment: Windows, OS X >Reporter: Kevin Bowman > Attachments: AmqTempRaceConditionMinimalTest.java > > > When a new connection is opened for the purpose of sending a message to a > temporary queue it sometimes fails with the following exception (stack trace > is from v5.13.0): > javax.jms.InvalidDestinationException: Cannot publish to a deleted > Destination: temp-queue://ID:Potomac.local-59943-1454448412194-1:1:96 > at org.apache.activemq.ActiveMQSession.send(ActiveMQSession.java:1904) > at > org.apache.activemq.ActiveMQMessageProducer.send(ActiveMQMessageProducer.java:288) > at > org.apache.activemq.ActiveMQMessageProducer.send(ActiveMQMessageProducer.java:223) > at > org.apache.activemq.ActiveMQMessageProducerSupport.send(ActiveMQMessageProducerSupport.java:241) > The actual problem appears to be in ActiveMQConnection.isDeleted(). Because > the connection being used to send to the temp queue is not the connection > under which the temp queue was created, it's dependent on AdvisoryConsumer to > populate the activeTempDestinations map before the send() call is made. The > AdvisoryConsumer gets called in a separate thread, asynchronous with the main > thread, so this constitutes a race condition. If the send() call is made > before AdvisoryConsumer can notify the new connection of all existing temp > queues then it will throw an InvalidDestinationException even though the temp > queue does actually exist. > Calling setWatchTopicAdvisories(false) on the sending connection's factory > alleviates the problem and the program can run indefinitely with no errors. > Also, adding a delay before the MessageProducer.send() call can alleviate the > error somewhat, but with a small enough delay it will still happen eventually. > I noticed this first in an environment I don't have full control over. It > happened the first time, every time, for reasons I still don't quite > understand. I have written a small test program that reproduces the error > outside of the original environment, but it runs in a loop and it takes a few > hundred iterations for it to occur. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
