duplicate column labels (SPR-11786) improved prefix detection in StringUtils.cleanPath (SPR-11793) fixed JMS problem with Oracle AQ when underlying DataSource is decorated (SPR-11791, SPR-10829) support lazy * spring-task-3.2.xsd allows for SpEL expressions in initial-delay attribute (SPR-10102) * spring-jms-3.2.xsd allows for SpEL expressions in prefetch and receive-timeout attributes (SPR-9553) * JmsTemplate shorter than remaining transaction timeout (SPR-10109) * added MappingJackson2MessageConverter for JMS (SPR-10099) * JDBC parameter binding uses JDBC 3.0 ParameterMetaData (if available) for type determination

MBeanServerForwarder * JmsInvokerClientInterceptor/FactoryBean always uses createConnection/createSession when on JMS 1.1 * RmiClientInterceptor detects nested SocketException as connect failure as well * Servlet/P "ehcache.xml" input stream, if any * revised JMS CachedConnectionFactory to avoid unnecessary rollback calls on Session return * fixed JMS CachedConnectionFactory to fully synchronize its Session JmsResourceHolder does not ignore IllegalStateException from locally synchronized transaction * fixed JMS CachingConnectionFactory to correctly cache a producer without fixed destination as well * Defa

Connections 1.12.1 MQTT 1.13 STOMP 1.14 OpenWire 1.15 Core 1.16 Mapping JMS Concepts to the Core API 1.17 Using JMS 1.18 The Client Classpath 1.19 Examples 1.20 Routing Messages With Wild Metrics 1.49 Security 1.50 Masking Passwords 1.51 Broker Plugins 1.52 Resource Limits 1.53 The JMS Bridge 1.54 Client Reconnection and Session Reattachment 1.55 Diverting and Splitting Message Flows to match the hostname in the client's URL. This impacts all core-based clients including core JMS clients and core connections between cluster nodes. Although this is a "breaking" change, not

5 Architecture 1.6 Using the Server 1.7 Address Model 1.8 Using JMS 1.9 Using Core 1.10 Using AMQP 1.11 Mapping JMS Concepts to the Core API 1.12 The Client Classpath 1.13 Examples 1.14 Acknowledge Modes 1.35 Management 1.36 Security 1.37 Broker Plugins 1.38 Resource Limits 1.39 The JMS Bridge 1.40 Client Reconnection and Session Reattachment 1.41 Diverting and Splitting Message Flows messaging many senders can send messages to an entity on the server, often called a topic (e.g. in the JMS world). There can be many subscriptions on a topic, a subscription is just another word for a consumer

Project Info 5. Messaging Concepts 6. Architecture 7. Using the Server 8. Using JMS 9. Using Core 10. Mapping JMS Concepts to the Core API 11. The Client Classpath 12. Examples 13. Routing Messages Grouping 31. Extra Acknowledge Modes 32. Management 33. Security 34. Resource Limits 35. The JMS Bridge 36. Client Reconnection and Session Reattachment 37. Diverting and Splitting Message Flows messaging many senders can send messages to an entity on the server, often called a topic (e.g. in the JMS world). There can be many subscriptions on a topic, a subscription is just another word for a consumer

heart-beating and connection-ttl ..... 22 7.6. Selector/Filter expressions ..... 24 7.7. STOMP and JMS interoperability ..... 24 7.8. Durable Subscriptions ..... 25 7.9. Handling of Large Messages with Listeners and SessionFailure Listeners ..... 45 12. Mapping JMS Concepts to the Core API ..... 46 12.1. JMS Topic 46 12.2. JMS Queue 46 13. Using JMS or Jakarta Messaging 47 13.1. A simple ordering system system 47 13.2. JNDI 47 13.3. Directly instantiating JMS Resources without using JNDI 52 13.4. Setting The Client ID 53 13.5. Setting The Batch Size for DUPS_OK 54 13.6. Setting The Transaction

5 Architecture 1.6 Using the Server 1.7 Address Model 1.8 Using JMS 1.9 Using Core 1.10 Using AMQP 1.11 Mapping JMS Concepts to the Core API 1.12 The Client Classpath 1.13 Examples 1.14 Acknowledge Modes 1.35 Management 1.36 Security 1.37 Broker Plugins 1.38 Resource Limits 1.39 The JMS Bridge 1.40 Client Reconnection and Session Reattachment 1.41 Diverting and Splitting Message Flows messaging many senders can send messages to an entity on the server, often called a topic (e.g. in the JMS world). There can be many subscriptions on a topic, a subscription is just another word for a consumer

5 Architecture 1.6 Using the Server 1.7 Address Model 1.8 Using JMS 1.9 Using Core 1.10 Using AMQP 1.11 Mapping JMS Concepts to the Core API 1.12 The Client Classpath 1.13 Examples 1.14 Console 1.38 Security 1.39 Masking Passwords 1.40 Broker Plugins 1.41 Resource Limits 1.42 The JMS Bridge 1.43 Client Reconnection and Session Reattachment 1.44 Diverting and Splitting Message Flows messaging many senders can send messages to an entity on the server, often called a topic (e.g. in the JMS world). There can be many subscriptions on a topic, a subscription is just another word for a consumer

11 AMQP 1.12 MQTT 1.13 STOMP 1.14 OpenWire 1.15 Core 1.16 Mapping JMS Concepts to the Core API 1.17 Using JMS 1.18 The Client Classpath 1.19 Examples 1.20 Routing Messages With Wild Metrics 1.48 Security 1.49 Masking Passwords 1.50 Broker Plugins 1.51 Resource Limits 1.52 The JMS Bridge 1.53 Client Reconnection and Session Reattachment 1.54 Diverting and Splitting Message Flows to be compatible with HornetQ and/or Artemis 1.x clients needs to have anycastPrefix=jms.queue.;multicastPrefix=jms.topic. in the acceptor url. This prefix used to be configured automatically behind the

5 Architecture 1.6 Using the Server 1.7 Address Model 1.8 Using JMS 1.9 Using Core 1.10 Using AMQP 1.11 Mapping JMS Concepts to the Core API 1.12 The Client Classpath 1.13 Examples 1.14 1.37 Management Console 1.38 Security 1.39 Broker Plugins 1.40 Resource Limits 1.41 The JMS Bridge 1.42 Client Reconnection and Session Reattachment 1.43 Diverting and Splitting Message Flows messaging many senders can send messages to an entity on the server, often called a topic (e.g. in the JMS world). There can be many subscriptions on a topic, a subscription is just another word for a consumer