I am canceling the vote for Qpid Dispatch Router 1.10.0 (RC1) due a segfault.
Here is the JIRA which details the problem -
https://issues.apache.org/jira/browse/DISPATCH-1523
I will put out a vote for 1.10.0 RC2 which will include a fix for the
above JIRA.
I apologize the inconvenience.
Thanks
On Fri, Dec 13, 2019 at 4:58 PM Chuck Rolke wrote:
> -1 A segfault has been identified.
>
> https://issues.apache.org/jira/browse/DISPATCH-1523
This segfault has been introduced by the fix for DISPATCH-1516 and does not
exist in the previously released v1.9.0. This crash can be easily and
consis
-1 A segfault has been identified.
https://issues.apache.org/jira/browse/DISPATCH-1523
- Original Message -
> From: "Ganesh Murthy"
> To: users@qpid.apache.org, d...@qpid.apache.org
> Sent: Thursday, December 12, 2019 1:32:39 PM
> Subject: [VOTE] Release Qpid Dispatch Router 1.10.0 (RC1)
+1
Verified the checksum, built on F30, and ran all the tests.
On Thu, Dec 12, 2019 at 1:39 PM Ganesh Murthy wrote:
> Hello All,
>
> Please cast your vote on this thread to release RC1 as the
> official Qpid Dispatch Router version 1.10.0.
>
> RC1 of Qpid Dispatch Router version 1.10.
+1
Built on Fedora 29
Ran tests
Started a couple of routers
Verified the console runs
On Fri, Dec 13, 2019 at 9:04 AM Gordon Sim wrote:
> On 12/12/2019 6:32 pm, Ganesh Murthy wrote:
> > Hello All,
> >
> > Please cast your vote on this thread to release RC1 as the
> > official Qpid
There were 6 +1 votes (5 binding) and 1 -1 vote. 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.
Robbie
On Fri, 2019-12-13 at 14:20 +, HADI Ali wrote:
> Hello,
>
> Sorry for the late reply. Thank you for the dev, it allows us to
> discover new endpoints when trying to reconnect.
>
> However there is one use case that we covered in Java with QPID-JMS
> that we couldn’t handle in C++.
> If at the
Hello,
Sorry for the late reply. Thank you for the dev, it allows us to discover new
endpoints when trying to reconnect.
However there is one use case that we covered in Java with QPID-JMS that we
couldn’t handle in C++.
If at the creation of the connection, no messaging server is yet available
There is no mechanism for this currently, the JMS client internally
sets properties+capabilities of its own or those required by the JMS
mapping, but it is not possible for applications to set them.
Robbie
On Thu, 12 Dec 2019 at 22:01, Neeraj Makam
wrote:
>
> Hi,
>
> I am using Qpid-Jms-Client,
I've tried this out and commented on the raised JIRA,
https://issues.apache.org/jira/browse/PROTON-2162. As it stands I dont
see this as a release blocking issue based on the description or the
previous and current behaviour I observed locally, and if there are
changes to be made think they can occ
On 12/12/2019 6:32 pm, Ganesh Murthy wrote:
Hello All,
Please cast your vote on this thread to release RC1 as the
official Qpid Dispatch Router version 1.10.0.
RC1 of Qpid Dispatch Router version 1.10.0 can be found here:
https://dist.apache.org/repos/dist/dev/qpid/dispatch/1.10.0-r
11 matches
Mail list logo