[jira] [Updated] (AMQ-7388) Upgrade to Jetty 9.4.27.v20200227

[ https://issues.apache.org/jira/browse/AMQ-7388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated AMQ-7388: -- Summary: Upgrade to Jetty 9.4.27.v20200227 (was: Upgrade to Jetty 9.4.26.v20200117) >

[jira] [Updated] (AMQ-7428) How to send same group of messages to one consumer thread

[ https://issues.apache.org/jira/browse/AMQ-7428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bala Konakalla updated AMQ-7428: Issue Type: New Feature (was: Bug) > How to send same group of messages to one consumer thread >

[jira] [Commented] (AMQ-7424) NPE under very high database load

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

[jira] [Resolved] (AMQ-7424) NPE under very high database load

[ https://issues.apache.org/jira/browse/AMQ-7424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved AMQ-7424. --- Resolution: Fixed > NPE under very high database load >

[jira] [Commented] (AMQ-7424) NPE under very high database load

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

[jira] [Commented] (AMQ-7424) NPE under very high database load

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

[jira] [Work logged] (AMQ-7424) NPE under very high database load

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

[jira] [Commented] (AMQ-7424) NPE under very high database load

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

[jira] [Commented] (AMQ-7131) ActiveMQ JMS pool has no borrow timeout causing starvation

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

[jira] [Resolved] (AMQ-7131) ActiveMQ JMS pool has no borrow timeout causing starvation

[ https://issues.apache.org/jira/browse/AMQ-7131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved AMQ-7131. --- Resolution: Fixed > ActiveMQ JMS pool has no borrow timeout causing starvation >

[jira] [Commented] (AMQ-7131) ActiveMQ JMS pool has no borrow timeout causing starvation

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

[jira] [Commented] (AMQ-7131) ActiveMQ JMS pool has no borrow timeout causing starvation

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

[jira] [Work logged] (AMQ-7131) ActiveMQ JMS pool has no borrow timeout causing starvation

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

[jira] [Updated] (AMQ-7059) Stale connection hanging at broker during consumer crash

[ https://issues.apache.org/jira/browse/AMQ-7059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated AMQ-7059: -- Fix Version/s: (was: 5.15.12) (was: 5.16.0)

[jira] [Commented] (AMQ-7131) ActiveMQ JMS pool has no borrow timeout causing starvation

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

[jira] [Commented] (AMQ-7368) Performance issue on PostgreSQL when we have lot of pending messages

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

[jira] [Resolved] (AMQ-7368) Performance issue on PostgreSQL when we have lot of pending messages

[ https://issues.apache.org/jira/browse/AMQ-7368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved AMQ-7368. --- Resolution: Fixed > Performance issue on PostgreSQL when we have lot of pending

[jira] [Commented] (AMQ-7368) Performance issue on PostgreSQL when we have lot of pending messages

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

[jira] [Commented] (AMQ-7368) Performance issue on PostgreSQL when we have lot of pending messages

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

[jira] [Work logged] (AMQ-7368) Performance issue on PostgreSQL when we have lot of pending messages

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

[jira] [Commented] (AMQ-7368) Performance issue on PostgreSQL when we have lot of pending messages

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

[jira] [Created] (AMQ-7428) How to send same group of messages to one consumer thread

Bala Konakalla created AMQ-7428: --- Summary: How to send same group of messages to one consumer thread Key: AMQ-7428 URL: https://issues.apache.org/jira/browse/AMQ-7428 Project: ActiveMQ Issue

[jira] [Resolved] (AMQ-7418) "queuePrefetch" policy doesn't seem to be working properly

[ https://issues.apache.org/jira/browse/AMQ-7418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved AMQ-7418. --- Resolution: Not A Problem It's the "normal" behavior as you are using group. If you

[jira] [Updated] (AMQ-7427) Durable subscriber

[ https://issues.apache.org/jira/browse/AMQ-7427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Kim updated AMQ-7427: - Description: I am using REST protocol to create a durable consumer.  And according to the online help,  a

[jira] [Created] (AMQ-7427) Durable subscriber

Timothy Kim created AMQ-7427: Summary: Durable subscriber Key: AMQ-7427 URL: https://issues.apache.org/jira/browse/AMQ-7427 Project: ActiveMQ Issue Type: Bug Affects Versions: 5.14.0

[jira] [Commented] (ARTEMIS-2637) Resilience around UDP Discovery

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

[jira] [Commented] (ARTEMIS-2637) Resilience around UDP Discovery

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

[jira] [Work logged] (ARTEMIS-2637) Resilience around UDP Discovery

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

[jira] [Work logged] (ARTEMIS-2637) Resilience around UDP Discovery

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

[jira] [Commented] (ARTEMIS-2637) Resilience around UDP Discovery

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

[jira] [Work logged] (ARTEMIS-2637) Resilience around UDP Discovery

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

[jira] [Resolved] (AMQ-3189) Postgresql with spring embedded activeMQ has "table already created" exception

[ https://issues.apache.org/jira/browse/AMQ-3189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved AMQ-3189. --- Fix Version/s: (was: 5.15.12) (was: 5.16.0)

[jira] [Resolved] (AMQ-7178) Table Creation Postgres ActiveMQ

[ https://issues.apache.org/jira/browse/AMQ-7178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved AMQ-7178. --- Fix Version/s: (was: 5.15.12) (was: 5.16.0)

[jira] [Work logged] (ARTEMIS-2637) Resilience around UDP Discovery

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

[jira] [Work logged] (ARTEMIS-2637) Resilience around UDP Discovery

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

[jira] [Work logged] (ARTEMIS-2637) Resilience around UDP Discovery

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

[jira] [Work logged] (ARTEMIS-2637) Resilience around UDP Discovery

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

[jira] [Created] (ARTEMIS-2637) Resilience around UDP Discovery

Clebert Suconic created ARTEMIS-2637: Summary: Resilience around UDP Discovery Key: ARTEMIS-2637 URL: https://issues.apache.org/jira/browse/ARTEMIS-2637 Project: ActiveMQ Artemis Issue

[jira] [Closed] (ARTEMIS-2634) Cellery uses AMQP as a broker

[ https://issues.apache.org/jira/browse/ARTEMIS-2634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy A. Bish closed ARTEMIS-2634. Resolution: Incomplete No info here that indicates a broker issue.  Please seek support

[jira] [Updated] (ARTEMIS-2636) Expose disk store used percentage metric

[ https://issues.apache.org/jira/browse/ARTEMIS-2636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christoph Ewerlin updated ARTEMIS-2636: --- Description: It would be very nice if the disk store used could be exposed via the

[jira] [Created] (ARTEMIS-2636) Expose disk store used percentage metric

Christoph Ewerlin created ARTEMIS-2636: -- Summary: Expose disk store used percentage metric Key: ARTEMIS-2636 URL: https://issues.apache.org/jira/browse/ARTEMIS-2636 Project: ActiveMQ Artemis

[jira] [Work logged] (ARTEMIS-2563) Create redistributor for remote broker even if local binding is missing

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

[jira] [Commented] (AMQ-7426) Upgrade to log4j2

[ https://issues.apache.org/jira/browse/AMQ-7426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17047551#comment-17047551 ] Jean-Baptiste Onofré commented on AMQ-7426: --- Yes, exactly. Let me come with a PR as discussion

[jira] [Commented] (AMQ-7426) Upgrade to log4j2

[ https://issues.apache.org/jira/browse/AMQ-7426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17047534#comment-17047534 ] Christopher L. Shannon commented on AMQ-7426: - Yeah so if there is no security issue than

[jira] [Commented] (AMQ-7426) Upgrade to log4j2

[ https://issues.apache.org/jira/browse/AMQ-7426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17047532#comment-17047532 ] Jean-Baptiste Onofré commented on AMQ-7426: --- [~cshannon] ActiveMQ is not affected by 

[jira] [Issue Comment Deleted] (AMQ-7426) Upgrade to log4j2

[ https://issues.apache.org/jira/browse/AMQ-7426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated AMQ-7426: -- Comment: was deleted (was: I agree, I mean 5.17.0. I'm creating the version.) > Upgrade

[jira] [Commented] (AMQ-7426) Upgrade to log4j2

[ https://issues.apache.org/jira/browse/AMQ-7426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17047531#comment-17047531 ] Christopher L. Shannon commented on AMQ-7426: - Cool, yeah I mean if it's important we can do a

[jira] [Updated] (AMQ-7426) Upgrade to log4j2

[ https://issues.apache.org/jira/browse/AMQ-7426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated AMQ-7426: -- Fix Version/s: (was: 5.17.0) 5.16.0 > Upgrade to log4j2 >

[jira] [Commented] (AMQ-7426) Upgrade to log4j2

[ https://issues.apache.org/jira/browse/AMQ-7426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17047530#comment-17047530 ] Christopher L. Shannon commented on AMQ-7426: - Nevermind, it looks like there's no log4j 1

[jira] [Updated] (AMQ-7426) Upgrade to log4j2

[ https://issues.apache.org/jira/browse/AMQ-7426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated AMQ-7426: -- Fix Version/s: (was: 5.16.0) 5.17.0 > Upgrade to log4j2 >

[jira] [Commented] (AMQ-7426) Upgrade to log4j2

[ https://issues.apache.org/jira/browse/AMQ-7426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17047528#comment-17047528 ] Jean-Baptiste Onofré commented on AMQ-7426: --- I agree, I mean 5.17.0. I'm creating the version. >

[jira] [Commented] (AMQ-7426) Upgrade to log4j2

[ https://issues.apache.org/jira/browse/AMQ-7426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17047527#comment-17047527 ] Christopher L. Shannon commented on AMQ-7426: - [~jbonofre]  - I don't think it's a very good

[jira] [Created] (ARTEMIS-2635) Cross network clustering in Kubernetes not working

Yasin Koyuncu created ARTEMIS-2635: -- Summary: Cross network clustering in Kubernetes not working Key: ARTEMIS-2635 URL: https://issues.apache.org/jira/browse/ARTEMIS-2635 Project: ActiveMQ Artemis

[jira] [Updated] (ARTEMIS-2634) Cellery uses AMQP as a broker

[ https://issues.apache.org/jira/browse/ARTEMIS-2634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yanwencheng updated ARTEMIS-2634: - Attachment: QQ截图20200228183922.png > Cellery uses AMQP as a broker >

[jira] [Created] (ARTEMIS-2634) Cellery uses AMQP as a broker

yanwencheng created ARTEMIS-2634: Summary: Cellery uses AMQP as a broker Key: ARTEMIS-2634 URL: https://issues.apache.org/jira/browse/ARTEMIS-2634 Project: ActiveMQ Artemis Issue Type: Bug

[jira] [Updated] (AMQ-7370) log4j 1.2 version used by AMQ 5.15.10 / 5.15.11 is vulnerable to CVE-2019-17571

[ https://issues.apache.org/jira/browse/AMQ-7370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated AMQ-7370: -- Fix Version/s: (was: 5.15.12) (was: 5.16.0) > log4j 1.2

[jira] [Created] (AMQ-7426) Upgrade to log4j2

Jean-Baptiste Onofré created AMQ-7426: - Summary: Upgrade to log4j2 Key: AMQ-7426 URL: https://issues.apache.org/jira/browse/AMQ-7426 Project: ActiveMQ Issue Type: Task

[jira] [Resolved] (AMQ-7370) log4j 1.2 version used by AMQ 5.15.10 / 5.15.11 is vulnerable to CVE-2019-17571

[ https://issues.apache.org/jira/browse/AMQ-7370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved AMQ-7370. --- Resolution: Not A Problem > log4j 1.2 version used by AMQ 5.15.10 / 5.15.11 is

[jira] [Commented] (AMQ-7370) log4j 1.2 version used by AMQ 5.15.10 / 5.15.11 is vulnerable to CVE-2019-17571

[ https://issues.apache.org/jira/browse/AMQ-7370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17047305#comment-17047305 ] Jean-Baptiste Onofré commented on AMQ-7370: --- Just checked and ActiveMQ is not affected as it