[jira] [Resolved] (ARTEMIS-835) Quick restart of broker will leave tmp dir dirty

[ https://issues.apache.org/jira/browse/ARTEMIS-835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Howard Gao resolved ARTEMIS-835. Resolution: Fixed > Quick restart of broker will leave tmp dir dirty >

[jira] [Commented] (ARTEMIS-550) Add support for virtual topic consumers

[ https://issues.apache.org/jira/browse/ARTEMIS-550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15631034#comment-15631034 ] ASF GitHub Bot commented on ARTEMIS-550: Github user clebertsuconic commented on

[jira] [Commented] (ARTEMIS-833) maxHops defaults to 0 when creating artemis cluster configuration through cli

[ https://issues.apache.org/jira/browse/ARTEMIS-833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15630829#comment-15630829 ] ASF subversion and git services commented on ARTEMIS-833: - Commit

[jira] [Commented] (ARTEMIS-786) Store user's password in hash form by default

[ https://issues.apache.org/jira/browse/ARTEMIS-786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15630830#comment-15630830 ] ASF subversion and git services commented on ARTEMIS-786: - Commit

[jira] [Commented] (AMQ-6482) Possible thread leak ?

[ https://issues.apache.org/jira/browse/AMQ-6482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15630685#comment-15630685 ] Maxence Dunnewind commented on AMQ-6482: New websocket connections are definitively

[jira] [Commented] (ARTEMIS-550) Add support for virtual topic consumers

[ https://issues.apache.org/jira/browse/ARTEMIS-550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15630416#comment-15630416 ] ASF GitHub Bot commented on ARTEMIS-550: Github user mattrpav commented on the is

[jira] [Closed] (ARTEMIS-786) Store user's password in hash form by default

[ https://issues.apache.org/jira/browse/ARTEMIS-786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-786. --- Resolution: Fixed > Store user's password in hash form by default > -

[jira] [Commented] (ARTEMIS-786) Store user's password in hash form by default

[ https://issues.apache.org/jira/browse/ARTEMIS-786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15630237#comment-15630237 ] ASF subversion and git services commented on ARTEMIS-786: - Commit

[jira] [Commented] (ARTEMIS-786) Store user's password in hash form by default

[ https://issues.apache.org/jira/browse/ARTEMIS-786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15630238#comment-15630238 ] ASF GitHub Bot commented on ARTEMIS-786: Github user asfgit closed the pull reque

[jira] [Commented] (ARTEMIS-786) Store user's password in hash form by default

[ https://issues.apache.org/jira/browse/ARTEMIS-786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15630236#comment-15630236 ] ASF subversion and git services commented on ARTEMIS-786: - Commit

[jira] [Commented] (AMQ-6482) Possible thread leak ?

[ https://issues.apache.org/jira/browse/AMQ-6482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15630112#comment-15630112 ] Christopher L. Shannon commented on AMQ-6482: - Are new websocket connections bei

[jira] [Assigned] (ARTEMIS-268) messages appear to remain on the queue after being sent pre-settled to a consumer

[ https://issues.apache.org/jira/browse/ARTEMIS-268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish reassigned ARTEMIS-268: Assignee: Timothy Bish > messages appear to remain on the queue after being sent pre-settl

[jira] [Closed] (ARTEMIS-268) messages appear to remain on the queue after being sent pre-settled to a consumer

[ https://issues.apache.org/jira/browse/ARTEMIS-268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed ARTEMIS-268. Resolution: Fixed > messages appear to remain on the queue after being sent pre-settled to a > con

[jira] [Commented] (ARTEMIS-814) Support outgoing connections for AMQP

[ https://issues.apache.org/jira/browse/ARTEMIS-814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15629971#comment-15629971 ] ASF GitHub Bot commented on ARTEMIS-814: Github user asfgit closed the pull reque

[jira] [Commented] (ARTEMIS-814) Support outgoing connections for AMQP

[ https://issues.apache.org/jira/browse/ARTEMIS-814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15629969#comment-15629969 ] ASF subversion and git services commented on ARTEMIS-814: - Commit

[jira] [Commented] (ARTEMIS-814) Support outgoing connections for AMQP

[ https://issues.apache.org/jira/browse/ARTEMIS-814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15629970#comment-15629970 ] ASF subversion and git services commented on ARTEMIS-814: - Commit

[jira] [Closed] (ARTEMIS-832) Openwire Protocol Manager did not implement OperationContext (sync) properly

[ https://issues.apache.org/jira/browse/ARTEMIS-832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-832. --- Resolution: Fixed > Openwire Protocol Manager did not implement OperationContext (sync) prope

[jira] [Commented] (ARTEMIS-832) Openwire Protocol Manager did not implement OperationContext (sync) properly

[ https://issues.apache.org/jira/browse/ARTEMIS-832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15629902#comment-15629902 ] ASF GitHub Bot commented on ARTEMIS-832: Github user asfgit closed the pull reque

[jira] [Commented] (ARTEMIS-832) Openwire Protocol Manager did not implement OperationContext (sync) properly

[ https://issues.apache.org/jira/browse/ARTEMIS-832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15629900#comment-15629900 ] ASF subversion and git services commented on ARTEMIS-832: - Commit

[jira] [Commented] (ARTEMIS-832) Openwire Protocol Manager did not implement OperationContext (sync) properly

[ https://issues.apache.org/jira/browse/ARTEMIS-832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15629899#comment-15629899 ] ASF subversion and git services commented on ARTEMIS-832: - Commit

[jira] [Commented] (ARTEMIS-833) maxHops defaults to 0 when creating artemis cluster configuration through cli

[ https://issues.apache.org/jira/browse/ARTEMIS-833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15629894#comment-15629894 ] ASF subversion and git services commented on ARTEMIS-833: - Commit

[jira] [Commented] (ARTEMIS-833) maxHops defaults to 0 when creating artemis cluster configuration through cli

[ https://issues.apache.org/jira/browse/ARTEMIS-833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15629895#comment-15629895 ] ASF GitHub Bot commented on ARTEMIS-833: Github user asfgit closed the pull reque

[jira] [Commented] (ARTEMIS-833) maxHops defaults to 0 when creating artemis cluster configuration through cli

[ https://issues.apache.org/jira/browse/ARTEMIS-833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15629892#comment-15629892 ] ASF subversion and git services commented on ARTEMIS-833: - Commit

[jira] [Commented] (ARTEMIS-268) messages appear to remain on the queue after being sent pre-settled to a consumer

[ https://issues.apache.org/jira/browse/ARTEMIS-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15629885#comment-15629885 ] ASF subversion and git services commented on ARTEMIS-268: - Commit

[jira] [Commented] (ARTEMIS-835) Quick restart of broker will leave tmp dir dirty

[ https://issues.apache.org/jira/browse/ARTEMIS-835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15629883#comment-15629883 ] ASF GitHub Bot commented on ARTEMIS-835: Github user asfgit closed the pull reque

[jira] [Commented] (ARTEMIS-268) messages appear to remain on the queue after being sent pre-settled to a consumer

[ https://issues.apache.org/jira/browse/ARTEMIS-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15629886#comment-15629886 ] ASF GitHub Bot commented on ARTEMIS-268: Github user asfgit closed the pull reque

[jira] [Commented] (ARTEMIS-835) Quick restart of broker will leave tmp dir dirty

[ https://issues.apache.org/jira/browse/ARTEMIS-835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15629882#comment-15629882 ] ASF subversion and git services commented on ARTEMIS-835: - Commit

[jira] [Commented] (ARTEMIS-835) Quick restart of broker will leave tmp dir dirty

[ https://issues.apache.org/jira/browse/ARTEMIS-835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15629881#comment-15629881 ] ASF subversion and git services commented on ARTEMIS-835: - Commit

[jira] [Commented] (ARTEMIS-786) Store user's password in hash form by default

[ https://issues.apache.org/jira/browse/ARTEMIS-786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15629874#comment-15629874 ] ASF GitHub Bot commented on ARTEMIS-786: Github user jbertram commented on a diff

[jira] [Resolved] (AMQ-6495) Boolean state flags in Failover transport should be volatile

[ https://issues.apache.org/jira/browse/AMQ-6495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-6495. --- Resolution: Fixed > Boolean state flags in Failover transport should be volatile > -

[jira] [Commented] (AMQ-6496) levelDB log files fill up disk on 5.14.0 & 5.14.1 releases

[ https://issues.apache.org/jira/browse/AMQ-6496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15629657#comment-15629657 ] Patrick Peng commented on AMQ-6496: --- More information for this JIRA: I've verified all mes

[jira] [Created] (AMQ-6496) levelDB log files fill up disk on 5.14.0 & 5.14.1 releases

Patrick Peng created AMQ-6496: - Summary: levelDB log files fill up disk on 5.14.0 & 5.14.1 releases Key: AMQ-6496 URL: https://issues.apache.org/jira/browse/AMQ-6496 Project: ActiveMQ Issue Type:

[jira] [Commented] (AMQ-6495) Boolean state flags in Failover transport should be volatile

[ https://issues.apache.org/jira/browse/AMQ-6495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15629595#comment-15629595 ] ASF subversion and git services commented on AMQ-6495: -- Commit ba1eab20

[jira] [Commented] (AMQ-6495) Boolean state flags in Failover transport should be volatile

[ https://issues.apache.org/jira/browse/AMQ-6495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15629591#comment-15629591 ] ASF subversion and git services commented on AMQ-6495: -- Commit 629ee285

[jira] [Updated] (AMQ-6495) Started boolean flag in Failover transport should be volatile

[ https://issues.apache.org/jira/browse/AMQ-6495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQ-6495: -- Description: The Failover transport reconnect task looks at the started / disposed / shuttingDown flags to

[jira] [Updated] (AMQ-6495) Boolean state flags in Failover transport should be volatile

[ https://issues.apache.org/jira/browse/AMQ-6495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQ-6495: -- Summary: Boolean state flags in Failover transport should be volatile (was: Started boolean flag in Failo

[jira] [Created] (AMQ-6495) Started boolean flag in Failover transport should be volatile

Timothy Bish created AMQ-6495: - Summary: Started boolean flag in Failover transport should be volatile Key: AMQ-6495 URL: https://issues.apache.org/jira/browse/AMQ-6495 Project: ActiveMQ Issue T

[jira] [Commented] (AMQ-6474) Memory leak

[ https://issues.apache.org/jira/browse/AMQ-6474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15629546#comment-15629546 ] ASF subversion and git services commented on AMQ-6474: -- Commit 3642ab1c

[jira] [Resolved] (AMQ-6474) Memory leak

[ https://issues.apache.org/jira/browse/AMQ-6474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-6474. --- Resolution: Fixed Fix Version/s: (was: 5.11.4) 5.14.2 5.

[jira] [Commented] (AMQ-6474) Memory leak

[ https://issues.apache.org/jira/browse/AMQ-6474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15629541#comment-15629541 ] ASF subversion and git services commented on AMQ-6474: -- Commit d1f42bd0

[jira] [Commented] (AMQ-6494) Exceptions and timeouts during shutdown of connectors

[ https://issues.apache.org/jira/browse/AMQ-6494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15629414#comment-15629414 ] Hadrian Zbarcea commented on AMQ-6494: -- This issue is visible in tests such as Destinat

[jira] [Assigned] (AMQ-6494) Exceptions and timeouts during shutdown of connectors

[ https://issues.apache.org/jira/browse/AMQ-6494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hadrian Zbarcea reassigned AMQ-6494: Assignee: Hadrian Zbarcea > Exceptions and timeouts during shutdown of connectors > -

[jira] [Commented] (ARTEMIS-833) maxHops defaults to 0 when creating artemis cluster configuration through cli

[ https://issues.apache.org/jira/browse/ARTEMIS-833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15629267#comment-15629267 ] ASF GitHub Bot commented on ARTEMIS-833: Github user clebertsuconic commented on

[jira] [Commented] (AMQ-6494) Exceptions and timeouts during shutdown of connectors

[ https://issues.apache.org/jira/browse/AMQ-6494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15629210#comment-15629210 ] ASF GitHub Bot commented on AMQ-6494: - GitHub user hzbarcea opened a pull request:

[jira] [Created] (AMQ-6494) Exceptions and timeouts during shutdown of connectors

Hadrian Zbarcea created AMQ-6494: Summary: Exceptions and timeouts during shutdown of connectors Key: AMQ-6494 URL: https://issues.apache.org/jira/browse/AMQ-6494 Project: ActiveMQ Issue Type

[jira] [Commented] (ARTEMIS-835) Quick restart of broker will leave tmp dir dirty

[ https://issues.apache.org/jira/browse/ARTEMIS-835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15628964#comment-15628964 ] ASF GitHub Bot commented on ARTEMIS-835: GitHub user gaohoward opened a pull requ

[jira] [Updated] (ARTEMIS-835) Quick restart of broker will leave tmp dir dirty

[ https://issues.apache.org/jira/browse/ARTEMIS-835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Howard Gao updated ARTEMIS-835: --- Affects Version/s: 1.4.0 Fix Version/s: 1.5.0 Component/s: Broker > Quick restart o

[jira] [Created] (ARTEMIS-835) Quick restart of broker will leave tmp dir dirty

Howard Gao created ARTEMIS-835: -- Summary: Quick restart of broker will leave tmp dir dirty Key: ARTEMIS-835 URL: https://issues.apache.org/jira/browse/ARTEMIS-835 Project: ActiveMQ Artemis Issue

[jira] [Created] (ARTEMIS-834) Management over AMQP throws exception

Ulf Lilleengen created ARTEMIS-834: -- Summary: Management over AMQP throws exception Key: ARTEMIS-834 URL: https://issues.apache.org/jira/browse/ARTEMIS-834 Project: ActiveMQ Artemis Issue Ty

[jira] [Commented] (ARTEMIS-833) maxHops defaults to 0 when creating artemis cluster configuration through cli

[ https://issues.apache.org/jira/browse/ARTEMIS-833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15628252#comment-15628252 ] Tom Ross commented on ARTEMIS-833: -- Sent PR https://github.com/apache/activemq-artemis/

[jira] [Commented] (ARTEMIS-833) maxHops defaults to 0 when creating artemis cluster configuration through cli

[ https://issues.apache.org/jira/browse/ARTEMIS-833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15628246#comment-15628246 ] ASF GitHub Bot commented on ARTEMIS-833: GitHub user TomRoss opened a pull reques

[jira] [Created] (ARTEMIS-833) maxHops defaults to 0 when creating artemis cluster configuration through cli

Tom Ross created ARTEMIS-833: Summary: maxHops defaults to 0 when creating artemis cluster configuration through cli Key: ARTEMIS-833 URL: https://issues.apache.org/jira/browse/ARTEMIS-833 Project: Activ