In your original post, you state that 'sometimes the connection to the database is getting closed' ...leading to the error. So does that mean that the Database element works just fine some of the time?
If so, I recommend you catch the java event *.* and try executing the DB element one more time (don't allow an infinite loop). As it may work the 2nd time you try it. That was the old workaround for such an issue as what you're seeing.
Do you know how to do this?
1.You use the Database element's Events tab press [Add] to add an event handler (this creates a new exit state) called NewEvent1
1a.In the events tab, at the top, select the NewEvent1. At the bottom of that tab, configure Name: JavaExc and EventList: *.* (star dot star to catch all java events)
1b. Now in the workspace, connect this new exit state JavaExc to a Decision element.
1c. Click: Use DecisionEditor - and select the IF statement in the Expression box.
1d. At the bottom of the DecisionEditor, configure it to check: if Caller Activity > Number of Times an Element has been visited > Element: Decision01 (or whatever the name of this current Decision element is) Operation: < (less than) 2ndArg: Constant Number 2
Then go to the upper right corner of that box (column named return) and enter: retry
Halfway down in that window, where it says Otherwise, enter: maxtries
Press OK to exit the Decision Editor
1e. Now connect the Decision01 element exit state named retry back to your Database element
And connect exit state: maxtries to tell the caller there's a problem and then return the caller to ICM.
If this works, let me know because then you need to connect the Database-JavaExc to an element that logs need to also log the {Data.Session.lastException.exception} to the Activity Log before executing the Decision01 element. Because catching events suppresses the error log from displaying the cause of the error.
