[
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.
