We have a 6.5.2 IS and broker running on windows server. We have a trigger that runs concurrently at 20 threads. The issue we are facing is that for some reason we are having hung threads of the subscriber service and ultimately if all the 20 threads get hung, the documents are getting stacked up in the broker queue.
The only we are able to get rid of this by restarting our IS as we dont have a way of killing those subscriber service hung threads alone.
The subscriber it self is in a Main,Try, Catch pattern so any exception should be handled gracefully. At this point I believe it happening because we are not getting any response from a customer webservice(not even a time out and hence the service is just waiting). However i do not have any concrete proof for that.
Is there any way we can set up a timeout on the subscriber service invoked by the trigger so that if the service doesnt completes in a set time, it will close off with out resulting in a hung thread.