[jira] [Resolved] (ARTEMIS-2590) Support com.sun.jndi.ldap.read.timeout in LDAPLoginModule
[ https://issues.apache.org/jira/browse/ARTEMIS-2590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram resolved ARTEMIS-2590. - Fix Version/s: 2.11.0 Resolution: Fixed > Support com.sun.jndi.ldap.read.timeout in LDAPLoginModule > - > > Key: ARTEMIS-2590 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2590 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Fix For: 2.11.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (ARTEMIS-2584) Optimize PageTransactionInfoImpl in-memory size
[ https://issues.apache.org/jira/browse/ARTEMIS-2584?focusedWorklogId=368301=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-368301 ] ASF GitHub Bot logged work on ARTEMIS-2584: --- Author: ASF GitHub Bot Created on: 08/Jan/20 17:39 Start Date: 08/Jan/20 17:39 Worklog Time Spent: 10m Work Description: asfgit commented on pull request #2925: ARTEMIS-2584 Optimize PageTransactionInfoImpl in-memory size URL: https://github.com/apache/activemq-artemis/pull/2925 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 368301) Time Spent: 20m (was: 10m) > Optimize PageTransactionInfoImpl in-memory size > --- > > Key: ARTEMIS-2584 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2584 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Broker >Affects Versions: 2.10.1 >Reporter: Wei Yang >Assignee: Wei Yang >Priority: Minor > Time Spent: 20m > Remaining Estimate: 0h > > The in-memory size of PageTransactionInfoImpl can be made smaller. > For numberOfMessages and numberOfPersistentMessages, we can use native int to > save object header size, i.e. 2*12=24 bytes if using Compressed oops or > 2*16=32 bytes if not. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ARTEMIS-2584) Optimize PageTransactionInfoImpl in-memory size
[ https://issues.apache.org/jira/browse/ARTEMIS-2584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17010861#comment-17010861 ] ASF subversion and git services commented on ARTEMIS-2584: -- Commit 0e6a1dee47fc15a3998a1b2e23c4885c5f90e76d in activemq-artemis's branch refs/heads/master from Wei Yang [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=0e6a1de ] ARTEMIS-2584 Optimize PageTransactionInfoImpl in-memory size > Optimize PageTransactionInfoImpl in-memory size > --- > > Key: ARTEMIS-2584 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2584 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Broker >Affects Versions: 2.10.1 >Reporter: Wei Yang >Assignee: Wei Yang >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > The in-memory size of PageTransactionInfoImpl can be made smaller. > For numberOfMessages and numberOfPersistentMessages, we can use native int to > save object header size, i.e. 2*12=24 bytes if using Compressed oops or > 2*16=32 bytes if not. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (ARTEMIS-2590) Support com.sun.jndi.ldap.read.timeout in LDAPLoginModule
[ https://issues.apache.org/jira/browse/ARTEMIS-2590?focusedWorklogId=368300=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-368300 ] ASF GitHub Bot logged work on ARTEMIS-2590: --- Author: ASF GitHub Bot Created on: 08/Jan/20 17:38 Start Date: 08/Jan/20 17:38 Worklog Time Spent: 10m Work Description: asfgit commented on pull request #2931: ARTEMIS-2590 support com.sun.jndi.ldap.read.timeout in LDAPLoginModule URL: https://github.com/apache/activemq-artemis/pull/2931 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 368300) Time Spent: 20m (was: 10m) > Support com.sun.jndi.ldap.read.timeout in LDAPLoginModule > - > > Key: ARTEMIS-2590 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2590 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ARTEMIS-2590) Support com.sun.jndi.ldap.read.timeout in LDAPLoginModule
[ https://issues.apache.org/jira/browse/ARTEMIS-2590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17010859#comment-17010859 ] ASF subversion and git services commented on ARTEMIS-2590: -- Commit 1ad8b3c05987a15309014c8d4b56a0b5af5b759d in activemq-artemis's branch refs/heads/master from Justin Bertram [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=1ad8b3c ] ARTEMIS-2590 support com.sun.jndi.ldap.read.timeout in LDAPLoginModule > Support com.sun.jndi.ldap.read.timeout in LDAPLoginModule > - > > Key: ARTEMIS-2590 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2590 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (ARTEMIS-2591) Add details to consumer lock timeout log
[ https://issues.apache.org/jira/browse/ARTEMIS-2591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram resolved ARTEMIS-2591. - Fix Version/s: 2.11.0 Resolution: Fixed > Add details to consumer lock timeout log > > > Key: ARTEMIS-2591 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2591 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Fix For: 2.11.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ARTEMIS-2591) Add details to consumer lock timeout log
[ https://issues.apache.org/jira/browse/ARTEMIS-2591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17010855#comment-17010855 ] ASF subversion and git services commented on ARTEMIS-2591: -- Commit 6a290cf2b27e140f0e311bc483e1b467b347ae20 in activemq-artemis's branch refs/heads/master from Justin Bertram [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=6a290cf ] ARTEMIS-2591 add details to consumer lock timeout log > Add details to consumer lock timeout log > > > Key: ARTEMIS-2591 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2591 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (ARTEMIS-2591) Add details to consumer lock timeout log
[ https://issues.apache.org/jira/browse/ARTEMIS-2591?focusedWorklogId=368297=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-368297 ] ASF GitHub Bot logged work on ARTEMIS-2591: --- Author: ASF GitHub Bot Created on: 08/Jan/20 17:35 Start Date: 08/Jan/20 17:35 Worklog Time Spent: 10m Work Description: asfgit commented on pull request #2932: ARTEMIS-2591 add details to consumer lock timeout log URL: https://github.com/apache/activemq-artemis/pull/2932 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 368297) Time Spent: 20m (was: 10m) > Add details to consumer lock timeout log > > > Key: ARTEMIS-2591 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2591 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (ARTEMIS-2497) Allow configuring alternative reject behavior for AMQP
[ https://issues.apache.org/jira/browse/ARTEMIS-2497?focusedWorklogId=368291=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-368291 ] ASF GitHub Bot logged work on ARTEMIS-2497: --- Author: ASF GitHub Bot Created on: 08/Jan/20 17:26 Start Date: 08/Jan/20 17:26 Worklog Time Spent: 10m Work Description: asfgit commented on pull request #2848: ARTEMIS-2497: [AMQP] Allow handling of the reject disposition to be configured URL: https://github.com/apache/activemq-artemis/pull/2848 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 368291) Time Spent: 1h 50m (was: 1h 40m) > Allow configuring alternative reject behavior for AMQP > -- > > Key: ARTEMIS-2497 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2497 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: AMQP >Affects Versions: 2.10.0 >Reporter: Ulf Lilleengen >Priority: Major > Time Spent: 1h 50m > Remaining Estimate: 0h > > In EnMasse, we use a broker plugin to forward messages to a remote AMQP > endpoint. If the remote endpoint responds with a reject, we would like to > retry the message. > > At present, the AMQP implementation will deal with rejects by immediately > putting the messages on a DLQ (if exists). > > It would be nice to have a configuration option to have rejects be treated > similarly to released by attempting retransmit before moving to DLQ. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ARTEMIS-2497) Allow configuring alternative reject behavior for AMQP
[ https://issues.apache.org/jira/browse/ARTEMIS-2497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17010850#comment-17010850 ] ASF subversion and git services commented on ARTEMIS-2497: -- Commit 39cd9d56f67ad167e60ffba4a14f82e05b43c169 in activemq-artemis's branch refs/heads/master from Keith Wall [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=39cd9d5 ] ARTEMIS-2497: [AMQP] Allow handling of the reject disposition to be configured. > Allow configuring alternative reject behavior for AMQP > -- > > Key: ARTEMIS-2497 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2497 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: AMQP >Affects Versions: 2.10.0 >Reporter: Ulf Lilleengen >Priority: Major > Time Spent: 1h 40m > Remaining Estimate: 0h > > In EnMasse, we use a broker plugin to forward messages to a remote AMQP > endpoint. If the remote endpoint responds with a reject, we would like to > retry the message. > > At present, the AMQP implementation will deal with rejects by immediately > putting the messages on a DLQ (if exists). > > It would be nice to have a configuration option to have rejects be treated > similarly to released by attempting retransmit before moving to DLQ. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (ARTEMIS-2591) Add details to consumer lock timeout log
[ https://issues.apache.org/jira/browse/ARTEMIS-2591?focusedWorklogId=368285=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-368285 ] ASF GitHub Bot logged work on ARTEMIS-2591: --- Author: ASF GitHub Bot Created on: 08/Jan/20 17:20 Start Date: 08/Jan/20 17:20 Worklog Time Spent: 10m Work Description: jbertram commented on pull request #2932: ARTEMIS-2591 add details to consumer lock timeout log URL: https://github.com/apache/activemq-artemis/pull/2932 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 368285) Remaining Estimate: 0h Time Spent: 10m > Add details to consumer lock timeout log > > > Key: ARTEMIS-2591 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2591 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ARTEMIS-2494) Artemis responds with disposition Rejected if queue is full
[ https://issues.apache.org/jira/browse/ARTEMIS-2494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated ARTEMIS-2494: Fix Version/s: 2.11.0 > Artemis responds with disposition Rejected if queue is full > --- > > Key: ARTEMIS-2494 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2494 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: AMQP >Affects Versions: 2.10.0 >Reporter: Ulf Lilleengen >Priority: Major > Fix For: 2.11.0 > > Time Spent: 3h 40m > Remaining Estimate: 0h > > When a queue is full, Artemis will respond with disposition=Rejected. In > certain situations, it is desirable to receive a Modified in this case, so > that a client may re-queue the message for re-delivery (this is what Artemis > does if consumers respond with released or modified for instance). > > The current behavior is determined by > ProtonServerReceiverContext#actualDelivery . It would be great if this method > could respond with Modified instead in the event of the exception being an > ActiveMQAddressFullException. > > This behavior should probably be exposed as a configuration option to avoid > breaking existing behavior. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (ARTEMIS-2494) Artemis responds with disposition Rejected if queue is full
[ https://issues.apache.org/jira/browse/ARTEMIS-2494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved ARTEMIS-2494. - Resolution: Fixed > Artemis responds with disposition Rejected if queue is full > --- > > Key: ARTEMIS-2494 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2494 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: AMQP >Affects Versions: 2.10.0 >Reporter: Ulf Lilleengen >Priority: Major > Fix For: 2.11.0 > > Time Spent: 3h 40m > Remaining Estimate: 0h > > When a queue is full, Artemis will respond with disposition=Rejected. In > certain situations, it is desirable to receive a Modified in this case, so > that a client may re-queue the message for re-delivery (this is what Artemis > does if consumers respond with released or modified for instance). > > The current behavior is determined by > ProtonServerReceiverContext#actualDelivery . It would be great if this method > could respond with Modified instead in the event of the exception being an > ActiveMQAddressFullException. > > This behavior should probably be exposed as a configuration option to avoid > breaking existing behavior. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ARTEMIS-2591) Add details to consumer lock timeout log
Justin Bertram created ARTEMIS-2591: --- Summary: Add details to consumer lock timeout log Key: ARTEMIS-2591 URL: https://issues.apache.org/jira/browse/ARTEMIS-2591 Project: ActiveMQ Artemis Issue Type: Improvement Reporter: Justin Bertram Assignee: Justin Bertram -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (ARTEMIS-2497) Allow configuring alternative reject behavior for AMQP
[ https://issues.apache.org/jira/browse/ARTEMIS-2497?focusedWorklogId=368262=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-368262 ] ASF GitHub Bot logged work on ARTEMIS-2497: --- Author: ASF GitHub Bot Created on: 08/Jan/20 16:50 Start Date: 08/Jan/20 16:50 Worklog Time Spent: 10m Work Description: jbertram commented on issue #2848: ARTEMIS-2497: [AMQP] Allow handling of the reject disposition to be configured URL: https://github.com/apache/activemq-artemis/pull/2848#issuecomment-572157569 @k-wall can you rebase this? Conflicts have developed. Thanks! This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 368262) Time Spent: 1h 40m (was: 1.5h) > Allow configuring alternative reject behavior for AMQP > -- > > Key: ARTEMIS-2497 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2497 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: AMQP >Affects Versions: 2.10.0 >Reporter: Ulf Lilleengen >Priority: Major > Time Spent: 1h 40m > Remaining Estimate: 0h > > In EnMasse, we use a broker plugin to forward messages to a remote AMQP > endpoint. If the remote endpoint responds with a reject, we would like to > retry the message. > > At present, the AMQP implementation will deal with rejects by immediately > putting the messages on a DLQ (if exists). > > It would be nice to have a configuration option to have rejects be treated > similarly to released by attempting retransmit before moving to DLQ. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (ARTEMIS-2590) Support com.sun.jndi.ldap.read.timeout in LDAPLoginModule
[ https://issues.apache.org/jira/browse/ARTEMIS-2590?focusedWorklogId=368260=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-368260 ] ASF GitHub Bot logged work on ARTEMIS-2590: --- Author: ASF GitHub Bot Created on: 08/Jan/20 16:47 Start Date: 08/Jan/20 16:47 Worklog Time Spent: 10m Work Description: jbertram commented on pull request #2931: ARTEMIS-2590 support com.sun.jndi.ldap.read.timeout in LDAPLoginModule URL: https://github.com/apache/activemq-artemis/pull/2931 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 368260) Remaining Estimate: 0h Time Spent: 10m > Support com.sun.jndi.ldap.read.timeout in LDAPLoginModule > - > > Key: ARTEMIS-2590 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2590 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ARTEMIS-2590) Support com.sun.jndi.ldap.read.timeout in LDAPLoginModule
Justin Bertram created ARTEMIS-2590: --- Summary: Support com.sun.jndi.ldap.read.timeout in LDAPLoginModule Key: ARTEMIS-2590 URL: https://issues.apache.org/jira/browse/ARTEMIS-2590 Project: ActiveMQ Artemis Issue Type: Improvement Reporter: Justin Bertram Assignee: Justin Bertram -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (ARTEMIS-2567) Shared-store failback broken on NFS
[
https://issues.apache.org/jira/browse/ARTEMIS-2567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram resolved ARTEMIS-2567.
-
Resolution: Fixed
> Shared-store failback broken on NFS
> ---
>
> Key: ARTEMIS-2567
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2567
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.10.1
>Reporter: Justin Bertram
>Assignee: Justin Bertram
>Priority: Major
> Fix For: 2.11.0
>
> Time Spent: 2h 50m
> Remaining Estimate: 0h
>
> The changes from ARTEMIS-2441 caused a regression of the issue fixed by
> ARTEMIS-1417.
> The changes in ARTEMIS-1417 made sure to lock/unlock the {{server.lock}} file
> when reading the state information in order to deal with stale data over NFS.
> However, the changes from ARTEMIS-2441 split the lock into several different
> files which means that when the state information is read now the
> {{server.lock}} file itself is not locked/unlocked which results in reading
> stale data on the slave.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ARTEMIS-2586) Inifinite Block in AMQ212054 after transient DB-error
[
https://issues.apache.org/jira/browse/ARTEMIS-2586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17010517#comment-17010517
]
Rico Neubauer commented on ARTEMIS-2586:
[~jbertram] Thanks for your reply and your hints.
No, we are not acknowledging the message before the send.
I will set up a test which provokes the situation and check whether
acknowledging resolves the situation (whereas this would actually not be the
desired flow).
About the AMQP - yes, it was because of the "AMQ" prefix - sorry for the
confusion I caused here. Just removed it as component.
> Inifinite Block in AMQ212054 after transient DB-error
> -
>
> Key: ARTEMIS-2586
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2586
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.10.1
> Environment: This is Ubuntu 18.04 and Oracle DB, but don't think it's
> that relevant for the issue.
>Reporter: Rico Neubauer
>Priority: Major
> Attachments: 2019-11-28_threaddump_01.txt,
> 2019-12-04_threaddump_01.txt, Message-Counts.png, artemis.xml,
> initial-error.txt, log-extract.txt, writerIndex-Credits.PNG
>
>
> Hi,
> Would like to describe a quite severe situation which was expirienced in a
> long-running test with 2 out of 3 instances/machines.
> We are running Karaf with Artemis 2.10.1.
> After some time (see screenshot), first one, then after a while a 2nd
> instance came to a complete stop.
> Looking into the logs and thread-dumps revealed the following (same for bith
> instances):
> # There was a temporary problem connecting to the DB ({{connection reset by
> peer}}and {{Closed Connection }})
> # This resulted (due to handling on our side) in an
> {{IllegalStateException}}/{{Error during two phase commit}} being thrown back
> to Artemis.
> # After this, there is no messaging possible anymore at all and the
> following log repeats:
> {noformat}
> AMQ212054: Destination address=DLQ is blocked. If the system is configured to
> block make sure you consume messages on this configuration.{noformat}
> (system is not configured to block, see attached config)
> which comes from threads like these, trying to obtain credits for sending:
>
> {noformat}
> "Thread-93 (ActiveMQ-client-global-threads)" Id=2001 in TIMED_WAITING on
> lock=java.util.concurrent.Semaphore$NonfairSync@1f9a57e0
> at sun.misc.Unsafe.park(Native Method)
> at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedNanos(AbstractQueuedSynchronizer.java:1039)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1332)
> at java.util.concurrent.Semaphore.tryAcquire(Semaphore.java:582)
> at
> org.apache.activemq.artemis.core.client.impl.ClientProducerCreditsImpl.actualAcquire(ClientProducerCreditsImpl.java:73)
> at
> org.apache.activemq.artemis.core.client.impl.AbstractProducerCreditsImpl.acquireCredits(AbstractProducerCreditsImpl.java:77)
> at
> org.apache.activemq.artemis.core.client.impl.ClientProducerImpl.sendRegularMessage(ClientProducerImpl.java:301)
> at
> org.apache.activemq.artemis.core.client.impl.ClientProducerImpl.doSend(ClientProducerImpl.java:275)
> at
> org.apache.activemq.artemis.core.client.impl.ClientProducerImpl.send(ClientProducerImpl.java:128)
> at
> org.apache.activemq.artemis.jms.client.ActiveMQMessageProducer.doSendx(ActiveMQMessageProducer.java:485)
> at
> org.apache.activemq.artemis.jms.client.ActiveMQMessageProducer.send(ActiveMQMessageProducer.java:195)
> at
> com.seeburger.engine.jms.MessageReceiverBase.sendToDLQ(MessageReceiverBase.java:571)
> at
> com.seeburger.engine.jms.MessageReceiverBase.handleException(MessageReceiverBase.java:493)
> at
> com.seeburger.engine.jms.MessageReceiverBase.onMessage(MessageReceiverBase.java:387)
> at
> org.apache.activemq.artemis.jms.client.JMSMessageListenerWrapper.onMessage(JMSMessageListenerWrapper.java:110)
> at
> org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:1031)
> at
> org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl.access$400(ClientConsumerImpl.java:50)
> at
> org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:1154)
> at
> org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:42)
> at
> org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:31)
> at
> org.apache.activemq.artemis.utils.actors.ProcessorBase.executePendingTasks(ProcessorBase.java:66)
> at
> org.apache.activemq.artemis.utils.actors.ProcessorBase$$Lambda$431/1769898766.run(Unknown
> Source)
> at
>
[jira] [Updated] (ARTEMIS-2586) Inifinite Block in AMQ212054 after transient DB-error
[
https://issues.apache.org/jira/browse/ARTEMIS-2586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rico Neubauer updated ARTEMIS-2586:
---
Component/s: (was: AMQP)
> Inifinite Block in AMQ212054 after transient DB-error
> -
>
> Key: ARTEMIS-2586
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2586
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.10.1
> Environment: This is Ubuntu 18.04 and Oracle DB, but don't think it's
> that relevant for the issue.
>Reporter: Rico Neubauer
>Priority: Major
> Attachments: 2019-11-28_threaddump_01.txt,
> 2019-12-04_threaddump_01.txt, Message-Counts.png, artemis.xml,
> initial-error.txt, log-extract.txt, writerIndex-Credits.PNG
>
>
> Hi,
> Would like to describe a quite severe situation which was expirienced in a
> long-running test with 2 out of 3 instances/machines.
> We are running Karaf with Artemis 2.10.1.
> After some time (see screenshot), first one, then after a while a 2nd
> instance came to a complete stop.
> Looking into the logs and thread-dumps revealed the following (same for bith
> instances):
> # There was a temporary problem connecting to the DB ({{connection reset by
> peer}}and {{Closed Connection }})
> # This resulted (due to handling on our side) in an
> {{IllegalStateException}}/{{Error during two phase commit}} being thrown back
> to Artemis.
> # After this, there is no messaging possible anymore at all and the
> following log repeats:
> {noformat}
> AMQ212054: Destination address=DLQ is blocked. If the system is configured to
> block make sure you consume messages on this configuration.{noformat}
> (system is not configured to block, see attached config)
> which comes from threads like these, trying to obtain credits for sending:
>
> {noformat}
> "Thread-93 (ActiveMQ-client-global-threads)" Id=2001 in TIMED_WAITING on
> lock=java.util.concurrent.Semaphore$NonfairSync@1f9a57e0
> at sun.misc.Unsafe.park(Native Method)
> at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedNanos(AbstractQueuedSynchronizer.java:1039)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1332)
> at java.util.concurrent.Semaphore.tryAcquire(Semaphore.java:582)
> at
> org.apache.activemq.artemis.core.client.impl.ClientProducerCreditsImpl.actualAcquire(ClientProducerCreditsImpl.java:73)
> at
> org.apache.activemq.artemis.core.client.impl.AbstractProducerCreditsImpl.acquireCredits(AbstractProducerCreditsImpl.java:77)
> at
> org.apache.activemq.artemis.core.client.impl.ClientProducerImpl.sendRegularMessage(ClientProducerImpl.java:301)
> at
> org.apache.activemq.artemis.core.client.impl.ClientProducerImpl.doSend(ClientProducerImpl.java:275)
> at
> org.apache.activemq.artemis.core.client.impl.ClientProducerImpl.send(ClientProducerImpl.java:128)
> at
> org.apache.activemq.artemis.jms.client.ActiveMQMessageProducer.doSendx(ActiveMQMessageProducer.java:485)
> at
> org.apache.activemq.artemis.jms.client.ActiveMQMessageProducer.send(ActiveMQMessageProducer.java:195)
> at
> com.seeburger.engine.jms.MessageReceiverBase.sendToDLQ(MessageReceiverBase.java:571)
> at
> com.seeburger.engine.jms.MessageReceiverBase.handleException(MessageReceiverBase.java:493)
> at
> com.seeburger.engine.jms.MessageReceiverBase.onMessage(MessageReceiverBase.java:387)
> at
> org.apache.activemq.artemis.jms.client.JMSMessageListenerWrapper.onMessage(JMSMessageListenerWrapper.java:110)
> at
> org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:1031)
> at
> org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl.access$400(ClientConsumerImpl.java:50)
> at
> org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:1154)
> at
> org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:42)
> at
> org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:31)
> at
> org.apache.activemq.artemis.utils.actors.ProcessorBase.executePendingTasks(ProcessorBase.java:66)
> at
> org.apache.activemq.artemis.utils.actors.ProcessorBase$$Lambda$431/1769898766.run(Unknown
> Source)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at
> org.apache.activemq.artemis.utils.ActiveMQThreadFactory$1.run(ActiveMQThreadFactory.java:118)
> Locked synchronizers: count = 1
> - java.util.concurrent.ThreadPoolExecutor$Worker@bc49fcf
> {noformat}
> which will never succeed, since the credits seem to no
