Trigger issue?

[Kerni]

Dear wmUsers,
In one of our interfaces we are using a parallel processing(publish multiple documents, subscribe them concurrently, process requests and wait for reply) method to meet the business requirment which the request and reply process should be completed within 20 sec.
Most of the time the process completes within 2-8 seconds. however, sometimes it takes more than 20 sec, which forces the requester to time-out. According to our log history, those failed requests, the published documents stay in the broker for long time (~20 sec) and all the process time elapsed before the trigger subscribes to the documents.
- We increased the trigger capcity to 50 with refill level 15. Processing more is concurrent with 15 max thread exec. But it didn't solve the issue.
- the docoments are small in side (<10kb)

If you have any suggestion or solution to this issue I appreciate your help.
thanks,
Kerni

[reamon]

I've looked but I cannot seem to find any info on controlling how often IS retrieves docs from the Broker. I looked in the Pub/Sub guide and in the performance tuning whitepaper in GEAR. Perhaps there is another doc somewhere on Advantage? This might be worth a chat with tech support.

[Muhammad.Gouse]

Hi Rob,

The same issue i am also facing, what kerni has described, i have checked with the Properties(Execution Threads, ProcessingMode , Capacity Level, Refill Level) some times the Triggers subscribes the documents from the Broke Queue very fase but some times it is very slow. I am not sure what is the processing speed of the documents and that to we have set the clusters.

If you find any solution please let us know.

Thanks in Advance
Gouse.

[dhimate]

I seem to overheard about following properties. I am not sure about reliability of these. :)


1.) watt.server.control.triggerInputControl.delays (which corresponds to Poll Delay Interval). By setting this to a specific value say X ms, you can force the trigger to keep polling the Broker after every X ms indefinitely until a document is available.
2.)watt.server.control.triggerInputControl.delayIncrementInterval (which corresponds to Poll Delay Interval Increment).

[griffima]

dhimate post is correct. The following parameter:
watt.server.control.triggerInputControl.delays will override the strange algorithm webMethods IS dispatcher has for getting documents from the broker.

It does seem to work okay, we have been using it for a while. I haven't seen any bad effects yet.....:eek:

[Kerni]

Thanks dhimate & griffima. I will try this an let you know the updates.