Hello everybody, I'm receiving a JDBC commit error while trying

Jin Pheh

Certified Associate Developer

over 9 years ago

Hello everybody,

I'm receiving a JDBC commit error while trying to execute a query rule within a SAIL interface. The interface works within the interface editor and the query rule works when tested both in a stand alone expression and the SAIL interface however when loading the form via /suite/tempo I am receiving a "JDBC Commit Failed - Caused by: java.sql.SQLException: Commit can not be set while enrolled in a transaction" error message.
Note that there are no bind variables and the form loads when clicking on an action - there are no database writes taking place.

The issue appears similar to this other issue though no resolution was posted there
forum.appian.com/.../e-199542

Has anyone experienced this before?

Discussion posts and replies are publicly visible

0 Eduardo Fuentes
Appian Employee
over 9 years ago

Are you sure the issue is happening when invoking the query rule? I've seen this before and is usually a red herring when receiving attachments via email or uploading files.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Eliot Gerson
Appian Employee
over 9 years ago

Hi Jin, what version of Appian are you using?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Jin Pheh
Certified Associate Developer
over 9 years ago

Hey Eduardo, Interesting - is there any way to track down the root cause of the problem? In my case I did have a document upload on the same form however commenting it out did not resolve the error. (and no email attachments to speak of)

Eliot: We're on 16.1 though I'm not sure which hotfix. Speaking of which, aside from contacting support is there a way to determine what hotfix level a cloud instance is running on?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Eduardo Fuentes
Appian Employee
over 9 years ago

Based on the symptoms it seems this is indeed an issue. You can create a support case to apply the fix to your site.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Evan Rust over 9 years ago

Hello, was there a resolution to this issue? I'm experiencing exactly the same thing.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Jin Pheh
Certified Associate Developer
over 9 years ago

In my case it was resolved by deploying the most recent 16.1 hotfix. Unfortunately there was nothing else I tried that worked.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Eliot Gerson
Appian Employee
over 9 years ago

The next Hotfix package will include a fix for this issue and will be released on Forum next week. For cloud environments, please create a Support Case to arrange for this hotfix to be applied.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel