[jira] [Resolved] (ARTEMIS-2492) [Doc] Confusing/old paragraph in clusters.md
[
https://issues.apache.org/jira/browse/ARTEMIS-2492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram resolved ARTEMIS-2492.
-
Fix Version/s: 2.34.0
Resolution: Fixed
> [Doc] Confusing/old paragraph in clusters.md
>
>
> Key: ARTEMIS-2492
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2492
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Reporter: Laurent Bigonville
>Assignee: Justin Bertram
>Priority: Trivial
> Fix For: 2.34.0
>
>
> Hello
> On line 372 in clusters.md the documentation is saying:
>
> {noformat}
> The element `discovery-group-ref` specifies the name of a discovery
> group defined in `broker.xml`.{noformat}
> But there is no such _discovery-group-ref_ element in the example above.
> Is that some left over?
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ARTEMIS-2492) [Doc] Confusing/old paragraph in clusters.md
[
https://issues.apache.org/jira/browse/ARTEMIS-2492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836417#comment-17836417
]
ASF subversion and git services commented on ARTEMIS-2492:
--
Commit aff360c70ee48bfde106d55d30858156da2b9523 in activemq-artemis's branch
refs/heads/main from Justin Bertram
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=aff360c70e ]
ARTEMIS-2492 remove defuct doc snippet
> [Doc] Confusing/old paragraph in clusters.md
>
>
> Key: ARTEMIS-2492
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2492
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Reporter: Laurent Bigonville
>Assignee: Justin Bertram
>Priority: Trivial
>
> Hello
> On line 372 in clusters.md the documentation is saying:
>
> {noformat}
> The element `discovery-group-ref` specifies the name of a discovery
> group defined in `broker.xml`.{noformat}
> But there is no such _discovery-group-ref_ element in the example above.
> Is that some left over?
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-3267) REST API has no params for authentication in broker
[
https://issues.apache.org/jira/browse/ARTEMIS-3267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram resolved ARTEMIS-3267.
-
Resolution: Won't Fix
The REST messaging API was deprecated and removed.
> REST API has no params for authentication in broker
> ---
>
> Key: ARTEMIS-3267
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3267
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: API
>Reporter: Andrey Danilenko
>Priority: Major
>
> Starting web application with rest api ends up with error _AMQ229031: Unable
> to validate user from . Username: null,_ if option *--allow-anonymous=Y* not
> applied while creating artemis instance. Because there is no way to pass
> authentication parameters via {{__}} - only protocol,
> host and port are being parsed. Anonymous connections are not allowed for
> commercial operation. How to solve this ?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-2469) Deprecate old JGroups properties syntax
[
https://issues.apache.org/jira/browse/ARTEMIS-2469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram resolved ARTEMIS-2469.
-
Assignee: Justin Bertram
Resolution: Duplicate
> Deprecate old JGroups properties syntax
> ---
>
> Key: ARTEMIS-2469
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2469
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Reporter: Igor Korolev
>Assignee: Justin Bertram
>Priority: Minor
>
> Quoting the
> [doc|https://activemq.apache.org/components/artemis/documentation/latest/using-jms.html]:
> {quote}
> Lastly, the jgroups scheme is supported which provides an alternative to the
> udp scheme for server discovery. The URL pattern is either
> jgroups://channelName?file=jgroups-xml-conf-filename where
> jgroups-xml-conf-filename refers to an XML file on the classpath that
> contains the JGroups configuration or it can be
> jgroups://channelName?properties=some-jgroups-properties. In both instance
> the channelName is the name given to the jgroups channel created.{quote}
> The problem is that the latter syntax (one without an XML file) relies on the
> JGroups old-style config parser, which was removed in JGroups 4. I suggest to
> deprecate it, remove it from the docs and at some point drop it from the code
> so that it allows us to upgrade to JGroups 4+ in the future.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ARTEMIS-3787) Allow ignoring validation of JMS property names
[ https://issues.apache.org/jira/browse/ARTEMIS-3787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836414#comment-17836414 ] Justin Bertram commented on ARTEMIS-3787: - Why not simply use the Qpid JMS client instead of the Core JMS client? > Allow ignoring validation of JMS property names > --- > > Key: ARTEMIS-3787 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3787 > Project: ActiveMQ Artemis > Issue Type: New Feature > Components: JMS >Affects Versions: 2.21.0 >Reporter: Vuk Vasic >Priority: Major > > Apache Qpid and Redhat AMQ support setting: > *jms.validatePropertyNames* to false which allows headers such as > X-Request-ID or cloudevents:id to be passed to the message broker. > > URLs: > https://access.redhat.com/documentation/en-us/red_hat_amq/7.2/html-single/using_the_amq_jms_client/index > [Client configuration - Apache > Qpid™|https://qpid.apache.org/releases/qpid-jms-0.51.0/docs/index.html] > > ActiveMQ Artemis should support this also on JMS Java Client in order to > allow the implementation of standards such as Cloud Events. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-3387) LDAPLoginModule using ssl with specific truststore and password
[ https://issues.apache.org/jira/browse/ARTEMIS-3387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram resolved ARTEMIS-3387. - Resolution: Won't Do > LDAPLoginModule using ssl with specific truststore and password > --- > > Key: ARTEMIS-3387 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3387 > Project: ActiveMQ Artemis > Issue Type: Wish > Components: JAAS >Reporter: Paul Vogt >Priority: Minor > > Using ldaps requires to specify a truststore if the CA certificate of the > ldap server is not in the cacerts file. The truststore can be set using > command line parameters like > -Djavax.net.ssl.trustStore=/appl/amq/security/paul_1_test/paul_1_test_ts.p12 > -Djavax.net.ssl.trustStorePassword=changeit > -Djavax.net.ssl.trustStoreType=PKCS12 > However this shows the truststore password with the ps -ef command. > Desired solution : adding 3 properties to > org.apache.activemq.artemis.spi.core.security.jaas.LDAPLoginModule > connectionTrustStore= > connectionTrustStorePassword= > connectionTrustStoreType= > > So the truststore can be specified without showing it in the process list. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-3857) Few issues with federation documentation
[
https://issues.apache.org/jira/browse/ARTEMIS-3857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram updated ARTEMIS-3857:
Component/s: Documentation
> Few issues with federation documentation
>
>
> Key: ARTEMIS-3857
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3857
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Documentation, Federation
>Affects Versions: 2.22.0
>Reporter: Ievgen Popovych
>Priority: Major
>
> Documentation on federation seem to be outdated or broken in some places.
> Some examples include:
> * {{policy-set}} is not shown/used while it seems to be required
> * in queue federation document, statement ??All of the configuration needed
> to establish the upstream links and the federated queue is in the downstream
> broker?? is given globally, but is only true for upstream configuration if I
> understand correctly.
> * in queue federation document, in downstream federation section, statement
> ??The benefit of this is being able to configure everything for federation on
> one broker in some cases to make it easier, such as a hub and spoke
> topology.?? is a bit misleading (IMO) since it highly depends on topology and
> desired message flow direction... I would suggest rephrasing to emphasize
> that this is _only_ beneficial in those cases and _only_ for having
> configuration in one place as it does not influence connection establishment
> direction, etc.
> * federation is not documented in {{Configuration Reference}} at all
--
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
]
Nagaraju updated AMQ-9479:
--
Description:
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)
~[jetty-webapp-9.4.53.v20231009.jar:9.4.53.v20231009]
2024-04-12T04:14:56.310501440Z at
org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1414)
~[jetty-webapp-9.4.53.v20231009.jar:9.4.53.v20231009]
2024-04-12T04:14:56.310668330Z at
org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:916)
~[jetty-server-9.4.53.v20231009.jar:9.4.53.v20231009]
2024-04-12T04:14:56.310688172Z at
org.eclipse.jetty.servlet.ServletContextHandler.doStart(ServletContextHandler.java:288)
~[jetty-servlet-9.4.53.v20231009.jar:9.4.53.v20231009]
2024-04-12T04:14:56.310694055Z 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
]
Nagaraju updated AMQ-9479:
--
Description:
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.}}
{{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)
~[jetty-webapp-9.4.53.v20231009.jar:9.4.53.v20231009]}}
{{2024-04-12T04:14:56.310501440Z at
org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1414)
~[jetty-webapp-9.4.53.v20231009.jar:9.4.53.v20231009]}}
{{2024-04-12T04:14:56.310668330Z at
org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:916)
~[jetty-server-9.4.53.v20231009.jar:9.4.53.v20231009]}}
{{2024-04-12T04:14:56.310688172Z at
org.eclipse.jetty.servlet.ServletContextHandler.doStart(ServletContextHandler.java:288)
[jira] [Created] (AMQ-9479) Unable to Access ActiveMQ Web Console (webconsole-embedded.xml not found)
Nagaraju created AMQ-9479:
-
Summary: 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
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:
{{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]}}
{{}}
{{We have verified the deployment and installation of ActiveMQ within the
Docker container and confirmed that all necessary files are included}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ARTEMIS-1177) clientFailureCheckPeriod option does not do what Doc says it does
[
https://issues.apache.org/jira/browse/ARTEMIS-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram updated ARTEMIS-1177:
Component/s: Documentation
(was: Broker)
> clientFailureCheckPeriod option does not do what Doc says it does
> -
>
> Key: ARTEMIS-1177
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1177
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Documentation
>Affects Versions: 2.1.0
>Reporter: Jiri Daněk
>Priority: Minor
>
> If I run the following
> {noformat}
> @Test fun `clientFailureCheckPeriod option`() {
> val f =
> org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory("tcp://127.0.0.1:61616?clientFailureCheckPeriod=1000=13000")
> val c = f.createConnection()
> Thread.sleep(5 * 1000)
> Runtime.getRuntime().exec("kill -SIGSTOP 27314")
> println(java.time.LocalDateTime.now())
> Thread.sleep(120 * 1000)
> }
> {noformat}
> (where 27314 is PID of Artemis), I get the following output
> {noformat}
> 2017-05-22T14:18:07.027
> 14:18:28,023 WARN AMQ212037: Connection failure has been detected: AMQ119011:
> Did not receive data from server for
> org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnection@1d90b3b6[local=
> /127.0.0.1:54584, remote=/127.0.0.1:61616] [code=CONNECTION_TIMEDOUT]
> {noformat}
> There is approx 13 second delay between broker going down and client noticing
> it. Given the documentation for clientFailureCheckPeriod, I'd expect the
> client notices it after just 1 second.
> "If the client does not receive any packets for a configurable number of
> milliseconds then it will consider the connection failed and will either
> initiate failover, or call any FailureListener instances (or
> ExceptionListener instances if you are using JMS) depending on how it has
> been configured."
> https://github.com/apache/activemq-artemis/blob/master/docs/user-manual/en/connection-ttl.md
> I think that the documentation is wrong.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ARTEMIS-615) Prompt users if they are browsing documentation for older release
[ https://issues.apache.org/jira/browse/ARTEMIS-615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram updated ARTEMIS-615: --- Component/s: Documentation > Prompt users if they are browsing documentation for older release > - > > Key: ARTEMIS-615 > URL: https://issues.apache.org/jira/browse/ARTEMIS-615 > Project: ActiveMQ Artemis > Issue Type: New Feature > Components: Documentation >Affects Versions: 1.4.0 >Reporter: Jiri Daněk >Priority: Major > > Opening documentation for an older Artemis release does not give any > indication that there is a never release available. > https://activemq.apache.org/artemis/docs/1.0.0/index.html > It seems to be customary to add a note to older documentations notifying > users that there is a never version available and a quick menu to switch > between documentation versions. For example, any readthedocs.io site like > buildbot: http://buildbot.readthedocs.io/en/v0.8.9/tutorial/docker.html or > Postgres: https://www.postgresql.org/docs/9.2/static/index.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-1756) Documentation of "injected properties"
[
https://issues.apache.org/jira/browse/ARTEMIS-1756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram updated ARTEMIS-1756:
Component/s: Documentation
> Documentation of "injected properties"
> --
>
> Key: ARTEMIS-1756
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1756
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Documentation
>Affects Versions: 2.4.0
>Reporter: Ingemar Allqvist
>Priority: Major
>
> It would be very helpful, if the user guide documentation contained
> description of:
> * which properties are available in the bootstrap phase; in the
> "bootstrap.xml" (e.g. ${artemis.instance}, ${artemis.URI.instance}, ...?
> * which properties are available at the broker setup phase, "broker.xml"
> (e.g ${data.dir}, ...?
> I can't finns any documentation of this.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ARTEMIS-615) Prompt users if they are browsing documentation for older release
[ https://issues.apache.org/jira/browse/ARTEMIS-615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram updated ARTEMIS-615: --- Labels: (was: documentation) > Prompt users if they are browsing documentation for older release > - > > Key: ARTEMIS-615 > URL: https://issues.apache.org/jira/browse/ARTEMIS-615 > Project: ActiveMQ Artemis > Issue Type: New Feature >Affects Versions: 1.4.0 >Reporter: Jiri Daněk >Priority: Major > > Opening documentation for an older Artemis release does not give any > indication that there is a never release available. > https://activemq.apache.org/artemis/docs/1.0.0/index.html > It seems to be customary to add a note to older documentations notifying > users that there is a never version available and a quick menu to switch > between documentation versions. For example, any readthedocs.io site like > buildbot: http://buildbot.readthedocs.io/en/v0.8.9/tutorial/docker.html or > Postgres: https://www.postgresql.org/docs/9.2/static/index.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-1729) Automatically check for broken documentation links
[
https://issues.apache.org/jira/browse/ARTEMIS-1729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram updated ARTEMIS-1729:
Component/s: Documentation
> Automatically check for broken documentation links
> --
>
> Key: ARTEMIS-1729
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1729
> Project: ActiveMQ Artemis
> Issue Type: Wish
> Components: Documentation
>Reporter: Lionel Cons
>Priority: Minor
>
> The Artemis GitBook documentation sometimes contains broken (internal) links.
> See for instance ARTEMIS-1076 or ARTEMIS-1721.
> It would be good to automatically check for broken links as part of the Maven
> {{test}} task.
> One way to do this would be to have a Maven task to run a webserver serving
> the generated documentation (Python can trivially do it with '{{python -m
> SimpleHTTPServer 8000}}' but an equivalent Java-based solution is probably
> better) and then a crawler checking for broken links ({{wget}} can easily be
> used for this as described in ARTEMIS-1076 but here again a Java-based
> solution is maybe better).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (ARTEMIS-1802) Cannot use the same name for a divert and an address
[
https://issues.apache.org/jira/browse/ARTEMIS-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836402#comment-17836402
]
Justin Bertram edited comment on ARTEMIS-1802 at 4/12/24 3:16 AM:
--
Taking another look at this...
I think you should be able to accomplish your goal without any changes to the
broker.
bq. First, I need to be able to subscribe to the topic to receive messages
without interfering with the queues.
You should be able to treat the address {{foo}} like a topic and subscribe to
it. This should create a _new_ queue for the subscription (i.e. without
interfering with the existing queues).
bq. Then, I need to be able to send messages directly to one queue without
interfering with the other.
You can do this using the [fully qualified queue
name|https://activemq.apache.org/components/artemis/documentation/latest/address-model.html#fully-qualified-queue-names]
(i.e. {{foo::foo-test}} or {{foo::foo-prod}}).
Generally speaking, all the virtual destination functionality from Classic
should be available in Artemis since it is essentially baked into the address
model.
was (Author: jbertram):
Taking another look at this...
I think you should be able to accomplish your goal without any changes to the
broker.
bq. First, I need to be able to subscribe to the topic to receive messages
without interfering with the queues.
You should be able to treat the address {{foo}} like a topic and subscribe to
it. This should create a _new_ queue for the subscription (i.e. without
interfering with the existing queues).
bq. Then, I need to be able to send messages directly to one queue without
interfering with the other.
You can do this using the fully qualified queue name (i.e. {{foo::foo-test}} or
{{foo::foo-prod}}).
Generally speaking, all the virtual destination functionality from Classic
should be available in Artemis since it is essentially baked into the address
model.
> Cannot use the same name for a divert and an address
>
>
> Key: ARTEMIS-1802
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1802
> Project: ActiveMQ Artemis
> Issue Type: Improvement
>Affects Versions: 2.5.0
>Reporter: Lionel Cons
>Priority: Minor
>
> I'm trying to use diverts to emulate ActiveMQ 5's virtual destinations
> (http://activemq.apache.org/virtual-destinations.html). The use case is a
> single topic ({{foo}}) bound to two queues ({{foo-test}} and {{foo-prod}}).
> The following configuration snippet almost works:
> {code:xml}
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> ...
>
>
>
>
> foo
> foo-test
> false
>
>
>
> foo
> foo-prod
> false
>
>
> {code}
> Artemis give me an error:
> {code}
> AMQ222006: Binding already exists with name foo-test, divert will not be
> deployed
> {code}
> Changing the divert names fixes the problem.
> Why can't I use the same name both for the queue and the divert feeding the
> queue?
> Since these are different kinds of objects, I should be able to reuse the
> same name, shouldn't I?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ARTEMIS-1802) Cannot use the same name for a divert and an address
[
https://issues.apache.org/jira/browse/ARTEMIS-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836402#comment-17836402
]
Justin Bertram commented on ARTEMIS-1802:
-
Taking another look at this...
I think you should be able to accomplish your goal without any changes to the
broker.
bq. First, I need to be able to subscribe to the topic to receive messages
without interfering with the queues.
You should be able to treat the address {{foo}} like a topic and subscribe to
it. This should create a _new_ queue for the subscription (i.e. without
interfering with the existing queues).
bq. Then, I need to be able to send messages directly to one queue without
interfering with the other.
You can do this using the fully qualified queue name (i.e. {{foo::foo-test}} or
{{foo::foo-prod}}).
Generally speaking, all the virtual destination functionality from Classic
should be available in Artemis since it is essentially baked into the address
model.
> Cannot use the same name for a divert and an address
>
>
> Key: ARTEMIS-1802
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1802
> Project: ActiveMQ Artemis
> Issue Type: Improvement
>Affects Versions: 2.5.0
>Reporter: Lionel Cons
>Priority: Minor
>
> I'm trying to use diverts to emulate ActiveMQ 5's virtual destinations
> (http://activemq.apache.org/virtual-destinations.html). The use case is a
> single topic ({{foo}}) bound to two queues ({{foo-test}} and {{foo-prod}}).
> The following configuration snippet almost works:
> {code:xml}
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> ...
>
>
>
>
> foo
> foo-test
> false
>
>
>
> foo
> foo-prod
> false
>
>
> {code}
> Artemis give me an error:
> {code}
> AMQ222006: Binding already exists with name foo-test, divert will not be
> deployed
> {code}
> Changing the divert names fixes the problem.
> Why can't I use the same name both for the queue and the divert feeding the
> queue?
> Since these are different kinds of objects, I should be able to reuse the
> same name, shouldn't I?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ARTEMIS-1231) deserialization black/white list are not used by regular JMS connection factories
[ https://issues.apache.org/jira/browse/ARTEMIS-1231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836401#comment-17836401 ] Justin Bertram commented on ARTEMIS-1231: - [~jmesnil] or [~ehsavoie], do you still need this? > deserialization black/white list are not used by regular JMS connection > factories > - > > Key: ARTEMIS-1231 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1231 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Broker >Affects Versions: 1.5.5, 2.1.0 >Reporter: Jeff Mesnil >Priority: Major > > in our app server, we set the deserialization black/white lists on the > ConnectionFactoryConfiguration and then call > org.apache.activemq.artemis.jms.server.JMSServerManager#createConnectionFactory > to let Artemis create the actual ConnectionFactory object. > However internally, Artemis does not use the deserialization black/white > lists to configure the actual ConnectionFactory object -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4047) Artemis does not send message to consumer AMQP
[
https://issues.apache.org/jira/browse/ARTEMIS-4047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836352#comment-17836352
]
Timothy A. Bish commented on ARTEMIS-4047:
--
This seems like a candidate for closure given the comment from [~jbertram]
There are no known issues with consumer blockages in the AMQP bits that we are
currently aware of.
> Artemis does not send message to consumer AMQP
> --
>
> Key: ARTEMIS-4047
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4047
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: AMQP, Broker
>Affects Versions: 2.25.0, 2.26.0
>Reporter: daves
>Priority: Major
> Attachments: 1.PNG, 2.PNG, 3.PNG, 4.PNG, 5.PNG, All.zip
>
>
> The broker does not send messages from one of many existing queues to the
> connected consumer.
> According to the UI the queue does contain ~15k messages.
> I’m not able to consume any of these messages. I also tried to read a message
> using the browse function of the UI/console but that does not work eighter.
> The message was created by a AMQP client and should be consumed by another
> AMQP client.
> I tried to capture the situation in a few screenshots…
> I don’t know which data can help you to understand the situation, so I’ve
> collected everything:
> * Logs
> * Broker
> * Data
> Please let me know if there are any other data I should add to the ticket.
> I don’t think that the code of my client is relevant since the problem only
> exist for a single queue…but here it is anyway:
> {code:java}
> using Amqp;
> using Amqp.Framing;
> using Amqp.Types;
> namespace Test;
> public sealed class MessageConsumer
> {
> private readonly String _address;
> private readonly CancellationToken _cancellationToken;
> private readonly String _consumerName;
> private readonly String[] _destinations;
> public MessageConsumer( String address, String consumerName, String[]
> destinations, CancellationToken cancellationToken )
> {
> _address = address;
> _consumerName = consumerName;
> _destinations = destinations;
> _cancellationToken = cancellationToken;
> }
> public async Task StartReceivingMessages()
> {
> await Task.Yield();
> while ( !_cancellationToken.IsCancellationRequested )
> {
> var connectionFactory = new ConnectionFactory();
> var address = new Address( _address );
> try
> {
> var connection = await connectionFactory.CreateAsync( address
> );
> var session = ( (IConnection) connection ).CreateSession();
> var receivers = new List();
> foreach ( var destination in _destinations )
> {
> var receiver = session.CreateReceiver(
> $"{_consumerName}_{destination}",
> new Source
> {
> Address =
> destination,
> Capabilities =
> new[] { new Symbol( "queue" ) }
> } );
> receivers.Add( receiver );
> }
> while ( !_cancellationToken.IsCancellationRequested )
> foreach ( var receiver in receivers )
> {
> // ReceiveAsync( TimeSpan.Zero ); blocks forever and
> no messages will be received
> var message = await receiver.ReceiveAsync(
> TimeSpan.FromMilliseconds( 1 ) );
> if ( message == null )
> continue;
> receiver.Accept( message );
> Console.WriteLine( $"{_consumerName} - Received
> message with id: '{message.Properties.MessageId}'" );
> }
> }
> catch ( Exception ex )
> {
> Console.WriteLine( $"{_consumerName} - Connection error in
> producer '{_consumerName}' {ex.Message} => create new connection." );
> await Task.Delay( 1000, CancellationToken.None );
> }
> }
> }
> }{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ARTEMIS-1307) Improve performance of OrderedExecutor
[ https://issues.apache.org/jira/browse/ARTEMIS-1307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836347#comment-17836347 ] Justin Bertram commented on ARTEMIS-1307: - I understand. Someone wiser than me once said, "Premature optimization is the root of all evil." > Improve performance of OrderedExecutor > -- > > Key: ARTEMIS-1307 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1307 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Broker >Affects Versions: 2.2.0 >Reporter: Francesco Nigro >Assignee: Francesco Nigro >Priority: Minor > > The current ordered executor is using ConcurrentLinkedQueue that: > - has expensive queue::size operation (ie O( n )) > - has node instances scattered in the heap > There are faster and cheaper alternatives in specialized libraries (eg > JCtools) that could be used instead of it to be more friendly with the GC and > to provide more throughput too when CPU bound. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-1307) Improve performance of OrderedExecutor
[ https://issues.apache.org/jira/browse/ARTEMIS-1307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836346#comment-17836346 ] Francesco Nigro commented on ARTEMIS-1307: -- I was young(er) and more naive and just wanted to make "everything" faster :) > Improve performance of OrderedExecutor > -- > > Key: ARTEMIS-1307 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1307 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Broker >Affects Versions: 2.2.0 >Reporter: Francesco Nigro >Assignee: Francesco Nigro >Priority: Minor > > The current ordered executor is using ConcurrentLinkedQueue that: > - has expensive queue::size operation (ie O( n )) > - has node instances scattered in the heap > There are faster and cheaper alternatives in specialized libraries (eg > JCtools) that could be used instead of it to be more friendly with the GC and > to provide more throughput too when CPU bound. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-1307) Improve performance of OrderedExecutor
[ https://issues.apache.org/jira/browse/ARTEMIS-1307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram resolved ARTEMIS-1307. - Resolution: Won't Do > Improve performance of OrderedExecutor > -- > > Key: ARTEMIS-1307 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1307 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Broker >Affects Versions: 2.2.0 >Reporter: Francesco Nigro >Assignee: Francesco Nigro >Priority: Minor > > The current ordered executor is using ConcurrentLinkedQueue that: > - has expensive queue::size operation (ie O( n )) > - has node instances scattered in the heap > There are faster and cheaper alternatives in specialized libraries (eg > JCtools) that could be used instead of it to be more friendly with the GC and > to provide more throughput too when CPU bound. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-1307) Improve performance of OrderedExecutor
[ https://issues.apache.org/jira/browse/ARTEMIS-1307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836345#comment-17836345 ] Justin Bertram commented on ARTEMIS-1307: - bq. I remember that most of the operations in Artemis (apart from OpenWire) use to run on the Netty Event Loops: if this thing still hold, probably it won't matter. I don't believe the fundamentals have changed here so I guess it's not a meaningful bottleneck. That said, I'm not a performance or Netty expert. :) > Improve performance of OrderedExecutor > -- > > Key: ARTEMIS-1307 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1307 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Broker >Affects Versions: 2.2.0 >Reporter: Francesco Nigro >Assignee: Francesco Nigro >Priority: Minor > > The current ordered executor is using ConcurrentLinkedQueue that: > - has expensive queue::size operation (ie O( n )) > - has node instances scattered in the heap > There are faster and cheaper alternatives in specialized libraries (eg > JCtools) that could be used instead of it to be more friendly with the GC and > to provide more throughput too when CPU bound. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-3359) Auto-Create of non-durable queue not possible
[
https://issues.apache.org/jira/browse/ARTEMIS-3359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy A. Bish closed ARTEMIS-3359.
Resolution: Information Provided
> Auto-Create of non-durable queue not possible
> -
>
> Key: ARTEMIS-3359
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3359
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.16.0
>Reporter: Rene Koch
>Priority: Major
>
> I have a application in which I want to have 1 durable and 1 non-durable
> queue in Active MQ Artemis. For connecting to this message bus I use
> amqpnetlite (https://github.com/Azure/amqpnetlite)
>
> {code:java}
> var source = new Source()
> {
> };
> if (durable)
> {
> source.Address =
> amqpAddressConverter.GetSubscriberAddress(address, useLoadBalancing);
> source.Durable = 1;
> source.ExpiryPolicy = new Symbol("never");
> source.DistributionMode = new Symbol("copy");
> }
> else
> {
> source.Address =
> amqpAddressConverter.GetSubscriberAddress(address);
> source.Durable = 0;
> }
> var receiverLink = new ReceiverLink(session, linkName, source, null);
> {code}
> {{}}
> So this is my receiver link. As shown I set the Durable uint of the Source
> which will given into the ReceiverLink.
> Because as I saw in the Active MQ Artemis documentation, that the Durable is
> a boolean but within the amqpnetlite library it is an uint my understanding
> is that everything over 0 should be true and 0 should be false. (Seen here:
> [http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-messaging-v1.0-os.html#type-terminus-durability)]
> At first the behaviour was very strange: Even when the Aretemis Web interface
> was shown a queue as durable it would be deleted as soon as no consumer would
> be connected.
> I found this:
>
> [https://stackoverflow.com/questions/66360625/activemq-artemis-queue-deleted-after-shutdown-of-consuming-client]
> which describes that even durable queues get deleted because of the default
> behaviour.
> So I changed the broker.xml and set AUTO-DELETE-QUEUE to false.
> Since then the behaviour completly switched:
> Both (durable = 1 and durable = 0) queues are being still there after the
> connection disconnected.
> What I saw, either the configuration in the broker.xml - every queue will be
> durable = true, it doesn't mather what I set within the Link.
> So how to create a durable and a non-durable connection correctly?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ARTEMIS-3359) Auto-Create of non-durable queue not possible
[
https://issues.apache.org/jira/browse/ARTEMIS-3359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836343#comment-17836343
]
Timothy A. Bish commented on ARTEMIS-3359:
--
TerminusDurability is not the same thing as queue durability and so is not used
internally for indicating this, the client can you the dynamic node option to
create a temporary queue attached to the subscription that will be destroyed
when the client disconnects.
The TerminusDurabily is only used in one place, appropriately, to indicate the
subscription to a topic node is durable or not. That is, the link/terminus is
durable or not. Not the queue the broker happens to create (which is an
implementation detail, there need not be any queue) in terms of the AMQP
specification.
> Auto-Create of non-durable queue not possible
> -
>
> Key: ARTEMIS-3359
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3359
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.16.0
>Reporter: Rene Koch
>Priority: Major
>
> I have a application in which I want to have 1 durable and 1 non-durable
> queue in Active MQ Artemis. For connecting to this message bus I use
> amqpnetlite (https://github.com/Azure/amqpnetlite)
>
> {code:java}
> var source = new Source()
> {
> };
> if (durable)
> {
> source.Address =
> amqpAddressConverter.GetSubscriberAddress(address, useLoadBalancing);
> source.Durable = 1;
> source.ExpiryPolicy = new Symbol("never");
> source.DistributionMode = new Symbol("copy");
> }
> else
> {
> source.Address =
> amqpAddressConverter.GetSubscriberAddress(address);
> source.Durable = 0;
> }
> var receiverLink = new ReceiverLink(session, linkName, source, null);
> {code}
> {{}}
> So this is my receiver link. As shown I set the Durable uint of the Source
> which will given into the ReceiverLink.
> Because as I saw in the Active MQ Artemis documentation, that the Durable is
> a boolean but within the amqpnetlite library it is an uint my understanding
> is that everything over 0 should be true and 0 should be false. (Seen here:
> [http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-messaging-v1.0-os.html#type-terminus-durability)]
> At first the behaviour was very strange: Even when the Aretemis Web interface
> was shown a queue as durable it would be deleted as soon as no consumer would
> be connected.
> I found this:
>
> [https://stackoverflow.com/questions/66360625/activemq-artemis-queue-deleted-after-shutdown-of-consuming-client]
> which describes that even durable queues get deleted because of the default
> behaviour.
> So I changed the broker.xml and set AUTO-DELETE-QUEUE to false.
> Since then the behaviour completly switched:
> Both (durable = 1 and durable = 0) queues are being still there after the
> connection disconnected.
> What I saw, either the configuration in the broker.xml - every queue will be
> durable = true, it doesn't mather what I set within the Link.
> So how to create a durable and a non-durable connection correctly?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-1665) Give PageSyncTimer a special executor
[ https://issues.apache.org/jira/browse/ARTEMIS-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram resolved ARTEMIS-1665. - Resolution: Invalid This no longer applies. The paging code has changed substantially since this was opened. > Give PageSyncTimer a special executor > - > > Key: ARTEMIS-1665 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1665 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Broker >Reporter: shoukun huai >Priority: Minor > > For each page store, we create a page sync timer and cursor provider, they > share the same executor. > The executor will be passed to page subscription, when an address begins > paging, all bindings will use the executor form page subscription to > depage/deliver. > So the executor is used to flush page file, depage, deliver. > Since producer relies on page sync done to send response, I think we can use > a special executor for page sync timer, this helps producer. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (AMQ-9447) ActiveMQ Jolokia health service returns "good" even when persistence or transports are failing
[ https://issues.apache.org/jira/browse/AMQ-9447?focusedWorklogId=914275=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-914275 ] ASF GitHub Bot logged work on AMQ-9447: --- Author: ASF GitHub Bot Created on: 11/Apr/24 20:03 Start Date: 11/Apr/24 20:03 Worklog Time Spent: 10m Work Description: AM-19 commented on PR #1194: URL: https://github.com/apache/activemq/pull/1194#issuecomment-2050429370 > Please add a quick unit test Have Added the same, Please have a look. Issue Time Tracking --- Worklog Id: (was: 914275) Time Spent: 2h 20m (was: 2h 10m) > ActiveMQ Jolokia health service returns "good" even when persistence or > transports are failing > -- > > Key: AMQ-9447 > URL: https://issues.apache.org/jira/browse/AMQ-9447 > Project: ActiveMQ Classic > Issue Type: Improvement > Components: Broker, JMX >Affects Versions: 5.18.3 >Reporter: Ephemeris Lappis >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 6.2.0, 5.18.5 > > Time Spent: 2h 20m > Remaining Estimate: 0h > > The Jolokia health service only considers the BrokerService status, it > doesn't check all layers (like persistent store or transports). > The CurrentStatus should not be "Good" if some underlying service is failing. > For example, with a JDBC persistence adapter, if the DB is not reachable, the > broker should not be considered as OK. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (ARTEMIS-1307) Improve performance of OrderedExecutor
[ https://issues.apache.org/jira/browse/ARTEMIS-1307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836341#comment-17836341 ] Francesco Nigro edited comment on ARTEMIS-1307 at 4/11/24 8:00 PM: --- Hi [~jbertram] I can if there's still the need for such: I mean, if it proves to be a costy component which would benefit by it. I remember that most of the operations in Artemis (apart from OpenWire) use to run on the Netty Event Loops: if this thing still hold, probably it won't matter. If it has changed instead (or there are other performance sentitive paths which run on the executors) I suppose you need to profile a use care and make sure that the bottleneck is on the OrderedExecutor's tasks. was (Author: nigrofranz): Hi [~jbertram] I can if there's still the need for such: I mean, if it proves to be a costy component which would benefit by it. I remember that most of the operations in Artemis (apart from OpenWire) use to run on the Netty Event Loops: if this thing still hold, probably it won't matter. If it has changed than, I suppose you need to profile to make sure that one bottleneck is on the OrderedExecutor's tasks. > Improve performance of OrderedExecutor > -- > > Key: ARTEMIS-1307 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1307 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Broker >Affects Versions: 2.2.0 >Reporter: Francesco Nigro >Assignee: Francesco Nigro >Priority: Minor > > The current ordered executor is using ConcurrentLinkedQueue that: > - has expensive queue::size operation (ie O( n )) > - has node instances scattered in the heap > There are faster and cheaper alternatives in specialized libraries (eg > JCtools) that could be used instead of it to be more friendly with the GC and > to provide more throughput too when CPU bound. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-1307) Improve performance of OrderedExecutor
[ https://issues.apache.org/jira/browse/ARTEMIS-1307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836341#comment-17836341 ] Francesco Nigro commented on ARTEMIS-1307: -- Hi [~jbertram] I can if there's still the need for such: I mean, if it proves to be a costy component which would benefit by it. I remember that most of the operations in Artemis (apart from OpenWire) use to run on the Netty Event Loops: if this thing still hold, probably it won't matter. If it has changed than, I suppose you need to profile to make sure that one bottleneck is on the OrderedExecutor's tasks. > Improve performance of OrderedExecutor > -- > > Key: ARTEMIS-1307 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1307 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Broker >Affects Versions: 2.2.0 >Reporter: Francesco Nigro >Assignee: Francesco Nigro >Priority: Minor > > The current ordered executor is using ConcurrentLinkedQueue that: > - has expensive queue::size operation (ie O( n )) > - has node instances scattered in the heap > There are faster and cheaper alternatives in specialized libraries (eg > JCtools) that could be used instead of it to be more friendly with the GC and > to provide more throughput too when CPU bound. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-1527) [Artemis Testsuite] ActiveMQMessageHandlerTest#testServerShutdownAndReconnect fails
[
https://issues.apache.org/jira/browse/ARTEMIS-1527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram resolved ARTEMIS-1527.
-
Resolution: Won't Do
> [Artemis Testsuite] ActiveMQMessageHandlerTest#testServerShutdownAndReconnect
> fails
> ---
>
> Key: ARTEMIS-1527
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1527
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 1.5.5
>Reporter: Jiri Ondrusek
>Priority: Major
>
> {code}
> java.lang.AssertionError: null
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertTrue(Assert.java:52)
> at
> org.apache.activemq.artemis.tests.integration.ra.ActiveMQMessageHandlerTest.testServerShutdownAndReconnect(ActiveMQMessageHandlerTest.java:245)
> {code}
> Maximum size of clients global thread pool is computed as {{8 *
> Runtime.getRuntime().availableProcessors()}}. In the case of CPU with one
> core, the thread pool has maximum size 8.
> The test fails because of following situation. When the server is stopped,
> all ClientSessionFactoryImpl try to reconnect and they add executor to the
> thread pool which tries to reconnect ad anfinitum, see \[1\]. These threads
> employ the whole thread pool and the rest is not able to work in normal way.
> For example, I can see warnings \[2\].
> This situation is known as Starvation or Livelock \[3\]. I think that the
> system should work properly even if the maximum size of thread pool will be 2.
> *Steps to reproduce:*
> Modify the test in the following way:
> {code}
> @Test
>public void testServerShutdownAndReconnect() throws Exception {
> ActiveMQClient.clearThreadPools();
> ActiveMQClient.setGlobalThreadPoolProperties(2, 1);
> ActiveMQResourceAdapter qResourceAdapter = newResourceAdapter();
> ...
> {code}
> \[1\]
> {code}
> Thread[Signal Dispatcher,5,main]
> com.ibm.misc.SignalDispatcher.waitForSignal(Native Method)
> com.ibm.misc.SignalDispatcher.run(SignalDispatcher.java:73)
> Thread[Thread-4
> (ActiveMQ-client-global-threads--90143455),5,ActiveMQ-client-global-threads--90143455]
> sun.misc.Unsafe.park(Native Method)
> java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:226)
>
> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedNanos(AbstractQueuedSynchronizer.java:1048)
>
> java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1339)
> java.util.concurrent.CountDownLatch.await(CountDownLatch.java:288)
>
> org.apache.activemq.artemis.core.protocol.core.impl.ActiveMQClientProtocolManager.waitOnLatch(ActiveMQClientProtocolManager.java:134)
>
> org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.getConnectionWithRetry(ClientSessionFactoryImpl.java:829)
>
> org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.reconnectSessions(ClientSessionFactoryImpl.java:753)
>
> org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.failoverOrReconnect(ClientSessionFactoryImpl.java:615)
>
> org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.handleConnectionFailure(ClientSessionFactoryImpl.java:513)
>
> org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.access$400(ClientSessionFactoryImpl.java:70)
>
> org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl$DelegatingFailureListener.connectionFailed(ClientSessionFactoryImpl.java:1191)
>
> org.apache.activemq.artemis.spi.core.protocol.AbstractRemotingConnection.callFailureListeners(AbstractRemotingConnection.java:64)
>
> org.apache.activemq.artemis.core.protocol.core.impl.RemotingConnectionImpl.fail(RemotingConnectionImpl.java:210)
>
> org.apache.activemq.artemis.spi.core.protocol.AbstractRemotingConnection.fail(AbstractRemotingConnection.java:206)
>
> org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl$CloseRunnable.run(ClientSessionFactoryImpl.java:1014)
>
> org.apache.activemq.artemis.utils.OrderedExecutorFactory$OrderedExecutor$ExecutorTask.run(OrderedExecutorFactory.java:100)
>
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1153)
>
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> java.lang.Thread.run(Thread.java:785)
> Thread[Thread-5
> (ActiveMQ-client-global-threads--90143455),5,ActiveMQ-client-global-threads--90143455]
> sun.misc.Unsafe.park(Native Method)
> java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:226)
>
> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedNanos(AbstractQueuedSynchronizer.java:1048)
>
>
[jira] [Resolved] (ARTEMIS-1279) Large message streaming can continue after the message handler has returned
[ https://issues.apache.org/jira/browse/ARTEMIS-1279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram resolved ARTEMIS-1279. - Resolution: Fixed > Large message streaming can continue after the message handler has returned > --- > > Key: ARTEMIS-1279 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1279 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Mike Hearn >Priority: Major > > It's possible for large messages to finish streaming after the handler has > returned (but the stream is still in use). The body is then discarded whilst > the stream might still be being read. > There's a simple fix: > https://github.com/corda/activemq-artemis/commit/a7c242023ebd8dd341e06c27761e3a6d619242b8 > but I'm not sure if it'd have other consequences, like a resource leak. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-2481) Outdated johnzon-core Library Upgrade to 1.1.13
[ https://issues.apache.org/jira/browse/ARTEMIS-2481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy A. Bish closed ARTEMIS-2481. Resolution: Fixed Johnzon has already been updated beyond this, most recently to v1.2.21 in ARTEMIS-4364 > Outdated johnzon-core Library Upgrade to 1.1.13 > --- > > Key: ARTEMIS-2481 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2481 > Project: ActiveMQ Artemis > Issue Type: Improvement >Affects Versions: 2.5.0 >Reporter: Roger Soland >Priority: Minor > > The org.apache.johnzon-core Library the artemis-core-client is built on > should be upgraded to the latest version 1.1.13. > artemis-core-client depends on johnzon-core 0.9.0 which is really outdated > and buggy. We have been struggling with the bug > https://issues.apache.org/jira/browse/JOHNZON-158. a state issue of the > JsonStreamParser Implementation. > By using the Artemis Resource Adapter, the johnzon-core Library is > automatically on our application classpath and brings in the buggy JsonParser. > Also the newest ActiveMQ Artemis Version 2.10.0 is affected > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-1309) artemis-server-osgi should explicitly import johnzon.core package
[
https://issues.apache.org/jira/browse/ARTEMIS-1309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram resolved ARTEMIS-1309.
-
Fix Version/s: 2.3.0
Resolution: Fixed
> artemis-server-osgi should explicitly import johnzon.core package
> -
>
> Key: ARTEMIS-1309
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1309
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: osgi
>Affects Versions: 2.1.0, 2.2.0
>Reporter: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 2.3.0
>
>
> The artemis karaf features defines johnzon bundle. However, the
> artemis-server-osgi bundle doesn't import {{johnzon.core}} package. It causes
> the following exception when trying to manage the queues:
> {code}
> java.lang.ExceptionInInitializerError
> at
> org.apache.activemq.artemis.api.core.JsonUtil.toJSONArray(JsonUtil.java:46)
> ~[72:org.apache.activemq.artemis-server-osgi:2.1.0]
> at
> org.apache.activemq.artemis.api.core.management.ManagementHelper.storeResult(ManagementHelper.java:181)
> ~[72:org.apache.activemq.artemis-server-osgi:2.1.0]
> at
> org.apache.activemq.artemis.core.server.management.impl.ManagementServiceImpl.handleMessage(ManagementServiceImpl.java:413)
> ~[72:org.apache.activemq.artemis-server-osgi:2.1.0]
> at
> org.apache.activemq.artemis.core.server.impl.ServerSessionImpl.handleManagementMessage(ServerSessionImpl.java:1562)
> ~[72:org.apache.activemq.artemis-server-osgi:2.1.0]
> at
> org.apache.activemq.artemis.core.server.impl.ServerSessionImpl.send(ServerSessionImpl.java:1349)
> ~[72:org.apache.activemq.artemis-server-osgi:2.1.0]
> at
> org.apache.activemq.artemis.core.server.impl.ServerSessionImpl.send(ServerSessionImpl.java:1295)
> ~[72:org.apache.activemq.artemis-server-osgi:2.1.0]
> at
> org.apache.activemq.artemis.core.server.impl.ServerSessionImpl.send(ServerSessionImpl.java:1288)
> ~[72:org.apache.activemq.artemis-server-osgi:2.1.0]
> at
> org.apache.activemq.artemis.core.protocol.core.ServerSessionPacketHandler.handlePacket(ServerSessionPacketHandler.java:494)
> [72:org.apache.activemq.artemis-server-osgi:2.1.0]
> at
> org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl.handlePacket(ChannelImpl.java:628)
> [72:org.apache.activemq.artemis-server-osgi:2.1.0]
> at
> org.apache.activemq.artemis.core.protocol.core.impl.RemotingConnectionImpl.doBufferReceived(RemotingConnectionImpl.java:381)
> [72:org.apache.activemq.artemis-server-osgi:2.1.0]
> at
> org.apache.activemq.artemis.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:363)
> [72:org.apache.activemq.artemis-server-osgi:2.1.0]
> at
> org.apache.activemq.artemis.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:631)
> [72:org.apache.activemq.artemis-server-osgi:2.1.0]
> at
> org.apache.activemq.artemis.core.remoting.impl.netty.ActiveMQChannelHandler.channelRead(ActiveMQChannelHandler.java:69)
> [72:org.apache.activemq.artemis-server-osgi:2.1.0]
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
> [60:io.netty.transport:4.1.9.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
> [60:io.netty.transport:4.1.9.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
> [60:io.netty.transport:4.1.9.Final]
> at
> io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:293)
> [54:io.netty.codec:4.1.9.Final]
> at
> io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:267)
> [54:io.netty.codec:4.1.9.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
> [60:io.netty.transport:4.1.9.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
> [60:io.netty.transport:4.1.9.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
> [60:io.netty.transport:4.1.9.Final]
> at
> io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1334)
> [60:io.netty.transport:4.1.9.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
> [60:io.netty.transport:4.1.9.Final]
> at
>
[jira] [Commented] (ARTEMIS-1307) Improve performance of OrderedExecutor
[ https://issues.apache.org/jira/browse/ARTEMIS-1307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836330#comment-17836330 ] Justin Bertram commented on ARTEMIS-1307: - [~nigro@gmail.com], do you plan on sending a PR for this? > Improve performance of OrderedExecutor > -- > > Key: ARTEMIS-1307 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1307 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Broker >Affects Versions: 2.2.0 >Reporter: Francesco Nigro >Assignee: Francesco Nigro >Priority: Minor > > The current ordered executor is using ConcurrentLinkedQueue that: > - has expensive queue::size operation (ie O( n )) > - has node instances scattered in the heap > There are faster and cheaper alternatives in specialized libraries (eg > JCtools) that could be used instead of it to be more friendly with the GC and > to provide more throughput too when CPU bound. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-1472) Individualize Loggers to Debug Protocol issues.
[ https://issues.apache.org/jira/browse/ARTEMIS-1472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy A. Bish closed ARTEMIS-1472. Resolution: Abandoned Given this has lingered for many years and we've gotten along without any additional changes I'm closing this one. > Individualize Loggers to Debug Protocol issues. > --- > > Key: ARTEMIS-1472 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1472 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: AMQP >Affects Versions: 2.3.0 >Reporter: Clebert Suconic >Assignee: Clebert Suconic >Priority: Major > > AMQP developers will usually set PN_TRACE_FRM as a System.property to get out > some information from Proton regarding the frame processing. > It would be a nice idea to also throw some log.info when that property is set > at Artemis.. around AMQP Processing, making it easier to Debug AMQP packets. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-1551) Conversion of most of the properties is not working when crossing protocols.
[
https://issues.apache.org/jira/browse/ARTEMIS-1551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram resolved ARTEMIS-1551.
-
Resolution: Cannot Reproduce
> Conversion of most of the properties is not working when crossing protocols.
>
>
> Key: ARTEMIS-1551
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1551
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: AMQP, OpenWire
>Affects Versions: 2.3.0, 2.4.0
> Environment: Artemis 2.3.0
>Reporter: Saurabh Rai
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Send a message using Openwire client
> Receive a message using AMQP client.
> Observe most of the fields like 'group-id', 'group-sequence',
> 'reply-to-group-id' are not getting converted properly.
> {code:java}
> $ java -jar aoc-downstream-ga-5.11.0.redhat-630187.jar sender --timeout 5000
> --log-msgs dict --broker tcp://localhost:61616 --address saurabhTest --count
> 1 --conn-username admin --conn-password admin --msg-user-id tester
> --msg-group-id g1 --msg-group-seq 10 --msg-content-type application/text
> --msg-reply-to-group-id g1
> {'durable': True, 'priority': 4, 'ttl': 0, 'first-acquirer': False,
> 'delivery-count': 0, 'redelivered': False, 'id':
> 'ID:sarai.pnq.csb-44142-1512964029323-1:1:1:1:1', 'user_id':'tester',
> 'address': 'queue://saurabhTest', 'subject': None, 'reply_to': None,
> 'correlation_id': None, 'content_type': 'application/text',
> 'content_encoding': None, 'absolute-expiry-time': 0, 'creation-time':
> 1512964029569, 'group-id': 'g1', 'group-sequence': 10, 'reply-to-group-id':
> 'g1', 'properties': {'JMS_AMQP_ContentType': 'application/text',
> 'JMS_AMQP_ReplyToGroupID': 'g1', 'JMSXUserID': 'tester', 'JMSXGroupSequence':
> '10', 'JMSXGroupID': 'g1', 'JMSXGroupSeq': 0}, 'content': None, 'type': None}
> {code}
> {code:java}
> $ java -jar aac-staging-0.21.0.redhat-1.jar receiver --timeout 5 --log-msgs
> dict --broker localhost:5672 --address saurabhTest --count 1 --conn-username
> admin --conn-password admin
> Unsupported object type org.apache.qpid.proton.amqp.Binary
> \x00\x00\x00\x01\x00\x0aJMSXUserID\x09\x00\x06tester
> Unsupported object type org.apache.qpid.proton.amqp.Binary
> \x00\x00\x005n\x02\xae\x02{\x00(ID:sarai.pnq.csb-33773-1512712171740-1:1\x00\x01\x00\x01\x00\x01
> Unsupported object type org.apache.qpid.proton.amqp.Binary
> \x00\x00\x001{\x01+\x00(ID:sarai.pnq.csb-33773-1512712171740-1:1\x00\x01\x00\x01
> {'durable': True, 'priority': 4, 'ttl': 0, 'first-acquirer': False,
> 'delivery-count': 0, 'redelivered': False, 'id': None, 'user_id': 'tester',
> 'address': 'saurabhTest', 'subject': None, 'reply_to': None,
> 'correlation_id': None, 'content_type': None, 'content_encoding': None,
> 'absolute-expiry-time': 0, 'creation-time': 1512712172006, 'group-id': None,
> 'group-sequence': 0, 'reply-to-group-id': None, 'properties':
> {'__HDR_COMMAND_ID': 5, 'JMSXDeliveryCount': 1, '__HDR_ARRIVAL': 0,
> '__HDR_GROUP_ID': 'g1', 'JMSXUserID': 'tester', '__HDR_MARSHALL_PROP':
> \x00\x00\x00\x01\x00\x0aJMSXUserID\x09\x00\x06tester, '__HDR_MESSAGE_ID':
> \x00\x00\x005n\x02\xae\x02{\x00(ID:sarai.pnq.csb-33773-1512712171740-1:1\x00\x01\x00\x01\x00\x01,
> '__HDR_GROUP_SEQUENCE': 0, '__HDR_PRODUCER_ID':
> \x00\x00\x001{\x01+\x00(ID:sarai.pnq.csb-33773-1512712171740-1:1\x00\x01\x00\x01,
> '__HDR_DROPPABLE': False, '__HDR_BROKER_IN_TIME': 1512712172007}, 'content':
> None}
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (ARTEMIS-2605) Unable to create non-durable queue with specific name
[ https://issues.apache.org/jira/browse/ARTEMIS-2605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy A. Bish closed ARTEMIS-2605. Resolution: Not A Problem As discussed in the issue AMQP clients setting terminus durability has no affect on Queue durability as that is not what that field does and AMQP itself has no behavioral linkage to Topics or Queues. > Unable to create non-durable queue with specific name > - > > Key: ARTEMIS-2605 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2605 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: AMQP >Affects Versions: 2.6.2 >Reporter: Dirkjan >Priority: Major > > When attaching as a receiver to create a new queue, it appears Artemis will > try to create a durable queue by default, even if I specify that the queue > should not be durable. If my user does not have permission to create durable > queues (even though it has permission to create non-durable queues), creation > of the queue will fail with a permission error. > More context: > The application I'm targeting usually uses Core messages to do RPC, but it > accepts AMQP messages as well, so it could be that there is a mismatch here > between how things are set up. > > When using Core, I see that ServerSessionPacketHandler triggers on a packet > with type -12 to create the queue with a well-defined name, which in the end > dispatches to ServerSessionImpl.createQueue() with temporary = true and > durable = false. This is the behavior I'm seeking to replicate. However, all > my attempts to create to a temporary non-durable queue by attaching to it > with AMQP seem to be failing so far. > > With my AMQP client, I try to create the response queue by attaching to it > with source address = . This lets me end up in > ProtonServerSenderContext.initialise() by way of > AMQPSessionContext.addSender(). However, this throws a permission error > (AMQ119213, my user does not have permission for CREATE_DURABLE_QUEUE). This > is surprising to me because I leave the "durable" field as default, which > should mean to default to no durability. It seems to happen because > AMQPSessionCallback.queueQuery() calls (through some indirection) > ServerSessionImpl.createQueue() with durable = true. > > I could potentially create non-durable queues by setting dynamic = true, but > in that case Artemis will create the queue with random UUID name, whereas my > user only has permission to create queues with a name with a specific prefix. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-1551) Conversion of most of the properties is not working when crossing protocols.
[
https://issues.apache.org/jira/browse/ARTEMIS-1551?focusedWorklogId=914266=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-914266
]
ASF GitHub Bot logged work on ARTEMIS-1551:
---
Author: ASF GitHub Bot
Created on: 11/Apr/24 18:37
Start Date: 11/Apr/24 18:37
Worklog Time Spent: 10m
Work Description: jbertram opened a new pull request, #4881:
URL: https://github.com/apache/activemq-artemis/pull/4881
(no comment)
Issue Time Tracking
---
Worklog Id: (was: 914266)
Remaining Estimate: 0h
Time Spent: 10m
> Conversion of most of the properties is not working when crossing protocols.
>
>
> Key: ARTEMIS-1551
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1551
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: AMQP, OpenWire
>Affects Versions: 2.3.0, 2.4.0
> Environment: Artemis 2.3.0
>Reporter: Saurabh Rai
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Send a message using Openwire client
> Receive a message using AMQP client.
> Observe most of the fields like 'group-id', 'group-sequence',
> 'reply-to-group-id' are not getting converted properly.
> {code:java}
> $ java -jar aoc-downstream-ga-5.11.0.redhat-630187.jar sender --timeout 5000
> --log-msgs dict --broker tcp://localhost:61616 --address saurabhTest --count
> 1 --conn-username admin --conn-password admin --msg-user-id tester
> --msg-group-id g1 --msg-group-seq 10 --msg-content-type application/text
> --msg-reply-to-group-id g1
> {'durable': True, 'priority': 4, 'ttl': 0, 'first-acquirer': False,
> 'delivery-count': 0, 'redelivered': False, 'id':
> 'ID:sarai.pnq.csb-44142-1512964029323-1:1:1:1:1', 'user_id':'tester',
> 'address': 'queue://saurabhTest', 'subject': None, 'reply_to': None,
> 'correlation_id': None, 'content_type': 'application/text',
> 'content_encoding': None, 'absolute-expiry-time': 0, 'creation-time':
> 1512964029569, 'group-id': 'g1', 'group-sequence': 10, 'reply-to-group-id':
> 'g1', 'properties': {'JMS_AMQP_ContentType': 'application/text',
> 'JMS_AMQP_ReplyToGroupID': 'g1', 'JMSXUserID': 'tester', 'JMSXGroupSequence':
> '10', 'JMSXGroupID': 'g1', 'JMSXGroupSeq': 0}, 'content': None, 'type': None}
> {code}
> {code:java}
> $ java -jar aac-staging-0.21.0.redhat-1.jar receiver --timeout 5 --log-msgs
> dict --broker localhost:5672 --address saurabhTest --count 1 --conn-username
> admin --conn-password admin
> Unsupported object type org.apache.qpid.proton.amqp.Binary
> \x00\x00\x00\x01\x00\x0aJMSXUserID\x09\x00\x06tester
> Unsupported object type org.apache.qpid.proton.amqp.Binary
> \x00\x00\x005n\x02\xae\x02{\x00(ID:sarai.pnq.csb-33773-1512712171740-1:1\x00\x01\x00\x01\x00\x01
> Unsupported object type org.apache.qpid.proton.amqp.Binary
> \x00\x00\x001{\x01+\x00(ID:sarai.pnq.csb-33773-1512712171740-1:1\x00\x01\x00\x01
> {'durable': True, 'priority': 4, 'ttl': 0, 'first-acquirer': False,
> 'delivery-count': 0, 'redelivered': False, 'id': None, 'user_id': 'tester',
> 'address': 'saurabhTest', 'subject': None, 'reply_to': None,
> 'correlation_id': None, 'content_type': None, 'content_encoding': None,
> 'absolute-expiry-time': 0, 'creation-time': 1512712172006, 'group-id': None,
> 'group-sequence': 0, 'reply-to-group-id': None, 'properties':
> {'__HDR_COMMAND_ID': 5, 'JMSXDeliveryCount': 1, '__HDR_ARRIVAL': 0,
> '__HDR_GROUP_ID': 'g1', 'JMSXUserID': 'tester', '__HDR_MARSHALL_PROP':
> \x00\x00\x00\x01\x00\x0aJMSXUserID\x09\x00\x06tester, '__HDR_MESSAGE_ID':
> \x00\x00\x005n\x02\xae\x02{\x00(ID:sarai.pnq.csb-33773-1512712171740-1:1\x00\x01\x00\x01\x00\x01,
> '__HDR_GROUP_SEQUENCE': 0, '__HDR_PRODUCER_ID':
> \x00\x00\x001{\x01+\x00(ID:sarai.pnq.csb-33773-1512712171740-1:1\x00\x01\x00\x01,
> '__HDR_DROPPABLE': False, '__HDR_BROKER_IN_TIME': 1512712172007}, 'content':
> None}
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (ARTEMIS-1899) AMQPMessage.getIntProperty() throws "UnsignedInteger cannot be cast to java.lang.Integer"
[
https://issues.apache.org/jira/browse/ARTEMIS-1899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy A. Bish closed ARTEMIS-1899.
Resolution: Not A Problem
The methods are doing just what they say they do in their names, getting
Integer or Long values, not UnsignedInteger or UnsignedLong values, that can be
done via getObjectProperty as the issue already points out. The other option
is to go to the proton message itself and get the application properties
directly.
> AMQPMessage.getIntProperty() throws "UnsignedInteger cannot be cast to
> java.lang.Integer"
> -
>
> Key: ARTEMIS-1899
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1899
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: AMQP
>Affects Versions: 2.6.0
>Reporter: Johan Stenberg
>Priority: Minor
>
> While testing a custom Artemis plugin with a RHEA based AMQP client I
> encountered the following exception in the server:
> {noformat}
> 23:56:57.993 WARN [y-threads)] ?(:)
> org.apache.qpid.proton.amqp.UnsignedInteger cannot be cast to
> java.lang.Integer
> java.lang.ClassCastException: org.apache.qpid.proton.amqp.UnsignedInteger
> cannot be cast to java.lang.Integer
> at
> org.apache.activemq.artemis.protocol.amqp.broker.AMQPMessage.getIntProperty(AMQPMessage.java:987)
> ~[artemis-amqp-protocol-2.6.0.jar:?]
> {noformat}
> On the client I am setting a message property with an int value and try to
> access this int value in the custom plugin on the server via
> AMQPMessage.getIntProperty.
> The problem lies in the fact that the AMQPMessage.getIntProperty method
> simply tries to cast the property to Integer and does not perform the same
> conversion as done by
> [getObjectProperty|https://github.com/apache/activemq-artemis/blob/master/artemis-protocols/artemis-amqp-protocol/src/main/java/org/apache/activemq/artemis/protocol/amqp/broker/AMQPMessage.java#L1030].
> Same is true for AMQPMessage.getLongProperty.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (ARTEMIS-2614) Create queues for AMQP clients based on FQQN
[ https://issues.apache.org/jira/browse/ARTEMIS-2614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy A. Bish closed ARTEMIS-2614. Resolution: Won't Fix Based on the discussion in the linked Github pull request it was decided that this is not something that should be added and so I am closing this issue > Create queues for AMQP clients based on FQQN > > > Key: ARTEMIS-2614 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2614 > Project: ActiveMQ Artemis > Issue Type: New Feature > Components: AMQP >Reporter: Krzysztof Porębski >Priority: Major > Time Spent: 11h 40m > Remaining Estimate: 0h > > As a follow up to the discussion on the mailing list I would like to suggest > a new feature regarding FQQN implementation for AMQP protocol - creating > queues. > Currently there is no way of attaching to a queue using FQQN if the queue is > not configured upfront. It should be changed so it would be possible to > create queue via FQQN and a subset of the following capabilities: > - shared > - topic > - queue -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-2113) When AMQP links are opened and closed in quick succession, Artemis doesn’t always respond with attach/detach frames confirming the opening/closing of the links
[
https://issues.apache.org/jira/browse/ARTEMIS-2113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy A. Bish closed ARTEMIS-2113.
Resolution: Information Provided
This is a limitation of the proton-j protocol engine that cannot process
pipelined Open, Begin, Attach and Detach framings due to the temporal squashing
being done. The broker has not part at that level and can't intervene. A
workaround is to await the initial attach response before sending the detach to
ensure the broker has a chance to process the data without pipelining.
> When AMQP links are opened and closed in quick succession, Artemis doesn’t
> always respond with attach/detach frames confirming the opening/closing of
> the links
> ---
>
> Key: ARTEMIS-2113
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2113
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: AMQP
>Affects Versions: 2.6.3
> Environment: This test was done in .NET using the Amqp.Net Lite
> library 2.1.4 (which is the latest version).
>Reporter: Simon Chalmers
>Priority: Major
> Attachments: ArtemisTest.zip, artemis-2.6.3.log, artemis-2.7.0.log,
> dotnet-artemis-2.6.3.txt, dotnet-artemis-2.7.0.txt
>
>
> A trace of a message exchange with Artemis where this has occurred is below.
> The lines highlighted in yellow show opening and then closing two AMQP links,
> but Artemis doesn’t respond after that with its own attach/detach frames,
> which acknowledge the opening/closing of those links. The lines highlighted
> in green are heartbeat frames sent to Artemis, sent every 15 seconds, which
> illustrates that one minute passed without receiving the attach/detach frames
> from Artemis.
> SEND AMQP 3 1 0 0
> RECV sasl-mechanisms(sasl-server-mechanisms:[PLAIN,ANONYMOUS])
> SEND sasl-init(mechanism:PLAIN,initial-response:...,hostname:localhost)
> RECV sasl-outcome(code:0)
> SEND AMQP 0 1.0.0
> SEND (ch=0)
> open(container-id:AMQPNetLite-43a6c9ad,host-name:localhost,max-frame-size:262144,channel-max:255,idle-time-out:2147483647)
> RECV AMQP 0 1 0 0
> SEND (ch=0)
> begin(next-outgoing-id:4294967293,incoming-window:2048,outgoing-window:2048,handle-max:63)
> RECV (ch=0)
> open(container-id:0.0.0.0,max-frame-size:131072,channel-max:65535,idle-time-out:3,offered-capabilities:[sole-connection-for-container,DELAYED_DELIVERY,SHARED-SUBS,ANONYMOUS-RELAY],properties:[product:apache-activemq-artemis,version:2.6.3])
> {color:#f6c342}SEND (ch=0)
> attach(name:link1,handle:0,role:False,source:source(),target:target(address:q1),initial-delivery-count:0)
> SEND (ch=0) detach(handle:0,closed:True)
> SEND (ch=0)
> attach(name:link0,handle:1,role:False,source:source(),target:target(address:q0),initial-delivery-count:0)
> SEND (ch=0) detach(handle:1,closed:True){color}
> RECV (ch=0)
> begin(remote-channel:0,next-outgoing-id:1,incoming-window:2147483647,outgoing-window:2147483647,handle-max:65535)
> {color:#14892c}SEND (ch=0) empty
> SEND (ch=0) empty
> SEND (ch=0) empty
> SEND (ch=0) empty{color}
> Note that this doesn’t always happen. Sometimes Artemis does respond, as
> shown by the lines highlighted in bold/grey in the trace below.
> SEND AMQP 3 1 0 0
> RECV sasl-mechanisms(sasl-server-mechanisms:[PLAIN,ANONYMOUS])
> SEND sasl-init(mechanism:PLAIN,initial-response:...,hostname:localhost)
> RECV sasl-outcome(code:0)
> SEND AMQP 0 1.0.0
> SEND (ch=0)
> open(container-id:AMQPNetLite-b00e0be7,host-name:localhost,max-frame-size:262144,channel-max:255,idle-time-out:2147483647)
> RECV AMQP 0 1 0 0
> RECV (ch=0)
> open(container-id:0.0.0.0,max-frame-size:131072,channel-max:65535,idle-time-out:3,offered-capabilities:[sole-connection-for-container,DELAYED_DELIVERY,SHARED-SUBS,ANONYMOUS-RELAY],properties:[product:apache-activemq-artemis,version:2.6.3])
> SEND (ch=0)
> begin(next-outgoing-id:4294967293,incoming-window:2048,outgoing-window:2048,handle-max:63)
> RECV (ch=0)
> begin(remote-channel:0,next-outgoing-id:1,incoming-window:2147483647,outgoing-window:2147483647,handle-max:65535)
> {color:#f6c342}SEND (ch=0)
> attach(name:link1,handle:0,role:False,source:source(),target:target(address:q1),initial-delivery-count:0)
> SEND (ch=0) detach(handle:0,closed:True)
> SEND (ch=0)
> attach(name:link0,handle:1,role:False,source:source(),target:target(address:q0),initial-delivery-count:0)
> SEND (ch=0) detach(handle:1,closed:True){color}
> *{color:#707070}RECV (ch=0)
> attach(name:link1,handle:0,role:True,snd-settle-mode:2,rcv-settle-mode:0,source:source(),target:target(address:q1)){color}*
> RECV (ch=0)
>
[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=17836304#comment-17836304
]
Justin Bertram commented on ARTEMIS-4528:
-
This change forced us to distribute bouncycastle with the broker. This added
over 10MB to the {{lib}} directory - a 25% increase! Disk space and bandwidth
are relatively cheap, but this is a pretty big penalty for one piece of
functionality that many users will never use.
This also increases our CVE footprint. The broker was recently flagged with two
new bouncycastle CVEs that we must deal with even if that's just to explain
that the broker isn't vulnerable.
Is there any reasonable alternative here?
> 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-4307) AMQP Artemis "hangs" on single message delivery
[
https://issues.apache.org/jira/browse/ARTEMIS-4307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy A. Bish closed ARTEMIS-4307.
Resolution: Cannot Reproduce
This has likely been addressed by changes in ARTEMIS-4233 amongst other fixes
since 2.28.0 and I would recommend updating to the latest release. A
reproducer would helpful if the problem still manifests with the latest release
> AMQP Artemis "hangs" on single message delivery
> ---
>
> Key: ARTEMIS-4307
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4307
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: AMQP
>Affects Versions: 2.28.0
>Reporter: daves
>Priority: Major
>
> My Setup:
> - Multiple clients ~500 send messages to a queue in Artemis using AMQP
> - A single application reads consumes the messages from the queue using AMQP
> At some point - I sadly don't know how to reproduce it - my consuming client
> does not receive messages anymore.
> From the perspective of my client the call to receiving new messages
> (AMQP.NET lite) just hands/waits for messages and never returns. Also, It
> still looks like the connection is open and healthy.
> On the Artemis side I see two different pictures.
> - In the Broker console I can see a consumer from my client, and it tells me
> that 1 Messages is in Transit. ...as if Artemis is waiting for an ACK for the
> message.
> In the Artemis log is see this:
> {noformat}
> 2023-06-09 15:11:37,934 WARN
> [org.apache.activemq.artemis.protocol.amqp.proton.ProtonServerSenderContext]
> Array must not be empty or null
> java.lang.IllegalArgumentException: Array must not be empty or null
> at
> org.apache.qpid.proton.codec.CompositeReadableBuffer.append(CompositeReadableBuffer.java:691)
> ~[proton-j-0.34.0.jar:?]
> at
> org.apache.qpid.proton.engine.impl.DeliveryImpl.send(DeliveryImpl.java:345)
> ~[proton-j-0.34.0.jar:?]
> at org.apache.qpid.proton.engine.impl.SenderImpl.send(SenderImpl.java:74)
> ~[proton-j-0.34.0.jar:?]
> at
> org.apache.activemq.artemis.protocol.amqp.proton.ProtonServerSenderContext$LargeMessageDeliveryContext.deliverInitialPacket(ProtonServerSenderContext.java:715)
> ~[artemis-amqp-protocol-2.28.0.jar:2.28.0]
> at
> org.apache.activemq.artemis.protocol.amqp.proton.ProtonServerSenderContext$LargeMessageDeliveryContext.deliver(ProtonServerSenderContext.java:622)
> ~[artemis-amqp-protocol-2.28.0.jar:2.28.0]
> at
> org.apache.activemq.artemis.protocol.amqp.proton.ProtonServerSenderContext.deliverLarge(ProtonServerSenderContext.java:837)
> ~[artemis-amqp-protocol-2.28.0.jar:2.28.0]
> at
> org.apache.activemq.artemis.protocol.amqp.proton.ProtonServerSenderContext.executeDelivery(ProtonServerSenderContext.java:567)
> ~[artemis-amqp-protocol-2.28.0.jar:2.28.0]
> at
> org.apache.activemq.artemis.core.paging.cursor.PagedReferenceImpl.run(PagedReferenceImpl.java:116)
> ~[artemis-server-2.28.0.jar:2.28.0]
> at
> io.netty.util.concurrent.AbstractEventExecutor.runTask(AbstractEventExecutor.java:174)
> ~[netty-common-4.1.86.Final.jar:4.1.86.Final]
> at
> io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:167)
> ~[netty-common-4.1.86.Final.jar:4.1.86.Final]
> at
> io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:470)
> ~[netty-common-4.1.86.Final.jar:4.1.86.Final]
> at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:566)
> ~[netty-transport-4.1.86.Final.jar:4.1.86.Final]
> at
> io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997)
> ~[netty-common-4.1.86.Final.jar:4.1.86.Final]
> at
> io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
> ~[netty-common-4.1.86.Final.jar:4.1.86.Final]
> at
> org.apache.activemq.artemis.utils.ActiveMQThreadFactory$1.run(ActiveMQThreadFactory.java:118)
> ~[artemis-commons-2.28.0.jar:?]
> 2023-06-09 15:11:37,934 WARN [org.apache.activemq.artemis.core.server]
> AMQ222151: removing consumer which did not handle a message,
> consumer=ServerConsumerImpl [id=3, filter=null, binding=LocalQueueBinding
> [address=MyQName, queue=QueueImpl[name=MyQName, postOffice=PostOfficeImpl
> [server=ActiveMQServerImpl::name=MyApp], temp=false]@776d381a, filter=null,
> name=MyQName, clusterName=MyQName431ed7e1-05dd-11ee-ade9-f44d30e2ecf9]],
> message=PagedReferenceImpl [message=PagedMessageImpl [queueIDs=[47],
> transactionID=-1, page=25, message=AMQPLargeMessage( [durable=false,
> messageID=12940183, address=MyQName, size=0, scanningStatus=SCANNED,
> applicationProperties={atmid=CHE8128,
> content-type=application/x-protobuf, content-version=2.0,
>
[jira] [Work logged] (AMQ-9469) Removing JRMS dependency from assembly POM
[
https://issues.apache.org/jira/browse/AMQ-9469?focusedWorklogId=914256=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-914256
]
ASF GitHub Bot logged work on AMQ-9469:
---
Author: ASF GitHub Bot
Created on: 11/Apr/24 17:41
Start Date: 11/Apr/24 17:41
Worklog Time Spent: 10m
Work Description: jbonofre commented on PR #1191:
URL: https://github.com/apache/activemq/pull/1191#issuecomment-2050189917
@kartg
1. Yes, I don't see problem to cherry-pick on `activemq-5.18.x`, I will do
that
2. To update website, you have to open a PR on
https://github.com/apache/activemq-website
Issue Time Tracking
---
Worklog Id: (was: 914256)
Time Spent: 40m (was: 0.5h)
> Removing JRMS dependency from assembly POM
> --
>
> Key: AMQ-9469
> URL: https://issues.apache.org/jira/browse/AMQ-9469
> Project: ActiveMQ Classic
> Issue Type: Improvement
> Environment: Tested using the libraries from the ActiveMQ 5.18.3
> tarball downloaded from
> https://activemq.apache.org/components/classic/download/
>Reporter: Kartik Ganesh
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Fix For: 6.2.0, 6.1.2
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Hello!
> I noticed that the ActiveMQ [assembly
> pom.xml|https://github.com/apache/activemq/blob/main/assembly/pom.xml#L484-L486]
> has a dependency on a very old library - "jrms-1.1" - and I'm wondering if
> this can be removed. This library has not seen any releases/updates since
> 2005 and [Maven|https://mvnrepository.com/artifact/jrms/jrms/usages] lists
> only ActiveMQ and Apache Camel as upstream usages.
> After digging through ActiveMQ's mailing lists and commit history, I found
> that it [used to be
> listed|https://github.com/apache/activemq-web/blob/7a7d976c/2004/06/23/jgroups-and-jrms-support.xml]
> on ActiveMQ's [URI
> Protocols|https://activemq.apache.org/components/classic/documentation/uri-protocols]
> page, but was removed at some point. JRMS seems to be listed as a
> peer-to-peer option on the
> [topologies|https://activemq.apache.org/components/classic/documentation/topologies]
> page but is not discussed in either the
> [peer|https://activemq.apache.org/components/classic/documentation/peer-transport-reference]
> or
> [multicast|https://activemq.apache.org/components/classic/documentation/multicast-transport-reference]
> transport reference pages.
> If I try to specify "jrms://" as a protocol for my ActiveMQConnectionFactory,
> I see the following stack-trace:
> {noformat}
> javax.jms.JMSException: Could not create Transport. Reason:
> java.io.IOException: Transport scheme NOT recognized: [jrms]
> at
> org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:49)
> at
> org.apache.activemq.ActiveMQConnectionFactory.createTransport(ActiveMQConnectionFactory.java:378)
> at
> org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:391)
> at
> org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:349)
> at
> org.apache.activemq.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:245)
> at App$HelloWorldProducer.run(App.java:66)
> at java.base/java.lang.Thread.run(Thread.java:840)
> Caused by: java.io.IOException: Transport scheme NOT recognized: [jrms]
> at
> org.apache.activemq.util.IOExceptionSupport.create(IOExceptionSupport.java:30)
> at
> org.apache.activemq.transport.TransportFactory.findTransportFactory(TransportFactory.java:185)
> at
> org.apache.activemq.transport.TransportFactory.connect(TransportFactory.java:64)
> at
> org.apache.activemq.ActiveMQConnectionFactory.createTransport(ActiveMQConnectionFactory.java:376)
> ... 5 more
> Caused by: java.io.IOException: Could not find factory class for resource:
> META-INF/services/org/apache/activemq/transport/jrms
> at
> org.apache.activemq.util.FactoryFinder$StandaloneObjectFactory.loadProperties(FactoryFinder.java:104)
> at
> org.apache.activemq.util.FactoryFinder$StandaloneObjectFactory.create(FactoryFinder.java:61)
> at
> org.apache.activemq.util.FactoryFinder.newInstance(FactoryFinder.java:154)
> at
> org.apache.activemq.transport.TransportFactory.findTransportFactory(TransportFactory.java:182)
> ... 7 more{noformat}
> An [email from 2011 on the users
> mailing-list|https://lists.apache.org/thread/wbwdj8011tmcqtdlbbfmzsthjdrh0gn0]
> came to the same conclusion, but I don't see any further discussion on it.
> I've confirmed that the
>
[jira] [Resolved] (AMQ-9430) ActiveMQ 5.18.3 (Classic) and Java 17: runtimeConfigurationPlugin causes ClassNotFoundException
[ https://issues.apache.org/jira/browse/AMQ-9430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved AMQ-9430. --- Resolution: Fixed > ActiveMQ 5.18.3 (Classic) and Java 17: runtimeConfigurationPlugin causes > ClassNotFoundException > --- > > Key: AMQ-9430 > URL: https://issues.apache.org/jira/browse/AMQ-9430 > Project: ActiveMQ Classic > Issue Type: Bug > Components: Broker, JMX, Plugin >Affects Versions: 5.18.3 > Environment: Linux myhost 6.5.0-14-generic #14~22.04.1-Ubuntu SMP > PREEMPT_DYNAMIC Mon Nov 20 18:15:30 UTC 2 x86_64 x86_64 x86_64 GNU/Linux > > java -version > > > openjdk version "17.0.9" 2023-10-17 > OpenJDK Runtime Environment (build 17.0.9+9-Ubuntu-122.04) > OpenJDK 64-Bit Server VM (build 17.0.9+9-Ubuntu-122.04, mixed mode, sharing) >Reporter: Mika Räty >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.18.5, 6.1.2 > > Time Spent: 0.5h > Remaining Estimate: 0h > > We are upgrading from java 8 to java 17 in a project that uses ActiveMQ > 5.18.3 and we noticed that when we try to use the JMX operation updateNow > that is available from Bean > > org.apache.activemq:type=Broker,brokerName=localhost,service=RuntimeConfiguration,name=Plugin > > using java 17 based deployment we get the following error on jconsole screen > > Failed to parse: class path resource [activemq.xml], > javax.xml.bind.JAXBException > - with linked exception: > [java.lang.ClassNotFoundException: > com.sun.xml.internal.bind.v2.ContextFactory];No material change to > configuration in class path resource [activemq.xml] at: Tue Jan 30 13:09:40 > EET 2024; > > On the activemq output we see the following stack trace > > INFO | Manual configuration update triggered > INFO | Failed to parse: class path resource [activemq.xml] > javax.xml.bind.JAXBException: null > at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:241) > ~[jaxb-api-2.2.11.jar:?] > at javax.xml.bind.ContextFinder.find(ContextFinder.java:477) > ~[jaxb-api-2.2.11.jar:?] > at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:656) > ~[jaxb-api-2.2.11.jar:?] > at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:599) > ~[jaxb-api-2.2.11.jar:?] > at > org.apache.activemq.plugin.RuntimeConfigurationBroker.loadConfiguration(RuntimeConfigurationBroker.java:176) > ~[activemq-runtime-config-5.18.3.jar:5.18.3] > at > org.apache.activemq.plugin.RuntimeConfigurationBroker.applyModifications(RuntimeConfigurationBroker.java:141) > ~[activemq-runtime-config-5.18.3.jar:5.18.3] > at > org.apache.activemq.plugin.RuntimeConfigurationBroker.updateNow(RuntimeConfigurationBroker.java:113) > ~[activemq-runtime-config-5.18.3.jar:5.18.3] > at > org.apache.activemq.plugin.jmx.RuntimeConfigurationView.updateNow(RuntimeConfigurationView.java:53) > ~[activemq-runtime-config-5.18.3.jar:5.18.3] > at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native > Method) ~[?:?] > at > jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) > ~[?:?] > ... [ some frames omitted for brevity ] > > Caused by: java.lang.ClassNotFoundException: > com.sun.xml.internal.bind.v2.ContextFactory > at > jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:641) > ~[?:?] > at > jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188) > ~[?:?] > at java.lang.ClassLoader.loadClass(ClassLoader.java:525) ~[?:?] > at javax.xml.bind.ContextFinder.safeLoadClass(ContextFinder.java:594) > ~[jaxb-api-2.2.11.jar:?] > at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:239) > ~[jaxb-api-2.2.11.jar:?] > ... 43 more > INFO | No material change to configuration in class path resource > [activemq.xml] at: Tue Jan 30 12:59:42 EET 2024 > > Java version info > java -version > openjdk version "17.0.9" 2023-10-17 > OpenJDK Runtime Environment (build 17.0.9+9-Ubuntu-122.04) > OpenJDK 64-Bit Server VM (build 17.0.9+9-Ubuntu-122.04, mixed mode, sharing) > > > Reproducing the above error: > > # extract amq package to linux host > tar xvf apache-activemq-5.18.3-bin.tar > # Add plugin to activemq.xml > > > > # Add start="false" to broker tag > according to instructions from here > [https://activemq.apache.org/runtime-configuration] > # Starting activemq with > activemq start > # Connect to the started amq instance with
[jira] [Commented] (AMQ-9430) ActiveMQ 5.18.3 (Classic) and Java 17: runtimeConfigurationPlugin causes ClassNotFoundException
[ https://issues.apache.org/jira/browse/AMQ-9430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836287#comment-17836287 ] ASF subversion and git services commented on AMQ-9430: -- Commit abcc0dcde388fc62a063aa8a32e8432bd0a143fc in activemq's branch refs/heads/activemq-5.18.x from Matt Pavlovich [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=abcc0dcde ] [AMQ-9430] RuntimeConfigPlugin wire in classloader to JAXBContext (cherry picked from commit 1e314d8dfc0242e56762954f5397a5299eb2a36e) > ActiveMQ 5.18.3 (Classic) and Java 17: runtimeConfigurationPlugin causes > ClassNotFoundException > --- > > Key: AMQ-9430 > URL: https://issues.apache.org/jira/browse/AMQ-9430 > Project: ActiveMQ Classic > Issue Type: Bug > Components: Broker, JMX, Plugin >Affects Versions: 5.18.3 > Environment: Linux myhost 6.5.0-14-generic #14~22.04.1-Ubuntu SMP > PREEMPT_DYNAMIC Mon Nov 20 18:15:30 UTC 2 x86_64 x86_64 x86_64 GNU/Linux > > java -version > > > openjdk version "17.0.9" 2023-10-17 > OpenJDK Runtime Environment (build 17.0.9+9-Ubuntu-122.04) > OpenJDK 64-Bit Server VM (build 17.0.9+9-Ubuntu-122.04, mixed mode, sharing) >Reporter: Mika Räty >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.18.5, 6.1.2 > > Time Spent: 0.5h > Remaining Estimate: 0h > > We are upgrading from java 8 to java 17 in a project that uses ActiveMQ > 5.18.3 and we noticed that when we try to use the JMX operation updateNow > that is available from Bean > > org.apache.activemq:type=Broker,brokerName=localhost,service=RuntimeConfiguration,name=Plugin > > using java 17 based deployment we get the following error on jconsole screen > > Failed to parse: class path resource [activemq.xml], > javax.xml.bind.JAXBException > - with linked exception: > [java.lang.ClassNotFoundException: > com.sun.xml.internal.bind.v2.ContextFactory];No material change to > configuration in class path resource [activemq.xml] at: Tue Jan 30 13:09:40 > EET 2024; > > On the activemq output we see the following stack trace > > INFO | Manual configuration update triggered > INFO | Failed to parse: class path resource [activemq.xml] > javax.xml.bind.JAXBException: null > at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:241) > ~[jaxb-api-2.2.11.jar:?] > at javax.xml.bind.ContextFinder.find(ContextFinder.java:477) > ~[jaxb-api-2.2.11.jar:?] > at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:656) > ~[jaxb-api-2.2.11.jar:?] > at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:599) > ~[jaxb-api-2.2.11.jar:?] > at > org.apache.activemq.plugin.RuntimeConfigurationBroker.loadConfiguration(RuntimeConfigurationBroker.java:176) > ~[activemq-runtime-config-5.18.3.jar:5.18.3] > at > org.apache.activemq.plugin.RuntimeConfigurationBroker.applyModifications(RuntimeConfigurationBroker.java:141) > ~[activemq-runtime-config-5.18.3.jar:5.18.3] > at > org.apache.activemq.plugin.RuntimeConfigurationBroker.updateNow(RuntimeConfigurationBroker.java:113) > ~[activemq-runtime-config-5.18.3.jar:5.18.3] > at > org.apache.activemq.plugin.jmx.RuntimeConfigurationView.updateNow(RuntimeConfigurationView.java:53) > ~[activemq-runtime-config-5.18.3.jar:5.18.3] > at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native > Method) ~[?:?] > at > jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) > ~[?:?] > ... [ some frames omitted for brevity ] > > Caused by: java.lang.ClassNotFoundException: > com.sun.xml.internal.bind.v2.ContextFactory > at > jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:641) > ~[?:?] > at > jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188) > ~[?:?] > at java.lang.ClassLoader.loadClass(ClassLoader.java:525) ~[?:?] > at javax.xml.bind.ContextFinder.safeLoadClass(ContextFinder.java:594) > ~[jaxb-api-2.2.11.jar:?] > at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:239) > ~[jaxb-api-2.2.11.jar:?] > ... 43 more > INFO | No material change to configuration in class path resource > [activemq.xml] at: Tue Jan 30 12:59:42 EET 2024 > > Java version info > java -version > openjdk version "17.0.9" 2023-10-17 > OpenJDK Runtime Environment (build 17.0.9+9-Ubuntu-122.04) > OpenJDK 64-Bit Server VM (build 17.0.9+9-Ubuntu-122.04, mixed mode, sharing) > > > Reproducing the
[jira] [Work logged] (AMQ-9447) ActiveMQ Jolokia health service returns "good" even when persistence or transports are failing
[ https://issues.apache.org/jira/browse/AMQ-9447?focusedWorklogId=914243=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-914243 ] ASF GitHub Bot logged work on AMQ-9447: --- Author: ASF GitHub Bot Created on: 11/Apr/24 17:16 Start Date: 11/Apr/24 17:16 Worklog Time Spent: 10m Work Description: AM-19 commented on PR #1194: URL: https://github.com/apache/activemq/pull/1194#issuecomment-2050149863 > Please add a quick unit test Sure, Let me work on that Issue Time Tracking --- Worklog Id: (was: 914243) Time Spent: 2h 10m (was: 2h) > ActiveMQ Jolokia health service returns "good" even when persistence or > transports are failing > -- > > Key: AMQ-9447 > URL: https://issues.apache.org/jira/browse/AMQ-9447 > Project: ActiveMQ Classic > Issue Type: Improvement > Components: Broker, JMX >Affects Versions: 5.18.3 >Reporter: Ephemeris Lappis >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 6.2.0, 5.18.5 > > Time Spent: 2h 10m > Remaining Estimate: 0h > > The Jolokia health service only considers the BrokerService status, it > doesn't check all layers (like persistent store or transports). > The CurrentStatus should not be "Good" if some underlying service is failing. > For example, with a JDBC persistence adapter, if the DB is not reachable, the > broker should not be considered as OK. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (AMQ-9469) Removing JRMS dependency from assembly POM
[
https://issues.apache.org/jira/browse/AMQ-9469?focusedWorklogId=914234=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-914234
]
ASF GitHub Bot logged work on AMQ-9469:
---
Author: ASF GitHub Bot
Created on: 11/Apr/24 16:42
Start Date: 11/Apr/24 16:42
Worklog Time Spent: 10m
Work Description: kartg commented on PR #1191:
URL: https://github.com/apache/activemq/pull/1191#issuecomment-2050097118
thank you @jbonofre! Two follow-up questions:
1. Do you think this is safe to backport to the `5.18.x` branch?
2. What's the right way to update the [topologies
documentation](https://activemq.apache.org/components/classic/documentation/topologies)
to remove the reference to JRMS?
Issue Time Tracking
---
Worklog Id: (was: 914234)
Time Spent: 0.5h (was: 20m)
> Removing JRMS dependency from assembly POM
> --
>
> Key: AMQ-9469
> URL: https://issues.apache.org/jira/browse/AMQ-9469
> Project: ActiveMQ Classic
> Issue Type: Improvement
> Environment: Tested using the libraries from the ActiveMQ 5.18.3
> tarball downloaded from
> https://activemq.apache.org/components/classic/download/
>Reporter: Kartik Ganesh
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Fix For: 6.2.0, 6.1.2
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Hello!
> I noticed that the ActiveMQ [assembly
> pom.xml|https://github.com/apache/activemq/blob/main/assembly/pom.xml#L484-L486]
> has a dependency on a very old library - "jrms-1.1" - and I'm wondering if
> this can be removed. This library has not seen any releases/updates since
> 2005 and [Maven|https://mvnrepository.com/artifact/jrms/jrms/usages] lists
> only ActiveMQ and Apache Camel as upstream usages.
> After digging through ActiveMQ's mailing lists and commit history, I found
> that it [used to be
> listed|https://github.com/apache/activemq-web/blob/7a7d976c/2004/06/23/jgroups-and-jrms-support.xml]
> on ActiveMQ's [URI
> Protocols|https://activemq.apache.org/components/classic/documentation/uri-protocols]
> page, but was removed at some point. JRMS seems to be listed as a
> peer-to-peer option on the
> [topologies|https://activemq.apache.org/components/classic/documentation/topologies]
> page but is not discussed in either the
> [peer|https://activemq.apache.org/components/classic/documentation/peer-transport-reference]
> or
> [multicast|https://activemq.apache.org/components/classic/documentation/multicast-transport-reference]
> transport reference pages.
> If I try to specify "jrms://" as a protocol for my ActiveMQConnectionFactory,
> I see the following stack-trace:
> {noformat}
> javax.jms.JMSException: Could not create Transport. Reason:
> java.io.IOException: Transport scheme NOT recognized: [jrms]
> at
> org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:49)
> at
> org.apache.activemq.ActiveMQConnectionFactory.createTransport(ActiveMQConnectionFactory.java:378)
> at
> org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:391)
> at
> org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:349)
> at
> org.apache.activemq.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:245)
> at App$HelloWorldProducer.run(App.java:66)
> at java.base/java.lang.Thread.run(Thread.java:840)
> Caused by: java.io.IOException: Transport scheme NOT recognized: [jrms]
> at
> org.apache.activemq.util.IOExceptionSupport.create(IOExceptionSupport.java:30)
> at
> org.apache.activemq.transport.TransportFactory.findTransportFactory(TransportFactory.java:185)
> at
> org.apache.activemq.transport.TransportFactory.connect(TransportFactory.java:64)
> at
> org.apache.activemq.ActiveMQConnectionFactory.createTransport(ActiveMQConnectionFactory.java:376)
> ... 5 more
> Caused by: java.io.IOException: Could not find factory class for resource:
> META-INF/services/org/apache/activemq/transport/jrms
> at
> org.apache.activemq.util.FactoryFinder$StandaloneObjectFactory.loadProperties(FactoryFinder.java:104)
> at
> org.apache.activemq.util.FactoryFinder$StandaloneObjectFactory.create(FactoryFinder.java:61)
> at
> org.apache.activemq.util.FactoryFinder.newInstance(FactoryFinder.java:154)
> at
> org.apache.activemq.transport.TransportFactory.findTransportFactory(TransportFactory.java:182)
> ... 7 more{noformat}
> An [email from 2011 on the users
> mailing-list|https://lists.apache.org/thread/wbwdj8011tmcqtdlbbfmzsthjdrh0gn0]
> came to the same conclusion, but I don't see any further discussion on it.
> I've confirmed that the
>
[jira] [Work logged] (AMQ-9430) ActiveMQ 5.18.3 (Classic) and Java 17: runtimeConfigurationPlugin causes ClassNotFoundException
[ https://issues.apache.org/jira/browse/AMQ-9430?focusedWorklogId=914229=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-914229 ] ASF GitHub Bot logged work on AMQ-9430: --- Author: ASF GitHub Bot Created on: 11/Apr/24 16:29 Start Date: 11/Apr/24 16:29 Worklog Time Spent: 10m Work Description: cshannon merged PR #1204: URL: https://github.com/apache/activemq/pull/1204 Issue Time Tracking --- Worklog Id: (was: 914229) Time Spent: 0.5h (was: 20m) > ActiveMQ 5.18.3 (Classic) and Java 17: runtimeConfigurationPlugin causes > ClassNotFoundException > --- > > Key: AMQ-9430 > URL: https://issues.apache.org/jira/browse/AMQ-9430 > Project: ActiveMQ Classic > Issue Type: Bug > Components: Broker, JMX, Plugin >Affects Versions: 5.18.3 > Environment: Linux myhost 6.5.0-14-generic #14~22.04.1-Ubuntu SMP > PREEMPT_DYNAMIC Mon Nov 20 18:15:30 UTC 2 x86_64 x86_64 x86_64 GNU/Linux > > java -version > > > openjdk version "17.0.9" 2023-10-17 > OpenJDK Runtime Environment (build 17.0.9+9-Ubuntu-122.04) > OpenJDK 64-Bit Server VM (build 17.0.9+9-Ubuntu-122.04, mixed mode, sharing) >Reporter: Mika Räty >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.18.5, 6.1.2 > > Time Spent: 0.5h > Remaining Estimate: 0h > > We are upgrading from java 8 to java 17 in a project that uses ActiveMQ > 5.18.3 and we noticed that when we try to use the JMX operation updateNow > that is available from Bean > > org.apache.activemq:type=Broker,brokerName=localhost,service=RuntimeConfiguration,name=Plugin > > using java 17 based deployment we get the following error on jconsole screen > > Failed to parse: class path resource [activemq.xml], > javax.xml.bind.JAXBException > - with linked exception: > [java.lang.ClassNotFoundException: > com.sun.xml.internal.bind.v2.ContextFactory];No material change to > configuration in class path resource [activemq.xml] at: Tue Jan 30 13:09:40 > EET 2024; > > On the activemq output we see the following stack trace > > INFO | Manual configuration update triggered > INFO | Failed to parse: class path resource [activemq.xml] > javax.xml.bind.JAXBException: null > at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:241) > ~[jaxb-api-2.2.11.jar:?] > at javax.xml.bind.ContextFinder.find(ContextFinder.java:477) > ~[jaxb-api-2.2.11.jar:?] > at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:656) > ~[jaxb-api-2.2.11.jar:?] > at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:599) > ~[jaxb-api-2.2.11.jar:?] > at > org.apache.activemq.plugin.RuntimeConfigurationBroker.loadConfiguration(RuntimeConfigurationBroker.java:176) > ~[activemq-runtime-config-5.18.3.jar:5.18.3] > at > org.apache.activemq.plugin.RuntimeConfigurationBroker.applyModifications(RuntimeConfigurationBroker.java:141) > ~[activemq-runtime-config-5.18.3.jar:5.18.3] > at > org.apache.activemq.plugin.RuntimeConfigurationBroker.updateNow(RuntimeConfigurationBroker.java:113) > ~[activemq-runtime-config-5.18.3.jar:5.18.3] > at > org.apache.activemq.plugin.jmx.RuntimeConfigurationView.updateNow(RuntimeConfigurationView.java:53) > ~[activemq-runtime-config-5.18.3.jar:5.18.3] > at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native > Method) ~[?:?] > at > jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) > ~[?:?] > ... [ some frames omitted for brevity ] > > Caused by: java.lang.ClassNotFoundException: > com.sun.xml.internal.bind.v2.ContextFactory > at > jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:641) > ~[?:?] > at > jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188) > ~[?:?] > at java.lang.ClassLoader.loadClass(ClassLoader.java:525) ~[?:?] > at javax.xml.bind.ContextFinder.safeLoadClass(ContextFinder.java:594) > ~[jaxb-api-2.2.11.jar:?] > at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:239) > ~[jaxb-api-2.2.11.jar:?] > ... 43 more > INFO | No material change to configuration in class path resource > [activemq.xml] at: Tue Jan 30 12:59:42 EET 2024 > > Java version info > java -version > openjdk version "17.0.9" 2023-10-17 > OpenJDK Runtime Environment (build 17.0.9+9-Ubuntu-122.04) > OpenJDK 64-Bit Server VM (build 17.0.9+9-Ubuntu-122.04, mixed mode, sharing) > > >
[jira] [Commented] (AMQ-9430) ActiveMQ 5.18.3 (Classic) and Java 17: runtimeConfigurationPlugin causes ClassNotFoundException
[ https://issues.apache.org/jira/browse/AMQ-9430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836268#comment-17836268 ] ASF subversion and git services commented on AMQ-9430: -- Commit 1e314d8dfc0242e56762954f5397a5299eb2a36e in activemq's branch refs/heads/main from Matt Pavlovich [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=1e314d8df ] [AMQ-9430] RuntimeConfigPlugin wire in classloader to JAXBContext > ActiveMQ 5.18.3 (Classic) and Java 17: runtimeConfigurationPlugin causes > ClassNotFoundException > --- > > Key: AMQ-9430 > URL: https://issues.apache.org/jira/browse/AMQ-9430 > Project: ActiveMQ Classic > Issue Type: Bug > Components: Broker, JMX, Plugin >Affects Versions: 5.18.3 > Environment: Linux myhost 6.5.0-14-generic #14~22.04.1-Ubuntu SMP > PREEMPT_DYNAMIC Mon Nov 20 18:15:30 UTC 2 x86_64 x86_64 x86_64 GNU/Linux > > java -version > > > openjdk version "17.0.9" 2023-10-17 > OpenJDK Runtime Environment (build 17.0.9+9-Ubuntu-122.04) > OpenJDK 64-Bit Server VM (build 17.0.9+9-Ubuntu-122.04, mixed mode, sharing) >Reporter: Mika Räty >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.18.5, 6.1.2 > > Time Spent: 0.5h > Remaining Estimate: 0h > > We are upgrading from java 8 to java 17 in a project that uses ActiveMQ > 5.18.3 and we noticed that when we try to use the JMX operation updateNow > that is available from Bean > > org.apache.activemq:type=Broker,brokerName=localhost,service=RuntimeConfiguration,name=Plugin > > using java 17 based deployment we get the following error on jconsole screen > > Failed to parse: class path resource [activemq.xml], > javax.xml.bind.JAXBException > - with linked exception: > [java.lang.ClassNotFoundException: > com.sun.xml.internal.bind.v2.ContextFactory];No material change to > configuration in class path resource [activemq.xml] at: Tue Jan 30 13:09:40 > EET 2024; > > On the activemq output we see the following stack trace > > INFO | Manual configuration update triggered > INFO | Failed to parse: class path resource [activemq.xml] > javax.xml.bind.JAXBException: null > at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:241) > ~[jaxb-api-2.2.11.jar:?] > at javax.xml.bind.ContextFinder.find(ContextFinder.java:477) > ~[jaxb-api-2.2.11.jar:?] > at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:656) > ~[jaxb-api-2.2.11.jar:?] > at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:599) > ~[jaxb-api-2.2.11.jar:?] > at > org.apache.activemq.plugin.RuntimeConfigurationBroker.loadConfiguration(RuntimeConfigurationBroker.java:176) > ~[activemq-runtime-config-5.18.3.jar:5.18.3] > at > org.apache.activemq.plugin.RuntimeConfigurationBroker.applyModifications(RuntimeConfigurationBroker.java:141) > ~[activemq-runtime-config-5.18.3.jar:5.18.3] > at > org.apache.activemq.plugin.RuntimeConfigurationBroker.updateNow(RuntimeConfigurationBroker.java:113) > ~[activemq-runtime-config-5.18.3.jar:5.18.3] > at > org.apache.activemq.plugin.jmx.RuntimeConfigurationView.updateNow(RuntimeConfigurationView.java:53) > ~[activemq-runtime-config-5.18.3.jar:5.18.3] > at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native > Method) ~[?:?] > at > jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) > ~[?:?] > ... [ some frames omitted for brevity ] > > Caused by: java.lang.ClassNotFoundException: > com.sun.xml.internal.bind.v2.ContextFactory > at > jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:641) > ~[?:?] > at > jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188) > ~[?:?] > at java.lang.ClassLoader.loadClass(ClassLoader.java:525) ~[?:?] > at javax.xml.bind.ContextFinder.safeLoadClass(ContextFinder.java:594) > ~[jaxb-api-2.2.11.jar:?] > at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:239) > ~[jaxb-api-2.2.11.jar:?] > ... 43 more > INFO | No material change to configuration in class path resource > [activemq.xml] at: Tue Jan 30 12:59:42 EET 2024 > > Java version info > java -version > openjdk version "17.0.9" 2023-10-17 > OpenJDK Runtime Environment (build 17.0.9+9-Ubuntu-122.04) > OpenJDK 64-Bit Server VM (build 17.0.9+9-Ubuntu-122.04, mixed mode, sharing) > > > Reproducing the above error: > > # extract amq package to linux host > tar xvf
[jira] [Commented] (AMQ-9430) ActiveMQ 5.18.3 (Classic) and Java 17: runtimeConfigurationPlugin causes ClassNotFoundException
[ https://issues.apache.org/jira/browse/AMQ-9430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836269#comment-17836269 ] ASF subversion and git services commented on AMQ-9430: -- Commit f6d067a49aa0f7aea18afa7738d60f9d15eeafa9 in activemq's branch refs/heads/main from Christopher L. Shannon [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=f6d067a49 ] Merge pull request #1204 from mattrpav/AMQ-9430 [AMQ-9430] RuntimeConfigPlugin wire in classloader to JAXBContext > ActiveMQ 5.18.3 (Classic) and Java 17: runtimeConfigurationPlugin causes > ClassNotFoundException > --- > > Key: AMQ-9430 > URL: https://issues.apache.org/jira/browse/AMQ-9430 > Project: ActiveMQ Classic > Issue Type: Bug > Components: Broker, JMX, Plugin >Affects Versions: 5.18.3 > Environment: Linux myhost 6.5.0-14-generic #14~22.04.1-Ubuntu SMP > PREEMPT_DYNAMIC Mon Nov 20 18:15:30 UTC 2 x86_64 x86_64 x86_64 GNU/Linux > > java -version > > > openjdk version "17.0.9" 2023-10-17 > OpenJDK Runtime Environment (build 17.0.9+9-Ubuntu-122.04) > OpenJDK 64-Bit Server VM (build 17.0.9+9-Ubuntu-122.04, mixed mode, sharing) >Reporter: Mika Räty >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.18.5, 6.1.2 > > Time Spent: 0.5h > Remaining Estimate: 0h > > We are upgrading from java 8 to java 17 in a project that uses ActiveMQ > 5.18.3 and we noticed that when we try to use the JMX operation updateNow > that is available from Bean > > org.apache.activemq:type=Broker,brokerName=localhost,service=RuntimeConfiguration,name=Plugin > > using java 17 based deployment we get the following error on jconsole screen > > Failed to parse: class path resource [activemq.xml], > javax.xml.bind.JAXBException > - with linked exception: > [java.lang.ClassNotFoundException: > com.sun.xml.internal.bind.v2.ContextFactory];No material change to > configuration in class path resource [activemq.xml] at: Tue Jan 30 13:09:40 > EET 2024; > > On the activemq output we see the following stack trace > > INFO | Manual configuration update triggered > INFO | Failed to parse: class path resource [activemq.xml] > javax.xml.bind.JAXBException: null > at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:241) > ~[jaxb-api-2.2.11.jar:?] > at javax.xml.bind.ContextFinder.find(ContextFinder.java:477) > ~[jaxb-api-2.2.11.jar:?] > at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:656) > ~[jaxb-api-2.2.11.jar:?] > at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:599) > ~[jaxb-api-2.2.11.jar:?] > at > org.apache.activemq.plugin.RuntimeConfigurationBroker.loadConfiguration(RuntimeConfigurationBroker.java:176) > ~[activemq-runtime-config-5.18.3.jar:5.18.3] > at > org.apache.activemq.plugin.RuntimeConfigurationBroker.applyModifications(RuntimeConfigurationBroker.java:141) > ~[activemq-runtime-config-5.18.3.jar:5.18.3] > at > org.apache.activemq.plugin.RuntimeConfigurationBroker.updateNow(RuntimeConfigurationBroker.java:113) > ~[activemq-runtime-config-5.18.3.jar:5.18.3] > at > org.apache.activemq.plugin.jmx.RuntimeConfigurationView.updateNow(RuntimeConfigurationView.java:53) > ~[activemq-runtime-config-5.18.3.jar:5.18.3] > at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native > Method) ~[?:?] > at > jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) > ~[?:?] > ... [ some frames omitted for brevity ] > > Caused by: java.lang.ClassNotFoundException: > com.sun.xml.internal.bind.v2.ContextFactory > at > jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:641) > ~[?:?] > at > jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188) > ~[?:?] > at java.lang.ClassLoader.loadClass(ClassLoader.java:525) ~[?:?] > at javax.xml.bind.ContextFinder.safeLoadClass(ContextFinder.java:594) > ~[jaxb-api-2.2.11.jar:?] > at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:239) > ~[jaxb-api-2.2.11.jar:?] > ... 43 more > INFO | No material change to configuration in class path resource > [activemq.xml] at: Tue Jan 30 12:59:42 EET 2024 > > Java version info > java -version > openjdk version "17.0.9" 2023-10-17 > OpenJDK Runtime Environment (build 17.0.9+9-Ubuntu-122.04) > OpenJDK 64-Bit Server VM (build 17.0.9+9-Ubuntu-122.04, mixed mode, sharing) > > > Reproducing the above error: > > #
[jira] [Commented] (AMQ-9478) Add unit test for modernized IntrospectionSupport
[ https://issues.apache.org/jira/browse/AMQ-9478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836267#comment-17836267 ] Christopher L. Shannon commented on AMQ-9478: - This is a generic testing ticket but AMQ-9473 drove the creation so we we should definitely make sure the tests cover the changes in that issue. > 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 >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] [Work logged] (ARTEMIS-4723) org.apache.activemq.artemis.utils.actors.Handler$Counter left on the ThreadLocal
[ https://issues.apache.org/jira/browse/ARTEMIS-4723?focusedWorklogId=914222=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-914222 ] ASF GitHub Bot logged work on ARTEMIS-4723: --- Author: ASF GitHub Bot Created on: 11/Apr/24 15:54 Start Date: 11/Apr/24 15:54 Worklog Time Spent: 10m Work Description: clebertsuconic commented on PR #4880: URL: https://github.com/apache/activemq-artemis/pull/4880#issuecomment-2050017298 @cardamon notice I'm keeping you as the author on the commit. as you discovered the issue. I went further and just removed the usage. if all my tests are good I will merge this. Issue Time Tracking --- Worklog Id: (was: 914222) Time Spent: 0.5h (was: 20m) > org.apache.activemq.artemis.utils.actors.Handler$Counter left on the > ThreadLocal > > > Key: ARTEMIS-4723 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4723 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Clebert Suconic >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > > org.apache.activemq.artemis.utils.actors.Handler$Counter is left on the > ThreadLocal. > This is used to verify if the execution is InHander. > The object could be removed after done. So it's not a growing leak (meaning > it will keep growing), but it's an unnecessary allocation that can be avoided. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-2059) NettyWritable should use UTF-8 exact length to encode strings
[ https://issues.apache.org/jira/browse/ARTEMIS-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy A. Bish closed ARTEMIS-2059. Resolution: Not A Problem Closing this as the discussion seems to have concluded there was no broker side issue here and no further work as been done here. > NettyWritable should use UTF-8 exact length to encode strings > - > > Key: ARTEMIS-2059 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2059 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: AMQP >Reporter: Francesco Nigro >Assignee: Francesco Nigro >Priority: Minor > Time Spent: 0.5h > Remaining Estimate: 0h > > NettyWritable.put(String) tries to enlarge the buffer used to write a UTF-8 > string until ByteBufUtil.utf8MaxBytes. > That means that it will fail or will enlarge any ByteBuf that is perfectly > sized to contain the encoded string. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4723) org.apache.activemq.artemis.utils.actors.Handler$Counter left on the ThreadLocal
[ https://issues.apache.org/jira/browse/ARTEMIS-4723?focusedWorklogId=914219=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-914219 ] ASF GitHub Bot logged work on ARTEMIS-4723: --- Author: ASF GitHub Bot Created on: 11/Apr/24 15:52 Start Date: 11/Apr/24 15:52 Worklog Time Spent: 10m Work Description: clebertsuconic opened a new pull request, #4880: URL: https://github.com/apache/activemq-artemis/pull/4880 co-authored: Clebert Suconic Issue Time Tracking --- Worklog Id: (was: 914219) Remaining Estimate: 0h Time Spent: 10m > org.apache.activemq.artemis.utils.actors.Handler$Counter left on the > ThreadLocal > > > Key: ARTEMIS-4723 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4723 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Clebert Suconic >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > org.apache.activemq.artemis.utils.actors.Handler$Counter is left on the > ThreadLocal. > This is used to verify if the execution is InHander. > The object could be removed after done. So it's not a growing leak (meaning > it will keep growing), but it's an unnecessary allocation that can be avoided. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4723) org.apache.activemq.artemis.utils.actors.Handler$Counter left on the ThreadLocal
[
https://issues.apache.org/jira/browse/ARTEMIS-4723?focusedWorklogId=914221=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-914221
]
ASF GitHub Bot logged work on ARTEMIS-4723:
---
Author: ASF GitHub Bot
Created on: 11/Apr/24 15:53
Start Date: 11/Apr/24 15:53
Worklog Time Spent: 10m
Work Description: clebertsuconic commented on code in PR #4880:
URL: https://github.com/apache/activemq-artemis/pull/4880#discussion_r1561260496
##
artemis-commons/src/main/java/org/apache/activemq/artemis/utils/actors/ProcessorBase.java:
##
@@ -117,13 +112,6 @@ public int shutdownNow(Consumer onPendingItem,
int timeout, TimeUnit
requestedShutdown = true;
yielded = false;
- if (!inHandler()) {
- // We don't have an option where we could do an immediate timeout
- // I just need to make one roundtrip to make sure there's no pending
tasks on the loop
- // for that I ellected one second
- flush(timeout, unit);
Review Comment:
This was for tests and it was still causing issues anyway...
so, time to go !!! more issues than benefits
Issue Time Tracking
---
Worklog Id: (was: 914221)
Time Spent: 20m (was: 10m)
> org.apache.activemq.artemis.utils.actors.Handler$Counter left on the
> ThreadLocal
>
>
> Key: ARTEMIS-4723
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4723
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Reporter: Clebert Suconic
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> org.apache.activemq.artemis.utils.actors.Handler$Counter is left on the
> ThreadLocal.
> This is used to verify if the execution is InHander.
> The object could be removed after done. So it's not a growing leak (meaning
> it will keep growing), but it's an unnecessary allocation that can be avoided.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ARTEMIS-1331) JMS test ConnectionTest#testTXTypeInvalid passes with Core JMS (artemis-jms-client) and fails with the other ones
[
https://issues.apache.org/jira/browse/ARTEMIS-1331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836248#comment-17836248
]
Justin Bertram commented on ARTEMIS-1331:
-
I'm torn on this. [This functionality was
added|https://github.com/hornetq/hornetq/commit/7c20a043a979497ddaa9a4f46d2f7f9c500f3c43]
way back in HornetQ apparently in order to pass the JMS 2 TCK. However, I
can't find the test referenced in the commit message in the TCK. In fact, I
can't find any test in the TCK that uses this combination of parameters for
{{createSession}}.
The JavaDoc for {{createSession}} states:
{quote}
In a *Java SE environment* or in the *Java EE application client container*:
* If transacted is set to {{true}} then the session will use a local
transaction which may subsequently be committed or rolled back by calling the
session's {{commit}} or {{rollback}} methods. The argument {{acknowledgeMode}}
is ignored.
* If transacted is set to {{false}} then the session will be non-transacted. In
this case the argument {{acknowledgeMode}} is used to specify how messages
received by this session will be acknowledged. The permitted values are
{{Session.CLIENT_ACKNOWLEDGE}}, {{Session.AUTO_ACKNOWLEDGE}} and
{{Session.DUPS_OK_ACKNOWLEDGE}}. For a definition of the meaning of these
acknowledgement modes see the links below.{quote}
Later it says that a {{JMSException}} may be thrown if there is a, "...lack of
support for the specific transaction and acknowledgement mode..."
> JMS test ConnectionTest#testTXTypeInvalid passes with Core JMS
> (artemis-jms-client) and fails with the other ones
> -
>
> Key: ARTEMIS-1331
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1331
> Project: ActiveMQ Artemis
> Issue Type: Test
>Affects Versions: 2.3.0
>Reporter: Jiri Daněk
>Priority: Trivial
>
> Consider
> {{org.apache.activemq.artemis.tests.integration.jms.client.ConnectionTest#testTXTypeInvalid}}.
> If you do
> {noformat}
> Session sess = conn.createSession(false, Session.SESSION_TRANSACTED);
> {noformat}
> then Core JMS does not throw {{javax.jms.JMSException: acknowledgeMode
> SESSION_TRANSACTED cannot be used for an non-transacted Session}}, the other
> JMS clients do.
> So either Core or the other clients do something wrong.
> (See full reproducer at
> https://github.com/jdanekrh/jms-reproducers/blob/master/src/test/java/org/apache/activemq/artemis/tests/integration/jms/client/ConnectionTest.java)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (ARTEMIS-4723) org.apache.activemq.artemis.utils.actors.Handler$Counter left on the ThreadLocal
Clebert Suconic created ARTEMIS-4723: Summary: org.apache.activemq.artemis.utils.actors.Handler$Counter left on the ThreadLocal Key: ARTEMIS-4723 URL: https://issues.apache.org/jira/browse/ARTEMIS-4723 Project: ActiveMQ Artemis Issue Type: Bug Reporter: Clebert Suconic org.apache.activemq.artemis.utils.actors.Handler$Counter is left on the ThreadLocal. This is used to verify if the execution is InHander. The object could be removed after done. So it's not a growing leak (meaning it will keep growing), but it's an unnecessary allocation that can be avoided. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (AMQ-9478) Add unit test for modernized IntrospectionSupport
Matt Pavlovich created AMQ-9478: --- Summary: 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 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] [Updated] (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 ] Matt Pavlovich updated AMQ-9478: Fix Version/s: 6.2.0 > 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 >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] [Work logged] (AMQ-9473) Client SSL Socket configuration fails while settings parameters
[
https://issues.apache.org/jira/browse/AMQ-9473?focusedWorklogId=914210=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-914210
]
ASF GitHub Bot logged work on AMQ-9473:
---
Author: ASF GitHub Bot
Created on: 11/Apr/24 15:12
Start Date: 11/Apr/24 15:12
Worklog Time Spent: 10m
Work Description: mattrpav commented on PR #1202:
URL: https://github.com/apache/activemq/pull/1202#issuecomment-2049929214
We should add a unit test for this JIRA
https://issues.apache.org/jira/browse/AMQ-9478 assigned to 6.2.0
Issue Time Tracking
---
Worklog Id: (was: 914210)
Time Spent: 0.5h (was: 20m)
> Client SSL Socket configuration fails while settings parameters
> ---
>
> Key: AMQ-9473
> URL: https://issues.apache.org/jira/browse/AMQ-9473
> Project: ActiveMQ Classic
> Issue Type: Bug
>Affects Versions: 6.0.1
> Environment: Windows and Java 21
>Reporter: Jukka Aalto
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 6.2.0, 5.18.5, 6.1.2
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Client connection creation fails when setting socket parameters.
> Exception was thrown, when I tried to set enabledProtocols parameter using
> url:
> ssl://127.0.0.1:12345?socket.enabledProtocols=TLSv1.3
> Exception is also thrown, when using tcpNoDelay parameter. It is thrown
> probably with most of the parameters related to sockets.
> Here is the exception thrown:
> {code:java}
> java.lang.reflect.InaccessibleObjectException: Unable to make public void
> sun.security.ssl.SSLSocketImpl.setEnabledProtocols(java.lang.String[])
> accessible: module java.base does not "exports sun.security.ssl" to unnamed
> module @48f2bd5b
> 13:22:43.976 [main] ERROR org.apache.activemq.util.IntrospectionSupport -
> Could not set property enabledProtocols on SSLSocket[hostname=127.0.0.1,
> port=12345, Session(...)]
> at
> java.lang.reflect.AccessibleObject.throwInaccessibleObjectException(AccessibleObject.java:391)
> ~[?:?]
> at
> java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:367)
> ~[?:?]
> at
> java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:315)
> ~[?:?]
> at
> java.lang.reflect.Method.checkCanSetAccessible(Method.java:203) ~[?:?]
> at java.lang.reflect.Method.setAccessible(Method.java:197) ~[?:?]
> at
> org.apache.activemq.util.IntrospectionSupport.setProperty(IntrospectionSupport.java:184)
> [test/:6.0.1]
> at
> org.apache.activemq.util.IntrospectionSupport.setProperties(IntrospectionSupport.java:155)
> [test/:6.0.1]
> at
> org.apache.activemq.util.IntrospectionSupport.setProperties(IntrospectionSupport.java:140)
> [test/:6.0.1]
> at
> org.apache.activemq.transport.tcp.TcpTransport.initialiseSocket(TcpTransport.java:449)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.tcp.SslTransport.initialiseSocket(SslTransport.java:137)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.tcp.TcpTransport.connect(TcpTransport.java:542)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.tcp.TcpTransport.doStart(TcpTransport.java:488)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:55)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.AbstractInactivityMonitor.start(AbstractInactivityMonitor.java:172)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.InactivityMonitor.start(InactivityMonitor.java:52)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.TransportFilter.start(TransportFilter.java:64)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.WireFormatNegotiator.start(WireFormatNegotiator.java:72)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.TransportFilter.start(TransportFilter.java:64)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.TransportFilter.start(TransportFilter.java:64)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:399)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:349)
> [activemq-client-6.0.1.jar:6.0.1]
> at
>
[jira] [Commented] (AMQ-9473) Client SSL Socket configuration fails while settings parameters
[
https://issues.apache.org/jira/browse/AMQ-9473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836231#comment-17836231
]
ASF subversion and git services commented on AMQ-9473:
--
Commit 9b81a7601014be8e90c889a3300fecf698d857fb in activemq's branch
refs/heads/activemq-5.18.x from JB Onofré
[ https://gitbox.apache.org/repos/asf?p=activemq.git;h=9b81a7601 ]
AMQ-9473: Fix IntrospectionSupport to deal with SSLSocket properties
(cherry picked from commit 550cb9b2be32e5a6454e7bee5e31632498626a9c)
> Client SSL Socket configuration fails while settings parameters
> ---
>
> Key: AMQ-9473
> URL: https://issues.apache.org/jira/browse/AMQ-9473
> Project: ActiveMQ Classic
> Issue Type: Bug
>Affects Versions: 6.0.1
> Environment: Windows and Java 21
>Reporter: Jukka Aalto
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 6.2.0, 5.18.5, 6.1.2
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Client connection creation fails when setting socket parameters.
> Exception was thrown, when I tried to set enabledProtocols parameter using
> url:
> ssl://127.0.0.1:12345?socket.enabledProtocols=TLSv1.3
> Exception is also thrown, when using tcpNoDelay parameter. It is thrown
> probably with most of the parameters related to sockets.
> Here is the exception thrown:
> {code:java}
> java.lang.reflect.InaccessibleObjectException: Unable to make public void
> sun.security.ssl.SSLSocketImpl.setEnabledProtocols(java.lang.String[])
> accessible: module java.base does not "exports sun.security.ssl" to unnamed
> module @48f2bd5b
> 13:22:43.976 [main] ERROR org.apache.activemq.util.IntrospectionSupport -
> Could not set property enabledProtocols on SSLSocket[hostname=127.0.0.1,
> port=12345, Session(...)]
> at
> java.lang.reflect.AccessibleObject.throwInaccessibleObjectException(AccessibleObject.java:391)
> ~[?:?]
> at
> java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:367)
> ~[?:?]
> at
> java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:315)
> ~[?:?]
> at
> java.lang.reflect.Method.checkCanSetAccessible(Method.java:203) ~[?:?]
> at java.lang.reflect.Method.setAccessible(Method.java:197) ~[?:?]
> at
> org.apache.activemq.util.IntrospectionSupport.setProperty(IntrospectionSupport.java:184)
> [test/:6.0.1]
> at
> org.apache.activemq.util.IntrospectionSupport.setProperties(IntrospectionSupport.java:155)
> [test/:6.0.1]
> at
> org.apache.activemq.util.IntrospectionSupport.setProperties(IntrospectionSupport.java:140)
> [test/:6.0.1]
> at
> org.apache.activemq.transport.tcp.TcpTransport.initialiseSocket(TcpTransport.java:449)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.tcp.SslTransport.initialiseSocket(SslTransport.java:137)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.tcp.TcpTransport.connect(TcpTransport.java:542)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.tcp.TcpTransport.doStart(TcpTransport.java:488)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:55)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.AbstractInactivityMonitor.start(AbstractInactivityMonitor.java:172)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.InactivityMonitor.start(InactivityMonitor.java:52)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.TransportFilter.start(TransportFilter.java:64)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.WireFormatNegotiator.start(WireFormatNegotiator.java:72)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.TransportFilter.start(TransportFilter.java:64)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.TransportFilter.start(TransportFilter.java:64)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:399)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:349)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:245)
> [activemq-client-6.0.1.jar:6.0.1]
> at
>
[jira] [Resolved] (AMQ-9473) Client SSL Socket configuration fails while settings parameters
[
https://issues.apache.org/jira/browse/AMQ-9473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré resolved AMQ-9473.
---
Resolution: Fixed
> Client SSL Socket configuration fails while settings parameters
> ---
>
> Key: AMQ-9473
> URL: https://issues.apache.org/jira/browse/AMQ-9473
> Project: ActiveMQ Classic
> Issue Type: Bug
>Affects Versions: 6.0.1
> Environment: Windows and Java 21
>Reporter: Jukka Aalto
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 6.2.0, 5.18.5, 6.1.2
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Client connection creation fails when setting socket parameters.
> Exception was thrown, when I tried to set enabledProtocols parameter using
> url:
> ssl://127.0.0.1:12345?socket.enabledProtocols=TLSv1.3
> Exception is also thrown, when using tcpNoDelay parameter. It is thrown
> probably with most of the parameters related to sockets.
> Here is the exception thrown:
> {code:java}
> java.lang.reflect.InaccessibleObjectException: Unable to make public void
> sun.security.ssl.SSLSocketImpl.setEnabledProtocols(java.lang.String[])
> accessible: module java.base does not "exports sun.security.ssl" to unnamed
> module @48f2bd5b
> 13:22:43.976 [main] ERROR org.apache.activemq.util.IntrospectionSupport -
> Could not set property enabledProtocols on SSLSocket[hostname=127.0.0.1,
> port=12345, Session(...)]
> at
> java.lang.reflect.AccessibleObject.throwInaccessibleObjectException(AccessibleObject.java:391)
> ~[?:?]
> at
> java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:367)
> ~[?:?]
> at
> java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:315)
> ~[?:?]
> at
> java.lang.reflect.Method.checkCanSetAccessible(Method.java:203) ~[?:?]
> at java.lang.reflect.Method.setAccessible(Method.java:197) ~[?:?]
> at
> org.apache.activemq.util.IntrospectionSupport.setProperty(IntrospectionSupport.java:184)
> [test/:6.0.1]
> at
> org.apache.activemq.util.IntrospectionSupport.setProperties(IntrospectionSupport.java:155)
> [test/:6.0.1]
> at
> org.apache.activemq.util.IntrospectionSupport.setProperties(IntrospectionSupport.java:140)
> [test/:6.0.1]
> at
> org.apache.activemq.transport.tcp.TcpTransport.initialiseSocket(TcpTransport.java:449)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.tcp.SslTransport.initialiseSocket(SslTransport.java:137)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.tcp.TcpTransport.connect(TcpTransport.java:542)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.tcp.TcpTransport.doStart(TcpTransport.java:488)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:55)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.AbstractInactivityMonitor.start(AbstractInactivityMonitor.java:172)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.InactivityMonitor.start(InactivityMonitor.java:52)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.TransportFilter.start(TransportFilter.java:64)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.WireFormatNegotiator.start(WireFormatNegotiator.java:72)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.TransportFilter.start(TransportFilter.java:64)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.TransportFilter.start(TransportFilter.java:64)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:399)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:349)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:245)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> test.ActiveMQClientSSLSocketParameter.main(ActiveMQClientSSLSocketParameter.java:25)
> [test/:?]
> {code}
> Here is example to reproduce issue:
> {code:java}
> package test;
> import java.io.IOException;
> import java.net.ServerSocket;
> import org.apache.activemq.ActiveMQSslConnectionFactory;
> public class ActiveMQClientSSLSocketParameter {
> public static void main(String[] args) throws Exception{
> // Dummy
[jira] [Commented] (AMQ-9473) Client SSL Socket configuration fails while settings parameters
[
https://issues.apache.org/jira/browse/AMQ-9473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836229#comment-17836229
]
ASF subversion and git services commented on AMQ-9473:
--
Commit 550cb9b2be32e5a6454e7bee5e31632498626a9c in activemq's branch
refs/heads/main from JB Onofré
[ https://gitbox.apache.org/repos/asf?p=activemq.git;h=550cb9b2b ]
AMQ-9473: Fix IntrospectionSupport to deal with SSLSocket properties
> Client SSL Socket configuration fails while settings parameters
> ---
>
> Key: AMQ-9473
> URL: https://issues.apache.org/jira/browse/AMQ-9473
> Project: ActiveMQ Classic
> Issue Type: Bug
>Affects Versions: 6.0.1
> Environment: Windows and Java 21
>Reporter: Jukka Aalto
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 6.2.0, 5.18.5, 6.1.2
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Client connection creation fails when setting socket parameters.
> Exception was thrown, when I tried to set enabledProtocols parameter using
> url:
> ssl://127.0.0.1:12345?socket.enabledProtocols=TLSv1.3
> Exception is also thrown, when using tcpNoDelay parameter. It is thrown
> probably with most of the parameters related to sockets.
> Here is the exception thrown:
> {code:java}
> java.lang.reflect.InaccessibleObjectException: Unable to make public void
> sun.security.ssl.SSLSocketImpl.setEnabledProtocols(java.lang.String[])
> accessible: module java.base does not "exports sun.security.ssl" to unnamed
> module @48f2bd5b
> 13:22:43.976 [main] ERROR org.apache.activemq.util.IntrospectionSupport -
> Could not set property enabledProtocols on SSLSocket[hostname=127.0.0.1,
> port=12345, Session(...)]
> at
> java.lang.reflect.AccessibleObject.throwInaccessibleObjectException(AccessibleObject.java:391)
> ~[?:?]
> at
> java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:367)
> ~[?:?]
> at
> java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:315)
> ~[?:?]
> at
> java.lang.reflect.Method.checkCanSetAccessible(Method.java:203) ~[?:?]
> at java.lang.reflect.Method.setAccessible(Method.java:197) ~[?:?]
> at
> org.apache.activemq.util.IntrospectionSupport.setProperty(IntrospectionSupport.java:184)
> [test/:6.0.1]
> at
> org.apache.activemq.util.IntrospectionSupport.setProperties(IntrospectionSupport.java:155)
> [test/:6.0.1]
> at
> org.apache.activemq.util.IntrospectionSupport.setProperties(IntrospectionSupport.java:140)
> [test/:6.0.1]
> at
> org.apache.activemq.transport.tcp.TcpTransport.initialiseSocket(TcpTransport.java:449)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.tcp.SslTransport.initialiseSocket(SslTransport.java:137)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.tcp.TcpTransport.connect(TcpTransport.java:542)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.tcp.TcpTransport.doStart(TcpTransport.java:488)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:55)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.AbstractInactivityMonitor.start(AbstractInactivityMonitor.java:172)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.InactivityMonitor.start(InactivityMonitor.java:52)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.TransportFilter.start(TransportFilter.java:64)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.WireFormatNegotiator.start(WireFormatNegotiator.java:72)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.TransportFilter.start(TransportFilter.java:64)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.TransportFilter.start(TransportFilter.java:64)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:399)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:349)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:245)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> test.ActiveMQClientSSLSocketParameter.main(ActiveMQClientSSLSocketParameter.java:25)
> [test/:?]
> {code}
> Here is example to reproduce issue:
>
[jira] [Commented] (AMQ-9473) Client SSL Socket configuration fails while settings parameters
[
https://issues.apache.org/jira/browse/AMQ-9473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836230#comment-17836230
]
ASF subversion and git services commented on AMQ-9473:
--
Commit 1c3c1289bbc4a4d4b6e7030210cf9dc6d2e2f038 in activemq's branch
refs/heads/main from JB Onofré
[ https://gitbox.apache.org/repos/asf?p=activemq.git;h=1c3c1289b ]
Merge pull request #1202 from jbonofre/AMQ-9473
AMQ-9473: Fix IntrospectionSupport to deal with SSLSocket properties
> Client SSL Socket configuration fails while settings parameters
> ---
>
> Key: AMQ-9473
> URL: https://issues.apache.org/jira/browse/AMQ-9473
> Project: ActiveMQ Classic
> Issue Type: Bug
>Affects Versions: 6.0.1
> Environment: Windows and Java 21
>Reporter: Jukka Aalto
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 6.2.0, 5.18.5, 6.1.2
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Client connection creation fails when setting socket parameters.
> Exception was thrown, when I tried to set enabledProtocols parameter using
> url:
> ssl://127.0.0.1:12345?socket.enabledProtocols=TLSv1.3
> Exception is also thrown, when using tcpNoDelay parameter. It is thrown
> probably with most of the parameters related to sockets.
> Here is the exception thrown:
> {code:java}
> java.lang.reflect.InaccessibleObjectException: Unable to make public void
> sun.security.ssl.SSLSocketImpl.setEnabledProtocols(java.lang.String[])
> accessible: module java.base does not "exports sun.security.ssl" to unnamed
> module @48f2bd5b
> 13:22:43.976 [main] ERROR org.apache.activemq.util.IntrospectionSupport -
> Could not set property enabledProtocols on SSLSocket[hostname=127.0.0.1,
> port=12345, Session(...)]
> at
> java.lang.reflect.AccessibleObject.throwInaccessibleObjectException(AccessibleObject.java:391)
> ~[?:?]
> at
> java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:367)
> ~[?:?]
> at
> java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:315)
> ~[?:?]
> at
> java.lang.reflect.Method.checkCanSetAccessible(Method.java:203) ~[?:?]
> at java.lang.reflect.Method.setAccessible(Method.java:197) ~[?:?]
> at
> org.apache.activemq.util.IntrospectionSupport.setProperty(IntrospectionSupport.java:184)
> [test/:6.0.1]
> at
> org.apache.activemq.util.IntrospectionSupport.setProperties(IntrospectionSupport.java:155)
> [test/:6.0.1]
> at
> org.apache.activemq.util.IntrospectionSupport.setProperties(IntrospectionSupport.java:140)
> [test/:6.0.1]
> at
> org.apache.activemq.transport.tcp.TcpTransport.initialiseSocket(TcpTransport.java:449)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.tcp.SslTransport.initialiseSocket(SslTransport.java:137)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.tcp.TcpTransport.connect(TcpTransport.java:542)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.tcp.TcpTransport.doStart(TcpTransport.java:488)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:55)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.AbstractInactivityMonitor.start(AbstractInactivityMonitor.java:172)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.InactivityMonitor.start(InactivityMonitor.java:52)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.TransportFilter.start(TransportFilter.java:64)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.WireFormatNegotiator.start(WireFormatNegotiator.java:72)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.TransportFilter.start(TransportFilter.java:64)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.TransportFilter.start(TransportFilter.java:64)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:399)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:349)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:245)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> test.ActiveMQClientSSLSocketParameter.main(ActiveMQClientSSLSocketParameter.java:25)
> [test/:?]
> {code}
[jira] [Work logged] (AMQ-9473) Client SSL Socket configuration fails while settings parameters
[
https://issues.apache.org/jira/browse/AMQ-9473?focusedWorklogId=914209=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-914209
]
ASF GitHub Bot logged work on AMQ-9473:
---
Author: ASF GitHub Bot
Created on: 11/Apr/24 15:05
Start Date: 11/Apr/24 15:05
Worklog Time Spent: 10m
Work Description: jbonofre merged PR #1202:
URL: https://github.com/apache/activemq/pull/1202
Issue Time Tracking
---
Worklog Id: (was: 914209)
Time Spent: 20m (was: 10m)
> Client SSL Socket configuration fails while settings parameters
> ---
>
> Key: AMQ-9473
> URL: https://issues.apache.org/jira/browse/AMQ-9473
> Project: ActiveMQ Classic
> Issue Type: Bug
>Affects Versions: 6.0.1
> Environment: Windows and Java 21
>Reporter: Jukka Aalto
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 6.2.0, 5.18.5, 6.1.2
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Client connection creation fails when setting socket parameters.
> Exception was thrown, when I tried to set enabledProtocols parameter using
> url:
> ssl://127.0.0.1:12345?socket.enabledProtocols=TLSv1.3
> Exception is also thrown, when using tcpNoDelay parameter. It is thrown
> probably with most of the parameters related to sockets.
> Here is the exception thrown:
> {code:java}
> java.lang.reflect.InaccessibleObjectException: Unable to make public void
> sun.security.ssl.SSLSocketImpl.setEnabledProtocols(java.lang.String[])
> accessible: module java.base does not "exports sun.security.ssl" to unnamed
> module @48f2bd5b
> 13:22:43.976 [main] ERROR org.apache.activemq.util.IntrospectionSupport -
> Could not set property enabledProtocols on SSLSocket[hostname=127.0.0.1,
> port=12345, Session(...)]
> at
> java.lang.reflect.AccessibleObject.throwInaccessibleObjectException(AccessibleObject.java:391)
> ~[?:?]
> at
> java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:367)
> ~[?:?]
> at
> java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:315)
> ~[?:?]
> at
> java.lang.reflect.Method.checkCanSetAccessible(Method.java:203) ~[?:?]
> at java.lang.reflect.Method.setAccessible(Method.java:197) ~[?:?]
> at
> org.apache.activemq.util.IntrospectionSupport.setProperty(IntrospectionSupport.java:184)
> [test/:6.0.1]
> at
> org.apache.activemq.util.IntrospectionSupport.setProperties(IntrospectionSupport.java:155)
> [test/:6.0.1]
> at
> org.apache.activemq.util.IntrospectionSupport.setProperties(IntrospectionSupport.java:140)
> [test/:6.0.1]
> at
> org.apache.activemq.transport.tcp.TcpTransport.initialiseSocket(TcpTransport.java:449)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.tcp.SslTransport.initialiseSocket(SslTransport.java:137)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.tcp.TcpTransport.connect(TcpTransport.java:542)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.tcp.TcpTransport.doStart(TcpTransport.java:488)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:55)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.AbstractInactivityMonitor.start(AbstractInactivityMonitor.java:172)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.InactivityMonitor.start(InactivityMonitor.java:52)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.TransportFilter.start(TransportFilter.java:64)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.WireFormatNegotiator.start(WireFormatNegotiator.java:72)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.TransportFilter.start(TransportFilter.java:64)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.transport.TransportFilter.start(TransportFilter.java:64)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:399)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:349)
> [activemq-client-6.0.1.jar:6.0.1]
> at
> org.apache.activemq.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:245)
> [activemq-client-6.0.1.jar:6.0.1]
> at
>
[jira] [Resolved] (ARTEMIS-4720) Add additional example for AMQP federation showing TLS configuration
[ https://issues.apache.org/jira/browse/ARTEMIS-4720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved ARTEMIS-4720. - Resolution: Fixed > Add additional example for AMQP federation showing TLS configuration > > > Key: ARTEMIS-4720 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4720 > Project: ActiveMQ Artemis > Issue Type: Task > Components: ActiveMQ-Artemis-Examples, AMQP >Affects Versions: 2.33.0 >Reporter: Timothy A. Bish >Assignee: Timothy A. Bish >Priority: Trivial > Fix For: 2.34.0 > > Time Spent: 40m > Remaining Estimate: 0h > > Add a new example in the AMQP Federation examples showing how to configure > the broker connections to use TLS to connect to the remote. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4720) Add additional example for AMQP federation showing TLS configuration
[ https://issues.apache.org/jira/browse/ARTEMIS-4720?focusedWorklogId=914205=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-914205 ] ASF GitHub Bot logged work on ARTEMIS-4720: --- Author: ASF GitHub Bot Created on: 11/Apr/24 15:00 Start Date: 11/Apr/24 15:00 Worklog Time Spent: 10m Work Description: gemmellr merged PR #9: URL: https://github.com/apache/activemq-artemis-examples/pull/9 Issue Time Tracking --- Worklog Id: (was: 914205) Time Spent: 40m (was: 0.5h) > Add additional example for AMQP federation showing TLS configuration > > > Key: ARTEMIS-4720 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4720 > Project: ActiveMQ Artemis > Issue Type: Task > Components: ActiveMQ-Artemis-Examples, AMQP >Affects Versions: 2.33.0 >Reporter: Timothy A. Bish >Assignee: Timothy A. Bish >Priority: Trivial > Fix For: 2.34.0 > > Time Spent: 40m > Remaining Estimate: 0h > > Add a new example in the AMQP Federation examples showing how to configure > the broker connections to use TLS to connect to the remote. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4722) Exclude netty-tcnative-boringssl-static artifacts
[ https://issues.apache.org/jira/browse/ARTEMIS-4722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836223#comment-17836223 ] ASF subversion and git services commented on ARTEMIS-4722: -- Commit 2db7940327548d96cda5e9b801e65004ac7c8371 in activemq-artemis's branch refs/heads/main from Domenico Francesco Bruscino [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=2db7940327 ] ARTEMIS-4722 Exclude netty-tcnative-boringssl-static artifacts The lib folder includes netty-tcnative-boringssl-static artifacts non-aligned with the netty-tcnative-version in pom.xml. Those artifacts are included because of zookeeper-server. > Exclude netty-tcnative-boringssl-static artifacts > - > > Key: ARTEMIS-4722 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4722 > Project: ActiveMQ Artemis > Issue Type: Task >Affects Versions: 2.33.0 >Reporter: Domenico Francesco Bruscino >Assignee: Domenico Francesco Bruscino >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > The lib folder includes netty-tcnative-boringssl-static artifacts non-aligned > with the netty-tcnative-version in pom.xml. Those artifacts are included > because of zookeeper-server. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4722) Exclude netty-tcnative-boringssl-static artifacts
[ https://issues.apache.org/jira/browse/ARTEMIS-4722?focusedWorklogId=914200=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-914200 ] ASF GitHub Bot logged work on ARTEMIS-4722: --- Author: ASF GitHub Bot Created on: 11/Apr/24 14:43 Start Date: 11/Apr/24 14:43 Worklog Time Spent: 10m Work Description: clebertsuconic merged PR #4879: URL: https://github.com/apache/activemq-artemis/pull/4879 Issue Time Tracking --- Worklog Id: (was: 914200) Time Spent: 20m (was: 10m) > Exclude netty-tcnative-boringssl-static artifacts > - > > Key: ARTEMIS-4722 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4722 > Project: ActiveMQ Artemis > Issue Type: Task >Affects Versions: 2.33.0 >Reporter: Domenico Francesco Bruscino >Assignee: Domenico Francesco Bruscino >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > The lib folder includes netty-tcnative-boringssl-static artifacts non-aligned > with the netty-tcnative-version in pom.xml. Those artifacts are included > because of zookeeper-server. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ARTEMIS-1745) Support full streaming on AMQP Messages
[ https://issues.apache.org/jira/browse/ARTEMIS-1745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clebert Suconic closed ARTEMIS-1745. Resolution: Abandoned I believe this was because we used to parse the whole message in memory before delivering. We certainly don't do that any more as we do streaming. This was open in 2.5.0.. a long time ago... so.. I'm closing it. > Support full streaming on AMQP Messages > --- > > Key: ARTEMIS-1745 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1745 > Project: ActiveMQ Artemis > Issue Type: Improvement >Affects Versions: 2.5.0 >Reporter: Clebert Suconic >Priority: Major > > ARTEMIS-1514 implemented conversion of large messages into AMQP. > > We should implement proper streaming of large messages. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (AMQ-9430) ActiveMQ 5.18.3 (Classic) and Java 17: runtimeConfigurationPlugin causes ClassNotFoundException
[ https://issues.apache.org/jira/browse/AMQ-9430?focusedWorklogId=914197=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-914197 ] ASF GitHub Bot logged work on AMQ-9430: --- Author: ASF GitHub Bot Created on: 11/Apr/24 14:34 Start Date: 11/Apr/24 14:34 Worklog Time Spent: 10m Work Description: mattrpav commented on PR #1204: URL: https://github.com/apache/activemq/pull/1204#issuecomment-2049837685 I confirmed testing this locally using jconsole ``` INFO | Manual configuration update triggered INFO | No material change to configuration in class path resource [activemq.xml] at: Thu Apr 11 09:31:19 CDT 2024 ``` Background: The issue is activemq distribution uses a different classloader to bootstrap. There is a unit test for jmx invocation, but it is not like-for-like b/c of the runtime differences between the unit test and the apache activemq dist. This fix should work for all dists, including embedded (karaf, etc) Issue Time Tracking --- Worklog Id: (was: 914197) Time Spent: 20m (was: 10m) > ActiveMQ 5.18.3 (Classic) and Java 17: runtimeConfigurationPlugin causes > ClassNotFoundException > --- > > Key: AMQ-9430 > URL: https://issues.apache.org/jira/browse/AMQ-9430 > Project: ActiveMQ Classic > Issue Type: Bug > Components: Broker, JMX, Plugin >Affects Versions: 5.18.3 > Environment: Linux myhost 6.5.0-14-generic #14~22.04.1-Ubuntu SMP > PREEMPT_DYNAMIC Mon Nov 20 18:15:30 UTC 2 x86_64 x86_64 x86_64 GNU/Linux > > java -version > > > openjdk version "17.0.9" 2023-10-17 > OpenJDK Runtime Environment (build 17.0.9+9-Ubuntu-122.04) > OpenJDK 64-Bit Server VM (build 17.0.9+9-Ubuntu-122.04, mixed mode, sharing) >Reporter: Mika Räty >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.18.5, 6.1.2 > > Time Spent: 20m > Remaining Estimate: 0h > > We are upgrading from java 8 to java 17 in a project that uses ActiveMQ > 5.18.3 and we noticed that when we try to use the JMX operation updateNow > that is available from Bean > > org.apache.activemq:type=Broker,brokerName=localhost,service=RuntimeConfiguration,name=Plugin > > using java 17 based deployment we get the following error on jconsole screen > > Failed to parse: class path resource [activemq.xml], > javax.xml.bind.JAXBException > - with linked exception: > [java.lang.ClassNotFoundException: > com.sun.xml.internal.bind.v2.ContextFactory];No material change to > configuration in class path resource [activemq.xml] at: Tue Jan 30 13:09:40 > EET 2024; > > On the activemq output we see the following stack trace > > INFO | Manual configuration update triggered > INFO | Failed to parse: class path resource [activemq.xml] > javax.xml.bind.JAXBException: null > at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:241) > ~[jaxb-api-2.2.11.jar:?] > at javax.xml.bind.ContextFinder.find(ContextFinder.java:477) > ~[jaxb-api-2.2.11.jar:?] > at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:656) > ~[jaxb-api-2.2.11.jar:?] > at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:599) > ~[jaxb-api-2.2.11.jar:?] > at > org.apache.activemq.plugin.RuntimeConfigurationBroker.loadConfiguration(RuntimeConfigurationBroker.java:176) > ~[activemq-runtime-config-5.18.3.jar:5.18.3] > at > org.apache.activemq.plugin.RuntimeConfigurationBroker.applyModifications(RuntimeConfigurationBroker.java:141) > ~[activemq-runtime-config-5.18.3.jar:5.18.3] > at > org.apache.activemq.plugin.RuntimeConfigurationBroker.updateNow(RuntimeConfigurationBroker.java:113) > ~[activemq-runtime-config-5.18.3.jar:5.18.3] > at > org.apache.activemq.plugin.jmx.RuntimeConfigurationView.updateNow(RuntimeConfigurationView.java:53) > ~[activemq-runtime-config-5.18.3.jar:5.18.3] > at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native > Method) ~[?:?] > at > jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) > ~[?:?] > ... [ some frames omitted for brevity ] > > Caused by: java.lang.ClassNotFoundException: > com.sun.xml.internal.bind.v2.ContextFactory > at > jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:641) > ~[?:?] > at > jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188) > ~[?:?] > at
[jira] [Commented] (ARTEMIS-4498) Enable management for internal addresses & queues
[ https://issues.apache.org/jira/browse/ARTEMIS-4498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836208#comment-17836208 ] ASF subversion and git services commented on ARTEMIS-4498: -- Commit 7702b39374d16816a096a0b282c29249ca2cee00 in activemq-artemis's branch refs/heads/main from Clebert Suconic [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=7702b39374 ] ARTEMIS-4498 Adding internal column on address view > Enable management for internal addresses & queues > - > > Key: ARTEMIS-4498 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4498 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Anton Roskvist >Priority: Major > Time Spent: 8h 20m > Remaining Estimate: 0h > > Originally "internal" addresses and queues weren't meant to be exposed via > management. However, due to a bug where the "internal" attribute of a queue > was not persisted properly such queues have been exposed to management for a > long time. This was fixed via ARTEMIS-4396, but users still want the ability > to manage internal queues because it is extremely helpful when trying to > troubleshoot issues. Therefore, this functionality should be configurable. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4498) Enable management for internal addresses & queues
[ https://issues.apache.org/jira/browse/ARTEMIS-4498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836207#comment-17836207 ] ASF subversion and git services commented on ARTEMIS-4498: -- Commit 51f39fc34d1f7c5c5b8797ffca2640161950064c in activemq-artemis's branch refs/heads/main from a181321 [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=51f39fc34d ] ARTEMIS-4498 Expose internal queues for management and observability > Enable management for internal addresses & queues > - > > Key: ARTEMIS-4498 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4498 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Anton Roskvist >Priority: Major > Time Spent: 8h 20m > Remaining Estimate: 0h > > Originally "internal" addresses and queues weren't meant to be exposed via > management. However, due to a bug where the "internal" attribute of a queue > was not persisted properly such queues have been exposed to management for a > long time. This was fixed via ARTEMIS-4396, but users still want the ability > to manage internal queues because it is extremely helpful when trying to > troubleshoot issues. Therefore, this functionality should be configurable. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4498) Enable management for internal addresses & queues
[ https://issues.apache.org/jira/browse/ARTEMIS-4498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836210#comment-17836210 ] ASF subversion and git services commented on ARTEMIS-4498: -- Commit e1bf8222e7029fcd3fa8a51f5676e318a3d01740 in activemq-artemis's branch refs/heads/main from Clebert Suconic [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=e1bf8222e7 ] ARTEMIS-4498 Adding release doc > Enable management for internal addresses & queues > - > > Key: ARTEMIS-4498 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4498 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Anton Roskvist >Priority: Major > Time Spent: 8h 20m > Remaining Estimate: 0h > > Originally "internal" addresses and queues weren't meant to be exposed via > management. However, due to a bug where the "internal" attribute of a queue > was not persisted properly such queues have been exposed to management for a > long time. This was fixed via ARTEMIS-4396, but users still want the ability > to manage internal queues because it is extremely helpful when trying to > troubleshoot issues. Therefore, this functionality should be configurable. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4498) Enable management for internal addresses & queues
[ https://issues.apache.org/jira/browse/ARTEMIS-4498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836209#comment-17836209 ] ASF subversion and git services commented on ARTEMIS-4498: -- Commit 162c4f6655dd4a513c1dfd491ebaa24ea817c414 in activemq-artemis's branch refs/heads/main from Clebert Suconic [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=162c4f6655 ] ARTEMIS-4498 Making queues always manageable > Enable management for internal addresses & queues > - > > Key: ARTEMIS-4498 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4498 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Anton Roskvist >Priority: Major > Time Spent: 8h 20m > Remaining Estimate: 0h > > Originally "internal" addresses and queues weren't meant to be exposed via > management. However, due to a bug where the "internal" attribute of a queue > was not persisted properly such queues have been exposed to management for a > long time. This was fixed via ARTEMIS-4396, but users still want the ability > to manage internal queues because it is extremely helpful when trying to > troubleshoot issues. Therefore, this functionality should be configurable. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4498) Enable management for internal addresses & queues
[ https://issues.apache.org/jira/browse/ARTEMIS-4498?focusedWorklogId=914193=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-914193 ] ASF GitHub Bot logged work on ARTEMIS-4498: --- Author: ASF GitHub Bot Created on: 11/Apr/24 14:28 Start Date: 11/Apr/24 14:28 Worklog Time Spent: 10m Work Description: clebertsuconic merged PR #4856: URL: https://github.com/apache/activemq-artemis/pull/4856 Issue Time Tracking --- Worklog Id: (was: 914193) Time Spent: 8h 20m (was: 8h 10m) > Enable management for internal addresses & queues > - > > Key: ARTEMIS-4498 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4498 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Anton Roskvist >Priority: Major > Time Spent: 8h 20m > Remaining Estimate: 0h > > Originally "internal" addresses and queues weren't meant to be exposed via > management. However, due to a bug where the "internal" attribute of a queue > was not persisted properly such queues have been exposed to management for a > long time. This was fixed via ARTEMIS-4396, but users still want the ability > to manage internal queues because it is extremely helpful when trying to > troubleshoot issues. Therefore, this functionality should be configurable. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4721) Possible documentation error in wildcard syntax recommendation
[
https://issues.apache.org/jira/browse/ARTEMIS-4721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836204#comment-17836204
]
Justin Bertram commented on ARTEMIS-4721:
-
bq. Regarding these very links, it would be good too to refer to the latest
version via the specific number, i.e. right now, "latest" can be replaced with
"2.32.0", but not with "2.33.0".
The links are _relative_, and right now the latest documentation is physically
located in a directory named _latest_. When 2.34.0 is released the
documentation currently in the _latest_ directory will be moved to a directory
named _2.33.0_.
> Possible documentation error in wildcard syntax recommendation
> --
>
> Key: ARTEMIS-4721
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4721
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: MQTT
>Affects Versions: 2.33.0
>Reporter: Daniel Martin
>Priority: Minor
>
> The [user manual for version
> 2.33.0|https://activemq.apache.org/components/artemis/documentation/latest/mqtt.html#wildcard-subscriptions]
> makes the recommendation to use the following configuration to match the
> MQTT specification for better performance:
> {code:java}
>
>/
>#
>*
> {code}
> Shouldn't it recommend "+" instead of "*" for single levels?
> Additionally, it would be good to clarify where this XML node is supposed to
> go. Top level? Inside {{{}{}}}? Inside {{{}{}}}?
> Somewhere else?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-4721) Possible documentation error in wildcard syntax recommendation
[
https://issues.apache.org/jira/browse/ARTEMIS-4721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram resolved ARTEMIS-4721.
-
Fix Version/s: 2.34.0
Assignee: Justin Bertram
Resolution: Fixed
> Possible documentation error in wildcard syntax recommendation
> --
>
> Key: ARTEMIS-4721
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4721
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: MQTT
>Affects Versions: 2.33.0
>Reporter: Daniel Martin
>Assignee: Justin Bertram
>Priority: Minor
> Fix For: 2.34.0
>
>
> The [user manual for version
> 2.33.0|https://activemq.apache.org/components/artemis/documentation/latest/mqtt.html#wildcard-subscriptions]
> makes the recommendation to use the following configuration to match the
> MQTT specification for better performance:
> {code:java}
>
>/
>#
>*
> {code}
> Shouldn't it recommend "+" instead of "*" for single levels?
> Additionally, it would be good to clarify where this XML node is supposed to
> go. Top level? Inside {{{}{}}}? Inside {{{}{}}}?
> Somewhere else?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4721) Possible documentation error in wildcard syntax recommendation
[
https://issues.apache.org/jira/browse/ARTEMIS-4721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836203#comment-17836203
]
ASF subversion and git services commented on ARTEMIS-4721:
--
Commit 6e3c7e055d80f82397dd427013fd234f1fdee029 in activemq-artemis's branch
refs/heads/main from Justin Bertram
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=6e3c7e055d ]
ARTEMIS-4721 fix MQTT link in upgrade instructions
> Possible documentation error in wildcard syntax recommendation
> --
>
> Key: ARTEMIS-4721
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4721
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: MQTT
>Affects Versions: 2.33.0
>Reporter: Daniel Martin
>Priority: Minor
>
> The [user manual for version
> 2.33.0|https://activemq.apache.org/components/artemis/documentation/latest/mqtt.html#wildcard-subscriptions]
> makes the recommendation to use the following configuration to match the
> MQTT specification for better performance:
> {code:java}
>
>/
>#
>*
> {code}
> Shouldn't it recommend "+" instead of "*" for single levels?
> Additionally, it would be good to clarify where this XML node is supposed to
> go. Top level? Inside {{{}{}}}? Inside {{{}{}}}?
> Somewhere else?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ARTEMIS-889) dispositions sent after link is detached with close=false and no error are ignored
[ https://issues.apache.org/jira/browse/ARTEMIS-889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836202#comment-17836202 ] Timothy A. Bish commented on ARTEMIS-889: - It's quite likely it behaves exactly as it did before as the proton-j bits haven't really changed since then > dispositions sent after link is detached with close=false and no error are > ignored > -- > > Key: ARTEMIS-889 > URL: https://issues.apache.org/jira/browse/ARTEMIS-889 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: AMQP >Affects Versions: 1.5.1 >Reporter: Gordon Sim >Priority: Major > > See > https://issues.apache.org/jira/browse/DISPATCH-595?focusedCommentId=15745826=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15745826 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4721) Possible documentation error in wildcard syntax recommendation
[
https://issues.apache.org/jira/browse/ARTEMIS-4721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836201#comment-17836201
]
ASF subversion and git services commented on ARTEMIS-4721:
--
Commit 221420b0b82ed912818b74c9d38f1982fc019153 in activemq-artemis's branch
refs/heads/main from Justin Bertram
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=221420b0b8 ]
ARTEMIS-4721 mqtt doc fixes
> Possible documentation error in wildcard syntax recommendation
> --
>
> Key: ARTEMIS-4721
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4721
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: MQTT
>Affects Versions: 2.33.0
>Reporter: Daniel Martin
>Priority: Minor
>
> The [user manual for version
> 2.33.0|https://activemq.apache.org/components/artemis/documentation/latest/mqtt.html#wildcard-subscriptions]
> makes the recommendation to use the following configuration to match the
> MQTT specification for better performance:
> {code:java}
>
>/
>#
>*
> {code}
> Shouldn't it recommend "+" instead of "*" for single levels?
> Additionally, it would be good to clarify where this XML node is supposed to
> go. Top level? Inside {{{}{}}}? Inside {{{}{}}}?
> Somewhere else?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (AMQ-9330) Polling empty queue via REST returns 500 Server Error
[ https://issues.apache.org/jira/browse/AMQ-9330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836200#comment-17836200 ] Christopher L. Shannon commented on AMQ-9330: - The issue was we needed to call the complete() method on the context (otherwise the spec says 500 error is returned) and also set the right status code, I made the change updated tests to verify > Polling empty queue via REST returns 500 Server Error > - > > Key: AMQ-9330 > URL: https://issues.apache.org/jira/browse/AMQ-9330 > Project: ActiveMQ Classic > Issue Type: Bug >Affects Versions: 5.18.2 >Reporter: Michael Hoyt >Assignee: Christopher L. Shannon >Priority: Major > Fix For: 5.18.5, 6.1.2 > > Time Spent: 20m > Remaining Estimate: 0h > > In AMQ 5.18.1 Polling an empty queue via the REST api returned a 204 No > Content response. In 5.18.2 that same method now returns a 500 Server Error > response. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (AMQ-9330) Polling empty queue via REST returns 500 Server Error
[ https://issues.apache.org/jira/browse/AMQ-9330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon resolved AMQ-9330. - Resolution: Fixed > Polling empty queue via REST returns 500 Server Error > - > > Key: AMQ-9330 > URL: https://issues.apache.org/jira/browse/AMQ-9330 > Project: ActiveMQ Classic > Issue Type: Bug >Affects Versions: 5.18.2 >Reporter: Michael Hoyt >Assignee: Christopher L. Shannon >Priority: Major > Fix For: 5.18.5, 6.1.2 > > Time Spent: 20m > Remaining Estimate: 0h > > In AMQ 5.18.1 Polling an empty queue via the REST api returned a 204 No > Content response. In 5.18.2 that same method now returns a 500 Server Error > response. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (AMQ-9330) Polling empty queue via REST returns 500 Server Error
[ https://issues.apache.org/jira/browse/AMQ-9330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836197#comment-17836197 ] ASF subversion and git services commented on AMQ-9330: -- Commit dc892d3dfc2f4b7d0402d947f40431ce4e50d92d in activemq's branch refs/heads/activemq-5.18.x from Christopher L. Shannon [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=dc892d3df ] AMQ-9330 - Return 204 code when polling empty destinations (#1203) Previously a timeout was thrown and complete was not called so Jetty was returning a 500 error (cherry picked from commit 8b6072d03e273b02288e71cac6eef0539c48ea02) (cherry picked from commit 45a1bd54d3e1202d775388cf5b7d63e4c96183a5) > Polling empty queue via REST returns 500 Server Error > - > > Key: AMQ-9330 > URL: https://issues.apache.org/jira/browse/AMQ-9330 > Project: ActiveMQ Classic > Issue Type: Bug >Affects Versions: 5.18.2 >Reporter: Michael Hoyt >Assignee: Christopher L. Shannon >Priority: Major > Fix For: 5.18.5, 6.1.2 > > Time Spent: 20m > Remaining Estimate: 0h > > In AMQ 5.18.1 Polling an empty queue via the REST api returned a 204 No > Content response. In 5.18.2 that same method now returns a 500 Server Error > response. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4720) Add additional example for AMQP federation showing TLS configuration
[ https://issues.apache.org/jira/browse/ARTEMIS-4720?focusedWorklogId=914177=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-914177 ] ASF GitHub Bot logged work on ARTEMIS-4720: --- Author: ASF GitHub Bot Created on: 11/Apr/24 14:02 Start Date: 11/Apr/24 14:02 Worklog Time Spent: 10m Work Description: tabish121 commented on PR #9: URL: https://github.com/apache/activemq-artemis-examples/pull/9#issuecomment-2049765432 > The example wasnt added to the verification script, so the CI checks wont be running it. > > Might be worth reference the .txt file to create the stores from the example README. Added this plus another missed example to the script and update the README. Issue Time Tracking --- Worklog Id: (was: 914177) Time Spent: 0.5h (was: 20m) > Add additional example for AMQP federation showing TLS configuration > > > Key: ARTEMIS-4720 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4720 > Project: ActiveMQ Artemis > Issue Type: Task > Components: ActiveMQ-Artemis-Examples, AMQP >Affects Versions: 2.33.0 >Reporter: Timothy A. Bish >Assignee: Timothy A. Bish >Priority: Trivial > Fix For: 2.34.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Add a new example in the AMQP Federation examples showing how to configure > the broker connections to use TLS to connect to the remote. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (AMQ-9330) Polling empty queue via REST returns 500 Server Error
[ https://issues.apache.org/jira/browse/AMQ-9330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836196#comment-17836196 ] ASF subversion and git services commented on AMQ-9330: -- Commit 8b6072d03e273b02288e71cac6eef0539c48ea02 in activemq's branch refs/heads/main from Christopher L. Shannon [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=8b6072d03 ] AMQ-9330 - Return 204 code when polling empty destinations (#1203) Previously a timeout was thrown and complete was not called so Jetty was returning a 500 error > Polling empty queue via REST returns 500 Server Error > - > > Key: AMQ-9330 > URL: https://issues.apache.org/jira/browse/AMQ-9330 > Project: ActiveMQ Classic > Issue Type: Bug >Affects Versions: 5.18.2 >Reporter: Michael Hoyt >Assignee: Christopher L. Shannon >Priority: Major > Fix For: 5.18.5, 6.1.2 > > Time Spent: 20m > Remaining Estimate: 0h > > In AMQ 5.18.1 Polling an empty queue via the REST api returned a 204 No > Content response. In 5.18.2 that same method now returns a 500 Server Error > response. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (AMQ-9330) Polling empty queue via REST returns 500 Server Error
[ https://issues.apache.org/jira/browse/AMQ-9330?focusedWorklogId=914174=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-914174 ] ASF GitHub Bot logged work on AMQ-9330: --- Author: ASF GitHub Bot Created on: 11/Apr/24 13:59 Start Date: 11/Apr/24 13:59 Worklog Time Spent: 10m Work Description: cshannon merged PR #1203: URL: https://github.com/apache/activemq/pull/1203 Issue Time Tracking --- Worklog Id: (was: 914174) Time Spent: 20m (was: 10m) > Polling empty queue via REST returns 500 Server Error > - > > Key: AMQ-9330 > URL: https://issues.apache.org/jira/browse/AMQ-9330 > Project: ActiveMQ Classic > Issue Type: Bug >Affects Versions: 5.18.2 >Reporter: Michael Hoyt >Assignee: Christopher L. Shannon >Priority: Major > Fix For: 5.18.5, 6.1.2 > > Time Spent: 20m > Remaining Estimate: 0h > > In AMQ 5.18.1 Polling an empty queue via the REST api returned a 204 No > Content response. In 5.18.2 that same method now returns a 500 Server Error > response. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4680) Upgrade the console to use HawtIO 4
[
https://issues.apache.org/jira/browse/ARTEMIS-4680?focusedWorklogId=914172=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-914172
]
ASF GitHub Bot logged work on ARTEMIS-4680:
---
Author: ASF GitHub Bot
Created on: 11/Apr/24 13:58
Start Date: 11/Apr/24 13:58
Worklog Time Spent: 10m
Work Description: andytaylor commented on code in PR #3:
URL:
https://github.com/apache/activemq-artemis-console-plugin/pull/3#discussion_r1561070218
##
artemis-plugin/craco.config.js:
##
@@ -0,0 +1,152 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+ const { ModuleFederationPlugin } = require('webpack').container
+const CracoEsbuildPlugin = require('craco-esbuild')
+const { hawtioBackend } = require('@hawtio/backend-middleware')
+const { dependencies } = require('./package.json')
+
+module.exports = {
+ plugins: [{ plugin: CracoEsbuildPlugin }],
+ webpack: {
+plugins: {
+ add: [
+new ModuleFederationPlugin({
+ // The container name corresponds to 'scope' passed to HawtioPlugin
+ name: 'artemisPlugin',
+ filename: 'remoteEntry.js',
+ // The key in exposes corresponds to 'remote' passed to HawtioPlugin
+ exposes: {
+'./plugin': './src/artemis-plugin',
+ },
+ shared: {
+...dependencies,
+react: {
+ singleton: true,
+ requiredVersion: dependencies['react'],
+},
+'react-dom': {
+ singleton: true,
+ requiredVersion: dependencies['react-dom'],
+},
+'react-router-dom': {
+ singleton: true,
+ requiredVersion: dependencies['react-router-dom'],
+},
+'@hawtio/react': {
+ singleton: true,
+ requiredVersion: dependencies['@hawtio/react'],
+},
+ },
+}),
+ ],
+},
+configure: webpackConfig => {
+ // Required for Module Federation
+ webpackConfig.output.publicPath = 'auto'
+
+ webpackConfig.module.rules.push({
+test: /\.md/,
+type: 'asset/source',
+ })
+
+ // For suppressing sourcemap warnings from dependencies
+ webpackConfig.ignoreWarnings = [/Failed to parse source map/]
+
+ // To resolve errors for @module-federation/utilities 2.x
+ // https://github.com/module-federation/universe/issues/827
+ webpackConfig.resolve = {
+...webpackConfig.resolve,
+fallback: {
+ path: require.resolve('path-browserify'),
+ os: require.resolve('os-browserify'),
+},
+ }
+
+ // MiniCssExtractPlugin - Ignore order as otherwise conflicting order
warning is raised
+ const miniCssExtractPlugin = webpackConfig.plugins.find(p =>
p.constructor.name === 'MiniCssExtractPlugin')
+ if (miniCssExtractPlugin) {
+miniCssExtractPlugin.options.ignoreOrder = true
+ }
+
+ return webpackConfig
+},
+ },
+ // For plugin development
+ devServer: {
+setupMiddlewares: (middlewares, devServer) => {
+ // Enabling branding in dev mode
+ devServer.app.use((req, _, next) => {
+if (req.url.startsWith('/artemis-plugin')) {
+ req.url = req.url.replace(/\/artemis-plugin(.*)/, '/hawtio$1')
+}
+next()
+ })
+ // Redirect / or /console to /console/
+ devServer.app.get('/', (_, res) => res.redirect('/console/'))
+ devServer.app.get('/console$', (_, res) => res.redirect('/console/'))
+
+ const username = 'developer'
+ const proxyEnabled = true
+ const plugin = []
+ const hawtconfig = {}
+
+ /**const keycloakEnabled = false
+ const keycloakClientConfig = {
+ }
+ const keycloakClientConfig = {
+realm: 'artemis-keycloak-demo',
+clientId: 'artemis-console',
+url: 'http://localhost:8080/',
+jaas: false,
+pkceMethod: 'S256',
+ }*/
Review Comment:
removed
##
artemis-plugin/craco.config.js:
##
@@ -0,0 +1,152 @@
+/*
+ * Licensed to the Apache Software
[jira] [Work logged] (ARTEMIS-4680) Upgrade the console to use HawtIO 4
[ https://issues.apache.org/jira/browse/ARTEMIS-4680?focusedWorklogId=914171=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-914171 ] ASF GitHub Bot logged work on ARTEMIS-4680: --- Author: ASF GitHub Bot Created on: 11/Apr/24 13:58 Start Date: 11/Apr/24 13:58 Worklog Time Spent: 10m Work Description: andytaylor commented on code in PR #3: URL: https://github.com/apache/activemq-artemis-console-plugin/pull/3#discussion_r1561069126 ## LICENSE: ## @@ -0,0 +1,326 @@ + + Apache License + Version 2.0, January 2004 +http://www.apache.org/licenses/ + + TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION + + 1. Definitions. + + "License" shall mean the terms and conditions for use, reproduction, + and distribution as defined by Sections 1 through 9 of this document. + + "Licensor" shall mean the copyright owner or entity authorized by + the copyright owner that is granting the License. + + "Legal Entity" shall mean the union of the acting entity and all + other entities that control, are controlled by, or are under common + control with that entity. For the purposes of this definition, + "control" means (i) the power, direct or indirect, to cause the + direction or management of such entity, whether by contract or + otherwise, or (ii) ownership of fifty percent (50%) or more of the + outstanding shares, or (iii) beneficial ownership of such entity. + + "You" (or "Your") shall mean an individual or Legal Entity + exercising permissions granted by this License. + + "Source" form shall mean the preferred form for making modifications, + including but not limited to software source code, documentation + source, and configuration files. + + "Object" form shall mean any form resulting from mechanical + transformation or translation of a Source form, including but + not limited to compiled object code, generated documentation, + and conversions to other media types. + + "Work" shall mean the work of authorship, whether in Source or + Object form, made available under the License, as indicated by a + copyright notice that is included in or attached to the work + (an example is provided in the Appendix below). + + "Derivative Works" shall mean any work, whether in Source or Object + form, that is based on (or derived from) the Work and for which the + editorial revisions, annotations, elaborations, or other modifications + represent, as a whole, an original work of authorship. For the purposes + of this License, Derivative Works shall not include works that remain + separable from, or merely link (or bind by name) to the interfaces of, + the Work and Derivative Works thereof. + + "Contribution" shall mean any work of authorship, including + the original version of the Work and any modifications or additions + to that Work or Derivative Works thereof, that is intentionally + submitted to Licensor for inclusion in the Work by the copyright owner + or by an individual or Legal Entity authorized to submit on behalf of + the copyright owner. For the purposes of this definition, "submitted" + means any form of electronic, verbal, or written communication sent + to the Licensor or its representatives, including but not limited to + communication on electronic mailing lists, source code control systems, + and issue tracking systems that are managed by, or on behalf of, the + Licensor for the purpose of discussing and improving the Work, but + excluding communication that is conspicuously marked or otherwise + designated in writing by the copyright owner as "Not a Contribution." + + "Contributor" shall mean Licensor and any individual or Legal Entity + on behalf of whom a Contribution has been received by Licensor and + subsequently incorporated within the Work. + + 2. Grant of Copyright License. Subject to the terms and conditions of + this License, each Contributor hereby grants to You a perpetual, + worldwide, non-exclusive, no-charge, royalty-free, irrevocable + copyright license to reproduce, prepare Derivative Works of, + publicly display, publicly perform, sublicense, and distribute the + Work and such Derivative Works in Source or Object form. + + 3. Grant of Patent License. Subject to the terms and conditions of + this License, each Contributor hereby grants to You a perpetual, + worldwide, non-exclusive, no-charge, royalty-free, irrevocable + (except as stated in this section) patent license to make, have made, + use, offer to sell, sell, import, and otherwise transfer the Work, + where such license
[jira] [Work logged] (AMQ-9430) ActiveMQ 5.18.3 (Classic) and Java 17: runtimeConfigurationPlugin causes ClassNotFoundException
[ https://issues.apache.org/jira/browse/AMQ-9430?focusedWorklogId=914170=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-914170 ] ASF GitHub Bot logged work on AMQ-9430: --- Author: ASF GitHub Bot Created on: 11/Apr/24 13:46 Start Date: 11/Apr/24 13:46 Worklog Time Spent: 10m Work Description: mattrpav opened a new pull request, #1204: URL: https://github.com/apache/activemq/pull/1204 (no comment) Issue Time Tracking --- Worklog Id: (was: 914170) Remaining Estimate: 0h Time Spent: 10m > ActiveMQ 5.18.3 (Classic) and Java 17: runtimeConfigurationPlugin causes > ClassNotFoundException > --- > > Key: AMQ-9430 > URL: https://issues.apache.org/jira/browse/AMQ-9430 > Project: ActiveMQ Classic > Issue Type: Bug > Components: Broker, JMX, Plugin >Affects Versions: 5.18.3 > Environment: Linux myhost 6.5.0-14-generic #14~22.04.1-Ubuntu SMP > PREEMPT_DYNAMIC Mon Nov 20 18:15:30 UTC 2 x86_64 x86_64 x86_64 GNU/Linux > > java -version > > > openjdk version "17.0.9" 2023-10-17 > OpenJDK Runtime Environment (build 17.0.9+9-Ubuntu-122.04) > OpenJDK 64-Bit Server VM (build 17.0.9+9-Ubuntu-122.04, mixed mode, sharing) >Reporter: Mika Räty >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.18.5, 6.1.2 > > Time Spent: 10m > Remaining Estimate: 0h > > We are upgrading from java 8 to java 17 in a project that uses ActiveMQ > 5.18.3 and we noticed that when we try to use the JMX operation updateNow > that is available from Bean > > org.apache.activemq:type=Broker,brokerName=localhost,service=RuntimeConfiguration,name=Plugin > > using java 17 based deployment we get the following error on jconsole screen > > Failed to parse: class path resource [activemq.xml], > javax.xml.bind.JAXBException > - with linked exception: > [java.lang.ClassNotFoundException: > com.sun.xml.internal.bind.v2.ContextFactory];No material change to > configuration in class path resource [activemq.xml] at: Tue Jan 30 13:09:40 > EET 2024; > > On the activemq output we see the following stack trace > > INFO | Manual configuration update triggered > INFO | Failed to parse: class path resource [activemq.xml] > javax.xml.bind.JAXBException: null > at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:241) > ~[jaxb-api-2.2.11.jar:?] > at javax.xml.bind.ContextFinder.find(ContextFinder.java:477) > ~[jaxb-api-2.2.11.jar:?] > at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:656) > ~[jaxb-api-2.2.11.jar:?] > at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:599) > ~[jaxb-api-2.2.11.jar:?] > at > org.apache.activemq.plugin.RuntimeConfigurationBroker.loadConfiguration(RuntimeConfigurationBroker.java:176) > ~[activemq-runtime-config-5.18.3.jar:5.18.3] > at > org.apache.activemq.plugin.RuntimeConfigurationBroker.applyModifications(RuntimeConfigurationBroker.java:141) > ~[activemq-runtime-config-5.18.3.jar:5.18.3] > at > org.apache.activemq.plugin.RuntimeConfigurationBroker.updateNow(RuntimeConfigurationBroker.java:113) > ~[activemq-runtime-config-5.18.3.jar:5.18.3] > at > org.apache.activemq.plugin.jmx.RuntimeConfigurationView.updateNow(RuntimeConfigurationView.java:53) > ~[activemq-runtime-config-5.18.3.jar:5.18.3] > at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native > Method) ~[?:?] > at > jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) > ~[?:?] > ... [ some frames omitted for brevity ] > > Caused by: java.lang.ClassNotFoundException: > com.sun.xml.internal.bind.v2.ContextFactory > at > jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:641) > ~[?:?] > at > jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188) > ~[?:?] > at java.lang.ClassLoader.loadClass(ClassLoader.java:525) ~[?:?] > at javax.xml.bind.ContextFinder.safeLoadClass(ContextFinder.java:594) > ~[jaxb-api-2.2.11.jar:?] > at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:239) > ~[jaxb-api-2.2.11.jar:?] > ... 43 more > INFO | No material change to configuration in class path resource > [activemq.xml] at: Tue Jan 30 12:59:42 EET 2024 > > Java version info > java -version > openjdk version "17.0.9" 2023-10-17 > OpenJDK Runtime Environment (build 17.0.9+9-Ubuntu-122.04) > OpenJDK 64-Bit Server VM
[jira] [Work logged] (AMQ-9330) Polling empty queue via REST returns 500 Server Error
[ https://issues.apache.org/jira/browse/AMQ-9330?focusedWorklogId=914169=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-914169 ] ASF GitHub Bot logged work on AMQ-9330: --- Author: ASF GitHub Bot Created on: 11/Apr/24 13:44 Start Date: 11/Apr/24 13:44 Worklog Time Spent: 10m Work Description: cshannon opened a new pull request, #1203: URL: https://github.com/apache/activemq/pull/1203 Previously a timeout was thrown and complete was not called so Jetty was returning a 500 error Issue Time Tracking --- Worklog Id: (was: 914169) Remaining Estimate: 0h Time Spent: 10m > Polling empty queue via REST returns 500 Server Error > - > > Key: AMQ-9330 > URL: https://issues.apache.org/jira/browse/AMQ-9330 > Project: ActiveMQ Classic > Issue Type: Bug >Affects Versions: 5.18.2 >Reporter: Michael Hoyt >Assignee: Christopher L. Shannon >Priority: Major > Fix For: 5.18.5, 6.1.2 > > Time Spent: 10m > Remaining Estimate: 0h > > In AMQ 5.18.1 Polling an empty queue via the REST api returned a 204 No > Content response. In 5.18.2 that same method now returns a 500 Server Error > response. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (AMQ-9330) Polling empty queue via REST returns 500 Server Error
[ https://issues.apache.org/jira/browse/AMQ-9330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon reassigned AMQ-9330: --- Assignee: Christopher L. Shannon (was: Jean-Baptiste Onofré) > Polling empty queue via REST returns 500 Server Error > - > > Key: AMQ-9330 > URL: https://issues.apache.org/jira/browse/AMQ-9330 > Project: ActiveMQ Classic > Issue Type: Bug >Affects Versions: 5.18.2 >Reporter: Michael Hoyt >Assignee: Christopher L. Shannon >Priority: Major > Fix For: 5.18.5, 6.1.2 > > > In AMQ 5.18.1 Polling an empty queue via the REST api returned a 204 No > Content response. In 5.18.2 that same method now returns a 500 Server Error > response. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] (AMQ-9330) Polling empty queue via REST returns 500 Server Error
[ https://issues.apache.org/jira/browse/AMQ-9330 ] Jean-Baptiste Onofré deleted comment on AMQ-9330: --- was (Author: jbonofre): I will add the fix for 5.18.5. > Polling empty queue via REST returns 500 Server Error > - > > Key: AMQ-9330 > URL: https://issues.apache.org/jira/browse/AMQ-9330 > Project: ActiveMQ Classic > Issue Type: Bug >Affects Versions: 5.18.2 >Reporter: Michael Hoyt >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.18.5, 6.1.2 > > > In AMQ 5.18.1 Polling an empty queue via the REST api returned a 204 No > Content response. In 5.18.2 that same method now returns a 500 Server Error > response. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (AMQ-9430) ActiveMQ 5.18.3 (Classic) and Java 17: runtimeConfigurationPlugin causes ClassNotFoundException
[ https://issues.apache.org/jira/browse/AMQ-9430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836176#comment-17836176 ] Jean-Baptiste Onofré commented on AMQ-9430: --- The problem is specific to JMX where using a different classloader. > ActiveMQ 5.18.3 (Classic) and Java 17: runtimeConfigurationPlugin causes > ClassNotFoundException > --- > > Key: AMQ-9430 > URL: https://issues.apache.org/jira/browse/AMQ-9430 > Project: ActiveMQ Classic > Issue Type: Bug > Components: Broker, JMX, Plugin >Affects Versions: 5.18.3 > Environment: Linux myhost 6.5.0-14-generic #14~22.04.1-Ubuntu SMP > PREEMPT_DYNAMIC Mon Nov 20 18:15:30 UTC 2 x86_64 x86_64 x86_64 GNU/Linux > > java -version > > > openjdk version "17.0.9" 2023-10-17 > OpenJDK Runtime Environment (build 17.0.9+9-Ubuntu-122.04) > OpenJDK 64-Bit Server VM (build 17.0.9+9-Ubuntu-122.04, mixed mode, sharing) >Reporter: Mika Räty >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.18.5 > > > We are upgrading from java 8 to java 17 in a project that uses ActiveMQ > 5.18.3 and we noticed that when we try to use the JMX operation updateNow > that is available from Bean > > org.apache.activemq:type=Broker,brokerName=localhost,service=RuntimeConfiguration,name=Plugin > > using java 17 based deployment we get the following error on jconsole screen > > Failed to parse: class path resource [activemq.xml], > javax.xml.bind.JAXBException > - with linked exception: > [java.lang.ClassNotFoundException: > com.sun.xml.internal.bind.v2.ContextFactory];No material change to > configuration in class path resource [activemq.xml] at: Tue Jan 30 13:09:40 > EET 2024; > > On the activemq output we see the following stack trace > > INFO | Manual configuration update triggered > INFO | Failed to parse: class path resource [activemq.xml] > javax.xml.bind.JAXBException: null > at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:241) > ~[jaxb-api-2.2.11.jar:?] > at javax.xml.bind.ContextFinder.find(ContextFinder.java:477) > ~[jaxb-api-2.2.11.jar:?] > at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:656) > ~[jaxb-api-2.2.11.jar:?] > at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:599) > ~[jaxb-api-2.2.11.jar:?] > at > org.apache.activemq.plugin.RuntimeConfigurationBroker.loadConfiguration(RuntimeConfigurationBroker.java:176) > ~[activemq-runtime-config-5.18.3.jar:5.18.3] > at > org.apache.activemq.plugin.RuntimeConfigurationBroker.applyModifications(RuntimeConfigurationBroker.java:141) > ~[activemq-runtime-config-5.18.3.jar:5.18.3] > at > org.apache.activemq.plugin.RuntimeConfigurationBroker.updateNow(RuntimeConfigurationBroker.java:113) > ~[activemq-runtime-config-5.18.3.jar:5.18.3] > at > org.apache.activemq.plugin.jmx.RuntimeConfigurationView.updateNow(RuntimeConfigurationView.java:53) > ~[activemq-runtime-config-5.18.3.jar:5.18.3] > at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native > Method) ~[?:?] > at > jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) > ~[?:?] > ... [ some frames omitted for brevity ] > > Caused by: java.lang.ClassNotFoundException: > com.sun.xml.internal.bind.v2.ContextFactory > at > jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:641) > ~[?:?] > at > jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188) > ~[?:?] > at java.lang.ClassLoader.loadClass(ClassLoader.java:525) ~[?:?] > at javax.xml.bind.ContextFinder.safeLoadClass(ContextFinder.java:594) > ~[jaxb-api-2.2.11.jar:?] > at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:239) > ~[jaxb-api-2.2.11.jar:?] > ... 43 more > INFO | No material change to configuration in class path resource > [activemq.xml] at: Tue Jan 30 12:59:42 EET 2024 > > Java version info > java -version > openjdk version "17.0.9" 2023-10-17 > OpenJDK Runtime Environment (build 17.0.9+9-Ubuntu-122.04) > OpenJDK 64-Bit Server VM (build 17.0.9+9-Ubuntu-122.04, mixed mode, sharing) > > > Reproducing the above error: > > # extract amq package to linux host > tar xvf apache-activemq-5.18.3-bin.tar > # Add plugin to activemq.xml > > > > # Add start="false" to broker tag > according to instructions from here > [https://activemq.apache.org/runtime-configuration] > # Starting activemq with > activemq start > # Connect to the
[jira] [Updated] (AMQ-9430) ActiveMQ 5.18.3 (Classic) and Java 17: runtimeConfigurationPlugin causes ClassNotFoundException
[ https://issues.apache.org/jira/browse/AMQ-9430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated AMQ-9430: -- Fix Version/s: 6.1.2 > ActiveMQ 5.18.3 (Classic) and Java 17: runtimeConfigurationPlugin causes > ClassNotFoundException > --- > > Key: AMQ-9430 > URL: https://issues.apache.org/jira/browse/AMQ-9430 > Project: ActiveMQ Classic > Issue Type: Bug > Components: Broker, JMX, Plugin >Affects Versions: 5.18.3 > Environment: Linux myhost 6.5.0-14-generic #14~22.04.1-Ubuntu SMP > PREEMPT_DYNAMIC Mon Nov 20 18:15:30 UTC 2 x86_64 x86_64 x86_64 GNU/Linux > > java -version > > > openjdk version "17.0.9" 2023-10-17 > OpenJDK Runtime Environment (build 17.0.9+9-Ubuntu-122.04) > OpenJDK 64-Bit Server VM (build 17.0.9+9-Ubuntu-122.04, mixed mode, sharing) >Reporter: Mika Räty >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.18.5, 6.1.2 > > > We are upgrading from java 8 to java 17 in a project that uses ActiveMQ > 5.18.3 and we noticed that when we try to use the JMX operation updateNow > that is available from Bean > > org.apache.activemq:type=Broker,brokerName=localhost,service=RuntimeConfiguration,name=Plugin > > using java 17 based deployment we get the following error on jconsole screen > > Failed to parse: class path resource [activemq.xml], > javax.xml.bind.JAXBException > - with linked exception: > [java.lang.ClassNotFoundException: > com.sun.xml.internal.bind.v2.ContextFactory];No material change to > configuration in class path resource [activemq.xml] at: Tue Jan 30 13:09:40 > EET 2024; > > On the activemq output we see the following stack trace > > INFO | Manual configuration update triggered > INFO | Failed to parse: class path resource [activemq.xml] > javax.xml.bind.JAXBException: null > at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:241) > ~[jaxb-api-2.2.11.jar:?] > at javax.xml.bind.ContextFinder.find(ContextFinder.java:477) > ~[jaxb-api-2.2.11.jar:?] > at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:656) > ~[jaxb-api-2.2.11.jar:?] > at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:599) > ~[jaxb-api-2.2.11.jar:?] > at > org.apache.activemq.plugin.RuntimeConfigurationBroker.loadConfiguration(RuntimeConfigurationBroker.java:176) > ~[activemq-runtime-config-5.18.3.jar:5.18.3] > at > org.apache.activemq.plugin.RuntimeConfigurationBroker.applyModifications(RuntimeConfigurationBroker.java:141) > ~[activemq-runtime-config-5.18.3.jar:5.18.3] > at > org.apache.activemq.plugin.RuntimeConfigurationBroker.updateNow(RuntimeConfigurationBroker.java:113) > ~[activemq-runtime-config-5.18.3.jar:5.18.3] > at > org.apache.activemq.plugin.jmx.RuntimeConfigurationView.updateNow(RuntimeConfigurationView.java:53) > ~[activemq-runtime-config-5.18.3.jar:5.18.3] > at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native > Method) ~[?:?] > at > jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) > ~[?:?] > ... [ some frames omitted for brevity ] > > Caused by: java.lang.ClassNotFoundException: > com.sun.xml.internal.bind.v2.ContextFactory > at > jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:641) > ~[?:?] > at > jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188) > ~[?:?] > at java.lang.ClassLoader.loadClass(ClassLoader.java:525) ~[?:?] > at javax.xml.bind.ContextFinder.safeLoadClass(ContextFinder.java:594) > ~[jaxb-api-2.2.11.jar:?] > at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:239) > ~[jaxb-api-2.2.11.jar:?] > ... 43 more > INFO | No material change to configuration in class path resource > [activemq.xml] at: Tue Jan 30 12:59:42 EET 2024 > > Java version info > java -version > openjdk version "17.0.9" 2023-10-17 > OpenJDK Runtime Environment (build 17.0.9+9-Ubuntu-122.04) > OpenJDK 64-Bit Server VM (build 17.0.9+9-Ubuntu-122.04, mixed mode, sharing) > > > Reproducing the above error: > > # extract amq package to linux host > tar xvf apache-activemq-5.18.3-bin.tar > # Add plugin to activemq.xml > > > > # Add start="false" to broker tag > according to instructions from here > [https://activemq.apache.org/runtime-configuration] > # Starting activemq with > activemq start > # Connect to the started amq instance with jconsole and call the updateNow > operation > > >
[jira] [Commented] (AMQ-9430) ActiveMQ 5.18.3 (Classic) and Java 17: runtimeConfigurationPlugin causes ClassNotFoundException
[
https://issues.apache.org/jira/browse/AMQ-9430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836175#comment-17836175
]
Matt Pavlovich commented on AMQ-9430:
-
I'm able to reproduce with JDK 11 and JDK 17. I believe the issue is
classloader related as it only impacts when the JMX operation is invoked.
Manual update (via JMX) has error:
{noformat}
INFO | Manual configuration update triggered
INFO | Failed to parse: class path resource [activemq.xml]
javax.xml.bind.JAXBException: null
at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:241)
~[jaxb-api-2.2.11.jar:?]
at javax.xml.bind.ContextFinder.find(ContextFinder.java:477)
~[jaxb-api-2.2.11.jar:?]
at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:656)
~[jaxb-api-2.2.11.jar:?]
at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:599)
~[jaxb-api-2.2.11.jar:?]
at
org.apache.activemq.plugin.RuntimeConfigurationBroker.loadConfiguration(RuntimeConfigurationBroker.java:176)
~[activemq-runtime-config-5.18.3.jar:5.18.3]
at
org.apache.activemq.plugin.RuntimeConfigurationBroker.applyModifications(RuntimeConfigurationBroker.java:141)
~[activemq-runtime-config-5.18.3.jar:5.18.3]
at
org.apache.activemq.plugin.RuntimeConfigurationBroker.updateNow(RuntimeConfigurationBroker.java:113)
~[activemq-runtime-config-5.18.3.jar:5.18.3]
at
org.apache.activemq.plugin.jmx.RuntimeConfigurationView.updateNow(RuntimeConfigurationView.java:53)
~[activemq-runtime-config-5.18.3.jar:5.18.3]
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
~[?:?]
at
jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
~[?:?]
at
jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
~[?:?]
at java.lang.reflect.Method.invoke(Method.java:566) ~[?:?]
at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:71) ~[?:?]
at jdk.internal.reflect.GeneratedMethodAccessor40.invoke(Unknown
Source) ~[?:?]
at
jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
~[?:?]
at java.lang.reflect.Method.invoke(Method.java:566) ~[?:?]
at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:260) ~[?:?]
at
com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:112)
~[?:?]
at
com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:46)
~[?:?]
at
com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:237)
~[?:?]
at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:138)
~[?:?]
at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:252)
~[?:?]
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:809)
~[?:?]
at
com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801) ~[?:?]
at
javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1466)
~[?:?]
at
javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1307)
~[?:?]
at
javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1399)
~[?:?]
at
javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:827)
~[?:?]
at jdk.internal.reflect.GeneratedMethodAccessor49.invoke(Unknown
Source) ~[?:?]
at
jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
~[?:?]
at java.lang.reflect.Method.invoke(Method.java:566) ~[?:?]
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:359)
~[?:?]
at sun.rmi.transport.Transport$1.run(Transport.java:200) ~[?:?]
at sun.rmi.transport.Transport$1.run(Transport.java:197) ~[?:?]
at java.security.AccessController.doPrivileged(Native Method) ~[?:?]
at sun.rmi.transport.Transport.serviceCall(Transport.java:196) ~[?:?]
at
sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:562) ~[?:?]
at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:796)
~[?:?]
at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:677)
~[?:?]
at java.security.AccessController.doPrivileged(Native Method) ~[?:?]
at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:676)
[?:?]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
[?:?]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
[?:?]
at java.lang.Thread.run(Thread.java:834) [?:?]
Caused by: java.lang.ClassNotFoundException:
[jira] [Updated] (AMQ-9430) ActiveMQ 5.18.3 (Classic) and Java 17: runtimeConfigurationPlugin causes ClassNotFoundException
[ https://issues.apache.org/jira/browse/AMQ-9430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated AMQ-9430: -- Fix Version/s: (was: 6.2.0) (was: 6.1.2) > ActiveMQ 5.18.3 (Classic) and Java 17: runtimeConfigurationPlugin causes > ClassNotFoundException > --- > > Key: AMQ-9430 > URL: https://issues.apache.org/jira/browse/AMQ-9430 > Project: ActiveMQ Classic > Issue Type: Bug > Components: Broker, JMX, Plugin >Affects Versions: 5.18.3 > Environment: Linux myhost 6.5.0-14-generic #14~22.04.1-Ubuntu SMP > PREEMPT_DYNAMIC Mon Nov 20 18:15:30 UTC 2 x86_64 x86_64 x86_64 GNU/Linux > > java -version > > > openjdk version "17.0.9" 2023-10-17 > OpenJDK Runtime Environment (build 17.0.9+9-Ubuntu-122.04) > OpenJDK 64-Bit Server VM (build 17.0.9+9-Ubuntu-122.04, mixed mode, sharing) >Reporter: Mika Räty >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.18.5 > > > We are upgrading from java 8 to java 17 in a project that uses ActiveMQ > 5.18.3 and we noticed that when we try to use the JMX operation updateNow > that is available from Bean > > org.apache.activemq:type=Broker,brokerName=localhost,service=RuntimeConfiguration,name=Plugin > > using java 17 based deployment we get the following error on jconsole screen > > Failed to parse: class path resource [activemq.xml], > javax.xml.bind.JAXBException > - with linked exception: > [java.lang.ClassNotFoundException: > com.sun.xml.internal.bind.v2.ContextFactory];No material change to > configuration in class path resource [activemq.xml] at: Tue Jan 30 13:09:40 > EET 2024; > > On the activemq output we see the following stack trace > > INFO | Manual configuration update triggered > INFO | Failed to parse: class path resource [activemq.xml] > javax.xml.bind.JAXBException: null > at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:241) > ~[jaxb-api-2.2.11.jar:?] > at javax.xml.bind.ContextFinder.find(ContextFinder.java:477) > ~[jaxb-api-2.2.11.jar:?] > at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:656) > ~[jaxb-api-2.2.11.jar:?] > at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:599) > ~[jaxb-api-2.2.11.jar:?] > at > org.apache.activemq.plugin.RuntimeConfigurationBroker.loadConfiguration(RuntimeConfigurationBroker.java:176) > ~[activemq-runtime-config-5.18.3.jar:5.18.3] > at > org.apache.activemq.plugin.RuntimeConfigurationBroker.applyModifications(RuntimeConfigurationBroker.java:141) > ~[activemq-runtime-config-5.18.3.jar:5.18.3] > at > org.apache.activemq.plugin.RuntimeConfigurationBroker.updateNow(RuntimeConfigurationBroker.java:113) > ~[activemq-runtime-config-5.18.3.jar:5.18.3] > at > org.apache.activemq.plugin.jmx.RuntimeConfigurationView.updateNow(RuntimeConfigurationView.java:53) > ~[activemq-runtime-config-5.18.3.jar:5.18.3] > at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native > Method) ~[?:?] > at > jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) > ~[?:?] > ... [ some frames omitted for brevity ] > > Caused by: java.lang.ClassNotFoundException: > com.sun.xml.internal.bind.v2.ContextFactory > at > jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:641) > ~[?:?] > at > jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188) > ~[?:?] > at java.lang.ClassLoader.loadClass(ClassLoader.java:525) ~[?:?] > at javax.xml.bind.ContextFinder.safeLoadClass(ContextFinder.java:594) > ~[jaxb-api-2.2.11.jar:?] > at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:239) > ~[jaxb-api-2.2.11.jar:?] > ... 43 more > INFO | No material change to configuration in class path resource > [activemq.xml] at: Tue Jan 30 12:59:42 EET 2024 > > Java version info > java -version > openjdk version "17.0.9" 2023-10-17 > OpenJDK Runtime Environment (build 17.0.9+9-Ubuntu-122.04) > OpenJDK 64-Bit Server VM (build 17.0.9+9-Ubuntu-122.04, mixed mode, sharing) > > > Reproducing the above error: > > # extract amq package to linux host > tar xvf apache-activemq-5.18.3-bin.tar > # Add plugin to activemq.xml > > > > # Add start="false" to broker tag > according to instructions from here > [https://activemq.apache.org/runtime-configuration] > # Starting activemq with > activemq start > # Connect to the started amq instance with jconsole and
[jira] [Commented] (AMQ-9430) ActiveMQ 5.18.3 (Classic) and Java 17: runtimeConfigurationPlugin causes ClassNotFoundException
[
https://issues.apache.org/jira/browse/AMQ-9430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836173#comment-17836173
]
Jean-Baptiste Onofré commented on AMQ-9430:
---
Just tested ActiveMQ 6.1.2-SNAPSHOT with JDK17, and it works fine. I changed
the configuration on the fly and I can see:
{code:java}
INFO | Monitoring for updates (every 1000millis) : class path resource
[activemq.xml], lastUpdate: Thu Apr 11 15:20:38 CEST 2024 {code}
> ActiveMQ 5.18.3 (Classic) and Java 17: runtimeConfigurationPlugin causes
> ClassNotFoundException
> ---
>
> Key: AMQ-9430
> URL: https://issues.apache.org/jira/browse/AMQ-9430
> Project: ActiveMQ Classic
> Issue Type: Bug
> Components: Broker, JMX, Plugin
>Affects Versions: 5.18.3
> Environment: Linux myhost 6.5.0-14-generic #14~22.04.1-Ubuntu SMP
> PREEMPT_DYNAMIC Mon Nov 20 18:15:30 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
>
> java -version
>
>
> openjdk version "17.0.9" 2023-10-17
> OpenJDK Runtime Environment (build 17.0.9+9-Ubuntu-122.04)
> OpenJDK 64-Bit Server VM (build 17.0.9+9-Ubuntu-122.04, mixed mode, sharing)
>Reporter: Mika Räty
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 6.2.0, 5.18.5, 6.1.2
>
>
> We are upgrading from java 8 to java 17 in a project that uses ActiveMQ
> 5.18.3 and we noticed that when we try to use the JMX operation updateNow
> that is available from Bean
>
> org.apache.activemq:type=Broker,brokerName=localhost,service=RuntimeConfiguration,name=Plugin
>
> using java 17 based deployment we get the following error on jconsole screen
>
> Failed to parse: class path resource [activemq.xml],
> javax.xml.bind.JAXBException
> - with linked exception:
> [java.lang.ClassNotFoundException:
> com.sun.xml.internal.bind.v2.ContextFactory];No material change to
> configuration in class path resource [activemq.xml] at: Tue Jan 30 13:09:40
> EET 2024;
>
> On the activemq output we see the following stack trace
>
> INFO | Manual configuration update triggered
> INFO | Failed to parse: class path resource [activemq.xml]
> javax.xml.bind.JAXBException: null
> at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:241)
> ~[jaxb-api-2.2.11.jar:?]
> at javax.xml.bind.ContextFinder.find(ContextFinder.java:477)
> ~[jaxb-api-2.2.11.jar:?]
> at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:656)
> ~[jaxb-api-2.2.11.jar:?]
> at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:599)
> ~[jaxb-api-2.2.11.jar:?]
> at
> org.apache.activemq.plugin.RuntimeConfigurationBroker.loadConfiguration(RuntimeConfigurationBroker.java:176)
> ~[activemq-runtime-config-5.18.3.jar:5.18.3]
> at
> org.apache.activemq.plugin.RuntimeConfigurationBroker.applyModifications(RuntimeConfigurationBroker.java:141)
> ~[activemq-runtime-config-5.18.3.jar:5.18.3]
> at
> org.apache.activemq.plugin.RuntimeConfigurationBroker.updateNow(RuntimeConfigurationBroker.java:113)
> ~[activemq-runtime-config-5.18.3.jar:5.18.3]
> at
> org.apache.activemq.plugin.jmx.RuntimeConfigurationView.updateNow(RuntimeConfigurationView.java:53)
> ~[activemq-runtime-config-5.18.3.jar:5.18.3]
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method) ~[?:?]
> at
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
> ~[?:?]
> ... [ some frames omitted for brevity ]
>
> Caused by: java.lang.ClassNotFoundException:
> com.sun.xml.internal.bind.v2.ContextFactory
> at
> jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:641)
> ~[?:?]
> at
> jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188)
> ~[?:?]
> at java.lang.ClassLoader.loadClass(ClassLoader.java:525) ~[?:?]
> at javax.xml.bind.ContextFinder.safeLoadClass(ContextFinder.java:594)
> ~[jaxb-api-2.2.11.jar:?]
> at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:239)
> ~[jaxb-api-2.2.11.jar:?]
> ... 43 more
> INFO | No material change to configuration in class path resource
> [activemq.xml] at: Tue Jan 30 12:59:42 EET 2024
>
> Java version info
> java -version
> openjdk version "17.0.9" 2023-10-17
> OpenJDK Runtime Environment (build 17.0.9+9-Ubuntu-122.04)
> OpenJDK 64-Bit Server VM (build 17.0.9+9-Ubuntu-122.04, mixed mode, sharing)
>
>
> Reproducing the above error:
>
> # extract amq package to linux host
> tar xvf apache-activemq-5.18.3-bin.tar
> # Add plugin to
[jira] [Updated] (ARTEMIS-4722) Exclude netty-tcnative-boringssl-static artifacts
[ https://issues.apache.org/jira/browse/ARTEMIS-4722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Domenico Francesco Bruscino updated ARTEMIS-4722: - Description: The lib folder includes netty-tcnative-boringssl-static artifacts non-aligned with the netty-tcnative-version in pom.xml. Those artifacts are included because of zookeeper-server. (was: The lib folder includes netty-tcnative-boringssl-static artifacts non-aligned with the netty-tcnative-version in pom.xml. Those artifacts are included only because of zookeeper-server.) > Exclude netty-tcnative-boringssl-static artifacts > - > > Key: ARTEMIS-4722 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4722 > Project: ActiveMQ Artemis > Issue Type: Task >Affects Versions: 2.33.0 >Reporter: Domenico Francesco Bruscino >Assignee: Domenico Francesco Bruscino >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > The lib folder includes netty-tcnative-boringssl-static artifacts non-aligned > with the netty-tcnative-version in pom.xml. Those artifacts are included > because of zookeeper-server. -- This message was sent by Atlassian Jira (v8.20.10#820010)
