-
Enhancement
-
Resolution: Fixed
-
P2
-
5.0u12
-
b05
-
x86, sparc
-
solaris_10, windows_xp
-
Verified
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2194318 | 7 | Andy Herrick | P3 | Closed | Fixed | b64 |
| JDK-2182130 | 5.0u21 | Vikram Aroskar | P2 | Closed | Fixed | b01 |
| JDK-2179630 | 5.0u20-rev | Vikram Aroskar | P2 | Closed | Fixed | b03 |
| JDK-2175811 | 5.0u19-rev | Vikram Aroskar | P2 | Closed | Fixed | b04 |
We are facing an issue with the SunMC console being started with java web start in a firewall-ed environment .
The console and server communication is happening through RMI .
When the console is started with java the communication happens in the specified port range , (between 45,000 to 48,000 ) but when it is started using java webstart it uses arbitary port range .
The Sunmc console when started with java with the following options :
/usr/bin/nohup $JAVA $MEMSIZE $C_STACKSIZE $FIREWALL_PROPS $PREFS_ROOT -DESROOT=$ESROOT com.sun.symon.base.console.main.ConsoleMain $ARGLIST -k 687a8398ad4a85077d33b72a94e16ffde0c4ba023e9c9ba77b247cc25bd3cd0015bc24b7429916751e681fd02e5ad6eb5345eb7c75b39a1c304e0f000846aa470b755b0640af974e7fc70daa6191dff6efa31a09431bb5e9848b7dc4cf4b97e1dbca31792d2860ca5a5990dfb369e1bcf296274a4e4984c8089329679dd304cd base-console.x >/dev/null 2>&1
The netstat output at the server is :
10.12.184.12.2099 10.12.162.93.45006 66384 0 49232 0 ESTABLISHED
10.12.184.12.39401 10.12.162.93.45009 66608 0 49232 0 ESTABLISHED
10.12.184.12.2099 10.12.162.93.45006 66384 0 49232 0 ESTABLISHED
10.12.184.12.39401 10.12.162.93.45009 65504 0 49232 268 ESTABLISHED
10.12.184.12.40498 10.12.162.93.45003 65204 0 49640 0 ESTABLISHED
10.12.184.12.2099 10.12.162.93.45006 66384 0 49232 0 ESTABLISHED
10.12.184.12.39401 10.12.162.93.45009 65504 50 49232 0 ESTABLISHED
10.12.184.12.40498 10.12.162.93.45003 65700 0 49640 106 ESTABLISHED
Console communication is happening using the correct port range .
Similarly when the SunMC console is started with javaws the options being passed are :
/usr/bin/nohup /usr/jdk/jdk1.5.0_12/bin/javaws $MEMSIZE $C_STACKSIZE $FIREWALL_PROPS $PREFS_ROOT -J-DESROOT=$ESROOT /var/tmp/smconsole.jnlp
when the application is started with javaws the netstat output is :
10.12.184.12.2099 10.12.162.93.37015 66384 0 49232 0 ESTABLISHED
10.12.184.12.39401 10.12.162.93.37016 65680 0 49232 0 ESTABLISHED
10.12.184.12.40565 10.12.162.93.37014 65204 0 49640 0 ESTABLISHED
10.12.184.12.2099 10.12.162.93.37015 66384 0 49232 0 ESTABLISHED
10.12.184.12.39401 10.12.162.93.37016 65504 50 49232 0 ESTABLISHED
10.12.184.12.40565 10.12.162.93.37014 64824 0 49640 106 ESTABLISHED
where 10.12.184.12 is a sunmc server
10.12.162.93 is the sunmc console
Communication happening using the wrong port ranges at the console . outside(45,000 to 48,000 )
The console and server communication is happening through RMI .
When the console is started with java the communication happens in the specified port range , (between 45,000 to 48,000 ) but when it is started using java webstart it uses arbitary port range .
The Sunmc console when started with java with the following options :
/usr/bin/nohup $JAVA $MEMSIZE $C_STACKSIZE $FIREWALL_PROPS $PREFS_ROOT -DESROOT=$ESROOT com.sun.symon.base.console.main.ConsoleMain $ARGLIST -k 687a8398ad4a85077d33b72a94e16ffde0c4ba023e9c9ba77b247cc25bd3cd0015bc24b7429916751e681fd02e5ad6eb5345eb7c75b39a1c304e0f000846aa470b755b0640af974e7fc70daa6191dff6efa31a09431bb5e9848b7dc4cf4b97e1dbca31792d2860ca5a5990dfb369e1bcf296274a4e4984c8089329679dd304cd base-console.x >/dev/null 2>&1
The netstat output at the server is :
10.12.184.12.2099 10.12.162.93.45006 66384 0 49232 0 ESTABLISHED
10.12.184.12.39401 10.12.162.93.45009 66608 0 49232 0 ESTABLISHED
10.12.184.12.2099 10.12.162.93.45006 66384 0 49232 0 ESTABLISHED
10.12.184.12.39401 10.12.162.93.45009 65504 0 49232 268 ESTABLISHED
10.12.184.12.40498 10.12.162.93.45003 65204 0 49640 0 ESTABLISHED
10.12.184.12.2099 10.12.162.93.45006 66384 0 49232 0 ESTABLISHED
10.12.184.12.39401 10.12.162.93.45009 65504 50 49232 0 ESTABLISHED
10.12.184.12.40498 10.12.162.93.45003 65700 0 49640 106 ESTABLISHED
Console communication is happening using the correct port range .
Similarly when the SunMC console is started with javaws the options being passed are :
/usr/bin/nohup /usr/jdk/jdk1.5.0_12/bin/javaws $MEMSIZE $C_STACKSIZE $FIREWALL_PROPS $PREFS_ROOT -J-DESROOT=$ESROOT /var/tmp/smconsole.jnlp
when the application is started with javaws the netstat output is :
10.12.184.12.2099 10.12.162.93.37015 66384 0 49232 0 ESTABLISHED
10.12.184.12.39401 10.12.162.93.37016 65680 0 49232 0 ESTABLISHED
10.12.184.12.40565 10.12.162.93.37014 65204 0 49640 0 ESTABLISHED
10.12.184.12.2099 10.12.162.93.37015 66384 0 49232 0 ESTABLISHED
10.12.184.12.39401 10.12.162.93.37016 65504 50 49232 0 ESTABLISHED
10.12.184.12.40565 10.12.162.93.37014 64824 0 49640 106 ESTABLISHED
where 10.12.184.12 is a sunmc server
10.12.162.93 is the sunmc console
Communication happening using the wrong port ranges at the console . outside(45,000 to 48,000 )
- backported by
-
JDK-2175811 sunmc console when started with javaws does not communicate with the firewall port range
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-