[
https://issues.apache.org/jira/browse/QPIDJMS-542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Andre Pearce updated QPIDJMS-542:
-----------------------------------------
Description:
Both in ActiveMQ OpenWire and ActiveMQ Artemis Core clients with their
respective JMS InitialContextFactory implementations it is possible to set the
connection url as the provider url directly.
This is very convenient as well some third party systems annoyingly have also
been built around that, making transition to Qpid JMS client from older
ActiveMQ Openwire or Artemis trickey and problematic where we want to migrate
fully to AMQP protocol with the brokers from all systems.
e.g.
ActiveMQ 5.x Openwire:
{code:java}
java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory
java.naming.provider.url=tcp://hostname:61616
{code}
ActiveMQ Artemis Core
{code:java}
java.naming.factory.initial=org.apache.activemq.artemis.jndi.ActiveMQInitialContextFactory
java.naming.provider.url=tcp://localhost:5445
{code}
Intent is to support the same, for qpid-jms.
e.g.
{code:java}
java.naming.factory.initial=org.apache.qpid.jms.jndi.JmsInitialContextFactory
java.naming.provider.url=amqp://localhost:5672
{code}
and
{code:java}
java.naming.factory.initial=org.apache.qpid.jms.jndi.JmsInitialContextFactory
java.naming.provider.url=failover:(amqps://host1:5672,amqps://host2:5672)
{code}
was:
Both in ActiveMQ OpenWire and ActiveMQ Artemis Core clients with their
respective JMS InitialContextFactory implementations it is possible to set the
connection url as the provider url directly.
This is very convenient as well some third party systems annoyingly have also
been built around that, making transition to Qpid JMS client from older
ActiveMQ Openwire or Artemis trickey and problematic where we want to migrate
fully to AMQP protocol with the brokers from all systems.
e.g.
ActiveMQ 5.x Openwire:
{code:java}
java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory
java.naming.provider.url=tcp://hostname:61616
{code}
ActiveMQ Artemis Core
{code:java}
java.naming.factory.initial=org.apache.activemq.artemis.jndi.ActiveMQInitialContextFactory
java.naming.provider.url=tcp://localhost:5445
{code}
Intent is to support the same
> Support setting amqp url as the provider url directly.
> ------------------------------------------------------
>
> Key: QPIDJMS-542
> URL: https://issues.apache.org/jira/browse/QPIDJMS-542
> Project: Qpid JMS
> Issue Type: Improvement
> Components: qpid-jms-client
> Affects Versions: 1.0.0
> Reporter: Michael Andre Pearce
> Priority: Major
>
> Both in ActiveMQ OpenWire and ActiveMQ Artemis Core clients with their
> respective JMS InitialContextFactory implementations it is possible to set
> the connection url as the provider url directly.
> This is very convenient as well some third party systems annoyingly have also
> been built around that, making transition to Qpid JMS client from older
> ActiveMQ Openwire or Artemis trickey and problematic where we want to migrate
> fully to AMQP protocol with the brokers from all systems.
>
>
> e.g.
> ActiveMQ 5.x Openwire:
> {code:java}
> java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory
> java.naming.provider.url=tcp://hostname:61616
> {code}
> ActiveMQ Artemis Core
> {code:java}
> java.naming.factory.initial=org.apache.activemq.artemis.jndi.ActiveMQInitialContextFactory
> java.naming.provider.url=tcp://localhost:5445
> {code}
>
>
> Intent is to support the same, for qpid-jms.
> e.g.
>
> {code:java}
> java.naming.factory.initial=org.apache.qpid.jms.jndi.JmsInitialContextFactory
> java.naming.provider.url=amqp://localhost:5672
> {code}
> and
>
> {code:java}
> java.naming.factory.initial=org.apache.qpid.jms.jndi.JmsInitialContextFactory
> java.naming.provider.url=failover:(amqps://host1:5672,amqps://host2:5672)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
