You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Andrei Shakirin (JIRA)" <ji...@apache.org> on 2017/05/31 11:53:04 UTC
[jira] [Updated] (AMQ-6692) Broker hangs after file writting
exception
[ https://issues.apache.org/jira/browse/AMQ-6692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrei Shakirin updated AMQ-6692:
---------------------------------
Description:
I observe the following strange broker behavior:
after following error by creating queue directory:
{code}
2017-05-29 10:15:25,477 | ERROR | java.lang.RuntimeException: Failed to start per destination persistence adapter for destination: queue://MY.QUEUE, options:[KahaDBPersistenceAdapter[/CE/activemq/queue#3a#2f#2fQ.MP.ORDER.SPLIT], KahaDBPersistenceAdapter[/CE/activemq/queue#3a#2f#2fQ.MP.ORDER.CREATE], KahaDBPersistenceAdapter[/CE/activemq/queue#3a#2f#2fQ.MP.ORDER.UPDATE], KahaDBPersistenceAdapter[/CE/activemq/queue#3a#2f#2fMY.QUEUE]] | org.apache.activemq.store.kahadb.MultiKahaDBPersistenceAdapter | ActiveMQ Transport: tcp:///172.26.244.182:54858@61617
java.io.IOException: Failed to create directory '/CE/activemq/queue#3a#2f#2fMY.QUEUE'
at org.apache.activemq.util.IOHelper.mkdirs(IOHelper.java:331)[activemq-broker-5.13.4.jar:5.13.4]
at org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:442)[activemq-kahadb-store-5.13.4.jar:5.13.4]
at org.apache.activemq.store.kahadb.MessageDatabase.doStart(MessageDatabase.java:287)[activemq-kahadb-store-5.13.4.jar:5.13.4]
at org.apache.activemq.store.kahadb.KahaDBStore.doStart(KahaDBStore.java:215)[activemq-kahadb-store-5.13.4.jar:5.13.4]
at org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:55)[activemq-client-5.13.4.jar:5.13.4]
at org.apache.activemq.store.kahadb.KahaDBPersistenceAdapter.doStart(KahaDBPersistenceAdapter.java:223)[activemq-kahadb-store-5.13.4.jar:5.13.4]
{code}
The broker hangs and keeps running connections. The JMS clients are blocked for undefined time.
InactivityMonitor reports a bunch of following warnings:
{code}
2017-05-29 11:31:09,545 | WARN | Transport Connection to: tcp://172.26.244.182:37994 failed: java.net.SocketException: Broken pipe (Write failed) | org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ InactivityMonitor Worker
{code}
Any option to prevent blocking benavior and drop active connections?
was:
I observe the following strange broker behavior:
after following error by creating queue directory:
{code}
2017-05-29 10:15:25,477 | ERROR | java.lang.RuntimeException: Failed to start per destination persistence adapter for destination: queue://MY.QUEUE, options:[KahaDBPersistenceAdapter[/CE/activemq/queue#3a#2f#2fQ.MP.ORDER.SPLIT], KahaDBPersistenceAdapter[/CE/activemq/queue#3a#2f#2fQ.MP.ORDER.CREATE], KahaDBPersistenceAdapter[/CE/activemq/queue#3a#2f#2fQ.MP.ORDER.UPDATE], KahaDBPersistenceAdapter[/CE/activemq/queue#3a#2f#2fMY.QUEUE]] | org.apache.activemq.store.kahadb.MultiKahaDBPersistenceAdapter | ActiveMQ Transport: tcp:///172.26.244.182:54858@61617
java.io.IOException: Failed to create directory '/CE/activemq/queue#3a#2f#2fMY.QUEUE'
at org.apache.activemq.util.IOHelper.mkdirs(IOHelper.java:331)[activemq-broker-5.13.4.jar:5.13.4]
at org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:442)[activemq-kahadb-store-5.13.4.jar:5.13.4]
at org.apache.activemq.store.kahadb.MessageDatabase.doStart(MessageDatabase.java:287)[activemq-kahadb-store-5.13.4.jar:5.13.4]
at org.apache.activemq.store.kahadb.KahaDBStore.doStart(KahaDBStore.java:215)[activemq-kahadb-store-5.13.4.jar:5.13.4]
at org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:55)[activemq-client-5.13.4.jar:5.13.4]
at org.apache.activemq.store.kahadb.KahaDBPersistenceAdapter.doStart(KahaDBPersistenceAdapter.java:223)[activemq-kahadb-store-5.13.4.jar:5.13.4]
{code}
The broker hangs and keeps running connections. The JMS clients are blocked for undfined time.
InactivityMonitor reports a bunch of following warnings:
{code}
2017-05-29 11:31:09,545 | WARN | Transport Connection to: tcp://172.26.244.182:37994 failed: java.net.SocketException: Broken pipe (Write failed) | org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ InactivityMonitor Worker
{code}
Any option to prevent blocking benavior and drop active connections?
> Broker hangs after file writting exception
> ------------------------------------------
>
> Key: AMQ-6692
> URL: https://issues.apache.org/jira/browse/AMQ-6692
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.13.4
> Reporter: Andrei Shakirin
>
> I observe the following strange broker behavior:
> after following error by creating queue directory:
> {code}
> 2017-05-29 10:15:25,477 | ERROR | java.lang.RuntimeException: Failed to start per destination persistence adapter for destination: queue://MY.QUEUE, options:[KahaDBPersistenceAdapter[/CE/activemq/queue#3a#2f#2fQ.MP.ORDER.SPLIT], KahaDBPersistenceAdapter[/CE/activemq/queue#3a#2f#2fQ.MP.ORDER.CREATE], KahaDBPersistenceAdapter[/CE/activemq/queue#3a#2f#2fQ.MP.ORDER.UPDATE], KahaDBPersistenceAdapter[/CE/activemq/queue#3a#2f#2fMY.QUEUE]] | org.apache.activemq.store.kahadb.MultiKahaDBPersistenceAdapter | ActiveMQ Transport: tcp:///172.26.244.182:54858@61617
> java.io.IOException: Failed to create directory '/CE/activemq/queue#3a#2f#2fMY.QUEUE'
> at org.apache.activemq.util.IOHelper.mkdirs(IOHelper.java:331)[activemq-broker-5.13.4.jar:5.13.4]
> at org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:442)[activemq-kahadb-store-5.13.4.jar:5.13.4]
> at org.apache.activemq.store.kahadb.MessageDatabase.doStart(MessageDatabase.java:287)[activemq-kahadb-store-5.13.4.jar:5.13.4]
> at org.apache.activemq.store.kahadb.KahaDBStore.doStart(KahaDBStore.java:215)[activemq-kahadb-store-5.13.4.jar:5.13.4]
> at org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:55)[activemq-client-5.13.4.jar:5.13.4]
> at org.apache.activemq.store.kahadb.KahaDBPersistenceAdapter.doStart(KahaDBPersistenceAdapter.java:223)[activemq-kahadb-store-5.13.4.jar:5.13.4]
> {code}
> The broker hangs and keeps running connections. The JMS clients are blocked for undefined time.
> InactivityMonitor reports a bunch of following warnings:
> {code}
> 2017-05-29 11:31:09,545 | WARN | Transport Connection to: tcp://172.26.244.182:37994 failed: java.net.SocketException: Broken pipe (Write failed) | org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ InactivityMonitor Worker
> {code}
> Any option to prevent blocking benavior and drop active connections?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)