[jira] [Comment Edited] (AMQ-9469) Removing JRMS dependency from assembly POM

2024-03-28 Thread Kartik Ganesh (Jira)


[ 
https://issues.apache.org/jira/browse/AMQ-9469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17831951#comment-17831951
 ] 

Kartik Ganesh edited comment on AMQ-9469 at 3/29/24 3:27 AM:
-

I've opened a -draft- PR for removal of the dependency here - 
[https://github.com/apache/activemq/pull/1191]


was (Author: JIRAUSER287644):
I've opened a draft PR for removal of the dependency here - 
https://github.com/apache/activemq/pull/1191

> 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
>Priority: Minor
>  Time Spent: 10m
>  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 I 
> can submit a PR to remove this. 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:
> {{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}}
>  
> 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 
> [META-INF/services/org/apache/activemq/transport|https://github.com/apache/activemq/tree/main/activemq-client/src/main/resources/META-INF/services/org/apache/activemq/transport]
>  folder under activemq-client does not have a "jrms" file.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Work logged] (ARTEMIS-4703) Add additional Queue federation example for AMQP federation

2024-03-28 Thread ASF GitHub Bot (Jira)


 [ 
https://issues.apache.org/jira/browse/ARTEMIS-4703?focusedWorklogId=912117=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-912117
 ]

ASF GitHub Bot logged work on ARTEMIS-4703:
---

Author: ASF GitHub Bot
Created on: 28/Mar/24 21:13
Start Date: 28/Mar/24 21:13
Worklog Time Spent: 10m 
  Work Description: tabish121 opened a new pull request, #8:
URL: https://github.com/apache/activemq-artemis-examples/pull/8

   Adds an example that demonstrates moving messages through an intermediary 
broker which has no consumer demand.




Issue Time Tracking
---

Worklog Id: (was: 912117)
Remaining Estimate: 0h
Time Spent: 10m

> Add additional Queue federation example for AMQP federation
> ---
>
> Key: ARTEMIS-4703
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4703
> Project: ActiveMQ Artemis
>  Issue Type: Task
>  Components: AMQP
>Affects Versions: 2.33.0
>Reporter: Timothy A. Bish
>Assignee: Timothy A. Bish
>Priority: Trivial
> Fix For: 2.34.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Add an additional Queue federation example showing how to federate queue 
> messages through an intermediary broker.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Resolved] (ARTEMIS-3262) Cannot get max-hops >= 2 federation to work

2024-03-28 Thread Timothy A. Bish (Jira)


 [ 
https://issues.apache.org/jira/browse/ARTEMIS-3262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Timothy A. Bish resolved ARTEMIS-3262.
--
Resolution: Information Provided

> Cannot get max-hops >= 2 federation to work
> ---
>
> Key: ARTEMIS-3262
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3262
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>  Components: Federation
>Affects Versions: 2.17.0, 2.20.0
> Environment: Artemis 2.17.0 on 3 Linux machines
> Dragonwell OpenJDK 11.0.10
>Reporter: Zhang Xiang
>Priority: Major
>  Labels: ActiveMQ, federation
>
> I want to construct a 3-level MQTT message forwarding system:
> A → B → C
> Once a message publish under the topic "from-A" to A, all clients subscribing 
> "from-A" on B and C should receive that message.
> Here is the config of B:
>  
> {code:xml}
> 
> tcp://192.168.1.200:61616
> 
> 
> 
> 
> true
> 
> connector-A
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> {code}
> And here is the config of C:
>  
>  
> {code:xml}
> 
> tcp://192.168.1.100:61616
> 
> 
> 
> 
> 
> connector-C
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> {code}
> The problem is that even I've set max-hops to 2, the message cannot be 
> forwarded for more than 1 time.
>  
>  * If I published a "from-A" message to B, all clients subscribing "from-A" 
> on C could receive the message.
>  * If I published a "from-A" message to A, all clients subscribing "from-A" 
> on B could receive the message, but clients on C wouldn't!
> The example config files provided by the software packages do not cover this 
> kind of situations, nor do the documentation.
> Please tell me if it is a bug and if not, what should I do.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (ARTEMIS-3262) Cannot get max-hops >= 2 federation to work

2024-03-28 Thread Timothy A. Bish (Jira)


[ 
https://issues.apache.org/jira/browse/ARTEMIS-3262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17831977#comment-17831977
 ] 

Timothy A. Bish commented on ARTEMIS-3262:
--

This is a configuration issue, the max-hops value isn't actually needed in this 
scenario as there is no loop of federated brokers that could cause cycling.  If 
you wanted to add max hops to this setup you should set the value to two on 
both brokers or set as the message is getting stopped right now from moving to 
C from B when published on A is because the configuration on C says only one 
hop is allowed and the message already hopped once from A to B. 

> Cannot get max-hops >= 2 federation to work
> ---
>
> Key: ARTEMIS-3262
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3262
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>  Components: Federation
>Affects Versions: 2.17.0, 2.20.0
> Environment: Artemis 2.17.0 on 3 Linux machines
> Dragonwell OpenJDK 11.0.10
>Reporter: Zhang Xiang
>Priority: Major
>  Labels: ActiveMQ, federation
>
> I want to construct a 3-level MQTT message forwarding system:
> A → B → C
> Once a message publish under the topic "from-A" to A, all clients subscribing 
> "from-A" on B and C should receive that message.
> Here is the config of B:
>  
> {code:xml}
> 
> tcp://192.168.1.200:61616
> 
> 
> 
> 
> true
> 
> connector-A
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> {code}
> And here is the config of C:
>  
>  
> {code:xml}
> 
> tcp://192.168.1.100:61616
> 
> 
> 
> 
> 
> connector-C
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> {code}
> The problem is that even I've set max-hops to 2, the message cannot be 
> forwarded for more than 1 time.
>  
>  * If I published a "from-A" message to B, all clients subscribing "from-A" 
> on C could receive the message.
>  * If I published a "from-A" message to A, all clients subscribing "from-A" 
> on B could receive the message, but clients on C wouldn't!
> The example config files provided by the software packages do not cover this 
> kind of situations, nor do the documentation.
> Please tell me if it is a bug and if not, what should I do.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (ARTEMIS-4703) Add additional Queue federation example for AMQP federation

2024-03-28 Thread Timothy A. Bish (Jira)


 [ 
https://issues.apache.org/jira/browse/ARTEMIS-4703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Timothy A. Bish updated ARTEMIS-4703:
-
Affects Version/s: 2.33.0
   (was: 2.34.0)

> Add additional Queue federation example for AMQP federation
> ---
>
> Key: ARTEMIS-4703
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4703
> Project: ActiveMQ Artemis
>  Issue Type: Task
>  Components: AMQP
>Affects Versions: 2.33.0
>Reporter: Timothy A. Bish
>Assignee: Timothy A. Bish
>Priority: Trivial
> Fix For: 2.33.0
>
>
> Add an additional Queue federation example showing how to federate queue 
> messages through an intermediary broker.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (ARTEMIS-4703) Add additional Queue federation example for AMQP federation

2024-03-28 Thread Timothy A. Bish (Jira)


 [ 
https://issues.apache.org/jira/browse/ARTEMIS-4703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Timothy A. Bish updated ARTEMIS-4703:
-
Fix Version/s: 2.34.0
   (was: 2.33.0)

> Add additional Queue federation example for AMQP federation
> ---
>
> Key: ARTEMIS-4703
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4703
> Project: ActiveMQ Artemis
>  Issue Type: Task
>  Components: AMQP
>Affects Versions: 2.33.0
>Reporter: Timothy A. Bish
>Assignee: Timothy A. Bish
>Priority: Trivial
> Fix For: 2.34.0
>
>
> Add an additional Queue federation example showing how to federate queue 
> messages through an intermediary broker.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Created] (ARTEMIS-4703) Add additional Queue federation example for AMQP federation

2024-03-28 Thread Timothy A. Bish (Jira)
Timothy A. Bish created ARTEMIS-4703:


 Summary: Add additional Queue federation example for AMQP 
federation
 Key: ARTEMIS-4703
 URL: https://issues.apache.org/jira/browse/ARTEMIS-4703
 Project: ActiveMQ Artemis
  Issue Type: Task
  Components: AMQP
Affects Versions: 2.34.0
Reporter: Timothy A. Bish
Assignee: Timothy A. Bish
 Fix For: 2.33.0


Add an additional Queue federation example showing how to federate queue 
messages through an intermediary broker.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (AMQ-9469) Removing JRMS dependency from assembly POM

2024-03-28 Thread Kartik Ganesh (Jira)


 [ 
https://issues.apache.org/jira/browse/AMQ-9469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kartik Ganesh updated AMQ-9469:
---
Description: 
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 I 
can submit a PR to remove this. 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:

{{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}}

 

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 
[META-INF/services/org/apache/activemq/transport|https://github.com/apache/activemq/tree/main/activemq-client/src/main/resources/META-INF/services/org/apache/activemq/transport]
 folder under activemq-client does not have a "jrms" file.

  was:
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 I 
can submit a PR to remove this. 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 

[jira] [Work logged] (AMQ-9469) Removing JRMS dependency from assembly POM

2024-03-28 Thread ASF GitHub Bot (Jira)


 [ 
https://issues.apache.org/jira/browse/AMQ-9469?focusedWorklogId=912111=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-912111
 ]

ASF GitHub Bot logged work on AMQ-9469:
---

Author: ASF GitHub Bot
Created on: 28/Mar/24 19:52
Start Date: 28/Mar/24 19:52
Worklog Time Spent: 10m 
  Work Description: kartg opened a new pull request, #1191:
URL: https://github.com/apache/activemq/pull/1191

   The jrms-1.1 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.
   
   The 
[META-INF/services/org/apache/activemq/transport](https://github.com/apache/activemq/tree/main/activemq-client/src/main/resources/META-INF/services/org/apache/activemq/transport)
 folder under `activemq-client` (tested using v5.18.3) does not have a "jrms" 
file, so "jrms://" does not resolve to a supported ActiveMQ protocol.
   
   More details in the JIRA issue - 
https://issues.apache.org/jira/browse/AMQ-9469




Issue Time Tracking
---

Worklog Id: (was: 912111)
Remaining Estimate: 0h
Time Spent: 10m

> 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
>Priority: Minor
>  Time Spent: 10m
>  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 I 
> can submit a PR to remove this. 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:
> {{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:829){}}}{{{}Caused by: 
> java.io.IOException: Transport scheme NOT recognized: [jrms]{}}}{{ at 
> org.apache.activemq.util.IOExceptionSupport.create(IOExceptionSupport.java:30)}}{{
>  at 
> 

[jira] [Commented] (AMQ-9469) Removing JRMS dependency from assembly POM

2024-03-28 Thread Kartik Ganesh (Jira)


[ 
https://issues.apache.org/jira/browse/AMQ-9469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17831951#comment-17831951
 ] 

Kartik Ganesh commented on AMQ-9469:


I've opened a draft PR for removal of the dependency here - 
https://github.com/apache/activemq/pull/1191

> 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
>Priority: Minor
>  Time Spent: 10m
>  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 I 
> can submit a PR to remove this. 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:
> {{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:829){}}}{{{}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{}}}{{{}{}}}
>  
> 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 
> [META-INF/services/org/apache/activemq/transport|https://github.com/apache/activemq/tree/main/activemq-client/src/main/resources/META-INF/services/org/apache/activemq/transport]
>  folder under activemq-client does not have a "jrms" file.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Created] (AMQ-9469) Removing JRMS dependency from assembly POM

2024-03-28 Thread Kartik Ganesh (Jira)
Kartik Ganesh created AMQ-9469:
--

 Summary: 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


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 I 
can submit a PR to remove this. 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:

{{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:829){}}}{{{}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{}}}{{{}{}}}

 

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 
[META-INF/services/org/apache/activemq/transport|https://github.com/apache/activemq/tree/main/activemq-client/src/main/resources/META-INF/services/org/apache/activemq/transport]
 folder under activemq-client does not have a "jrms" file.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Work logged] (ARTEMIS-4510) Add auto-create-destination logic to diverts

2024-03-28 Thread ASF GitHub Bot (Jira)


 [ 
https://issues.apache.org/jira/browse/ARTEMIS-4510?focusedWorklogId=912072=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-912072
 ]

ASF GitHub Bot logged work on ARTEMIS-4510:
---

Author: ASF GitHub Bot
Created on: 28/Mar/24 14:43
Start Date: 28/Mar/24 14:43
Worklog Time Spent: 10m 
  Work Description: AntonRoskvist opened a new pull request, #4867:
URL: https://github.com/apache/activemq-artemis/pull/4867

   This is the second try of #4681 after a round of feedback on the dev mailing 
list.
   @jbertram @brusdev @clebertsuconic Please let me know if you agree to these 
changes or if I should change anything else.
   
   An additional thing of note in this PR is added handling for a fringe issue 
I found while working on this PR pertaining to redistributed messages arriving 
on the divert. There is an added test for this as well. I can break this part 
out into a separate PR if preferred.




Issue Time Tracking
---

Worklog Id: (was: 912072)
Time Spent: 3h 50m  (was: 3h 40m)

> Add auto-create-destination logic to diverts
> 
>
> Key: ARTEMIS-4510
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4510
> Project: ActiveMQ Artemis
>  Issue Type: Improvement
>Reporter: Anton Roskvist
>Priority: Major
>  Time Spent: 3h 50m
>  Remaining Estimate: 0h
>
> This enables the use of dynamic routing decisions within the transformer by 
> setting the message address. It also covers for a rare problem where if any 
> of the forwarding addresses are removed during runtime, such as from 
> auto-delete, the message would get silently dropped.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)