Re: [ANNOUNCE] Apache Qpid C++ 1.38.0 released

[Chris Richardson]

FYI, Gentoo ebuilds for this release (together with required Proton
versions) are available here:
https://github.com/fourceu/qpid-portage-overlay


On 4 April 2018 at 00:20, Justin Ross  wrote:

> The Apache Qpid community is pleased to announce the immediate availability
> of Apache Qpid C++ 1.38.0.
>
> Apache Qpid (https://qpid.apache.org) is a cross-platform messaging
> solution
> that implements the Advanced Message Queuing Protocol (AMQP,
> https://www.amqp.org). It provides message brokers written in C++
> and Java, a message router, and messaging APIs for C, C++, Java,
> JMS, Python, and Ruby.
>
> This release provides an update of the Qpid C++ broker and the
> C++ Qpid Messaging API with its related language bindings, incorporating
> various bug fixes and improvements.
>
> This release incorporates a number of defect fixes and enhancements.
> Release notes are available at:
>
> http://qpid.apache.org/releases/qpid-cpp-1.38.0/release-notes.html
>
> The release is available now from our website:
>
> http://qpid.apache.org/download.html
>
> Thanks to all the users and contributors who have helped to improve
> Apache Qpid C++.
>
> Justin
>



-- 

*Chris Richardson*, System Architect
c...@fourc.eu


*FourC AS, Vestre Rosten 81, Trekanten, NO-7075 Tiller, Norwaywww.fourc.eu
*

*Follow us on LinkedIn , Facebook
, Google+  and Twitter
!*

[ANNOUNCE] Apache Qpid C++ 1.38.0 released

[Justin Ross]

The Apache Qpid community is pleased to announce the immediate availability
of Apache Qpid C++ 1.38.0.

Apache Qpid (https://qpid.apache.org) is a cross-platform messaging solution
that implements the Advanced Message Queuing Protocol (AMQP,
https://www.amqp.org). It provides message brokers written in C++
and Java, a message router, and messaging APIs for C, C++, Java,
JMS, Python, and Ruby.

This release provides an update of the Qpid C++ broker and the
C++ Qpid Messaging API with its related language bindings, incorporating
various bug fixes and improvements.

This release incorporates a number of defect fixes and enhancements.
Release notes are available at:

http://qpid.apache.org/releases/qpid-cpp-1.38.0/release-notes.html

The release is available now from our website:

http://qpid.apache.org/download.html

Thanks to all the users and contributors who have helped to improve
Apache Qpid C++.

Justin

Re: [VOTE] Release Qpid for Java 6.1.6

[Oleksandr Rudyy]

+1

I performed the following tests:

* verified signatures and checksums
* built and ran java-mms.0-9 tests from source bundle
* started broker on fedora 27
* created test queue using Web Management Console
* ran "hello world" example using JMS AMQP 1.0 client
* ran "hello world" example using JMS AMQP 0-x client


On 30 March 2018 at 16:45, Oleksandr Rudyy  wrote:
> Hi all,
>
> A bug-fix release candidate for the version 6.1.6 of the Qpid for
> Java Components has been created.
>
> The list of defect fixes can be found in Jira:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310520=12342163
>
> Please test and vote accordingly.
>
> The source and binary archives can be grabbed from here:
> https://dist.apache.org/repos/dist/dev/qpid/java/6.1.6-rc1
>
> Those files and the other maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1135
>
> Kind regards
>
> P.S. If you want to test it out using maven (e.g with the examples src,
> or your own things), you can temporarily add this to your poms to access
> the staging repo:
>
>   
> 
>   staging
>
> https://repository.apache.org/content/repositories/orgapacheqpid-1135
> 
>   
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org

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

Re: [VOTE] Release Apache Qpid Broker-J 7.0.3

[Oleksandr Rudyy]

+1

I performed the following tests:

* verified signatures and checksums
* built and ran java-mms.1-0 tests from source bundle
* started broker on fedora 27
* created test queue using Web Management Console
* ran "hello world" example using JMS AMQP 1.0 client
* ran "hello world" example using JMS AMQP 0-x client


On 30 March 2018 at 15:40, Oleksandr Rudyy  wrote:
> Hi all,
>
> I built a release candidate for a Qpid Broker-J 7.0.3.
> Please give it a test out and vote accordingly.
>
> The source and binary archives can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/broker-j/7.0.3-rc1
>
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1134
>
> The JIRAs currently assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310520=12342887
>
> Regards,
> Alex
>
> P.S. For testing of maven broker staging repo artefacts, please add into to
> your poms the staging repo as below:
>
>   
> 
>   staging
>
> https://repository.apache.org/content/repositories/orgapacheqpid-1134
> 
>   
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org

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

Qpid Dispatch Router release (1.1.0)

[Ted Ross]

Since the release of Qpid Proton 0.22.0, Qpid Dispatch Router's tests
fail against the latest released Proton because of the removal of the
deprecated Messenger API.  We are planning to push some of the
in-progress Jiras to the next release so we can produce version 1.1.0
soon.

Please look for a release candidate for 1.1.0 this week.

-Ted

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

Re: Building proton from master fails on Red Hat Enterprise Linux Server release 7.3 Maipo with "fatal error: bits/c++config.h: No such file or directory"

[Andrew Stitcher]

On Tue, 2018-04-03 at 10:56 +0100, Keith W wrote:
> ...
> Thanks for the replies.  The 7.3 Maipo image in question is
> corporatised by our organisation, so it could be special in this
> respect.

"corporatised" sounds like an archaic swear word!

A


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

Re: [VOTE] Release Qpid for Java 6.1.6

[Keith W]

+1.

My testing was:

1) Verified the sha512 checksums on all distribution artefacts
2) Verified signatures on all the distribution artefacts
3) Ran apache RAT
4) Built/ran test profile bdb (0-9) and dby (0-10) from source bundle
5) Ran hello world against staged maven client artefacts against
broker from binary distribution artefact
6) Repeated a manual test verifying the fix for QPID-8144 (Memory
compaction may not run when Direct Memory exceeds 2GB)

On 2 April 2018 at 13:24, Robbie Gemmell  wrote:
> On 30 March 2018 at 16:45, Oleksandr Rudyy  wrote:
>> Hi all,
>>
>> A bug-fix release candidate for the version 6.1.6 of the Qpid for
>> Java Components has been created.
>>
>> The list of defect fixes can be found in Jira:
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310520=12342163
>>
>> Please test and vote accordingly.
>>
>> The source and binary archives can be grabbed from here:
>> https://dist.apache.org/repos/dist/dev/qpid/java/6.1.6-rc1
>>
>> Those files and the other maven artifacts are also staged for now at:
>> https://repository.apache.org/content/repositories/orgapacheqpid-1135
>>
>> Kind regards
>>
>> P.S. If you want to test it out using maven (e.g with the examples src,
>> or your own things), you can temporarily add this to your poms to access
>> the staging repo:
>>
>>   
>> 
>>   staging
>>   
>> https://repository.apache.org/content/repositories/orgapacheqpid-1135
>> 
>>   
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
>> For additional commands, e-mail: users-h...@qpid.apache.org
>
> +1
>
> I checked things over as follows:
> - Verified the signature and checksum files.
> - Used "mvn apache-rat:check" to verify the headers in source release.
> - Checked for LICENCE and NOTICE files being present in each archive.
> - Ran the source build and tests using the default profile, all passed.
> - Started the broker, used the web console to create a queue, ran the
> Qpid JMS master HelloWorld example against the broker.
>
> Robbie
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>

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

Re: Building proton from master fails on Red Hat Enterprise Linux Server release 7.3 Maipo with "fatal error: bits/c++config.h: No such file or directory"

[Keith W]

On 3 April 2018 at 10:31, Robbie Gemmell  wrote:
> "The package is not listed as required in INSTALL.md, I am curious
> whether the instructions needs to be amended to include this package."
>
> It seems its a dependency of the "gcc-c++" package which is mentioned,
> so I'd guess thats why it isnt noted explicitly. Not sure how you came
> to have the x64 version of one and the i686 version of the other
> though.
>

Thanks for the replies.  The 7.3 Maipo image in question is
corporatised by our organisation, so it could be special in this
respect.

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

Re: Building proton from master fails on Red Hat Enterprise Linux Server release 7.3 Maipo with "fatal error: bits/c++config.h: No such file or directory"

[Robbie Gemmell]

"The package is not listed as required in INSTALL.md, I am curious
whether the instructions needs to be amended to include this package."

It seems its a dependency of the "gcc-c++" package which is mentioned,
so I'd guess thats why it isnt noted explicitly. Not sure how you came
to have the x64 version of one and the i686 version of the other
though.

Robbie

On 3 April 2018 at 09:24, Oleksandr Rudyy  wrote:
> Hi Andrew,
>
> Thanks for helping with the issue.
>
> Yes, you are right we are trying to compile for 64 bits.
>
> It is a freshly built Red Hat Enterprise Linux Server release 7.3.
>
> All required dependencies have been installed as per instructions in
> proton INSTALL.md [1].
>
> I am not sure how we ended-up with installed 32 bits libstdc++-devel
> instead of 64 bits.
> We will try to install libstdc++-devel-4.8.5-16.el7_4.2.x86_64 .
>
> The package is not listed as required in INSTALL.md, I am curious
> whether the instructions needs to be amended to include this package.
>
> I am not sure what other 32 bits packages have been installed instead
> of 64 bits. Is there a way to verify that all required 64bits
> dependencies are installed for proton apart from running cmake/make
> and dealing with compilation errors?
>
> Kind Regards,
> Alex
>
> [1] https://github.com/apache/qpid-proton/blob/master/INSTALL.md
>
> On 2 April 2018 at 19:49, Andrew Stitcher  wrote:
>> On Mon, 2018-04-02 at 17:15 +0100, Oleksandr Rudyy wrote:
>>> Hi Andrew,
>>>
>>> In Red Hat Enterprise Linux Server release 7.3 I found file
>>> /usr/include/c++/4.8.2/i686-redhat-linux/bits/c++config.h which was
>>> installed as part of libstdc++-devel.
>>>
>>> rpm -qf /usr/include/c++/4.8.2/i686-redhat-linux/bits/c++config.h
>>> libstdc++-devel-4.8.5-16.el7_4.2.i686
>>>
>>> ' /usr/include/c++/4.8.2/cstddef' was installed as part of the same
>>> package
>>>
>>> rpm -qf /usr/include/c++/4.8.2/cstddef
>>> libstdc++-devel-4.8.5-16.el7_4.2.i686
>>
>> Are you compiling for 32 or 64 bits?
>>
>> That header file is for 32 bits, but it looks like your compile line is
>> for 64 bits.
>>
>> You probably need the package libstdc++-devel-4.8.5-16.el7_4.2.x86_64
>>
>> Andrew
>>
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
>> For additional commands, e-mail: users-h...@qpid.apache.org
>>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>

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

Re: Building proton from master fails on Red Hat Enterprise Linux Server release 7.3 Maipo with "fatal error: bits/c++config.h: No such file or directory"

[Oleksandr Rudyy]

Hi Andrew,

Thanks for helping with the issue.

Yes, you are right we are trying to compile for 64 bits.

It is a freshly built Red Hat Enterprise Linux Server release 7.3.

All required dependencies have been installed as per instructions in
proton INSTALL.md [1].

I am not sure how we ended-up with installed 32 bits libstdc++-devel
instead of 64 bits.
We will try to install libstdc++-devel-4.8.5-16.el7_4.2.x86_64 .

The package is not listed as required in INSTALL.md, I am curious
whether the instructions needs to be amended to include this package.

I am not sure what other 32 bits packages have been installed instead
of 64 bits. Is there a way to verify that all required 64bits
dependencies are installed for proton apart from running cmake/make
and dealing with compilation errors?

Kind Regards,
Alex

[1] https://github.com/apache/qpid-proton/blob/master/INSTALL.md

On 2 April 2018 at 19:49, Andrew Stitcher  wrote:
> On Mon, 2018-04-02 at 17:15 +0100, Oleksandr Rudyy wrote:
>> Hi Andrew,
>>
>> In Red Hat Enterprise Linux Server release 7.3 I found file
>> /usr/include/c++/4.8.2/i686-redhat-linux/bits/c++config.h which was
>> installed as part of libstdc++-devel.
>>
>> rpm -qf /usr/include/c++/4.8.2/i686-redhat-linux/bits/c++config.h
>> libstdc++-devel-4.8.5-16.el7_4.2.i686
>>
>> ' /usr/include/c++/4.8.2/cstddef' was installed as part of the same
>> package
>>
>> rpm -qf /usr/include/c++/4.8.2/cstddef
>> libstdc++-devel-4.8.5-16.el7_4.2.i686
>
> Are you compiling for 32 or 64 bits?
>
> That header file is for 32 bits, but it looks like your compile line is
> for 64 bits.
>
> You probably need the package libstdc++-devel-4.8.5-16.el7_4.2.x86_64
>
> Andrew
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>

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

Re: [VOTE] Release Apache Qpid Broker-J 7.0.3

[Keith W]

+1.

My testing was:

1) Verified the md5/sha checksums on all distribution artefacts
2) Verified signatures on all the distribution artefacts
3) Ran apache RAT
4) Built/ran test profile mms/bdb 0-9/0-10//1.0 from source bundle
(Qpid JMS Client 0.31.0)
5) Generally kicked the tyres within the Web Management Console using
Broker from the tar,gz bundle
6) Spun up an embedded Broker-J using the staged maven artefacts.
7) Repeated a manual test verifying the fix for QPID-8144 (Memory
compaction may not run when Direct Memory exceeds 2GB)

On 2 April 2018 at 12:47, Robbie Gemmell  wrote:
> On 30 March 2018 at 15:40, Oleksandr Rudyy  wrote:
>> Hi all,
>>
>> I built a release candidate for a Qpid Broker-J 7.0.3.
>> Please give it a test out and vote accordingly.
>>
>> The source and binary archives can be grabbed from:
>> https://dist.apache.org/repos/dist/dev/qpid/broker-j/7.0.3-rc1
>>
>> The maven artifacts are also staged for now at:
>> https://repository.apache.org/content/repositories/orgapacheqpid-1134
>>
>> The JIRAs currently assigned are:
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310520=12342887
>>
>> Regards,
>> Alex
>>
>> P.S. For testing of maven broker staging repo artefacts, please add into to
>> your poms the staging repo as below:
>>
>>   
>> 
>>   staging
>>   
>> https://repository.apache.org/content/repositories/orgapacheqpid-1134
>> 
>>   
>>
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
>> For additional commands, e-mail: users-h...@qpid.apache.org
>
> +1
>
> I checked things over as follows:
> - Verified the signature and checksum files.
> - Used "mvn apache-rat:check" to verify the headers in source release.
> - Checked for LICENCE and NOTICE files being present in each archive.
> - Ran the source build and tests using the default profile, all good.
> - Started the broker, used the web console to create a queue, ran the
> Qpid JMS master HelloWorld example against the broker.
>
> Robbie
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>

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