Re: Tomcat 7 cannot get ciphers with SHA256 or SHA384

NSA: "So, how much do you want to not actually *use* string ciphers with perfect forward secrecy"? Mozilla,Google,Opera,et-al: "Hey, that's a business model RIGHT THERE! How much do you even have?" NSA: "How about, not being put out of business permanently, family members keeping up their low i

Tomcat is down or refused connection

Hello, Soap request is failing with below message in our application. 2014/05/20 06:48:43 [ERROR] (browse_csl) failed to reach startSearch service, soapRC 502 2014/05/20 06:48:43 [ERROR] (soap)Error 502 fault: SOAP-ENV:Server [no subcode] I am seeing bel

Re: Tomcat 7 cannot get ciphers with SHA256 or SHA384

I have found out that the connector can use these ciphers, but Chromium can't. I wrote a small Java program that makes a HttpsConnection with Tomcat without problem. Output with -Djavax.net.debug=ssl main, WRITE: TLSv1.2 Change Cipher Spec, length = 1 *** Finished verify_data: { 167, 191, 12, 139

Re: AJP protocol with Apache Tomcat Version 7.0.52

Now we have configured three tomcat instances with below configurations to test the above issue 1. AJP BIO with JkOptions +DisableReuse, connectionTimeout=2, maxThreads=250, maxConnection=245 2. AJP NIO with maxThreads=250, maxConnection=245, connectionTimeout=2 and bufferSize=4096 3.

Re: AJP protocol with Apache Tomcat Version 7.0.52

Yes, we have 300 such threads waiting and after some period of time the server is hung and not responding. We are using AJP BIO with below parameters maxThreads=250 maxConnection=245 -- View this message in context: http://tomcat.10.x6.nabble.com/AJP-protocol-with-Apache-Tomcat-Version-7-0-52

Re: Tomcat 7 cannot get ciphers with SHA256 or SHA384

On 21/05/2014 8:22 PM, "Sverre Moe" wrote: > > I installed Tomcat-7 7.0.42 in OpenSUSE 13.1, configured support for > TLSv1.2. I then configured a list of strong ciphers only, that I wanted to > use. > > protocol="org.apache.coyote.http11.Http11NioProtocol" maxThreads="150" > clientAuth="false" S

Re: How to monitor performance of tomcat

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Randir, On 5/21/14, 8:32 AM, Randhir Singh wrote: > There is a correction as JAVA_OPTS variable is defined in > catalina.sh under $CATALINA_HOME/bin and we use > $CATALINA_HOME/bin/startup.sh to start tomcat. > $CATALINA_HOME/bin/startup.sh has the

Re: AJP protocol with Apache Tomcat Version 7.0.52

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Pradeep, On 5/21/14, 5:15 PM, Pradeep Kumar G M wrote: > We are using mod_jk AJP connections will always be "waiting" for data when they are not actively processing a request. You should expect to see all your "idle" threads sitting in this state.

Re: AJP protocol with Apache Tomcat Version 7.0.52

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Ravi, On 5/21/14, 2:28 AM, ravishankar_d wrote: > Hi Dan, > > We are using apache web server provided along with RHEL.So I > believe we are getting back port fixes. In the threaddump we are > seeing the below long running threads many times.As ment

Re: Tomcat 7 cannot get ciphers with SHA256 or SHA384

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Sverre, On 5/21/14, 6:21 AM, Sverre Moe wrote: > I have tried running Tomcat with Java 7 and Java 8. Both of these > should support CBC_SHA256 and CBC_SHA384, but only Java 8 supports > GCM_SHA384. I have downloaded the Java cryptographic extensions

[ANN] Apache Tomcat 8.0.8 (beta) available

The Apache Tomcat team announces the immediate availability of Apache Tomcat 8.0.8 (beta). Apache Tomcat 8 is an open source software implementation of the Java Servlet, JavaServer Pages, Java Unified Expression Language and Java WebSocket technologies. Apache Tomcat 8 is aligned with Java EE 7.