[jira] [Commented] (ARTEMIS-1691) JMS Bridge: After the FailureHandler exits, a bridge cannot be started full functional anymore
[
https://issues.apache.org/jira/browse/ARTEMIS-1691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17837504#comment-17837504
]
ASF subversion and git services commented on ARTEMIS-1691:
--
Commit a1db72395c055069439870ca147ebde6a0d16f44 in activemq-artemis's branch
refs/heads/main from Justin Bertram
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=a1db72395c ]
ARTEMIS-1691 JMS bridge can't be manually restarted after failure
> JMS Bridge: After the FailureHandler exits, a bridge cannot be started full
> functional anymore
> --
>
> Key: ARTEMIS-1691
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1691
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.4.0
> Environment: WildFly Servers.
>Reporter: Markus F
>Assignee: Justin Bertram
>Priority: Minor
> Time Spent: 20m
> Remaining Estimate: 0h
>
> h4. Setup
> JMSBridge on server a pulls messages from a remote server B.
> failureRetryInterval = 1 sec
> maxRetries = 1
> h4. To Reproduce
> Restart the remote server (need to take more than one second.)
> JMS Bridge prints out:
> {noformat}
> JMS Bridge unable to set up connections, bridge will be stopped{noformat}
> After the remote server is up again, start the bridge again.
> JMS Bridge prints out:
> {noformat}
> Started JMS Bridge testbridge{noformat}
> h4. Result:
> The bridge is started, but does still not consume messages.
> h4. Reason
> In {{JMSBridgeImpl}} line 1624, the failed boolean parameter is checked. It
> is not set to true anywhere outside the failure handlers ({{FailureHandler}}
> and {{StartupFailureHandler}}) or on initial adding of the bridge.
> But the {{FailureHandler}} has already exited. So the bridge will wait all
> time long for 500 ms in line 1626.
> h4. Solution
> I would add a
> {code:java}
> failed = false;{code}
> after line 403.
> I don't know how the release process is handled here, if I can make a pull
> request or something like that, I will do, if it is needed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-1691) JMS Bridge: After the FailureHandler exits, a bridge cannot be started full functional anymore
[
https://issues.apache.org/jira/browse/ARTEMIS-1691?focusedWorklogId=914774=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-914774
]
ASF GitHub Bot logged work on ARTEMIS-1691:
---
Author: ASF GitHub Bot
Created on: 16/Apr/24 03:49
Start Date: 16/Apr/24 03:49
Worklog Time Spent: 10m
Work Description: clebertsuconic merged PR #4883:
URL: https://github.com/apache/activemq-artemis/pull/4883
Issue Time Tracking
---
Worklog Id: (was: 914774)
Time Spent: 20m (was: 10m)
> JMS Bridge: After the FailureHandler exits, a bridge cannot be started full
> functional anymore
> --
>
> Key: ARTEMIS-1691
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1691
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.4.0
> Environment: WildFly Servers.
>Reporter: Markus F
>Assignee: Justin Bertram
>Priority: Minor
> Time Spent: 20m
> Remaining Estimate: 0h
>
> h4. Setup
> JMSBridge on server a pulls messages from a remote server B.
> failureRetryInterval = 1 sec
> maxRetries = 1
> h4. To Reproduce
> Restart the remote server (need to take more than one second.)
> JMS Bridge prints out:
> {noformat}
> JMS Bridge unable to set up connections, bridge will be stopped{noformat}
> After the remote server is up again, start the bridge again.
> JMS Bridge prints out:
> {noformat}
> Started JMS Bridge testbridge{noformat}
> h4. Result:
> The bridge is started, but does still not consume messages.
> h4. Reason
> In {{JMSBridgeImpl}} line 1624, the failed boolean parameter is checked. It
> is not set to true anywhere outside the failure handlers ({{FailureHandler}}
> and {{StartupFailureHandler}}) or on initial adding of the bridge.
> But the {{FailureHandler}} has already exited. So the bridge will wait all
> time long for 500 ms in line 1626.
> h4. Solution
> I would add a
> {code:java}
> failed = false;{code}
> after line 403.
> I don't know how the release process is handled here, if I can make a pull
> request or something like that, I will do, if it is needed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4702) Only run command needs custom JVM settings
[
https://issues.apache.org/jira/browse/ARTEMIS-4702?focusedWorklogId=914768=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-914768
]
ASF GitHub Bot logged work on ARTEMIS-4702:
---
Author: ASF GitHub Bot
Created on: 16/Apr/24 03:18
Start Date: 16/Apr/24 03:18
Worklog Time Spent: 10m
Work Description: clebertsuconic commented on code in PR #4885:
URL: https://github.com/apache/activemq-artemis/pull/4885#discussion_r1566656217
##
artemis-cli/src/main/resources/org/apache/activemq/artemis/cli/commands/etc/artemis.profile:
##
@@ -36,7 +36,7 @@ ARTEMIS_INSTANCE_ETC_URI='${artemis.instance.etc.uri}'
HAWTIO_ROLE='${role}'
# Java Opts
-if [ -z "$JAVA_ARGS" ]; then
+if [ -z "$JAVA_ARGS" ] && [ "$1" = "run" ]; then
Review Comment:
the export might need special memory to load large journals as well.
Also, if you don't pass an argument you may enter the shell where you can do
export, data print, and also.. run from the shell. (not very common, but
possible).
Issue Time Tracking
---
Worklog Id: (was: 914768)
Time Spent: 20m (was: 10m)
> Only run command needs custom JVM settings
> --
>
> Key: ARTEMIS-4702
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4702
> Project: ActiveMQ Artemis
> Issue Type: Improvement
>Reporter: Justin Bertram
>Assignee: Justin Bertram
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Right now every {{artemis}} command uses the same JVM settings from
> {{artemis.profile}}. So, for example, if the settings included {{-Xms8G
> -Xmx8G}} for running the broker (i.e. the {{run}} command) those same
> settings would be used for the {{queue stat}}, {{consumer}}, {{producer}},
> etc. commands as well. At best, it's overkill to use 8G of memory for these
> secondary commands and at worst it can actually prevent them from operating
> at all (e.g. if the machine is low on memory).
> JVM settings really only need to apply to the {{run}} command.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4725) Mirror may send wrong headers
[ https://issues.apache.org/jira/browse/ARTEMIS-4725?focusedWorklogId=914764=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-914764 ] ASF GitHub Bot logged work on ARTEMIS-4725: --- Author: ASF GitHub Bot Created on: 16/Apr/24 02:35 Start Date: 16/Apr/24 02:35 Worklog Time Spent: 10m Work Description: clebertsuconic opened a new pull request, #4888: URL: https://github.com/apache/activemq-artemis/pull/4888 Issue manifested during Mirror delivery and full brokers restart Issue Time Tracking --- Worklog Id: (was: 914764) Remaining Estimate: 0h Time Spent: 10m > Mirror may send wrong headers > - > > Key: ARTEMIS-4725 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4725 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Clebert Suconic >Assignee: Clebert Suconic >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > This is not specifically an issue in Mirroring or Broker Connection, but it > manifested as part of the broker connection codebase. > When a delivery for the first time after a reload happens, the delivery > annotation may be written before the header, breaking the specification. > Later on delivery the message, createDelieryCopy could get confused with the > positions: > https://github.com/apache/activemq-artemis/blob/50fae08b09a76e200ef107d06cc867231f644ccd/artemis-protocols/artemis-amqp-protocol/src/main/java/org/apache/activemq/artemis/protocol/amqp/broker/AMQPMessage.java#L829 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ARTEMIS-4725) Mirror may send wrong headers
Clebert Suconic created ARTEMIS-4725: Summary: Mirror may send wrong headers Key: ARTEMIS-4725 URL: https://issues.apache.org/jira/browse/ARTEMIS-4725 Project: ActiveMQ Artemis Issue Type: Bug Reporter: Clebert Suconic Assignee: Clebert Suconic This is not specifically an issue in Mirroring or Broker Connection, but it manifested as part of the broker connection codebase. When a delivery for the first time after a reload happens, the delivery annotation may be written before the header, breaking the specification. Later on delivery the message, createDelieryCopy could get confused with the positions: https://github.com/apache/activemq-artemis/blob/50fae08b09a76e200ef107d06cc867231f644ccd/artemis-protocols/artemis-amqp-protocol/src/main/java/org/apache/activemq/artemis/protocol/amqp/broker/AMQPMessage.java#L829 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] (ARTEMIS-1769) Return JMS Session's ClientID via JMX
[ https://issues.apache.org/jira/browse/ARTEMIS-1769 ] Justin Bertram deleted comment on ARTEMIS-1769: - was (Author: jbertram): This should be resolved via ARTEMIS-1921. > Return JMS Session's ClientID via JMX > - > > Key: ARTEMIS-1769 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1769 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Broker >Affects Versions: 2.5.0 >Reporter: Maxim Kalina >Assignee: Justin Bertram >Priority: Minor > Labels: patch > Attachments: return_jms_session's_clientID_via_JMX_if_exists.patch > > > As discussed in the mailing list, currently there is no possibility to get > the JMS session's *clientID* via JMX. > > I've attached the patch that extends the *ActiveMQServerControlImpl* and > *SessionView* classes to return the *clientID* if available. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (ARTEMIS-1769) Return JMS Session's ClientID via JMX
[ https://issues.apache.org/jira/browse/ARTEMIS-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram reopened ARTEMIS-1769: - Assignee: Justin Bertram > Return JMS Session's ClientID via JMX > - > > Key: ARTEMIS-1769 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1769 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Broker >Affects Versions: 2.5.0 >Reporter: Maxim Kalina >Assignee: Justin Bertram >Priority: Minor > Labels: patch > Attachments: return_jms_session's_clientID_via_JMX_if_exists.patch > > > As discussed in the mailing list, currently there is no possibility to get > the JMS session's *clientID* via JMX. > > I've attached the patch that extends the *ActiveMQServerControlImpl* and > *SessionView* classes to return the *clientID* if available. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-1769) Return JMS Session's ClientID via JMX
[ https://issues.apache.org/jira/browse/ARTEMIS-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram resolved ARTEMIS-1769. - Resolution: Duplicate This should be resolved via ARTEMIS-1921. > Return JMS Session's ClientID via JMX > - > > Key: ARTEMIS-1769 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1769 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Broker >Affects Versions: 2.5.0 >Reporter: Maxim Kalina >Priority: Minor > Labels: patch > Attachments: return_jms_session's_clientID_via_JMX_if_exists.patch > > > As discussed in the mailing list, currently there is no possibility to get > the JMS session's *clientID* via JMX. > > I've attached the patch that extends the *ActiveMQServerControlImpl* and > *SessionView* classes to return the *clientID* if available. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-1921) Setting client ID on core JMS should be reflected in broker RemotingConnection
[ https://issues.apache.org/jira/browse/ARTEMIS-1921?focusedWorklogId=914742=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-914742 ] ASF GitHub Bot logged work on ARTEMIS-1921: --- Author: ASF GitHub Bot Created on: 15/Apr/24 20:19 Start Date: 15/Apr/24 20:19 Worklog Time Spent: 10m Work Description: jbertram opened a new pull request, #4887: URL: https://github.com/apache/activemq-artemis/pull/4887 (no comment) Issue Time Tracking --- Worklog Id: (was: 914742) Remaining Estimate: 0h Time Spent: 10m > Setting client ID on core JMS should be reflected in broker RemotingConnection > -- > > Key: ARTEMIS-1921 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1921 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Broker >Affects Versions: 2.6.1 >Reporter: Johan Stenberg >Priority: Major > Attachments: Artemis1921_CoreJmsClient_SetClientId_Test.java > > Time Spent: 10m > Remaining Estimate: 0h > > As opposite to Qpid JMS Client over AMPQ1.0 or FuseSource StompJMS client > over STOMP, a clientID set on the JMS ConnectionFactory or the Connection in > the Artemis JMS Client is not available on the broker via > RemotingConnection#getClientID(). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-1921) Setting client ID on core JMS should be reflected in broker RemotingConnection
[
https://issues.apache.org/jira/browse/ARTEMIS-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17837405#comment-17837405
]
Justin Bertram commented on ARTEMIS-1921:
-
[~johan1], upon closer inspection I can't get your attached code to work with
Qpid JMS. The client ID is *not* available during authentication. Here's the
test I'm running:
{code:java}
import javax.jms.Connection;
import java.util.Arrays;
import java.util.HashSet;
import java.util.Set;
import org.apache.activemq.artemis.api.core.TransportConfiguration;
import org.apache.activemq.artemis.core.config.impl.ConfigurationImpl;
import
org.apache.activemq.artemis.core.remoting.impl.netty.NettyAcceptorFactory;
import org.apache.activemq.artemis.core.remoting.impl.netty.TransportConstants;
import org.apache.activemq.artemis.core.security.CheckType;
import org.apache.activemq.artemis.core.security.Role;
import org.apache.activemq.artemis.core.server.embedded.EmbeddedActiveMQ;
import org.apache.activemq.artemis.spi.core.protocol.RemotingConnection;
import org.apache.activemq.artemis.spi.core.security.ActiveMQSecurityManager3;
import org.apache.activemq.artemis.tests.util.ActiveMQTestBase;
import org.apache.qpid.jms.JmsConnectionFactory;
import org.junit.After;
import org.junit.Before;
import org.junit.Test;
public class Artemis1921 extends ActiveMQTestBase {
private EmbeddedActiveMQ broker;
@Before
public void setup() throws Exception {
broker = new EmbeddedActiveMQ();
broker.setSecurityManager(new ActiveMQSecurityManager3() {
@Override
public boolean validateUserAndRole(final String user, final String
password, final Set roles, final CheckType checkType) {
return validateUser(user, password);
}
@Override
public boolean validateUser(final String user, final String password) {
return "foo".equals(user) && "bar".equals(password);
}
@Override
public String validateUserAndRole(final String user, final String
password, final Set roles, final CheckType checkType, final String
address,
final RemotingConnection
remotingConnection) {
return validateUser(user, password, remotingConnection);
}
@Override
public String validateUser(final String user, final String password,
final RemotingConnection remotingConnection) {
final String clientID = remotingConnection.getClientID();
if (clientID == null) {
System.err.println("*");
System.err.println("* No clientID set!");
System.err.println("*");
return null;
}
return validateUser(user, password) ? user : null;
}
});
final TransportConfiguration transportCfg = new
TransportConfiguration(NettyAcceptorFactory.class.getName());
transportCfg.getParams().put(TransportConstants.PROTOCOLS_PROP_NAME,
"CORE,AMQP");
transportCfg.getParams().put(TransportConstants.HOST_PROP_NAME,
"0.0.0.0");
transportCfg.getParams().put(TransportConstants.PORT_PROP_NAME, "61616");
broker.setConfiguration(new ConfigurationImpl()
.setPersistenceEnabled(false)
.setSecurityEnabled(true)
.setAcceptorConfigurations(new
HashSet<>(Arrays.asList(transportCfg)))
);
broker.start();
}
@After
public void tearDown() throws Exception {
broker.stop();
}
@Test
public void testJMSConnect() throws Exception {
final JmsConnectionFactory jmsCF = new
JmsConnectionFactory("amqp://localhost:61616");
jmsCF.setUsername("foo");
jmsCF.setPassword("bar");
jmsCF.setClientID("foo_001"); // trying to set clientID on CF
final Connection jmsConn = jmsCF.createConnection();
jmsConn.setClientID("foo_001"); // trying to set clientID on connection
jmsConn.start();
jmsConn.close();
}
}{code}
This code doesn't work for any of the supported JMS clients (i.e. Core JMS,
Qpid JMS, and OpenWire JMS).
> Setting client ID on core JMS should be reflected in broker RemotingConnection
> --
>
> Key: ARTEMIS-1921
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1921
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
>Affects Versions: 2.6.1
>Reporter: Johan Stenberg
>Priority: Major
> Attachments: Artemis1921_CoreJmsClient_SetClientId_Test.java
>
>
> As opposite to Qpid JMS Client over AMPQ1.0 or FuseSource StompJMS client
> over STOMP, a clientID set on the JMS ConnectionFactory or the Connection in
[jira] [Updated] (ARTEMIS-1921) Setting client ID on core JMS should be reflected in broker RemotingConnection
[ https://issues.apache.org/jira/browse/ARTEMIS-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram updated ARTEMIS-1921: Summary: Setting client ID on core JMS should be reflected in broker RemotingConnection (was: Setting clientID in artemis-jms-client has no effect) > Setting client ID on core JMS should be reflected in broker RemotingConnection > -- > > Key: ARTEMIS-1921 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1921 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Broker >Affects Versions: 2.6.1 >Reporter: Johan Stenberg >Priority: Major > Attachments: Artemis1921_CoreJmsClient_SetClientId_Test.java > > > As opposite to Qpid JMS Client over AMPQ1.0 or FuseSource StompJMS client > over STOMP, a clientID set on the JMS ConnectionFactory or the Connection in > the Artemis JMS Client is not available on the broker via > RemotingConnection#getClientID(). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-1921) Setting clientID in artemis-jms-client has no effect
[ https://issues.apache.org/jira/browse/ARTEMIS-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17837387#comment-17837387 ] Robbie Gemmell commented on ARTEMIS-1921: - I wasn't really getting into whether the current implementation is actually able to do what was expected, just noting the attached application code did also do something that is portable, which your reply didnt seem to cover by concentrating only on the other bit that isnt. Reading again, it also seems like you were suggesting it only works for Qpid JMS due to setting it on the ConnectionFactory, but I dont believe that is the case. If a ClientID wasnt set on the ConnectionFactory 'administratively' (i.e via impl-detail setter or its URI options) then the client will actually create the TCP connection and authenticate, but defer establishing the bare AMQP connection (which carries the ClientID as its container-id) until such time a Connection method is called, like setClientID first if you want to set the ClientID (and it hasnt been set 'administratively' already), or any other method if you don't want to (and havent already) set it . The client can be configured not to defer the bare AMQP connection like this, if you know you wont set a clientID and also e.g want to take a while before using the Connection. > Setting clientID in artemis-jms-client has no effect > > > Key: ARTEMIS-1921 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1921 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Broker >Affects Versions: 2.6.1 >Reporter: Johan Stenberg >Priority: Major > Attachments: Artemis1921_CoreJmsClient_SetClientId_Test.java > > > As opposite to Qpid JMS Client over AMPQ1.0 or FuseSource StompJMS client > over STOMP, a clientID set on the JMS ConnectionFactory or the Connection in > the Artemis JMS Client is not available on the broker via > RemotingConnection#getClientID(). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-1921) Setting clientID in artemis-jms-client has no effect
[ https://issues.apache.org/jira/browse/ARTEMIS-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17837379#comment-17837379 ] Justin Bertram commented on ARTEMIS-1921: - The latter _is portable_ as you note. However, the fact that the client ID is set _after the connection is created_ means that the client ID will *not* be passed to the security manager which is the desired behavior here. > Setting clientID in artemis-jms-client has no effect > > > Key: ARTEMIS-1921 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1921 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Broker >Affects Versions: 2.6.1 >Reporter: Johan Stenberg >Priority: Major > Attachments: Artemis1921_CoreJmsClient_SetClientId_Test.java > > > As opposite to Qpid JMS Client over AMPQ1.0 or FuseSource StompJMS client > over STOMP, a clientID set on the JMS ConnectionFactory or the Connection in > the Artemis JMS Client is not available on the broker via > RemotingConnection#getClientID(). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (ARTEMIS-1921) Setting clientID in artemis-jms-client has no effect
[ https://issues.apache.org/jira/browse/ARTEMIS-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17837376#comment-17837376 ] Robbie Gemmell edited comment on ARTEMIS-1921 at 4/15/24 5:19 PM: -- The attached code tries _both_ the ConnectionFactory method that is impl-detail and not part of the API (though is in the vein of 'administratively configured' values the spec does speak to), as well as the Connection method that _is_ part of the spec. The latter is portable. was (Author: gemmellr): The attached code tries _both_ the ConnectionFactory method that is impl-detail and not part of the APUI (though is in the vein of 'administratively configured' values the spec does speak to), as well as the Connection method that _is_ part of the spec. The latter is portable. > Setting clientID in artemis-jms-client has no effect > > > Key: ARTEMIS-1921 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1921 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Broker >Affects Versions: 2.6.1 >Reporter: Johan Stenberg >Priority: Major > Attachments: Artemis1921_CoreJmsClient_SetClientId_Test.java > > > As opposite to Qpid JMS Client over AMPQ1.0 or FuseSource StompJMS client > over STOMP, a clientID set on the JMS ConnectionFactory or the Connection in > the Artemis JMS Client is not available on the broker via > RemotingConnection#getClientID(). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-1921) Setting clientID in artemis-jms-client has no effect
[ https://issues.apache.org/jira/browse/ARTEMIS-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17837376#comment-17837376 ] Robbie Gemmell commented on ARTEMIS-1921: - The attached code tries _both_ the ConnectionFactory method that is impl-detail and not part of the APUI (though is in the vein of 'administratively configured' values the spec does speak to), as well as the Connection method that _is_ part of the spec. The latter is portable. > Setting clientID in artemis-jms-client has no effect > > > Key: ARTEMIS-1921 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1921 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Broker >Affects Versions: 2.6.1 >Reporter: Johan Stenberg >Priority: Major > Attachments: Artemis1921_CoreJmsClient_SetClientId_Test.java > > > As opposite to Qpid JMS Client over AMPQ1.0 or FuseSource StompJMS client > over STOMP, a clientID set on the JMS ConnectionFactory or the Connection in > the Artemis JMS Client is not available on the broker via > RemotingConnection#getClientID(). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (ARTEMIS-1921) Setting clientID in artemis-jms-client has no effect
[
https://issues.apache.org/jira/browse/ARTEMIS-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17837364#comment-17837364
]
Justin Bertram edited comment on ARTEMIS-1921 at 4/15/24 5:02 PM:
--
Your attachment uses
{{org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory#setClientID}}.
This is a _convenience method_ provided by the Core JMS client and is *not*
part of the
[JMS|https://docs.oracle.com/javaee/7/api/javax/jms/ConnectionFactory.html] or
[Jakarta
Messaging|https://jakarta.ee/specifications/messaging/3.0/apidocs/jakarta/jms/connectionfactory]
API. A similar method is provided by the [Qpid JMS
client|setsetCsetClientIdsetClientIdsetClientIDsetClientIdsetClientID].
I don't see a similar method on the [FuseSource StompJMS
client|https://github.com/fusesource/stompjms/blob/master/stompjms-client/src/main/java/org/fusesource/stomp/jms/StompJmsConnectionFactory.java]
so I'm not sure exactly what you're using there. That said, Artemis supports
setting the {{client-id}} header on the {{CONNECT}} frame.
In the instances with Qpid and STOMP the client ID is present _at the time the
connection is made_ which is why it is then available on the
{{RemotingConnection}} passed to the security manager. I can update the broker
so that the same happens for the Core JMS client, but as noted previously, this
will rely on the fact that the client ID can be set on the
{{ConnectionFactory}} implementation which is not part of the specification.
The danger here is that if you ever moved to a different JMS broker this code
would break.
was (Author: jbertram):
Your attachment uses
{{org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory#setClientID}}.
This is a _convenience method_ provided by the Core JMS client and is **not**
part of the
[JMS|https://docs.oracle.com/javaee/7/api/javax/jms/ConnectionFactory.html] or
[Jakarta
Messaging|https://jakarta.ee/specifications/messaging/3.0/apidocs/jakarta/jms/connectionfactory]
API. A similar method is provided by the [Qpid JMS
client|setsetCsetClientIdsetClientIdsetClientIDsetClientIdsetClientID].
I don't see a similar method on the [FuseSource StompJMS
client|https://github.com/fusesource/stompjms/blob/master/stompjms-client/src/main/java/org/fusesource/stomp/jms/StompJmsConnectionFactory.java]
so I'm not sure exactly what you're using there. That said, Artemis supports
setting the {{client-id}} header on the {{CONNECT}} frame.
In the instances with Qpid and STOMP the client ID is present _at the time the
connection is made_ which is why it is then available on the
{{RemotingConnection}} passed to the security manager. I can update the broker
so that the same happens for the Core JMS client, but as noted previously, this
will rely on the fact that the client ID can be set on the
{{ConnectionFactory}} implementation which is not part of the specification.
The danger here is that if you ever moved to a different JMS broker this code
would break.
> Setting clientID in artemis-jms-client has no effect
>
>
> Key: ARTEMIS-1921
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1921
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
>Affects Versions: 2.6.1
>Reporter: Johan Stenberg
>Priority: Major
> Attachments: Artemis1921_CoreJmsClient_SetClientId_Test.java
>
>
> As opposite to Qpid JMS Client over AMPQ1.0 or FuseSource StompJMS client
> over STOMP, a clientID set on the JMS ConnectionFactory or the Connection in
> the Artemis JMS Client is not available on the broker via
> RemotingConnection#getClientID().
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (ARTEMIS-1921) Setting clientID in artemis-jms-client has no effect
[
https://issues.apache.org/jira/browse/ARTEMIS-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17837364#comment-17837364
]
Justin Bertram edited comment on ARTEMIS-1921 at 4/15/24 5:03 PM:
--
Your attachment uses
{{org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory#setClientID}}.
This is a _convenience method_ provided by the Core JMS client and is *not*
part of the
[JMS|https://docs.oracle.com/javaee/7/api/javax/jms/ConnectionFactory.html] or
[Jakarta
Messaging|https://jakarta.ee/specifications/messaging/3.0/apidocs/jakarta/jms/connectionfactory]
API. A similar method is provided by the [Qpid JMS
client|https://github.com/apache/qpid-jms/blob/e0c40397ed7380c7009acc1d5dfa39de1687d588/qpid-jms-client/src/main/java/org/apache/qpid/jms/JmsConnectionFactory.java#L783].
I don't see a similar method on the [FuseSource StompJMS
client|https://github.com/fusesource/stompjms/blob/master/stompjms-client/src/main/java/org/fusesource/stomp/jms/StompJmsConnectionFactory.java]
so I'm not sure exactly what you're using there. That said, Artemis supports
setting the {{client-id}} header on the {{CONNECT}} frame.
In the instances with Qpid and STOMP the client ID is present _at the time the
connection is made_ which is why it is then available on the
{{RemotingConnection}} passed to the security manager. I can update the broker
so that the same happens for the Core JMS client, but as noted previously, this
will rely on the fact that the client ID can be set on the
{{ConnectionFactory}} implementation which is not part of the specification.
The danger here is that if you ever moved to a different JMS broker this code
would break.
was (Author: jbertram):
Your attachment uses
{{org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory#setClientID}}.
This is a _convenience method_ provided by the Core JMS client and is *not*
part of the
[JMS|https://docs.oracle.com/javaee/7/api/javax/jms/ConnectionFactory.html] or
[Jakarta
Messaging|https://jakarta.ee/specifications/messaging/3.0/apidocs/jakarta/jms/connectionfactory]
API. A similar method is provided by the [Qpid JMS
client|setsetCsetClientIdsetClientIdsetClientIDsetClientIdsetClientID].
I don't see a similar method on the [FuseSource StompJMS
client|https://github.com/fusesource/stompjms/blob/master/stompjms-client/src/main/java/org/fusesource/stomp/jms/StompJmsConnectionFactory.java]
so I'm not sure exactly what you're using there. That said, Artemis supports
setting the {{client-id}} header on the {{CONNECT}} frame.
In the instances with Qpid and STOMP the client ID is present _at the time the
connection is made_ which is why it is then available on the
{{RemotingConnection}} passed to the security manager. I can update the broker
so that the same happens for the Core JMS client, but as noted previously, this
will rely on the fact that the client ID can be set on the
{{ConnectionFactory}} implementation which is not part of the specification.
The danger here is that if you ever moved to a different JMS broker this code
would break.
> Setting clientID in artemis-jms-client has no effect
>
>
> Key: ARTEMIS-1921
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1921
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
>Affects Versions: 2.6.1
>Reporter: Johan Stenberg
>Priority: Major
> Attachments: Artemis1921_CoreJmsClient_SetClientId_Test.java
>
>
> As opposite to Qpid JMS Client over AMPQ1.0 or FuseSource StompJMS client
> over STOMP, a clientID set on the JMS ConnectionFactory or the Connection in
> the Artemis JMS Client is not available on the broker via
> RemotingConnection#getClientID().
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ARTEMIS-1921) Setting clientID in artemis-jms-client has no effect
[
https://issues.apache.org/jira/browse/ARTEMIS-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17837364#comment-17837364
]
Justin Bertram commented on ARTEMIS-1921:
-
Your attachment uses
{{org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory#setClientID}}.
This is a _convenience method_ provided by the Core JMS client and is **not**
part of the
[JMS|https://docs.oracle.com/javaee/7/api/javax/jms/ConnectionFactory.html] or
[Jakarta
Messaging|https://jakarta.ee/specifications/messaging/3.0/apidocs/jakarta/jms/connectionfactory]
API. A similar method is provided by the [Qpid JMS
client|setsetCsetClientIdsetClientIdsetClientIDsetClientIdsetClientID].
I don't see a similar method on the [FuseSource StompJMS
client|https://github.com/fusesource/stompjms/blob/master/stompjms-client/src/main/java/org/fusesource/stomp/jms/StompJmsConnectionFactory.java]
so I'm not sure exactly what you're using there. That said, Artemis supports
setting the {{client-id}} header on the {{CONNECT}} frame.
In the instances with Qpid and STOMP the client ID is present _at the time the
connection is made_ which is why it is then available on the
{{RemotingConnection}} passed to the security manager. I can update the broker
so that the same happens for the Core JMS client, but as noted previously, this
will rely on the fact that the client ID can be set on the
{{ConnectionFactory}} implementation which is not part of the specification.
The danger here is that if you ever moved to a different JMS broker this code
would break.
> Setting clientID in artemis-jms-client has no effect
>
>
> Key: ARTEMIS-1921
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1921
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
>Affects Versions: 2.6.1
>Reporter: Johan Stenberg
>Priority: Major
> Attachments: Artemis1921_CoreJmsClient_SetClientId_Test.java
>
>
> As opposite to Qpid JMS Client over AMPQ1.0 or FuseSource StompJMS client
> over STOMP, a clientID set on the JMS ConnectionFactory or the Connection in
> the Artemis JMS Client is not available on the broker via
> RemotingConnection#getClientID().
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-4716) Improve Jakarta Messaging / JMS documentation
[
https://issues.apache.org/jira/browse/ARTEMIS-4716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram resolved ARTEMIS-4716.
-
Resolution: Information Provided
> Improve Jakarta Messaging / JMS documentation
> -
>
> Key: ARTEMIS-4716
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4716
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: JMS
>Affects Versions: 2.33.0
>Reporter: Daniel Martin
>Priority: Minor
>
> I'm struggling to understand [these
> instructions|https://activemq.apache.org/components/artemis/documentation/latest/using-jms.html]
> to use Artemis in the context of Jakarta Messaging which perhaps could be
> updated / simplified / improved.
> At the moment, I'm depending on {{artemis-jakarta-client}} and manually
> instantiating {{ActiveMQConnectionFactory}}. While investigating a memory
> leak that may come from my usage of ActiveMQ, I wanted to simplify this part
> and rely on dependency injection instead. However, I don't begin to
> understand how to do such thing.
> My expectation was to be able to use the {{@Inject}} annotation to get a
> reference to a {{ConnectionFactory}}, {{JMSContext}}, or similar and to be
> able to provide configuration such as broker address and credentials
> _somewhere_ as to end up with a reference to a {{Connection}} which is
> ultimately what I need. Is this possible? What's the recommended way? Is
> there any (working) reference examples?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4716) Improve Jakarta Messaging / JMS documentation
[
https://issues.apache.org/jira/browse/ARTEMIS-4716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17837325#comment-17837325
]
Justin Bertram commented on ARTEMIS-4716:
-
There are general guides for writing EE code that provide examples (e.g.
[here's one|https://www.baeldung.com/java-ee-cdi] for EE CDI), but I'm not
aware of anything that covers the specifics for every application server.
If you need a JCA RA archive for ActiveMQ Artemis you can create one by
following these steps:
# Clone https://github.com/apache/activemq-artemis-examples
# Follow the [_Getting
Started_|https://github.com/apache/activemq-artemis-examples#getting-started]
instructions
# Execute the following:
{noformat}
$ cd examples/features/sub-modules/artemis-jakarta-ra-rar/
$ mvn clean verify{noformat}
The {{rar}} file will be in the {{target}} directory. Deploy that based on the
instructions provided by your application server.
> Improve Jakarta Messaging / JMS documentation
> -
>
> Key: ARTEMIS-4716
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4716
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: JMS
>Affects Versions: 2.33.0
>Reporter: Daniel Martin
>Priority: Minor
>
> I'm struggling to understand [these
> instructions|https://activemq.apache.org/components/artemis/documentation/latest/using-jms.html]
> to use Artemis in the context of Jakarta Messaging which perhaps could be
> updated / simplified / improved.
> At the moment, I'm depending on {{artemis-jakarta-client}} and manually
> instantiating {{ActiveMQConnectionFactory}}. While investigating a memory
> leak that may come from my usage of ActiveMQ, I wanted to simplify this part
> and rely on dependency injection instead. However, I don't begin to
> understand how to do such thing.
> My expectation was to be able to use the {{@Inject}} annotation to get a
> reference to a {{ConnectionFactory}}, {{JMSContext}}, or similar and to be
> able to provide configuration such as broker address and credentials
> _somewhere_ as to end up with a reference to a {{Connection}} which is
> ultimately what I need. Is this possible? What's the recommended way? Is
> there any (working) reference examples?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4719) Artemis Metrics plugin reports wrong data
[
https://issues.apache.org/jira/browse/ARTEMIS-4719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17837297#comment-17837297
]
Justin Bertram commented on ARTEMIS-4719:
-
Every queue should have a corresponding {{artemis.message.count}} metric. The
metric will be tagged with the name of the related {{address}} and {{queue}}.
The fact that your graph is labeled as "eESB Messages Count" indicates to me
that it's aggregating the {{artemis.message.count}} metric from more than one
queue, perhaps every queue on the broker. Do you know what the {{address}} and
{{queue}} tags are for this graph? Are you 100% certain it's not aggregating
anything and is only for a single queue?
What metrics plugin are you using?
Do you have a way to reproduce this?
> Artemis Metrics plugin reports wrong data
> -
>
> Key: ARTEMIS-4719
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4719
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
>Affects Versions: 2.32.1
>Reporter: Mohanavalli A
>Priority: Minor
> Attachments: 6m peak.png, image-2024-04-10-12-46-10-394.png
>
>
> We are using an Artemis broker metrics plugin to monitor the message count on
> each address of the broker. Recently we have noticed that the plugin reported
> values which were not realistic and not matching with any of our other
> monitoring information available.
> !6m peak.png|width=502,height=471!
> For a particular address, the plugin reported below values every minute. The
> messages count increase from 437k to 5million and 451K to 6million and a fall
> from 6M to 462 K are not realistic considering the producer/consumers
> capacity. From the values 5M and 6M look to be fake values.
> !image-2024-04-10-12-46-10-394.png|width=211,height=429!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4719) Artemis Metrics plugin reports wrong data
[ https://issues.apache.org/jira/browse/ARTEMIS-4719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram updated ARTEMIS-4719: Description: We are using an Artemis broker metrics plugin to monitor the message count on each address of the broker. Recently we have noticed that the plugin reported values which were not realistic and not matching with any of our other monitoring information available. !6m peak.png|width=502,height=471! For a particular address, the plugin reported below values every minute. The messages count increase from 437k to 5million and 451K to 6million and a fall from 6M to 462 K are not realistic considering the producer/consumers capacity. From the values 5M and 6M look to be fake values. !image-2024-04-10-12-46-10-394.png|width=211,height=429! was: Hi Team, We are using the Artemis broker metrics plugin to monitor the message count on each address of the broker. Recently we have noticed that the plugin reported values which were not realistic and not matching with any of our other monitoring information available. !6m peak.png|width=502,height=471! For a particular address, the plugin reported below values every minute. The messages count increase from 437k to 5million and 451K to 6million and a fall from 6M to 462 K are not realistic considering the producer/consumers capacity. From the values 5M and 6M look to be fake values. !image-2024-04-10-12-46-10-394.png|width=211,height=429! > Artemis Metrics plugin reports wrong data > - > > Key: ARTEMIS-4719 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4719 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Broker >Affects Versions: 2.32.1 >Reporter: Mohanavalli A >Priority: Minor > Attachments: 6m peak.png, image-2024-04-10-12-46-10-394.png > > > We are using an Artemis broker metrics plugin to monitor the message count on > each address of the broker. Recently we have noticed that the plugin reported > values which were not realistic and not matching with any of our other > monitoring information available. > !6m peak.png|width=502,height=471! > For a particular address, the plugin reported below values every minute. The > messages count increase from 437k to 5million and 451K to 6million and a fall > from 6M to 462 K are not realistic considering the producer/consumers > capacity. From the values 5M and 6M look to be fake values. > !image-2024-04-10-12-46-10-394.png|width=211,height=429! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4719) Artemis Metrics plugin reports wrong data
[ https://issues.apache.org/jira/browse/ARTEMIS-4719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram updated ARTEMIS-4719: Affects Version/s: 2.32.1 (was: 2.23.1) > Artemis Metrics plugin reports wrong data > - > > Key: ARTEMIS-4719 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4719 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Broker >Affects Versions: 2.32.1 >Reporter: Mohanavalli A >Priority: Minor > Attachments: 6m peak.png, image-2024-04-10-12-46-10-394.png > > > Hi Team, > > We are using the Artemis broker metrics plugin to monitor the message count > on each address of the broker. Recently we have noticed that the plugin > reported values which were not realistic and not matching with any of our > other monitoring information available. > !6m peak.png|width=502,height=471! > > For a particular address, the plugin reported below values every minute. The > messages count increase from 437k to 5million and 451K to 6million and a fall > from 6M to 462 K are not realistic considering the producer/consumers > capacity. From the values 5M and 6M look to be fake values. > > !image-2024-04-10-12-46-10-394.png|width=211,height=429! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4724) Upgrade karaf version to 4.4.6
[ https://issues.apache.org/jira/browse/ARTEMIS-4724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17837263#comment-17837263 ] ASF subversion and git services commented on ARTEMIS-4724: -- Commit 021993fe7ccbd39936c2b6450a7e9d9a551ed9e2 in activemq-artemis's branch refs/heads/main from Domenico Francesco Bruscino [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=021993fe7c ] ARTEMIS-4724 Upgrade karaf version to 4.4.6 > Upgrade karaf version to 4.4.6 > -- > > Key: ARTEMIS-4724 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4724 > Project: ActiveMQ Artemis > Issue Type: Dependency upgrade >Reporter: Domenico Francesco Bruscino >Assignee: Domenico Francesco Bruscino >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-4724) Upgrade karaf version to 4.4.6
[ https://issues.apache.org/jira/browse/ARTEMIS-4724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Domenico Francesco Bruscino resolved ARTEMIS-4724. -- Fix Version/s: 2.34.0 Resolution: Fixed > Upgrade karaf version to 4.4.6 > -- > > Key: ARTEMIS-4724 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4724 > Project: ActiveMQ Artemis > Issue Type: Dependency upgrade >Reporter: Domenico Francesco Bruscino >Assignee: Domenico Francesco Bruscino >Priority: Major > Fix For: 2.34.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4724) Upgrade karaf version to 4.4.6
[ https://issues.apache.org/jira/browse/ARTEMIS-4724?focusedWorklogId=914642=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-914642 ] ASF GitHub Bot logged work on ARTEMIS-4724: --- Author: ASF GitHub Bot Created on: 15/Apr/24 13:32 Start Date: 15/Apr/24 13:32 Worklog Time Spent: 10m Work Description: brusdev merged PR #4886: URL: https://github.com/apache/activemq-artemis/pull/4886 Issue Time Tracking --- Worklog Id: (was: 914642) Time Spent: 20m (was: 10m) > Upgrade karaf version to 4.4.6 > -- > > Key: ARTEMIS-4724 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4724 > Project: ActiveMQ Artemis > Issue Type: Dependency upgrade >Reporter: Domenico Francesco Bruscino >Assignee: Domenico Francesco Bruscino >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4582) add view and edit permissions to extend security-settings rbac for management operations
[ https://issues.apache.org/jira/browse/ARTEMIS-4582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17837241#comment-17837241 ] ASF subversion and git services commented on ARTEMIS-4582: -- Commit 66caefe1d7309cf453f98dd1d048ebe0a3aaef28 in activemq-artemis's branch refs/heads/main from Gary Tully [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=66caefe1d7 ] ARTEMIS-4582 - fix missed change from update to view naming in the doc > add view and edit permissions to extend security-settings rbac for management > operations > > > Key: ARTEMIS-4582 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4582 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Broker, Configuration, JMX, Web Console >Affects Versions: 2.31.0 >Reporter: Gary Tully >Assignee: Gary Tully >Priority: Major > Fix For: 2.33.0 > > Time Spent: 4h 40m > Remaining Estimate: 0h > > we have the manage permission that allows sending to the management address, > to access any control resource. We don't however distinguish what a user can > do. > We should segment control operations into categories: CRUD provides a basis > view for get/is (Read) > edit for set or operations that mutate or modify. > We allow this sort of configuration via management.xml for jmx mbean access > but using a different model based on object name. > All of the mbeans delegate to the control resources. > If we add these two additional permissions then we can have a single rbac > model (that supports config reload) and more granularity on control resource > access from the management address. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4582) add view and edit permissions to extend security-settings rbac for management operations
[ https://issues.apache.org/jira/browse/ARTEMIS-4582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17837231#comment-17837231 ] ASF subversion and git services commented on ARTEMIS-4582: -- Commit e43707aba953c4edc33e9370fa89526a5337e3f0 in activemq-artemis's branch refs/heads/main from Gary Tully [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=e43707aba9 ] ARTEMIS-4582 - doc update to remove incorrect info > add view and edit permissions to extend security-settings rbac for management > operations > > > Key: ARTEMIS-4582 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4582 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Broker, Configuration, JMX, Web Console >Affects Versions: 2.31.0 >Reporter: Gary Tully >Assignee: Gary Tully >Priority: Major > Fix For: 2.33.0 > > Time Spent: 4h 40m > Remaining Estimate: 0h > > we have the manage permission that allows sending to the management address, > to access any control resource. We don't however distinguish what a user can > do. > We should segment control operations into categories: CRUD provides a basis > view for get/is (Read) > edit for set or operations that mutate or modify. > We allow this sort of configuration via management.xml for jmx mbean access > but using a different model based on object name. > All of the mbeans delegate to the control resources. > If we add these two additional permissions then we can have a single rbac > model (that supports config reload) and more granularity on control resource > access from the management address. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-1827) Improve HA tests to use remote brokers and not invm
[ https://issues.apache.org/jira/browse/ARTEMIS-1827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Taylor closed ARTEMIS-1827. Resolution: Invalid > Improve HA tests to use remote brokers and not invm > --- > > Key: ARTEMIS-1827 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1827 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Andy Taylor >Assignee: Andy Taylor >Priority: Major > > This could possibly be implemented using Arquillian which allows resource > life cycle control -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4528) TLS support PEM format for key and trust store type
[ https://issues.apache.org/jira/browse/ARTEMIS-4528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17837207#comment-17837207 ] Robbie Gemmell commented on ARTEMIS-4528: - (Though only in the sense that its possible to operate without it, so you could now _exclude_ it, but its still there otherwise...i.e pem-keystore still isnt listed as an optional dependency in the maven sense). > TLS support PEM format for key and trust store type > --- > > Key: ARTEMIS-4528 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4528 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Configuration >Affects Versions: 2.31.0 >Reporter: Gary Tully >Assignee: Gary Tully >Priority: Major > Fix For: 2.32.0 > > Time Spent: 4.5h > Remaining Estimate: 0h > > managing key and trust store passwords when the credentials are securely > stored or managed by other means is a nuisance. > there is a nice PEM keystore provider at: > [https://github.com/ctron/pem-keystore] > This gives us an intuitive way to easily reference a simple cert or key > without a password as is the case with jsk or pkcs12 > name="netty-ssl-acceptor">tcp://localhost:5500?sslEnabled=true;keyStorePath=server-keystore.pem;keyStoreType=PEM > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4724) Upgrade karaf version to 4.4.6
[ https://issues.apache.org/jira/browse/ARTEMIS-4724?focusedWorklogId=914615=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-914615 ] ASF GitHub Bot logged work on ARTEMIS-4724: --- Author: ASF GitHub Bot Created on: 15/Apr/24 11:20 Start Date: 15/Apr/24 11:20 Worklog Time Spent: 10m Work Description: brusdev opened a new pull request, #4886: URL: https://github.com/apache/activemq-artemis/pull/4886 (no comment) Issue Time Tracking --- Worklog Id: (was: 914615) Remaining Estimate: 0h Time Spent: 10m > Upgrade karaf version to 4.4.6 > -- > > Key: ARTEMIS-4724 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4724 > Project: ActiveMQ Artemis > Issue Type: Dependency upgrade >Reporter: Domenico Francesco Bruscino >Assignee: Domenico Francesco Bruscino >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ARTEMIS-4724) Upgrade karaf version to 4.4.6
Domenico Francesco Bruscino created ARTEMIS-4724: Summary: Upgrade karaf version to 4.4.6 Key: ARTEMIS-4724 URL: https://issues.apache.org/jira/browse/ARTEMIS-4724 Project: ActiveMQ Artemis Issue Type: Dependency upgrade Reporter: Domenico Francesco Bruscino Assignee: Domenico Francesco Bruscino -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4528) TLS support PEM format for key and trust store type
[ https://issues.apache.org/jira/browse/ARTEMIS-4528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17837168#comment-17837168 ] Gary Tully commented on ARTEMIS-4528: - ARTEMIS-4710 makes the bc dependency optional > TLS support PEM format for key and trust store type > --- > > Key: ARTEMIS-4528 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4528 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Configuration >Affects Versions: 2.31.0 >Reporter: Gary Tully >Assignee: Gary Tully >Priority: Major > Fix For: 2.32.0 > > Time Spent: 4.5h > Remaining Estimate: 0h > > managing key and trust store passwords when the credentials are securely > stored or managed by other means is a nuisance. > there is a nice PEM keystore provider at: > [https://github.com/ctron/pem-keystore] > This gives us an intuitive way to easily reference a simple cert or key > without a password as is the case with jsk or pkcs12 > name="netty-ssl-acceptor">tcp://localhost:5500?sslEnabled=true;keyStorePath=server-keystore.pem;keyStoreType=PEM > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-1968) Kerberos authentication/authorization support for STOMP and Openwire transports
[ https://issues.apache.org/jira/browse/ARTEMIS-1968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully closed ARTEMIS-1968. --- Resolution: Won't Do The amqp kerberos support sits under SASL, I don' see us adding SASL to STOMP or Openwire for this use case. Things like JWT tokens can already be provided over mtls in the password field for all transports/protocols and that is a viable path forward to externalise auth and have simple expiry/rotations. An alternative is plain mtls for identity with JAAS cert login nodule. > Kerberos authentication/authorization support for STOMP and Openwire > transports > --- > > Key: ARTEMIS-1968 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1968 > Project: ActiveMQ Artemis > Issue Type: New Feature > Components: OpenWire, STOMP >Affects Versions: 2.6.2 >Reporter: Abhi >Priority: Major > > I am looking to setup Artemis for my use-cases that are currently using > ActiveMQ v5.14.1 and want to use Kerberos auth which isn't available in > ActiveMQ currently. In Artemis, currently only AMQP transport supports > Kerberos auth. > Please add Kerberos auth to STOMP and Openwire. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4528) TLS support PEM format for key and trust store type
[ https://issues.apache.org/jira/browse/ARTEMIS-4528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17837141#comment-17837141 ] Gary Tully commented on ARTEMIS-4528: - I don't know if there is a better alternative, or a smaller subset of bc that will satisfy the need. The subsequent change to remove the direct reference means that the static dependency is not longer required, if will only be resolved at runtime at first use. see: https://github.com/apache/activemq-artemis/commit/bf1ea4128775c97e6c6fc6a0ab6921feaf8197d5 that helps, but I am not aware of an alternative to bc. > TLS support PEM format for key and trust store type > --- > > Key: ARTEMIS-4528 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4528 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Configuration >Affects Versions: 2.31.0 >Reporter: Gary Tully >Assignee: Gary Tully >Priority: Major > Fix For: 2.32.0 > > Time Spent: 4.5h > Remaining Estimate: 0h > > managing key and trust store passwords when the credentials are securely > stored or managed by other means is a nuisance. > there is a nice PEM keystore provider at: > [https://github.com/ctron/pem-keystore] > This gives us an intuitive way to easily reference a simple cert or key > without a password as is the case with jsk or pkcs12 > name="netty-ssl-acceptor">tcp://localhost:5500?sslEnabled=true;keyStorePath=server-keystore.pem;keyStoreType=PEM > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (ARTEMIS-4719) Artemis Metrics plugin reports wrong data
[ https://issues.apache.org/jira/browse/ARTEMIS-4719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17837138#comment-17837138 ] Mohanavalli A edited comment on ARTEMIS-4719 at 4/15/24 9:32 AM: - Sorry the broker version is 2.32.1. There is no aggregation of any other metrics, its just the `artemis.message.count`. was (Author: JIRAUSER300906): Sorry the broker version is 2.32.1 > Artemis Metrics plugin reports wrong data > - > > Key: ARTEMIS-4719 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4719 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Broker >Affects Versions: 2.23.1 >Reporter: Mohanavalli A >Priority: Minor > Attachments: 6m peak.png, image-2024-04-10-12-46-10-394.png > > > Hi Team, > > We are using the Artemis broker metrics plugin to monitor the message count > on each address of the broker. Recently we have noticed that the plugin > reported values which were not realistic and not matching with any of our > other monitoring information available. > !6m peak.png|width=502,height=471! > > For a particular address, the plugin reported below values every minute. The > messages count increase from 437k to 5million and 451K to 6million and a fall > from 6M to 462 K are not realistic considering the producer/consumers > capacity. From the values 5M and 6M look to be fake values. > > !image-2024-04-10-12-46-10-394.png|width=211,height=429! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4719) Artemis Metrics plugin reports wrong data
[ https://issues.apache.org/jira/browse/ARTEMIS-4719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17837138#comment-17837138 ] Mohanavalli A commented on ARTEMIS-4719: Sorry the broker version is 2.32.1 > Artemis Metrics plugin reports wrong data > - > > Key: ARTEMIS-4719 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4719 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Broker >Affects Versions: 2.23.1 >Reporter: Mohanavalli A >Priority: Minor > Attachments: 6m peak.png, image-2024-04-10-12-46-10-394.png > > > Hi Team, > > We are using the Artemis broker metrics plugin to monitor the message count > on each address of the broker. Recently we have noticed that the plugin > reported values which were not realistic and not matching with any of our > other monitoring information available. > !6m peak.png|width=502,height=471! > > For a particular address, the plugin reported below values every minute. The > messages count increase from 437k to 5million and 451K to 6million and a fall > from 6M to 462 K are not realistic considering the producer/consumers > capacity. From the values 5M and 6M look to be fake values. > > !image-2024-04-10-12-46-10-394.png|width=211,height=429! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (AMQ-9480) Update activemq-osgi import for Jetty 11
[ https://issues.apache.org/jira/browse/AMQ-9480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated AMQ-9480: -- Component/s: OSGi/Karaf > Update activemq-osgi import for Jetty 11 > > > Key: AMQ-9480 > URL: https://issues.apache.org/jira/browse/AMQ-9480 > Project: ActiveMQ Classic > Issue Type: Task > Components: OSGi/Karaf >Reporter: Matt Pavlovich >Assignee: Matt Pavlovich >Priority: Minor > Fix For: 6.2.0 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (AMQ-9479) Unable to Access ActiveMQ Web Console (webconsole-embedded.xml not found)
[
https://issues.apache.org/jira/browse/AMQ-9479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated AMQ-9479:
--
Affects Version/s: 5.18.3
> Unable to Access ActiveMQ Web Console (webconsole-embedded.xml not found)
> -
>
> Key: AMQ-9479
> URL: https://issues.apache.org/jira/browse/AMQ-9479
> Project: ActiveMQ Classic
> Issue Type: Bug
> Components: Web Console
>Affects Versions: 5.18.3
>Reporter: Nagaraju
>Assignee: Jean-Baptiste Onofré
>Priority: Major
>
> We are encountering an issue with accessing the ActiveMQ web console
> ({{{}/admin{}}}) in version 5.18.3 when running within a Docker container.
> The web console fails to start up and throws the following error:
> {{We have verified the deployment and installation of ActiveMQ within the
> Docker container and confirmed that all necessary files are included.}}
> {code:java}
> 2024-04-12T04:14:56.310393470Z WARN | Failed startup of context
> o.e.j.w.WebAppContext@1d99ee1b{ActiveMQ
> Console,/admin,file:///opt/activemq/webapps/admin/,UNAVAILABLE}
> 2024-04-12T04:14:56.310437252Z
> org.springframework.beans.factory.BeanDefinitionStoreException: IOException
> parsing XML document from ServletContext resource
> [/WEB-INF/webconsole-embedded.xml]; nested exception is
> java.io.FileNotFoundException: Could not open ServletContext resource
> [/WEB-INF/webconsole-embedded.xml]
> 2024-04-12T04:14:56.310447017Z at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:342)
> ~[spring-beans-5.3.30.jar:5.3.30]
> 2024-04-12T04:14:56.310449955Z at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:310)
> ~[spring-beans-5.3.30.jar:5.3.30]
> 2024-04-12T04:14:56.310454959Z at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:196)
> ~[spring-beans-5.3.30.jar:5.3.30]
> 2024-04-12T04:14:56.310457953Z at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:232)
> ~[spring-beans-5.3.30.jar:5.3.30]
> 2024-04-12T04:14:56.310460644Z at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:203)
> ~[spring-beans-5.3.30.jar:5.3.30]
> 2024-04-12T04:14:56.310463866Z at
> org.springframework.web.context.support.XmlWebApplicationContext.loadBeanDefinitions(XmlWebApplicationContext.java:125)
> ~[spring-web-5.3.30.jar:5.3.30]
> 2024-04-12T04:14:56.310466466Z at
> org.springframework.web.context.support.XmlWebApplicationContext.loadBeanDefinitions(XmlWebApplicationContext.java:94)
> ~[spring-web-5.3.30.jar:5.3.30]
> 2024-04-12T04:14:56.310471148Z at
> org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:130)
> ~[spring-context-5.3.30.jar:5.3.30]
> 2024-04-12T04:14:56.310473706Z at
> org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory(AbstractApplicationContext.java:671)
> ~[spring-context-5.3.30.jar:5.3.30]
> 2024-04-12T04:14:56.310476043Z at
> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:553)
> ~[spring-context-5.3.30.jar:5.3.30]
> 2024-04-12T04:14:56.310480906Z at
> org.apache.activemq.web.WebConsoleStarter.createWebapplicationContext(WebConsoleStarter.java:71)
> ~[?:?]
> 2024-04-12T04:14:56.310483550Z at
> org.apache.activemq.web.WebConsoleStarter.contextInitialized(WebConsoleStarter.java:44)
> ~[?:?]
> 2024-04-12T04:14:56.310486458Z at
> org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:1073)
> ~[jetty-server-9.4.53.v20231009.jar:9.4.53.v20231009]
> 2024-04-12T04:14:56.310489543Z at
> org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:572)
> ~[jetty-servlet-9.4.53.v20231009.jar:9.4.53.v20231009]
> 2024-04-12T04:14:56.310492245Z at
> org.eclipse.jetty.server.handler.ContextHandler.contextInitialized(ContextHandler.java:1002)
> ~[jetty-server-9.4.53.v20231009.jar:9.4.53.v20231009]
> 2024-04-12T04:14:56.310495282Z at
> org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:765)
> ~[jetty-servlet-9.4.53.v20231009.jar:9.4.53.v20231009]
> 2024-04-12T04:14:56.310497458Z at
> org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:379)
> ~[jetty-servlet-9.4.53.v20231009.jar:9.4.53.v20231009]
> 2024-04-12T04:14:56.310499318Z at
>
[jira] [Assigned] (AMQ-9479) Unable to Access ActiveMQ Web Console (webconsole-embedded.xml not found)
[
https://issues.apache.org/jira/browse/AMQ-9479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré reassigned AMQ-9479:
-
Assignee: Jean-Baptiste Onofré
> Unable to Access ActiveMQ Web Console (webconsole-embedded.xml not found)
> -
>
> Key: AMQ-9479
> URL: https://issues.apache.org/jira/browse/AMQ-9479
> Project: ActiveMQ Classic
> Issue Type: Bug
>Reporter: Nagaraju
>Assignee: Jean-Baptiste Onofré
>Priority: Major
>
> We are encountering an issue with accessing the ActiveMQ web console
> ({{{}/admin{}}}) in version 5.18.3 when running within a Docker container.
> The web console fails to start up and throws the following error:
> {{We have verified the deployment and installation of ActiveMQ within the
> Docker container and confirmed that all necessary files are included.}}
> {code:java}
> 2024-04-12T04:14:56.310393470Z WARN | Failed startup of context
> o.e.j.w.WebAppContext@1d99ee1b{ActiveMQ
> Console,/admin,file:///opt/activemq/webapps/admin/,UNAVAILABLE}
> 2024-04-12T04:14:56.310437252Z
> org.springframework.beans.factory.BeanDefinitionStoreException: IOException
> parsing XML document from ServletContext resource
> [/WEB-INF/webconsole-embedded.xml]; nested exception is
> java.io.FileNotFoundException: Could not open ServletContext resource
> [/WEB-INF/webconsole-embedded.xml]
> 2024-04-12T04:14:56.310447017Z at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:342)
> ~[spring-beans-5.3.30.jar:5.3.30]
> 2024-04-12T04:14:56.310449955Z at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:310)
> ~[spring-beans-5.3.30.jar:5.3.30]
> 2024-04-12T04:14:56.310454959Z at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:196)
> ~[spring-beans-5.3.30.jar:5.3.30]
> 2024-04-12T04:14:56.310457953Z at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:232)
> ~[spring-beans-5.3.30.jar:5.3.30]
> 2024-04-12T04:14:56.310460644Z at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:203)
> ~[spring-beans-5.3.30.jar:5.3.30]
> 2024-04-12T04:14:56.310463866Z at
> org.springframework.web.context.support.XmlWebApplicationContext.loadBeanDefinitions(XmlWebApplicationContext.java:125)
> ~[spring-web-5.3.30.jar:5.3.30]
> 2024-04-12T04:14:56.310466466Z at
> org.springframework.web.context.support.XmlWebApplicationContext.loadBeanDefinitions(XmlWebApplicationContext.java:94)
> ~[spring-web-5.3.30.jar:5.3.30]
> 2024-04-12T04:14:56.310471148Z at
> org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:130)
> ~[spring-context-5.3.30.jar:5.3.30]
> 2024-04-12T04:14:56.310473706Z at
> org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory(AbstractApplicationContext.java:671)
> ~[spring-context-5.3.30.jar:5.3.30]
> 2024-04-12T04:14:56.310476043Z at
> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:553)
> ~[spring-context-5.3.30.jar:5.3.30]
> 2024-04-12T04:14:56.310480906Z at
> org.apache.activemq.web.WebConsoleStarter.createWebapplicationContext(WebConsoleStarter.java:71)
> ~[?:?]
> 2024-04-12T04:14:56.310483550Z at
> org.apache.activemq.web.WebConsoleStarter.contextInitialized(WebConsoleStarter.java:44)
> ~[?:?]
> 2024-04-12T04:14:56.310486458Z at
> org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:1073)
> ~[jetty-server-9.4.53.v20231009.jar:9.4.53.v20231009]
> 2024-04-12T04:14:56.310489543Z at
> org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:572)
> ~[jetty-servlet-9.4.53.v20231009.jar:9.4.53.v20231009]
> 2024-04-12T04:14:56.310492245Z at
> org.eclipse.jetty.server.handler.ContextHandler.contextInitialized(ContextHandler.java:1002)
> ~[jetty-server-9.4.53.v20231009.jar:9.4.53.v20231009]
> 2024-04-12T04:14:56.310495282Z at
> org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:765)
> ~[jetty-servlet-9.4.53.v20231009.jar:9.4.53.v20231009]
> 2024-04-12T04:14:56.310497458Z at
> org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:379)
> ~[jetty-servlet-9.4.53.v20231009.jar:9.4.53.v20231009]
> 2024-04-12T04:14:56.310499318Z at
> org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1449)
>
[jira] [Commented] (AMQ-9479) Unable to Access ActiveMQ Web Console (webconsole-embedded.xml not found)
[
https://issues.apache.org/jira/browse/AMQ-9479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17837120#comment-17837120
]
Jean-Baptiste Onofré commented on AMQ-9479:
---
I gonna reproduce and fix that.
> Unable to Access ActiveMQ Web Console (webconsole-embedded.xml not found)
> -
>
> Key: AMQ-9479
> URL: https://issues.apache.org/jira/browse/AMQ-9479
> Project: ActiveMQ Classic
> Issue Type: Bug
>Reporter: Nagaraju
>Assignee: Jean-Baptiste Onofré
>Priority: Major
>
> We are encountering an issue with accessing the ActiveMQ web console
> ({{{}/admin{}}}) in version 5.18.3 when running within a Docker container.
> The web console fails to start up and throws the following error:
> {{We have verified the deployment and installation of ActiveMQ within the
> Docker container and confirmed that all necessary files are included.}}
> {code:java}
> 2024-04-12T04:14:56.310393470Z WARN | Failed startup of context
> o.e.j.w.WebAppContext@1d99ee1b{ActiveMQ
> Console,/admin,file:///opt/activemq/webapps/admin/,UNAVAILABLE}
> 2024-04-12T04:14:56.310437252Z
> org.springframework.beans.factory.BeanDefinitionStoreException: IOException
> parsing XML document from ServletContext resource
> [/WEB-INF/webconsole-embedded.xml]; nested exception is
> java.io.FileNotFoundException: Could not open ServletContext resource
> [/WEB-INF/webconsole-embedded.xml]
> 2024-04-12T04:14:56.310447017Z at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:342)
> ~[spring-beans-5.3.30.jar:5.3.30]
> 2024-04-12T04:14:56.310449955Z at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:310)
> ~[spring-beans-5.3.30.jar:5.3.30]
> 2024-04-12T04:14:56.310454959Z at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:196)
> ~[spring-beans-5.3.30.jar:5.3.30]
> 2024-04-12T04:14:56.310457953Z at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:232)
> ~[spring-beans-5.3.30.jar:5.3.30]
> 2024-04-12T04:14:56.310460644Z at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:203)
> ~[spring-beans-5.3.30.jar:5.3.30]
> 2024-04-12T04:14:56.310463866Z at
> org.springframework.web.context.support.XmlWebApplicationContext.loadBeanDefinitions(XmlWebApplicationContext.java:125)
> ~[spring-web-5.3.30.jar:5.3.30]
> 2024-04-12T04:14:56.310466466Z at
> org.springframework.web.context.support.XmlWebApplicationContext.loadBeanDefinitions(XmlWebApplicationContext.java:94)
> ~[spring-web-5.3.30.jar:5.3.30]
> 2024-04-12T04:14:56.310471148Z at
> org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:130)
> ~[spring-context-5.3.30.jar:5.3.30]
> 2024-04-12T04:14:56.310473706Z at
> org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory(AbstractApplicationContext.java:671)
> ~[spring-context-5.3.30.jar:5.3.30]
> 2024-04-12T04:14:56.310476043Z at
> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:553)
> ~[spring-context-5.3.30.jar:5.3.30]
> 2024-04-12T04:14:56.310480906Z at
> org.apache.activemq.web.WebConsoleStarter.createWebapplicationContext(WebConsoleStarter.java:71)
> ~[?:?]
> 2024-04-12T04:14:56.310483550Z at
> org.apache.activemq.web.WebConsoleStarter.contextInitialized(WebConsoleStarter.java:44)
> ~[?:?]
> 2024-04-12T04:14:56.310486458Z at
> org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:1073)
> ~[jetty-server-9.4.53.v20231009.jar:9.4.53.v20231009]
> 2024-04-12T04:14:56.310489543Z at
> org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:572)
> ~[jetty-servlet-9.4.53.v20231009.jar:9.4.53.v20231009]
> 2024-04-12T04:14:56.310492245Z at
> org.eclipse.jetty.server.handler.ContextHandler.contextInitialized(ContextHandler.java:1002)
> ~[jetty-server-9.4.53.v20231009.jar:9.4.53.v20231009]
> 2024-04-12T04:14:56.310495282Z at
> org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:765)
> ~[jetty-servlet-9.4.53.v20231009.jar:9.4.53.v20231009]
> 2024-04-12T04:14:56.310497458Z at
> org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:379)
> ~[jetty-servlet-9.4.53.v20231009.jar:9.4.53.v20231009]
> 2024-04-12T04:14:56.310499318Z at
>
[jira] [Updated] (AMQ-9479) Unable to Access ActiveMQ Web Console (webconsole-embedded.xml not found)
[
https://issues.apache.org/jira/browse/AMQ-9479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated AMQ-9479:
--
Component/s: Web Console
> Unable to Access ActiveMQ Web Console (webconsole-embedded.xml not found)
> -
>
> Key: AMQ-9479
> URL: https://issues.apache.org/jira/browse/AMQ-9479
> Project: ActiveMQ Classic
> Issue Type: Bug
> Components: Web Console
>Reporter: Nagaraju
>Assignee: Jean-Baptiste Onofré
>Priority: Major
>
> We are encountering an issue with accessing the ActiveMQ web console
> ({{{}/admin{}}}) in version 5.18.3 when running within a Docker container.
> The web console fails to start up and throws the following error:
> {{We have verified the deployment and installation of ActiveMQ within the
> Docker container and confirmed that all necessary files are included.}}
> {code:java}
> 2024-04-12T04:14:56.310393470Z WARN | Failed startup of context
> o.e.j.w.WebAppContext@1d99ee1b{ActiveMQ
> Console,/admin,file:///opt/activemq/webapps/admin/,UNAVAILABLE}
> 2024-04-12T04:14:56.310437252Z
> org.springframework.beans.factory.BeanDefinitionStoreException: IOException
> parsing XML document from ServletContext resource
> [/WEB-INF/webconsole-embedded.xml]; nested exception is
> java.io.FileNotFoundException: Could not open ServletContext resource
> [/WEB-INF/webconsole-embedded.xml]
> 2024-04-12T04:14:56.310447017Z at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:342)
> ~[spring-beans-5.3.30.jar:5.3.30]
> 2024-04-12T04:14:56.310449955Z at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:310)
> ~[spring-beans-5.3.30.jar:5.3.30]
> 2024-04-12T04:14:56.310454959Z at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:196)
> ~[spring-beans-5.3.30.jar:5.3.30]
> 2024-04-12T04:14:56.310457953Z at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:232)
> ~[spring-beans-5.3.30.jar:5.3.30]
> 2024-04-12T04:14:56.310460644Z at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:203)
> ~[spring-beans-5.3.30.jar:5.3.30]
> 2024-04-12T04:14:56.310463866Z at
> org.springframework.web.context.support.XmlWebApplicationContext.loadBeanDefinitions(XmlWebApplicationContext.java:125)
> ~[spring-web-5.3.30.jar:5.3.30]
> 2024-04-12T04:14:56.310466466Z at
> org.springframework.web.context.support.XmlWebApplicationContext.loadBeanDefinitions(XmlWebApplicationContext.java:94)
> ~[spring-web-5.3.30.jar:5.3.30]
> 2024-04-12T04:14:56.310471148Z at
> org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:130)
> ~[spring-context-5.3.30.jar:5.3.30]
> 2024-04-12T04:14:56.310473706Z at
> org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory(AbstractApplicationContext.java:671)
> ~[spring-context-5.3.30.jar:5.3.30]
> 2024-04-12T04:14:56.310476043Z at
> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:553)
> ~[spring-context-5.3.30.jar:5.3.30]
> 2024-04-12T04:14:56.310480906Z at
> org.apache.activemq.web.WebConsoleStarter.createWebapplicationContext(WebConsoleStarter.java:71)
> ~[?:?]
> 2024-04-12T04:14:56.310483550Z at
> org.apache.activemq.web.WebConsoleStarter.contextInitialized(WebConsoleStarter.java:44)
> ~[?:?]
> 2024-04-12T04:14:56.310486458Z at
> org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:1073)
> ~[jetty-server-9.4.53.v20231009.jar:9.4.53.v20231009]
> 2024-04-12T04:14:56.310489543Z at
> org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:572)
> ~[jetty-servlet-9.4.53.v20231009.jar:9.4.53.v20231009]
> 2024-04-12T04:14:56.310492245Z at
> org.eclipse.jetty.server.handler.ContextHandler.contextInitialized(ContextHandler.java:1002)
> ~[jetty-server-9.4.53.v20231009.jar:9.4.53.v20231009]
> 2024-04-12T04:14:56.310495282Z at
> org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:765)
> ~[jetty-servlet-9.4.53.v20231009.jar:9.4.53.v20231009]
> 2024-04-12T04:14:56.310497458Z at
> org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:379)
> ~[jetty-servlet-9.4.53.v20231009.jar:9.4.53.v20231009]
> 2024-04-12T04:14:56.310499318Z at
>
[jira] [Assigned] (AMQ-9478) Add unit test for modernized IntrospectionSupport
[ https://issues.apache.org/jira/browse/AMQ-9478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reassigned AMQ-9478: - Assignee: Jean-Baptiste Onofré > Add unit test for modernized IntrospectionSupport > - > > Key: AMQ-9478 > URL: https://issues.apache.org/jira/browse/AMQ-9478 > Project: ActiveMQ Classic > Issue Type: Task >Reporter: Matt Pavlovich >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 6.2.0 > > > Update unit test to verify transport connector and network connector uri > handling for > IntrospectionSupport to deal with TcpSocket properties > IntrospectionSupport to deal with SSLSocket properties -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (AMQ-9481) Concurrent access error attempting to consume messages via REST API in 5.18.2 or higher
[
https://issues.apache.org/jira/browse/AMQ-9481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17837118#comment-17837118
]
Jean-Baptiste Onofré commented on AMQ-9481:
---
This is due to the move from Jetty Continuation to AsyncRequestServlet. Let me
check with.
> Concurrent access error attempting to consume messages via REST API in 5.18.2
> or higher
> ---
>
> Key: AMQ-9481
> URL: https://issues.apache.org/jira/browse/AMQ-9481
> Project: ActiveMQ Classic
> Issue Type: Bug
>Affects Versions: 5.18.2, 5.18.3, 5.18.4
>Reporter: Andrew Smith
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 5.18.5, 6.1.3
>
>
> I am attempting to download a file from a queue via PowerShell. This can be
> done with the following 4 lines:
> {code:java}
> $user="admin"
> $pass="admin" | ConvertTo-SecureString -AsPlainText -Force
> $cred = New-Object Management.Automation.PSCredential($user,$pass)
> $status = Invoke-WebRequest -Uri
> "http://localhost:8161/api/message/TestQueue?type=queue=Importer;
> -Credential $cred -ContentType "application/base64"{code}
> When I do this using 5.18.1, it works and either downloads a file or times
> out after a short period if there are no files on the queue. When I run the
> same script against 5.18.2 or higher, I get the following error the first
> time I try to download a file after starting the broker:
> {noformat}
> Invoke-WebRequest : HTTP ERROR 500 AsyncContext timeout
> URI:/api/message/TestQueue
> STATUS:500
> MESSAGE:AsyncContext timeout
> SERVLET:MessageServlet
> At line:1 char:11
> + $status = Invoke-WebRequest -Uri "http://localhost:8161/api/message/T ...
> + ~~~
> + CategoryInfo : InvalidOperation:
> (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-WebRequest], WebExc
> eption
> + FullyQualifiedErrorId :
> WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand{noformat}
> Then every time I try after that I get the following:
> {noformat}
> Invoke-WebRequest : HTTP ERROR 500 javax.servlet.ServletException:
> javax.servlet.ServletException:
> javax.servlet.ServletException: Concurrent access to consumer is not supported
> URI:/api/message/TestQueue
> STATUS:500
> MESSAGE:javax.servlet.ServletException: javax.servlet.ServletException:
> javax.servlet.ServletException: Concurrent
> access to consumer is not supported
> SERVLET:MessageServlet
> CAUSED BY:javax.servlet.ServletException: javax.servlet.ServletException:
> javax.servlet.ServletException: Concurrent
> access to consumer is not supported
> CAUSED BY:javax.servlet.ServletException: javax.servlet.ServletException:
> Concurrent access to consumer is not
> supported
> CAUSED BY:javax.servlet.ServletException: Concurrent access to consumer is
> not supported
> Caused by:
> javax.servlet.ServletException: javax.servlet.ServletException:
> javax.servlet.ServletException: Concurrent access to
> consumer is not supported
> at
> org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:162)
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127)
> at org.eclipse.jetty.server.Server.handle(Server.java:516)
> at
> org.eclipse.jetty.server.HttpChannel.lambda$handle$1(HttpChannel.java:487)
> at org.eclipse.jetty.server.HttpChannel.dispatch(HttpChannel.java:732)
> at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:479)
> at
> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:277)
> at
> org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:311)
> at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:105)
> at
> org.eclipse.jetty.io.ChannelEndPoint$1.run(ChannelEndPoint.java:104)
> at
> org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:338)
> at
> org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:315)
> at
> org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:173)
> at
> org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:131)
> at
> org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:409)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:883)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:1034)
> at java.base/java.lang.Thread.run(Thread.java:1583)
> Caused by: javax.servlet.ServletException:
[jira] [Assigned] (AMQ-9481) Concurrent access error attempting to consume messages via REST API in 5.18.2 or higher
[
https://issues.apache.org/jira/browse/AMQ-9481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré reassigned AMQ-9481:
-
Assignee: Jean-Baptiste Onofré
> Concurrent access error attempting to consume messages via REST API in 5.18.2
> or higher
> ---
>
> Key: AMQ-9481
> URL: https://issues.apache.org/jira/browse/AMQ-9481
> Project: ActiveMQ Classic
> Issue Type: Bug
>Affects Versions: 5.18.2, 5.18.3, 5.18.4
>Reporter: Andrew Smith
>Assignee: Jean-Baptiste Onofré
>Priority: Major
>
> I am attempting to download a file from a queue via PowerShell. This can be
> done with the following 4 lines:
> {code:java}
> $user="admin"
> $pass="admin" | ConvertTo-SecureString -AsPlainText -Force
> $cred = New-Object Management.Automation.PSCredential($user,$pass)
> $status = Invoke-WebRequest -Uri
> "http://localhost:8161/api/message/TestQueue?type=queue=Importer;
> -Credential $cred -ContentType "application/base64"{code}
> When I do this using 5.18.1, it works and either downloads a file or times
> out after a short period if there are no files on the queue. When I run the
> same script against 5.18.2 or higher, I get the following error the first
> time I try to download a file after starting the broker:
> {noformat}
> Invoke-WebRequest : HTTP ERROR 500 AsyncContext timeout
> URI:/api/message/TestQueue
> STATUS:500
> MESSAGE:AsyncContext timeout
> SERVLET:MessageServlet
> At line:1 char:11
> + $status = Invoke-WebRequest -Uri "http://localhost:8161/api/message/T ...
> + ~~~
> + CategoryInfo : InvalidOperation:
> (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-WebRequest], WebExc
> eption
> + FullyQualifiedErrorId :
> WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand{noformat}
> Then every time I try after that I get the following:
> {noformat}
> Invoke-WebRequest : HTTP ERROR 500 javax.servlet.ServletException:
> javax.servlet.ServletException:
> javax.servlet.ServletException: Concurrent access to consumer is not supported
> URI:/api/message/TestQueue
> STATUS:500
> MESSAGE:javax.servlet.ServletException: javax.servlet.ServletException:
> javax.servlet.ServletException: Concurrent
> access to consumer is not supported
> SERVLET:MessageServlet
> CAUSED BY:javax.servlet.ServletException: javax.servlet.ServletException:
> javax.servlet.ServletException: Concurrent
> access to consumer is not supported
> CAUSED BY:javax.servlet.ServletException: javax.servlet.ServletException:
> Concurrent access to consumer is not
> supported
> CAUSED BY:javax.servlet.ServletException: Concurrent access to consumer is
> not supported
> Caused by:
> javax.servlet.ServletException: javax.servlet.ServletException:
> javax.servlet.ServletException: Concurrent access to
> consumer is not supported
> at
> org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:162)
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127)
> at org.eclipse.jetty.server.Server.handle(Server.java:516)
> at
> org.eclipse.jetty.server.HttpChannel.lambda$handle$1(HttpChannel.java:487)
> at org.eclipse.jetty.server.HttpChannel.dispatch(HttpChannel.java:732)
> at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:479)
> at
> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:277)
> at
> org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:311)
> at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:105)
> at
> org.eclipse.jetty.io.ChannelEndPoint$1.run(ChannelEndPoint.java:104)
> at
> org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:338)
> at
> org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:315)
> at
> org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:173)
> at
> org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:131)
> at
> org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:409)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:883)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:1034)
> at java.base/java.lang.Thread.run(Thread.java:1583)
> Caused by: javax.servlet.ServletException: javax.servlet.ServletException:
> Concurrent access to consumer is not
> supported
> at
>
[jira] [Updated] (AMQ-9481) Concurrent access error attempting to consume messages via REST API in 5.18.2 or higher
[
https://issues.apache.org/jira/browse/AMQ-9481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated AMQ-9481:
--
Fix Version/s: 6.1.3
5.18.5
> Concurrent access error attempting to consume messages via REST API in 5.18.2
> or higher
> ---
>
> Key: AMQ-9481
> URL: https://issues.apache.org/jira/browse/AMQ-9481
> Project: ActiveMQ Classic
> Issue Type: Bug
>Affects Versions: 5.18.2, 5.18.3, 5.18.4
>Reporter: Andrew Smith
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 5.18.5, 6.1.3
>
>
> I am attempting to download a file from a queue via PowerShell. This can be
> done with the following 4 lines:
> {code:java}
> $user="admin"
> $pass="admin" | ConvertTo-SecureString -AsPlainText -Force
> $cred = New-Object Management.Automation.PSCredential($user,$pass)
> $status = Invoke-WebRequest -Uri
> "http://localhost:8161/api/message/TestQueue?type=queue=Importer;
> -Credential $cred -ContentType "application/base64"{code}
> When I do this using 5.18.1, it works and either downloads a file or times
> out after a short period if there are no files on the queue. When I run the
> same script against 5.18.2 or higher, I get the following error the first
> time I try to download a file after starting the broker:
> {noformat}
> Invoke-WebRequest : HTTP ERROR 500 AsyncContext timeout
> URI:/api/message/TestQueue
> STATUS:500
> MESSAGE:AsyncContext timeout
> SERVLET:MessageServlet
> At line:1 char:11
> + $status = Invoke-WebRequest -Uri "http://localhost:8161/api/message/T ...
> + ~~~
> + CategoryInfo : InvalidOperation:
> (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-WebRequest], WebExc
> eption
> + FullyQualifiedErrorId :
> WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand{noformat}
> Then every time I try after that I get the following:
> {noformat}
> Invoke-WebRequest : HTTP ERROR 500 javax.servlet.ServletException:
> javax.servlet.ServletException:
> javax.servlet.ServletException: Concurrent access to consumer is not supported
> URI:/api/message/TestQueue
> STATUS:500
> MESSAGE:javax.servlet.ServletException: javax.servlet.ServletException:
> javax.servlet.ServletException: Concurrent
> access to consumer is not supported
> SERVLET:MessageServlet
> CAUSED BY:javax.servlet.ServletException: javax.servlet.ServletException:
> javax.servlet.ServletException: Concurrent
> access to consumer is not supported
> CAUSED BY:javax.servlet.ServletException: javax.servlet.ServletException:
> Concurrent access to consumer is not
> supported
> CAUSED BY:javax.servlet.ServletException: Concurrent access to consumer is
> not supported
> Caused by:
> javax.servlet.ServletException: javax.servlet.ServletException:
> javax.servlet.ServletException: Concurrent access to
> consumer is not supported
> at
> org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:162)
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127)
> at org.eclipse.jetty.server.Server.handle(Server.java:516)
> at
> org.eclipse.jetty.server.HttpChannel.lambda$handle$1(HttpChannel.java:487)
> at org.eclipse.jetty.server.HttpChannel.dispatch(HttpChannel.java:732)
> at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:479)
> at
> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:277)
> at
> org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:311)
> at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:105)
> at
> org.eclipse.jetty.io.ChannelEndPoint$1.run(ChannelEndPoint.java:104)
> at
> org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:338)
> at
> org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:315)
> at
> org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:173)
> at
> org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:131)
> at
> org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:409)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:883)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:1034)
> at java.base/java.lang.Thread.run(Thread.java:1583)
> Caused by: javax.servlet.ServletException: javax.servlet.ServletException:
> Concurrent access to consumer is not
> supported
> at
>
