You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by Clebert Suconic <cl...@gmail.com> on 2015/05/05 17:33:20 UTC
Artemis options
I have added data options to the runtime CLI, moved it from artemis-tools,
Now users will be able to do:
./artemis data print
and print all the data on the journals and paging (the option will
open the journals and print all the contents)
To export the data
./artemis data exp
you can use ./artemis help data print (I - at the end of the email)
I tried to be as much user friendly as possible... if you could play
with it... it would help me to make sure it's really user friendly :)
I:
$ ./artemis help data print
NAME
artemis data print - Print data records information (WARNING: don't use
while a production server is running)
SYNOPSIS
artemis data print [--bindings <binding>] [--broker <brokerConfig>]
[--journal <journal>] [--large-messages <largeMessges>]
[--paging <paging>] [--] [<configuration>]
OPTIONS
--bindings <binding>
The folder used for bindings (default from broker.xml)
--broker <brokerConfig>
This would override the broker configuration from the bootstrap
--journal <journal>
The folder used for messages journal (default from broker.xml)
--large-messages <largeMessges>
The folder used for large-messages (default from broker.xml)
--paging <paging>
The folder used for paging (default from broker.xml)
--
This option can be used to separate command-line options from the
list of argument, (useful when arguments might be mistaken for
command-line options
<configuration>
Broker Configuration URI, default
'xml:${ARTEMIS_INSTANCE}/etc/bootstrap.xml'
Re: Artemis options
Posted by Clebert Suconic <cl...@gmail.com>.
good point.. will do it!
On Tue, May 5, 2015 at 5:18 PM, Hiram Chirino <hi...@hiramchirino.com> wrote:
> perhaps you should print out a nicer error messages saying they should
> use the --bindings / --journal options :)
>
> On Tue, May 5, 2015 at 5:14 PM, Clebert Suconic
> <cl...@gmail.com> wrote:
>> I did it like that but I always analyze user's data without a running
>> instance. So I would be able to do something like --
>>
>> ./artemis data print --bindings /users-data --journal /users-data
>>
>>
>>
>>
>> Maybe I should ignore that error and just print an empty report if no
>> folders are available?
>>
>>
>>
>>
>>
>> On Tue, May 5, 2015 at 4:35 PM, Hiram Chirino <hi...@hiramchirino.com> wrote:
>>> Nice!
>>>
>>> But perhaps the 'data' command should only be enabled in the
>>> ${ARTEMIS_INSTANCE}/bin/artemis case. When used with
>>> ${ARTEMIS_HOME}/bin/artemis it fails since it can't find the data
>>> files.
>>>
>>> On Tue, May 5, 2015 at 11:33 AM, Clebert Suconic
>>> <cl...@gmail.com> wrote:
>>>> I have added data options to the runtime CLI, moved it from artemis-tools,
>>>>
>>>> Now users will be able to do:
>>>>
>>>>
>>>> ./artemis data print
>>>>
>>>>
>>>> and print all the data on the journals and paging (the option will
>>>> open the journals and print all the contents)
>>>>
>>>>
>>>> To export the data
>>>>
>>>> ./artemis data exp
>>>>
>>>>
>>>>
>>>>
>>>> you can use ./artemis help data print (I - at the end of the email)
>>>>
>>>>
>>>>
>>>>
>>>> I tried to be as much user friendly as possible... if you could play
>>>> with it... it would help me to make sure it's really user friendly :)
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> I:
>>>>
>>>> $ ./artemis help data print
>>>>
>>>> NAME
>>>>
>>>> artemis data print - Print data records information (WARNING: don't use
>>>>
>>>> while a production server is running)
>>>>
>>>>
>>>> SYNOPSIS
>>>>
>>>> artemis data print [--bindings <binding>] [--broker <brokerConfig>]
>>>>
>>>> [--journal <journal>] [--large-messages <largeMessges>]
>>>>
>>>> [--paging <paging>] [--] [<configuration>]
>>>>
>>>>
>>>> OPTIONS
>>>>
>>>> --bindings <binding>
>>>>
>>>> The folder used for bindings (default from broker.xml)
>>>>
>>>>
>>>> --broker <brokerConfig>
>>>>
>>>> This would override the broker configuration from the bootstrap
>>>>
>>>>
>>>> --journal <journal>
>>>>
>>>> The folder used for messages journal (default from broker.xml)
>>>>
>>>>
>>>> --large-messages <largeMessges>
>>>>
>>>> The folder used for large-messages (default from broker.xml)
>>>>
>>>>
>>>> --paging <paging>
>>>>
>>>> The folder used for paging (default from broker.xml)
>>>>
>>>>
>>>> --
>>>>
>>>> This option can be used to separate command-line options from the
>>>>
>>>> list of argument, (useful when arguments might be mistaken for
>>>>
>>>> command-line options
>>>>
>>>>
>>>> <configuration>
>>>>
>>>> Broker Configuration URI, default
>>>>
>>>> 'xml:${ARTEMIS_INSTANCE}/etc/bootstrap.xml'
>>>
>>>
>>>
>>> --
>>> Hiram Chirino
>>> Engineering | Red Hat, Inc.
>>> hchirino@redhat.com | fusesource.com | redhat.com
>>> skype: hiramchirino | twitter: @hiramchirino
>>
>>
>>
>> --
>> Clebert Suconic
>> http://community.jboss.org/people/clebert.suconic@jboss.com
>> http://clebertsuconic.blogspot.com
>
>
>
> --
> Hiram Chirino
> Engineering | Red Hat, Inc.
> hchirino@redhat.com | fusesource.com | redhat.com
> skype: hiramchirino | twitter: @hiramchirino
--
Clebert Suconic
http://community.jboss.org/people/clebert.suconic@jboss.com
http://clebertsuconic.blogspot.com
Re: Artemis options
Posted by Hiram Chirino <hi...@hiramchirino.com>.
perhaps you should print out a nicer error messages saying they should
use the --bindings / --journal options :)
On Tue, May 5, 2015 at 5:14 PM, Clebert Suconic
<cl...@gmail.com> wrote:
> I did it like that but I always analyze user's data without a running
> instance. So I would be able to do something like --
>
> ./artemis data print --bindings /users-data --journal /users-data
>
>
>
>
> Maybe I should ignore that error and just print an empty report if no
> folders are available?
>
>
>
>
>
> On Tue, May 5, 2015 at 4:35 PM, Hiram Chirino <hi...@hiramchirino.com> wrote:
>> Nice!
>>
>> But perhaps the 'data' command should only be enabled in the
>> ${ARTEMIS_INSTANCE}/bin/artemis case. When used with
>> ${ARTEMIS_HOME}/bin/artemis it fails since it can't find the data
>> files.
>>
>> On Tue, May 5, 2015 at 11:33 AM, Clebert Suconic
>> <cl...@gmail.com> wrote:
>>> I have added data options to the runtime CLI, moved it from artemis-tools,
>>>
>>> Now users will be able to do:
>>>
>>>
>>> ./artemis data print
>>>
>>>
>>> and print all the data on the journals and paging (the option will
>>> open the journals and print all the contents)
>>>
>>>
>>> To export the data
>>>
>>> ./artemis data exp
>>>
>>>
>>>
>>>
>>> you can use ./artemis help data print (I - at the end of the email)
>>>
>>>
>>>
>>>
>>> I tried to be as much user friendly as possible... if you could play
>>> with it... it would help me to make sure it's really user friendly :)
>>>
>>>
>>>
>>>
>>>
>>> I:
>>>
>>> $ ./artemis help data print
>>>
>>> NAME
>>>
>>> artemis data print - Print data records information (WARNING: don't use
>>>
>>> while a production server is running)
>>>
>>>
>>> SYNOPSIS
>>>
>>> artemis data print [--bindings <binding>] [--broker <brokerConfig>]
>>>
>>> [--journal <journal>] [--large-messages <largeMessges>]
>>>
>>> [--paging <paging>] [--] [<configuration>]
>>>
>>>
>>> OPTIONS
>>>
>>> --bindings <binding>
>>>
>>> The folder used for bindings (default from broker.xml)
>>>
>>>
>>> --broker <brokerConfig>
>>>
>>> This would override the broker configuration from the bootstrap
>>>
>>>
>>> --journal <journal>
>>>
>>> The folder used for messages journal (default from broker.xml)
>>>
>>>
>>> --large-messages <largeMessges>
>>>
>>> The folder used for large-messages (default from broker.xml)
>>>
>>>
>>> --paging <paging>
>>>
>>> The folder used for paging (default from broker.xml)
>>>
>>>
>>> --
>>>
>>> This option can be used to separate command-line options from the
>>>
>>> list of argument, (useful when arguments might be mistaken for
>>>
>>> command-line options
>>>
>>>
>>> <configuration>
>>>
>>> Broker Configuration URI, default
>>>
>>> 'xml:${ARTEMIS_INSTANCE}/etc/bootstrap.xml'
>>
>>
>>
>> --
>> Hiram Chirino
>> Engineering | Red Hat, Inc.
>> hchirino@redhat.com | fusesource.com | redhat.com
>> skype: hiramchirino | twitter: @hiramchirino
>
>
>
> --
> Clebert Suconic
> http://community.jboss.org/people/clebert.suconic@jboss.com
> http://clebertsuconic.blogspot.com
--
Hiram Chirino
Engineering | Red Hat, Inc.
hchirino@redhat.com | fusesource.com | redhat.com
skype: hiramchirino | twitter: @hiramchirino
Re: Artemis options
Posted by Clebert Suconic <cl...@gmail.com>.
I did it like that but I always analyze user's data without a running
instance. So I would be able to do something like --
./artemis data print --bindings /users-data --journal /users-data
Maybe I should ignore that error and just print an empty report if no
folders are available?
On Tue, May 5, 2015 at 4:35 PM, Hiram Chirino <hi...@hiramchirino.com> wrote:
> Nice!
>
> But perhaps the 'data' command should only be enabled in the
> ${ARTEMIS_INSTANCE}/bin/artemis case. When used with
> ${ARTEMIS_HOME}/bin/artemis it fails since it can't find the data
> files.
>
> On Tue, May 5, 2015 at 11:33 AM, Clebert Suconic
> <cl...@gmail.com> wrote:
>> I have added data options to the runtime CLI, moved it from artemis-tools,
>>
>> Now users will be able to do:
>>
>>
>> ./artemis data print
>>
>>
>> and print all the data on the journals and paging (the option will
>> open the journals and print all the contents)
>>
>>
>> To export the data
>>
>> ./artemis data exp
>>
>>
>>
>>
>> you can use ./artemis help data print (I - at the end of the email)
>>
>>
>>
>>
>> I tried to be as much user friendly as possible... if you could play
>> with it... it would help me to make sure it's really user friendly :)
>>
>>
>>
>>
>>
>> I:
>>
>> $ ./artemis help data print
>>
>> NAME
>>
>> artemis data print - Print data records information (WARNING: don't use
>>
>> while a production server is running)
>>
>>
>> SYNOPSIS
>>
>> artemis data print [--bindings <binding>] [--broker <brokerConfig>]
>>
>> [--journal <journal>] [--large-messages <largeMessges>]
>>
>> [--paging <paging>] [--] [<configuration>]
>>
>>
>> OPTIONS
>>
>> --bindings <binding>
>>
>> The folder used for bindings (default from broker.xml)
>>
>>
>> --broker <brokerConfig>
>>
>> This would override the broker configuration from the bootstrap
>>
>>
>> --journal <journal>
>>
>> The folder used for messages journal (default from broker.xml)
>>
>>
>> --large-messages <largeMessges>
>>
>> The folder used for large-messages (default from broker.xml)
>>
>>
>> --paging <paging>
>>
>> The folder used for paging (default from broker.xml)
>>
>>
>> --
>>
>> This option can be used to separate command-line options from the
>>
>> list of argument, (useful when arguments might be mistaken for
>>
>> command-line options
>>
>>
>> <configuration>
>>
>> Broker Configuration URI, default
>>
>> 'xml:${ARTEMIS_INSTANCE}/etc/bootstrap.xml'
>
>
>
> --
> Hiram Chirino
> Engineering | Red Hat, Inc.
> hchirino@redhat.com | fusesource.com | redhat.com
> skype: hiramchirino | twitter: @hiramchirino
--
Clebert Suconic
http://community.jboss.org/people/clebert.suconic@jboss.com
http://clebertsuconic.blogspot.com
Re: Artemis options
Posted by Hiram Chirino <hi...@hiramchirino.com>.
Nice!
But perhaps the 'data' command should only be enabled in the
${ARTEMIS_INSTANCE}/bin/artemis case. When used with
${ARTEMIS_HOME}/bin/artemis it fails since it can't find the data
files.
On Tue, May 5, 2015 at 11:33 AM, Clebert Suconic
<cl...@gmail.com> wrote:
> I have added data options to the runtime CLI, moved it from artemis-tools,
>
> Now users will be able to do:
>
>
> ./artemis data print
>
>
> and print all the data on the journals and paging (the option will
> open the journals and print all the contents)
>
>
> To export the data
>
> ./artemis data exp
>
>
>
>
> you can use ./artemis help data print (I - at the end of the email)
>
>
>
>
> I tried to be as much user friendly as possible... if you could play
> with it... it would help me to make sure it's really user friendly :)
>
>
>
>
>
> I:
>
> $ ./artemis help data print
>
> NAME
>
> artemis data print - Print data records information (WARNING: don't use
>
> while a production server is running)
>
>
> SYNOPSIS
>
> artemis data print [--bindings <binding>] [--broker <brokerConfig>]
>
> [--journal <journal>] [--large-messages <largeMessges>]
>
> [--paging <paging>] [--] [<configuration>]
>
>
> OPTIONS
>
> --bindings <binding>
>
> The folder used for bindings (default from broker.xml)
>
>
> --broker <brokerConfig>
>
> This would override the broker configuration from the bootstrap
>
>
> --journal <journal>
>
> The folder used for messages journal (default from broker.xml)
>
>
> --large-messages <largeMessges>
>
> The folder used for large-messages (default from broker.xml)
>
>
> --paging <paging>
>
> The folder used for paging (default from broker.xml)
>
>
> --
>
> This option can be used to separate command-line options from the
>
> list of argument, (useful when arguments might be mistaken for
>
> command-line options
>
>
> <configuration>
>
> Broker Configuration URI, default
>
> 'xml:${ARTEMIS_INSTANCE}/etc/bootstrap.xml'
--
Hiram Chirino
Engineering | Red Hat, Inc.
hchirino@redhat.com | fusesource.com | redhat.com
skype: hiramchirino | twitter: @hiramchirino