On 08/28/2016 06:03 PM, Steffen Moser wrote:
> On 08/13/2016 12:59 AM, Mike Jumper wrote:
>> On Fri, Aug 12, 2016 at 3:18 PM, Steffen Moser wrote:
>> On 08/12/2016 08:39 PM, Cahill, Benjamin wrote:
>>> I failed to mention that I have already done this. The
>>> connections are also failing in the same way for Windows XP RDP
>>> connections as well as Linux SSH connections.
>>> Other ideas?
>> I had quite similar problems when I upgraded from Tomcat 6 to
>> Tomcat 8 (both running on Solaris 11.3) after a server crash. The
>> RDP connection was closed immediately after opening it and the
>> message you mentioned was displayed. I didn't see any helpful logs,
>> but I must admit that I unfortunately didn't have much time for
>> further analyzing, because I had to restore the production system
>> after its breakdown.
>> Downgrading to Tomcat 6 fixed the problem for me.
>> Tomcat 8 *should* work fine (as should 7). I highly recommend
>> against downgrading all the way to Tomcat 6 - you'll lose support
>> for WebSocket, as well as any other enhancements the Tomcat
>> community has made since.
> I totally agree, it was only a very quick fix. After a severe crash
> of one of our RAID systems, I had to re-setup a few things and used
> this to upgrade from Tomcat 6.0.45 to Tomcat 8.0.32. Both versions of
> Tomcat are available as packages in Oracle Solaris 11.3.
> After the upgrade, I had exactly the same problem which Benjamin
> reported about in this thread. So to get the system up quickly, I
> did the downgrade to Tomcat 6.0.45 and Guacamole began to work fine
> again. In the meantime (and also initiated by your message) I took
> some time to narrow down the problem. It seems it is related to
> websockets, and it also seems to be related to encryption. Currently,
> our users are accessing Guacamole directly which means there isn't
> any Apache or NGINX Reverse Proxy between user and the servlet
> container Tomcat. For this reason, Tomcat is doing the security (TLS)
> itself. As soon as I disable SSL/TLS and use HTTP instead of HTTPS
> for Guacamole, it works well with Tomcat 8.0.32. So there seems to be
> an issue which SSL/TLS, and we also found out that the issue does not
> affect all browsers: Safari on OS X 10.11.6 works well. Chrome and
> Firefox don't (tested with OS X, Windows and Linux).
>> If you find Tomcat 8 is failing, it'd be better to try a
>> slightly-newer or slightly-older version of the same (but still
>> 8.0.x). You shouldn't need to fall down two whole major releases.
> I've seen that there are some websocket-related changes and bug fixes
> in newer versions of Tomcat (beginning in version 8.0.33 and newer).
> I am going to upgrade the platform to the latest SRU (patch level) of
> Solaris 11.3 in the next days. This includes an upgrade to Tomcat
> 8.5.3. If the problem still occurs with this version of Tomcat, I'll
> spend time for digging more deeply.
Last week, I eventually updated the server zone to the latest Solaris
patch level which also brought a major upgrade of the "Tomcat-8" PKG
package from Tomcat 8.0.33 to Tomcat 8.5.3. While I had no success in
running Guacamole 0.9.9 on Tomcat 8.0.33 (the connection was immediately
closed as described by Benjamin in this thread's original posting),
there doesn't seem to occur any problem with Tomcat 8.5.3.
Everything seems to run quite well and it also seems to run more
smoothly (regarding latency) than on Tomcat 6.0.45 which has been in
production usage before (maybe caused by the availability of websockets
in Tomcat 8).
Testing Guacamole with another minor revision of the 8.0 series of
Apache Tomcat would require me manually building and installing it from
the scratch as Oracle doesn't provide a suitable built. Is it
necessary/required to do such tests for the development of Guacamole?
Dipl.-Inf. Steffen Moser
School of Advanced Professional Studies Room: 45.3.110
Ulm University Tel: +49.731.50-32407
Albert-Einstein-Allee 45 Fax: +49.731.50-32409
89081 Ulm, Germany http://saps.uni-ulm.de/