Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-7061191

some javax/management tests fail with fastdebug VM

    Details

      Description

      Here's the JDK version info for these Server VM WinXP failures:

          java version "1.7.0"
          Java(TM) SE Runtime Environment (build 1.7.0-b147)
          Java HotSpot(TM) Server VM (build 21.0-b17-fastdebug, compiled mode)

      Please note that these are fastdebug Server VM bits with the
      -Xcomp option (sdk-mm_jmx-prod-server-fast-comp.windows-i586).
      I did not observe any failures of these tests in the following
      Server VM configs:

          sdk-mm_jmx-prod-server-fast-mixed.windows-i586
          sdk-mm_jmx-prod-server-prod-comp.windows-i586
          sdk-mm_jmx-prod-server-prod-mixed.windows-i586

      This indicates that these failures are timing related.


      javax/management/loading/ParserInfiniteLoopTest.java

      Here is a snippet from the .jtr file:

      TEST PASSED: Got expected non-null cause in ServiceNotFoundException
      javax.management.ServiceNotFoundException: Problems while parsing URL [file:/C:/work/shared/mirrors/src_clones/jdk7/tl_jdk_baseline/test/javax/management/loading/mlet1.html], got exception [java.io.IOException: Missing '>' in tag]
              at javax.management.loading.MLet.getMBeansFromURL(MLet.java:511)
              at ParserInfiniteLoopTest.main(ParserInfiniteLoopTest.java:85)
              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
              at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
              at java.lang.reflect.Method.invoke(Method.java:601)
              at com.sun.javatest.regtest.MainWrapper$MainThread.run(MainWrapper.java:94)
              at java.lang.Thread.run(Thread.java:722)
      Caused by: java.io.IOException: Missing '>' in tag
              at javax.management.loading.MLetParser.scanTag(MLetParser.java:119)
              at javax.management.loading.MLetParser.parse(MLetParser.java:238)
              at javax.management.loading.MLetParser.parseURL(MLetParser.java:284)
              at javax.management.loading.MLet.getMBeansFromURL(MLet.java:505)
              ... 7 more
      Unregister the MLet MBean
      Release the MBean server
      Bye! Bye!
      ----------System.err:(5/162)----------
      java version "1.7.0"
      Java(TM) SE Runtime Environment (build 1.7.0-b147)
      Java HotSpot(TM) Server VM (build 21.0-b17-fastdebug, compiled mode)

      STATUS:Passed.
      result: Error. Program `c:\work\local\baseline_jdks\1.7.0_b147\windows-i586\bin\java' interrupted! (timed out?)


      The test status is "Passed", but it timed out. I suspect this is
      because of the "timeout=5" setting.


      javax/management/monitor/DerivedGaugeMonitorTest.java

      Here is a snippet from the .jtr file:

      Testing AByte
      java.lang.Exception: AByte: Count down not reached!
              at DerivedGaugeMonitorTest.test(DerivedGaugeMonitorTest.java:243)
              at DerivedGaugeMonitorTest.main(DerivedGaugeMonitorTest.java:263)
              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
              at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
              at java.lang.reflect.Method.invoke(Method.java:601)
              at com.sun.javatest.regtest.MainWrapper$MainThread.run(MainWrapper.java:94)
              at java.lang.Thread.run(Thread.java:722)

      JavaTest Message: Test threw exception: java.lang.Exception: AByte: Count down not reached!
      JavaTest Message: shutting down test

      STATUS:Failed.`main' threw exception: java.lang.Exception: AByte: Count down not reached!
      result: Failed. Execution failed: `main' threw exception: java.lang.Exception: AByte: Count down not reached!


      javax/management/monitor/NonComparableAttributeValueTest.java

      The failure mode in this .jtr file is almost identical to
      NullAttributeValueTest.jtr file in the previous note.


      javax/management/monitor/NullAttributeValueTest.java

      The failure mode in this .jtr file is identical to
      NullAttributeValueTest.jtr file in the previous note
      so the Client and Server fastdebug VMs are failing the
      same way.


      javax/management/monitor/ReflectionExceptionTest.java

      The failure mode in this .jtr file is almost identical to
      NullAttributeValueTest.jtr file in the previous note.


      javax/management/monitor/RuntimeExceptionTest.java

      The failure mode in this .jtr file is almost identical to
      NullAttributeValueTest.jtr file in the previous note.


      javax/management/monitor/StartStopTest.java

      The failure mode in this .jtr file is almost identical to
      StartStopTest.jtr file in the previous note.


      javax/management/remote/mandatory/connection/MultiThreadDeadLockTest.java

      java.rmi.NoSuchObjectException: no such object in table
              at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:273)
              at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:251)
              at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:160)
              at com.sun.jmx.remote.internal.PRef.invoke(Unknown Source)
              at javax.management.remote.rmi.RMIConnectionImpl_Stub.getConnectionId(Unknown Source)
              at javax.management.remote.rmi.RMIConnector.getConnectionId(RMIConnector.java:372)
              at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:334)
              at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:267)
              at MultiThreadDeadLockTest.main(MultiThreadDeadLockTest.java:67)
              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
              at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
              at java.lang.reflect.Method.invoke(Method.java:601)
              at com.sun.javatest.regtest.MainWrapper$MainThread.run(MainWrapper.java:94)
              at java.lang.Thread.run(Thread.java:722)

      JavaTest Message: Test threw exception: java.rmi.NoSuchObjectException: no such object in table
      JavaTest Message: shutting down test

      STATUS:Failed.`main' threw exception: java.rmi.NoSuchObjectException: no such object in table
      result: Failed. Execution failed: `main' threw exception: java.rmi.NoSuchObjectException: no such object in table


      javax/management/remote/mandatory/connection/ReconnectTest.java

      The failure mode in this .jtr file is almost identical to
      ReconnectTest.jtr file in the previous note.
      I recently noticed some holes in the test coverage in my Colorado lab
      so I've added the SDK/JDK javax/management tests to my setup. Here's
      the JDK version info for these Client VM WinXP failures:

          java version "1.7.0"
          Java(TM) SE Runtime Environment (build 1.7.0-b147)
          Java HotSpot(TM) Client VM (build 21.0-b17-fastdebug, compiled mode)

      Please note that these are fastdebug Client VM bits with the
      -Xcomp option (sdk-mm_jmx-prod-client-fast-comp.windows-i586).
      I did not observe any failures of these tests in the following
      Client VM configs:

          sdk-mm_jmx-prod-client-fast-mixed.windows-i586
          sdk-mm_jmx-prod-client-prod-comp.windows-i586
          sdk-mm_jmx-prod-client-prod-mixed.windows-i586

      This indicates that these failures are timing related.


      javax/management/monitor/NullAttributeValueTest.java

      Here is a snippet of the .jtr file:

      java.lang.IllegalStateException: Test FAILED: Didn't get all the notifications that were expected by the test!
              at NullAttributeValueTest.main(NullAttributeValueTest.java:346)
              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
              at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
              at java.lang.reflect.Method.invoke(Method.java:601)
              at com.sun.javatest.regtest.MainWrapper$MainThread.run(MainWrapper.java:94)
              at java.lang.Thread.run(Thread.java:722)

      JavaTest Message: Test threw exception: java.lang.IllegalStateException: Test FAILED: Didn't get all the notifications that were expected by the test!
      JavaTest Message: shutting down test

      STATUS:Failed.`main' threw exception: java.lang.IllegalStateException: Test FAILED: Didn't get all the notifications that were expected by the test!
      result: Failed. Execution failed: `main' threw exception: java.lang.IllegalStateException: Test FAILED: Didn't get all the notifications that were expected by the test!


      javax/management/monitor/ReflectionExceptionTest.java

      The failure mode in this .jtr file is almost identical to
      NullAttributeValueTest.jtr.


      javax/management/monitor/StartStopTest.java

      Here is a snippet of the .jtr file:

      java.lang.IllegalStateException: Test FAILED: Unexpected Maximum Pool Size Overflow!
              at StartStopTest.main(StartStopTest.java:205)
              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
              at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
              at java.lang.reflect.Method.invoke(Method.java:601)
              at com.sun.javatest.regtest.MainWrapper$MainThread.run(MainWrapper.java:94)
              at java.lang.Thread.run(Thread.java:722)

      JavaTest Message: Test threw exception: java.lang.IllegalStateException: Test FAILED: Unexpected Maximum Pool Size Overflow!
      JavaTest Message: shutting down test

      STATUS:Failed.`main' threw exception: java.lang.IllegalStateException: Test FAILED: Unexpected Maximum Pool Size Overflow!
      result: Failed. Execution failed: `main' threw exception: java.lang.IllegalStateException: Test FAILED: Unexpected Maximum Pool Size Overflow!


      javax/management/remote/mandatory/connection/ReconnectTest.java

      Here is a snippet of the .jtr file:

      Jun 29, 2011 6:27:23 PM ClientCommunicatorAdmin Checker-run
      WARNING: Failed to check the connection: org.omg.CORBA.OBJECT_NOT_EXIST: ----------BEGIN server-side stack trace----------
      org.omg.CORBA.OBJECT_NOT_EXIST: vmcid: SUN minor code: 1004 completed: No
              at com.sun.corba.se.impl.logging.POASystemException.nullServant(POASystemException.java:2040)
              at com.sun.corba.se.impl.logging.POASystemException.nullServant(POASystemException.java:2062)
              at com.sun.corba.se.impl.oa.toa.TOAImpl.getInvocationServant(TOAImpl.java:129)
              at com.sun.corba.se.impl.protocol.CorbaServerRequestDispatcherImpl.getServant(CorbaServerRequestDispatcherImpl.java:326)
              at com.sun.corba.se.impl.protocol.CorbaServerRequestDispatcherImpl.getServantWithPI(CorbaServerRequestDispatcherImpl.java:360)
              at com.sun.corba.se.impl.protocol.CorbaServerRequestDispatcherImpl.dispatch(CorbaServerRequestDispatcherImpl.java:202)
              at com.sun.corba.se.impl.protocol.CorbaMessageMediatorImpl.handleRequestRequest(CorbaMessageMediatorImpl.java:1698)
              at com.sun.corba.se.impl.protocol.SharedCDRClientRequestDispatcherImpl.marshalingComplete(SharedCDRClientRequestDispatcherImpl.java:171)
              at com.sun.corba.se.impl.protocol.CorbaClientDelegateImpl.invoke(CorbaClientDelegateImpl.java:147)
              at org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:475)
              at com.sun.jmx.remote.protocol.iiop.ProxyStub._invoke(Unknown Source)
              at org.omg.stub.javax.management.remote.rmi._RMIConnection_Stub.getDefaultDomain(Unknown Source)
              at javax.management.remote.rmi.RMIConnector$RMIClientCommunicatorAdmin.checkConnection(RMIConnector.java:1611)
              at com.sun.jmx.remote.internal.ClientCommunicatorAdmin$Checker.run(ClientCommunicatorAdmin.java:185)
              at java.lang.Thread.run(Thread.java:722)

      ----------END server-side stack trace---------- vmcid: SUN minor code: 1004 completed: No
      Jun 29, 2011 6:27:25 PM ClientCommunicatorAdmin restart
      WARNING: Failed to restart: java.lang.NullPointerException
      result: Failed. Unexpected exit from test [exit code: 1]
      Here's the JDK version info for this Server VM WinXP failure:

          java version "1.7.0"
          Java(TM) SE Runtime Environment (build 1.7.0-b147)
          Java HotSpot(TM) Server VM (build 21.0-b17-fastdebug, compiled mode)

      Please note that these are fastdebug Server VM bits with the
      -Xcomp option (sdk-mm_jmx_closed-prod-server-fast-comp.windows-i586).
      I did not observe any failures of this test in the following
      Server VM configs:

          sdk-mm_jmx_closed-prod-server-fast-mixed.windows-i586
          sdk-mm_jmx_closed-prod-server-prod-comp.windows-i586
          sdk-mm_jmx_closed-prod-server-prod-mixed.windows-i586

      This indicates that the failures are timing related.


      closed/javax/management/remote/mandatory/sslStub/SSLSocketParametersTest.sh

      The above test timed out:

      Timeout signalled after 600 seconds

      Here is the tail end of the .jtr file:

      java version "1.7.0"
      Java(TM) SE Runtime Environment (build 1.7.0-b147)
      Java HotSpot(TM) Server VM (build 21.0-b17-fastdebug, compiled mode)

      result: Error. Execution failed


      test result: Error. Execution failed


      Since there are 26 sets of version information in the .jtr file,
      I'm guessing that this test launched 26 separate java processes.
      That tends to take a lot of time with fastdebug bits.
      Here's the JDK version info for these Server VM Solaris X86 failures:

          java version "1.7.0"
          Java(TM) SE Runtime Environment (build 1.7.0-b147)
          Java HotSpot(TM) Server VM (build 21.0-b17-fastdebug, compiled mode)

      Please note that these are fastdebug Server VM bits with the
      -Xcomp option (sdk-mm_jmx-prod-server-fast-comp.solaris-i586).
      I did not observe any failures of these tests in the following
      Server VM configs:

          sdk-mm_jmx-prod-server-fast-mixed.solaris-i586
          sdk-mm_jmx-prod-server-prod-comp.solaris-i586
          sdk-mm_jmx-prod-server-prod-mixed.solaris-i586

      This indicates that these failures are timing related.


      javax/management/remote/mandatory/connection/ReconnectTest.java

      The failure mode in this .jtr file is almost identical to
      ReconnectTest.jtr in the first note.


      javax/management/remote/mandatory/connection/MultiThreadDeadLockTest.java

      The failure mode in this .jtr file is almost identical to
      MultiThreadDeadLockTest.jtr in the third note.


      javax/management/monitor/NullAttributeValueTest.java

      The failure mode in this .jtr file is almost identical to
      NullAttributeValueTest.jtr in the first note.


      javax/management/monitor/CounterMonitorTest.java

      The failure mode in this .jtr file is almost identical to
      CounterMonitorTest.jtr in the fourth note.


      javax/management/monitor/NonComparableAttributeValueTest.java

      The failure mode in this .jtr file is almost identical to
      NullAttributeValueTest.jtr in the first note.


      javax/management/monitor/ReflectionExceptionTest.java

      The failure mode in this .jtr file is almost identical to
      NullAttributeValueTest.jtr in the first note.


      javax/management/monitor/RuntimeExceptionTest.java

      The failure mode in this .jtr file is almost identical to
      NullAttributeValueTest.jtr in the first note.


      javax/management/monitor/CounterMonitorThresholdTest.java

      Here is a snippet of the .jtr file:

      java.lang.IllegalArgumentException: wrong derived gauge
              at CounterMonitorThresholdTest.runTest(CounterMonitorThresholdTest.java:
      155)
              at CounterMonitorThresholdTest.main(CounterMonitorThresholdTest.java:176
      )
              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
              at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
      java:57)
              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
      sorImpl.java:43)
              at java.lang.reflect.Method.invoke(Method.java:601)
              at com.sun.javatest.regtest.MainWrapper$MainThread.run(MainWrapper.java:
      94)
              at java.lang.Thread.run(Thread.java:722)

      JavaTest Message: Test threw exception: java.lang.IllegalArgumentException: wron
      g derived gauge
      JavaTest Message: shutting down test

      STATUS:Failed.`main' threw exception: java.lang.IllegalArgumentException: wrong
      derived gauge
      result: Failed. Execution failed: `main' threw exception: java.lang.IllegalArgum
      entException: wrong derived gauge


      javax/management/monitor/StartStopTest.java

      The failure mode in this .jtr file is almost identical to
      StartStopTest.jtr in the first note.


      javax/management/loading/ParserInfiniteLoopTest.java

      The failure mode in this .jtr file is different than the
      failure mode for ParserInfiniteLoopTest.jtr in the second note:

      result: Error. Program `/work/shared/baseline_jdks/1.7.0_b147/solaris-i586/bin/j
      ava' interrupted! (timed out?)

      This time the test did not get to the end.
      I suspect this is because of the "timeout=5" setting.
      Here's the JDK version info for these Client VM Solaris X86 failures:

          java version "1.7.0"
          Java(TM) SE Runtime Environment (build 1.7.0-b147)
          Java HotSpot(TM) Client VM (build 21.0-b17-fastdebug, compiled mode)

      Please note that these are fastdebug Client VM bits with the
      -Xcomp option (sdk-mm_jmx-prod-client-fast-comp.solaris-i586).
      I did not observe any failures of these tests in the following
      Client VM configs:

          sdk-mm_jmx-prod-client-fast-mixed.solaris-i586
          sdk-mm_jmx-prod-client-prod-comp.solaris-i586
          sdk-mm_jmx-prod-client-prod-mixed.solaris-i586

      This indicates that these failures are timing related.


      javax/management/monitor/CounterMonitorTest.java

      Here is a snippet from the .jtr file:

      java.lang.IllegalStateException: Notification lost
              at CounterMonitorTest.thresholdNotification(CounterMonitorTest.java:196)
              at CounterMonitorTest.main(CounterMonitorTest.java:241)
              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
              at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
      java:57)
              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
      sorImpl.java:43)
              at java.lang.reflect.Method.invoke(Method.java:601)
              at com.sun.javatest.regtest.MainWrapper$MainThread.run(MainWrapper.java:
      94)
              at java.lang.Thread.run(Thread.java:722)

      JavaTest Message: Test threw exception: java.lang.IllegalStateException: Notific
      ation lost
      JavaTest Message: shutting down test

      STATUS:Failed.`main' threw exception: java.lang.IllegalStateException: Notificat
      ion lost
      result: Failed. Execution failed: `main' threw exception: java.lang.IllegalState
      Exception: Notification lost


      javax/management/monitor/ReflectionExceptionTest.java

      The failure mode in this .jtr file is almost identical to
      NullAttributeValueTest.jtr in the first note.


      javax/management/monitor/NullAttributeValueTest.java

      The failure mode in this .jtr file is almost identical to
      NullAttributeValueTest.jtr in the first note.


      javax/management/monitor/StartStopTest.java

      The failure mode in this .jtr file is almost identical to
      StartStopTest.jtr in the first note.


      javax/management/monitor/NonComparableAttributeValueTest.java

      The failure mode in this .jtr file is almost identical to
      NullAttributeValueTest.jtr in the first note.


      javax/management/monitor/RuntimeExceptionTest.java

      The failure mode in this .jtr file is almost identical to
      NullAttributeValueTest.jtr in the first note.
      Here's the JDK version info for this Server VM Solaris X86 failure:

          java version "1.7.0"
          Java(TM) SE Runtime Environment (build 1.7.0-b147)
          Java HotSpot(TM) Server VM (build 21.0-b17-fastdebug, compiled mode)

      Please note that these are fastdebug Server VM bits with the
      -Xcomp option (sdk-mm_jmx_closed-prod-server-fast-comp.solaris-i586).
      I did not observe any failures of this test in the following
      Server VM configs:

          sdk-mm_jmx_closed-prod-server-fast-mixed.solaris-i586
          sdk-mm_jmx_closed-prod-server-prod-comp.solaris-i586
          sdk-mm_jmx_closed-prod-server-prod-mixed.solaris-i586

      This indicates that the failures are timing related.


      closed/javax/management/remote/mandatory/sslStub/SSLSocketParametersTest.sh

      The above test timed out:

      Timeout signalled after 600 seconds

      Here is the tail end of the .jtr file:

      java version "1.7.0"
      Java(TM) SE Runtime Environment (build 1.7.0-b147)
      Java HotSpot(TM) Server VM (build 21.0-b17-fastdebug, compiled mode)

      result: Error. Execution failed


      test result: Error. Execution failed


      Since there are 25 sets of version information in the .jtr file,
      I'm guessing that this test launched 25 separate java processes.
      That tends to take a lot of time with fastdebug bits.
      Another test failure on WinXP doing a rerun of JDK7-B147 testing:

          javax/management/remote/mandatory/threads/ExecutorTest.java

      Note this failure is in a Client VM -Xmixed fastdebug config so
      I've removed the "test-fail-comp" keyword.

      Here is a snippet of the .jtr file:

      ----------System.out:(9/202)----------

      TEST: rmi
      Test with no executor in env
      Got notifications
      Test with null executor in env
      Got notifications
      Test with non-null executor in env
      Got notifications
      Executor was called enough times
      ----------System.err:(24/1735)----------
      java version "1.7.0"
      Java(TM) SE Runtime Environment (build 1.7.0-b147)
      Java HotSpot(TM) Client VM (build 21.0-b17-fastdebug, mixed mode)

      java.lang.reflect.UndeclaredThrowableException
              at $Proxy0.execute(Unknown Source)
              at com.sun.jmx.remote.internal.ClientNotifForwarder$NotifFetcher.doRun(ClientNotifForwarder.java:553)
              at com.sun.jmx.remote.internal.ClientNotifForwarder$NotifFetcher.run(ClientNotifForwarder.java:451)
              at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
              at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
              at java.lang.Thread.run(Thread.java:722)
      Caused by: java.lang.reflect.InvocationTargetException
              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
              at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
              at java.lang.reflect.Method.invoke(Method.java:601)
              at ExecutorTest$CountInvocationHandler.invoke(ExecutorTest.java:239)
              ... 6 more
      Caused by: java.util.concurrent.RejectedExecutionException: Task com.sun.jmx.remote.internal.ClientNotifForwarder$NotifFetcher@1baf36f rejected from java.util.concurrent.ThreadPoolExecutor@c42968[Shutting down, pool size = 1, active threads = 1, queued tasks = 0, completed tasks = 9]
              at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2001)
              at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:816)
              at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1337)
              ... 11 more
      STATUS:Failed.`main' threw exception: java.lang.reflect.UndeclaredThrowableException
      result: Failed. Execution failed: `main' threw exception: java.lang.reflect.UndeclaredThrowableException


      test result: Failed. Execution failed: `main' threw exception: java.lang.reflect.UndeclaredThrowableException
      Another test failure on WinXP doing a rerun of JDK7-B147 testing:

          javax/management/remote/mandatory/notif/NotificationEmissionTest.java

      Note this failure is in a Server VM -Xcomp fastdebug config.

      Here is a snippet of the .jtr file:

      ----------messages:(3/112)----------
      command: build NotificationEmissionTest
      reason: Named class compiled on demand
      elapsed time (seconds): 7.016
      result: Passed. All files up to date

      #section:main
      ----------messages:(3/143)----------
      command: main NotificationEmissionTest2
      reason: User specified action: run main NotificationEmissionTest 2
      elapsed time (seconds): 120.324
      ----------System.out:(8/313)*----------

      --- Check the emission of notifications when a Security Manager is installed

      =-=-= Running testcase 2 =-=-=

      Setting policy file C:\\work\\shared\\mirrors\\src_clones\\jdk7\\tl_jdk_baseline\\test\\javax\\management\\remote\\mandatory\\notif\\policy.positive
      Create principal with name = role
      Setting SM
      ----------System.err:(4/146)----------
      java version "1.7.0"
      Java(TM) SE Runtime Environment (build 1.7.0-b147)
      Java HotSpot(TM) Server VM (build 21.0-b17-fastdebug, compiled mode)

      result: Error. Program `c:\work\local\baseline_jdks\1.7.0_b147\windows-i586\bin\java' interrupted! (timed out?)


      test result: Error. Program `c:\work\local\baseline_jdks\1.7.0_b147\windows-i586\bin\java' interrupted! (timed out?)


      The above timeout is with the second test in the file.
      Here's the set of elapsed times:

      elapsed time (seconds): 0.02
      elapsed time (seconds): 3.212
      elapsed time (seconds): 3.212
      elapsed time (seconds): 0.451
      elapsed time (seconds): 54.946
      elapsed time (seconds): 7.016
      elapsed time (seconds): 120.324

      The first five time lines are for the first test
      (NotificationEmissionTest 1) and the last two time
      lines are for the second test (NotificationEmissionTest 2).

      There are three more invocations of NotificationEmissionTest.
      I reran JDK7-B147 baseline testing to check out the latest VM testbase
      release (v7r06). The following SDK/JDK test failed:

          javax/management/monitor/StartStopTest.java

      with the same failure mode as described in Description note #1.
      However, the failing configuration is different:

      java version "1.7.0"
      Java(TM) SE Runtime Environment (build 1.7.0-b147)
      Java HotSpot(TM) Server VM (build 21.0-b17, compiled mode)

      This failure occurred with the Server VM product bits with
      the -Xcomp option. I've removed the 'test-fail-debug' and
      'test-fail-fastdebug' keywords. So it is looking like these
      failures can happen when the testing takes a bit of time:

          fastdebug -Xmixed
          fastdebug -Xcomp
          product -Xcomp
      Another test failure on WinXP doing JDK8-B08 baseline testing:

          javax/management/remote/mandatory/notif/ListenerScaleTest.java

      Note this failure is in a Client VM -Xcomp fastdebug config.

      Here is a snippet of the .jtr file:

      ----------System.err:(18/962)----------
      java version "1.8.0-ea"
      Java(TM) SE Runtime Environment (build 1.8.0-ea-b08)
      Java HotSpot(TM) Client VM (build 23.0-b01-fastdebug, compiled mode)

      java.lang.Exception: Failed: ratio=130.44534852626447
              at ListenerScaleTest.test(ListenerScaleTest.java:180)
              at ListenerScaleTest.main(ListenerScaleTest.java:138)
              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
              at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
              at java.lang.reflect.Method.invoke(Method.java:474)
              at com.sun.javatest.regtest.MainWrapper$MainThread.run(MainWrapper.java:94)
              at java.lang.Thread.run(Thread.java:722)

      JavaTest Message: Test threw exception: java.lang.Exception: Failed: ratio=130.44534852626447
      JavaTest Message: shutting down test

      STATUS:Failed.`main' threw exception: java.lang.Exception: Failed: ratio=130.44534852626447
      result: Failed. Execution failed: `main' threw exception: java.lang.Exception: Failed: ratio=130.44534852626447


      test result: Failed. Execution failed: `main' threw exception: java.lang.Exception: Failed: ratio=130.44534852626447


      Here is the failing part of the test:

          175 System.out.println("Timing a notification send now");
          176 long manyMBeansTime = timeNotif(mbs);
          177 System.out.println("Time with many MBeans: " + manyMBeansTime + "ns");
          178 double ratio = (double) manyMBeansTime / singleMBeanTime;
          179 if (ratio > 100.0)
          180 throw new Exception("Failed: ratio=" + ratio);
          181 System.out.println("Test passed: ratio=" + ratio);
          182 }


      The test fails if the ratio is greater than 100 and in this
      test run the ratio was 130.XXX. However, the limit of 100
      may not be a good assumption when either fastdebug bits are
      used or -Xcomp is specified.
      Another test failure on WinXP doing JDK8-B15 baseline testing:

          javax/management/remote/mandatory/connection/IdleTimeoutTest.java

      Note this failure is in a Client VM -Xcomp fastdebug config.

      Here is a snippet of the .jtr file:

      ----------messages:(3/102)----------
      command: build IdleTimeoutTest
      reason: Named class compiled on demand
      elapsed time (seconds): 0.01
      result: Passed. All files up to date

      #section:main
      ----------messages:(3/121)----------
      command: main IdleTimeoutTest
      reason: User specified action: run main IdleTimeoutTest
      elapsed time (seconds): 68.779
      ----------System.out:(37/1509)----------
      Idle timeout test for protocol rmi
      Timeout for rmi is: 1600 ms
      Idle Time: 10ms
      add Listener0: starting at 10ms
      add Listener1: starting at 10ms
      connId=rmi://141.144.21.181 3
      Operation[1]: starting at 902ms
      Listener0 got notification: d:type=mlet,instance=0
      Listener1 got notification: d:type=mlet,instance=0
      Operation[2]: starting at 2804ms
      Listener0 got notification: d:type=mlet,instance=1
      Listener1 got notification: d:type=mlet,instance=1
      Operation[3]: starting at 2814ms
      Listener0 got notification: d:type=mlet,instance=2
      Listener1 got notification: d:type=mlet,instance=2
      Operation[4]: starting at 2814ms
      Listener0 got notification: d:type=mlet,instance=3
      Listener1 got notification: d:type=mlet,instance=3
      Waiting for notifs: starting at 2885ms
      Waited 440ms for notifs to arrive
      idle time since last operation: 511ms
      Requesting conn id at: 3325ms
      Got conn id <rmi://141.144.21.181 3> at: 3325ms
      Removing notification listener: Listener0
      Removing notification listener: Listener1
      Waiting for id list to drop ours
      Client id changed as expected: <rmi://141.144.21.181 3> -> <rmi://141.144.21.181 4>
      Connection id list on server after client close: []
      *** ------------------------------------------
      *** Test passed for rmi
      *** ------------------------------------------
      Test for protocol rmi passed
      Idle timeout test for protocol iiop
      Timeout for iiop is: 2110 ms
      Idle Time: 100ms
      add Listener0: starting at 100ms
      Connection id list on server after client close: []
      ----------System.err:(31/2221)----------
      java version "1.8.0-ea"
      Java(TM) SE Runtime Environment (build 1.8.0-ea-b15)
      Java HotSpot(TM) Client VM (build 23.0-b06-fastdebug, compiled mode)

      java.lang.NullPointerException
              at org.omg.stub.javax.management.remote.rmi._RMIConnectionImpl_Tie._invoke(Unknown Source)
              at com.sun.corba.se.impl.protocol.CorbaServerRequestDispatcherImpl.dispatchToServant(CorbaServerRequestDispatcherImpl.java:654)
              at com.sun.corba.se.impl.protocol.CorbaServerRequestDispatcherImpl.dispatch(CorbaServerRequestDispatcherImpl.java:205)
              at com.sun.corba.se.impl.protocol.CorbaMessageMediatorImpl.handleRequestRequest(CorbaMessageMediatorImpl.java:1698)
              at com.sun.corba.se.impl.protocol.SharedCDRClientRequestDispatcherImpl.marshalingComplete(SharedCDRClientRequestDispatcherImpl.java:171)
              at com.sun.corba.se.impl.protocol.CorbaClientDelegateImpl.invoke(CorbaClientDelegateImpl.java:148)
              at org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:475)
              at com.sun.jmx.remote.protocol.iiop.ProxyStub._invoke(Unknown Source)
              at org.omg.stub.javax.management.remote.rmi._RMIConnection_Stub.addNotificationListeners(Unknown Source)
              at javax.management.remote.rmi.RMIConnector.addListenersWithSubjects(RMIConnector.java:590)
              at javax.management.remote.rmi.RMIConnector.addListenerWithSubject(RMIConnector.java:566)
              at javax.management.remote.rmi.RMIConnector.access$700(RMIConnector.java:119)
              at javax.management.remote.rmi.RMIConnector$RemoteMBeanServerConnection.addNotificationListener(RMIConnector.java:1235)
              at IdleTimeoutTest.test(IdleTimeoutTest.java:195)
              at IdleTimeoutTest.main(IdleTimeoutTest.java:76)
              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
              at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
              at java.lang.reflect.Method.invoke(Method.java:474)
              at com.sun.javatest.regtest.MainWrapper$MainThread.run(MainWrapper.java:94)
              at java.lang.Thread.run(Thread.java:722)

      JavaTest Message: Test threw exception: java.lang.NullPointerException
      JavaTest Message: shutting down test

      STATUS:Failed.`main' threw exception: java.lang.NullPointerException
      result: Failed. Execution failed: `main' threw exception: java.lang.NullPointerException


      test result: Failed. Execution failed: `main' threw exception: java.lang.NullPointerException


      The System.out portion of the .jtr file is caliming that the test
      passed, but the System.err portion is showing that an NPE was
      thrown. In any case, the test ran for 68 seconds so I suspect
      that the test's timeout logic is not expecting to run with
      fastdebug VM bits or in -Xcomp mode.
      Another test failure on Solaris X64 doing JDK8-B21 baseline testing:

          javax/management/monitor/ThreadPoolAccTest.java

      Note this failure is in a 64-bit Server VM -Xcomp fastdebug config.

      Here is a snippet of the .jtr file:

      java version "1.8.0-ea"
      Java(TM) SE Runtime Environment (build 1.8.0-ea-b21)
      Java HotSpot(TM) 64-Bit Server VM (build 23.0-b09-fastdebug, compiled mode)

      java.lang.NullPointerException
              at ThreadPoolAccTest.runTest(ThreadPoolAccTest.java:162)
              at ThreadPoolAccTest.main(ThreadPoolAccTest.java:192)
              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
              at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
      java:57)
              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
      sorImpl.java:43)
              at java.lang.reflect.Method.invoke(Method.java:474)
              at com.sun.javatest.regtest.MainWrapper$MainThread.run(MainWrapper.java:
      94)
              at java.lang.Thread.run(Thread.java:722)

      JavaTest Message: Test threw exception: java.lang.NullPointerException
      JavaTest Message: shutting down test

      STATUS:Failed.`main' threw exception: java.lang.NullPointerException
      result: Failed. Execution failed: `main' threw exception: java.lang.NullPointerE
      xception


      test result: Failed. Execution failed: `main' threw exception: java.lang.NullPoi
      nterException


      Here is the test code that threw the NPE:

         153 // Check if task principal is correct
         154 //
         155 for (int i = 0; i < 6; i++) {
         156 echo(">>> Monitor = " + monitorNames[i]);
         157 echo(">>> ObservedObject = " +
         158 monitor[i].getObservedObject());
         159 echo(">>> ObservedAttribute = " +
         160 monitor[i].getObservedAttribute());
         161 echo(">>> Principal = " + monitored[i].principal);
         162 if (monitored[i].principal.equals(principals[i / 3])) {
         163 echo("\tOK: Got Expected Principal");
         164 } else {
         165 echo("\tKO: Got Unexpected Principal");
         166 return 1;
         167 }
         168 }

      The .jtr file shows that principal is "null" on line 161 so
      the use of principal on line 162 is going to throw NPE. I
      don't know why this failure mode shows up with fastdebug bits.
      A test failure on Solaris X64 doing JDK8-B24 baseline testing:

          closed/sun/management/snmp/notifications/NotificationTest.sh

      Note this failure is in a 64-bit Server VM -Xcomp fastdebug config.

      Here is a snippet of the .jtr file:

      #section:script_messages
      ----------messages:(5/256)----------
      JDK under test: (/work/shared/baseline_jdks/1.8.0_b24/solaris-x64)
      java version "1.8.0-ea"
      Java(TM) SE Runtime Environment (build 1.8.0-ea-b24)
      Java HotSpot(TM) 64-Bit Server VM (build 23.0-b12-fastdebug, compiled mode)
      Timeout signalled after 300 seconds

      <snip>

      ----------System.err:(29/2380)----------
      /work/shared/mirrors/src_clones/jdk8/tl_jdk_baseline/test/closed/sun/management/
      snmp/notifications/NotificationAgent.java:17: warning: NotificationTargetImpl is
       internal proprietary API and may be removed in a future release
      import sun.management.snmp.jvminstr.NotificationTargetImpl;
                                         ^
      /work/shared/mirrors/src_clones/jdk8/tl_jdk_baseline/test/closed/sun/management/
      snmp/notifications/NotificationManager.java:39: warning: JVM_MANAGEMENT_MIBOidTa
      ble is internal proprietary API and may be removed in a future release
      import sun.management.snmp.jvmmib.JVM_MANAGEMENT_MIBOidTable;
                                       ^
      /work/shared/mirrors/src_clones/jdk8/tl_jdk_baseline/test/closed/sun/management/
      snmp/notifications/NotificationAgent.java:126: warning: NotificationTargetImpl i
      s internal proprietary API and may be removed in a future release
              NotificationTargetImpl target =
              ^
      /work/shared/mirrors/src_clones/jdk8/tl_jdk_baseline/test/closed/sun/management/
      snmp/notifications/NotificationAgent.java:127: warning: NotificationTargetImpl i
      s internal proprietary API and may be removed in a future release
                  new NotificationTargetImpl(host + ":" + portStr +":" + community);
                      ^
      /work/shared/mirrors/src_clones/jdk8/tl_jdk_baseline/test/closed/sun/management/
      snmp/notifications/NotificationManager.java:57: warning: JVM_MANAGEMENT_MIBOidTa
      ble is internal proprietary API and may be removed in a future release
              final public JVM_MANAGEMENT_MIBOidTable table;
                           ^
      /work/shared/mirrors/src_clones/jdk8/tl_jdk_baseline/test/closed/sun/management/
      snmp/notifications/NotificationManager.java:81: warning: JVM_MANAGEMENT_MIBOidTa
      ble is internal proprietary API and may be removed in a future release
                  table = new JVM_MANAGEMENT_MIBOidTable();
                              ^
      Note: Some input files use unchecked or unsafe operations.
      Note: Recompile with -Xlint:unchecked for details.
      6 warnings
      java version "1.8.0-ea"
      Java(TM) SE Runtime Environment (build 1.8.0-ea-b24)
      Java HotSpot(TM) 64-Bit Server VM (build 23.0-b12-fastdebug, compiled mode)

      Exception in thread "main" java.lang.OutOfMemoryError: Java heap space
              at NotificationAgent.allocate(NotificationAgent.java:177)
              at NotificationAgent.run(NotificationAgent.java:169)
              at NotificationTest.main(NotificationTest.java:38)
      result: Error. Execution failed


      test result: Error. Execution failed
      A test failure on Solaris X64 doing JDK8-B24 baseline testing:

          javax/management/remote/mandatory/connection/ConnectionTest.java

      Note this failure is in a 64-bit Server VM -Xcomp fastdebug config.

      Here is a snippet of the .jtr file:

      ----------System.err:(37/2925)----------
      java version "1.8.0-ea"
      Java(TM) SE Runtime Environment (build 1.8.0-ea-b24)
      Java HotSpot(TM) 64-Bit Server VM (build 23.0-b12-fastdebug, compiled mode)

      Feb 05, 2012 4:32:44 AM ClientCommunicatorAdmin restart
      WARNING: Failed to restart: java.rmi.NoSuchObjectException: no such object in ta
      ble
      Feb 05, 2012 4:33:29 AM ClientCommunicatorAdmin restart
      WARNING: Failed to restart: java.rmi.NoSuchObjectException: CORBA OBJECT_NOT_EXI
      ST 1398080492 No; nested exception is:
              org.omg.CORBA.OBJECT_NOT_EXIST: ----------BEGIN server-side stack trace-
      ---------
      org.omg.CORBA.OBJECT_NOT_EXIST: vmcid: SUN minor code: 1004 completed: No
              at com.sun.corba.se.impl.logging.POASystemException.nullServant(POASyste
      mException.java:2040)
              at com.sun.corba.se.impl.logging.POASystemException.nullServant(POASyste
      mException.java:2062)
              at com.sun.corba.se.impl.oa.toa.TOAImpl.getInvocationServant(TOAImpl.jav
      a:129)
              at com.sun.corba.se.impl.protocol.CorbaServerRequestDispatcherImpl.getSe
      rvant(CorbaServerRequestDispatcherImpl.java:326)
              at com.sun.corba.se.impl.protocol.CorbaServerRequestDispatcherImpl.getSe
      rvantWithPI(CorbaServerRequestDispatcherImpl.java:360)
              at com.sun.corba.se.impl.protocol.CorbaServerRequestDispatcherImpl.dispa
      tch(CorbaServerRequestDispatcherImpl.java:202)
              at com.sun.corba.se.impl.protocol.CorbaMessageMediatorImpl.handleRequest
      Request(CorbaMessageMediatorImpl.java:1698)
              at com.sun.corba.se.impl.protocol.SharedCDRClientRequestDispatcherImpl.m
      arshalingComplete(SharedCDRClientRequestDispatcherImpl.java:171)
              at com.sun.corba.se.impl.protocol.CorbaClientDelegateImpl.invoke(CorbaCl
      ientDelegateImpl.java:148)
              at org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:475)
              at org.omg.stub.javax.management.remote.rmi._RMIServer_Stub.newClient(Un
      known Source)
              at javax.management.remote.rmi.RMIConnector$RMIClientCommunicatorAdmin.d
      oStart(RMIConnector.java:1629)
              at com.sun.jmx.remote.internal.ClientCommunicatorAdmin.restart(ClientCom
      municatorAdmin.java:126)
              at com.sun.jmx.remote.internal.ClientCommunicatorAdmin.gotIOException(Cl
      ientCommunicatorAdmin.java:54)
              at javax.management.remote.rmi.RMIConnector$RMIClientCommunicatorAdmin.g
      otIOException(RMIConnector.java:1469)
              at javax.management.remote.rmi.RMIConnector$RemoteMBeanServerConnection.
      getDefaultDomain(RMIConnector.java:1044)
              at ConnectionTest.test(ConnectionTest.java:194)
              at ConnectionTest.main(ConnectionTest.java:80)
              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
              at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
      java:57)
              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
      sorImpl.java:43)
              at java.lang.reflect.Method.invoke(Method.java:474)
              at com.sun.javatest.regtest.MainWrapper$MainThread.run(MainWrapper.java:
      94)
              at java.lang.Thread.run(Thread.java:722)
      A test failure on Win32 doing JDK8-B24 baseline testing:

          javax/management/remote/mandatory/notif/NotifReconnectDeadlockTest.java

      Note this failure is in a 32-bit Server VM -Xcomp fastdebug config.

      Here is a snippet of the .jtr file:

      ----------System.err:(12/853)----------
      java version "1.8.0-ea"
      Java(TM) SE Runtime Environment (build 1.8.0-ea-b24)
      Java HotSpot(TM) Server VM (build 23.0-b12-fastdebug, compiled mode)

      Feb 04, 2012 5:29:45 PM ServerCommunicatorAdmin reqIncoming
      WARNING: The server has decided to close this client connection.
      java.lang.IllegalArgumentException: More than one command
              at com.sun.jmx.remote.internal.ClientNotifForwarder$LinearExecutor.execute(ClientNotifForwarder.java:89)
              at com.sun.jmx.remote.internal.ClientNotifForwarder$NotifFetcher.doRun(ClientNotifForwarder.java:553)
              at com.sun.jmx.remote.internal.ClientNotifForwarder$NotifFetcher.run(ClientNotifForwarder.java:451)
              at com.sun.jmx.remote.internal.ClientNotifForwarder$LinearExecutor$1.run(ClientNotifForwarder.java:107)
      STATUS:Failed.`main' threw exception: java.lang.IllegalArgumentException: More than one command
      result: Failed. Execution failed: `main' threw exception: java.lang.IllegalArgumentException: More than one command


      test result: Failed. Execution failed: `main' threw exception: java.lang.IllegalArgumentException: More than one command
      A test failure on Win32 doing JDK8-B24 baseline testing:

          javax/management/remote/mandatory/connection/BrokenConnectionTest.java

      Note this failure is in a Client VM -Xcomp fastdebug config.

      Here is a snippet of the .jtr file:

      Test 21 passed

      Test 22: break during receive for getAttribute
      Created and started connector server
      Client connected OK
      Got IOException as expected: java.rmi.UnmarshalException: Error unmarshaling return header; nested exception is:
              java.io.EOFException
      Stopping server
      Waiting for failure notif
      Did not get failure notif!
      Test 22 FAILED
      FAILING CASES: 22
      Also there is failure of
      closed/sun/management/snmp/notifications/NotificationTest.sh
      with
      Note: Some input files use unchecked or unsafe operations.
      Note: Recompile with -Xlint:unchecked for details.
      6 warnings
      Test Failed: null
      result: Failed. Execution failed: exit code 20

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                jbachorik Jaroslav BachorĂ­k
                Reporter:
                dcubed Daniel Daugherty
              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Imported:
                  Indexed: