You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Jörn Kottmann (JIRA)" <ui...@incubator.apache.org> on 2010/01/07 13:19:54 UTC
[jira] Commented: (UIMA-1718) The UIMA core code fails to unlock a
CAS if there is an exception in CasMultiplier's next() or hasNext() methods
[ https://issues.apache.org/jira/browse/UIMA-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12797604#action_12797604 ]
Jörn Kottmann commented on UIMA-1718:
-------------------------------------
Thanks, the warning "CASAdminException: Can't flush CAS, flushing is disabled." does not appear anymore in my log file.
> The UIMA core code fails to unlock a CAS if there is an exception in CasMultiplier's next() or hasNext() methods
> ----------------------------------------------------------------------------------------------------------------
>
> Key: UIMA-1718
> URL: https://issues.apache.org/jira/browse/UIMA-1718
> Project: UIMA
> Issue Type: Bug
> Components: Core Java Framework
> Reporter: Jerry Cwiklik
> Assignee: Jerry Cwiklik
> Fix For: 2.3
>
>
> If there is an exception in user's Cas Multiplier hasNext() or next() method, the framework does not unlock the input CAS. If an application attempts to reset a CAS that failed in above methods, the following is produced: CASAdminException: Can't flush CAS, flushing is disabled.
> Modify AnalysisComponentCasIterator (an inner class of PrimitiveAnalysisEngine_impl) to call
> ((CASImpl)mInputCas).restoreClassLoaderUnlockCas();
> in both hasNext() and next() while handling an exception thrown from user's code.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.