Re: Bad Gateway
On 09/10/2013 04:43, Salisbury, Richard W DLA CTR TRANSACTION SERVICES snip/ We confirmed that Tomcat on server-B is configured to handle port 53309, from this excerpt from its server.xml: Connector description=Content Switch HTTPS maxHttpHeaderSize=8192 maxThreads=150 minSpareThreads=25 maxSpareThreads=75 enableLookups=false disableUploadTimeout=true acceptCount=100 scheme=https secure=true keystoreFile=/keystore/server-ks.p12 keystoreType=PKCS12 keystorePass=pass truststoreFile=/keystore/ts.jks truststoreType=JKS truststorePass=pass clientAuth=false algorithm=SunX509 sslProtocol=TLS port=53309 / We confirmed Tomcat was started successfully on server-B and listening on port 53309, from the application log: 2013-08-22 18:01:49,321 INFO : Succesfully started Apache Tomcat/6.0.35 @ Catalina:53309 Any ideas on what might be going on? You appear to be missing SSLEnabled=true on your Tomcat connector. The start-up log messages for that connector will confirm whether that analysis is correct. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Bad Gateway
You appear to be missing SSLEnabled=true on your Tomcat connector. The start-up log messages for that connector will confirm whether that analysis is correct. Mark Thank you Mark. That was it. I added SSLEnabled=true to the Tomcat connector, restarted Tomcat and the Bad Gateway error disappeared. Don't know why the production system works without that setting, unless it is because it is a different version. Anyway, we thank you very much for your assistance. This is awesome. Richard - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Bad Gateway
On 09/10/2013 16:21, Salisbury, Richard W DLA CTR TRANSACTION SERVICES wrote: You appear to be missing SSLEnabled=true on your Tomcat connector. The start-up log messages for that connector will confirm whether that analysis is correct. Mark Thank you Mark. That was it. Happy to help. I added SSLEnabled=true to the Tomcat connector, restarted Tomcat and the Bad Gateway error disappeared. Don't know why the production system works without that setting, unless it is because it is a different version. It could be. You might want to check that because any earlier version is likely to have known security vulnerabilities (5.5.x certainly does). That might be an issue depending on the nature of your production system. Mark Anyway, we thank you very much for your assistance. This is awesome. Richard - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
