Hi Marshall,
The issue is the same as you mentioned here It resolved. But I got the
same error if I used more documents and this error is coming on the same
set of document suppose(250) but not on a particular document but some
time after 50 document's processing or some time after 100 document's
processing and some time after 150 or 170 document's processing. So, It
is not the issue of the pipeline but I noticed that the heap space for
the Memory Pool PS|Surviver space.
|
On 07/19/2013 03:11 PM, reshu.agarwal wrote:
On 07/18/2013 10:35 PM, Marshall Schor wrote:
See
http://uima.apache.org/d/uima-as-2.4.0/uima_async_scaleout.html#ugr.async.ov.concepts.parallelFlows
-Marshall
On 7/18/2013 11:29 AM, Marshall Schor wrote:
When you run in parallel, there's a restriction on what the remote
annotators
can modify in the CAS: the annotators are not allowed to modify feature
structures that already exist; they can only add new feature
structures.
The error reported below occurs when the CAS being returned from a
remote
annotator has modified some feature structure in the CAS that
existed when it
received the CAS.
-Marshall
On 7/17/2013 4:36 AM, reshu.agarwal wrote:
Hi JC,
Thanks for replying. This works and I also implemented it to my own
descriptors.
If I used serial flow it works perfectly but if I used parallel
flow and
deploying all the descriptors services which are in parallel,
it shows the following error:
Error on process CAS call to remote service:
org.apache.uima.aae.error.UimaEEServiceException:
org.apache.uima.cas.CASRuntimeException: "Preexisting FS
encountered but not
allowed. "xmi:id=17"
at
org.apache.uima.adapter.jms.activemq.JmsOutputChannel.sendReply(JmsOutputChannel.java:871)
at
org.apache.uima.aae.controller.AggregateAnalysisEngineController_impl.sendReplyWithException(AggregateAnalysisEngineController_impl.java:1967)
at
org.apache.uima.aae.controller.AggregateAnalysisEngineController_impl.sendReplyToRemoteClient(AggregateAnalysisEngineController_impl.java:2054)
at
org.apache.uima.aae.controller.AggregateAnalysisEngineController_impl.replyToClient(AggregateAnalysisEngineController_impl.java:2195)
at
org.apache.uima.aae.controller.AggregateAnalysisEngineController_impl.finalStep(AggregateAnalysisEngineController_impl.java:1758)
at
org.apache.uima.aae.controller.AggregateAnalysisEngineController_impl.abortProcessingCas(AggregateAnalysisEngineController_impl.java:1057)
at
org.apache.uima.aae.controller.AggregateAnalysisEngineController_impl.process(AggregateAnalysisEngineController_impl.java:1099)
at
org.apache.uima.aae.error.handler.ProcessCasErrorHandler.handleError(ProcessCasErrorHandler.java:565)
at
org.apache.uima.aae.error.ErrorHandlerChain.handle(ErrorHandlerChain.java:57)
at
org.apache.uima.aae.handler.input.ProcessResponseHandler.handleProcessResponseFromRemote(ProcessResponseHandler.java:360)
at
org.apache.uima.aae.handler.input.ProcessResponseHandler.handle(ProcessResponseHandler.java:704)
at
org.apache.uima.adapter.jms.activemq.JmsInputChannel.onMessage(JmsInputChannel.java:702)
at
org.apache.uima.adapter.jms.activemq.ConcurrentMessageListener$1.run(ConcurrentMessageListener.java:211)
at
org.apache.uima.aae.UimaBlockingExecutor$1.run(UimaBlockingExecutor.java:106)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at
org.apache.uima.aae.UimaAsThreadFactory$1.run(UimaAsThreadFactory.java:118)
at java.lang.Thread.run(Thread.java:722)
Caused by: org.apache.uima.cas.CASRuntimeException: "Preexisting FS
encountered but not allowed. "xmi:id=17"
at
org.apache.uima.cas.impl.XmiCasDeserializer$XmiCasDeserializerHandler.startElement(XmiCasDeserializer.java:362)
at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:506)
at
com.sun.org.apache.xerces.internal.parsers.AbstractXMLDocumentParser.emptyElement(AbstractXMLDocumentParser.java:182)
at
com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanStartElement(XMLNSDocumentScannerImpl.java:353)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2717)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:607)
at
com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:116)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:489)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:835)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764)
at
com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:123)
at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1210)
at
org.apache.uima.aae.UimaSerializer.deserializeCasFromXmi(UimaSerializer.java:197)
at
org.apache.uima.aae.handler.input.ProcessResponseHandler.deserialize(ProcessResponseHandler.java:382)
at
org.apache.uima.aae.handler.input.ProcessResponseHandler.handleProcessResponseFromRemote(ProcessResponseHandler.java:274)
... 8 more
Terminating Client...
Thanks in advance.
Have you deployed RoomNumberAnnotator service first? Use
Deploy_RoomNumberAnnotator.xml to launch it.
JC
On Tue, Jul 16, 2013 at 1:32 AM, Reshu Agarwal <reshu.agarwal@...
<http://gmane.org/get-address.php?address=reshu.agarwal%2dp5hCDL3j3lDQT0dZR%2bAlfA%40public.gmane.org>>wrote:
Hii...
If I try to run the Deploy_MeetingDetectorTAE_RemoteRoomNumber.xml
{example
deployment xml} the following error is given in uima.log:
7/16/13 10:53:23 AM - 25:.
org.apache.uima.aae.delegate.Delegate$2.Delegate.TimerTask.run:
WARNING:
Timeout While Waiting For Reply From Delegate:RoomNumber GetMeta
Request
Timed Out. Configured Reply Window Of 100,000.
Please help me out.
Thanks in advance.
Reshu
<http://news.gmane.org/find-root.php?message_id=%3cCAO329yAg6NDmx3JgT%2bTGVy1FxR2Z4YePY%5f0T3%2d3ZdNQOcJJUPw%40mail.gmail.com%3e>
Thanks Marshall, this description solves all my doubts .
I will try the defined scenario in the document and get back here with
my new problems If come any.
--
Thanks and Regards,
Reshu Agarwal
