ConnectionFactory=tcp://myhost:5445 In the example above the client is using the tcp scheme for the provider URL. A client may also specify multiple comma- delimited host:port combinations in the URL (e.g naming.factory.initial=org.apache.activemq.artemis.jndi.ActiveMQInitialContextFactory java.naming.provider.url=tcp://localhost:5445?type=CF In this example it is still set to the default, below shows a naming.factory.initial=org.apache.activemq.artemis.jndi.ActiveMQInitialContextFactory java.naming.provider.url=tcp://myhost:5445 queue.queues/OrderQueue=OrderQueue It is also possible to look-up JMS destinations

ConnectionFactory=tcp://myhost:5445 In the example above the client is using the tcp scheme for the provider URL. A client may also specify multiple comma- delimited host:port combinations in the URL (e.g naming.factory.initial=org.apache.activemq.artemis.jndi.ActiveMQInitialContextFactory java.naming.provider.url=tcp://localhost:5445?type=CF In this example it is still set to the default, below shows a naming.factory.initial=org.apache.activemq.artemis.jndi.ActiveMQInitialContextFactory java.naming.provider.url=tcp://myhost:5445 queue.queues/OrderQueue=OrderQueue It is also possible to look-up JMS destinations

ConnectionFactory=tcp://myhost:5445 In the example above the client is using the tcp scheme for the provider URL. A client may also specify multiple comma- delimited host:port combinations in the URL (e.g naming.factory.initial=org.apache.activemq.artemis.jndi.ActiveMQInitialContextFactory java.naming.provider.url=tcp://localhost:5445?type=CF In this example it is still set to the default, below shows a naming.factory.initial=org.apache.activemq.artemis.jndi.ActiveMQInitialContextFactory java.naming.provider.url=tcp://myhost:5445 queue.queues/OrderQueue=OrderQueue It is also possible to look-up JMS destinations

for logging various broker events (i.e. LoggingActiveMQServerPlugin ). Option to use OpenSSL provider for Netty via the sslProvider URL parameter. Enable splitting of broker.xml into multiple files myhost:5445 Using JMS 107 In the example above the client is using the tcp scheme for the provider URL. A client may also specify multiple comma-delimited host:port combinations in the URL (e.g so: java.naming.factory.initial=org.apache.activemq.artemis.jndi.ActiveMQInitialCo java.naming.provider.url=tcp://localhost:5445?type=CF Using JMS 109

for logging various broker events (i.e. LoggingActiveMQServerPlugin ). Option to use OpenSSL provider for Netty via the sslProvider URL parameter. Enable splitting of broker.xml into multiple files myhost:5445 Using JMS 107 In the example above the client is using the tcp scheme for the provider URL. A client may also specify multiple comma-delimited host:port combinations in the URL (e.g so: java.naming.factory.initial=org.apache.activemq.artemis.jndi.ActiveMQInitialCo java.naming.provider.url=tcp://localhost:5445?type=CF Using JMS 109

for logging various broker events (i.e. LoggingActiveMQServerPlugin ). Option to use OpenSSL provider for Netty via the sslProvider URL parameter. Enable splitting of broker.xml into multiple files myhost:5445 Using JMS 108 In the example above the client is using the tcp scheme for the provider URL. A client may also specify multiple comma-delimited host:port combinations in the URL (e.g so: java.naming.factory.initial=org.apache.activemq.artemis.jndi.ActiveMQInitialCo java.naming.provider.url=tcp://localhost:5445?type=CF Using JMS 110

implementation for logging various broker events (i.e. LoggingActiveMQServerPlugin ). Option to use OpenSSL provider for Netty via the sslProvider URL parameter. Enable splitting of broker.xml into multiple files ConnectionFactory=tcp://myhost:5445 In the example above the client is using the tcp scheme for the provider URL. A client may also specify multiple comma- delimited host:port combinations in the URL (e.g naming.factory.initial=org.apache.activemq.artemis.jndi.ActiveMQInitialContextFactory java.naming.provider.url=tcp://localhost:5445?type=CF In this example it is still set to the default, below shows a

for logging various broker events (i.e. LoggingActiveMQServerPlugin ). Option to use OpenSSL provider for Netty via the sslProvider URL parameter. Enable splitting of broker.xml into multiple files ConnectionFactory=tcp://myhost:5445 In the example above the client is using the tcp scheme for the provider URL. A client may also specify multiple comma-delimited host:port combinations in the URL (e.g naming.factory.initial=org.apache.activemq.artemis.jndi.ActiveMQInitialContex tFactory java.naming.provider.url=tcp://localhost:5445?type=CF In this example it is still set to the default, below shows a

for logging various broker events (i.e. LoggingActiveMQServerPlugin ). Option to use OpenSSL provider for Netty via the sslProvider URL parameter. Enable splitting of broker.xml into multiple files myhost:5445 Using JMS 107 In the example above the client is using the tcp scheme for the provider URL. A client may also specify multiple comma-delimited host:port combinations in the URL (e.g so: java.naming.factory.initial=org.apache.activemq.artemis.jndi.ActiveMQInitialCo java.naming.provider.url=tcp://localhost:5445?type=CF Using JMS 109

for logging various broker events (i.e. LoggingActiveMQServerPlugin ). Option to use OpenSSL provider for Netty via the sslProvider URL parameter. Enable splitting of broker.xml into multiple files myhost:5445 Using JMS 107 In the example above the client is using the tcp scheme for the provider URL. A client may also specify multiple comma-delimited host:port combinations in the URL (e.g so: java.naming.factory.initial=org.apache.activemq.artemis.jndi.ActiveMQInitialCo java.naming.provider.url=tcp://localhost:5445?type=CF Using JMS 109