Re: Tomcat 7 cannot get ciphers with SHA256 or SHA384

When using JSSE it seems the cipher order is predetermined. http://docs.oracle.com/javase/8/docs/technotes/guides/security/SunProviders.html "cipher suites supported by SunJSSE in preference order and the release in which they were introduced." 2014-05-24 1:15 GMT+02:00 Igor Cicimov : > On 24/0

Re: Tomcat is down or refused connection

On 5/23/2014 5:34 PM, Terence M. Bandoian wrote: On 5/23/2014 1:22 AM, Ballarpure, Akshay (EXT-Tata Consultancy Ser - IN/Hyderabad) wrote: Hello, Soap request is failing with below message in our application. 2014/05/20 06:48:43 [ERROR] (browse_csl) failed to reach startSearch

Re: Tomcat is down or refused connection

On 5/23/2014 1:22 AM, Ballarpure, Akshay (EXT-Tata Consultancy Ser - IN/Hyderabad) wrote: 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]

Re: Tomcat 7 cannot get ciphers with SHA256 or SHA384

On 24/05/2014 1:15 AM, "Sverre Moe" wrote: > > NIO does support them according to the java documentation. I was refering to cipher order and tomcat7 connector documentation where only the apr connector supports the option SSLHonorCipherOrder http://tomcat.apache.org/tomcat-7.0-doc/config/http.ht

Re: Java Wrapper Service -Linux

On 5/23/2014 6:05 AM, vicky wrote: Guys, CAn someone please share the steps needed to configure the Java wrapper service for Tomcat. I'm using Tomcat 7 with JDK 1.7 on a Linux machine I have added the wrapper.conf under "/conf " directory & wrapper script under "/bin". WHile executing the "

Re: AJP protocol with Apache Tomcat Version 7.0.52

On 23/05/2014 19:26, pradeepgm wrote: >> You have a blocking AJP connector (BIO) with maxThreads of 250. >> Therefore that connector can support a maximum of 250 connections. You >> have httpd with MaxClients 1536 and - since AJP uses persistent >> connections - you have httpd trying to create up t

Re: AJP protocol with Apache Tomcat Version 7.0.52

> You have a blocking AJP connector (BIO) with maxThreads of 250. > Therefore that connector can support a maximum of 250 connections. You > have httpd with MaxClients 1536 and - since AJP uses persistent > connections - you have httpd trying to create up to 1536 persistent > connections. The first

Re: AJP protocol with Apache Tomcat Version 7.0.52

On 23/05/2014 17:59, Mark Eggers wrote: > In general, it's not a good idea to reference a zip file. Post > information inline without comments, and with sensitive information > obscured (not removed - since that can alter the configuration meaning). +1 Thanks for doing this. >

Re: AJP protocol with Apache Tomcat Version 7.0.52

On 5/23/2014 8:09 AM, pradeepgm wrote: Attached all files here. Just masked the customer domain. conf-files.zip Please note that we have multiple tomcat instances supported by one common apache httpd server. I just added the one (Tom

Re: Tomcat 7 cannot get ciphers with SHA256 or SHA384

NIO does support them according to the java documentation. These ciphers have been implemented in the JSSE provider. I have no problem making a connection to Tomcat via a Java program using a HttpsConnection and are getting the highest cipher (TLS_ECDHE_RSA_WITH_ AES_256_GCM_SHA384). 2014-05-23 1

Re: AJP protocol with Apache Tomcat Version 7.0.52

Attached all files here. Just masked the customer domain. conf-files.zip Please note that we have multiple tomcat instances supported by one common apache httpd server. I just added the one (Tomcat 7) which is having this issue (serv

Java Wrapper Service -Linux

Guys, CAn someone please share the steps needed to configure the Java wrapper service for Tomcat. I'm using Tomcat 7 with JDK 1.7 on a Linux machine I have added the wrapper.conf under "/conf " directory & wrapper script under "/bin". WHile executing the "./wrapper -c ../conf/wrapper.conf "

Re: CATALINA_PID != real PID

The usual Heisenbug. regards Leon On Fri, May 23, 2014 at 1:24 PM, Арсений Зинченко wrote: > Hi, Leon. > > Thanks for replay. > > Don't know why - but now it works good :-) >

Re: CATALINA_PID != real PID

Hi, Leon. Thanks for replay. Don't know why - but now it works good :-)

Re: CATALINA_PID != real PID

Hello Arseniy, I don't know why it doesn't work for you, it works for me: export CATALINA_PID=/opt/app/tomcat7/pid */opt/app/tomcat7*$ more pid 5856 ps aux | grep 5856: thales5856 0.0 43.6 642472 228788 ? Sl Apr28 29:19 /opt/java/jdk1.7.0_45/bin/java -Djava.util.logging.config.f

CATALINA_PID != real PID

Hi, guys. I set: $ export CATALINA_PID="$CATALINA_HOME/conf/catalina.pid" Started *Tomcat*: $ ./bin/startup.shUsing CATALINA_BASE: /home/tomcats/apache-tomcat-7.0.53Using CATALINA_HOME: /home/tomcats/apache-tomcat-7.0.53Using CATALINA_TMPDIR: /home/tomcats/apache-tomcat-7.0.53/tempUsing JRE_HOM

Re: Tomcat 7 cannot get ciphers with SHA256 or SHA384

On 23/05/2014 5:43 PM, "Sverre Moe" wrote: > > I am using the following ciphers in Tomcat: > ciphers="TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA,TLS

Re: Tomcat 7 cannot get ciphers with SHA256 or SHA384

I am using the following ciphers in Tomcat: ciphers="TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA,TLS_ECDHE_ECDSA_WI

Re: AJP protocol with Apache Tomcat Version 7.0.52

On 23/05/2014 03:42, pradeepgm wrote: > 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=24