Hi

I am facing a problem with SQL adapter. I have my solution running at
production and it critically needs a solution.

I am using SQL adapter to submit a batch every 15mins. In two days of
continuous execution, SQL Adapter has logged a warning twice with the
message "A connection with the transaction manager was lost". Now the
problem is that SQL adapter, though configured for retry, does not attempt
any retry, and the message de-hydrates.(for every other error, retry attempt
are made).

I further have a Try - Catch implemented over SQL adapter's send port, but
the orchestration never completes and the catch block is never executed.
Everything related to that message de-hydrates. The over all solution is not
affected and subsequent messages are passed on successfully. But the
de-hydrated messages are very crucial for the integrity of the solution.

Any Idea why "transaction manager connection losing" occurs, and why no
retry attempts are made?

Thanks in advance.

Imran Ramzan

[ Post a follow-up to this message ]