[jira] [Resolved] (STORM-470) DisruptorQueue catch blocks do not capture stack trace

["Sriharsha Chintalapani (JIRA)" <ji...@apache.org>]

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

Sriharsha Chintalapani resolved STORM-470.
------------------------------------------
    Resolution: Fixed

> DisruptorQueue catch blocks do not capture stack trace
> ------------------------------------------------------
>
>                 Key: STORM-470
>                 URL: https://issues.apache.org/jira/browse/STORM-470
>             Project: Apache Storm
>          Issue Type: Bug
>    Affects Versions: 0.9.2-incubating
>         Environment: java 1.7 update 67 debian wheezy and squeeze
>            Reporter: Jason Kania
>              Labels: RuntimeException, debugging, newbie, tracing
>
> The catch blocks for many of the Exceptions in the DisruptorQueue.java file do not extract the stack trace for debugging with the result being that errors cannot readily be diagnosed. The stack trace output should become part of the subsequent Runtime exception text such that it can be used in the diagnosis of problems. As it is now, all that a person gets is the error message which depends highly on the quality of the error text that the code author wrote for the class that raised the error. In many cases, this can be poor.



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