queue. The messaging system delivers each message to one and only one of the ordering processing components. Different messages can be processed by different order processors, but a single order is only 135 Client Reconnection and Session Reattachment Client reconnection is also used internally by components such as core bridges to allow them to reconnect to their target servers. Please see the section store the "entries" defined for your JMS components within broker.xml in an internal concurrent hash map. The EmbeddedJMS.lookup() method returns components stored in this map. If you want to use JNDI

queue. The messaging system delivers each message to one and only one of the ordering processing components. Different messages can be processed by different order processors, but a single order is only happens during failover onto a backup server. Client reconnection is also used internally by components such as core bridges to allow them to reconnect to their target servers. Please see the section store the "entries" defined for your JMS components within broker.xml in an internal concurrent hash map. The EmbeddedJMS.lookup() method returns components stored in this map. If you want to use

queue. The messaging system delivers each message to one and only one of the ordering processing components. Different messages can be processed by different order processors, but a single order is only happens during failover onto a backup server. Client reconnection is also used internally by components such as core bridges to allow them to reconnect to their target servers. Please see the section store the "entries" defined for your JMS components within broker.xml in an internal concurrent hash map. The EmbeddedJMS.lookup() method returns components stored in this map. If you want to use

queue. The messaging system delivers each message to one and only one of the ordering processing components. Different messages can be processed by different order processors, but a single order is only happens during failover onto a backup server. Client reconnection is also used internally by components such as core bridges to allow them to reconnect to their target servers. Please see the section store the "entries" defined for your JMS components within broker.xml in an internal concurrent hash map. The EmbeddedJMS.lookup() method returns components stored in this map. If you want to use

queue. The messaging system delivers each message to one and only one of the ordering processing components. Different messages can be processed by different order processors, but a single order is only happens during failover onto a backup server. Client reconnection is also used internally by components such as core bridges to allow them to reconnect to their target servers. Please see the section store the "entries" defined for your JMS components within broker.xml in an internal concurrent hash map. The EmbeddedJMS.lookup() method returns components stored in this map. If you want to use JNDI

queue. The messaging system delivers each message to one and only one of the ordering processing components. Different messages can be processed by different order processors, but a single order is only happens during failover onto a backup server. Client reconnection is also used internally by components such as core bridges to allow them to reconnect to their target servers. Please see the section store the "entries" defined for your JMS components within broker.xml in an internal concurrent hash map. The EmbeddedJMS.lookup() method returns components stored in this map. If you want to use

queue. The messaging system delivers each message to one and only one of the ordering processing components. Different messages can be processed by different order processors, but a single order is only happens during failover onto a backup server. Client reconnection is also used internally by components such as core bridges to allow them to reconnect to their target servers. Please see the section store the "entries" defined for your JMS components within broker.xml in an internal concurrent hash map. The EmbeddedJMS.lookup() method returns components stored in this map. If you want to use

queue. The messaging system delivers each message to one and only one of the ordering processing components. Different messages can be processed by different order processors, but a single order is only 134 Client Reconnection and Session Reattachment Client reconnection is also used internally by components such as core bridges to allow them to reconnect to their target servers. Please see the section lookup() method returns components stored in this map. If you want to use JNDI, call the EmbeddedJMS.setContext() method with the root JNDI context you want your components bound into. See the javadocs

queue. The messaging system delivers each message to one and only one of the ordering processing components. Different messages can be processed by different order processors, but a single order is only 125 Client Reconnection and Session Reattachment Client reconnection is also used internally by components such as core bridges to allow them to reconnect to their target servers. Please see the section lookup() method returns components stored in this map. If you want to use JNDI, call the EmbeddedJMS.setContext() method with the root JNDI context you want your components bound into. See the javadocs

Apache ActiveMQ Artemis project page: https://activemq.apache.org/components/artemis/. Software download: https://activemq.apache.org/components/artemis/download/ Git repository: https://github.com/apache/activemq-artemis queue. The messaging system delivers each message to one and only one of the ordering processing components. Different messages can be processed by different order processors, but a single order is only Warning:These repackaged jars include all the client's dependencies. Be careful with mixing other components jars in your application as they may clash with each other. JMS 105 Artemis JMS Client Dependencies