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

Posted to dev@usergrid.apache.org by "Michael Russo (JIRA)" <ji...@apache.org> on 2016/05/11 06:33:13 UTC

[jira] [Commented] (USERGRID-1288) Don't log full stack trace on Elasticsearch timeouts

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

Michael Russo commented on USERGRID-1288:
-----------------------------------------

Fixed in dfaf344a0e294520e12f672be595b52c7c857330

> Don't log full stack trace on Elasticsearch timeouts
> ----------------------------------------------------
>
>                 Key: USERGRID-1288
>                 URL: https://issues.apache.org/jira/browse/USERGRID-1288
>             Project: Usergrid
>          Issue Type: Story
>    Affects Versions: 2.1.0
>            Reporter: Michael Russo
>            Assignee: Michael Russo
>            Priority: Minor
>             Fix For: 2.1.1
>
>
> Observed when Usergrid application servers were running out of memory, thousands of Elasticsearch exception stack traces were logged.  Change this to log only the exception message and no need to print the full stack trace.



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