You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@uima.apache.org by "Jerry Cwiklik (JIRA)" <de...@uima.apache.org> on 2014/02/28 17:08:23 UTC

[jira] [Created] (UIMA-3660) Improve UIMA-AS logging in UimaAsThreadFactory when handling java Error

Jerry Cwiklik created UIMA-3660:
-----------------------------------

             Summary: Improve UIMA-AS logging in UimaAsThreadFactory when handling java Error
                 Key: UIMA-3660
                 URL: https://issues.apache.org/jira/browse/UIMA-3660
             Project: UIMA
          Issue Type: Bug
          Components: Async Scaleout
    Affects Versions: 2.4.2AS
            Reporter: Jerry Cwiklik
            Assignee: Jerry Cwiklik
            Priority: Minor
             Fix For: 2.5.0AS


The UimaAsThreadFactory attempts to log a java error in the catch(E) block. If the error is OOM, the cause of the error is not logged as the jvm is tight on memory and it fails to log. The code succeeds dumping a message to stdout. Given that, improve the message that goes to stdout to include  the real cause of the error



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)