the fundamental design. Several improvements are planned in the Spring 1.1 time frame, which will preserve backward compatibility. These include: • Performance improvements: The creation of AOP proxies is sets up an actual Timer and schedules the tasks it has references to. You can specify whether or not daemon threads should be used. 5 true true JMX Support Spring Framework Version

the fundamental design. Several improvements are planned in the Spring 1.1 time frame, which will preserve backward compatibility. These include: • Performance improvements: The creation of AOP proxies is sets up an actual Timer and schedules the tasks it has references to. You can specify whether or not daemon threads should be used. 5 true true JMX Support Spring Framework Version

after separator, i.e. to accept path "/test/" for pattern "/test/*" * WeakReferenceMonitor uses a daemon thread, to avoid a hanging thread even if weak references have not been released * refined StopWatch and does nothing in this case * (many new convenience classes and methods) * (too many minor improvements to list) * (lots of minor bugfixes)

the fundamental design. Several improvements are planned in the Spring 1.1 time frame, which will preserve backward compatibility. These include: • Performance improvements: The creation of AOP proxies is value="service:jmx:iiop://localhost:9875"/> sets up an actual Timer and schedules the tasks it has references to. You can specify whether or not daemon threads should be used.

STOMP clients connecting over WebSockets via ARTEMIS-3509. • Lots of internal "code gardening" improvements for developers to make the code-base simpler and more consistent. 15.3. 2.35.0 Full release 1. Highlights • Extensive resiliency tests and hardening on Mirroring. • Paging performance improvements on sync. • Statistics about security events. • Replication status metrics. 15.4.2. Upgrading bootstrap.xml to detect and automatically reload whe SSL stores change on disk • Performance improvements on mirroring and paging • Logging metrics to mitigate the risk of missing WARN or ERROR messages

STOMP clients connecting over WebSockets via ARTEMIS-3509. • Lots of internal "code gardening" improvements for developers to make the code-base simpler and more consistent. 15.2. 2.35.0 Full release 1. Highlights • Extensive resiliency tests and hardening on Mirroring. • Paging performance improvements on sync. • Statistics about security events. • Replication status metrics. 15.3.2. Upgrading bootstrap.xml to detect and automatically reload whe SSL stores change on disk • Performance improvements on mirroring and paging • Logging metrics to mitigate the risk of missing WARN or ERROR messages

1. Highlights • Extensive resiliency tests and hardening on Mirroring. • Paging performance improvements on sync. • Statistics about security events. • Replication status metrics. 15.2.2. Upgrading bootstrap.xml to detect and automatically reload whe SSL stores change on disk • Performance improvements on mirroring and paging • Logging metrics to mitigate the risk of missing WARN or ERROR messages Core Messages can now be sent on their native format without conversions • Mirror bug fixes and improvements • ActiveMQ Artemis has now adopted more inclusive language definitions. • The examples are now

1. Highlights • Extensive resiliency tests and hardening on Mirroring. • Paging performance improvements on sync. • Statistics about security events. • Replication status metrics. 15.1.2. Upgrading bootstrap.xml to detect and automatically reload whe SSL stores change on disk • Performance improvements on mirroring and paging • Logging metrics to mitigate the risk of missing WARN or ERROR messages Core Messages can now be sent on their native format without conversions • Mirror bug fixes and improvements • ActiveMQ Artemis has now adopted more inclusive language definitions. • The examples are now

into Spock. It is recommended that you use Spock 1.1 or later to benefit from a number of recent improvements to Spock’s Spring Framework and Spring Boot integration. Please refer to the documentation for "mem": 986624, "mem.free": 933858, "processors": 8, "threads": 15, "threads.daemon": 11, "threads.peak": 15, "threads.totalStarted": 42, "uptime": 494836, "instance KB (heap, heap.committed, heap.init, heap.used) Thread information (threads, thread.peak, thread.daemon) Class load information (classes, classes.loaded, classes.unloaded) Garbage collection information

after separator, i.e. to accept path "/test/" for pattern "/test/*" * WeakReferenceMonitor uses a daemon thread, to avoid a hanging thread even if weak references have not been released * refined StopWatch and does nothing in this case * (many new convenience classes and methods) * (too many minor improvements to list) * (lots of minor bugfixes)