[jira] [Created] (ARTEMIS-4519) Why can a client connect and see two different session IDs on the console?

gongping.zhu created ARTEMIS-4519: - Summary: Why can a client connect and see two different session IDs on the console? Key: ARTEMIS-4519 URL: https://issues.apache.org/jira/browse/ARTEMIS-4519

[jira] [Resolved] (ARTEMIS-4514) Make Jetty thread pool configurable

[ https://issues.apache.org/jira/browse/ARTEMIS-4514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram resolved ARTEMIS-4514. - Fix Version/s: 2.32.0 Resolution: Fixed > Make Jetty thread pool configurable >

[jira] [Work logged] (ARTEMIS-4498) Expose internal queues for management and observability

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

[jira] [Work logged] (ARTEMIS-4498) Expose internal queues for management and observability

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

[jira] [Work logged] (ARTEMIS-4498) Expose internal queues for management and observability

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

[jira] [Commented] (ARTEMIS-4512) JMS queue consumer can mistakenly connect to multicast queue

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

[jira] [Commented] (ARTEMIS-4515) Setting web request log using system properties not working

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

[jira] [Work logged] (ARTEMIS-4512) JMS queue consumer can mistakenly connect to multicast queue

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

[jira] [Commented] (ARTEMIS-4517) rollback causes loss of message order if concurrent producers commit out of order

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

[jira] [Commented] (ARTEMIS-4514) Make Jetty thread pool configurable

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

[jira] [Work logged] (ARTEMIS-4514) Make Jetty thread pool configurable

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

[jira] [Work logged] (ARTEMIS-4517) rollback causes loss of message order if concurrent producers commit out of order

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

[jira] [Work logged] (ARTEMIS-4515) Setting web request log using system properties not working

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

[jira] [Work logged] (ARTEMIS-4517) rollback causes loss of message order if concurrent producers commit out of order

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

[jira] [Resolved] (ARTEMIS-4518) Exclude slf4j-api from activemq-client to prevent java.lang.LinkageError during artemis-jms-bridge.war deployment

[ https://issues.apache.org/jira/browse/ARTEMIS-4518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram resolved ARTEMIS-4518. - Fix Version/s: 2.32.0 Resolution: Fixed > Exclude slf4j-api from

[jira] [Commented] (ARTEMIS-4518) Exclude slf4j-api from activemq-client to prevent java.lang.LinkageError during artemis-jms-bridge.war deployment

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

[jira] [Updated] (ARTEMIS-4518) Exclude slf4j-api from activemq-client to prevent java.lang.LinkageError during artemis-jms-bridge.war deployment

[ https://issues.apache.org/jira/browse/ARTEMIS-4518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram updated ARTEMIS-4518: Description: In version 2.27.1 one was able to build and deploy

[jira] [Created] (ARTEMIS-4518) Exclude slf4j-api from activemq-client to prevent java.lang.LinkageError during artemis-jms-bridge.war deployment

Justin Bertram created ARTEMIS-4518: --- Summary: Exclude slf4j-api from activemq-client to prevent java.lang.LinkageError during artemis-jms-bridge.war deployment Key: ARTEMIS-4518 URL:

[jira] [Work logged] (ARTEMIS-4514) Make Jetty thread pool configurable

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

[jira] [Work logged] (ARTEMIS-4517) rollback causes loss of message order if concurrent producers commit out of order

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

[jira] [Work logged] (ARTEMIS-4517) rollback causes loss of message order if concurrent producers commit out of order

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

[jira] [Work logged] (ARTEMIS-4517) rollback causes loss of message order if concurrent producers commit out of order

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

[jira] [Work logged] (ARTEMIS-4517) rollback causes loss of message order if concurrent producers commit out of order

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

[jira] [Work logged] (ARTEMIS-4517) rollback causes loss of message order if concurrent producers commit out of order

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

[jira] [Work logged] (ARTEMIS-4517) rollback causes loss of message order if concurrent producers commit out of order

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

[jira] [Work logged] (ARTEMIS-4517) rollback causes loss of message order if concurrent producers commit out of order

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

[jira] [Work logged] (ARTEMIS-4517) rollback causes loss of message order if concurrent producers commit out of order

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

[jira] [Created] (ARTEMIS-4517) rollback causes loss of message order if concurrent producers commit out of order

Gary Tully created ARTEMIS-4517: --- Summary: rollback causes loss of message order if concurrent producers commit out of order Key: ARTEMIS-4517 URL: https://issues.apache.org/jira/browse/ARTEMIS-4517

[jira] [Commented] (AMQ-9406) Upgrade to Camel 4.2.0

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

[jira] [Resolved] (AMQ-9406) Upgrade to Camel 4.2.0

[ https://issues.apache.org/jira/browse/AMQ-9406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved AMQ-9406. --- Resolution: Fixed > Upgrade to Camel 4.2.0 > -- > >

[jira] [Work logged] (AMQ-9406) Upgrade to Camel 4.2.0

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

[jira] [Commented] (AMQ-9406) Upgrade to Camel 4.2.0

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

[jira] [Commented] (AMQ-9406) Upgrade to Camel 4.2.0

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

[jira] [Resolved] (AMQ-9407) Upgrade to log4j 2.22.0

[ https://issues.apache.org/jira/browse/AMQ-9407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved AMQ-9407. --- Resolution: Fixed > Upgrade to log4j 2.22.0 > --- > >

[jira] [Work logged] (AMQ-9407) Upgrade to log4j 2.22.0

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

[jira] [Commented] (AMQ-9407) Upgrade to log4j 2.22.0

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

[jira] [Commented] (AMQ-9407) Upgrade to log4j 2.22.0

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

[jira] [Commented] (AMQ-9407) Upgrade to log4j 2.22.0

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

[jira] [Resolved] (AMQ-9404) Upgrade to Spring 6.0.14

[ https://issues.apache.org/jira/browse/AMQ-9404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved AMQ-9404. --- Resolution: Fixed > Upgrade to Spring 6.0.14 > > >

[jira] [Commented] (AMQ-9404) Upgrade to Spring 6.0.14

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

[jira] [Commented] (AMQ-9404) Upgrade to Spring 6.0.14

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

[jira] [Work logged] (AMQ-9404) Upgrade to Spring 6.0.14

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

[jira] [Updated] (ARTEMIS-4516) Support reloading connectors

[ https://issues.apache.org/jira/browse/ARTEMIS-4516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sascha Dirbach updated ARTEMIS-4516: Description: ARTEMIS-3685 allows reloading/creation of bridges on config reload. If

[jira] [Created] (ARTEMIS-4516) Support reloading connectors

Sascha Dirbach created ARTEMIS-4516: --- Summary: Support reloading connectors Key: ARTEMIS-4516 URL: https://issues.apache.org/jira/browse/ARTEMIS-4516 Project: ActiveMQ Artemis Issue Type:

[jira] [Work logged] (ARTEMIS-4515) Setting web request log using system properties not working

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

[jira] [Created] (ARTEMIS-4515) Setting web request log using system properties not working

Domenico Francesco Bruscino created ARTEMIS-4515: Summary: Setting web request log using system properties not working Key: ARTEMIS-4515 URL: https://issues.apache.org/jira/browse/ARTEMIS-4515

[jira] [Assigned] (AMQ-9408) Jolokia throws exception during Windows service startup

[ https://issues.apache.org/jira/browse/AMQ-9408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reassigned AMQ-9408: - Assignee: Jean-Baptiste Onofré > Jolokia throws exception during Windows service

[jira] [Commented] (AMQ-9408) Jolokia throws exception during Windows service startup

[ https://issues.apache.org/jira/browse/AMQ-9408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17790476#comment-17790476 ] Jean-Baptiste Onofré commented on AMQ-9408: --- Good catch, I forgot to update the wrapper. Let me

[jira] [Updated] (AMQ-9408) Jolokia throws exception during Windows service startup

[ https://issues.apache.org/jira/browse/AMQ-9408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated AMQ-9408: -- Fix Version/s: 6.0.1 6.1.0 5.18.4 > Jolokia throws

[jira] [Updated] (AMQ-9408) Jolokia throws exception during Windows service startup

[ https://issues.apache.org/jira/browse/AMQ-9408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated AMQ-9408: -- Fix Version/s: 5.17.7 > Jolokia throws exception during Windows service startup >