Release 2.0.2

Minor patch to resolve an issue in the Solace Publisher Service when the session somehow was shutdown and messages continued to flow in, the message publisher would throw an illegal state error. Error handling now reinitializes the session and message producer objects.

Release 2.0.1

Update spring boot parent version to resolve security vulnerability in snakeyaml.

Release 2.0.0

Updated spring framework dependencies to latest version to resolve security vulnerabilities.
Removed support for AWS S3.
Requires minimum Java 17 runtime.

Release 1.4.0

Updated AWS S3 library version to latest (1.12.262) due to security vulnerability. Deprecating this feature as well. Recommend using Solace's cloud integration pattern using REST delivery points.

Updated to latest Spring and Solace libraries.

Release 1.3.0

Update library dependencies to latest versions in order to address the Log4J vulnerability issue.

Modified the SolacePublishingService to leverage the new Solace Java API vs the Solace JCSMP API.

Configuration file change in the property name for the consumer destination. Change the property name from solace.jms.consumer.queue-name.0 to solace.jms.consumer.destination-name.0. This was for a request to support connecting to either queues or topics. Used the generic term destination similarly used in the JMS API. This is the only change the configuration files needed to work with this version.

Pull just the 1.3.0.jar file and replace in your directory if you have an existing deployment. Otherwise pull the .tar.gz file for everything including the configuration template files.

Refer to the README file for additional instructions on setup/configuration.

Release 1.2.0

Update Publishing Service to publish message headers back to Solace as the original object and not as casted String.

Release 1.1.5

Modified the Solace Publishing Service to continue to try to reconnect "forever" upon a connection failure. Previously it only attempted to reconnect the default 3 times.

Release 1.1.4

Change to logging configuration to only keep 1 hour of archived log data as default in attempt to reduce disk usage.

Release 1.1.3

Added profile name to system log file.  This allows distinct logs when running multiple instances at the same time. The spring active profile is now passed as a JVM parameter vs app param. Please refer to the README for specific instructions.
Updated run command to pass in active profile via JVM paramter.  This resolves issue of "spring.profiles.active_IS_UNDEFINED" in log file name upon initiation.
Turned off tomcat by default.  Resolved issue when attempting to run multiple instances on the same compute node.

R1.1.2

Fixed minor issue with NullOpService expecting a password field.