Max transacted sessions exceeded (503) error - PubSub+ Event Broker and Camel Solace component issue
Our team is currently working on a proof of concept with Apache Camel to split a file and publish the events to a Solace queue (PubSub+ Event Broker). Unfortunately, we are experiencing a persistent issue from the consuming route where, after a few minutes of consuming messages using the Solace Camel component, we start to receive "Max transacted sessions exceeded (503)" errors. This error continues to get worse as processing continues.
Here is what we've done so far in an attempt to fix the error:
Ensured that the authenticated user is associated with a client profile that sets the maximum transacted session limit to 1000.
Set maxConcurrentConsumers to 200 and tried numerous values for concurrentConsumers. We've even gone as low as maxConcurrentConsumers = 20.
Set the Solace component query parameter, cacheLevelName, to CACHE_CONSUMER. We've also tried CACHE_CONNECTION and CACHE_NONE all of which resulted in similar behaviour. Our complete component URI is:
// Camel route for consuming events from Solace
One thing we've noticed is that, regardless of using CACHE_CONNECTION/CONSUMER, the smfclient ids continue to increase because, according to the logs, the connections to Solace are continually closed and re-opened. The consumer count, as viewed from the Solace admin dashboard, never exceed the maxConcurrentConsumers value. This seems to point to some sort of session/connection garbage collection as connections are open/closed so quickly; i.e. the session associated with the channel needs to be cleaned up by the PubSub+ Event Broker and lags behind. I don't know why this is the case.
Any suggestions on how to proceed?
Edit: we are using solace-spring-boot version 1.1.0 (which pulls in solace-jms-spring-boot-starter-4.1.0.jar / sol-jms-10.8.1.jar)