-
Bug
-
Resolution: Incomplete
-
P3
-
None
-
8u20
-
x86
-
windows_2008
FULL PRODUCT VERSION :
java version "1.8.0_20"
Java(TM) SE Runtime Environment (build 1.8.0_20-b26)
Java HotSpot(TM) 64-Bit Server VM (build 25.20-b23, mixed mode)
ADDITIONAL OS VERSION INFORMATION :
Windows Server 2008 R2
EXTRA RELEVANT SYSTEM CONFIGURATION :
WinRM / WinRs used for remote command line launch
A DESCRIPTION OF THE PROBLEM :
When a javaws command line is run locally it works fine:
javaws -Xnosplash http://beast:8084/VtWebUi/dsv/ascert/vtmp/www/vtmp.jnlp
When the same command is run remotely over a WinRs command shell, it seems the new jp2launcher is attempting to set additional command line arguments which are invalid for a javaws secure sandbox model e.g.
winrs -r:http://qc11dot5:5985 -u:<user> -p:<pwd> javaws -Xnosplash http://beast:8084/VtWebUi/dsv/ascert/vtmp/wwwvtmp.jnlp
The following 3 errors are shown on the console, and the application fails to launch:
Rejecting attempt to specify insecure property: -classpath
Rejecting attempt to specify insecure property: -Xverify:remote
Rejecting attempt to specify insecure property: -Xbootclasspath/a:C:\Program Files\Java\jre1.8.0_20\lib\javaws.jar;C:\Program Files\Java\jre1.8.0_20\lib\deploy.jar;C:\Program Files\Java\jre1.8.0_20\lib\plugin.jar
The application is properly signed with a secure certificate for WebStart usage.
REGRESSION. Last worked in version 8u5
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
Attempt to launch a webstart application using javaws over a remote WinRS shell
REPRODUCIBILITY :
This bug can be reproduced always.
java version "1.8.0_20"
Java(TM) SE Runtime Environment (build 1.8.0_20-b26)
Java HotSpot(TM) 64-Bit Server VM (build 25.20-b23, mixed mode)
ADDITIONAL OS VERSION INFORMATION :
Windows Server 2008 R2
EXTRA RELEVANT SYSTEM CONFIGURATION :
WinRM / WinRs used for remote command line launch
A DESCRIPTION OF THE PROBLEM :
When a javaws command line is run locally it works fine:
javaws -Xnosplash http://beast:8084/VtWebUi/dsv/ascert/vtmp/www/vtmp.jnlp
When the same command is run remotely over a WinRs command shell, it seems the new jp2launcher is attempting to set additional command line arguments which are invalid for a javaws secure sandbox model e.g.
winrs -r:http://qc11dot5:5985 -u:<user> -p:<pwd> javaws -Xnosplash http://beast:8084/VtWebUi/dsv/ascert/vtmp/wwwvtmp.jnlp
The following 3 errors are shown on the console, and the application fails to launch:
Rejecting attempt to specify insecure property: -classpath
Rejecting attempt to specify insecure property: -Xverify:remote
Rejecting attempt to specify insecure property: -Xbootclasspath/a:C:\Program Files\Java\jre1.8.0_20\lib\javaws.jar;C:\Program Files\Java\jre1.8.0_20\lib\deploy.jar;C:\Program Files\Java\jre1.8.0_20\lib\plugin.jar
The application is properly signed with a secure certificate for WebStart usage.
REGRESSION. Last worked in version 8u5
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
Attempt to launch a webstart application using javaws over a remote WinRS shell
REPRODUCIBILITY :
This bug can be reproduced always.