You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Chris Robison (Created) (JIRA)" <ji...@apache.org> on 2012/02/23 02:23:48 UTC

[jira] [Created] (AMQ-3735) Java service wrapper ${activemq.conf} not found

Java service wrapper ${activemq.conf} not found
-----------------------------------------------

                 Key: AMQ-3735
                 URL: https://issues.apache.org/jira/browse/AMQ-3735
             Project: ActiveMQ
          Issue Type: Bug
          Components: Broker
         Environment: Ubuntu 11.10 x64
            Reporter: Chris Robison


I downloaded the latest snapshot of the source today and tried installing the broker as a service using the instructions here: http://www.forwardslashbin.com/?p=46. When running it, apparently the Jetty configuration could not find the path to the conf folder. When removing the jetty.xml file from activemq xml, everything seemed to execute fine. Looking at the revision history, it looks like ${activemq.conf} is new to help externalize conf files. I'll be attaching the wrapper.log to this bug.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Resolved] (AMQ-3735) Java service wrapper ${activemq.conf} not found

Posted by "Timothy Bish (Resolved) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AMQ-3735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Bish resolved AMQ-3735.
-------------------------------

    Resolution: Fixed

Added the activemq.conf and activemq.data defs in the wrapper.conf files.
                
> Java service wrapper ${activemq.conf} not found
> -----------------------------------------------
>
>                 Key: AMQ-3735
>                 URL: https://issues.apache.org/jira/browse/AMQ-3735
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>         Environment: Ubuntu 11.10 x64
>            Reporter: Chris Robison
>             Fix For: 5.6.0
>
>         Attachments: wrapper.log
>
>
> I downloaded the latest snapshot of the source today and tried installing the broker as a service using the instructions here: http://www.forwardslashbin.com/?p=46. When running it, apparently the Jetty configuration could not find the path to the conf folder. When removing the jetty.xml file from activemq xml, everything seemed to execute fine. Looking at the revision history, it looks like ${activemq.conf} is new to help externalize conf files. I'll be attaching the wrapper.log to this bug.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (AMQ-3735) Java service wrapper ${activemq.conf} not found

Posted by "Gary Tully (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AMQ-3735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Tully updated AMQ-3735:
----------------------------

    Fix Version/s: 5.6.0

make sure we fix for 5.6
                
> Java service wrapper ${activemq.conf} not found
> -----------------------------------------------
>
>                 Key: AMQ-3735
>                 URL: https://issues.apache.org/jira/browse/AMQ-3735
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>         Environment: Ubuntu 11.10 x64
>            Reporter: Chris Robison
>             Fix For: 5.6.0
>
>         Attachments: wrapper.log
>
>
> I downloaded the latest snapshot of the source today and tried installing the broker as a service using the instructions here: http://www.forwardslashbin.com/?p=46. When running it, apparently the Jetty configuration could not find the path to the conf folder. When removing the jetty.xml file from activemq xml, everything seemed to execute fine. Looking at the revision history, it looks like ${activemq.conf} is new to help externalize conf files. I'll be attaching the wrapper.log to this bug.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (AMQ-3735) Java service wrapper ${activemq.conf} not found

Posted by "Chris Robison (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AMQ-3735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Robison updated AMQ-3735:
-------------------------------

    Attachment: wrapper.log

Java service wrapper log file.
                
> Java service wrapper ${activemq.conf} not found
> -----------------------------------------------
>
>                 Key: AMQ-3735
>                 URL: https://issues.apache.org/jira/browse/AMQ-3735
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>         Environment: Ubuntu 11.10 x64
>            Reporter: Chris Robison
>         Attachments: wrapper.log
>
>
> I downloaded the latest snapshot of the source today and tried installing the broker as a service using the instructions here: http://www.forwardslashbin.com/?p=46. When running it, apparently the Jetty configuration could not find the path to the conf folder. When removing the jetty.xml file from activemq xml, everything seemed to execute fine. Looking at the revision history, it looks like ${activemq.conf} is new to help externalize conf files. I'll be attaching the wrapper.log to this bug.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira