[
https://issues.apache.org/jira/browse/STORM-793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628121#comment-14628121
]
ASF GitHub Bot commented on STORM-793:
--------------------------------------
GitHub user redsanket opened a pull request:
https://github.com/apache/storm/pull/634
STORM-793 Made change to logviewer.clj in order to remove the invalid http
500 response
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/redsanket/storm fix_500_error
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/storm/pull/634.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #634
----
commit 6778b567b56b77a1ac0afe223305865b8684d199
Author: Sanket <schintap@untilservice-lm>
Date: 2015-07-15T14:10:37Z
made change to logviewer.clj in order to remove the invalid 500 http
response instead of 404
----
> Logviewer 500 response when metadata has not yet been written (with auth
> enabled)
> ---------------------------------------------------------------------------------
>
> Key: STORM-793
> URL: https://issues.apache.org/jira/browse/STORM-793
> Project: Apache Storm
> Issue Type: Bug
> Affects Versions: 0.10.0
> Reporter: Derek Dagit
> Assignee: Sanket Reddy
> Priority: Minor
> Labels: Newbie
>
> When ui.filter is defined and used, and a user navigates to a logviewer link
> for which the logging metadata has not yet been initialized, we [throw an
> NPE|https://github.com/apache/storm/blob/84e8bc6d28b54056dd75375be7d316ab03125fb6/storm-core/src/clj/backtype/storm/daemon/logviewer.clj#L184]
> that results in a 500 response.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
