qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Keith W <keith.w...@gmail.com>
Subject Re: [Qpid Broker - 6.0.4] Junit testable?
Date Fri, 17 Mar 2017 14:19:45 GMT
Hi Adel

There is a recognition that the embed-ability of the Qpid Broker for
Java is not what it should be.   We have been making incremental
improvements with each major release but things still aren't ideal

For the dynamically bound port number, QPID-7597 changes the Broker so
that it is available from the model:  Port#getBoundPort().  This will
be part of the next major release.  As things stand in 6.0,
unfortunately, there is no clean way to discover the actual bound
port.  The best you could do it scrape the log, or intercept the event
logging so pull out the bound port number for AMQP and HTTP, neither
of which are clean I know.  The classes to look at are:

For the creation of queues/exchanges, I suggest using the REST API to
create the objects.  This is a public API and will be maintained going
forwards.  There is REST API summary documentation in the docbook.


There is some online documentation for the REST API available from the
Web Management Console (API link, menu at top right).  Firebug within
Firefox has a neat feature to give you a cURL command line for network
requests that have been sent by the browser.  You can use this as a
quick way to get a curl command line for an action corresponding you
have just performed interactively.  The API is pretty simple.

The next major release (v7.0) will include support for AMQP
Management.  This will allow you to fully manage the Broker from an
AMQP messaging connection. You will be able to use this to fully
configure the Broker from say, a JMS connection.  I expect this will
become our recommendation.

Hope this helps.

On 17 March 2017 at 12:41, Adel Boutros <Adelboutros@live.com> wrote:
> Hello Robbie,
> Can you please provide a simple example?
> Regards,
> Adel
> ________________________________
> From: Robbie Gemmell <robbie.gemmell@gmail.com>
> Sent: Friday, March 17, 2017 12:57:59 PM
> To: users@qpid.apache.org
> Subject: Re: [Qpid Broker - 6.0.4] Junit testable?
> On 16 March 2017 at 18:01, Adel Boutros <Adelboutros@live.com> wrote:
>> Hello,
>> As we are currently deploying a messaging solution based on the Java Broker, we have
tried to start a broker from a Junit test and it is not very straightforward as the configuration
part is a bit difficult. Of course here we are talking about Component Based Testing and Integration
Testing to allow clients to test their code before deploying it.
>> Some of the pain points when using org.apache.qpid.server.Broker:
>>   *   If port 0 is specified, I have no way to get the actual port allocated
>>   *   I need a json config file to configure queues, topics (There is no Java Api
for it directly)
> It might not be as easy as would be desired, but the brokers own test
> suite creates queues at runtime (using its HTTP or AMQP management
> support) and as far as I know also starts brokers on 'port 0' these
> days. Perhaps something to look at.
>> Another team had tested HornetQ[1] which seems to be more adapted to embedded testing.
However as our production broker will be Qpid Java Broker, we would like our tests to be as
close as possible to production.
>> So my questions are:
>> * Is there currently a way to use an embedded Java Broker easily configurable in
a Junit test?
>> * If not, what would be required to provide such easibility?
>> [1]: http://docs.jboss.org/hornetq/2.2.5.Final/user-manual/en/html/embedding-hornetq.html
>> Regards,
>> Adel
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org

To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org

View raw message