You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by Claus Ibsen <cl...@gmail.com> on 2013/11/13 13:21:40 UTC
[ISSUE] - bin/activemq.bat for Windows users
Hi
I was looking at ticket
https://issues.apache.org/jira/browse/AMQ-3101
I wonder why starting ActiveMQ on windows and unix is different, according to
http://activemq.apache.org/version-5-getting-started.html#Version5GettingStarted-StartingActiveMQ
On windows we tell users to do
bin\activemq
And on unix
bin/activemq start
eg on unix you pass in the start command.
I would prefer that on Windows you should pass on the command as well such as
bin\activemq start
Otherwise you cannot get the help syntax by just using bin/activemq
Usage: Main [--extdir <dir>] [task] [task-options] [task data]
Tasks:
browse - Display selected messages in a
specified destination.
bstat - Performs a predefined query that
displays useful statistics regarding the specified broker
create - Creates a runnable broker instance in
the specified path.
decrypt - Decrypts given text
dstat - Performs a predefined query that
displays useful tabular statistics regarding the specified destination
type
encrypt - Encrypts given text
export - Exports a stopped brokers data files to
an archive file
list - Lists all available brokers in the
specified JMX context
purge - Delete selected destination's messages
that matches the message selector
query - Display selected broker component's
attributes and statistics.
start - Creates and starts a broker using a
configuration file, or a broker URI.
stop - Stops a running broker specified by the
broker name.
So I would if we should change this for Windows in the activemq.bat
file, to not have the "start" command in there. So its consistent with
unix.
And also fixes AMQ-3101
Anyone know any reason about the "start" in the bin/activemq.bat file?
--
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cibsen@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
Re: [ISSUE] - bin/activemq.bat for Windows users
Posted by Dejan Bosanac <de...@nighttale.net>.
I agree. Putting too much in the activemq unix start script was an
oversight and led to some bugs and inconsistencies we could have avoided.
Regards
--
Dejan Bosanac
----------------------
Red Hat, Inc.
FuseSource is now part of Red Hat
dbosanac@redhat.com
Twitter: @dejanb
Blog: http://sensatic.net
ActiveMQ in Action: http://www.manning.com/snyder/
On Thu, Nov 14, 2013 at 4:38 PM, Hiram Chirino <hi...@hiramchirino.com>wrote:
> I kinda wish that both activemq unix script and activemq were simple
> start activemq in the foreground scripts. Starting activemq as a
> service/background is different on Windows and Linux/Unix so that
> should done using other extra files etc.
>
> For example we could have a bin/activemq-service script for unix that
> handles doing the init.d unix stuff: 'activemq-service start'
> 'activemq-service stop' etc.
>
> On Wed, Nov 13, 2013 at 8:57 AM, Claus Ibsen <cl...@gmail.com>
> wrote:
> > Thanks
> >
> > So I assume it would be okay to remove the start from the
> > activemq.bat, and have Windows users start the broker as we do unix.
> >
> >
> >
> > On Wed, Nov 13, 2013 at 1:47 PM, Gary Tully <ga...@gmail.com>
> wrote:
> >> I think part of the reason is that only the unix scripts got an update
> >> via https://issues.apache.org/jira/browse/AMQ-2453
> >>
> >> consistency is good and simpler from a doc perspective.
> >>
> >> On 13 November 2013 12:21, Claus Ibsen <cl...@gmail.com> wrote:
> >>> Hi
> >>>
> >>> I was looking at ticket
> >>> https://issues.apache.org/jira/browse/AMQ-3101
> >>>
> >>>
> >>> I wonder why starting ActiveMQ on windows and unix is different,
> according to
> >>>
> http://activemq.apache.org/version-5-getting-started.html#Version5GettingStarted-StartingActiveMQ
> >>>
> >>> On windows we tell users to do
> >>> bin\activemq
> >>>
> >>> And on unix
> >>> bin/activemq start
> >>>
> >>> eg on unix you pass in the start command.
> >>>
> >>> I would prefer that on Windows you should pass on the command as well
> such as
> >>> bin\activemq start
> >>>
> >>> Otherwise you cannot get the help syntax by just using bin/activemq
> >>>
> >>> Usage: Main [--extdir <dir>] [task] [task-options] [task data]
> >>>
> >>> Tasks:
> >>> browse - Display selected messages in a
> >>> specified destination.
> >>> bstat - Performs a predefined query that
> >>> displays useful statistics regarding the specified broker
> >>> create - Creates a runnable broker instance in
> >>> the specified path.
> >>> decrypt - Decrypts given text
> >>> dstat - Performs a predefined query that
> >>> displays useful tabular statistics regarding the specified destination
> >>> type
> >>> encrypt - Encrypts given text
> >>> export - Exports a stopped brokers data files to
> >>> an archive file
> >>> list - Lists all available brokers in the
> >>> specified JMX context
> >>> purge - Delete selected destination's messages
> >>> that matches the message selector
> >>> query - Display selected broker component's
> >>> attributes and statistics.
> >>> start - Creates and starts a broker using a
> >>> configuration file, or a broker URI.
> >>> stop - Stops a running broker specified by the
> >>> broker name.
> >>>
> >>>
> >>> So I would if we should change this for Windows in the activemq.bat
> >>> file, to not have the "start" command in there. So its consistent with
> >>> unix.
> >>>
> >>> And also fixes AMQ-3101
> >>>
> >>>
> >>> Anyone know any reason about the "start" in the bin/activemq.bat file?
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> --
> >>> Claus Ibsen
> >>> -----------------
> >>> Red Hat, Inc.
> >>> Email: cibsen@redhat.com
> >>> Twitter: davsclaus
> >>> Blog: http://davsclaus.com
> >>> Author of Camel in Action: http://www.manning.com/ibsen
> >>
> >>
> >>
> >> --
> >> http://redhat.com
> >> http://blog.garytully.com
> >
> >
> >
> > --
> > Claus Ibsen
> > -----------------
> > Red Hat, Inc.
> > Email: cibsen@redhat.com
> > Twitter: davsclaus
> > Blog: http://davsclaus.com
> > Author of Camel in Action: http://www.manning.com/ibsen
>
>
>
> --
> Hiram Chirino
>
> Engineering | Red Hat, Inc.
>
> hchirino@redhat.com | fusesource.com | redhat.com
>
> skype: hiramchirino | twitter: @hiramchirino
>
> blog: Hiram Chirino's Bit Mojo
>
Re: [ISSUE] - bin/activemq.bat for Windows users
Posted by Hiram Chirino <hi...@hiramchirino.com>.
I kinda wish that both activemq unix script and activemq were simple
start activemq in the foreground scripts. Starting activemq as a
service/background is different on Windows and Linux/Unix so that
should done using other extra files etc.
For example we could have a bin/activemq-service script for unix that
handles doing the init.d unix stuff: 'activemq-service start'
'activemq-service stop' etc.
On Wed, Nov 13, 2013 at 8:57 AM, Claus Ibsen <cl...@gmail.com> wrote:
> Thanks
>
> So I assume it would be okay to remove the start from the
> activemq.bat, and have Windows users start the broker as we do unix.
>
>
>
> On Wed, Nov 13, 2013 at 1:47 PM, Gary Tully <ga...@gmail.com> wrote:
>> I think part of the reason is that only the unix scripts got an update
>> via https://issues.apache.org/jira/browse/AMQ-2453
>>
>> consistency is good and simpler from a doc perspective.
>>
>> On 13 November 2013 12:21, Claus Ibsen <cl...@gmail.com> wrote:
>>> Hi
>>>
>>> I was looking at ticket
>>> https://issues.apache.org/jira/browse/AMQ-3101
>>>
>>>
>>> I wonder why starting ActiveMQ on windows and unix is different, according to
>>> http://activemq.apache.org/version-5-getting-started.html#Version5GettingStarted-StartingActiveMQ
>>>
>>> On windows we tell users to do
>>> bin\activemq
>>>
>>> And on unix
>>> bin/activemq start
>>>
>>> eg on unix you pass in the start command.
>>>
>>> I would prefer that on Windows you should pass on the command as well such as
>>> bin\activemq start
>>>
>>> Otherwise you cannot get the help syntax by just using bin/activemq
>>>
>>> Usage: Main [--extdir <dir>] [task] [task-options] [task data]
>>>
>>> Tasks:
>>> browse - Display selected messages in a
>>> specified destination.
>>> bstat - Performs a predefined query that
>>> displays useful statistics regarding the specified broker
>>> create - Creates a runnable broker instance in
>>> the specified path.
>>> decrypt - Decrypts given text
>>> dstat - Performs a predefined query that
>>> displays useful tabular statistics regarding the specified destination
>>> type
>>> encrypt - Encrypts given text
>>> export - Exports a stopped brokers data files to
>>> an archive file
>>> list - Lists all available brokers in the
>>> specified JMX context
>>> purge - Delete selected destination's messages
>>> that matches the message selector
>>> query - Display selected broker component's
>>> attributes and statistics.
>>> start - Creates and starts a broker using a
>>> configuration file, or a broker URI.
>>> stop - Stops a running broker specified by the
>>> broker name.
>>>
>>>
>>> So I would if we should change this for Windows in the activemq.bat
>>> file, to not have the "start" command in there. So its consistent with
>>> unix.
>>>
>>> And also fixes AMQ-3101
>>>
>>>
>>> Anyone know any reason about the "start" in the bin/activemq.bat file?
>>>
>>>
>>>
>>>
>>>
>>> --
>>> Claus Ibsen
>>> -----------------
>>> Red Hat, Inc.
>>> Email: cibsen@redhat.com
>>> Twitter: davsclaus
>>> Blog: http://davsclaus.com
>>> Author of Camel in Action: http://www.manning.com/ibsen
>>
>>
>>
>> --
>> http://redhat.com
>> http://blog.garytully.com
>
>
>
> --
> Claus Ibsen
> -----------------
> Red Hat, Inc.
> Email: cibsen@redhat.com
> Twitter: davsclaus
> Blog: http://davsclaus.com
> Author of Camel in Action: http://www.manning.com/ibsen
--
Hiram Chirino
Engineering | Red Hat, Inc.
hchirino@redhat.com | fusesource.com | redhat.com
skype: hiramchirino | twitter: @hiramchirino
blog: Hiram Chirino's Bit Mojo
Re: [ISSUE] - bin/activemq.bat for Windows users
Posted by Claus Ibsen <cl...@gmail.com>.
Thanks
So I assume it would be okay to remove the start from the
activemq.bat, and have Windows users start the broker as we do unix.
On Wed, Nov 13, 2013 at 1:47 PM, Gary Tully <ga...@gmail.com> wrote:
> I think part of the reason is that only the unix scripts got an update
> via https://issues.apache.org/jira/browse/AMQ-2453
>
> consistency is good and simpler from a doc perspective.
>
> On 13 November 2013 12:21, Claus Ibsen <cl...@gmail.com> wrote:
>> Hi
>>
>> I was looking at ticket
>> https://issues.apache.org/jira/browse/AMQ-3101
>>
>>
>> I wonder why starting ActiveMQ on windows and unix is different, according to
>> http://activemq.apache.org/version-5-getting-started.html#Version5GettingStarted-StartingActiveMQ
>>
>> On windows we tell users to do
>> bin\activemq
>>
>> And on unix
>> bin/activemq start
>>
>> eg on unix you pass in the start command.
>>
>> I would prefer that on Windows you should pass on the command as well such as
>> bin\activemq start
>>
>> Otherwise you cannot get the help syntax by just using bin/activemq
>>
>> Usage: Main [--extdir <dir>] [task] [task-options] [task data]
>>
>> Tasks:
>> browse - Display selected messages in a
>> specified destination.
>> bstat - Performs a predefined query that
>> displays useful statistics regarding the specified broker
>> create - Creates a runnable broker instance in
>> the specified path.
>> decrypt - Decrypts given text
>> dstat - Performs a predefined query that
>> displays useful tabular statistics regarding the specified destination
>> type
>> encrypt - Encrypts given text
>> export - Exports a stopped brokers data files to
>> an archive file
>> list - Lists all available brokers in the
>> specified JMX context
>> purge - Delete selected destination's messages
>> that matches the message selector
>> query - Display selected broker component's
>> attributes and statistics.
>> start - Creates and starts a broker using a
>> configuration file, or a broker URI.
>> stop - Stops a running broker specified by the
>> broker name.
>>
>>
>> So I would if we should change this for Windows in the activemq.bat
>> file, to not have the "start" command in there. So its consistent with
>> unix.
>>
>> And also fixes AMQ-3101
>>
>>
>> Anyone know any reason about the "start" in the bin/activemq.bat file?
>>
>>
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> Red Hat, Inc.
>> Email: cibsen@redhat.com
>> Twitter: davsclaus
>> Blog: http://davsclaus.com
>> Author of Camel in Action: http://www.manning.com/ibsen
>
>
>
> --
> http://redhat.com
> http://blog.garytully.com
--
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cibsen@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
Re: [ISSUE] - bin/activemq.bat for Windows users
Posted by Gary Tully <ga...@gmail.com>.
I think part of the reason is that only the unix scripts got an update
via https://issues.apache.org/jira/browse/AMQ-2453
consistency is good and simpler from a doc perspective.
On 13 November 2013 12:21, Claus Ibsen <cl...@gmail.com> wrote:
> Hi
>
> I was looking at ticket
> https://issues.apache.org/jira/browse/AMQ-3101
>
>
> I wonder why starting ActiveMQ on windows and unix is different, according to
> http://activemq.apache.org/version-5-getting-started.html#Version5GettingStarted-StartingActiveMQ
>
> On windows we tell users to do
> bin\activemq
>
> And on unix
> bin/activemq start
>
> eg on unix you pass in the start command.
>
> I would prefer that on Windows you should pass on the command as well such as
> bin\activemq start
>
> Otherwise you cannot get the help syntax by just using bin/activemq
>
> Usage: Main [--extdir <dir>] [task] [task-options] [task data]
>
> Tasks:
> browse - Display selected messages in a
> specified destination.
> bstat - Performs a predefined query that
> displays useful statistics regarding the specified broker
> create - Creates a runnable broker instance in
> the specified path.
> decrypt - Decrypts given text
> dstat - Performs a predefined query that
> displays useful tabular statistics regarding the specified destination
> type
> encrypt - Encrypts given text
> export - Exports a stopped brokers data files to
> an archive file
> list - Lists all available brokers in the
> specified JMX context
> purge - Delete selected destination's messages
> that matches the message selector
> query - Display selected broker component's
> attributes and statistics.
> start - Creates and starts a broker using a
> configuration file, or a broker URI.
> stop - Stops a running broker specified by the
> broker name.
>
>
> So I would if we should change this for Windows in the activemq.bat
> file, to not have the "start" command in there. So its consistent with
> unix.
>
> And also fixes AMQ-3101
>
>
> Anyone know any reason about the "start" in the bin/activemq.bat file?
>
>
>
>
>
> --
> Claus Ibsen
> -----------------
> Red Hat, Inc.
> Email: cibsen@redhat.com
> Twitter: davsclaus
> Blog: http://davsclaus.com
> Author of Camel in Action: http://www.manning.com/ibsen
--
http://redhat.com
http://blog.garytully.com