The original developer took a look at the CPE code and saw that the
status of the component
is changed to failed immediately upon detecting an exception. What
happens to the CAS after the exception is subject to
a strategy defined in the cpe descriptor.
If the cpe descriptor is set up like this:
<casProcessors dropCasOnException="true" ...
the CPE will drop the CAS after detecting the exception. User's code can
check events as described and assume that the CAS was dropped.
-Marshall
Muon Le wrote:
Hi Marshall,
I found a means to know if a CPE has an entity that is skipped or not.
For each EntityProcessComplete(CAS, EntityProcessStatus), we can get a list of
ProcessTraceEvents (using cpe.getPerformanceReport().getEvents()). These events
contain all component names for the CPE and their status (success or failed).
When the EntityProcessStatus.isException() returns FALSE and the process tracing events
contain a component in "failed" status, we can assume the CPE has a component
that is skipped.
Do you think I can use that means instead of
EntityProcessStatus.isEntitySkipped() which is bugged until it is corrected?
Thanks a lot,
LE Tan Muon.
-----Message d'origine-----
De : Marshall Schor [mailto:[EMAIL PROTECTED]
Envoyé : jeudi 29 mars 2007 21:35
À : [email protected]
Objet : Re: EntityProcessStatus.isEntitySkipped() always returns false
Hi Eric -
This appears to be a new bug, unknown before. We think it is *not*
fixed in the 2.1 release. We'll work on getting it fixed in the next
release.
Thanks for reporting it. -Marshall
Eric VACHON wrote:
Hi
As Olivier already described it in the alphaworks forum, we have a
simple CPE composed of a collection reader, an analysis engine (named ERROR) remotely deployed as a Vinci service and an integrated consumer. Our error handling parameters are set to "continue"
The descriptor looks like:
<?xml version="1.0" encoding="UTF-8"?> <cpeDescription>
<collectionReader>
<collectionIterator>
<descriptor>
<include href="SimpleCollectionReader.xml"/>
</descriptor>
<configurationParameterSettings />
</collectionIterator>
</collectionReader>
<casProcessors casPoolSize="2" processingUnitThreadCount="1">
<casProcessor deployment="remote" name="ERROR">
<descriptor>
<include href="ERROR.xml"/>
</descriptor>
<filter/>
<errorHandling>
<errorRateThreshold action="continue" value="2/5"/>
<maxConsecutiveRestarts action="continue" value="2"/>
<timeout max="300000"/>
</errorHandling>
<checkpoint batch="1"/>
<deploymentParameters>
<parameter name="vnsHost" type="string" value="localhost"/>
<parameter name="vnsPort" type="string" value="9000"/>
<parameter name="service-access" type="string"
value="exclusive"/>
</deploymentParameters>
</casProcessor>
<casProcessor deployment="integrated" name="SimpleCasConsumer">
<descriptor>
<include href="SimpleCasConsumer.xml"/>
</descriptor>
<deploymentParameters/>
<filter/>
<errorHandling>
<errorRateThreshold action="continue" value="2/5"/>
<maxConsecutiveRestarts action="continue" value="2"/>
<timeout max="300000"/>
</errorHandling>
<checkpoint batch="1"/>
</casProcessor>
</casProcessors>
<cpeConfig>
<numToProcess>-1</numToProcess>
<deployAs>immediate</deployAs>
<checkpoint file="" time="300000"/>
<timerImpl/>
</cpeConfig>
</cpeDescription>
The ERROR cas processor generates AnnotatorProcessException when the processing
of some particular documents ( CAS ) went wrong.
We have a StatusCallbackListener with a entityProcessComplete method
implemented like that:
public void entityProcessComplete(CAS aCas, EntityProcessStatus aStatus) {
if (aStatus.isEntitySkipped()) {
System.err.println("The CAS has been skipped by at
least one component");
}
if (aStatus.isException()) {
List exceptions = aStatus.getExceptions();
for (int i = 0; i < exceptions.size(); i++) {
((Throwable)
exceptions.get(i)).printStackTrace(System.err);
}
return;
}
entityCount++;
size += aCas.getTCAS().getDocumentText().length();
}
Our ERROR cas processor generates exceptions that are nicely detected by the
aStatus.getExceptions() call. But after the number of 'retries' is reached for
the processor (this number is set to 2 as
you can see in the descriptor), the entityProcessComplete is called with a
aStatus.isException() set to false which is the expected behaviour but the
aStatus.isEntitySkipped() is also set to false
which is not the expected value because the CAS has actually been skipped by
the ERROR processor.
We have this bug in the UIMA 1.4.3 version and we have to stick with it for
some more time. But we will upgrade to the apache version soon and we would
like to know if this issue has been fixed in 2.1.
Can you confirm that it is a known bug and if it is already fixed ?
Thanks a lot
