[
https://issues.apache.org/jira/browse/STORM-1001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14706344#comment-14706344
]
ASF GitHub Bot commented on STORM-1001:
---------------------------------------
GitHub user drewrobb opened a pull request:
https://github.com/apache/storm/pull/695
Fixes STORM-1001
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/drewrobb/incubator-storm dr/STORM-1001
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/storm/pull/695.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 #695
----
commit 2169a616f7b117edf7ef654d59ecd3fa3b8dc1cc
Author: Drew Robb <[email protected]>
Date: 2015-08-21T07:31:51Z
Fixes STORM-1001
----
> Undefined STORM_EXT_CLASSPATH adds '::' to classpath of workers
> ---------------------------------------------------------------
>
> Key: STORM-1001
> URL: https://issues.apache.org/jira/browse/STORM-1001
> Project: Apache Storm
> Issue Type: Bug
> Affects Versions: 0.10.0
> Reporter: Drew Robb
> Priority: Minor
>
> If environment variable STORM_EXT_CLASSPATH is undefined, an empty string
> will used in the classpath for workers. I'm not sure how java is expected to
> handle this, but bad things happen, including behavior that is dependent on
> the working directory that the supervisor was launched in. A simple
> workaround is to set STORM_EXT_CLASSPATH to a path that does not exist.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
