There were 8 binding +1 votes, 1 non-binding +1 votes and no other
votes received. The vote has passed.
I will add the files to the dist release repo and create the final tag
shortly. The website will be updated after the release has had time to
sync to the mirrors.
Thanks to everybody for
+1
Ran the oslo.messaging smoke tests under Ubuntu Xenial - all good.
On Fri, Jun 29, 2018 at 3:21 PM, Ganesh Murthy wrote:
> Hello All,
>
> Please cast your vote on this thread to release RC2 as the
> official Qpid Dispatch Router version 1.2.0.
>
> RC2 of Qpid Dispatch Router
+1
Built against Proton 0.25.0-SNAPSHOT on Fedora 28
Ran system tests tests
ran console unit tests
started routers and started some message traffic
visited all console pages and verified things worked as expected
On Mon, Jul 2, 2018 at 10:54 AM, Ganesh Murthy wrote:
> +1
> * Validated
Since I lodged my vote (which remains unchanged) I did notice and
raise https://issues.apache.org/jira/browse/DISPATCH-1060 about the
test suite leaving some routers behind.
Robbie
On 2 July 2018 at 17:19, Robbie Gemmell wrote:
> +1
>
> I checked things out as follows:
> - Verified the
+1 ... build from source on CentOS 7 and used with different clients.
On Mon, Jul 2, 2018 at 6:19 PM Robbie Gemmell
wrote:
> +1
>
> I checked things out as follows:
> - Verified the signature and checksum files.
> - Checked for LICENCE+NOTICE files in the archive.
> - Ran mvn
+1
I checked things out as follows:
- Verified the signature and checksum files.
- Checked for LICENCE+NOTICE files in the archive.
- Ran mvn apache-rat:check to verify the licence headers.
- Built the router against Proton 0.24.0 and ran all the tests.
- Ran the JMS client 0.34.0 HelloWorld
+1
Tested against Proton 0.23 and 0.24 (Fedora 27)
On Mon, Jul 2, 2018 at 10:55 AM, Chuck Rolke wrote:
> +1
>
> * Verified download
> * Fedora 27
> * Built against proton 0.24-rc1 tag
> * Self tests pass
>
>
> - Original Message -
>> From: "Ganesh Murthy"
>> To: users@qpid.apache.org
+1
* Validated signatures and checksums
* Checked for presence of LICENSE and NOTICE files
* Ran mvn apache-rat:check, no files with missing license headers found.
* Built from source against Proton 0.24.0 in Fedora 27 and ran system
tests. All tests passed
On Fri, Jun 29, 2018 at 3:21 PM, Ganesh
+1
* Verified download
* Fedora 27
* Built against proton 0.24-rc1 tag
* Self tests pass
- Original Message -
> From: "Ganesh Murthy"
> To: users@qpid.apache.org
> Sent: Friday, June 29, 2018 3:21:48 PM
> Subject: [VOTE] Release Qpid Dispatch Router 1.2.0 (RC2)
>
> Hello All,
>
>
On 02/07/18 13:02, Robbie Gemmell wrote:
On 2 July 2018 at 12:47, Gordon Sim wrote:
On 02/07/18 12:33, akabhishek1 wrote:
Conclusion - It seems, we definitely need to have one active
producer/consumer
Requirement - Need to create producer on demand.
Could you please suggest best
On 2 July 2018 at 12:47, Gordon Sim wrote:
> On 02/07/18 12:33, akabhishek1 wrote:
>>
>> Hi Gordon And Robbie,
>>
>> Thanks a lot for your response. I think you are right it seems upper level
>> exception.
>> After doing research, i came on below conclusion.
>>
>> Problem - If we create only
The Apache Qpid (http://qpid.apache.org) community is pleased to announce
the immediate availability of Apache Qpid Proton 0.24.0.
Apache Qpid Proton is a messaging library for the Advanced Message Queuing
Protocol 1.0 (AMQP 1.0, ISO/IEC 19464, http://www.amqp.org). It can be used
in a wide range
On 02/07/18 12:33, akabhishek1 wrote:
Hi Gordon And Robbie,
Thanks a lot for your response. I think you are right it seems upper level
exception.
After doing research, i came on below conclusion.
Problem - If we create only Connection(without producer and consumer) and
kept Connection idle
Hi Gordon And Robbie,
Thanks a lot for your response. I think you are right it seems upper level
exception.
After doing research, i came on below conclusion.
Problem - If we create only Connection(without producer and consumer) and
kept Connection idle without creating producer and consumer,
On 2 July 2018 at 11:05, Gordon Sim wrote:
> On 30/06/18 14:43, Abhishek Kumar wrote:
>>
>> HI Team,
>>
>>
>>
>> I am using "qpid-jms-client-0.34.0" for connecting to servicebus.
>>
>>
>>
>> I am getting error "*The connection was inactive for more than the allowed
>> 6 milliseconds and is
On 30/06/18 14:43, Abhishek Kumar wrote:
HI Team,
I am using "qpid-jms-client-0.34.0" for connecting to servicebus.
I am getting error "*The connection was inactive for more than the allowed
6 milliseconds and is closed by container*".
I even setted as "amqp.idleTimeout=-1" but it
Hello,
I was testing the overflow policy introduced in the Broker-J 7.
With REJECT policy, the message is indeed discarded if the queue is already
full but I was actually expecting an exception on client side and didn't
receive anything.
Is that expected? Did I miss something?
Thanks,
Olivier
On 29/06/18 20:21, Ganesh Murthy wrote:
Hello All,
Please cast your vote on this thread to release RC2 as the
official Qpid Dispatch Router version 1.2.0.
RC2 of Qpid Dispatch Router version 1.2.0 can be found here:
https://dist.apache.org/repos/dist/dev/qpid/dispatch/1.2.0-rc2/
18 matches
Mail list logo
