Hi Enrico,

Adding a method to BrokerOptions to allow skipping the logging
configuration (and registration of the associated JMX
LoggingManagementMBean) when embedding the broker seems reasonable enough,
I'll look into doing this in the next few days.

There wont be another release before the end of March, the next release
(0.22) is currently being aimed for around the end of April. If you are
looking to run something before then, you could build a modified 0.20
broker using the 'full source release' on the download page or pick up one
of the nightly builds from trunk.

Robbie

On 15 March 2013 16:04, Enrico Olivelli <[email protected]> wrote:

> Hi,
> I'm going to use your Java Broker "embedded" in my platform (
> http://www.magnews.it).
> MagNews is a plaftorm for building email marketing solutions, we use JMS
> to spread bacxkground jobs thru the cluster.
>
> We were using ActiveMQ but due to its limits in HA configurations we are
> migrating to QPid, we use  essentially JMS so the port has been simple.
>
> I see at
> http://svn.apache.org/viewvc/**qpid/trunk/qpid/java/broker/**
> src/main/java/org/apache/qpid/**server/Broker.java?view=markup<http://svn.apache.org/viewvc/qpid/trunk/qpid/java/broker/src/main/java/org/apache/qpid/server/Broker.java?view=markup>
> that your broker wants to "configure" logging at startup in its way, but
> we want to configure logging "in our way", before broker startup and with
> log4j API (not config files)
>
> I would like to have a BrokerOption in order to skip the call of
> "Borker.configureLogging" method (and any other Qpid programmating effort
> to reconfigure log4j)
>
> We are going online with the release of our platform at the end of March,
> are you going to release another versione of QPid java broker by that date ?
>
> Thanks in advance
>
> I hope that QPid will become soon my preferred Java JMS Broker
>
>
> Enrico
>
>
>
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: 
> [email protected].**org<[email protected]>
> For additional commands, e-mail: [email protected]
>
>

Reply via email to