[
https://issues.apache.org/jira/browse/STORM-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13967458#comment-13967458
]
Padma Priya Chitturi edited comment on STORM-278 at 4/12/14 9:54 AM:
---------------------------------------------------------------------
P. Taylor Goetz will create a pull request, Thanks.
What is the significance of JMX_REMOTE_PORT added to STORM_OPTS ? Removing
from STORM_OPTS didn't have any impact on the running the daemons. Is it
necessary to have these JMXREMOTE options in STORM_OPTS ?
was (Author: padmach):
P. Taylor Goetz, will create a pull request, Thanks.
What is the significance of JMX_REMOTE_PORT added to STORM_OPTS ? Removing
from STORM_OPTS didn't have any impact on the running the daemons. Is it
necessary to have these JMXREMOTE options in STORM_OPTS ?
> Storm on Windows: Modifications required for storm.cmd
> ------------------------------------------------------
>
> Key: STORM-278
> URL: https://issues.apache.org/jira/browse/STORM-278
> Project: Apache Storm (Incubating)
> Issue Type: Improvement
> Environment: Windows
> Reporter: Padma Priya Chitturi
> Labels: windows
> Attachments: storm-278-patch.patch, storm-config-278-patch.patch
>
>
> When I started working on storm.cmd on windows platform, identified that
> logs for nimbus/supervisor were not seen. Also, storm classpath doesn't seem
> to have storm jars and jars in lib.
> The childopts from storm.yaml are not read by the bat files. Could see some
> hardcoded values for these childopts in storm.cmd.
> storm.cmd file doesn't provide all features as in storm.py
--
This message was sent by Atlassian JIRA
(v6.2#6252)
