TOraAlerter Blocking Register Call Question
Posted: Thu 26 Feb 2009 14:10
hi there
i have question regarding how to handle the following scenario with oracle alerts. suppose there are two clients each interested in the same alert-type, both using the oraalerter component. client A has started a transaction in which a message of the alert-type has been signaled. however, before committing its transaction client a has encountered an unhandled error of some sort, hence no commit or rollback will be issued.
in this case, when client B tries to register the signaled alert-type, it is blocked until client A will finally commit or rollback. however, who knows when that will ever happen (well, except for windows patch day
).
my question is, what is the suggested way of handling that situation. i would like the application to continue, but without using alerting (maybe notifying the user in some way). my first was thought was to start the alerter in a thread using a WaitForSingleObject on the thread-handle, but since the alerter itself is nonblocking i wondered if this will cause more trouble than it solves...
what is the best strategy here?
i have question regarding how to handle the following scenario with oracle alerts. suppose there are two clients each interested in the same alert-type, both using the oraalerter component. client A has started a transaction in which a message of the alert-type has been signaled. however, before committing its transaction client a has encountered an unhandled error of some sort, hence no commit or rollback will be issued.
in this case, when client B tries to register the signaled alert-type, it is blocked until client A will finally commit or rollback. however, who knows when that will ever happen (well, except for windows patch day
my question is, what is the suggested way of handling that situation. i would like the application to continue, but without using alerting (maybe notifying the user in some way). my first was thought was to start the alerter in a thread using a WaitForSingleObject on the thread-handle, but since the alerter itself is nonblocking i wondered if this will cause more trouble than it solves...
what is the best strategy here?