Re: SSL on Tomcat7 on AWS not connecting

2016-11-18 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 George, On 11/17/16 4:48 PM, George Chanady wrote: > Chris, > > I tried curl with the -tls1 switch and received the same error. > > [ec2-user@ip-172-31-52-159 bin]$ curl -vk > https://bageoconsultants.com:8443 -tls1 * Rebuilt URL to: > https:/

Re: Getting "Invalid message received with signature xxxxx" messages in catalina.out

2016-11-18 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 James, On 11/18/16 2:39 PM, Christopher Schultz wrote: > James, > > On 11/18/16 2:06 PM, James H. H. Lampert wrote: >> On 11/18/16, 9:08 AM, Caldarale, Charles R wrote: >>> No, 8009 is the default port for communication between httpd >>> and Tomcat

Re: Tomcat6 enabling SSL for JDBC during startup

2016-11-18 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Kumar, On 11/16/16 5:01 PM, Mohan Kumar wrote: > I'm using Tomcat 6.0.29 version with Java 1.6.0_45 on Windows > server 2008 and started noticing SSL related information in > Catalina logs recently. Upgrade upgrade upgrade! All 3 of those component

Re: Getting "Invalid message received with signature xxxxx" messages in catalina.out

2016-11-18 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 James, On 11/18/16 2:06 PM, James H. H. Lampert wrote: > On 11/18/16, 9:08 AM, Caldarale, Charles R wrote: >> No, 8009 is the default port for communication between httpd and >> Tomcat. 8005 is the default shutdown port. > >> Correct. If you're

RE: Getting "Invalid message received with signature xxxxx" messages in catalina.out

2016-11-18 Thread Caldarale, Charles R
> From: James H. H. Lampert [mailto:jam...@touchtonecorp.com] > Subject: Re: Getting "Invalid message received with signature x" messages > in catalina.out > > No, 8009 is the default port for communication between httpd and Tomcat. > > 8005 is > > the default shutdown port. > > If you'r

Re: Sanity Check

2016-11-18 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Konstantin, On 11/18/16 2:10 PM, Konstantin Kolinko wrote: > One more authority, that I forgot to mention in my mail: IANA > registry of mime types > > Registry: > https://www.iana.org/assignments/media-types/media-types.xhtml > > Registration en

Re: Getting "Invalid message received with signature xxxxx" messages in catalina.out

2016-11-18 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Chuck, On 11/18/16 12:08 PM, Caldarale, Charles R wrote: >> From: James H. H. Lampert [mailto:jam...@touchtonecorp.com] >> Subject: Re: Getting "Invalid message received with signature >> x" messages in catalina.out > >> This is interesting: >

Re: Sanity Check

2016-11-18 Thread Konstantin Kolinko
2016-11-18 19:02 GMT+03:00 Christopher Schultz : > André, > > On 11/18/16 3:50 AM, André Warnier (tomcat) wrote: >> On 18.11.2016 05:56, Christopher Schultz wrote: >>> Since UTF-8 is supposed to be the "official" character encoding, >> >> Now where is that specified ? As far as I know, the default

Re: Getting "Invalid message received with signature xxxxx" messages in catalina.out

2016-11-18 Thread James H. H. Lampert
On 11/18/16, 9:08 AM, Caldarale, Charles R wrote: No, 8009 is the default port for communication between httpd and Tomcat. 8005 is the default shutdown port. Correct. If you're not using it, remove (or comment out) the declaration. Fascinating. Can somebody point me to the right docs, so

RE: Getting "Invalid message received with signature xxxxx" messages in catalina.out

2016-11-18 Thread Caldarale, Charles R
> From: James H. H. Lampert [mailto:jam...@touchtonecorp.com] > Subject: Re: Getting "Invalid message received with signature x" messages > in catalina.out > This is interesting: > > Isn't 8009 some sort of backchannel control port, perhaps the one used > for controlled shutdown of Tomca

Re: Getting "Invalid message received with signature xxxxx" messages in catalina.out

2016-11-18 Thread tomcat
On 18.11.2016 17:56, James H. H. Lampert wrote: On 11/17/16, 9:00 PM, Christopher Schultz wrote: There must be another connector. This one uses HTTP, and the error messages you posted are using AJP. Do you have a connector in conf/server.xml that you thought was disabled, but isn't? Dear Mr.

Re: Sanity Check

2016-11-18 Thread tomcat
On 18.11.2016 17:02, Christopher Schultz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 André, On 11/18/16 3:50 AM, André Warnier (tomcat) wrote: On 18.11.2016 05:56, Christopher Schultz wrote: Since UTF-8 is supposed to be the "official" character encoding, Now where is that specif

Re: Getting "Invalid message received with signature xxxxx" messages in catalina.out

2016-11-18 Thread James H. H. Lampert
On 11/17/16, 9:00 PM, Christopher Schultz wrote: There must be another connector. This one uses HTTP, and the error messages you posted are using AJP. Do you have a connector in conf/server.xml that you thought was disabled, but isn't? Dear Mr. Schultz: This is interesting: Isn't 8009 so

Re: Sanity Check

2016-11-18 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 André, On 11/18/16 3:50 AM, André Warnier (tomcat) wrote: > On 18.11.2016 05:56, Christopher Schultz wrote: >> Since UTF-8 is supposed to be the "official" character encoding, > > Now where is that specified ? As far as I know, the default > chars

Re: Sanity Check

2016-11-18 Thread tomcat
On 18.11.2016 05:56, Christopher Schultz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Konstantin, On 11/17/16 4:58 PM, Konstantin Kolinko wrote: 2016-11-17 17:21 GMT+03:00 Christopher Schultz : All, I've got a problem with a vendor and I'd like another opinion just to make sure I'm