AMQ Clients 1.2 Release Notes
Release Notes for Red Hat JBoss AMQ Clients
Chapter 1. Features
- AMQ C++ now offers automatic reconnect with connection failover.
- AMQ C++ now supports multithreaded operation on Red Hat Enterprise Linux.
- AMQ C++, AMQ JMS, and AMQ Python now support Kerberos authentication.
Chapter 2. Enhancements
2.1. AMQ C++
ENTMQCL-420 - Improve the API for handling map data
The API for map-structured data now provides methods to convert to standard C++ data structures as well as to raw
ENTMQCL-516 - Expose connection driver "tick"
connection_driverinterface now includes a method to trigger additional IO and event processing. This is useful for custom IO integrations.
ENTMQCL-527 - Improve the API for scheduling work
This release introduces the
workinterfaces. They enable you to define routines that can be injected into the event-processing stream across thread boundaries or scheduled for later execution.
- AMQ C++ is now based on Qpid Proton 0.18.0
2.3. AMQ JMS
ENTMQCL-543 - Add ability to reject messages in
You can now set the message-acknowledgment policy for redelivered messages using the
jms.redeliveryPolicy.outcomeconnection URI option.
Add support for the Netty epoll transport
If the OS supports it, the client now uses the epoll IO interface for improved performance.
- AMQ JMS is now based on Qpid JMS 0.26.0
2.4. AMQ Python
- AMQ Python is now based on Qpid Proton 0.18.0
Chapter 3. Resolved Issues
ENTMQCL-485 - Filter module unavailable in the browser
In earlier releases of the product, the filter module was unavailable in a browser. As a consequence, filters could not be used in browser code.
In this release, the filter module is made available from the container object and is now usable in browser code.
ENTMQCL-490 - Logging prints
[object]instead of content of object
In earlier releases of the product, the code to print object information was not showing component details of the object. As a consequence, log messages had less detail than expected.
In this release, the object printing code now prints the members representing the object and the log messages have the expected level of detail.
ENTMQCL-505 - Examples fail on Node.js 0.10
In earlier releases of the product, the example code had a dependency on an arg parsing module that is not available for Node.js 0.10. As a consequence, the examples failed to run.
In this release, the examples are rewritten to use another arg parsing module, and now the examples can run on Node.js 0.10.
ENTMQCL-532 - The browserify command ignores locally installed files
In previous releases of the product, the
browserifyscript did not include locally installed files in its path. As a result, you could not run the script without NPM (node package manager) installing all of your code.
In the this release, the current directory is now included in the Node.js path and the
browserifyscript uses code from modules in the current directory.
3.2. AMQ JMS
ENTMQCL-511 - Memory leak after remote connection close
In earlier releases of the product, various concurrent AMQP operations were triggering memory leaks. As a consequence, client memory use was growing.
In this release, the leaks are fixed and client memory use is now stable.
3.3. AMQ Python
ENTMQCL-470 - Faulty error handling when listener address is already in use
In earlier releases of the product, there was an incorrect string format in an error handler. As a consequence, the
address already in useerror message was obscured.
In this release, the string format is corrected and the error message is no longer obscured.
ENTMQCL-471 - Creating a container leaks two file descriptors
In earlier releases of the product, the client was not cleaning up all references to internal objects. As a consequence, file descriptors were not being freed after container deletion.
In this release, the client frees all of its file descriptors on container deletion.
Chapter 4. Known Issues
4.1. AMQ C++
ENTMQCL-565 - Windows build does not compile the examples that require C++11
The AMQ C++ client is supported for use on Microsoft Windows Server 2012 R2. However, compiling the examples as C++11 is not yet supported on this operating system.
ENTMQCL-584 - Kerberos authentication cannot proceed if the user option is not set
In order for Kerberos authentication to succeed, a value must be supplied to the
userconnection option. This value need not match the credential established using
4.2. AMQ Python
ENTMQCL-483 - Selectors with backslashes are invalid in non-Unicode strings
Container.create_receiver()accepts a string. If the string is not supplied as Unicode (in Python 2,
u"somestring"), any elements escaped with backslashes might not be processed correctly.
Workaround: Users of Python 2 should use an explicit Unicode string in filter declarations to avoid the problem.
ENTMQCL-546 - Transactions introduce unexpected link events
Starting a transaction internally opens a sending link for controlling the transaction. This special link can trigger extra application events.
Workaround: Code using transactions should ensure link handler functions are processing the link they expect.
4.3. AMQ .NET
ENTMQCL-500 - Receive does not raise exception when link closed with error
Pipelined protocol state events can prevent the client from raising link errors to the API user. Notification of errors might occur in subsequent event handling functions.
Chapter 5. Important Notes
5.1. Preferred Clients
In general, AMQ clients that support the AMQP 1.0 standard are preferred for new application development. However, the following exceptions apply.
- If your implementation requires distributed transactions, use the AMQ Core Protocol JMS client (the JMS implementation previously provided with HornetQ).
- If you require MQTT or STOMP in your domain (for IoT applications, for instance), use community-supported MQTT or STOMP clients.
The considerations above do not necessarily apply if you are already using:
- The AMQ OpenWire JMS client (the JMS implementation previously provided in A-MQ 6)
- The AMQ Core Protocol JMS client (the JMS implementation previously provided with HornetQ)
5.2. NMS and CMS
Deprecation of the CMS and NMS APIs
The ActiveMQ CMS and NMS messaging APIs are deprecated in AMQ 7. It is recommended that users of the CMS API migrate to AMQ C++, and users of the NMS API migrate to AMQ .NET. The CMS and NMS APIs might have reduced functionality in AMQ 7.
5.3. AMQ C++
The AMQ C++ messaging API includes classes and methods that are not yet proven and can change in future releases. Be aware that use of these interfaces might require changes to your application code in the future.
These interfaces are marked Unsettled API in the API reference. They include the interfaces in the
proton::ionamespaces and the following interfaces in the
API elements present in header files but not yet documented are considered unsettled and are subject to change.
Interfaces marked Deprecated in the API reference are scheduled for removal in a future release.
This release deprecates the following interfaces in the
void_function0- Use the
workclass or C++11 lambdas instead.
default_container- Use the
url_error- Use a third-party URL library instead.