You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Marshall Schor (JIRA)" <de...@uima.apache.org> on 2016/10/04 17:48:20 UTC

[jira] [Commented] (UIMA-5120) Enable/disable CAS logging via JMX

    [ https://issues.apache.org/jira/browse/UIMA-5120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15546116#comment-15546116 ] 

Marshall Schor commented on UIMA-5120:
--------------------------------------

The logging of CASs is in xmi format, with an additional typesystem.xml file in the directory.

2.9.0 added some conventions for storing / loading type systems.  However, the format is in the form that CAS Complete Serialization does this.
Perhaps some additional work should be done to have the CasUtility methods and conventions support the plain xml format.

Another extension for Cas utils could be around recognizing the convention of putting the typesystem.xml file in the same directory as a bunch of CASes.  WDOT?  (What do others think)

> Enable/disable CAS logging via JMX
> ----------------------------------
>
>                 Key: UIMA-5120
>                 URL: https://issues.apache.org/jira/browse/UIMA-5120
>             Project: UIMA
>          Issue Type: Improvement
>          Components: Async Scaleout
>            Reporter: Eddie Epstein
>
> CAS logging in UIMA-AS is currently done using java properties. This requires custom process configuration to dump CASes for one or more components. Putting a CAS dump control in the mbean of each asynchronous component would allow dumping to be turned off and on as needed for a running UIMA-AS service.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)