[
https://issues.apache.org/jira/browse/STORM-469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14284581#comment-14284581
]
Derek Dagit commented on STORM-469:
-----------------------------------
Meant to reply earlier. OK, I would rather not resolve this jira as a
duplicate then. What if we rename it to something like "No easy way to reach
full stack trace from UI Last Error Detail?" Then we can see what solution
would be appropriate.
> Storm UI Last Error Detail Insufficient for debugging
> -----------------------------------------------------
>
> Key: STORM-469
> URL: https://issues.apache.org/jira/browse/STORM-469
> 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
> Assignee: Rekha Joshi
>
> The error text that is captured in the Storm UI is insufficient to debug the
> issue as it gets cut off and does not link to the actual error to allow a
> person to get more detail. This means that the debugging is unnecessarily
> blind. This prevents diagnosis of the error.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
