Uploaded image for project: 'Axis2'
  1. Axis2
  2. AXIS2-4696

Axis2 build broken on JDK 1.6 by r937604

        Details

        • Type: Bug
        • Status: Resolved
        • Priority: Minor
        • Resolution: Fixed
        • Affects Version/s: None
        • Fix Version/s: None
        • Component/s: None
        • Labels:
          None
        • Environment:

          Description

          If you build the latest revision of axis2 using JDK 1.6, there are 2 test failures in the jaxws-integration module:

          -------------------------------------------------------------------------------
          Test set: org.apache.axis2.jaxws.provider.AddressingProviderTests
          -------------------------------------------------------------------------------
          Tests run: 3, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 5.796 sec <<< FAILURE!
          testInjectAddressingHeaders(org.apache.axis2.jaxws.provider.AddressingProviderTests) Time elapsed: 0.672 sec <<< ERROR!
          javax.xml.ws.soap.SOAPFaultException: The [action] cannot be processed at the receiver.
          at org.apache.axis2.jaxws.marshaller.impl.alt.MethodMarshallerUtils.createSystemException(MethodMarshallerUtils.java:1326)
          at org.apache.axis2.jaxws.client.dispatch.BaseDispatch.getFaultResponse(BaseDispatch.java:618)
          at org.apache.axis2.jaxws.client.dispatch.BaseDispatch.invoke(BaseDispatch.java:186)
          at org.apache.axis2.jaxws.provider.AddressingProviderTests.testInjectAddressingHeaders(AddressingProviderTests.java:90)
          at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
          at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
          at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
          at java.lang.reflect.Method.invoke(Method.java:597)
          at junit.framework.TestCase.runTest(TestCase.java:168)
          at junit.framework.TestCase.runBare(TestCase.java:134)
          at junit.framework.TestResult$1.protect(TestResult.java:110)
          at junit.framework.TestResult.runProtected(TestResult.java:128)
          at junit.framework.TestResult.run(TestResult.java:113)
          at junit.framework.TestCase.run(TestCase.java:124)
          at junit.framework.TestSuite.runTest(TestSuite.java:232)
          at junit.framework.TestSuite.run(TestSuite.java:227)
          at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
          at junit.extensions.TestSetup$1.protect(TestSetup.java:23)
          at junit.framework.TestResult.runProtected(TestResult.java:128)
          at junit.extensions.TestSetup.run(TestSetup.java:27)
          at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:81)
          at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
          at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140)
          at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:165)
          at org.apache.maven.surefire.Surefire.run(Surefire.java:107)
          at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
          at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
          at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
          at java.lang.reflect.Method.invoke(Method.java:597)
          at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:289)
          at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:993)

          testWithAddressingHeaders(org.apache.axis2.jaxws.provider.AddressingProviderTests) Time elapsed: 0.047 sec <<< ERROR!
          javax.xml.ws.soap.SOAPFaultException: The [action] cannot be processed at the receiver.
          at org.apache.axis2.jaxws.marshaller.impl.alt.MethodMarshallerUtils.createSystemException(MethodMarshallerUtils.java:1326)
          at org.apache.axis2.jaxws.client.dispatch.BaseDispatch.getFaultResponse(BaseDispatch.java:618)
          at org.apache.axis2.jaxws.client.dispatch.BaseDispatch.invoke(BaseDispatch.java:186)
          at org.apache.axis2.jaxws.provider.AddressingProviderTests.testWithAddressingHeaders(AddressingProviderTests.java:122)
          at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
          at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
          at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
          at java.lang.reflect.Method.invoke(Method.java:597)
          at junit.framework.TestCase.runTest(TestCase.java:168)
          at junit.framework.TestCase.runBare(TestCase.java:134)
          at junit.framework.TestResult$1.protect(TestResult.java:110)
          at junit.framework.TestResult.runProtected(TestResult.java:128)
          at junit.framework.TestResult.run(TestResult.java:113)
          at junit.framework.TestCase.run(TestCase.java:124)
          at junit.framework.TestSuite.runTest(TestSuite.java:232)
          at junit.framework.TestSuite.run(TestSuite.java:227)
          at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
          at junit.extensions.TestSetup$1.protect(TestSetup.java:23)
          at junit.framework.TestResult.runProtected(TestResult.java:128)
          at junit.extensions.TestSetup.run(TestSetup.java:27)
          at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:81)
          at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
          at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140)
          at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:165)
          at org.apache.maven.surefire.Surefire.run(Surefire.java:107)
          at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
          at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
          at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
          at java.lang.reflect.Method.invoke(Method.java:597)
          at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:289)
          at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:993)

          These failures were introduced by r937604 which fixed the build on JDK 1.5, so any fix for this issue should test on both JDKs. The build succeeds with JDK 1.5.0_16 and maven 2.0.11.

            Activity

            Ascending order - Click to sort in descending order
            Hide
            Permalink
            veithen Andreas Veithen added a comment -

            I just tested r937604 with the following JDK and I don't see any test failures:

            java version "1.6.0_17"
            Java(TM) SE Runtime Environment (build 1.6.0_17-b04-248-9M3125)
            Java HotSpot(TM) 64-Bit Server VM (build 14.3-b01-101, mixed mode)

            Operation system is Mac OS X (which ships with a Sun derived JDK).

            Show
            veithen Andreas Veithen added a comment - I just tested r937604 with the following JDK and I don't see any test failures: java version "1.6.0_17" Java(TM) SE Runtime Environment (build 1.6.0_17-b04-248-9M3125) Java HotSpot(TM) 64-Bit Server VM (build 14.3-b01-101, mixed mode) Operation system is Mac OS X (which ships with a Sun derived JDK).
            Hide
            Permalink
            veithen Andreas Veithen added a comment -

            Also builds fine with JDK 1.6 on Hudson:

            http://hudson.zones.apache.org/hudson/view/Axis2/job/Axis2-trunk-java-1.6/

            Show
            veithen Andreas Veithen added a comment - Also builds fine with JDK 1.6 on Hudson: http://hudson.zones.apache.org/hudson/view/Axis2/job/Axis2-trunk-java-1.6/
            Hide
            Permalink
            sanderka Katherine Sanders added a comment -

            Closing this since it's working with JDK 1.6 in other environments and I can use JDK 1.5 to build so it's not worth investigating further.

            Show
            sanderka Katherine Sanders added a comment - Closing this since it's working with JDK 1.6 in other environments and I can use JDK 1.5 to build so it's not worth investigating further.
            Hide
            Permalink
            veithen Andreas Veithen added a comment -

            Jeff fixed a platform dependent issue in r938653 related to class path separators. This should explain why the build works fine on Unix systems, but not on Windows. So actually the issue was not the Java version, but the platform.

            Show
            veithen Andreas Veithen added a comment - Jeff fixed a platform dependent issue in r938653 related to class path separators. This should explain why the build works fine on Unix systems, but not on Windows. So actually the issue was not the Java version, but the platform.
            Hide
            Permalink
            sanderka Katherine Sanders added a comment -

            I don't think this issue could be the platform because the build worked fine with JDK 1.5.0_16 on the same Windows machine.

            Show
            sanderka Katherine Sanders added a comment - I don't think this issue could be the platform because the build worked fine with JDK 1.5.0_16 on the same Windows machine.
            Hide
            Permalink
            veithen Andreas Veithen added a comment -

            Actually it is. My fix to Jeff's change caused the boot classpath to be incorrect on Windows. The fact that an incorrect boot class path is the same as specifying no boot classpath at all explains why this works on JDK 1.5: it simply loads the JARs from the application classpath (as it did before Jeff's change).

            Show
            veithen Andreas Veithen added a comment - Actually it is. My fix to Jeff's change caused the boot classpath to be incorrect on Windows. The fact that an incorrect boot class path is the same as specifying no boot classpath at all explains why this works on JDK 1.5: it simply loads the JARs from the application classpath (as it did before Jeff's change).
            Hide
            Permalink
            sanderka Katherine Sanders added a comment -

            Ah I see. Yes you're right, I can build the latest level without errors with JDK 1.6.0_16 now.

            Show
            sanderka Katherine Sanders added a comment - Ah I see. Yes you're right, I can build the latest level without errors with JDK 1.6.0_16 now.

              People

              • Assignee:
                Unassigned
                Reporter:
                sanderka Katherine Sanders
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Development