[VOTE] Release Qpid Broker-J 7.0.8

classic Classic list List threaded Threaded
18 messages Options
Reply | Threaded
Open this post in threaded view
|

[VOTE] Release Qpid Broker-J 7.0.8

orudyy
Hi folks,

I built release artefacts for Qpid Broker-J version 7.0.8 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/7.0.8-rc1/

The maven artifacts are also staged at:
https://repository.apache.org/content/repositories/orgapacheqpid-1180

The new version incorporates a number of improvements and bug fixes.
You can find the full list of JIRAs included into the release here:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310520&version=12345043

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-1180</url>
    </repository>
</repositories>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Qpid Broker-J 7.0.8

Oleksandr Rudyy
+1

My tests included the following
* verified checksums and signatures
* built and ran tests from source bundle
* started broker and used web management console to create bind queue
* used hello world application to publish and consume messages

On Wed, 3 Jul 2019 at 14:07, Alex Rudyy <[hidden email]> wrote:

> Hi folks,
>
> I built release artefacts for Qpid Broker-J version 7.0.8 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/7.0.8-rc1/
>
> The maven artifacts are also staged at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1180
>
> The new version incorporates a number of improvements and bug fixes.
> You can find the full list of JIRAs included into the release here:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310520&version=12345043
>
> 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-1180
> </url>
>     </repository>
> </repositories>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Qpid Broker-J 7.0.8

Robbie Gemmell
Administrator
In reply to this post by orudyy
On Wed, 3 Jul 2019 at 14:07, Alex Rudyy <[hidden email]> wrote:

>
> Hi folks,
>
> I built release artefacts for Qpid Broker-J version 7.0.8 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/7.0.8-rc1/
>
> The maven artifacts are also staged at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1180
>
> The new version incorporates a number of improvements and bug fixes.
> You can find the full list of JIRAs included into the release here:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310520&version=12345043
>
> 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-1180</url>
>     </repository>
> </repositories>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]

+1

I checked things over like so:
- Verified the signature and checksum files.
- Ran "mvn apache-rat:check" to verify headers in the source archive.
- Checked for LICENCE + NOTICE files present in the archives.
- Ran the build + tests with "mvn clean verify -DskipITs=false" on JDK 8.
- Started a broker using the binary archive, created queue with the console.
- Ran the Qpid JMS 0.44.0 HelloWorld example against the broker.

Robbie

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Qpid Broker-J 7.0.8

Gordon Sim
In reply to this post by orudyy
On 03/07/2019 2:07 pm, Alex Rudyy wrote:
> Hi folks,
>
> I built release artefacts for Qpid Broker-J version 7.0.8 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/7.0.8-rc1/

I'm seeing a test failure:

> Tests run: 6, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 9.073 sec <<< FAILURE! - in org.apache.qpid.tests.protocol.v1_0.transport.connection.OpenTest
> failOpenOnNonExistingHostname(org.apache.qpid.tests.protocol.v1_0.transport.connection.OpenTest)  Time elapsed: 6.019 sec  <<< ERROR!
> java.lang.IllegalStateException: Unexpected response. Expected one of '[]' got 'null'.
> at org.apache.qpid.tests.protocol.v1_0.transport.connection.OpenTest.failOpenOnNonExistingHostname(OpenTest.java:184)
>

This is with openjdk version "1.8.0_191"

Other than that all is good, the other tests pass and I succesfully ran
the same examples as for 7.1.4. If the above is likely to be
environmental and not a blocker (for which I would defer to Alex), I
vote +1.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Qpid Broker-J 7.0.8

Oleksandr Rudyy
Hi Gordon,

Thanks for testing the release and reporting a test failure.

The failed test sends open performative against non existing virtual host
and expects to receive an "open" back containing an error "amqp:not-found"
within 6 seconds after sending "open".
The failure occurred because "open" was not received within 6 seconds. It
could be environmental. For example, a long GC "stop the world" pause can
cause it, or, environment in use could be slow.

The test logs could provide more details about test execution.

If you still have a test log file
./systests/protocol-tests-amqp-1-0/target/surefire-reports/java-mms.1-0/TEST-org.apache.qpid.tests.protocol.v1_0.transport.connection.OpenTest.failOpenOnNonExistingHostname.txt,
could you please send it over?

Kind Regards,
Alex

On Thu, 4 Jul 2019 at 18:01, Gordon Sim <[hidden email]> wrote:

> On 03/07/2019 2:07 pm, Alex Rudyy wrote:
> > Hi folks,
> >
> > I built release artefacts for Qpid Broker-J version 7.0.8 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/7.0.8-rc1/
>
> I'm seeing a test failure:
>
> > Tests run: 6, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 9.073
> sec <<< FAILURE! - in
> org.apache.qpid.tests.protocol.v1_0.transport.connection.OpenTest
> >
> failOpenOnNonExistingHostname(org.apache.qpid.tests.protocol.v1_0.transport.connection.OpenTest)
> Time elapsed: 6.019 sec  <<< ERROR!
> > java.lang.IllegalStateException: Unexpected response. Expected one of
> '[]' got 'null'.
> >       at
> org.apache.qpid.tests.protocol.v1_0.transport.connection.OpenTest.failOpenOnNonExistingHostname(OpenTest.java:184)
> >
>
> This is with openjdk version "1.8.0_191"
>
> Other than that all is good, the other tests pass and I succesfully ran
> the same examples as for 7.1.4. If the above is likely to be
> environmental and not a blocker (for which I would defer to Alex), I
> vote +1.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Qpid Broker-J 7.0.8

Gordon Sim
On 05/07/2019 9:26 am, Oleksandr Rudyy wrote:

> Hi Gordon,
>
> Thanks for testing the release and reporting a test failure.
>
> The failed test sends open performative against non existing virtual host
> and expects to receive an "open" back containing an error "amqp:not-found"
> within 6 seconds after sending "open".
> The failure occurred because "open" was not received within 6 seconds. It
> could be environmental. For example, a long GC "stop the world" pause can
> cause it, or, environment in use could be slow.
I did run all the tests a second time and again it failed on that
specific test only. (Not that that necessarily rules out your hypothesis)

> The test logs could provide more details about test execution.
>
> If you still have a test log file
> ./systests/protocol-tests-amqp-1-0/target/surefire-reports/java-mms.1-0/TEST-org.apache.qpid.tests.protocol.v1_0.transport.connection.OpenTest.failOpenOnNonExistingHostname.txt,
> could you please send it over?

Attached


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

TEST-org.apache.qpid.tests.protocol.v1_0.transport.connection.OpenTest.failOpenOnNonExistingHostname.txt (2K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Qpid Broker-J 7.0.8

rgodfrey
On Fri, 5 Jul 2019 at 10:54, Gordon Sim <[hidden email]> wrote:

> On 05/07/2019 9:26 am, Oleksandr Rudyy wrote:
> > Hi Gordon,
> >
> > Thanks for testing the release and reporting a test failure.
> >
> > The failed test sends open performative against non existing virtual host
> > and expects to receive an "open" back containing an error
> "amqp:not-found"
> > within 6 seconds after sending "open".
> > The failure occurred because "open" was not received within 6 seconds. It
> > could be environmental. For example, a long GC "stop the world" pause can
> > cause it, or, environment in use could be slow.
>
> I did run all the tests a second time and again it failed on that
> specific test only. (Not that that necessarily rules out your hypothesis)
>

I am also seeing this error on this test (MacOs 10.14 Mojave, jdk 1.8.0_74)

-- Rob


>
> > The test logs could provide more details about test execution.
> >
> > If you still have a test log file
> >
> ./systests/protocol-tests-amqp-1-0/target/surefire-reports/java-mms.1-0/TEST-org.apache.qpid.tests.protocol.v1_0.transport.connection.OpenTest.failOpenOnNonExistingHostname.txt,
> > could you please send it over?
>
> Attached
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Qpid Broker-J 7.0.8

Oleksandr Rudyy
In reply to this post by Gordon Sim
Gordon,

Thanks for the logs. Though, there is nothing interesting there which would
shed light over the failure cause.

The log file contain a record for receiving OPEN performative, and, after
that, in 6 seconds the test fails.

Rob reported QPID-8150 [1] about issues with time taken by hostname
resolution. There are port host aliases configured in broker configuration
which are resolving host names. On some environments it take a lot of time.
  It could be potential reason for the test failure.

What is your environment?

You can remove the hostname alias entry from the broker test configuration
to make sure that it does not impact the test.

The diff is below

$ git diff
diff --git
a/systests/protocol-tests-amqp-1-0/src/main/resources/config-protocol-tests.json
b/systests/protocol-tests-amqp-1-0/src/main/resources/config-protocol-tests.json
index 764ff891a..522fd5bea 100644
---
a/systests/protocol-tests-amqp-1-0/src/main/resources/config-protocol-tests.json
+++
b/systests/protocol-tests-amqp-1-0/src/main/resources/config-protocol-tests.json
@@ -47,9 +47,6 @@
     "virtualhostaliases" : [ {
       "name" : "defaultAlias",
       "type" : "defaultAlias"
-    }, {
-      "name" : "hostnameAlias",
-      "type" : "hostnameAlias"
     }, {
       "name" : "nameAlias",
       "type" : "nameAlias"
@@ -64,10 +61,6 @@
       "name" : "defaultAlias",
       "type" : "defaultAlias",
       "durable" : true
-    }, {
-      "name" : "hostnameAlias",
-      "type" : "hostnameAlias",
-      "durable" : true
     }, {
       "name" : "nameAlias",
       "type" : "nameAlias",


I hope that the above should fix the issue.

Kind Regards,
Alex

[1] https://issues.apache.org/jira/browse/QPID-8150


On Fri, 5 Jul 2019 at 09:54, Gordon Sim <[hidden email]> wrote:

> On 05/07/2019 9:26 am, Oleksandr Rudyy wrote:
> > Hi Gordon,
> >
> > Thanks for testing the release and reporting a test failure.
> >
> > The failed test sends open performative against non existing virtual host
> > and expects to receive an "open" back containing an error
> "amqp:not-found"
> > within 6 seconds after sending "open".
> > The failure occurred because "open" was not received within 6 seconds. It
> > could be environmental. For example, a long GC "stop the world" pause can
> > cause it, or, environment in use could be slow.
>
> I did run all the tests a second time and again it failed on that
> specific test only. (Not that that necessarily rules out your hypothesis)
>
> > The test logs could provide more details about test execution.
> >
> > If you still have a test log file
> >
> ./systests/protocol-tests-amqp-1-0/target/surefire-reports/java-mms.1-0/TEST-org.apache.qpid.tests.protocol.v1_0.transport.connection.OpenTest.failOpenOnNonExistingHostname.txt,
> > could you please send it over?
>
> Attached
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Qpid Broker-J 7.0.8

rgodfrey
Hi Alex,

thanks for finding that JIRA for me - I knew that I'd fixed this at some
point in the past.

Just to confirm that that fixes the test for me.  So I'm +1 on the release
(perhaps we should apply that fix to the 7.0.x branch in case we do any
more releases from there)

Build from src, ran tests (passing with the fix to the test configuration
applied)
Started the broker and tested the web console.

-- Rob


On Fri, 5 Jul 2019 at 12:09, Oleksandr Rudyy <[hidden email]> wrote:

> Gordon,
>
> Thanks for the logs. Though, there is nothing interesting there which would
> shed light over the failure cause.
>
> The log file contain a record for receiving OPEN performative, and, after
> that, in 6 seconds the test fails.
>
> Rob reported QPID-8150 [1] about issues with time taken by hostname
> resolution. There are port host aliases configured in broker configuration
> which are resolving host names. On some environments it take a lot of time.
>   It could be potential reason for the test failure.
>
> What is your environment?
>
> You can remove the hostname alias entry from the broker test configuration
> to make sure that it does not impact the test.
>
> The diff is below
>
> $ git diff
> diff --git
>
> a/systests/protocol-tests-amqp-1-0/src/main/resources/config-protocol-tests.json
>
> b/systests/protocol-tests-amqp-1-0/src/main/resources/config-protocol-tests.json
> index 764ff891a..522fd5bea 100644
> ---
>
> a/systests/protocol-tests-amqp-1-0/src/main/resources/config-protocol-tests.json
> +++
>
> b/systests/protocol-tests-amqp-1-0/src/main/resources/config-protocol-tests.json
> @@ -47,9 +47,6 @@
>      "virtualhostaliases" : [ {
>        "name" : "defaultAlias",
>        "type" : "defaultAlias"
> -    }, {
> -      "name" : "hostnameAlias",
> -      "type" : "hostnameAlias"
>      }, {
>        "name" : "nameAlias",
>        "type" : "nameAlias"
> @@ -64,10 +61,6 @@
>        "name" : "defaultAlias",
>        "type" : "defaultAlias",
>        "durable" : true
> -    }, {
> -      "name" : "hostnameAlias",
> -      "type" : "hostnameAlias",
> -      "durable" : true
>      }, {
>        "name" : "nameAlias",
>        "type" : "nameAlias",
>
>
> I hope that the above should fix the issue.
>
> Kind Regards,
> Alex
>
> [1] https://issues.apache.org/jira/browse/QPID-8150
>
>
> On Fri, 5 Jul 2019 at 09:54, Gordon Sim <[hidden email]> wrote:
>
> > On 05/07/2019 9:26 am, Oleksandr Rudyy wrote:
> > > Hi Gordon,
> > >
> > > Thanks for testing the release and reporting a test failure.
> > >
> > > The failed test sends open performative against non existing virtual
> host
> > > and expects to receive an "open" back containing an error
> > "amqp:not-found"
> > > within 6 seconds after sending "open".
> > > The failure occurred because "open" was not received within 6 seconds.
> It
> > > could be environmental. For example, a long GC "stop the world" pause
> can
> > > cause it, or, environment in use could be slow.
> >
> > I did run all the tests a second time and again it failed on that
> > specific test only. (Not that that necessarily rules out your hypothesis)
> >
> > > The test logs could provide more details about test execution.
> > >
> > > If you still have a test log file
> > >
> >
> ./systests/protocol-tests-amqp-1-0/target/surefire-reports/java-mms.1-0/TEST-org.apache.qpid.tests.protocol.v1_0.transport.connection.OpenTest.failOpenOnNonExistingHostname.txt,
> > > could you please send it over?
> >
> > Attached
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
>
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Qpid Broker-J 7.0.8

Oleksandr Rudyy
Hi Rob,

Thanks for confirmation.
I will port QPID-8150 changes into the 7.0.x branch. Somehow, I missed to
merge them into 7.0 :(

Kind Regards,
Alex

On Fri, 5 Jul 2019 at 11:16, Rob Godfrey <[hidden email]> wrote:

> Hi Alex,
>
> thanks for finding that JIRA for me - I knew that I'd fixed this at some
> point in the past.
>
> Just to confirm that that fixes the test for me.  So I'm +1 on the release
> (perhaps we should apply that fix to the 7.0.x branch in case we do any
> more releases from there)
>
> Build from src, ran tests (passing with the fix to the test configuration
> applied)
> Started the broker and tested the web console.
>
> -- Rob
>
>
> On Fri, 5 Jul 2019 at 12:09, Oleksandr Rudyy <[hidden email]> wrote:
>
> > Gordon,
> >
> > Thanks for the logs. Though, there is nothing interesting there which
> would
> > shed light over the failure cause.
> >
> > The log file contain a record for receiving OPEN performative, and, after
> > that, in 6 seconds the test fails.
> >
> > Rob reported QPID-8150 [1] about issues with time taken by hostname
> > resolution. There are port host aliases configured in broker
> configuration
> > which are resolving host names. On some environments it take a lot of
> time.
> >   It could be potential reason for the test failure.
> >
> > What is your environment?
> >
> > You can remove the hostname alias entry from the broker test
> configuration
> > to make sure that it does not impact the test.
> >
> > The diff is below
> >
> > $ git diff
> > diff --git
> >
> >
> a/systests/protocol-tests-amqp-1-0/src/main/resources/config-protocol-tests.json
> >
> >
> b/systests/protocol-tests-amqp-1-0/src/main/resources/config-protocol-tests.json
> > index 764ff891a..522fd5bea 100644
> > ---
> >
> >
> a/systests/protocol-tests-amqp-1-0/src/main/resources/config-protocol-tests.json
> > +++
> >
> >
> b/systests/protocol-tests-amqp-1-0/src/main/resources/config-protocol-tests.json
> > @@ -47,9 +47,6 @@
> >      "virtualhostaliases" : [ {
> >        "name" : "defaultAlias",
> >        "type" : "defaultAlias"
> > -    }, {
> > -      "name" : "hostnameAlias",
> > -      "type" : "hostnameAlias"
> >      }, {
> >        "name" : "nameAlias",
> >        "type" : "nameAlias"
> > @@ -64,10 +61,6 @@
> >        "name" : "defaultAlias",
> >        "type" : "defaultAlias",
> >        "durable" : true
> > -    }, {
> > -      "name" : "hostnameAlias",
> > -      "type" : "hostnameAlias",
> > -      "durable" : true
> >      }, {
> >        "name" : "nameAlias",
> >        "type" : "nameAlias",
> >
> >
> > I hope that the above should fix the issue.
> >
> > Kind Regards,
> > Alex
> >
> > [1] https://issues.apache.org/jira/browse/QPID-8150
> >
> >
> > On Fri, 5 Jul 2019 at 09:54, Gordon Sim <[hidden email]> wrote:
> >
> > > On 05/07/2019 9:26 am, Oleksandr Rudyy wrote:
> > > > Hi Gordon,
> > > >
> > > > Thanks for testing the release and reporting a test failure.
> > > >
> > > > The failed test sends open performative against non existing virtual
> > host
> > > > and expects to receive an "open" back containing an error
> > > "amqp:not-found"
> > > > within 6 seconds after sending "open".
> > > > The failure occurred because "open" was not received within 6
> seconds.
> > It
> > > > could be environmental. For example, a long GC "stop the world" pause
> > can
> > > > cause it, or, environment in use could be slow.
> > >
> > > I did run all the tests a second time and again it failed on that
> > > specific test only. (Not that that necessarily rules out your
> hypothesis)
> > >
> > > > The test logs could provide more details about test execution.
> > > >
> > > > If you still have a test log file
> > > >
> > >
> >
> ./systests/protocol-tests-amqp-1-0/target/surefire-reports/java-mms.1-0/TEST-org.apache.qpid.tests.protocol.v1_0.transport.connection.OpenTest.failOpenOnNonExistingHostname.txt,
> > > > could you please send it over?
> > >
> > > Attached
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [hidden email]
> > > For additional commands, e-mail: [hidden email]
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Qpid Broker-J 7.0.8

rgodfrey
On Fri, 5 Jul 2019 at 12:19, Oleksandr Rudyy <[hidden email]> wrote:

> Hi Rob,
>
> Thanks for confirmation.
> I will port QPID-8150 changes into the 7.0.x branch. Somehow, I missed to
> merge them into 7.0 :(
>
>
I certainly don't think it is a blocker for this release, the test
"failure" is simply down to how long (failed) dns resolution takes on the
machine running the test.

-- Rob


> Kind Regards,
> Alex
>
> On Fri, 5 Jul 2019 at 11:16, Rob Godfrey <[hidden email]> wrote:
>
> > Hi Alex,
> >
> > thanks for finding that JIRA for me - I knew that I'd fixed this at some
> > point in the past.
> >
> > Just to confirm that that fixes the test for me.  So I'm +1 on the
> release
> > (perhaps we should apply that fix to the 7.0.x branch in case we do any
> > more releases from there)
> >
> > Build from src, ran tests (passing with the fix to the test configuration
> > applied)
> > Started the broker and tested the web console.
> >
> > -- Rob
> >
> >
> > On Fri, 5 Jul 2019 at 12:09, Oleksandr Rudyy <[hidden email]> wrote:
> >
> > > Gordon,
> > >
> > > Thanks for the logs. Though, there is nothing interesting there which
> > would
> > > shed light over the failure cause.
> > >
> > > The log file contain a record for receiving OPEN performative, and,
> after
> > > that, in 6 seconds the test fails.
> > >
> > > Rob reported QPID-8150 [1] about issues with time taken by hostname
> > > resolution. There are port host aliases configured in broker
> > configuration
> > > which are resolving host names. On some environments it take a lot of
> > time.
> > >   It could be potential reason for the test failure.
> > >
> > > What is your environment?
> > >
> > > You can remove the hostname alias entry from the broker test
> > configuration
> > > to make sure that it does not impact the test.
> > >
> > > The diff is below
> > >
> > > $ git diff
> > > diff --git
> > >
> > >
> >
> a/systests/protocol-tests-amqp-1-0/src/main/resources/config-protocol-tests.json
> > >
> > >
> >
> b/systests/protocol-tests-amqp-1-0/src/main/resources/config-protocol-tests.json
> > > index 764ff891a..522fd5bea 100644
> > > ---
> > >
> > >
> >
> a/systests/protocol-tests-amqp-1-0/src/main/resources/config-protocol-tests.json
> > > +++
> > >
> > >
> >
> b/systests/protocol-tests-amqp-1-0/src/main/resources/config-protocol-tests.json
> > > @@ -47,9 +47,6 @@
> > >      "virtualhostaliases" : [ {
> > >        "name" : "defaultAlias",
> > >        "type" : "defaultAlias"
> > > -    }, {
> > > -      "name" : "hostnameAlias",
> > > -      "type" : "hostnameAlias"
> > >      }, {
> > >        "name" : "nameAlias",
> > >        "type" : "nameAlias"
> > > @@ -64,10 +61,6 @@
> > >        "name" : "defaultAlias",
> > >        "type" : "defaultAlias",
> > >        "durable" : true
> > > -    }, {
> > > -      "name" : "hostnameAlias",
> > > -      "type" : "hostnameAlias",
> > > -      "durable" : true
> > >      }, {
> > >        "name" : "nameAlias",
> > >        "type" : "nameAlias",
> > >
> > >
> > > I hope that the above should fix the issue.
> > >
> > > Kind Regards,
> > > Alex
> > >
> > > [1] https://issues.apache.org/jira/browse/QPID-8150
> > >
> > >
> > > On Fri, 5 Jul 2019 at 09:54, Gordon Sim <[hidden email]> wrote:
> > >
> > > > On 05/07/2019 9:26 am, Oleksandr Rudyy wrote:
> > > > > Hi Gordon,
> > > > >
> > > > > Thanks for testing the release and reporting a test failure.
> > > > >
> > > > > The failed test sends open performative against non existing
> virtual
> > > host
> > > > > and expects to receive an "open" back containing an error
> > > > "amqp:not-found"
> > > > > within 6 seconds after sending "open".
> > > > > The failure occurred because "open" was not received within 6
> > seconds.
> > > It
> > > > > could be environmental. For example, a long GC "stop the world"
> pause
> > > can
> > > > > cause it, or, environment in use could be slow.
> > > >
> > > > I did run all the tests a second time and again it failed on that
> > > > specific test only. (Not that that necessarily rules out your
> > hypothesis)
> > > >
> > > > > The test logs could provide more details about test execution.
> > > > >
> > > > > If you still have a test log file
> > > > >
> > > >
> > >
> >
> ./systests/protocol-tests-amqp-1-0/target/surefire-reports/java-mms.1-0/TEST-org.apache.qpid.tests.protocol.v1_0.transport.connection.OpenTest.failOpenOnNonExistingHostname.txt,
> > > > > could you please send it over?
> > > >
> > > > Attached
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: [hidden email]
> > > > For additional commands, e-mail: [hidden email]
> > >
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Qpid Broker-J 7.0.8

Gordon Sim
In reply to this post by rgodfrey
On 05/07/2019 11:15 am, Rob Godfrey wrote:
> So I'm +1 on the release

Just to confirm I am also.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Qpid Broker-J 7.0.8

Oleksandr Rudyy
In reply to this post by rgodfrey
Rob,

I agree. It is definitely not a blocker for release.

Alex

On Fri, 5 Jul 2019 at 11:25, Rob Godfrey <[hidden email]> wrote:

> On Fri, 5 Jul 2019 at 12:19, Oleksandr Rudyy <[hidden email]> wrote:
>
> > Hi Rob,
> >
> > Thanks for confirmation.
> > I will port QPID-8150 changes into the 7.0.x branch. Somehow, I missed to
> > merge them into 7.0 :(
> >
> >
> I certainly don't think it is a blocker for this release, the test
> "failure" is simply down to how long (failed) dns resolution takes on the
> machine running the test.
>
> -- Rob
>
>
> > Kind Regards,
> > Alex
> >
> > On Fri, 5 Jul 2019 at 11:16, Rob Godfrey <[hidden email]>
> wrote:
> >
> > > Hi Alex,
> > >
> > > thanks for finding that JIRA for me - I knew that I'd fixed this at
> some
> > > point in the past.
> > >
> > > Just to confirm that that fixes the test for me.  So I'm +1 on the
> > release
> > > (perhaps we should apply that fix to the 7.0.x branch in case we do any
> > > more releases from there)
> > >
> > > Build from src, ran tests (passing with the fix to the test
> configuration
> > > applied)
> > > Started the broker and tested the web console.
> > >
> > > -- Rob
> > >
> > >
> > > On Fri, 5 Jul 2019 at 12:09, Oleksandr Rudyy <[hidden email]> wrote:
> > >
> > > > Gordon,
> > > >
> > > > Thanks for the logs. Though, there is nothing interesting there which
> > > would
> > > > shed light over the failure cause.
> > > >
> > > > The log file contain a record for receiving OPEN performative, and,
> > after
> > > > that, in 6 seconds the test fails.
> > > >
> > > > Rob reported QPID-8150 [1] about issues with time taken by hostname
> > > > resolution. There are port host aliases configured in broker
> > > configuration
> > > > which are resolving host names. On some environments it take a lot of
> > > time.
> > > >   It could be potential reason for the test failure.
> > > >
> > > > What is your environment?
> > > >
> > > > You can remove the hostname alias entry from the broker test
> > > configuration
> > > > to make sure that it does not impact the test.
> > > >
> > > > The diff is below
> > > >
> > > > $ git diff
> > > > diff --git
> > > >
> > > >
> > >
> >
> a/systests/protocol-tests-amqp-1-0/src/main/resources/config-protocol-tests.json
> > > >
> > > >
> > >
> >
> b/systests/protocol-tests-amqp-1-0/src/main/resources/config-protocol-tests.json
> > > > index 764ff891a..522fd5bea 100644
> > > > ---
> > > >
> > > >
> > >
> >
> a/systests/protocol-tests-amqp-1-0/src/main/resources/config-protocol-tests.json
> > > > +++
> > > >
> > > >
> > >
> >
> b/systests/protocol-tests-amqp-1-0/src/main/resources/config-protocol-tests.json
> > > > @@ -47,9 +47,6 @@
> > > >      "virtualhostaliases" : [ {
> > > >        "name" : "defaultAlias",
> > > >        "type" : "defaultAlias"
> > > > -    }, {
> > > > -      "name" : "hostnameAlias",
> > > > -      "type" : "hostnameAlias"
> > > >      }, {
> > > >        "name" : "nameAlias",
> > > >        "type" : "nameAlias"
> > > > @@ -64,10 +61,6 @@
> > > >        "name" : "defaultAlias",
> > > >        "type" : "defaultAlias",
> > > >        "durable" : true
> > > > -    }, {
> > > > -      "name" : "hostnameAlias",
> > > > -      "type" : "hostnameAlias",
> > > > -      "durable" : true
> > > >      }, {
> > > >        "name" : "nameAlias",
> > > >        "type" : "nameAlias",
> > > >
> > > >
> > > > I hope that the above should fix the issue.
> > > >
> > > > Kind Regards,
> > > > Alex
> > > >
> > > > [1] https://issues.apache.org/jira/browse/QPID-8150
> > > >
> > > >
> > > > On Fri, 5 Jul 2019 at 09:54, Gordon Sim <[hidden email]> wrote:
> > > >
> > > > > On 05/07/2019 9:26 am, Oleksandr Rudyy wrote:
> > > > > > Hi Gordon,
> > > > > >
> > > > > > Thanks for testing the release and reporting a test failure.
> > > > > >
> > > > > > The failed test sends open performative against non existing
> > virtual
> > > > host
> > > > > > and expects to receive an "open" back containing an error
> > > > > "amqp:not-found"
> > > > > > within 6 seconds after sending "open".
> > > > > > The failure occurred because "open" was not received within 6
> > > seconds.
> > > > It
> > > > > > could be environmental. For example, a long GC "stop the world"
> > pause
> > > > can
> > > > > > cause it, or, environment in use could be slow.
> > > > >
> > > > > I did run all the tests a second time and again it failed on that
> > > > > specific test only. (Not that that necessarily rules out your
> > > hypothesis)
> > > > >
> > > > > > The test logs could provide more details about test execution.
> > > > > >
> > > > > > If you still have a test log file
> > > > > >
> > > > >
> > > >
> > >
> >
> ./systests/protocol-tests-amqp-1-0/target/surefire-reports/java-mms.1-0/TEST-org.apache.qpid.tests.protocol.v1_0.transport.connection.OpenTest.failOpenOnNonExistingHostname.txt,
> > > > > > could you please send it over?
> > > > >
> > > > > Attached
> > > > >
> > > > >
> ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: [hidden email]
> > > > > For additional commands, e-mail: [hidden email]
> > > >
> > >
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Qpid Broker-J 7.0.8

Robbie Gemmell
Administrator
In reply to this post by Oleksandr Rudyy
FWIW the test is passing for me on two different Fedora systems with
OpenJDK 1.8.0_212 and Oracle JDK 1.8.0_181, but the log does suggest
an issue which could very well be the one you point to. Especially
since the JIRA is marked fixed in 7.1.0 and so could also explain any
difference from the 7.1.4 release under vote if the test hasnt changed
between the branches. Though oddly, Gordon and Rob have tested 7.0.x
before and not reported this issue, so is it a new test?

Robbie

On Fri, 5 Jul 2019 at 11:09, Oleksandr Rudyy <[hidden email]> wrote:

>
> Gordon,
>
> Thanks for the logs. Though, there is nothing interesting there which would
> shed light over the failure cause.
>
> The log file contain a record for receiving OPEN performative, and, after
> that, in 6 seconds the test fails.
>
> Rob reported QPID-8150 [1] about issues with time taken by hostname
> resolution. There are port host aliases configured in broker configuration
> which are resolving host names. On some environments it take a lot of time.
>   It could be potential reason for the test failure.
>
> What is your environment?
>
> You can remove the hostname alias entry from the broker test configuration
> to make sure that it does not impact the test.
>
> The diff is below
>
> $ git diff
> diff --git
> a/systests/protocol-tests-amqp-1-0/src/main/resources/config-protocol-tests.json
> b/systests/protocol-tests-amqp-1-0/src/main/resources/config-protocol-tests.json
> index 764ff891a..522fd5bea 100644
> ---
> a/systests/protocol-tests-amqp-1-0/src/main/resources/config-protocol-tests.json
> +++
> b/systests/protocol-tests-amqp-1-0/src/main/resources/config-protocol-tests.json
> @@ -47,9 +47,6 @@
>      "virtualhostaliases" : [ {
>        "name" : "defaultAlias",
>        "type" : "defaultAlias"
> -    }, {
> -      "name" : "hostnameAlias",
> -      "type" : "hostnameAlias"
>      }, {
>        "name" : "nameAlias",
>        "type" : "nameAlias"
> @@ -64,10 +61,6 @@
>        "name" : "defaultAlias",
>        "type" : "defaultAlias",
>        "durable" : true
> -    }, {
> -      "name" : "hostnameAlias",
> -      "type" : "hostnameAlias",
> -      "durable" : true
>      }, {
>        "name" : "nameAlias",
>        "type" : "nameAlias",
>
>
> I hope that the above should fix the issue.
>
> Kind Regards,
> Alex
>
> [1] https://issues.apache.org/jira/browse/QPID-8150
>
>
> On Fri, 5 Jul 2019 at 09:54, Gordon Sim <[hidden email]> wrote:
>
> > On 05/07/2019 9:26 am, Oleksandr Rudyy wrote:
> > > Hi Gordon,
> > >
> > > Thanks for testing the release and reporting a test failure.
> > >
> > > The failed test sends open performative against non existing virtual host
> > > and expects to receive an "open" back containing an error
> > "amqp:not-found"
> > > within 6 seconds after sending "open".
> > > The failure occurred because "open" was not received within 6 seconds. It
> > > could be environmental. For example, a long GC "stop the world" pause can
> > > cause it, or, environment in use could be slow.
> >
> > I did run all the tests a second time and again it failed on that
> > specific test only. (Not that that necessarily rules out your hypothesis)
> >
> > > The test logs could provide more details about test execution.
> > >
> > > If you still have a test log file
> > >
> > ./systests/protocol-tests-amqp-1-0/target/surefire-reports/java-mms.1-0/TEST-org.apache.qpid.tests.protocol.v1_0.transport.connection.OpenTest.failOpenOnNonExistingHostname.txt,
> > > could you please send it over?
> >
> > Attached
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Qpid Broker-J 7.0.8

Robbie Gemmell
Administrator
..and now all the intermediate mails confirming the issue/fix before I
even typed this have arrived in my inbox...sigh :)

On Fri, 5 Jul 2019 at 11:30, Robbie Gemmell <[hidden email]> wrote:

>
> FWIW the test is passing for me on two different Fedora systems with
> OpenJDK 1.8.0_212 and Oracle JDK 1.8.0_181, but the log does suggest
> an issue which could very well be the one you point to. Especially
> since the JIRA is marked fixed in 7.1.0 and so could also explain any
> difference from the 7.1.4 release under vote if the test hasnt changed
> between the branches. Though oddly, Gordon and Rob have tested 7.0.x
> before and not reported this issue, so is it a new test?
>
> Robbie
>
> On Fri, 5 Jul 2019 at 11:09, Oleksandr Rudyy <[hidden email]> wrote:
> >
> > Gordon,
> >
> > Thanks for the logs. Though, there is nothing interesting there which would
> > shed light over the failure cause.
> >
> > The log file contain a record for receiving OPEN performative, and, after
> > that, in 6 seconds the test fails.
> >
> > Rob reported QPID-8150 [1] about issues with time taken by hostname
> > resolution. There are port host aliases configured in broker configuration
> > which are resolving host names. On some environments it take a lot of time.
> >   It could be potential reason for the test failure.
> >
> > What is your environment?
> >
> > You can remove the hostname alias entry from the broker test configuration
> > to make sure that it does not impact the test.
> >
> > The diff is below
> >
> > $ git diff
> > diff --git
> > a/systests/protocol-tests-amqp-1-0/src/main/resources/config-protocol-tests.json
> > b/systests/protocol-tests-amqp-1-0/src/main/resources/config-protocol-tests.json
> > index 764ff891a..522fd5bea 100644
> > ---
> > a/systests/protocol-tests-amqp-1-0/src/main/resources/config-protocol-tests.json
> > +++
> > b/systests/protocol-tests-amqp-1-0/src/main/resources/config-protocol-tests.json
> > @@ -47,9 +47,6 @@
> >      "virtualhostaliases" : [ {
> >        "name" : "defaultAlias",
> >        "type" : "defaultAlias"
> > -    }, {
> > -      "name" : "hostnameAlias",
> > -      "type" : "hostnameAlias"
> >      }, {
> >        "name" : "nameAlias",
> >        "type" : "nameAlias"
> > @@ -64,10 +61,6 @@
> >        "name" : "defaultAlias",
> >        "type" : "defaultAlias",
> >        "durable" : true
> > -    }, {
> > -      "name" : "hostnameAlias",
> > -      "type" : "hostnameAlias",
> > -      "durable" : true
> >      }, {
> >        "name" : "nameAlias",
> >        "type" : "nameAlias",
> >
> >
> > I hope that the above should fix the issue.
> >
> > Kind Regards,
> > Alex
> >
> > [1] https://issues.apache.org/jira/browse/QPID-8150
> >
> >
> > On Fri, 5 Jul 2019 at 09:54, Gordon Sim <[hidden email]> wrote:
> >
> > > On 05/07/2019 9:26 am, Oleksandr Rudyy wrote:
> > > > Hi Gordon,
> > > >
> > > > Thanks for testing the release and reporting a test failure.
> > > >
> > > > The failed test sends open performative against non existing virtual host
> > > > and expects to receive an "open" back containing an error
> > > "amqp:not-found"
> > > > within 6 seconds after sending "open".
> > > > The failure occurred because "open" was not received within 6 seconds. It
> > > > could be environmental. For example, a long GC "stop the world" pause can
> > > > cause it, or, environment in use could be slow.
> > >
> > > I did run all the tests a second time and again it failed on that
> > > specific test only. (Not that that necessarily rules out your hypothesis)
> > >
> > > > The test logs could provide more details about test execution.
> > > >
> > > > If you still have a test log file
> > > >
> > > ./systests/protocol-tests-amqp-1-0/target/surefire-reports/java-mms.1-0/TEST-org.apache.qpid.tests.protocol.v1_0.transport.connection.OpenTest.failOpenOnNonExistingHostname.txt,
> > > > could you please send it over?
> > >
> > > Attached
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [hidden email]
> > > For additional commands, e-mail: [hidden email]

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Qpid Broker-J 7.0.8

Oleksandr Rudyy
In reply to this post by Robbie Gemmell
Hi Robbie,
It is not a new test. It was there for ages.
I actually do not remember see it failing in my test environments which are
Fedora/RedHat based.
I suspect that Rob and Gordon could be testing previous releases in
different environments or host resolution happened before quicker (within 6
seconds test interval).

Anyway, if I ever build 7.0.9 release, the issue [1] will be resolved there.

Kind Regards,
Alex

[1] https://issues.apache.org/jira/browse/QPID-8338



On Fri, 5 Jul 2019 at 11:30, Robbie Gemmell <[hidden email]>
wrote:

> FWIW the test is passing for me on two different Fedora systems with
> OpenJDK 1.8.0_212 and Oracle JDK 1.8.0_181, but the log does suggest
> an issue which could very well be the one you point to. Especially
> since the JIRA is marked fixed in 7.1.0 and so could also explain any
> difference from the 7.1.4 release under vote if the test hasnt changed
> between the branches. Though oddly, Gordon and Rob have tested 7.0.x
> before and not reported this issue, so is it a new test?
>
> Robbie
>
> On Fri, 5 Jul 2019 at 11:09, Oleksandr Rudyy <[hidden email]> wrote:
> >
> > Gordon,
> >
> > Thanks for the logs. Though, there is nothing interesting there which
> would
> > shed light over the failure cause.
> >
> > The log file contain a record for receiving OPEN performative, and, after
> > that, in 6 seconds the test fails.
> >
> > Rob reported QPID-8150 [1] about issues with time taken by hostname
> > resolution. There are port host aliases configured in broker
> configuration
> > which are resolving host names. On some environments it take a lot of
> time.
> >   It could be potential reason for the test failure.
> >
> > What is your environment?
> >
> > You can remove the hostname alias entry from the broker test
> configuration
> > to make sure that it does not impact the test.
> >
> > The diff is below
> >
> > $ git diff
> > diff --git
> >
> a/systests/protocol-tests-amqp-1-0/src/main/resources/config-protocol-tests.json
> >
> b/systests/protocol-tests-amqp-1-0/src/main/resources/config-protocol-tests.json
> > index 764ff891a..522fd5bea 100644
> > ---
> >
> a/systests/protocol-tests-amqp-1-0/src/main/resources/config-protocol-tests.json
> > +++
> >
> b/systests/protocol-tests-amqp-1-0/src/main/resources/config-protocol-tests.json
> > @@ -47,9 +47,6 @@
> >      "virtualhostaliases" : [ {
> >        "name" : "defaultAlias",
> >        "type" : "defaultAlias"
> > -    }, {
> > -      "name" : "hostnameAlias",
> > -      "type" : "hostnameAlias"
> >      }, {
> >        "name" : "nameAlias",
> >        "type" : "nameAlias"
> > @@ -64,10 +61,6 @@
> >        "name" : "defaultAlias",
> >        "type" : "defaultAlias",
> >        "durable" : true
> > -    }, {
> > -      "name" : "hostnameAlias",
> > -      "type" : "hostnameAlias",
> > -      "durable" : true
> >      }, {
> >        "name" : "nameAlias",
> >        "type" : "nameAlias",
> >
> >
> > I hope that the above should fix the issue.
> >
> > Kind Regards,
> > Alex
> >
> > [1] https://issues.apache.org/jira/browse/QPID-8150
> >
> >
> > On Fri, 5 Jul 2019 at 09:54, Gordon Sim <[hidden email]> wrote:
> >
> > > On 05/07/2019 9:26 am, Oleksandr Rudyy wrote:
> > > > Hi Gordon,
> > > >
> > > > Thanks for testing the release and reporting a test failure.
> > > >
> > > > The failed test sends open performative against non existing virtual
> host
> > > > and expects to receive an "open" back containing an error
> > > "amqp:not-found"
> > > > within 6 seconds after sending "open".
> > > > The failure occurred because "open" was not received within 6
> seconds. It
> > > > could be environmental. For example, a long GC "stop the world"
> pause can
> > > > cause it, or, environment in use could be slow.
> > >
> > > I did run all the tests a second time and again it failed on that
> > > specific test only. (Not that that necessarily rules out your
> hypothesis)
> > >
> > > > The test logs could provide more details about test execution.
> > > >
> > > > If you still have a test log file
> > > >
> > >
> ./systests/protocol-tests-amqp-1-0/target/surefire-reports/java-mms.1-0/TEST-org.apache.qpid.tests.protocol.v1_0.transport.connection.OpenTest.failOpenOnNonExistingHostname.txt,
> > > > could you please send it over?
> > >
> > > Attached
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [hidden email]
> > > For additional commands, e-mail: [hidden email]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Qpid Broker-J 7.0.8

rgodfrey
In reply to this post by Robbie Gemmell
On Fri, 5 Jul 2019 at 12:30, Robbie Gemmell <[hidden email]>
wrote:

> FWIW the test is passing for me on two different Fedora systems with
> OpenJDK 1.8.0_212 and Oracle JDK 1.8.0_181, but the log does suggest
> an issue which could very well be the one you point to. Especially
> since the JIRA is marked fixed in 7.1.0 and so could also explain any
> difference from the 7.1.4 release under vote if the test hasnt changed
> between the branches. Though oddly, Gordon and Rob have tested 7.0.x
> before and not reported this issue, so is it a new test?
>

So the failure is completely environment dependent.  IIRC, for example, the
test passes when I'm on my UK ISP because it has a "broken" DNS resolver
that resolves unknown hostnames to their own IP address.  I've never had
the issue on Fedora, only on OS X.  I don't actually remember what I tested
7.0.7 on.  I remembered that I often got this error, and that I thought I
fixed it, but had forgotten the exact JIRA until Alex found it :-).


>
> Robbie
>
> On Fri, 5 Jul 2019 at 11:09, Oleksandr Rudyy <[hidden email]> wrote:
> >
> > Gordon,
> >
> > Thanks for the logs. Though, there is nothing interesting there which
> would
> > shed light over the failure cause.
> >
> > The log file contain a record for receiving OPEN performative, and, after
> > that, in 6 seconds the test fails.
> >
> > Rob reported QPID-8150 [1] about issues with time taken by hostname
> > resolution. There are port host aliases configured in broker
> configuration
> > which are resolving host names. On some environments it take a lot of
> time.
> >   It could be potential reason for the test failure.
> >
> > What is your environment?
> >
> > You can remove the hostname alias entry from the broker test
> configuration
> > to make sure that it does not impact the test.
> >
> > The diff is below
> >
> > $ git diff
> > diff --git
> >
> a/systests/protocol-tests-amqp-1-0/src/main/resources/config-protocol-tests.json
> >
> b/systests/protocol-tests-amqp-1-0/src/main/resources/config-protocol-tests.json
> > index 764ff891a..522fd5bea 100644
> > ---
> >
> a/systests/protocol-tests-amqp-1-0/src/main/resources/config-protocol-tests.json
> > +++
> >
> b/systests/protocol-tests-amqp-1-0/src/main/resources/config-protocol-tests.json
> > @@ -47,9 +47,6 @@
> >      "virtualhostaliases" : [ {
> >        "name" : "defaultAlias",
> >        "type" : "defaultAlias"
> > -    }, {
> > -      "name" : "hostnameAlias",
> > -      "type" : "hostnameAlias"
> >      }, {
> >        "name" : "nameAlias",
> >        "type" : "nameAlias"
> > @@ -64,10 +61,6 @@
> >        "name" : "defaultAlias",
> >        "type" : "defaultAlias",
> >        "durable" : true
> > -    }, {
> > -      "name" : "hostnameAlias",
> > -      "type" : "hostnameAlias",
> > -      "durable" : true
> >      }, {
> >        "name" : "nameAlias",
> >        "type" : "nameAlias",
> >
> >
> > I hope that the above should fix the issue.
> >
> > Kind Regards,
> > Alex
> >
> > [1] https://issues.apache.org/jira/browse/QPID-8150
> >
> >
> > On Fri, 5 Jul 2019 at 09:54, Gordon Sim <[hidden email]> wrote:
> >
> > > On 05/07/2019 9:26 am, Oleksandr Rudyy wrote:
> > > > Hi Gordon,
> > > >
> > > > Thanks for testing the release and reporting a test failure.
> > > >
> > > > The failed test sends open performative against non existing virtual
> host
> > > > and expects to receive an "open" back containing an error
> > > "amqp:not-found"
> > > > within 6 seconds after sending "open".
> > > > The failure occurred because "open" was not received within 6
> seconds. It
> > > > could be environmental. For example, a long GC "stop the world"
> pause can
> > > > cause it, or, environment in use could be slow.
> > >
> > > I did run all the tests a second time and again it failed on that
> > > specific test only. (Not that that necessarily rules out your
> hypothesis)
> > >
> > > > The test logs could provide more details about test execution.
> > > >
> > > > If you still have a test log file
> > > >
> > >
> ./systests/protocol-tests-amqp-1-0/target/surefire-reports/java-mms.1-0/TEST-org.apache.qpid.tests.protocol.v1_0.transport.connection.OpenTest.failOpenOnNonExistingHostname.txt,
> > > > could you please send it over?
> > >
> > > Attached
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [hidden email]
> > > For additional commands, e-mail: [hidden email]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Qpid Broker-J 7.0.8

Robbie Gemmell
Administrator
On Fri, 5 Jul 2019 at 12:55, Rob Godfrey <[hidden email]> wrote:

>
> On Fri, 5 Jul 2019 at 12:30, Robbie Gemmell <[hidden email]>
> wrote:
>
> > FWIW the test is passing for me on two different Fedora systems with
> > OpenJDK 1.8.0_212 and Oracle JDK 1.8.0_181, but the log does suggest
> > an issue which could very well be the one you point to. Especially
> > since the JIRA is marked fixed in 7.1.0 and so could also explain any
> > difference from the 7.1.4 release under vote if the test hasnt changed
> > between the branches. Though oddly, Gordon and Rob have tested 7.0.x
> > before and not reported this issue, so is it a new test?
> >
>
> So the failure is completely environment dependent.  IIRC, for example, the
> test passes when I'm on my UK ISP because it has a "broken" DNS resolver
> that resolves unknown hostnames to their own IP address.

Ah, good point. I also have that situation.

>  I've never had
> the issue on Fedora, only on OS X.  I don't actually remember what I tested
> 7.0.7 on.  I remembered that I often got this error, and that I thought I
> fixed it, but had forgotten the exact JIRA until Alex found it :-).
>
>
> >
> > Robbie
> >
> > On Fri, 5 Jul 2019 at 11:09, Oleksandr Rudyy <[hidden email]> wrote:
> > >
> > > Gordon,
> > >
> > > Thanks for the logs. Though, there is nothing interesting there which
> > would
> > > shed light over the failure cause.
> > >
> > > The log file contain a record for receiving OPEN performative, and, after
> > > that, in 6 seconds the test fails.
> > >
> > > Rob reported QPID-8150 [1] about issues with time taken by hostname
> > > resolution. There are port host aliases configured in broker
> > configuration
> > > which are resolving host names. On some environments it take a lot of
> > time.
> > >   It could be potential reason for the test failure.
> > >
> > > What is your environment?
> > >
> > > You can remove the hostname alias entry from the broker test
> > configuration
> > > to make sure that it does not impact the test.
> > >
> > > The diff is below
> > >
> > > $ git diff
> > > diff --git
> > >
> > a/systests/protocol-tests-amqp-1-0/src/main/resources/config-protocol-tests.json
> > >
> > b/systests/protocol-tests-amqp-1-0/src/main/resources/config-protocol-tests.json
> > > index 764ff891a..522fd5bea 100644
> > > ---
> > >
> > a/systests/protocol-tests-amqp-1-0/src/main/resources/config-protocol-tests.json
> > > +++
> > >
> > b/systests/protocol-tests-amqp-1-0/src/main/resources/config-protocol-tests.json
> > > @@ -47,9 +47,6 @@
> > >      "virtualhostaliases" : [ {
> > >        "name" : "defaultAlias",
> > >        "type" : "defaultAlias"
> > > -    }, {
> > > -      "name" : "hostnameAlias",
> > > -      "type" : "hostnameAlias"
> > >      }, {
> > >        "name" : "nameAlias",
> > >        "type" : "nameAlias"
> > > @@ -64,10 +61,6 @@
> > >        "name" : "defaultAlias",
> > >        "type" : "defaultAlias",
> > >        "durable" : true
> > > -    }, {
> > > -      "name" : "hostnameAlias",
> > > -      "type" : "hostnameAlias",
> > > -      "durable" : true
> > >      }, {
> > >        "name" : "nameAlias",
> > >        "type" : "nameAlias",
> > >
> > >
> > > I hope that the above should fix the issue.
> > >
> > > Kind Regards,
> > > Alex
> > >
> > > [1] https://issues.apache.org/jira/browse/QPID-8150
> > >
> > >
> > > On Fri, 5 Jul 2019 at 09:54, Gordon Sim <[hidden email]> wrote:
> > >
> > > > On 05/07/2019 9:26 am, Oleksandr Rudyy wrote:
> > > > > Hi Gordon,
> > > > >
> > > > > Thanks for testing the release and reporting a test failure.
> > > > >
> > > > > The failed test sends open performative against non existing virtual
> > host
> > > > > and expects to receive an "open" back containing an error
> > > > "amqp:not-found"
> > > > > within 6 seconds after sending "open".
> > > > > The failure occurred because "open" was not received within 6
> > seconds. It
> > > > > could be environmental. For example, a long GC "stop the world"
> > pause can
> > > > > cause it, or, environment in use could be slow.
> > > >
> > > > I did run all the tests a second time and again it failed on that
> > > > specific test only. (Not that that necessarily rules out your
> > hypothesis)
> > > >
> > > > > The test logs could provide more details about test execution.
> > > > >
> > > > > If you still have a test log file
> > > > >
> > > >
> > ./systests/protocol-tests-amqp-1-0/target/surefire-reports/java-mms.1-0/TEST-org.apache.qpid.tests.protocol.v1_0.transport.connection.OpenTest.failOpenOnNonExistingHostname.txt,
> > > > > could you please send it over?
> > > >
> > > > Attached
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: [hidden email]
> > > > For additional commands, e-mail: [hidden email]
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
> >

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]