On 13/02/2013 15:19, Amit Bhagra wrote:
I am developing a tomcat application which requires
a large number of websocket connections to remain opened during the time
users are logged in (around 40-50 thousand). I have a ruby script (written
using faye-websocket) which can
Il giorno gio, 14/02/2013 alle 11.38 -0500, Christopher Schultz ha
scritto:
[...]
Tomcat version is the one shipped with Debian, and uses jdk
1.6.0_u39 with jce unrestricted policy. I also added bouncy castle
jar in $JAVA_HOME/jre/lib/ext and added its provider in
Il giorno ven, 15/02/2013 alle 09.39 +0100, Giuseppe Sacco ha scritto:
[...]
Connector port=8443 protocol=HTTP/1.1 SSLEnabled=true
maxThreads=150 scheme=https secure=true clientAuth=false
sslProtocol=TLS proxyName=www.my-visible-name.tld
proxyPort=8443 address=192.168.1.55 /
Debugging the SSL handshake, I found that the problem is really about
ciphers because the handshake fails with exception
javax.net.ssl.SSLHandshakeException: no cipher suites in common
So, this is really something to be investigated in JSSE instead of
tomcat. I am sorry for noise in this list :-(
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Giuseppe,
On 2/15/13 9:07 AM, Giuseppe Sacco wrote:
Debugging the SSL handshake, I found that the problem is really
about ciphers because the handshake fails with exception
javax.net.ssl.SSLHandshakeException: no cipher suites in common
So,
Mark,
On 2/14/13 5:22 AM, Mark Thomas wrote:
On 14/02/2013 02:22, Steve van Loben Sels wrote:
Greetings.
I recently upgraded from Tomcat 6.0.36 to 7.0.35 with the native
APR connector, and I ran into a problem with numbers in my
access Log. I use the %D (Time taken to process the
someone put cipherSuites patch on TC 7 Connector..
*IF you are implementing TC7 Connector with cipherSuites attribute support and
have not specified cipherSuites supported by your ppk keys*
then yes its tomcats fault
Otherwise its not..
Ciao,
Martin Gainty
