[jira] [Resolved] (STORM-2659) storm.cmd does not set -Ddaemon.name, which prevents Log4j2 from logging

["Stig Rohde Døssing (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/STORM-2659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stig Rohde Døssing resolved STORM-2659.
---------------------------------------
       Resolution: Fixed
    Fix Version/s: 1.1.1

> storm.cmd does not set -Ddaemon.name, which prevents Log4j2 from logging
> ------------------------------------------------------------------------
>
>                 Key: STORM-2659
>                 URL: https://issues.apache.org/jira/browse/STORM-2659
>             Project: Apache Storm
>          Issue Type: Bug
>          Components: storm-core
>    Affects Versions: 1.1.0
>            Reporter: Stig Rohde Døssing
>            Assignee: Stig Rohde Døssing
>            Priority: Critical
>             Fix For: 1.1.1
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> When trying to start any daemon from storm.cmd the following error occurs:
> {code}
> main ERROR Unable to create file E:\apache-storm-1.1.1\logs/access-web-${sys:daemon.name}.log java.io.IOException: The filename, directory name, or volume label syntax is incorrect
> {code}
> It looks like the daemon-name variable was introduced at some point, but only the storm.py script was updated. This prevents Storm from logging when started from this script.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)