Release Notes for Solace PubSub+ Messaging API for Java, Version 1.0.0
September 2021

New Features Introduced in Release 1.0

This section lists the new features in Solace PubSub+ Messaging API for Java, Version 1.0.
NameDescriptionVersion
New, Modern Java Client API
This is the initial release of the PubSub+ Messaging API for Java. Solace created this API to modernize our JCSMP API. This is a separate standalone API which provides modern interfaces, patterns and usability in a native Java environment.
This version contains a feature set that allows for the common messaging patterns like publish/subscribe using Direct Messaging and Guaranteed Messaging. This API provides support for all deployments of PubSub+ across software, appliance, and cloud.
Future versions of the Java API will introduce more features as Solace builds out the roadmap for this API.
The Java API 1.0.0 supports:
* Connection management to PubSub+ event brokers
* Addition and removal of topic subscriptions
* Sending and receiving Direct and Guaranteed Messages
* Message compression
* Use of Selectors
* Kerberos authentication
* Message Replay
* Structured data types that allow interoperability between various architectures and programming languages
The Java API 1.0.0 does not support the following features:
* Request/Reply message exchange pattern
* PubSub+ Cache Client API support
* Session Transactions
* XA Transactions
* Queue browsing
1.0.0
New Java API - Replay From Message ID
Applications can now replay messages following the message-ID of the last message which they successfully-processed.
The feature uses "replication group message ID" which uniquely identifies messages within an HA group and Replication/DR group of brokers. The broker includes this ID in all guaranteed messages it delivers to the consumer. Consuming applications can extract and save this ID along with the message payload, and then use it later to initiate a replay.
This is a more "fine-grained" way to start a replay than from date-and-time, and is ideal in cases where the last message-ID successfully processed is known by the application (e.g. recovery from a database crash).
To initiate replay after message-ID from an application, both the PubSub+ Event Broker and must be upgraded.
Broker:
* PubSub+ Event Broker version 9.9.0
1.0.0

Issues Resolved in Release 1.0

This section lists the resolved issues in Solace PubSub+ Messaging API for Java, Version 1.0.
None

Changed Functionality in Release 1.0

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

Known Issues in Release 1.0

This section describes known issues in Solace PubSub+ Messaging API for Java, Version 1.0.
Reference NumberDescription
SOL-54746
The stat PERSISTENT_ACKNOWLEDGE_SENT is not accurate when using multiple receivers in a single service.
For more details refer to the Release Notes page for the individual Solace Messaging APIs.

Supported Environments