[ 
https://issues.apache.org/jira/browse/AMQ-9434?focusedWorklogId=904700&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-904700
 ]

ASF GitHub Bot logged work on AMQ-9434:
---------------------------------------

                Author: ASF GitHub Bot
            Created on: 13/Feb/24 09:11
            Start Date: 13/Feb/24 09:11
    Worklog Time Spent: 10m 
      Work Description: cliviu opened a new pull request, #1152:
URL: https://github.com/apache/activemq/pull/1152

   allow starting ActiveMQ on Linux when there is space in the folder path




Issue Time Tracking
-------------------

            Worklog Id:     (was: 904700)
    Remaining Estimate: 0h
            Time Spent: 10m

> Unable to start ActiveMQ on Linux when there is space in the folder path
> ------------------------------------------------------------------------
>
>                 Key: AMQ-9434
>                 URL: https://issues.apache.org/jira/browse/AMQ-9434
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.18.3, 5.17.6
>         Environment: OpenSuse 15.5 
> jdk-11.0.17+8
>            Reporter: Liviu Carausu
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> When installed in a folder containing a space, the broker cannot start on a 
> Linux system.
> On Windows it works.
> {noformat}
> ~/data/programs/apache-activemq 5.18.3/bin> ./activemq start
> INFO: Using default configuration
>       Configurations are loaded in the following order: /etc/default/activemq 
> /home/johndoe/.activemqrc /home/johndoe/data/programs/apache-activemq 
> 5.18.3//bin/env
> INFO: Using java '/home/johndoe/data/programs/java/jdk-11.0.17+8//bin/java'
> ./activemq: line 492: [: /home/johndoe/data/programs/apache-activemq: binary 
> operator expected
> INFO: Starting - inspect logfiles specified in logging.properties and 
> log4j2.properties to get details
> {noformat}
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to