Pierre, thanks I will try to replicate the scenario to see what is
preventing CASes from timing out in the application client.
JC
On Thu, Mar 31, 2011 at 11:03 AM, Pierre Pujalon wrote:
> JC, I have this timeout setted already then. The callback only receives
> the timeout exception for the fi
JC, I have this timeout setted already then. The callback only receives
the timeout exception for the first CAS.
This only occurs when I have a delegated annotator.
When I configure my application with aggregates without any delegate
annotator, the callback receives timeout from all CASes.
Pierre, to set a timeout on the aggregate do the following in the
application client:
//create Asynchronous Client API
uimaAsEngine = new BaseUIMAAsynchronousEngine_impl();
//create Map to pass server URI and Endpoint parameters
Map appCtx = new HashMap();
...
appCtx.put(UimaAsynchronousEngine.Tim
JC
I have a 15000ms process timeout for the UIMAEngine and I have a 15000ms
timeout for the remoteDelegate
I haven't found how to set a timeout for the aggregate to be honest.
You are right I have this exception in the console
javax.jms.InvalidDestinationException: Cannot publish to a deleted
Pierre, since the aggregate received the three CASes and these are never
returned to the application client I suspect that a temp reply queue
associated with the three CASes is no longer valid. Check your aggregate log
for exceptions. Perhaps the aggregate is trying to return the CASes but it
fails
JC,
I had to work on this topic and add instrumentation a bit to try to have
a clearer vision. The basic idea is to test robustness of the processing
when the ActiveMQ have a downtime (generally only for milliseconds).
This scenario is a real life scenario.
I have an application client using
