You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@qpid.apache.org by Robbie Gemmell <ro...@gmail.com> on 2017/09/18 16:45:52 UTC
[VOTE] Release Apache Qpid JMS 0.25.0
Hi folks,
I have put together a spin for a 0.25.0 Qpid JMS client release, 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/jms/0.25.0-rc1/
The maven artifacts are also staged for now at:
https://repository.apache.org/content/repositories/orgapacheqpid-1115
The JIRAs currently assigned are:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524&version=12341292
Regards,
Robbie
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:
<repositories>
<repository>
<id>staging</id>
<url>https://repository.apache.org/content/repositories/orgapacheqpid-1115</url>
</repository>
</repositories>
The dependency for the client itself would then be:
<dependency>
<groupId>org.apache.qpid</groupId>
<artifactId>qpid-jms-client</artifactId>
<version>0.25.0</version>
</dependency>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: [VOTE] Release Apache Qpid JMS 0.25.0
Posted by Jakub Scholz <ja...@scholz.cz>.
+1 ... used the staged artifacts and run my tests against different
versions of Qpid C++ broker (including the latest master).
On Mon, Sep 18, 2017 at 9:02 PM, Timothy Bish <ta...@gmail.com> wrote:
> On 09/18/2017 12:45 PM, Robbie Gemmell wrote:
>
>> Hi folks,
>>
>> I have put together a spin for a 0.25.0 Qpid JMS client release, 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/jms/0.25.0-rc1/
>>
>> The maven artifacts are also staged for now at:
>> https://repository.apache.org/content/repositories/orgapacheqpid-1115
>>
>> The JIRAs currently assigned are:
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje
>> ctId=12314524&version=12341292
>>
>> Regards,
>> Robbie
>>
>> 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:
>>
>> <repositories>
>> <repository>
>> <id>staging</id>
>> <url>https://repository.apache.org/content/repositories/
>> orgapacheqpid-1115</url>
>> </repository>
>> </repositories>
>>
>> The dependency for the client itself would then be:
>>
>> <dependency>
>> <groupId>org.apache.qpid</groupId>
>> <artifactId>qpid-jms-client</artifactId>
>> <version>0.25.0</version>
>> </dependency>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
>> For additional commands, e-mail: users-help@qpid.apache.org
>>
>>
>> +1
>
> * Validated signatures and checksums
> * Checked bin and src archives for proper license and notice files
> * Built from source and ran the tests
> * Checked for license issues using 'mvn apache-rat:check'
> * Used the staged artifacts in ActiveMQ 5.x to build and run all AMQP tests
> * Used the staged artifacts in Artemis to build and run all AMQP tests
> * Ran the example from the src archive against a running 5.x broker.
>
>
> --
> Tim Bish
> twitter: @tabish121
> blog: http://timbish.blogspot.com/
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
>
Re: [VOTE] Release Apache Qpid JMS 0.25.0
Posted by Timothy Bish <ta...@gmail.com>.
On 09/18/2017 12:45 PM, Robbie Gemmell wrote:
> Hi folks,
>
> I have put together a spin for a 0.25.0 Qpid JMS client release, 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/jms/0.25.0-rc1/
>
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1115
>
> The JIRAs currently assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524&version=12341292
>
> Regards,
> Robbie
>
> 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:
>
> <repositories>
> <repository>
> <id>staging</id>
> <url>https://repository.apache.org/content/repositories/orgapacheqpid-1115</url>
> </repository>
> </repositories>
>
> The dependency for the client itself would then be:
>
> <dependency>
> <groupId>org.apache.qpid</groupId>
> <artifactId>qpid-jms-client</artifactId>
> <version>0.25.0</version>
> </dependency>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
>
+1
* Validated signatures and checksums
* Checked bin and src archives for proper license and notice files
* Built from source and ran the tests
* Checked for license issues using 'mvn apache-rat:check'
* Used the staged artifacts in ActiveMQ 5.x to build and run all AMQP tests
* Used the staged artifacts in Artemis to build and run all AMQP tests
* Ran the example from the src archive against a running 5.x broker.
--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: [VOTE] Release Apache Qpid JMS 0.25.0
Posted by Robbie Gemmell <ro...@gmail.com>.
On 19 September 2017 at 12:51, Gordon Sim <gs...@redhat.com> wrote:
> On 19/09/17 11:28, Robbie Gemmell wrote:
>>
>> On 19 September 2017 at 11:20, Gordon Sim <gs...@redhat.com> wrote:
>>>
>>> I did see the following test failures, but suspect this is just a
>>> configuration issue(?).
>>>
>>>> Failed tests:
>>>>
>>>> SaslGssApiIntegrationTest.testGssapiOnlySelectedWhenPresentIfExplicitlyEnabled:228->doMechanismSelectedTestImpl:253
>>>> All handlers did not complete within the 1000ms timeout.
>>>> Tests in error: SaslGssApiIntegrationTest.testSaslGssApiKrbConnection
>>>> »
>>>> JMSSecurity Exception ...
>>>> SaslGssApiIntegrationTest.testSaslGssApiKrbConnectionWithDefaultScope
>>>> »
>>>> JMSSecurity
>>>>
>>>>
>>>> SaslGssApiIntegrationTest.testSaslGssApiKrbConnectionWithPrincipalViaJmsUsernameConnFactory
>>>> » JMSSecurity
>>>>
>>>>
>>>> SaslGssApiIntegrationTest.testSaslGssApiKrbConnectionWithPrincipalViaJmsUsernameUri
>>>> » JMSSecurity
>>>
>>>
>>
>> Given they are all highly related and we havent seen issue elsewhere,
>> I think it points to something particular with the environment
>
>
> Agreed, just noting then for completeness.
>
>
Yep, please do, can't investigate if we don't know.
Gordon sent me the logs I asked for off list, and there looks to be
something going on with naming and/or unhandled interaction with
existing config in the env. I've suggested some changes to try and
help find out what, whether we could make them pass, or perhaps use
info to skip if needed.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: [VOTE] Release Apache Qpid JMS 0.25.0
Posted by Gordon Sim <gs...@redhat.com>.
On 19/09/17 11:28, Robbie Gemmell wrote:
> On 19 September 2017 at 11:20, Gordon Sim <gs...@redhat.com> wrote:
>> I did see the following test failures, but suspect this is just a
>> configuration issue(?).
>>
>>> Failed tests:
>>> SaslGssApiIntegrationTest.testGssapiOnlySelectedWhenPresentIfExplicitlyEnabled:228->doMechanismSelectedTestImpl:253
>>> All handlers did not complete within the 1000ms timeout.
>>> Tests in error: SaslGssApiIntegrationTest.testSaslGssApiKrbConnection »
>>> JMSSecurity Exception ...
>>> SaslGssApiIntegrationTest.testSaslGssApiKrbConnectionWithDefaultScope »
>>> JMSSecurity
>>>
>>> SaslGssApiIntegrationTest.testSaslGssApiKrbConnectionWithPrincipalViaJmsUsernameConnFactory
>>> » JMSSecurity
>>>
>>> SaslGssApiIntegrationTest.testSaslGssApiKrbConnectionWithPrincipalViaJmsUsernameUri
>>> » JMSSecurity
>>
>
> Given they are all highly related and we havent seen issue elsewhere,
> I think it points to something particular with the environment
Agreed, just noting then for completeness.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: [VOTE] Release Apache Qpid JMS 0.25.0
Posted by Robbie Gemmell <ro...@gmail.com>.
On 19 September 2017 at 11:20, Gordon Sim <gs...@redhat.com> wrote:
> On 18/09/17 17:45, Robbie Gemmell wrote:
>>
>> Hi folks,
>>
>> I have put together a spin for a 0.25.0 Qpid JMS client release, 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/jms/0.25.0-rc1/
>>
>> The maven artifacts are also staged for now at:
>> https://repository.apache.org/content/repositories/orgapacheqpid-1115
>>
>> The JIRAs currently assigned are:
>>
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524&version=12341292
>
>
> +1
>
> Built and installed source, ran example against router and both brokers.
>
> I did see the following test failures, but suspect this is just a
> configuration issue(?).
>
>> Failed tests:
>> SaslGssApiIntegrationTest.testGssapiOnlySelectedWhenPresentIfExplicitlyEnabled:228->doMechanismSelectedTestImpl:253
>> All handlers did not complete within the 1000ms timeout.
>> Tests in error: SaslGssApiIntegrationTest.testSaslGssApiKrbConnection »
>> JMSSecurity Exception ...
>> SaslGssApiIntegrationTest.testSaslGssApiKrbConnectionWithDefaultScope »
>> JMSSecurity
>>
>> SaslGssApiIntegrationTest.testSaslGssApiKrbConnectionWithPrincipalViaJmsUsernameConnFactory
>> » JMSSecurity
>>
>> SaslGssApiIntegrationTest.testSaslGssApiKrbConnectionWithPrincipalViaJmsUsernameUri
>> » JMSSecurity
>
Given they are all highly related and we havent seen issue elsewhere,
I think it points to something particular with the environment and the
tests themselves, though I'm not immediately thinking of anything it
could be. Nothing has changed around that area so I expect the same
would have been true with 0.24.0 too (when they were added) rather
than being new. I'll ask you for some more details off list to see if
I can figure out whats going on and whether we need to e.g adjust the
tests or make them skip in certain env cases.
Robbie
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: [VOTE] Release Apache Qpid JMS 0.25.0
Posted by Gordon Sim <gs...@redhat.com>.
On 18/09/17 17:45, Robbie Gemmell wrote:
> Hi folks,
>
> I have put together a spin for a 0.25.0 Qpid JMS client release, 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/jms/0.25.0-rc1/
>
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1115
>
> The JIRAs currently assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524&version=12341292
+1
Built and installed source, ran example against router and both brokers.
I did see the following test failures, but suspect this is just a
configuration issue(?).
> Failed tests:
> SaslGssApiIntegrationTest.testGssapiOnlySelectedWhenPresentIfExplicitlyEnabled:228->doMechanismSelectedTestImpl:253 All handlers did not complete within the 1000ms timeout.
> Tests in error:
> SaslGssApiIntegrationTest.testSaslGssApiKrbConnection » JMSSecurity Exception ...
> SaslGssApiIntegrationTest.testSaslGssApiKrbConnectionWithDefaultScope » JMSSecurity
> SaslGssApiIntegrationTest.testSaslGssApiKrbConnectionWithPrincipalViaJmsUsernameConnFactory » JMSSecurity
> SaslGssApiIntegrationTest.testSaslGssApiKrbConnectionWithPrincipalViaJmsUsernameUri » JMSSecurity
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: [VOTE] Release Apache Qpid JMS 0.25.0
Posted by Oleksandr Rudyy <or...@gmail.com>.
+1
* verified checksums and signatures
* built successfully from sources
* ran successfully qpid-broker-j system tests with staged 0.25.0 artefacts
* ran successfully hello world example against trunk version of
qpid-broker-j
Re: [VOTE] Release Apache Qpid JMS 0.25.0
Posted by Keith W <ke...@gmail.com>.
+1
* Verified the checksums and signatures on source and binary artefacts
* Ran Apache RAT
* Built from source and ran the tests (on Oracle JVM 1.8.0_144-b01 on
Mac OS X 10.11.6)
* Tested the staged maven artefacts with the Java Broker's system test
suite (master) and Joram test suite.
On 19 September 2017 at 17:47, Robbie Gemmell <ro...@gmail.com> wrote:
> On 19 September 2017 at 15:50, Jiri Danek <jd...@redhat.com> wrote:
>> +1 (nonbinding)
>>
>> Used the maven repo with https://github.com/rh-messaging-qe/cli-java and
>> executed the few tests there against ActiveMQ Artemis 2.4.0-SNAPSHOT
>> broker. Result is that https://issues.apache.org/jira/browse/QPIDJMS-314 is
>> apparently still not resolved (as expected), but without setting the
>> problematic SO_LINGER option all tests passed.
>> --
>> Jiří Daněk
>
> Yep, 314 didn't seem like a reason to wait on releasing the other
> existing fixes etc. I doubt anyone will hit it outside a test, but it
> is another reason to do a further release later once a fix is
> available in a Netty release (the related PR was merged earlier
> today).
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: [VOTE] Release Apache Qpid JMS 0.25.0
Posted by Robbie Gemmell <ro...@gmail.com>.
On 19 September 2017 at 15:50, Jiri Danek <jd...@redhat.com> wrote:
> +1 (nonbinding)
>
> Used the maven repo with https://github.com/rh-messaging-qe/cli-java and
> executed the few tests there against ActiveMQ Artemis 2.4.0-SNAPSHOT
> broker. Result is that https://issues.apache.org/jira/browse/QPIDJMS-314 is
> apparently still not resolved (as expected), but without setting the
> problematic SO_LINGER option all tests passed.
> --
> Jiří Daněk
Yep, 314 didn't seem like a reason to wait on releasing the other
existing fixes etc. I doubt anyone will hit it outside a test, but it
is another reason to do a further release later once a fix is
available in a Netty release (the related PR was merged earlier
today).
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: [VOTE] Release Apache Qpid JMS 0.25.0
Posted by Jiri Danek <jd...@redhat.com>.
+1 (nonbinding)
Used the maven repo with https://github.com/rh-messaging-qe/cli-java and
executed the few tests there against ActiveMQ Artemis 2.4.0-SNAPSHOT
broker. Result is that https://issues.apache.org/jira/browse/QPIDJMS-314 is
apparently still not resolved (as expected), but without setting the
problematic SO_LINGER option all tests passed.
--
Jiří Daněk
Re: [VOTE] Release Apache Qpid JMS 0.25.0
Posted by Robbie Gemmell <ro...@gmail.com>.
On 18 September 2017 at 17:45, Robbie Gemmell <ro...@gmail.com> wrote:
> Hi folks,
>
> I have put together a spin for a 0.25.0 Qpid JMS client release, 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/jms/0.25.0-rc1/
>
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1115
>
> The JIRAs currently assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524&version=12341292
>
> Regards,
> Robbie
>
> 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:
>
> <repositories>
> <repository>
> <id>staging</id>
> <url>https://repository.apache.org/content/repositories/orgapacheqpid-1115</url>
> </repository>
> </repositories>
>
> The dependency for the client itself would then be:
>
> <dependency>
> <groupId>org.apache.qpid</groupId>
> <artifactId>qpid-jms-client</artifactId>
> <version>0.25.0</version>
> </dependency>
Adding my +1
I tested things as follows:
- Verified the signature and checksum files.
- Checked LICENCE+NOTICE files in the src and bin archives.
- Used mvn apache-rat:check to verify licence headers in the src archive.
- Ran the source build and tests.
- Built the examples from the binary release archive with Maven using the
staging repo and ran HelloWorld against Qpid Broker-J 6.1.4,
ActiveMQ 5.15.x, and ActiveMQ Artemis master.
- Built the examples manually using javac and ran HelloWorld to verify.
- Ran the ActiveMQ Artemis master and ActiveMQ 5.15.x builds and
their AMQP tests using the staging repo bits.
Robbie
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: [VOTE] Release Apache Qpid JMS 0.25.0
Posted by Rob Godfrey <ro...@gmail.com>.
+1
Built from source and ran tests (saw 1 (non recurring) test failure,
discussed off list with Robbie - looks like a ActiveMQ issue)
Ran Qpid Broker-J AMQP 1.0 tests (from master) using 0.25.0 client
-- Rob
On 18 September 2017 at 18:45, Robbie Gemmell <ro...@gmail.com>
wrote:
> Hi folks,
>
> I have put together a spin for a 0.25.0 Qpid JMS client release, 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/jms/0.25.0-rc1/
>
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1115
>
> The JIRAs currently assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12314524&version=12341292
>
> Regards,
> Robbie
>
> 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:
>
> <repositories>
> <repository>
> <id>staging</id>
> <url>https://repository.apache.org/content/
> repositories/orgapacheqpid-1115</url>
> </repository>
> </repositories>
>
> The dependency for the client itself would then be:
>
> <dependency>
> <groupId>org.apache.qpid</groupId>
> <artifactId>qpid-jms-client</artifactId>
> <version>0.25.0</version>
> </dependency>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
>