[
https://issues.apache.org/jira/browse/AMQ-9819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18045918#comment-18045918
]
ASF subversion and git services commented on AMQ-9819:
------------------------------------------------------
Commit 009b4f3cbb1469389497ab6ffe2df68ce897dd2c in activemq's branch
refs/heads/activemq-5.19.x from Jean-Louis Monteiro
[ https://gitbox.apache.org/repos/asf?p=activemq.git;h=009b4f3cbb ]
[AMQ-9819]: harden #testConsumeAsyncTimeout() so it does not rely on a specific
order of the 2 async requests made
(cherry picked from commit a53f05015b01b4572ad1b6a8f0a6e62fb8b18785)
> org.apache.activemq.web.RestTest randomly failing
> -------------------------------------------------
>
> Key: AMQ-9819
> URL: https://issues.apache.org/jira/browse/AMQ-9819
> Project: ActiveMQ
> Issue Type: Bug
> Reporter: Jean-Louis Monteiro
> Assignee: Christopher L. Shannon
> Priority: Major
> Fix For: 6.3.0, 5.19.2, 6.2.1
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> #testConsumeAsyncTimeout() relies on 2 async calls issued to the Jetty server
> to make sure the first one get through and times out producing a 204 and the
> second gets rejected with 500 because there is already an active consumer.
>
> Unfortunately, when we issue 2 async calls, there is no guarantee on the
> server side that the MessageServlet instance will treat the first request
> first registering its consumer to the set.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
