You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by Hiram Chirino <hi...@hiramchirino.com> on 2011/04/21 21:00:11 UTC
Re: Apollo startup script
Hi Lionel,
I think it's good idea. I think that the 'apollo create' command
should generate a bin/apollo-service script that does what your
suggesting.
Also I think we should not force folks to use the java service
wrapper, while it's handy, there are several other watchdog processes
available (like monit, and launchd) which could take care of
restarting ActiveMQ on failure so, if anything perhaps we should
optionally generate a second service script that uses the jsw.
Regards,
Hiram
FuseSource
Web: http://fusesource.com/
Connect at CamelOne May 24-26
The Open Source Integration Conference
On Thu, Apr 21, 2011 at 1:42 AM, Lionel Cons <li...@cern.ch> wrote:
> Hiram,
>
> Now that Apollo is getting more mature (beta), it's probably the right
> time to improve its integration with the operating system.
>
> It would be good to have a solid init script to be put in /etc/init.d.
> Here are the features that we would like to see:
> - use a pid file
> - handle the change of user (since the init script will run as root)
> - handle status and stop even if the console (REST interface) is disabled
>
> Also, we currently use the Java wrapper with ActiveMQ 5.x. Is this
> something you would recommend for Apollo? If yes, it should be
> integrated with the init script...
>
> Cheers,
>
> Lionel
>
Re: Clustering brokers
Posted by Adam Kaminiecki <ad...@dgt.com.pl>.
Hi,
I would like to repeat a question if anyone can give me a hint anything
on the configuration, AMQ 38 servers so that everyone had a connection
with each and that Consumers can communicate with each other.
Has anyone ever tested such a large number of servers?
Is a good setup to enter the addresses of each broker or some other
schema the stars may be, or else? What is needed is the high-availability.
I will be grateful for any hint.
Best regards,
Adam
W dniu 2011-05-04 11:50, Adam Kaminiecki pisze:
> Hi,
>
> I have situation where I need to bind 38 brokers.
> Brokers are grouped in 2 by static connection.
> There is 19 sites.
>
> My question is how to bind them properly ??
> All-to-all??
>
> Thanks for any reply.
>
>
>
> Best regards,
> Adam
Clustering brokers
Posted by Adam Kaminiecki <ad...@dgt.com.pl>.
Hi,
I have situation where I need to bind 38 brokers.
Brokers are grouped in 2 by static connection.
There is 19 sites.
My question is how to bind them properly ??
All-to-all??
Thanks for any reply.
Best regards,
Adam
Re: Apollo startup script
Posted by Hiram Chirino <hi...@hiramchirino.com>.
Sounds reasonable.. will try to add that in today.
Regards,
Hiram
FuseSource
Web: http://fusesource.com/
Connect at CamelOne May 24-26
The Open Source Integration Conference
On Mon, May 2, 2011 at 9:23 AM, Lionel Cons <li...@cern.ch> wrote:
> Hiram Chirino writes:
> > I've just finished implementing that request. The freshly deployed
> > snapshot will now create an apollo-broker-service script which can be
> > linked to your system's /etc/init.d directory.
>
> Hiram,
>
> This looks fine and the symlink trick allows to easily have several
> instances of Apollo running on the same box.
>
> However, for apollo-broker-service like for apollo-broker, I do not
> really like to have to edit the scripts to configure some parameters
> like APOLLO_USER or APOLLO_OPTS.
>
> I would much prefer having a separate file that contains these settings.
> For instance a file named ${APOLLO_BASE}/etc/apollo.conf that you could
> source from apollo-broker-service and apollo-broker. What is your
> opinion on this?
>
> Cheers,
>
> Lionel
>
Re: Apollo startup script
Posted by Lionel Cons <li...@cern.ch>.
Hiram Chirino writes:
> I've just finished implementing that request. The freshly deployed
> snapshot will now create an apollo-broker-service script which can be
> linked to your system's /etc/init.d directory.
Hiram,
This looks fine and the symlink trick allows to easily have several
instances of Apollo running on the same box.
However, for apollo-broker-service like for apollo-broker, I do not
really like to have to edit the scripts to configure some parameters
like APOLLO_USER or APOLLO_OPTS.
I would much prefer having a separate file that contains these settings.
For instance a file named ${APOLLO_BASE}/etc/apollo.conf that you could
source from apollo-broker-service and apollo-broker. What is your
opinion on this?
Cheers,
Lionel
Re: Apollo startup script
Posted by Hiram Chirino <hi...@hiramchirino.com>.
Hi Lionel,
I've just finished implementing that request. The freshly deployed
snapshot will now create an apollo-broker-service script which can be
linked to your system's /etc/init.d directory.
Regards,
Hiram
FuseSource
Web: http://fusesource.com/
Connect at CamelOne May 24-26
The Open Source Integration Conference
On Thu, Apr 21, 2011 at 3:00 PM, Hiram Chirino <hi...@hiramchirino.com> wrote:
> Hi Lionel,
>
> I think it's good idea. I think that the 'apollo create' command
> should generate a bin/apollo-service script that does what your
> suggesting.
> Also I think we should not force folks to use the java service
> wrapper, while it's handy, there are several other watchdog processes
> available (like monit, and launchd) which could take care of
> restarting ActiveMQ on failure so, if anything perhaps we should
> optionally generate a second service script that uses the jsw.
>
>
> Regards,
> Hiram
>
> FuseSource
> Web: http://fusesource.com/
>
> Connect at CamelOne May 24-26
> The Open Source Integration Conference
>
>
>
> On Thu, Apr 21, 2011 at 1:42 AM, Lionel Cons <li...@cern.ch> wrote:
>> Hiram,
>>
>> Now that Apollo is getting more mature (beta), it's probably the right
>> time to improve its integration with the operating system.
>>
>> It would be good to have a solid init script to be put in /etc/init.d.
>> Here are the features that we would like to see:
>> - use a pid file
>> - handle the change of user (since the init script will run as root)
>> - handle status and stop even if the console (REST interface) is disabled
>>
>> Also, we currently use the Java wrapper with ActiveMQ 5.x. Is this
>> something you would recommend for Apollo? If yes, it should be
>> integrated with the init script...
>>
>> Cheers,
>>
>> Lionel
>>
>