-
Bug
-
Resolution: Not an Issue
-
P4
-
None
-
1.0.1
-
unknown
-
generic
JMX 1.2.2_r026
JMX Remote 1.0.1 b40
J2SE 1.4.2_03
The TCK tests
api/javax/management/remote/JMXConnector/optional/index.html#JMXMPConnectorTest
and
api/javax/management/remote/JMXConnector/optional/index.html#GenericConnectorTest
both fail for the same reason.
Test extract :
/**
* Test Case : 2
* Input:
* Action: Check the connect() method
* Create a connector server and a connector client.
* Do not start the server and try to connect the client.
* Finally, close the connection and stop the server.
* Output: IOException after the connect
*/
<trunc>
ref.println("An IOException is expected.");
connector.connect();
ref.println("(ERROR) Expected IOException not raised");
That test fails on RedHat 9 as it pass with Solaris 9 (both Sparc and X86) and RedHat AS 2.1.
When it fails, we stay stuck on the connect() call;
JavaTest harness has no other choice than stopping the test after time out expires.
I did a try where I do activate the JMX Remote debugging. Results are then different, the test goes further but blocks in test case 6 for the same reason.
I attached the output that exhibits several stacks (SocketException, BindException, NPE).
JMX Remote 1.0.1 b40
J2SE 1.4.2_03
The TCK tests
api/javax/management/remote/JMXConnector/optional/index.html#JMXMPConnectorTest
and
api/javax/management/remote/JMXConnector/optional/index.html#GenericConnectorTest
both fail for the same reason.
Test extract :
/**
* Test Case : 2
* Input:
* Action: Check the connect() method
* Create a connector server and a connector client.
* Do not start the server and try to connect the client.
* Finally, close the connection and stop the server.
* Output: IOException after the connect
*/
<trunc>
ref.println("An IOException is expected.");
connector.connect();
ref.println("(ERROR) Expected IOException not raised");
That test fails on RedHat 9 as it pass with Solaris 9 (both Sparc and X86) and RedHat AS 2.1.
When it fails, we stay stuck on the connect() call;
JavaTest harness has no other choice than stopping the test after time out expires.
I did a try where I do activate the JMX Remote debugging. Results are then different, the test goes further but blocks in test case 6 for the same reason.
I attached the output that exhibits several stacks (SocketException, BindException, NPE).
- relates to
-
JDK-6286631 JMXMP connector server should not call ServerSocket.setReuseAddress(true) by default
-
- Resolved
-
-
JDK-4969962 JMXMP server gets NullPointerException
-
- Resolved
-