Re: [VOTE] Release Qpid JMS client 0.20.0

+1 * Validated the signatures and sums * Reviewed the License and Notice files * Reviewed the documentation file * Built from source and ran the tests * Used the staged artifacts in the ActiveMQ AMQP test suite * Ran the provided examples against an ActiveMQ broker On 01/16/2017 01:38 PM,

RE: Slow-starting queue visibility and handling it

Doh. It turned out we had a mismatched queue name. Sorry ...! And thanks. Jeff From: Gordon Sim [g...@redhat.com] Sent: Monday, January 16, 2017 1:55 AM To: users@qpid.apache.org Subject: Re: Slow-starting queue visibility and handling it On 14/01/17

Re: [VOTE] Release Qpid JMS client 0.20.0

On 01/16/2017 02:29 PM, Adel Boutros wrote: Hello Robbie, Out of curiosity, can you please explain why the release is 0.20.0 and not 0.12.0? When will an official 1.0.0 be out? The main reason for the bump is that this version now implements the JMS 2.0 API and is therefore a larger shift

Re: [VOTE] Release Qpid JMS client 0.20.0

Hello Robbie, Out of curiosity, can you please explain why the release is 0.20.0 and not 0.12.0? When will an official 1.0.0 be out? Regards, Adel From: Robbie Gemmell Sent: Monday, January 16, 2017 7:38:04 PM To:

Re: [Proton 0.16.0] Compiling Proton Python bindings on Solaris is failing in the python tests

Adel - I've hit this error before and it was due to a mix up with my library paths. When I got that error my 2.7 python env was trying to load the .so built using the python3 library. Can you run strace on the test to see exactly which _cproton.so is being loaded? -K - Original Message

[VOTE] Release Qpid JMS client 0.20.0

Hi folks, I have put together a spin for a 0.20.0 Qpid JMS client release, please test it and vote accordingly. The source and binary archives can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/jms/0.20.0-rc1/ Those files and the other maven artifacts are also staged for now at:

Re: [Proton 0.16.0] Compiling Proton Python bindings on Solaris is failing in the python tests

I just compiled SWIG 1.3.40 on Solaris and tried but still got the same error :( From: Adel Boutros Sent: Monday, January 16, 2017 7:00:41 PM To: users@qpid.apache.org Subject: [Proton 0.16.0] Compiling Proton Python bindings on Solaris is

[Proton 0.16.0] Compiling Proton Python bindings on Solaris is failing in the python tests

Hello, I am actually trying to activate the python bindings in Proton so I can compile Dispatch Router on Solaris. However, the python unit tests of Proton are failing. Cmake Configuration Found PythonInterp: /bin/python (found version "2.7.9") Found SWIG:

Re: [Dispatch Router] Dispatch router not able to use Proton 0.16.0

Thank you Ganesh! Regards, Adel From: Ganesh Murthy Sent: Monday, January 16, 2017 3:37:08 PM To: users@qpid.apache.org Subject: Re: [Dispatch Router] Dispatch router not able to use Proton 0.16.0 Hi Adel, This problem has been fixed

Re: [Dispatch Router] Dispatch router not able to use Proton 0.16.0

Hi Adel, This problem has been fixed on the master branch via https://issues.apache.org/jira/browse/DISPATCH-569 It will be available in the 0.8.0 release of the Dispatch Router. Thanks. - Original Message - > From: "Adel Boutros" > To: users@qpid.apache.org

Re: Slow-starting queue visibility and handling it

On 14/01/17 02:43, Jeff Donner wrote: We're using proton 14, and qpidd 1.35. We probably have bad routing at one spot from a proton client to a qpidd broker on another machine, and the client is slow to see the queue (it fails out with "amqp:no-found"), even though the broker has been

[Dispatch Router] Dispatch router not able to use Proton 0.16.0

Hello, I was trying to compile the Dispatch Router to use Proton 0.16.0 however the compilation failed because it seems the code is not yet adapted to the newest version of Proton. Is there some work to make it work on this version of Proton? The error seems to be related to