JDK-7140929 : NotSerializableNotifTest.java fails intermittently
  • Type: Bug
  • Component: core-svc
  • Sub-Component: java.lang.management
  • Affected Version: 8
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2012-01-30
  • Updated: 2019-08-16
  • Resolved: 2013-10-21
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 8
8 b115Fixed
Related Reports
Relates :  
Description
I observed the following SDK/JDK test fail in my baseline test for JDK8-B22
and JDK8-B23 on Solaris X64:

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

Here is the configuration info:

$ cat sdk-mm_jmx-prod-server-fast-comp.solaris-x64/do_sdk_common_tests.15722.version 
java version "1.8.0-ea"
Java(TM) SE Runtime Environment (build 1.8.0-ea-b22)
Java HotSpot(TM) 64-Bit Server VM (build 23.0-b10-fastdebug, compiled mode)


Here is a snippet from the .jtr file:

----------System.out:(27/1884)----------
>>> Test to send a not serializable notification

>>> Test for protocol rmi
>>> Create a server: service:jmx:rmi://frankenputer:2468
Warning: Handler @0 takes mixed loaded/unloaded exceptions in
virtual jobject sun.reflect.MethodAccessorGenerator$1.run()
Warning: Handler @0 takes mixed loaded/unloaded exceptions in
virtual jobject sun.reflect.MethodAccessorGenerator$1.run()
Warning: Handler @0 takes mixed loaded/unloaded exceptions in
virtual jobject sun.reflect.MethodAccessorGenerator$1.run()
Warning: Handler @0 takes mixed loaded/unloaded exceptions in
virtual jobject sun.reflect.MethodAccessorGenerator$1.run()
>>> Creating a client connectint to: service:jmx:rmi://frankenputer:2468/stub/rO
0ABXNyAC5qYXZheC5tYW5hZ2VtZW50LnJlbW90ZS5ybWkuUk1JU2VydmVySW1wbF9TdHViAAAAAAAAAA
ICAAB4cgAaamF2YS5ybWkuc2VydmVyLlJlbW90ZVN0dWLp/tzJi+FlGgIAAHhyABxqYXZhLnJtaS5zZX
J2ZXIuUmVtb3RlT2JqZWN002G0kQxhMx4DAAB4cHc5AAtVbmljYXN0UmVmMgAADjE0MS4xNDQuMjEuMT
c4AAAJpLoLcVqoK9M17wUIggAAATUENkOcgAEAeA==
Failed: received 0 but should be 10
>>> Test failed for rmi


There are a number of NotSerializableException shown in the stderr
part of the test out. Don't be fooled by those. Those exceptions
are thrown as part of the tests that pass.

Comments
There are more failures in Aurora for b101, b105 and b110. All those failures are related to -Xcomp flag. When this flag is specified the execution is slowed down, in case of fastdebug it barely moves. The test gives up after 10 seconds of waiting for the notifications to arrive. This is all good but the error message should mention timeout rather than missing notifications.
18-10-2013