Documents are suddenly queuing up in 2 clients in one of the brokers in our environment. Corresponding triggers in IS are enabled and Broker is connected too. How to make these documents process further? Disabling and enabling the triggers will help? Will the queued up documents be lost by restarting the trigger ?
Follow the below steps if you have multiple servers which are connected to same broker :
Login to IS and Goto Messaging → webMethods Trigger Management. Suspend the Document Retrieval and Document Processing for the triggers which are queued up.
Login to MWS → Messaging → Broker Servers → Clients and search for the trigger which is queued. Click on the client and navigate to Sessions tab. Identify the IP address of your IS where the documents are queued and then disconnect that session.
Once this is done, queued docs gets processed from other available servers.
Post this you can restart the IS where the docs were queued.
I would first go to the Trigger Management screen on the IS Admin console to ensure the trigger’s didn’t get suspended. If they did, then resume them. If they didn’t, then you can try reloading the package containing the triggers. That has worked for me in the past for a similar issue.
I don’t recommend disabling and re-enabling the trigger because that can result in the messages that are currently queued up getting purged in a non-clustered environment.
If we go for package reload , still docs in the queue will be available or processed or purged ?
I have one more question, what is the unacknowledged length in client statistics. will the docs got processed ?
Thanks in advance…!!
the unacknowledged length is the number of documents already retrieved by IntegrationServer or PartnerSystem, but not yet processed and acknowledged. Documents will be processed.
Regarding Package reload:
During the package reload the documents will not be processed. Processing restarts after the package reload completes.
Some times , I see an error like 'http response error please contact administrator ’ in MWS when try to search for service logs.
Can anyone please suggest me what will be root cause and how resolve this issue.
This issue in wM 9.7 &9.12