[
https://issues.apache.org/jira/browse/ARTEMIS-2556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mario Mahovlić updated ARTEMIS-2556:
------------------------------------
Description:
We run Artemis embedded on our Spring service and occasionally get this issue
where all our producer threads become blocked so no messages can be produced to
queue (happened 3 times in 2 weeks). We produce both regular and large messages
to the queue. All we get during this time from artemis are timeout exceptions
on our producer client side:
{noformat}
nested exception is javax.jms.JMSException: AMQ219014: Timed out after waiting
30,000 ms for response when sending packet 71{noformat}
We took a thread dump of the service while issue was in effect (attached).
>From what we can see Thread t@11854 and thread Thread t@202 seem to be
>permanently locked, all other BLOCKED threads are blocked on session creation:
{noformat}
org.apache.activemq.artemis.jms.client.ActiveMQConnection.createSession(ActiveMQConnection.java:234){noformat}
We are in the process of analyzing the issue further but wanted to report this
as soon as possible, so someone else can also take a look. If you need any
additional info, we will provide it.
was:
We run Artemis embedded on our Spring service and occasionally get this issue
where all our producer threads become blocked so no messages can be produced to
queue (happened 3 times in 2 weeks). We produce both regular and large messages
to the queue. All we get are during this time from artemis are timeout
exceptions:
{noformat}
nested exception is javax.jms.JMSException: AMQ219014: Timed out after waiting
30,000 ms for response when sending packet 71{noformat}
We took a thread dump of the service while issue was in effect (attached).
>From what we can see Thread t@11854 and thread Thread t@202 seem to be
>permanently locked, all other BLOCKED threads are blocked on session creation:
{noformat}
org.apache.activemq.artemis.jms.client.ActiveMQConnection.createSession(ActiveMQConnection.java:234){noformat}
We are in the process of analyzing the issue further but wanted to report this
as soon as possible, so someone else can also take a look. If you need any
additional info, we will provide it.
> Thread deadlock during message processing
> -----------------------------------------
>
> Key: ARTEMIS-2556
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2556
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 2.6.4
> Environment: Service is running within a docker container and folder
> containing the journal is mapped to the host machine.
> Metrics for the node on which service was running show no disk I/O issues at
> that time.
> Artemis version: 2.6.4, Spring boot version: 2.1.5.RELEASE
> Relevant artemis settings (rest of the settings are default):
> {noformat}
> durable: true
> max-size-bytes : 1GB
> address-full-policy: FAIL
> journal-sync-non-transactional : false
> journal-sync-transactional: false{noformat}
> Reporter: Mario Mahovlić
> Priority: Critical
> Attachments: threaddump
>
>
> We run Artemis embedded on our Spring service and occasionally get this issue
> where all our producer threads become blocked so no messages can be produced
> to queue (happened 3 times in 2 weeks). We produce both regular and large
> messages to the queue. All we get during this time from artemis are timeout
> exceptions on our producer client side:
> {noformat}
> nested exception is javax.jms.JMSException: AMQ219014: Timed out after
> waiting 30,000 ms for response when sending packet 71{noformat}
> We took a thread dump of the service while issue was in effect (attached).
> From what we can see Thread t@11854 and thread Thread t@202 seem to be
> permanently locked, all other BLOCKED threads are blocked on session creation:
> {noformat}
> org.apache.activemq.artemis.jms.client.ActiveMQConnection.createSession(ActiveMQConnection.java:234){noformat}
> We are in the process of analyzing the issue further but wanted to report
> this as soon as possible, so someone else can also take a look. If you need
> any additional info, we will provide it.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
