Release Notes for Solace PubSub+ Messaging API for JMS, Version 10.12.0
July 2021

New Features Introduced in Release 10.12

This section lists the new features in Solace PubSub+ Messaging API for JMS, Version 10.12.
NameDescriptionVersion
Publish the JCA Resource Adapter to Maven repository
The JCA Resource Adapter can now be downloaded from the Maven repository.
10.12.0

Issues Resolved in Release 10.12

This section lists the resolved issues in Solace PubSub+ Messaging API for JMS, Version 10.12.
Reference NumberDescriptionVersion
SOL-43207
Javax.jms.TemporaryQueue.delete() needs to be optimized to improve performance when called repeatedly over many threads.
10.12.0
SOL-44343
Messages received by the API should be read-only but this is not the case for messages received over a shared subscription.
10.12.0
SOL-44822
Zero length BytesMessages that are received from REST publishers are mistakenly being converted into generic JMS messages(javax.jms.Message).
10.12.0
SOL-46144
Apache commons logging has been upgraded from 1.1.3 to 1.2.
10.12.0
SOL-48422
If the API receives a corrupted message such that the decoded length of the binary metadata portion greatly exceeds the length of the byte buffer, the API may not reconnect to the broker as it is supposed to.
10.12.0

Changed Functionality in Release 10.12

This section lists the changed functionality in Solace PubSub+ Messaging API for JMS, Version 10.12.
None

Known Issues in Release 10.12

This section describes known issues in Solace PubSub+ Messaging API for JMS, Version 10.12.
Reference NumberDescription
SOL-52253
The Java/JMS API can deadlock when the internal reactor thread is blocked on trying to send an message.
As an example, this can occur when the TCP socket's send buffer is full, and the application attempts to unbind from an endpoint.
For more details refer to the Release Notes page for the Solace JMS Open API.

Supported Environments