Show Table of Contents
Chapter 5. Enhancements
5.1. Messaging - 6.3.0
Table 5.1, “Messaging Enhancements in 6.3.0” lists the enhancements in version 6.3.0.
Table 5.1. Messaging Enhancements in 6.3.0
| Enhancement | Description |
|---|---|
| ENTESB-3176 | Set OriginalDestination AMQ message property before sending it to DLQ |
| ENTESB-4135 | Update to the JMS 2.0 API |
| ENTMQ-1432 | [A-MQ,kahadb] add configuration so broker will not start if storeUsage limit is not available on the disk |
| ENTMQ-1498 | Work with JMS 2.0 osgi dependency |
| ENTMQ-1525 | [A-MQ, RuntimeConfigurationBroker] allowing policy that applies to multiple destination to be updated. |
| ENTMQ-1528 | JDBC Concurrency |
| ENTMQ-1628 | Stand-alone A-MQ has DBCP2, whilst OSGi version has DBCP1.4 |
| ENTMQ-1836 | Temporary store index/log files splitting |
| ENTMQ-1885 | configurable hostname for published address strategy |
| AMQ-5289 | Track forwards across a network in destination statistics |
| AMQ-5578 | preallocate journal files |
| AMQ-5603 | Consider preallocation of journal files in batch increments |
| AMQ-5621 | Unit tests cleanup |
| AMQ-5636 | Upgrade the bundled DBCP component. The current one is very old and buggy. |
| AMQ-5845 | AMQP: Include broker version information in the Connection properties |
| AMQ-6001 | AMQP: Refill sender credit faster to avoid throttling fast producers |
| AMQ-6015 | AMQP: Report more meaningful error conditions when an incoming send fails |
| AMQ-6077 | Better configuration of restricted classes for clients |
| AMQ-6100 | Virtual topic message destination should be the target queue |
| AMQ-6116 | Improve security context authorization cache |
| AMQ-6126 | The corePoolSize value of the TaskRunnerFactory created Executor should be configurable |
| AMQ-6147 | AMQP: Update Proton-J to 0.12.1 |
| AMQ-6149 | Pre-configure jolokia |
| AMQ-6164 | queue sendLock prevents concurrent journal updates |
| AMQ-6167 | examples/other/perfharness misses readme and uses broken link. |
| AMQ-6184 | Improve nio transport scalability |
| AMQ-6203 | KahaDB: Allow rewrite of message acks in older logs which prevent cleanup |
| AMQ-6228 | Max Frame Size Error exception shows incorrect values at times |
| AMQ-6239 | Performance issue in PrioritizedPendingListIterator |
| AMQ-6259 | Enable configuration for mqtt-over-ws transport |
| AMQ-6276 | Remove fileserver webapp |
| AMQ-6277 | KahaDB does journal recovery for last append in error in normal restart case |
| AMQ-6278 | Revisit the log level in LeaseDatabaseLocker |
| AMQ-6292 | ACK rewrite task does unnecessary syncs |
| AMQ-6304 | Container-id field blank on sending an AMQP 1.0 open frame to the client |
| AMQ-6336 | QueueBrowser delivers expired messages |
| AMQ-6403 | Allow splitting the temporary message store |
| CAMEL-8522 | Set OriginalDestination AMQ message property before sending it to DLQ |
| AMQ-3519 | Allow getJMSRedelivered flag to survive a restart |
| AMQ-5847 | AMQP: Support transactions that span multiple session for a single TXN |
| AMQ-6037 | AMQP: Add support for sending scheduled message using message annotations |
| AMQ-6362 | Add an option to time out connection attempts when blocked in ensureConnectionInfoSent |
| ENTMQ-1659 | Consider preallocation of journal files in batch increments |
| AMQ-5962 | Update HTTP Client and Core versions |
| AMQ-5980 | Update to the latest Jetty version |
| AMQ-6084 | Have an option to error out if a limit is exceeded |
| AMQ-5957 | Update outdated dependencies used by broker. |
| AMQ-6044 | AMQP: Add support for testing transactions with the test client. |
| AMQ-6093 | Remove deprecated getXURL methods from the BrokerServiceMBean |
| AMQ-6107 | AMQP: Remove deprecated prefetch size configuration option from the transport |
| AMQ-6178 | AMQP: Update Qpid JMS to 0.9.0 |
| AMQ-6181 | Upgrade to Joda-time 2.9 |
| AMQ-6309 | AMQP: Static code analysis of activemq-amqp |
| ENTESB-5636 | 3rd party alignments - built from source strict alignments |
| ENTMQ-1565 | The Readme File For The Stomp Extras Example Needs More Details |

Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.