You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Alexander Fisher (JIRA)" <ji...@apache.org> on 2010/11/23 16:37:24 UTC

[jira] Created: (AMQ-3050) ActiveMQ standalone script doesn't return with 0 when stop is called.

ActiveMQ standalone script doesn't return with 0 when stop is called.
---------------------------------------------------------------------

                 Key: AMQ-3050
                 URL: https://issues.apache.org/activemq/browse/AMQ-3050
             Project: ActiveMQ
          Issue Type: Bug
    Affects Versions: 5.4.1
            Reporter: Alexander Fisher


I was testing to see if the ./bin/activemq script was LSB compatible (I want to integrate activemq into a pacemaker setup).

When calling ./bin/activemq stop, the script should return 0 on success.

The problem is in the invokeJar function.  In the 'stop' case , the value of RET is set in the context of a forked process.
The proposed fix, is identical to how RET is handled in the other 2 cases.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Assigned: (AMQ-3050) ActiveMQ standalone script doesn't return with 0 when stop is called.

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

Dejan Bosanac reassigned AMQ-3050:
----------------------------------

    Assignee: Dejan Bosanac

> ActiveMQ standalone script doesn't return with 0 when stop is called.
> ---------------------------------------------------------------------
>
>                 Key: AMQ-3050
>                 URL: https://issues.apache.org/activemq/browse/AMQ-3050
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.4.1
>            Reporter: Alexander Fisher
>            Assignee: Dejan Bosanac
>         Attachments: activemq-return-value.patch
>
>
> I was testing to see if the ./bin/activemq script was LSB compatible (I want to integrate activemq into a pacemaker setup).
> When calling ./bin/activemq stop, the script should return 0 on success.
> The problem is in the invokeJar function.  In the 'stop' case , the value of RET is set in the context of a forked process.
> The proposed fix, is identical to how RET is handled in the other 2 cases.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (AMQ-3050) ActiveMQ standalone script doesn't return with 0 when stop is called.

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

Alexander Fisher updated AMQ-3050:
----------------------------------

    Attachment: activemq-return-value.patch

Patch correcting issue.

> ActiveMQ standalone script doesn't return with 0 when stop is called.
> ---------------------------------------------------------------------
>
>                 Key: AMQ-3050
>                 URL: https://issues.apache.org/activemq/browse/AMQ-3050
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.4.1
>            Reporter: Alexander Fisher
>         Attachments: activemq-return-value.patch
>
>
> I was testing to see if the ./bin/activemq script was LSB compatible (I want to integrate activemq into a pacemaker setup).
> When calling ./bin/activemq stop, the script should return 0 on success.
> The problem is in the invokeJar function.  In the 'stop' case , the value of RET is set in the context of a forked process.
> The proposed fix, is identical to how RET is handled in the other 2 cases.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (AMQ-3050) ActiveMQ standalone script doesn't return with 0 when stop is called.

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

Dejan Bosanac resolved AMQ-3050.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 5.5.0

Fixed with svn revision 1038539. Thanks for the patch

> ActiveMQ standalone script doesn't return with 0 when stop is called.
> ---------------------------------------------------------------------
>
>                 Key: AMQ-3050
>                 URL: https://issues.apache.org/activemq/browse/AMQ-3050
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.4.1
>            Reporter: Alexander Fisher
>            Assignee: Dejan Bosanac
>             Fix For: 5.5.0
>
>         Attachments: activemq-return-value.patch
>
>
> I was testing to see if the ./bin/activemq script was LSB compatible (I want to integrate activemq into a pacemaker setup).
> When calling ./bin/activemq stop, the script should return 0 on success.
> The problem is in the invokeJar function.  In the 'stop' case , the value of RET is set in the context of a forked process.
> The proposed fix, is identical to how RET is handled in the other 2 cases.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.