[jira] [Commented] (AMQ-6213) Unable to use default login config in "activemq*.bat" files if ActiveMQ is installed in a path with spaces.

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMQ-6213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15250684#comment-15250684 ] 

ASF subversion and git services commented on AMQ-6213:
------------------------------------------------------

Commit 3bd03c4e186da4f96b77a832403c100a0c52efe1 in activemq's branch refs/heads/activemq-5.13.x from [~tabish121]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=3bd03c4 ]

AMQ-6213 Quote path values to ensure the script works when the path
contains spaces.

This closes #173
(cherry picked from commit 69c5fd7d5a56d13b4be2c56ca8e932c3d06b5d05)


> Unable to use default login config in "activemq*.bat" files if ActiveMQ is installed in a path with spaces.
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-6213
>                 URL: https://issues.apache.org/jira/browse/AMQ-6213
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Distribution
>    Affects Versions: 5.13.2
>         Environment: Windows 7 Enterprise x64
>            Reporter: Ryan Ferraro
>            Priority: Minor
>              Labels: newbie, patch
>             Fix For: 5.14.0, 5.13.3
>
>
> If ActiveMQ is installed in a path with spaces (like: "C:\Program Files\AMQ"), the batch files activemq.bat and activemq-admin.bat cannot start the service. 
> The source of the issue appears to be that the -Djava.security.auth.login.config command line option is getting passed a raw path value that is not properly encoded for spaces in the path. I have a patch available that surrounds this parameter value with quotations.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)