[
https://issues.apache.org/jira/browse/ARTEMIS-1186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030969#comment-16030969
]
ASF GitHub Bot commented on ARTEMIS-1186:
-----------------------------------------
GitHub user TomasHofman opened a pull request:
https://github.com/apache/activemq-artemis/pull/1309
ARTEMIS-1186 Consumer.receive hangs if http acceptor with non-zero ba…
…tch-delay is configured
https://issues.apache.org/jira/browse/ARTEMIS-1186
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/TomasHofman/activemq-artemis JBEAP-6570-1.x
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq-artemis/pull/1309.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1309
----
commit 9085b6d617d9f3445a24b5a19ecf4e27519995a8
Author: Tomas Hofman <[email protected]>
Date: 2017-05-29T10:00:32Z
ARTEMIS-1186 Consumer.receive hangs if http acceptor with non-zero
batch-delay is configured
----
> Consumer.receive hangs if http acceptor with non-zero batch-delay is
> configured
> -------------------------------------------------------------------------------
>
> Key: ARTEMIS-1186
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1186
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Tomas Hofman
>
> Test scenario:
> # Call consumer.receive(1000) on empty queue.
> # Check whether receive call is unblocked after the 1 second.
> Issue: The receive call is not unblocked.
> I hit the issue which was initially reported in JBEAP-6443. I found out that
> the issue is somehow related to http connectors/acceptors and {{batch-delay}}
> parameter. I am able to reproduce it only if a client connects via
> http-connector with non-zero batch-delay. When I tried classic
> {{remote-connector}}, everything worked with both zero and non-zero
> {{batch-delay}}.
> I am able to reproduce the issue with both Artemis 1.1 (EAP 7.0.3) and
> Artemis 1.4.
> From the thread dump, you can see where the client hangs.
> {code}
> Stack trace of thread: Thread[Thread-10,5,main]
> ---java.lang.Object.wait(Native Method)
> ---org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl.receive(ClientConsumerImpl.java:258)
> ---org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl.receive(ClientConsumerImpl.java:391)
> ---org.apache.activemq.artemis.jms.client.ActiveMQMessageConsumer.getMessage(ActiveMQMessageConsumer.java:198)
> ---org.apache.activemq.artemis.jms.client.ActiveMQMessageConsumer.receive(ActiveMQMessageConsumer.java:122)
> ---org.jboss.qa.hornetq.apps.clients.Receiver11.receiveMessage(Receiver11.java:140)
> ---org.jboss.qa.hornetq.apps.clients.ReceiverAutoAck.run(ReceiverAutoAck.java:75)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
