Discussion:
[SunRay-Users] Random disconnects
Tim Mulvaney
2014-11-11 22:47:57 UTC
Permalink
Hi everyone,

Any help would be appreciated on this matter. Thanks in advance.

Tim

Environment
- 150 Sun Ray 2 thin clients connecting to VMware View 4.6 linked clones over the Sun Ray VMware View connector through RDP.
- 3 Sun Ray servers running Software version 5.2.5 (hoping to upgrade to latest sometime soon but not there yet).
- Clients used in labs for classes
- OS version on all three Sun Ray servers: Solaris 10

Issue
Recently I've been hearing reports of sessions randomly disconnecting and then after a couple of minutes it will reconnect to the same session. After looking at the messages log on the three Sun Ray servers I see one server has some Java errors that I am wondering might be causing the problem. See logs below. Also, the CPU load is rather high with the uttscpd process using up about 50% of the CPU.

Questions
- Would the Java errors listed in the log cause the Sun Ray thin clients to disconnect?
- Has anyone everyone ever had to increase the Java heap size or add more swap memory to address a problem like this?
- Anyone ever had to increase the code cache size using the -XX:ReservedCodeCacheSize= option? As suggested by the log file
- Is there a tool on Solaris to check java heap usage or a monitoring tool to warn me when the Java memory is out of memory?

Sample of Logs
kiosk:vdm[17572]: [ID 702911 user.error] Exception in thread "main" java.lang.OutOfMemoryError: heap allocation failed
kiosk:vdm[19805]: [ID 702911 user.error] # There is insufficient memory for the Java Runtime Environment to continue.
Worker3 UNEXPECTED: during send to: ***@51bc8a error=java.net.SocketException: Broken pipe
utauthd: [ID 188617 user.info] Worker3 UNEXPECTED: Terminal.readMesages: java.net.SocketException: Connection timed out
kiosk:vdm[4256]: [ID 702911 user.error] Java HotSpot(TM) Client VM warning: CodeCache is full. Compiler has been disabled.
kiosk:vdm[25614]: [ID 702911 user.error] Java HotSpot(TM) Client VM warning: Try increasing the code cache size using -XX:ReservedCodeCacheSize=
Loading...