[
https://issues.jboss.org/browse/WFLY-4847?page=com.atlassian.jira.plugin....
]
Ville Skyttä commented on WFLY-4847:
------------------------------------
With the dependency in place, connection closed warnings do get logged properly:
{code}
19:53:01,495 WARN [org.hornetq.core.protocol.stomp] (Thread-88) HQ222068: connection
closed org.hornetq.core.protocol.stomp.StompConnection@51881e0
{code}
...and unsupported version connects get a proper error response:
{code}
$ nc localhost 61613
CONNECT
accept-version:2.0
^@
ERROR
message:HQ339002: Stomp versions not supported: 2.0
version:2.0
content-type:text/plain
Supported protocol version are v1.0 v1.1 v1.2
{code}
STOMP logging does not work
---------------------------
Key: WFLY-4847
URL:
https://issues.jboss.org/browse/WFLY-4847
Project: WildFly
Issue Type: Bug
Affects Versions: 9.0.0.CR2
Reporter: Ville Skyttä
Assignee: Jason Greene
STOMP errors do not get logged at all, for example "HQ222068: connection closed
..." on unclean connection close.
Also, apparently due to the same root cause (or at least fixed by the same fix), for
example connecting with an unsupported STOMP version just hangs instead of responding with
the ERROR frame.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)