Time It Takes To Resume An Order In An Asynchronous Cartridge
(Doc ID 1579783.1)
Last updated on JUNE 14, 2017
Applies to:Oracle Communications ASAP - Version 7.0.2 and later
Information in this document applies to any platform.
What is the time it takes to resume an order in an asynchronous cartridge?
Below is the explanation of the requirement:
An asynchronous cartridge for a JMS solution is being built and the examples given in the supplied 'samples' directory for ASAP are being followed.
It all works as expected except when the event handler resumes, the order that has received back the complete set of JMS responses for that order. The order gets resumed but it takes over 20 seconds for the order to actually get restarted again.
An order has a number of sets of JMS requests to send. Each time it is taking 20 seconds to resume the order. This means the order is taking over 90 seconds to complete when it should be 10 seconds. The solution also requires a user to wait until the order is completed so they can check the config - this adds a lot of additional waiting time that should not be necessary.
Is there some way we can get the order to be resumed straight away? Is there a config setting somewhere?
Otherwise, the only solution is to keep the order open and poll for the responses to be completed - which is not really a proper asynchronous solution.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document