JDK-6631273 : PIT: JDBC and RMI tests failed with the 6u10 build8 (pit build)
  • Type: Bug
  • Component: deploy
  • Sub-Component: webstart
  • Affected Version: 6u10
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • OS: windows
  • CPU: x86
  • Submitted: 2007-11-17
  • Updated: 2010-09-17
  • Resolved: 2008-01-08
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 6 JDK 7
6u10 b08Fixed 7Fixed
Related Reports
Relates :  
Description
JDBC and RMI tests failed with the 6u10 build8 (pit build) on all platforms.
Steps to reproduce:
run JDBC and RMI tests:
http://nicole1.sfbay.sun.com:8080/JavawsMustangIntegTest/jdbc
http://nicole1.sfbay.sun.com:8080/JavawsMustangIntegTest/rmi

Here the logs:

JDBC log:
-----------------------------------------------------------------------------
STATUS: JDBC START
Attempting to load Driver.
Finished loading Driver.
Attempting to get connection ...
STATUS: JDBC Exception
com.mysql.jdbc.CommunicationsException: Communications link failure due to underlying exception:

** BEGIN NESTED EXCEPTION **

java.net.SocketException
MESSAGE: java.net.SocketException: Unknown proxy type : HTTP

STACKTRACE:

java.net.SocketException: java.net.SocketException: Unknown proxy type : HTTP
   at com.mysql.jdbc.StandardSocketFactory.connect(StandardSocketFactory.java:151)
   at com.mysql.jdbc.MysqlIO.<init>(MysqlIO.java:280)
   at com.mysql.jdbc.Connection.createNewIO(Connection.java:1765)
   at com.mysql.jdbc.Connection.<init>(Connection.java:430)
   at com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:268)
   at java.sql.DriverManager.getConnection(Unknown Source)
   at java.sql.DriverManager.getConnection(Unknown Source)
   at jdbctest.runTest(jdbctest.java:119)
   at jdbctest.main(jdbctest.java:36)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
   at java.lang.reflect.Method.invoke(Unknown Source)
   at com.sun.javaws.Launcher.executeApplication(Unknown Source)
   at com.sun.javaws.Launcher.executeMainClass(Unknown Source)
   at com.sun.javaws.Launcher.doLaunchApp(Unknown Source)
   at com.sun.javaws.Launcher.run(Unknown Source)
   at java.lang.Thread.run(Unknown Source)


** END NESTED EXCEPTION **


   at com.mysql.jdbc.Connection.createNewIO(Connection.java:1830)
   at com.mysql.jdbc.Connection.<init>(Connection.java:430)
   at com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:268)
   at java.sql.DriverManager.getConnection(Unknown Source)
   at java.sql.DriverManager.getConnection(Unknown Source)
   at jdbctest.runTest(jdbctest.java:119)
   at jdbctest.main(jdbctest.java:36)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
   at java.lang.reflect.Method.invoke(Unknown Source)
   at com.sun.javaws.Launcher.executeApplication(Unknown Source)
   at com.sun.javaws.Launcher.executeMainClass(Unknown Source)
   at com.sun.javaws.Launcher.doLaunchApp(Unknown Source)
   at com.sun.javaws.Launcher.run(Unknown Source)
   at java.lang.Thread.run(Unknown Source)
STATUS: JDBC FAILED 

RMI log:

STATUS: RMI START
JavawsRMITestClient exception: Exception creating connection to: nicole1.sfbay.sun.com; nested exception is:
   java.net.SocketException: Unknown proxy type : HTTP
java.rmi.ConnectIOException: Exception creating connection to: nicole1.sfbay.sun.com; nested exception is:
   java.net.SocketException: Unknown proxy type : HTTP
   at sun.rmi.transport.tcp.TCPEndpoint.newSocket(Unknown Source)
   at sun.rmi.transport.tcp.TCPChannel.createConnection(Unknown Source)
   at sun.rmi.transport.tcp.TCPChannel.newConnection(Unknown Source)
   at sun.rmi.server.UnicastRef.newCall(Unknown Source)
   at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source)
   at java.rmi.Naming.lookup(Unknown Source)
   at JavawsRMITestClient.<init>(JavawsRMITestClient.java:31)
   at JavawsRMIAutoTest.<init>(JavawsRMIAutoTest.java:40)
   at JavawsRMIAutoTest.main(JavawsRMIAutoTest.java:29)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
   at java.lang.reflect.Method.invoke(Unknown Source)
   at com.sun.javaws.Launcher.executeApplication(Unknown Source)
   at com.sun.javaws.Launcher.executeMainClass(Unknown Source)
   at com.sun.javaws.Launcher.doLaunchApp(Unknown Source)
   at com.sun.javaws.Launcher.run(Unknown Source)
   at java.lang.Thread.run(Unknown Source)
Caused by: java.net.SocketException: Unknown proxy type : HTTP
   at sun.rmi.transport.proxy.RMIMasterSocketFactory.checkConnector(Unknown Source)
   at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(Unknown Source)
   ... 18 more
JavawsRMITestClient exception: null
java.lang.NullPointerException
   at JavawsRMITestClient.getNewUserName(JavawsRMITestClient.java:40)
   at JavawsRMIAutoTest.runTest(JavawsRMIAutoTest.java:44)
   at JavawsRMIAutoTest.main(JavawsRMIAutoTest.java:31)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
   at java.lang.reflect.Method.invoke(Unknown Source)
   at com.sun.javaws.Launcher.executeApplication(Unknown Source)
   at com.sun.javaws.Launcher.executeMainClass(Unknown Source)
   at com.sun.javaws.Launcher.doLaunchApp(Unknown Source)
   at com.sun.javaws.Launcher.run(Unknown Source)
   at java.lang.Thread.run(Unknown Source)
STATUS: RMI FAILED

Comments
SUGGESTED FIX http://sa.sfbay.sun.com/projects/deployment_data/6u10/6631273.1/ testcase: http://web-east.east.sun.com/deployment/www/tests/1.6.0_10/6631273/
17-11-2007

EVALUATION A refactoring of the proxy code during integration of the new Java Plug-In caused some information to be lost about whether the URI corresponded to a socket or server socket. Reorganized code to preserve this information both in the common deployment code as well as the new Java Plug-In. Tested with clean rebuild of deploy workspace, and the Java Web Start test case and some applets both with and without proxies set. For the applets, tested with both the old and new plug-in, and in both IE and Firefox.
17-11-2007

EVALUATION This is a regression caused by changes in the shared proxy code made with the integration of the new Java Plug-In.
17-11-2007

EVALUATION OK - I can reproduce the problem now. Problem only occur if proxy is used. Bug is when we are making socket connection, we should default to DIRECT, unless socks proxy is specified. We change some code in the proxy area in this PIT, and I think this caused the breakage. -Thomas
17-11-2007