[
https://issues.jboss.org/browse/WFLY-6420?page=com.atlassian.jira.plugin....
]
Tomohisa igarashi commented on WFLY-6420:
-----------------------------------------
OK you are right... I'm sorry for the confusion, client API doesn't matter. If
TransportConstants.HTTP_UPGRADE_ENDPOINT_PROP_NAME is not set then delay occurs. It just
reproduced if I commented out that property setting in your testcases.
30secs delay on consumer.receive() in spite of shorter timeout
--------------------------------------------------------------
Key: WFLY-6420
URL:
https://issues.jboss.org/browse/WFLY-6420
Project: WildFly
Issue Type: Bug
Components: JMS
Affects Versions: 10.0.0.Final
Reporter: Tomohisa igarashi
Assignee: Jeff Mesnil
Fix For: 10.1.0.Final
Attachments: artemis-hornetq-client.tgz, artemis-hornetq-client.tgz,
artemis-hornetq-client.tgz
consumer.receive() is blocked 30secs even if shorter timeout is specified. Attached a
maven project including testcases.
The ArtemisStandaloneTest do same against embedded server, but this in contrast works
fine. So the issue seems to happen only on WildFly via http upgrade connection.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)