JMS Transaction COMMIT error

General Discussions
1

Hi Team,

I have seen this error in logs. Can someone explains me when this error occurs and what happens to messages?

javax.jms.JMSException: Error committing - internal error (Operation COMMIT disallowed in state COMMITTING.)
Caused by: com.solacesystems.jcsmp.InvalidOperationException: Operation COMMIT disallowed in state COMMITTING.

2

Hi @SasikumarSP,

Hmm. I haven’t seen this one before. Can you share your code?
Also can you verify that your client-profile has the allow-transacted-sessions property enabled? (It is disabled by default). Info on this docs page might also give you a hint. JMS API

3

Hey @SasikumarSP,

I got some info from our support team that should help you troubleshoot. It seems like your app is likely calling commit from multiple threads. Hopefully that will help!

The issue here is that the application is calling javax.jms.Session.commit() when an outstanding commit is already in progress. Because commit() is a blocking function that only returns after the commit operation is completed, this indicates that there must be multiple threads calling commit().

Do note that JMS sessions do not support concurrent use. This is defined in section “2.8 Multithreading” of the JMS 1.1 specification.

4

Hi @marc , @SasikumarSP any work around to avoid this error? Is there explicit way to commit the messages?

5

Hey @vshivk99,
Yes, you would commit by invoking commit() in the JMS API.
Using transacted sessions is explained in the Solace docs here: JMS API

Hope that helps :slight_smile:

6

Thanks for the response