You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by Enrico Olivelli <eo...@gmail.com> on 2013/03/15 17:04:44 UTC
Embedding java broker and log4j configuration
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
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: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
Re: Embedding java broker and log4j configuration
Posted by Enrico Olivelli <eo...@gmail.com>.
Thank you very much !!!
I will wait for the 0.22 release at the end of April
Enrico
Il 18/03/2013 01:42, Robbie Gemmell ha scritto:
> Change made on trunk:
>
> https://issues.apache.org/jira/browse/QPID-4655
> http://svn.apache.org/viewvc?view=revision&revision=1457612
>
> Robbie
>
> On 15 March 2013 21:17, Robbie Gemmell <ro...@gmail.com> wrote:
>
>> 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 <eo...@gmail.com> 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: dev-unsubscribe@qpid.apache.**org<de...@qpid.apache.org>
>>> For additional commands, e-mail: dev-help@qpid.apache.org
>>>
>>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
Re: Embedding java broker and log4j configuration
Posted by Robbie Gemmell <ro...@gmail.com>.
Change made on trunk:
https://issues.apache.org/jira/browse/QPID-4655
http://svn.apache.org/viewvc?view=revision&revision=1457612
Robbie
On 15 March 2013 21:17, Robbie Gemmell <ro...@gmail.com> wrote:
> 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 <eo...@gmail.com> 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: dev-unsubscribe@qpid.apache.**org<de...@qpid.apache.org>
>> For additional commands, e-mail: dev-help@qpid.apache.org
>>
>>
>
Re: Embedding java broker and log4j configuration
Posted by Robbie Gemmell <ro...@gmail.com>.
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 <eo...@gmail.com> 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: dev-unsubscribe@qpid.apache.**org<de...@qpid.apache.org>
> For additional commands, e-mail: dev-help@qpid.apache.org
>
>