Posted: Mon Jul 28, 2014 11:42 am Post subject: Database input node Failure terminal issue
Apprentice
Joined: 14 Apr 2006 Posts: 37
Hi,
I am seeing weird behavior in Database input node. See below details.
Requirement:
1) Using Database input node to get the record if any new event arrives in database table.
2) Should send response message for any database connectivity/failure issues when database is not available after retry few times based on retry mechanism property in database input node.
Message Broker Version and tool kit version: 8.0.0.2
Current settings at database input node: Currently I am not setting any retry mechanism at Database input node level and using default retry property which is 'Failure'. I should get failure through Database input node failure terminal if database is not available.
Issue: I stopped database to make it fail at database input node. But I am not getting any failure at Database input node failure terminal.
Not getting any failure when I use below either RESIGNAL statement OR default database procedure HandleDatabaseError.
Could someone let me know why is it is not working as expected?
ESQL Code:
With RESIGNAL
RESIGNAL; /* pass the error back to the node */
/* To choose to handle Database errors yourself, delete the RESIGNAL statement above
* and uncomment the following procedure call */
--CALL HandleDatabaseError('ReadEvents');
With Database handler error:
--RESIGNAL; /* pass the error back to the node */
/* To choose to handle Database errors yourself, delete the RESIGNAL statement above
* and uncomment the following procedure call */
CALL HandleDatabaseError('ReadEvents');
We are getting failure through database input node failure terminal in Production when database is restarting on weekly maintenance.
I am trying to reproduce same error in development environment but I am not getting any failure through failure terminal. It is behaving different way in both environments. It’s weird.
Is there any way to get failure through failure terminal when database is not available?
Requirement:
Our database will be up in less than 5 minutes when it is restarting in weekly maintenance.
If I got failure through failure terminal then I can use Retry mechanism property and use Retry interval more than 5 minutes in Database input node level to avoid these kind of issues.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum