[jira] [Comment Edited] (ARTEMIS-3683) Failed to bind acceptor cluster to

[ https://issues.apache.org/jira/browse/ARTEMIS-3683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17491238#comment-17491238 ] Justin Bertram edited comment on ARTEMIS-3683 at 2/12/22, 3:17 AM: ---

[jira] [Commented] (ARTEMIS-3683) Failed to bind acceptor cluster to

[ https://issues.apache.org/jira/browse/ARTEMIS-3683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17491243#comment-17491243 ] Justin Bertram commented on ARTEMIS-3683: - If you're starting a broker with an acceptor

[jira] [Commented] (ARTEMIS-3683) Failed to bind acceptor cluster to

[ https://issues.apache.org/jira/browse/ARTEMIS-3683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17491238#comment-17491238 ] Ekta commented on ARTEMIS-3683: --- Hello, Thanks for your response. What I can see that on both servers

[jira] [Commented] (ARTEMIS-3683) Failed to bind acceptor cluster to

[ https://issues.apache.org/jira/browse/ARTEMIS-3683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17491230#comment-17491230 ] Justin Bertram commented on ARTEMIS-3683: - bq. ...even restarting isn't helping in one of the

[jira] [Comment Edited] (ARTEMIS-3683) Failed to bind acceptor cluster to

[ https://issues.apache.org/jira/browse/ARTEMIS-3683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17491161#comment-17491161 ] Ekta edited comment on ARTEMIS-3683 at 2/11/22, 10:09 PM: -- [~jbertram]  even

[jira] [Comment Edited] (ARTEMIS-3683) Failed to bind acceptor cluster to

[ https://issues.apache.org/jira/browse/ARTEMIS-3683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17491161#comment-17491161 ] Ekta edited comment on ARTEMIS-3683 at 2/11/22, 10:05 PM: -- [~jbertram]  even

[jira] [Comment Edited] (ARTEMIS-3683) Failed to bind acceptor cluster to

[ https://issues.apache.org/jira/browse/ARTEMIS-3683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17491161#comment-17491161 ] Ekta edited comment on ARTEMIS-3683 at 2/11/22, 10:03 PM: -- [~jbertram]  even

[jira] [Comment Edited] (ARTEMIS-3683) Failed to bind acceptor cluster to

[ https://issues.apache.org/jira/browse/ARTEMIS-3683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17491161#comment-17491161 ] Ekta edited comment on ARTEMIS-3683 at 2/11/22, 9:58 PM: - [~jbertram]  even

[jira] [Comment Edited] (ARTEMIS-3683) Failed to bind acceptor cluster to

[ https://issues.apache.org/jira/browse/ARTEMIS-3683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17491161#comment-17491161 ] Ekta edited comment on ARTEMIS-3683 at 2/11/22, 9:47 PM: - [~jbertram]  even

[jira] [Commented] (ARTEMIS-3683) Failed to bind acceptor cluster to

[ https://issues.apache.org/jira/browse/ARTEMIS-3683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17491161#comment-17491161 ] Ekta commented on ARTEMIS-3683: --- [~jbertram]  even restarting isn't helping in one of the server though

[jira] [Commented] (ARTEMIS-3683) Failed to bind acceptor cluster to

[ https://issues.apache.org/jira/browse/ARTEMIS-3683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17491146#comment-17491146 ] Justin Bertram commented on ARTEMIS-3683: - Thanks for attaching the log. Unfortunately the

[jira] [Resolved] (ARTEMIS-3683) Failed to bind acceptor cluster to

[ https://issues.apache.org/jira/browse/ARTEMIS-3683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram resolved ARTEMIS-3683. - Resolution: Not A Bug > Failed to bind acceptor cluster to >

[jira] [Commented] (ARTEMIS-3683) Failed to bind acceptor cluster to

[ https://issues.apache.org/jira/browse/ARTEMIS-3683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17491143#comment-17491143 ] Ekta commented on ARTEMIS-3683: --- I have attached to this ticket. Please check.  > Failed to bind

[jira] [Updated] (ARTEMIS-3683) Failed to bind acceptor cluster to

[ https://issues.apache.org/jira/browse/ARTEMIS-3683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekta updated ARTEMIS-3683: -- Attachment: artemis.log > Failed to bind acceptor cluster to > -- > >

[jira] [Comment Edited] (ARTEMIS-3683) Failed to bind acceptor cluster to

[ https://issues.apache.org/jira/browse/ARTEMIS-3683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17491136#comment-17491136 ] Ekta edited comment on ARTEMIS-3683 at 2/11/22, 8:30 PM: - Below is the rest of

[jira] [Commented] (ARTEMIS-3683) Failed to bind acceptor cluster to

[ https://issues.apache.org/jira/browse/ARTEMIS-3683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17491138#comment-17491138 ] Justin Bertram commented on ARTEMIS-3683: - I don't see any more of the aforementioned

[jira] [Comment Edited] (ARTEMIS-3683) Failed to bind acceptor cluster to

[ https://issues.apache.org/jira/browse/ARTEMIS-3683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17491136#comment-17491136 ] Ekta edited comment on ARTEMIS-3683 at 2/11/22, 8:29 PM: - Below is the rest of

[jira] [Updated] (ARTEMIS-3683) Failed to bind acceptor cluster to

[ https://issues.apache.org/jira/browse/ARTEMIS-3683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram updated ARTEMIS-3683: Description: I am facing below issue when I am trying to start up the broker using 2.18.

[jira] [Commented] (ARTEMIS-3683) Failed to bind acceptor cluster to

[ https://issues.apache.org/jira/browse/ARTEMIS-3683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17491136#comment-17491136 ] Ekta commented on ARTEMIS-3683: --- Below is the rest of it.     2022-02-11 14:13:32,994 INFO  

[jira] [Commented] (ARTEMIS-3683) Failed to bind acceptor cluster to

[ https://issues.apache.org/jira/browse/ARTEMIS-3683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17491135#comment-17491135 ] Justin Bertram commented on ARTEMIS-3683: - Is that the entire stack-trace? I would have

[jira] [Updated] (ARTEMIS-3683) Not able to start broker using 2.18 Artemis

[ https://issues.apache.org/jira/browse/ARTEMIS-3683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekta updated ARTEMIS-3683: -- Description: Hello, I am facing below issue when I am trying to start up the broker using 2.18 activemq

[jira] [Updated] (ARTEMIS-3683) Failed to bind acceptor cluster to

[ https://issues.apache.org/jira/browse/ARTEMIS-3683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekta updated ARTEMIS-3683: -- Summary: Failed to bind acceptor cluster to (was: Not able to start broker using 2.18 Artemis) > Failed to

[jira] [Created] (ARTEMIS-3683) Not able to start broker using 2.18 Artemis

Ekta created ARTEMIS-3683: - Summary: Not able to start broker using 2.18 Artemis Key: ARTEMIS-3683 URL: https://issues.apache.org/jira/browse/ARTEMIS-3683 Project: ActiveMQ Artemis Issue Type: Task

[jira] [Work logged] (ARTEMIS-3050) Reduce PagedReferenceImpl memory footprint

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

[jira] [Work logged] (ARTEMIS-3509) STOMP Websocket client disconnected after ConcurrentModificationException in Broker

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

[jira] [Work logged] (ARTEMIS-3509) STOMP Websocket client disconnected after ConcurrentModificationException in Broker

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

[jira] [Work logged] (ARTEMIS-3509) STOMP Websocket client disconnected after ConcurrentModificationException in Broker

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

[jira] [Commented] (ARTEMIS-3681) Add the function to define a static port for artemis to connect with client

[ https://issues.apache.org/jira/browse/ARTEMIS-3681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17491071#comment-17491071 ] Justin Bertram commented on ARTEMIS-3681: - It's worth noting that if you're using the core

[jira] [Updated] (ARTEMIS-3681) Add the function to define a static port for artemis to connect with client

[ https://issues.apache.org/jira/browse/ARTEMIS-3681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram updated ARTEMIS-3681: Description: Artemis uses 3 ports - 61616 , 8181 and a random port. # 61616 is the

[jira] [Updated] (ARTEMIS-3682) No way of knowing if a bridge was successfully deployed or not

[ https://issues.apache.org/jira/browse/ARTEMIS-3682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Hugonnet updated ARTEMIS-3682: --- Component/s: Broker > No way of knowing if a bridge was successfully deployed or

[jira] [Created] (ARTEMIS-3682) No way of knowing if a bridge was successfully deployed or not

Emmanuel Hugonnet created ARTEMIS-3682: -- Summary: No way of knowing if a bridge was successfully deployed or not Key: ARTEMIS-3682 URL: https://issues.apache.org/jira/browse/ARTEMIS-3682

[jira] [Commented] (ARTEMIS-3681) Add the function to define a static port for artemis to connect with client

[ https://issues.apache.org/jira/browse/ARTEMIS-3681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17491063#comment-17491063 ] Justin Bertram commented on ARTEMIS-3681: - To be clear, the broker _will_ communicate with most

[jira] [Resolved] (ARTEMIS-3681) Add the function to define a static port for artemis to connect with client

[ https://issues.apache.org/jira/browse/ARTEMIS-3681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram resolved ARTEMIS-3681. - Resolution: Invalid > Add the function to define a static port for artemis to connect

[jira] [Work logged] (ARTEMIS-3509) STOMP Websocket client disconnected after ConcurrentModificationException in Broker

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

[jira] [Comment Edited] (ARTEMIS-3681) Add the function to define a static port for artemis to connect with client

[ https://issues.apache.org/jira/browse/ARTEMIS-3681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17491058#comment-17491058 ] Justin Bertram edited comment on ARTEMIS-3681 at 2/11/22, 5:08 PM: ---

[jira] [Commented] (ARTEMIS-3681) Add the function to define a static port for artemis to connect with client

[ https://issues.apache.org/jira/browse/ARTEMIS-3681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17491058#comment-17491058 ] Justin Bertram commented on ARTEMIS-3681: - If you use the same commands as those listed at xxx

[jira] [Commented] (ARTEMIS-3681) Add the function to define a static port for artemis to connect with client

[ https://issues.apache.org/jira/browse/ARTEMIS-3681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17491054#comment-17491054 ] Justin Bertram commented on ARTEMIS-3681: - Are you using ActiveMQ "Classic" (i.e. 5.x) or are

[jira] [Work logged] (ARTEMIS-3509) STOMP Websocket client disconnected after ConcurrentModificationException in Broker

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

[jira] [Work logged] (AMQ-8472) Switch to reload4j for logging

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

[jira] [Work logged] (AMQ-8472) Switch to reload4j for logging

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

[jira] [Work logged] (AMQ-8472) Switch to reload4j for logging

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

[jira] [Resolved] (AMQ-8472) Switch to reload4j for logging

[ https://issues.apache.org/jira/browse/AMQ-8472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved AMQ-8472. --- Resolution: Fixed scope is now fixed > Switch to reload4j for logging >

[jira] [Work logged] (AMQ-8472) Switch to reload4j for logging

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

[jira] [Commented] (AMQ-8472) Switch to reload4j for logging

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

[jira] [Commented] (AMQ-8484) slf4j-reload4j scope is not correct

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

[jira] [Commented] (AMQ-8472) Switch to reload4j for logging

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

[jira] [Work logged] (AMQ-8472) Switch to reload4j for logging

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

[jira] [Work logged] (AMQ-8472) Switch to reload4j for logging

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

[jira] [Work logged] (AMQNET-637) NMS 2.0

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

[jira] [Work logged] (AMQNET-637) NMS 2.0

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

[jira] [Work logged] (AMQNET-637) NMS 2.0

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

[jira] [Comment Edited] (ARTEMIS-3509) STOMP Websocket client disconnected after ConcurrentModificationException in Broker

[ https://issues.apache.org/jira/browse/ARTEMIS-3509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17490964#comment-17490964 ] Benoît BERTHONNEAU edited comment on ARTEMIS-3509 at 2/11/22, 2:54 PM:

[jira] [Work logged] (AMQNET-637) NMS 2.0

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

[jira] [Work logged] (AMQ-8472) Switch to reload4j for logging

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

[jira] [Work logged] (ARTEMIS-3509) STOMP Websocket client disconnected after ConcurrentModificationException in Broker

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

[jira] [Commented] (ARTEMIS-3509) STOMP Websocket client disconnected after ConcurrentModificationException in Broker

[ https://issues.apache.org/jira/browse/ARTEMIS-3509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17490964#comment-17490964 ] Benoît BERTHONNEAU commented on ARTEMIS-3509: - Hi all, I'm working with [~Elodie] and I

[jira] [Created] (ARTEMIS-3681) Add the function to define a static port for artemis to connect with client

Ning Kang created ARTEMIS-3681: -- Summary: Add the function to define a static port for artemis to connect with client Key: ARTEMIS-3681 URL: https://issues.apache.org/jira/browse/ARTEMIS-3681 Project:

[jira] [Work logged] (AMQ-8472) Switch to reload4j for logging

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

[jira] [Work logged] (AMQ-8472) Switch to reload4j for logging

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

[jira] [Work logged] (AMQ-8472) Switch to reload4j for logging

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

[jira] [Work logged] (AMQ-8472) Switch to reload4j for logging

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

[jira] [Updated] (AMQ-8484) slf4j-reload4j scope is not correct

[ https://issues.apache.org/jira/browse/AMQ-8484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated AMQ-8484: Summary: slf4j-reload4j scope is not correct (was: reload4j scope is not correct) > slf4j-reload4j

[jira] [Commented] (AMQ-8484) reload4j scope is not correct

[ https://issues.apache.org/jira/browse/AMQ-8484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17490931#comment-17490931 ] Robbie Gemmell commented on AMQ-8484: - (Reversed the link direction, so it says this one is the

[jira] [Work logged] (AMQ-8472) Switch to reload4j for logging

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

[jira] [Work logged] (AMQ-8472) Switch to reload4j for logging

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

[jira] [Comment Edited] (AMQ-8484) reload4j scope is not correct

[ https://issues.apache.org/jira/browse/AMQ-8484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17490901#comment-17490901 ] Robbie Gemmell edited comment on AMQ-8484 at 2/11/22, 1:26 PM: --- Feels like

[jira] [Commented] (AMQ-8484) reload4j scope is not correct

[ https://issues.apache.org/jira/browse/AMQ-8484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17490907#comment-17490907 ] Jean-Baptiste Onofré commented on AMQ-8484: --- I set this Jira as duplicate to AMQ-8472. Thanks for

[jira] [Resolved] (AMQ-8484) reload4j scope is not correct

[ https://issues.apache.org/jira/browse/AMQ-8484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved AMQ-8484. --- Fix Version/s: (was: 5.16.4) Resolution: Duplicate > reload4j scope is not

[jira] [Commented] (AMQ-8484) reload4j scope is not correct

[ https://issues.apache.org/jira/browse/AMQ-8484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17490905#comment-17490905 ] Colm O hEigeartaigh commented on AMQ-8484: -- Yes I think in activemq-partition, it wasn't correct

[jira] [Reopened] (AMQ-8472) Switch to reload4j for logging

[ https://issues.apache.org/jira/browse/AMQ-8472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reopened AMQ-8472: --- > Switch to reload4j for logging > -- > > Key:

[jira] [Commented] (AMQ-8484) reload4j scope is not correct

[ https://issues.apache.org/jira/browse/AMQ-8484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17490901#comment-17490901 ] Robbie Gemmell commented on AMQ-8484: - Feels like reload4j reloaded changes should go on the original

[jira] [Work logged] (AMQ-8484) reload4j scope is not correct

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

[jira] [Resolved] (AMQ-8093) Illegal reflective access by IntrospectionSupport

[ https://issues.apache.org/jira/browse/AMQ-8093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved AMQ-8093. --- Fix Version/s: 5.16.4 Resolution: Fixed > Illegal reflective access by

[jira] [Commented] (AMQ-8093) Illegal reflective access by IntrospectionSupport

[ https://issues.apache.org/jira/browse/AMQ-8093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17490893#comment-17490893 ] Jean-Baptiste Onofré commented on AMQ-8093: --- It's fixed in coming 5.16.4 release. > Illegal

[jira] [Created] (AMQ-8484) reload4j scope is not correct

Jean-Baptiste Onofré created AMQ-8484: - Summary: reload4j scope is not correct Key: AMQ-8484 URL: https://issues.apache.org/jira/browse/AMQ-8484 Project: ActiveMQ Issue Type: Bug

[jira] [Commented] (AMQ-8093) Illegal reflective access by IntrospectionSupport

[ https://issues.apache.org/jira/browse/AMQ-8093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17490887#comment-17490887 ] Geert Schuring commented on AMQ-8093: - Im running version 5.16.3 and still get this warning. Is there

[jira] [Work logged] (ARTEMIS-3677) Mitigate NPE when browsing messages

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

[jira] [Created] (AMQ-8483) HttpClientTransport refuses to accept cookies using `Expires' header

bogdan.tomc...@sabre.com created AMQ-8483: - Summary: HttpClientTransport refuses to accept cookies using `Expires' header Key: AMQ-8483 URL: https://issues.apache.org/jira/browse/AMQ-8483

[jira] [Commented] (AMQ-8482) JMSAppender Remote Code Execution (CVE-2021-4104)

[ https://issues.apache.org/jira/browse/AMQ-8482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17490847#comment-17490847 ] Robbie Gemmell commented on AMQ-8482: - {quote}... and a 5.16.4 release is currently-under-vote. {quote}

[jira] [Commented] (AMQ-8482) JMSAppender Remote Code Execution (CVE-2021-4104)

[ https://issues.apache.org/jira/browse/AMQ-8482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17490844#comment-17490844 ] Beng Sokhom commented on AMQ-8482: -- when you expect to release the latest version of AMQ? > JMSAppender

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

[ https://issues.apache.org/jira/browse/AMQ-7426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated AMQ-7426: Description: This JIRA will upgrade 5.17.x to use Log4J 2.x instead of 1.x (5.16.x was switched to

[jira] [Resolved] (AMQ-8482) JMSAppender Remote Code Execution (CVE-2021-4104)

[ https://issues.apache.org/jira/browse/AMQ-8482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved AMQ-8482. - Resolution: Duplicate > JMSAppender Remote Code Execution (CVE-2021-4104) >

[jira] [Closed] (AMQ-8482) JMSAppender Remote Code Execution (CVE-2021-4104)

[ https://issues.apache.org/jira/browse/AMQ-8482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell closed AMQ-8482. --- > JMSAppender Remote Code Execution (CVE-2021-4104) > --

[jira] [Reopened] (AMQ-8482) JMSAppender Remote Code Execution (CVE-2021-4104)

[ https://issues.apache.org/jira/browse/AMQ-8482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell reopened AMQ-8482: - > JMSAppender Remote Code Execution (CVE-2021-4104) >

[jira] [Closed] (AMQ-8482) JMSAppender Remote Code Execution (CVE-2021-4104)

[ https://issues.apache.org/jira/browse/AMQ-8482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell closed AMQ-8482. --- Resolution: Fixed > JMSAppender Remote Code Execution (CVE-2021-4104) >

[jira] [Comment Edited] (AMQ-8482) JMSAppender Remote Code Execution (CVE-2021-4104)

[ https://issues.apache.org/jira/browse/AMQ-8482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17490771#comment-17490771 ] Robbie Gemmell edited comment on AMQ-8482 at 2/11/22, 9:25 AM: --- Effective

[jira] [Reopened] (AMQ-8482) JMSAppender Remote Code Execution (CVE-2021-4104)

[ https://issues.apache.org/jira/browse/AMQ-8482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell reopened AMQ-8482: - > JMSAppender Remote Code Execution (CVE-2021-4104) >

[jira] [Closed] (AMQ-8482) JMSAppender Remote Code Execution (CVE-2021-4104)

[ https://issues.apache.org/jira/browse/AMQ-8482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell closed AMQ-8482. --- Resolution: Duplicate Effective duplicate of _several_ other JIRAs. Please look before raising