In order to overcome the incompatibility between jre 1.6_29 and shared shell, this CR is to test a beta shared shell server running Java 1.7
Reason for running Java 1.7 for sharedshell
1. ability to upgrade jdk going forward
2. avoid beast vulerability.
3. compatability issue using different jre's on client /server after changes made
aroung jdk 1.6.0_29
Problem manifests as follows during a shared shall connection
Using jdk 1.7.0_5 on tunnel server and on client

On Tunnel Server, the following stack trace:
     [java] 2012-06-27 17:34:08.828 INFO [T28 TunnelProtocolFilter.execute] DBG TunnelProtocolFilter.execute.2 tmh=TunnelMessageHeader(version=2.0,source=0,destination=32766,type=1,flags=0x0,channel=0,conferenceID=null,expectLength=0) isValid=true
     [java] 2012-06-27 17:34:13.258 INFO [T27 TunnelProtocolFilter.execute] DBG TunnelProtocolFilter.execute.1 bufcnt=1 < TMH.SIZE 30
     [java] 2012-06-27 17:34:13.259 INFO [T26 TunnelProtocolFilter.execute] DBG TunnelProtocolFilter.execute.2 tmh=TunnelMessageHeader(version=0.-1,source=-129,destination=-512,type=12800,flags=0x0,channel=0,conferenceID=null,expectLength=129964) isValid=false
     [java] 2012-06-27 17:34:13.259 SEVERE [T26 TunnelProtocolFilter.execute] Invalid msg header:<-----problem here TunnelMessageHeader(version=0.-1,source=-129,destination=-512,type=12800,flags=0x0,channel=0,conferenceID=null,expectLength=129964)

On client side (javaws)

Jun 27, 2012 5:35:39 PM com.sun.srs.tunneling.util.misc.TunnelMessageReceiver run
WARNING: Exception: incomplete TunnelMessageHeader occurred during message reception. Receiver terminating.
java.io.EOFException: incomplete TunnelMessageHeader
        at com.sun.srs.tunneling.util.api.TunnelMessageHeader.readHeader(TunnelMessageHeader.java:631)
        at com.sun.srs.tunneling.util.api.TunnelMessage.readMessage(TunnelMessage.java:438)
        at com.sun.srs.tunneling.util.misc.TunnelMessageReceiver.run(TunnelMessageReceiver.java:135)