On 3/4/2014 1:36 PM, Bill Davidson wrote:
On 3/4/2014 1:24 PM, Christopher Schultz wrote:
Well... then you'd need a balancer for each balancer ;)
Can you reproduce this issue yourself on your own computer (running
the applet locally)? If so, what version of Java is running?
That's mostly what I've been doing for the last 24 hours.
Java recently made some changes to the SSL code that make it a much
bigger pain in the neck to make HTTPS connections for instance. I
haven't seen any "Remote host closed connection during handshake" but
presumably that could happen under the right failed-negotiation
conditions.
Hmm. We were building with Java 1.7.0_25 (I think) when it was working and
now we're building with Java 1.7.0_45. Could that actually be it?
Hmm, is the applet signed, and is the certificate from a trusted authority?
Oracle recently made some changes to Java which tightened down applet
security. They also made some changes in the security policy that block
communication on well-known ports unless you create a policy exception.
I got bit by the latter when I moved to 1.7.0_51 on Windows and tried to
start up a Derby database.
. . . just some random thoughts
/mde/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
