Re: [VOTE] Release Qpid for Java 6.1.2 (RC1)

2017-03-17 Thread Robbie Gemmell
On 15 March 2017 at 16:51, Oleksandr Rudyy wrote: > Hi everyone, > > The release candidate version 6.1.2 of Qpid for Java is built and > available from dev staging repos. > Please, test it and vote accordingly. > > The list of changes can be found in Jira: > https://issues.apache.org/jira/issues/?

[Proton C++ 0.16.0] Reconnect and reconnect timer

2017-03-17 Thread Rabih M
Hello, Bit of context: I am trying to implement a connection retry mechanism using proton. A bit similar to the failover Url in JMS... I discovered that we can set "reconnect" option in the connection_options.reconnect(reconnect_timer). There are no clear documentation, how does this option beha

Re: [VOTE] Release Qpid for Java 6.1.2 (RC1)

2017-03-17 Thread Keith W
+1. My testing was: 1) Verified the md5/sha checksums on all distribution artefacts 2) Verified signatures on all all distribution artefacts 3) Ran apache RAT and built/ran test profile mms 0-10 from source bundle 4) Ran hello world against staged maven artefacts against broker from binary distri

Re: [HEADS UP] qpid-cpp 1.37.0

2017-03-17 Thread Robbie Gemmell
I'm probably not going to get this started this week after all, https://issues.apache.org/jira/browse/QPID-7713 was noticed in some pre-testing, and I think it would be good to get some review on https://issues.apache.org/jira/browse/QPID-7702 and decide whether its ok and/or needs to be included.

Re: [Qpid Broker - 6.0.4] Junit testable?

2017-03-17 Thread Adel Boutros
Indeed, most users will most probably inject a JMS connection using Spring annotations. So testing it against an easy to embedd broker would be highly appreciated because Spring already provides a lot of helpers in testing. The problem is that each broker respects the specifications the way it

Re: [Qpid Broker - 6.0.4] Junit testable?

2017-03-17 Thread Dan Langford
You already mentioned HornetQ I would also toss out there ActiveMQ as one that is fantastic at embedding. In my Java projects I code to JMS and in Unit tests I mock out JMS apis because I am just testing MY code. Sometimes it's just easier or a more thorough test to include a broker especially sinc

Re: [Qpid Broker - 6.0.4] Junit testable?

2017-03-17 Thread Keith W
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 state. For the dynamically bound port number, QPID-7597 changes the Broker so that it is

Re: [Qpid Broker - 6.0.4] Junit testable?

2017-03-17 Thread Rob Godfrey
As Robbie says, all the Qpid Java Broker system tests start up a broker and configure it... There is a fair bit of baggage that comes along with the system tests though to enable running all the different profiles, etc... so extracting a "simple" example may be a little difficult. Most of the hea

Re: Can anyone recall what changed to remove the need to run ldconfig after make install on later qpid versions?

2017-03-17 Thread Fraser Adams
Just an update, your guess was spot on Robbie - sorting the RPATH made it happy. Thanks again! Frase On 17/03/17 11:47, Fraser Adams wrote: Thanks Robbie, I'll have a play. On 17/03/17 11:15, Robbie Gemmell wrote: Total guess, but with a compare of tags I noticed: https://github.com/apach

Re: [Qpid Broker - 6.0.4] Junit testable?

2017-03-17 Thread Adel Boutros
Hello Robbie, Can you please provide a simple example? Regards, Adel From: Robbie Gemmell 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 wrote: > Hell

Re: [Qpid Broker - 6.0.4] Junit testable?

2017-03-17 Thread Robbie Gemmell
On 16 March 2017 at 18:01, Adel Boutros 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 a

Re: Can anyone recall what changed to remove the need to run ldconfig after make install on later qpid versions?

2017-03-17 Thread Fraser Adams
Thanks Robbie, I'll have a play. On 17/03/17 11:15, Robbie Gemmell wrote: Total guess, but with a compare of tags I noticed: https://github.com/apache/qpid/commit/8397804122e452ec338f38b53652eeb5bed14b1d#diff-e7b9c71b9cfb2d6fbd9eaecc19612879R189 On 17 March 2017 at 10:58, Fraser Adams wrote:

Re: Can anyone recall what changed to remove the need to run ldconfig after make install on later qpid versions?

2017-03-17 Thread Robbie Gemmell
Total guess, but with a compare of tags I noticed: https://github.com/apache/qpid/commit/8397804122e452ec338f38b53652eeb5bed14b1d#diff-e7b9c71b9cfb2d6fbd9eaecc19612879R189 On 17 March 2017 at 10:58, Fraser Adams wrote: > I'm doing a bit of "archeology" on some older qpid versions and one thing >

Can anyone recall what changed to remove the need to run ldconfig after make install on later qpid versions?

2017-03-17 Thread Fraser Adams
I'm doing a bit of "archeology" on some older qpid versions and one thing I've noticed is that for versions up to and including 0.20 I need to run ldconfig after make install otherwise I get /usr/local/sbin/qpidd: error while loading shared libraries: libqpidbroker.so.2.0.0: cannot open shared