You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@qpid.apache.org by Alex Rudyy <or...@apache.org> on 2020/03/04 11:44:00 UTC
[VOTE] Release Qpid Broker-J 8.0.0
Hi all,
I built release artefacts for Qpid Broker-J version 8.0.0 RC1.
Please, give them a test out and vote accordingly.
The source and binary archives can be found at:
https://dist.apache.org/repos/dist/dev/qpid/broker-j/8.0.0-rc1/
The maven artifacts are also staged at:
https://repository.apache.org/content/repositories/orgapacheqpid-1192
The new version brings a number of improvements and bug fixes
including changes to ACL to limit the number of connections per user
and support for trusted CA revocation list.
You can find the full list of JIRAs included into the release here:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310520&version=12344778
Kind Regards,
Alex
P.S. For testing of maven broker staging repo artefacts, please add into to
your project pom the staging repo as below:
<repositories>
<repository>
<id>staging</id>
<url>
https://repository.apache.org/content/repositories/orgapacheqpid-1192</url>
</repository>
</repositories>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: [VOTE] Release Qpid Broker-J 8.0.0
Posted by Oleksandr Rudyy <or...@gmail.com>.
+1
My tests included the following:
* verified signatures and checksums
* verified source headers with mvn apache-rat:check
* built broker from source bundle with running all unit and integration
tests using default profile
* started broker and created queue via web management console
* ran successfully hello world examples
On Wed, 4 Mar 2020 at 11:44, Alex Rudyy <or...@apache.org> wrote:
> Hi all,
>
> I built release artefacts for Qpid Broker-J version 8.0.0 RC1.
> Please, give them a test out and vote accordingly.
>
> The source and binary archives can be found at:
> https://dist.apache.org/repos/dist/dev/qpid/broker-j/8.0.0-rc1/
>
> The maven artifacts are also staged at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1192
>
> The new version brings a number of improvements and bug fixes
> including changes to ACL to limit the number of connections per user
> and support for trusted CA revocation list.
>
> You can find the full list of JIRAs included into the release here:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310520&version=12344778
>
> Kind Regards,
> Alex
>
> P.S. For testing of maven broker staging repo artefacts, please add into
> to your project pom the staging repo as below:
>
> <repositories>
> <repository>
> <id>staging</id>
> <url>
> https://repository.apache.org/content/repositories/orgapacheqpid-1192
> </url>
> </repository>
> </repositories>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
Re: [VOTE] Release Qpid Broker-J 8.0.0
Posted by Gordon Sim <gs...@redhat.com>.
On 11/03/2020 6:39 pm, Oleksandr Rudyy wrote:
> Gordon,
>
> Thanks for letting me know that the issue still exists.
> I committed a fix to the tests in QPID-8426 which changes the test to use
> the same domain in service principal name and kdc.
> Previously, kdc domain was set to
> InetAddress.getLoopbackAddress().getCanonicalHostName()
> whilst SPN domain was hard-coded to "localhost". I suspect that the
> difference in domain name could cause the test failure.
That could very well be it! Thanks Alex!
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: [VOTE] Release Qpid Broker-J 8.0.0
Posted by Oleksandr Rudyy <or...@gmail.com>.
Gordon,
Thanks for letting me know that the issue still exists.
I committed a fix to the tests in QPID-8426 which changes the test to use
the same domain in service principal name and kdc.
Previously, kdc domain was set to
InetAddress.getLoopbackAddress().getCanonicalHostName()
whilst SPN domain was hard-coded to "localhost". I suspect that the
difference in domain name could cause the test failure.
Kind Regards,
Alex
On Wed, 11 Mar 2020 at 12:39, Gordon Sim <gs...@redhat.com> wrote:
> On 11/03/2020 12:22 pm, Oleksandr Rudyy wrote:
> > Gordon,
> > Do you still see any test failures from test suites
> > KerberosAuthenticationManagerTest and SpnegoAuthenticatorTest in your
> > environment?
>
> Yes:
>
> > [ERROR] Tests run: 4, Failures: 0, Errors: 1, Skipped: 0, Time elapsed:
> 0.277 s <<< FAILURE! - in
> org.apache.qpid.server.security.auth.manager.KerberosAuthenticationManagerTest
> > [ERROR]
> testCreateSaslNegotiator(org.apache.qpid.server.security.auth.manager.KerberosAuthenticationManagerTest)
> Time elapsed: 0.095 s <<< ERROR!
> > java.security.PrivilegedActionException
> > at
> org.apache.qpid.server.security.auth.manager.KerberosAuthenticationManagerTest.performNegotiation(KerberosAuthenticationManagerTest.java:242)
> > at
> org.apache.qpid.server.security.auth.manager.KerberosAuthenticationManagerTest.authenticate(KerberosAuthenticationManagerTest.java:212)
> > at
> org.apache.qpid.server.security.auth.manager.KerberosAuthenticationManagerTest.testCreateSaslNegotiator(KerberosAuthenticationManagerTest.java:137)
> > Caused by: javax.security.sasl.SaslException: GSS initiate failed
> > at
> org.apache.qpid.server.security.auth.manager.KerberosAuthenticationManagerTest.lambda$performNegotiation$0(KerberosAuthenticationManagerTest.java:245)
> > at
> org.apache.qpid.server.security.auth.manager.KerberosAuthenticationManagerTest.performNegotiation(KerberosAuthenticationManagerTest.java:242)
> > at
> org.apache.qpid.server.security.auth.manager.KerberosAuthenticationManagerTest.authenticate(KerberosAuthenticationManagerTest.java:212)
> > at
> org.apache.qpid.server.security.auth.manager.KerberosAuthenticationManagerTest.testCreateSaslNegotiator(KerberosAuthenticationManagerTest.java:137)
> > Caused by: org.ietf.jgss.GSSException: No valid credentials provided
> (Mechanism level: Server not found in Kerberos database (7) - Server not
> found in Kerberos database)
> > at
> org.apache.qpid.server.security.auth.manager.KerberosAuthenticationManagerTest.lambda$performNegotiation$0(KerberosAuthenticationManagerTest.java:245)
> > at
> org.apache.qpid.server.security.auth.manager.KerberosAuthenticationManagerTest.performNegotiation(KerberosAuthenticationManagerTest.java:242)
> > at
> org.apache.qpid.server.security.auth.manager.KerberosAuthenticationManagerTest.authenticate(KerberosAuthenticationManagerTest.java:212)
> > at
> org.apache.qpid.server.security.auth.manager.KerberosAuthenticationManagerTest.testCreateSaslNegotiator(KerberosAuthenticationManagerTest.java:137)
> > Caused by: sun.security.krb5.KrbException: Server not found in Kerberos
> database (7) - Server not found in Kerberos database
> > at
> org.apache.qpid.server.security.auth.manager.KerberosAuthenticationManagerTest.lambda$performNegotiation$0(KerberosAuthenticationManagerTest.java:245)
> > at
> org.apache.qpid.server.security.auth.manager.KerberosAuthenticationManagerTest.performNegotiation(KerberosAuthenticationManagerTest.java:242)
> > at
> org.apache.qpid.server.security.auth.manager.KerberosAuthenticationManagerTest.authenticate(KerberosAuthenticationManagerTest.java:212)
> > at
> org.apache.qpid.server.security.auth.manager.KerberosAuthenticationManagerTest.testCreateSaslNegotiator(KerberosAuthenticationManagerTest.java:137)
> > Caused by: sun.security.krb5.Asn1Exception: Identifier doesn't match
> expected value (906)
> > at
> org.apache.qpid.server.security.auth.manager.KerberosAuthenticationManagerTest.lambda$performNegotiation$0(KerberosAuthenticationManagerTest.java:245)
> > at
> org.apache.qpid.server.security.auth.manager.KerberosAuthenticationManagerTest.performNegotiation(KerberosAuthenticationManagerTest.java:242)
> > at
> org.apache.qpid.server.security.auth.manager.KerberosAuthenticationManagerTest.authenticate(KerberosAuthenticationManagerTest.java:212)
> > at
> org.apache.qpid.server.security.auth.manager.KerberosAuthenticationManagerTest.testCreateSaslNegotiator(KerberosAuthenticationManagerTest.java:137)
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
>
Re: [VOTE] Release Qpid Broker-J 8.0.0
Posted by Gordon Sim <gs...@redhat.com>.
On 11/03/2020 12:22 pm, Oleksandr Rudyy wrote:
> Gordon,
> Do you still see any test failures from test suites
> KerberosAuthenticationManagerTest and SpnegoAuthenticatorTest in your
> environment?
Yes:
> [ERROR] Tests run: 4, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.277 s <<< FAILURE! - in org.apache.qpid.server.security.auth.manager.KerberosAuthenticationManagerTest
> [ERROR] testCreateSaslNegotiator(org.apache.qpid.server.security.auth.manager.KerberosAuthenticationManagerTest) Time elapsed: 0.095 s <<< ERROR!
> java.security.PrivilegedActionException
> at org.apache.qpid.server.security.auth.manager.KerberosAuthenticationManagerTest.performNegotiation(KerberosAuthenticationManagerTest.java:242)
> at org.apache.qpid.server.security.auth.manager.KerberosAuthenticationManagerTest.authenticate(KerberosAuthenticationManagerTest.java:212)
> at org.apache.qpid.server.security.auth.manager.KerberosAuthenticationManagerTest.testCreateSaslNegotiator(KerberosAuthenticationManagerTest.java:137)
> Caused by: javax.security.sasl.SaslException: GSS initiate failed
> at org.apache.qpid.server.security.auth.manager.KerberosAuthenticationManagerTest.lambda$performNegotiation$0(KerberosAuthenticationManagerTest.java:245)
> at org.apache.qpid.server.security.auth.manager.KerberosAuthenticationManagerTest.performNegotiation(KerberosAuthenticationManagerTest.java:242)
> at org.apache.qpid.server.security.auth.manager.KerberosAuthenticationManagerTest.authenticate(KerberosAuthenticationManagerTest.java:212)
> at org.apache.qpid.server.security.auth.manager.KerberosAuthenticationManagerTest.testCreateSaslNegotiator(KerberosAuthenticationManagerTest.java:137)
> Caused by: org.ietf.jgss.GSSException: No valid credentials provided (Mechanism level: Server not found in Kerberos database (7) - Server not found in Kerberos database)
> at org.apache.qpid.server.security.auth.manager.KerberosAuthenticationManagerTest.lambda$performNegotiation$0(KerberosAuthenticationManagerTest.java:245)
> at org.apache.qpid.server.security.auth.manager.KerberosAuthenticationManagerTest.performNegotiation(KerberosAuthenticationManagerTest.java:242)
> at org.apache.qpid.server.security.auth.manager.KerberosAuthenticationManagerTest.authenticate(KerberosAuthenticationManagerTest.java:212)
> at org.apache.qpid.server.security.auth.manager.KerberosAuthenticationManagerTest.testCreateSaslNegotiator(KerberosAuthenticationManagerTest.java:137)
> Caused by: sun.security.krb5.KrbException: Server not found in Kerberos database (7) - Server not found in Kerberos database
> at org.apache.qpid.server.security.auth.manager.KerberosAuthenticationManagerTest.lambda$performNegotiation$0(KerberosAuthenticationManagerTest.java:245)
> at org.apache.qpid.server.security.auth.manager.KerberosAuthenticationManagerTest.performNegotiation(KerberosAuthenticationManagerTest.java:242)
> at org.apache.qpid.server.security.auth.manager.KerberosAuthenticationManagerTest.authenticate(KerberosAuthenticationManagerTest.java:212)
> at org.apache.qpid.server.security.auth.manager.KerberosAuthenticationManagerTest.testCreateSaslNegotiator(KerberosAuthenticationManagerTest.java:137)
> Caused by: sun.security.krb5.Asn1Exception: Identifier doesn't match expected value (906)
> at org.apache.qpid.server.security.auth.manager.KerberosAuthenticationManagerTest.lambda$performNegotiation$0(KerberosAuthenticationManagerTest.java:245)
> at org.apache.qpid.server.security.auth.manager.KerberosAuthenticationManagerTest.performNegotiation(KerberosAuthenticationManagerTest.java:242)
> at org.apache.qpid.server.security.auth.manager.KerberosAuthenticationManagerTest.authenticate(KerberosAuthenticationManagerTest.java:212)
> at org.apache.qpid.server.security.auth.manager.KerberosAuthenticationManagerTest.testCreateSaslNegotiator(KerberosAuthenticationManagerTest.java:137)
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: [VOTE] Release Qpid Broker-J 8.0.0
Posted by Oleksandr Rudyy <or...@gmail.com>.
Hi Gordon,
Thanks for reporting the issues with the tests.
* InMemoryDatabaseTestBase is an abstract class not containing any test.
Thus, its execution should fail with "no runnable methods".
* The test
MalformedMessage#publishMalformedMessageInTransactionExceedingMaxUncommittedLimit
should be skipped for the memory message store (default). I added a
corresponding change in commit fe3883045490d811150b19bbe81a261d3299a568
Gordon,
Do you still see any test failures from test suites
KerberosAuthenticationManagerTest and SpnegoAuthenticatorTest in your
environment?
After upgrading a kerby test dependency to 2.0, I have not seen any test
failures previously reported by you:
> [ERROR] Errors:
> [ERROR]
KerberosAuthenticationManagerTest.testCreateSaslNegotiator:133->authenticate:205->performNegotiation:226
» PrivilegedAction
> [ERROR] SpnegoAuthenticatorTest.testAuthenticate:99->buildToken:175 »
GSS No valid cre...
> [ERROR]
SpnegoAuthenticatorTest.testAuthenticateNoNegotiatePrefix:126->buildToken:175
» GSS
> [ERROR]
SpnegoAuthenticatorTest.testAuthenticateWrongConfigName:154->buildToken:175
» GSS
> [ERROR]
SpnegoAuthenticatorTest.testAuthenticateWrongServer:165->buildToken:175 »
GSS ...
> [INFO]
> [ERROR] Tests run: 1385, Failures: 0, Errors: 5, Skipped: 15
Could you please clarify?
Kind Regards,
Alex
On Tue, 10 Mar 2020 at 16:45, Gordon Sim <gs...@redhat.com> wrote:
> On 04/03/2020 11:44 am, Alex Rudyy wrote:
> > Hi all,
> >
> > I built release artefacts for Qpid Broker-J version 8.0.0 RC1.
> > Please, give them a test out and vote accordingly.
> >
> > The source and binary archives can be found at:
> > https://dist.apache.org/repos/dist/dev/qpid/broker-j/8.0.0-rc1/
> >
> > The maven artifacts are also staged at:
> > https://repository.apache.org/content/repositories/orgapacheqpid-1192
> >
> > The new version brings a number of improvements and bug fixes
> > including changes to ACL to limit the number of connections per user
> > and support for trusted CA revocation list.
> >
> > You can find the full list of JIRAs included into the release here:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310520&version=12344778
>
> Verified signature and checksum, built from source, ran tests (see
> below) and ran c++ qpid::messaging and python proton examples against it
> without issue.
>
> However I did get a few errors running the tests. As well as the
> kerberos related ones mentioned for previous releases, which are somehow
> a result of my environment, this time I got:
>
> > [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed:
> 0.004 s <<< FAILURE! - in
> org.apache.qpid.server.logging.logback.jdbc.InMemoryDatabaseTestBase
> > [ERROR]
> initializationError(org.apache.qpid.server.logging.logback.jdbc.InMemoryDatabaseTestBase)
> Time elapsed: 0.004 s <<< ERROR!
> > org.junit.runners.model.InvalidTestClassError:
> > Invalid test class
> 'org.apache.qpid.server.logging.logback.jdbc.InMemoryDatabaseTestBase':
> > 1. No runnable methods
>
> and:
>
> > [ERROR] Tests run: 5, Failures: 0, Errors: 1, Skipped: 0, Time elapsed:
> 1.028 s <<< FAILURE! - in
> org.apache.qpid.tests.protocol.v0_8.extension.basic.MalformedMessage
> > [ERROR]
> publishMalformedMessageInTransactionExceedingMaxUncommittedLimit(org.apache.qpid.tests.protocol.v0_8.extension.basic.MalformedMessage)
> Time elapsed: 0.017 s <<< ERROR!
> > java.lang.IllegalStateException: Unexpected response. Expected
> 'ChannelClosedResponse' got '[TxCommitOkBody]'.
> > at
> org.apache.qpid.tests.protocol.v0_8.extension.basic.MalformedMessage.publishMalformedMessageInTransactionExceedingMaxUncommittedLimit(MalformedMessage.java:154)
>
> These may again be environmental.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
>
Re: [VOTE] Release Qpid Broker-J 8.0.0
Posted by Rob Godfrey <ro...@gmail.com>.
On Tue, 10 Mar 2020 at 18:09, Gordon Sim <gs...@redhat.com> wrote:
> On 10/03/2020 4:45 pm, Gordon Sim wrote:
> > On 04/03/2020 11:44 am, Alex Rudyy wrote:
> >> Hi all,
> >>
> >> I built release artefacts for Qpid Broker-J version 8.0.0 RC1.
> >> Please, give them a test out and vote accordingly.
> >>
> >> The source and binary archives can be found at:
> >> https://dist.apache.org/repos/dist/dev/qpid/broker-j/8.0.0-rc1/
> >>
> >> The maven artifacts are also staged at:
> >> https://repository.apache.org/content/repositories/orgapacheqpid-1192
> >>
> >> The new version brings a number of improvements and bug fixes
> >> including changes to ACL to limit the number of connections per user
> >> and support for trusted CA revocation list.
> >>
> >> You can find the full list of JIRAs included into the release here:
> >>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310520&version=12344778
> >>
> >
> > Verified signature and checksum, built from source, ran tests (see
> > below) and ran c++ qpid::messaging and python proton examples against it
> > without issue.
>
> To be explicit, I am +1 on the release and only mention the issues below
> in passing.
>
+1 from me
Built from source, ran 1.0 and 0-9-1 tests
Used the management console for a bit of ad-hoc testing
-- Rob
>
>
> > However I did get a few errors running the tests. As well as the
> > kerberos related ones mentioned for previous releases, which are somehow
> > a result of my environment, this time I got:
> >
> >> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time
> >> elapsed: 0.004 s <<< FAILURE! - in
> >> org.apache.qpid.server.logging.logback.jdbc.InMemoryDatabaseTestBase
> >> [ERROR]
> >>
> initializationError(org.apache.qpid.server.logging.logback.jdbc.InMemoryDatabaseTestBase)
>
> >> Time elapsed: 0.004 s <<< ERROR!
> >> org.junit.runners.model.InvalidTestClassError: Invalid test class
> >> 'org.apache.qpid.server.logging.logback.jdbc.InMemoryDatabaseTestBase':
> >> 1. No runnable methods
> >
> > and:
> >
> >> [ERROR] Tests run: 5, Failures: 0, Errors: 1, Skipped: 0, Time
> >> elapsed: 1.028 s <<< FAILURE! - in
> >> org.apache.qpid.tests.protocol.v0_8.extension.basic.MalformedMessage
> >> [ERROR]
> >>
> publishMalformedMessageInTransactionExceedingMaxUncommittedLimit(org.apache.qpid.tests.protocol.v0_8.extension.basic.MalformedMessage)
>
> >> Time elapsed: 0.017 s <<< ERROR!
> >> java.lang.IllegalStateException: Unexpected response. Expected
> >> 'ChannelClosedResponse' got '[TxCommitOkBody]'.
> >> at
> >>
> org.apache.qpid.tests.protocol.v0_8.extension.basic.MalformedMessage.publishMalformedMessageInTransactionExceedingMaxUncommittedLimit(MalformedMessage.java:154)
>
> >>
> >
> > These may again be environmental.
> >
> >
> > ---------------------------------------------------------------------
> > 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 Qpid Broker-J 8.0.0
Posted by Gordon Sim <gs...@redhat.com>.
On 10/03/2020 4:45 pm, Gordon Sim wrote:
> On 04/03/2020 11:44 am, Alex Rudyy wrote:
>> Hi all,
>>
>> I built release artefacts for Qpid Broker-J version 8.0.0 RC1.
>> Please, give them a test out and vote accordingly.
>>
>> The source and binary archives can be found at:
>> https://dist.apache.org/repos/dist/dev/qpid/broker-j/8.0.0-rc1/
>>
>> The maven artifacts are also staged at:
>> https://repository.apache.org/content/repositories/orgapacheqpid-1192
>>
>> The new version brings a number of improvements and bug fixes
>> including changes to ACL to limit the number of connections per user
>> and support for trusted CA revocation list.
>>
>> You can find the full list of JIRAs included into the release here:
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310520&version=12344778
>>
>
> Verified signature and checksum, built from source, ran tests (see
> below) and ran c++ qpid::messaging and python proton examples against it
> without issue.
To be explicit, I am +1 on the release and only mention the issues below
in passing.
> However I did get a few errors running the tests. As well as the
> kerberos related ones mentioned for previous releases, which are somehow
> a result of my environment, this time I got:
>
>> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time
>> elapsed: 0.004 s <<< FAILURE! - in
>> org.apache.qpid.server.logging.logback.jdbc.InMemoryDatabaseTestBase
>> [ERROR]
>> initializationError(org.apache.qpid.server.logging.logback.jdbc.InMemoryDatabaseTestBase)
>> Time elapsed: 0.004 s <<< ERROR!
>> org.junit.runners.model.InvalidTestClassError: Invalid test class
>> 'org.apache.qpid.server.logging.logback.jdbc.InMemoryDatabaseTestBase':
>> 1. No runnable methods
>
> and:
>
>> [ERROR] Tests run: 5, Failures: 0, Errors: 1, Skipped: 0, Time
>> elapsed: 1.028 s <<< FAILURE! - in
>> org.apache.qpid.tests.protocol.v0_8.extension.basic.MalformedMessage
>> [ERROR]
>> publishMalformedMessageInTransactionExceedingMaxUncommittedLimit(org.apache.qpid.tests.protocol.v0_8.extension.basic.MalformedMessage)
>> Time elapsed: 0.017 s <<< ERROR!
>> java.lang.IllegalStateException: Unexpected response. Expected
>> 'ChannelClosedResponse' got '[TxCommitOkBody]'.
>> at
>> org.apache.qpid.tests.protocol.v0_8.extension.basic.MalformedMessage.publishMalformedMessageInTransactionExceedingMaxUncommittedLimit(MalformedMessage.java:154)
>>
>
> These may again be environmental.
>
>
> ---------------------------------------------------------------------
> 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 Qpid Broker-J 8.0.0
Posted by Gordon Sim <gs...@redhat.com>.
On 04/03/2020 11:44 am, Alex Rudyy wrote:
> Hi all,
>
> I built release artefacts for Qpid Broker-J version 8.0.0 RC1.
> Please, give them a test out and vote accordingly.
>
> The source and binary archives can be found at:
> https://dist.apache.org/repos/dist/dev/qpid/broker-j/8.0.0-rc1/
>
> The maven artifacts are also staged at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1192
>
> The new version brings a number of improvements and bug fixes
> including changes to ACL to limit the number of connections per user
> and support for trusted CA revocation list.
>
> You can find the full list of JIRAs included into the release here:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310520&version=12344778
Verified signature and checksum, built from source, ran tests (see
below) and ran c++ qpid::messaging and python proton examples against it
without issue.
However I did get a few errors running the tests. As well as the
kerberos related ones mentioned for previous releases, which are somehow
a result of my environment, this time I got:
> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.004 s <<< FAILURE! - in org.apache.qpid.server.logging.logback.jdbc.InMemoryDatabaseTestBase
> [ERROR] initializationError(org.apache.qpid.server.logging.logback.jdbc.InMemoryDatabaseTestBase) Time elapsed: 0.004 s <<< ERROR!
> org.junit.runners.model.InvalidTestClassError:
> Invalid test class 'org.apache.qpid.server.logging.logback.jdbc.InMemoryDatabaseTestBase':
> 1. No runnable methods
and:
> [ERROR] Tests run: 5, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.028 s <<< FAILURE! - in org.apache.qpid.tests.protocol.v0_8.extension.basic.MalformedMessage
> [ERROR] publishMalformedMessageInTransactionExceedingMaxUncommittedLimit(org.apache.qpid.tests.protocol.v0_8.extension.basic.MalformedMessage) Time elapsed: 0.017 s <<< ERROR!
> java.lang.IllegalStateException: Unexpected response. Expected 'ChannelClosedResponse' got '[TxCommitOkBody]'.
> at org.apache.qpid.tests.protocol.v0_8.extension.basic.MalformedMessage.publishMalformedMessageInTransactionExceedingMaxUncommittedLimit(MalformedMessage.java:154)
These may again be environmental.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: [VOTE] Release Qpid Broker-J 8.0.0
Posted by Robbie Gemmell <ro...@gmail.com>.
On Wed, 4 Mar 2020 at 11:44, Alex Rudyy <or...@apache.org> wrote:
>
> Hi all,
>
> I built release artefacts for Qpid Broker-J version 8.0.0 RC1.
> Please, give them a test out and vote accordingly.
>
> The source and binary archives can be found at:
> https://dist.apache.org/repos/dist/dev/qpid/broker-j/8.0.0-rc1/
>
> The maven artifacts are also staged at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1192
>
> The new version brings a number of improvements and bug fixes
> including changes to ACL to limit the number of connections per user
> and support for trusted CA revocation list.
>
> You can find the full list of JIRAs included into the release here:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310520&version=12344778
>
> Kind Regards,
> Alex
>
> P.S. For testing of maven broker staging repo artefacts, please add into to
> your project pom the staging repo as below:
>
> <repositories>
> <repository>
> <id>staging</id>
> <url>
> https://repository.apache.org/content/repositories/orgapacheqpid-1192</url>
> </repository>
> </repositories>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
+1
I checked things over as so:
- Verified the signature + checksum files.
- Ran mvn apache-rat:check to check headers in the source archive.
- Checked for LICENCE and NOTICE files present in the archives.
- Ran the build+tests with "mvn clean verify -DskipITs=false" on JDK 8 + 11.
- Started brokers from the binary archive and created a queue using the
web console, on JDK 8 + 11.
- Ran Qpid JMS 0.49.0 HelloWorld example against the brokers on JDK 8 + 11.
Robbie
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: [VOTE] Release Qpid Broker-J 8.0.0
Posted by Vavricka <va...@gmail.com>.
+1
* built from source
* executed system and integration tests
* installed broker with BDB store
* * added broker objects (queues/exchanges/ports/...) via REST API
* * password and external authentication
* * send and receive
* * message recovery after broker restart
* * ACL rights
Tomas
--
Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org