Details

    • Type: Task Task
    • Status: Reopened
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: 5.9.0
    • Fix Version/s: 5.x
    • Component/s: None
    • Labels:
      None
    • Environment:

      Ubuntu 13.04, version: "3.8.0-26-generic", arch: "i386"
      OpenJDK 8b99
      Maven 3.1.0

      Description

      I've tried to make a build under OpenJDK 8b99 and I've got these testing errors:

      Running org.apache.activemq.transport.mqtt.MQTTNioTest
      Tests run: 18, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 162.262 sec <<< FAILURE!
      Running org.apache.activemq.transport.mqtt.MQTTSSLTest
      Tests run: 17, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 160.224 sec <<< FAILURE!
      Running org.apache.activemq.transport.mqtt.MQTTTest
      Tests run: 17, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 156.354 sec <<< FAILURE!

      Results :

      Tests in error:
      testPingOnMQTTNIO(org.apache.activemq.transport.mqtt.MQTTNioTest): The client id MUST be configured when clean session is set to false
      testReceiveMessageSentWhileOffline(org.apache.activemq.transport.mqtt.MQTTSSLTest): Command from server contained an invalid message id: 1
      testReceiveMessageSentWhileOffline(org.apache.activemq.transport.mqtt.MQTTTest): Command from server contained an invalid message id: 1

        Activity

        Hide
        Timothy Bish added a comment -

        This is not at all surprising since

        1. Java 8 is not released.
        2. We haven't built a broker with it or run test against it.

        Show
        Timothy Bish added a comment - This is not at all surprising since 1. Java 8 is not released. 2. We haven't built a broker with it or run test against it.
        Hide
        Timothy Bish added a comment -

        Java 8 isn't slated for release until next march, so at this point its a bit early to worry about test failures.

        Show
        Timothy Bish added a comment - Java 8 isn't slated for release until next march, so at this point its a bit early to worry about test failures.
        Hide
        Martijn Verburg added a comment -

        Hi Timothy,

        A volunteer group of technologists are testing major projects early with Java 8 to avoid situations like the Apache Lucene/Solr crashes when Java 7 first came out. You can see more details about this programme at https://java.net/projects/adoptopenjdk/pages/TestingJava8

        We'd be grateful if this issue could be re-opened so that we can track the general readiness of applications for Java 8 as the March date gets closer .

        Cheers,
        Martijn

        Show
        Martijn Verburg added a comment - Hi Timothy, A volunteer group of technologists are testing major projects early with Java 8 to avoid situations like the Apache Lucene/Solr crashes when Java 7 first came out. You can see more details about this programme at https://java.net/projects/adoptopenjdk/pages/TestingJava8 We'd be grateful if this issue could be re-opened so that we can track the general readiness of applications for Java 8 as the March date gets closer . Cheers, Martijn
        Hide
        Claus Ibsen added a comment -

        Martin, this sounds great. You could add Apache Camel to that list and it would test a lot of Java projects for you as we have 140+ components in Camel today.

        Show
        Claus Ibsen added a comment - Martin, this sounds great. You could add Apache Camel to that list and it would test a lot of Java projects for you as we have 140+ components in Camel today.
        Hide
        Claus Ibsen added a comment -

        Besides the MQTT test failures do you see others? You could try disabling the MQTT tests and see if other errors shows up?

        Show
        Claus Ibsen added a comment - Besides the MQTT test failures do you see others? You could try disabling the MQTT tests and see if other errors shows up?
        Hide
        Martijn Verburg added a comment -

        Thanks, we'll add Camel for sure! I think it was only the MQTT tests that failed, but I'll check with Greg.

        Show
        Martijn Verburg added a comment - Thanks, we'll add Camel for sure! I think it was only the MQTT tests that failed, but I'll check with Greg.
        Hide
        Greg Bakos added a comment -

        I've made a successful build with these Maven parameters:

        -e -X -Dtest=false -DfailIfNoTests=false clean install

        Show
        Greg Bakos added a comment - I've made a successful build with these Maven parameters: -e -X -Dtest=false -DfailIfNoTests=false clean install
        Hide
        Anuj Khandelwal added a comment -

        Since Java 8 is out now and ActiveMQ is still built with Java 7.
        When can we expect ActiveMQ compiled with java 8 ?

        Thanks,
        Anuj

        Show
        Anuj Khandelwal added a comment - Since Java 8 is out now and ActiveMQ is still built with Java 7. When can we expect ActiveMQ compiled with java 8 ? Thanks, Anuj
        Hide
        Timothy Bish added a comment -

        I think we can close this one now, the tests under Java 8 are have only failures that also occur under the Java 7 test run also so there's no Java specific issues there. The current and foreseeable future we are going to be building with Java 7.

        Show
        Timothy Bish added a comment - I think we can close this one now, the tests under Java 8 are have only failures that also occur under the Java 7 test run also so there's no Java specific issues there. The current and foreseeable future we are going to be building with Java 7.

          People

          • Assignee:
            Unassigned
            Reporter:
            Greg Bakos
          • Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

            • Created:
              Updated:

              Development