[
https://issues.apache.org/jira/browse/STORM-1542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Agarwal updated STORM-1542:
------------------------------------
Summary: Clicking jstack for a worker in UI results in endless empty jstack
dumps (was: Clicking jstack in ui results in endless empty jstack dumps)
> Clicking jstack for a worker in UI results in endless empty jstack dumps
> ------------------------------------------------------------------------
>
> Key: STORM-1542
> URL: https://issues.apache.org/jira/browse/STORM-1542
> Project: Apache Storm
> Issue Type: Bug
> Components: storm-core
> Affects Versions: 1.0.0
> Reporter: Abhishek Agarwal
> Assignee: Abhishek Agarwal
> Priority: Critical
>
> Resolved path for jstack is
> /home/y/share/yjava_jdk/java/jstack which doesn't exist. Exit code returned
> is 127. When a request for jstack dump is made, a zookeeper entry is made for
> the action. Now supervisor keeps on reading this action, executes it and
> since exit code is non-zero, doesn't delete the node. So supervisor keeps on
> trying forever and the non-existent command results in empty file
> {noformat}
> $BINPATH/jstack $1 > "$2/${FILENAME}"
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
