[
https://issues.apache.org/jira/browse/ARTEMIS-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16512856#comment-16512856
]
ASF GitHub Bot commented on ARTEMIS-1935:
-----------------------------------------
GitHub user graben opened a pull request:
https://github.com/apache/activemq-artemis/pull/2141
ARTEMIS-1935: Close of connection closes all open sessions
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/graben/activemq-artemis master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq-artemis/pull/2141.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 #2141
----
commit 1cdf64da0449195c47ab252311da5998bceec2aa
Author: Benjamin Graf <benjamin.graf@...>
Date: 2018-06-14T18:34:04Z
ARTEMIS-1935: Close of connection closes all open sessions
----
> Openwire connection logs failures on close for open sessions
> ------------------------------------------------------------
>
> Key: ARTEMIS-1935
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1935
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Benjamin Graf
> Priority: Major
>
> Openwire implementation acts different to core protocoll and ActiveMQ
> OpenWire implementation. Actually only internal sessions are automatically
> closed with connection. This causes the same urgly warning messages as
> resolved in ARTEMIS-1768. According to the JavaDoc of ActiveMQConnection it
> should close all open sessions not only internal ones. This would avoid the
> warning log messages at all.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
