[jira] [Updated] (UIMA-1426) More control for apps against OOMs from UIMA core: Add configuration option to set the maximum heap size the CAS will grow to

["Richard Eckart de Castilho (JIRA)" <de...@uima.apache.org>]

     [ https://issues.apache.org/jira/browse/UIMA-1426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Richard Eckart de Castilho updated UIMA-1426:
---------------------------------------------
    Labels: Stale  (was: )

This issue is marked as "stale" due to inactivity for 5 years or longer. If no further activity is detected on this issue, it is scheduled be closed as 'unresolved' in 3 months time from now (Dec 2016).

> More control for apps against OOMs from UIMA core: Add configuration option to set the maximum heap size the CAS will grow to
> -----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: UIMA-1426
>                 URL: https://issues.apache.org/jira/browse/UIMA-1426
>             Project: UIMA
>          Issue Type: Improvement
>          Components: Core Java Framework
>    Affects Versions: 2.3
>            Reporter: Thomas Hampp
>              Labels: Stale
>
> Applications need to protect themselves against out of memory exceptions (OOMs). UIMA should help with that by making sure a growth in the CAS heap size will not cause an OOM. One way to do this is to add a config param that controls the maximum heap size for a CAS and throw a runtime exception if that threshold is exceeded.
> Since apps often use multiple CASes in pools in multihreaded fashion they would still need to exercise some app specific math (and guesswork) to determine the right value for this param. But at least they would be able to have some control.
> (There could still be OOMs during UIMA processing from other sources)



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