Idea Details

SQL Closed Connection error handling

Last activity 12-17-2016 10:52 AM
William Patton's profile image
03-03-2015 02:47 PM

We would like the product to be able to move a task to a failed status when the tasks receives a connection closed error from the database when processing tasks.

 

Sometimes when tasks get a connection closed error from the database, the tasks stay in progress in task persistence waiting for an update from the database that never comes.

We would like to enhance the products ability to handle situations where a task that is being submitted to task persistence is waiting of a DB connection or has an active DB connection and that connection receives a connection closed message, we would like that task to error out.

 

We would also like that function to be an option that we can turn on or off, This option should be configurable within the miscellaneous heading in the advanced settings of an IME and be set to false by default.


Comments

04-01-2016 02:47 PM

Hi Bill,

I think this is great description. Thanks for the clarification.

03-31-2016 01:50 PM

I edited the original post, do you need more?

03-18-2016 12:13 PM

Hi Bill  - Can you provide more specifics here?   I am aware of task not being able to reach a final state and there are a number of causes for this ( DB issues, JMS Issues, task persistence component issues).  It just isn't clear if this a database connection closed error is expected or benign, or what?