[jira] [Resolved] (AMQ-5504) activemq should not need nohup to be daemonized

[ https://issues.apache.org/jira/browse/AMQ-5504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Pavlovich resolved AMQ-5504. - Resolution: Not A Problem ActiveMQ does not need nohup to run as a daemon > activemq should not

[jira] [Commented] (AMQ-5504) activemq should not need nohup to be daemonized

[ https://issues.apache.org/jira/browse/AMQ-5504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17244628#comment-17244628 ] Matt Pavlovich commented on AMQ-5504: - ActiveMQ does not need nohup to run as a daemon. Closing this

[jira] [Work started] (AMQ-5504) activemq should not need nohup to be daemonized

[ https://issues.apache.org/jira/browse/AMQ-5504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on AMQ-5504 started by Matt Pavlovich. --- > activemq should not need nohup to be daemonized >

[jira] [Assigned] (AMQ-5504) activemq should not need nohup to be daemonized

[ https://issues.apache.org/jira/browse/AMQ-5504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Pavlovich reassigned AMQ-5504: --- Assignee: Matt Pavlovich > activemq should not need nohup to be daemonized >

[jira] [Commented] (AMQ-5536) Inconsistent Behavior for Duplicate Message Handling

[ https://issues.apache.org/jira/browse/AMQ-5536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17244627#comment-17244627 ] Matt Pavlovich commented on AMQ-5536: - [~rimovm]There have been significant changes in the JDBC layer

[jira] [Assigned] (AMQ-5536) Inconsistent Behavior for Duplicate Message Handling

[ https://issues.apache.org/jira/browse/AMQ-5536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Pavlovich reassigned AMQ-5536: --- Assignee: Matt Pavlovich > Inconsistent Behavior for Duplicate Message Handling >

[jira] [Updated] (AMQ-5536) Inconsistent Behavior for Duplicate Message Handling

[ https://issues.apache.org/jira/browse/AMQ-5536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Pavlovich updated AMQ-5536: Labels: bug close-pending jdbc (was: bug jdbc) > Inconsistent Behavior for Duplicate Message

[jira] [Commented] (AMQ-5569) activemq broker was blocked on log4j call appender

[ https://issues.apache.org/jira/browse/AMQ-5569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17244626#comment-17244626 ] Matt Pavlovich commented on AMQ-5569: - [~anujm] Was the disk space where logging was happening full?

[jira] [Assigned] (AMQ-5569) activemq broker was blocked on log4j call appender

[ https://issues.apache.org/jira/browse/AMQ-5569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Pavlovich reassigned AMQ-5569: --- Assignee: Matt Pavlovich > activemq broker was blocked on log4j call appender >

[jira] [Updated] (AMQ-5569) activemq broker was blocked on log4j call appender

[ https://issues.apache.org/jira/browse/AMQ-5569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Pavlovich updated AMQ-5569: Labels: close-pending (was: ) > activemq broker was blocked on log4j call appender >

[jira] [Updated] (AMQ-5137) make networkConnector decreaseNetworkConsumerPriority="true" the default

[ https://issues.apache.org/jira/browse/AMQ-5137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Pavlovich updated AMQ-5137: Affects Version/s: (was: 5.17.0) 5.15.13 > make networkConnector

[jira] [Updated] (AMQ-5137) make networkConnector decreaseNetworkConsumerPriority="true" the default

[ https://issues.apache.org/jira/browse/AMQ-5137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Pavlovich updated AMQ-5137: Fix Version/s: 5.17.0 > make networkConnector decreaseNetworkConsumerPriority="true" the default >

[jira] [Updated] (AMQ-5130) If a STOMP listener attempts to connect to an OpenWire transport connector the broker dies

[ https://issues.apache.org/jira/browse/AMQ-5130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Pavlovich updated AMQ-5130: Affects Version/s: 5.15.13 > If a STOMP listener attempts to connect to an OpenWire transport

[jira] [Updated] (AMQ-5130) If a STOMP listener attempts to connect to an OpenWire transport connector the broker dies

[ https://issues.apache.org/jira/browse/AMQ-5130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Pavlovich updated AMQ-5130: Fix Version/s: 5.17.0 > If a STOMP listener attempts to connect to an OpenWire transport connector

[jira] [Commented] (AMQ-5130) If a STOMP listener attempts to connect to an OpenWire transport connector the broker dies

[ https://issues.apache.org/jira/browse/AMQ-5130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17244623#comment-17244623 ] Matt Pavlovich commented on AMQ-5130: - Pulling this forward into the 5.17.0 bucket for discussion > If

[jira] [Updated] (AMQ-5130) If a STOMP listener attempts to connect to an OpenWire transport connector the broker dies

[ https://issues.apache.org/jira/browse/AMQ-5130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Pavlovich updated AMQ-5130: Affects Version/s: (was: 5.9.0) > If a STOMP listener attempts to connect to an OpenWire

[jira] [Updated] (AMQ-5137) make networkConnector decreaseNetworkConsumerPriority="true" the default

[ https://issues.apache.org/jira/browse/AMQ-5137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Pavlovich updated AMQ-5137: Affects Version/s: (was: 5.9.0) 5.17.0 > make networkConnector

[jira] [Assigned] (AMQ-5137) make networkConnector decreaseNetworkConsumerPriority="true" the default

[ https://issues.apache.org/jira/browse/AMQ-5137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Pavlovich reassigned AMQ-5137: --- Assignee: Matt Pavlovich > make networkConnector decreaseNetworkConsumerPriority="true" the

[jira] [Commented] (AMQ-5137) make networkConnector decreaseNetworkConsumerPriority="true" the default

[ https://issues.apache.org/jira/browse/AMQ-5137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17244621#comment-17244621 ] Matt Pavlovich commented on AMQ-5137: - I agree w/ Gary and Tim and am also +1 changing the default.

[jira] [Comment Edited] (AMQ-5151) Incorrect authorization on virtual destination (wildcard)

[ https://issues.apache.org/jira/browse/AMQ-5151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17244620#comment-17244620 ] Matt Pavlovich edited comment on AMQ-5151 at 12/6/20, 2:22 AM: --- [~apauzies]

[jira] [Work started] (AMQ-5151) Incorrect authorization on virtual destination (wildcard)

[ https://issues.apache.org/jira/browse/AMQ-5151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on AMQ-5151 started by Matt Pavlovich. --- > Incorrect authorization on virtual destination (wildcard) >

[jira] [Commented] (AMQ-5151) Incorrect authorization on virtual destination (wildcard)

[ https://issues.apache.org/jira/browse/AMQ-5151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17244620#comment-17244620 ] Matt Pavlovich commented on AMQ-5151: - [~apauzies]Have you tried this with more recent versions of

[jira] [Assigned] (AMQ-5151) Incorrect authorization on virtual destination (wildcard)

[ https://issues.apache.org/jira/browse/AMQ-5151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Pavlovich reassigned AMQ-5151: --- Assignee: Matt Pavlovich > Incorrect authorization on virtual destination (wildcard) >

[jira] [Updated] (AMQ-5157) Non persistent Messages not getting expired

[ https://issues.apache.org/jira/browse/AMQ-5157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Pavlovich updated AMQ-5157: Labels: close-pending (was: ) > Non persistent Messages not getting expired >

[jira] [Assigned] (AMQ-5157) Non persistent Messages not getting expired

[ https://issues.apache.org/jira/browse/AMQ-5157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Pavlovich reassigned AMQ-5157: --- Assignee: Matt Pavlovich > Non persistent Messages not getting expired >

[jira] [Commented] (AMQ-5157) Non persistent Messages not getting expired

[ https://issues.apache.org/jira/browse/AMQ-5157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17244619#comment-17244619 ] Matt Pavlovich commented on AMQ-5157: - Additional destinationPolicy setting for topics has been added:

[jira] [Commented] (AMQ-5185) Duplicate messages occur for MQTT cleanSession=false client with network of brokers

[ https://issues.apache.org/jira/browse/AMQ-5185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17244618#comment-17244618 ] Matt Pavlovich commented on AMQ-5185: - [~pcarman]have you validated the ability to solve your issue

[jira] [Updated] (AMQ-5185) Duplicate messages occur for MQTT cleanSession=false client with network of brokers

[ https://issues.apache.org/jira/browse/AMQ-5185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Pavlovich updated AMQ-5185: Labels: close-pending mqtt (was: mqtt) > Duplicate messages occur for MQTT cleanSession=false

[jira] [Assigned] (AMQ-5185) Duplicate messages occur for MQTT cleanSession=false client with network of brokers

[ https://issues.apache.org/jira/browse/AMQ-5185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Pavlovich reassigned AMQ-5185: --- Assignee: Matt Pavlovich > Duplicate messages occur for MQTT cleanSession=false client with

[jira] [Updated] (AMQ-5196) Corrupted Kahadb store after failover: "Could not load journal record. Invalid location"

[ https://issues.apache.org/jira/browse/AMQ-5196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Pavlovich updated AMQ-5196: Labels: close-pending (was: ) > Corrupted Kahadb store after failover: "Could not load journal

[jira] [Commented] (AMQ-5196) Corrupted Kahadb store after failover: "Could not load journal record. Invalid location"

[ https://issues.apache.org/jira/browse/AMQ-5196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17244617#comment-17244617 ] Matt Pavlovich commented on AMQ-5196: - [~windeyu] What was the shared filesystem used in this? I

[jira] [Assigned] (AMQ-5196) Corrupted Kahadb store after failover: "Could not load journal record. Invalid location"

[ https://issues.apache.org/jira/browse/AMQ-5196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Pavlovich reassigned AMQ-5196: --- Assignee: Matt Pavlovich > Corrupted Kahadb store after failover: "Could not load journal

[jira] [Work logged] (ARTEMIS-3021) OOM due to wrong CORE message memory estimation

[ https://issues.apache.org/jira/browse/ARTEMIS-3021?focusedWorklogId=520580=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-520580 ] ASF GitHub Bot logged work on ARTEMIS-3021: --- Author: ASF GitHub Bot

[jira] [Work logged] (ARTEMIS-3021) OOM due to wrong CORE message memory estimation

[ https://issues.apache.org/jira/browse/ARTEMIS-3021?focusedWorklogId=520579=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-520579 ] ASF GitHub Bot logged work on ARTEMIS-3021: --- Author: ASF GitHub Bot

[jira] [Closed] (AMQ-8098) BlackOut

[ https://issues.apache.org/jira/browse/AMQ-8098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy A. Bish closed AMQ-8098. Resolution: Invalid > BlackOut > > > Key: AMQ-8098 > URL:

[jira] [Created] (ARTEMIS-3021) OOM due to wrong CORE message memory estimation

Francesco Nigro created ARTEMIS-3021: Summary: OOM due to wrong CORE message memory estimation Key: ARTEMIS-3021 URL: https://issues.apache.org/jira/browse/ARTEMIS-3021 Project: ActiveMQ Artemis

[jira] [Created] (ARTEMIS-3020) Allow choosing table columns at the "Browse Queues" listing in the web console

João Santos created ARTEMIS-3020: Summary: Allow choosing table columns at the "Browse Queues" listing in the web console Key: ARTEMIS-3020 URL: https://issues.apache.org/jira/browse/ARTEMIS-3020

[jira] [Work logged] (ARTEMIS-1883) Address name of ::test.topic incorrectly interpreted as FQQN

[ https://issues.apache.org/jira/browse/ARTEMIS-1883?focusedWorklogId=520484=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-520484 ] ASF GitHub Bot logged work on ARTEMIS-1883: --- Author: ASF GitHub Bot

[jira] [Work logged] (ARTEMIS-1883) Address name of ::test.topic incorrectly interpreted as FQQN

[ https://issues.apache.org/jira/browse/ARTEMIS-1883?focusedWorklogId=520483=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-520483 ] ASF GitHub Bot logged work on ARTEMIS-1883: --- Author: ASF GitHub Bot

[jira] [Work logged] (ARTEMIS-1883) Address name of ::test.topic incorrectly interpreted as FQQN

[ https://issues.apache.org/jira/browse/ARTEMIS-1883?focusedWorklogId=520482=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-520482 ] ASF GitHub Bot logged work on ARTEMIS-1883: --- Author: ASF GitHub Bot