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

Posted to notifications@geode.apache.org by "pdxcodemonkey (GitHub)" <gi...@apache.org> on 2019/04/09 22:17:46 UTC

[GitHub] [geode-native] pdxcodemonkey opened pull request #472: GEODE-6624: Fix nested exception in geode-native causing SIGABRT

Co-authored-by: Matthew Reddington <mr...@pivotal.io>

We were hitting a nested exception, which caused a SIGABRT in the client.  Now we catch the second exception, and clear the first out of the "pending" location, so it doesn't get thrown from within a catch block and blow us up.

[ Full content available at: https://github.com/apache/geode-native/pull/472 ]
This message was relayed via gitbox.apache.org for notifications@geode.apache.org

[GitHub] [geode-native] pdxcodemonkey closed pull request #472: GEODE-6624: Fix nested exception in geode-native causing SIGABRT

Posted by "pdxcodemonkey (GitHub)" <gi...@apache.org>.

[ pull request closed by pdxcodemonkey ]

[ Full content available at: https://github.com/apache/geode-native/pull/472 ]
This message was relayed via gitbox.apache.org for notifications@geode.apache.org

[GitHub] [geode-native] pdxcodemonkey commented on issue #472: GEODE-6624: Fix nested exception in geode-native causing SIGABRT

Posted by "pdxcodemonkey (GitHub)" <gi...@apache.org>.

Actually, gonna close this for a while until I can add a repro test case.

[ Full content available at: https://github.com/apache/geode-native/pull/472 ]
This message was relayed via gitbox.apache.org for notifications@geode.apache.org