We are having some issues with our Universal Messaging 10.3.
We created some services with Software AG Designer 10.3 that invoke the “Publish” method that publishes some documents that are sent to Universal Messaging to process it to another service.
But, for some reason, something happen that makes these published documents can’t be processed by our Universal Messaging. It stucks on “outstanding” when we check the service using the UniversalMessaging Enterprise Viewer .
The only solution that “fix” this is clicking on service and then clicking on “Purge all Events”. This causes future events to be processed correctly.
But, does exists another way to solve this type of problem instead of purging all events?
Another question is: Does exists a way to warn via email if one of our services got stuck events?
Normally if events are held in Outstanding it means they have not been subscribed to, I would suggest restarting the trigger to see what happens as it sounds like something strange with the consumer not being connected. You can also in Enterprise Manager go to the durable and click on the connections to see if something is connected to it.
Let me know if that is fruitful else we may need to raise a support ticket so we can help refine the issue.
WRT the other question I would suggest raising that in the Integration Server Forum
Thank you so much for your reply. It was very fruitful! I would like to provide more information as you requested.
First, I would like to ask: How can I restart a trigger? In Software AG Designer 10.3 I didn’t find any option to restart one of the triggers that have outstanding events. The “Screenshot_4.png” attachment shows my current trigger settings. It seems correct, right?
As you suggested, I checked the “Connections” tab on Universal Messaging Enterprise Manager and the “Screenshot_3.png” attached file shows what result I got.
On “Screenshot_2.png” you can see what I got when I clicked on a connection from “Connections” tab connections list.
It would be great if you could find where the connection comes from - IS trigger, client application, etc. and reset it from there. But from your posts I assume that this is not applicable in your case. So while you are in the durable subscribers view for a channel in Enterprise Manager:
Remember the ID of the connection that you want to reset.
Click on the channel which this durable belongs to in the left hand side tree.
Click the Connections tab in the right hand side panel - you will see all connections to this channel.
Find and click the connection which you want to reset (from step 1).
Press the Bounce button at the bottom.
The connection will be “bounced” - closed and recreated by the client.
I’m glad that you have solved the problem. This seems like a good solution. In such situations you should pay attention to consumers (in your case - triggers) and check if they are consuming and acknowledging events properly. If they are not, you need to fix them (if possible) or restart them (hoping that they will start working well afterwards).