Re: Tomcat 8.0.39 and tomcat 8.5.8 fails handling requsest

On 16/11/2016 20:05, Mark Eggers wrote: > Mark, > > On 11/16/2016 12:23 AM, Mark Thomas wrote: >> On 15/11/2016 22:36, Zdeněk Henek wrote: >>> Hi, >>> >>> we are using tomcat 8.0.30 without problems. >>> >>> I have tested upgrade to 8.0.38 today and I got this error >>> More env. details JDK 8,

Re: Need Help on Tomcat 8.1.1 SSL Public Facing URL !!

Hi, 2016-11-17 7:51 GMT+02:00 : > > Hi Group, > > Please help in resolving the issue with Public Facing URL of Tomcat server. Currently the existing configuration is as follows : > > > 1) Tomcat 8.1.1 is installed on Red-Hat Linux OS along with Jdk1.7

Re: SSL on Tomcat7 on AWS not connecting

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 George, On 11/16/16 12:38 PM, George Chanady wrote: > I hope someone can help.I have exhausted all my troubleshooting > skills and all of my newbie Linux knowledge and I am at the end of > my rope. > > All documentation from around the web always

Re: Need Help on Tomcat 8.1.1 SSL Public Facing URL !!

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Ramagopala, On 11/17/16 12:51 AM, ramagopala.chaturved...@wipro.com wrote: > Please help in resolving the issue with Public Facing URL of > Tomcat server. Currently the existing configuration is as follows > : > > > 1) Tomcat 8.1.1 is

Re: Tomcat6 enabling SSL for JDBC during startup

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Mohan, 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. >> From the logs it looks like SSL is getting

Sanity Check

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 All, I've got a problem with a vendor and I'd like another opinion just to make sure I'm not crazy. The vendor and I have a difference of opinion about how a character should be encoded in an HTTP POST request. The vendor's API officially should

RE: SSL on Tomcat7 on AWS not connecting

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://bageoconsultants.com:8443/ * Trying 52.54.85.95... * Connected to bageoconsultants.com

Re: Sanity Check

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 not crazy. The vendor and I have a difference of opinion > about how a character should be encoded in an HTTP POST

RE: SSL on Tomcat7 on AWS not connecting

Hi Igor, I am too new at Linux to know if the output from this is bad, other than the first line. Not really sure what the rest is telling me. [ec2-user@ip-172-31-52-159 logs]$ tail -f catalina.out java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method

Re: Tomcat 8.0.39 and tomcat 8.5.8 fails handling requsest

Mark, On 11/17/2016 1:06 PM, Mark Thomas wrote: > On 17/11/2016 21:29, Mark Eggers wrote: >> Mark, >> >> >> On 11/17/2016 2:00 AM, Mark Thomas wrote: >>> On 16/11/2016 20:05, Mark Eggers wrote: Mark, On 11/16/2016 12:23 AM, Mark Thomas wrote: > On 15/11/2016 22:36, Zdeněk Henek

Re: Tomcat 8.0.39 and tomcat 8.5.8 fails handling requsest

Mark, On 11/17/2016 2:00 AM, Mark Thomas wrote: > On 16/11/2016 20:05, Mark Eggers wrote: >> Mark, >> >> On 11/16/2016 12:23 AM, Mark Thomas wrote: >>> On 15/11/2016 22:36, Zdeněk Henek wrote: Hi, we are using tomcat 8.0.30 without problems. I have tested upgrade to

Re: Tomcat 8.0.39 and tomcat 8.5.8 fails handling requsest

On 17/11/2016 21:29, Mark Eggers wrote: > Mark, > > > On 11/17/2016 2:00 AM, Mark Thomas wrote: >> On 16/11/2016 20:05, Mark Eggers wrote: >>> Mark, >>> >>> On 11/16/2016 12:23 AM, Mark Thomas wrote: On 15/11/2016 22:36, Zdeněk Henek wrote: > Hi, > > we are using tomcat 8.0.30

Multi-level context path

I can't get my multi-level context path to deploy correctly. In Tomcat 5.5.26 foo#bar.war placed in my webapps directory deploys to /foo/bar. This is how I think is should work. In Tomcat 8.0.39 foo#bar.war placed in my webapps directory deploys to /foo#bar. It is like Tomcat doesn't recognize

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

On 11/17/16, 9:34 AM, Christopher Schultz wrote: Presumably, you have httpd out in front of your Tomcat instances? I wouldn't know. Tomcat is running by itself, rather than under Apache (or anything else), using JSSE, rather than OpenSSL. Connector tag is: Two other details (the

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

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 James, On 11/17/16 11:54 AM, James H. H. Lampert wrote: > Ladies and Gentlemen: > > Got a customer box, Tomcat 7.0.47 running on an AS/400, and I'm > getting a lot of >> Nov 17, 2016 3:39:44 AM org.apache.coyote.ajp.AjpMessage >> processHeader

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

Ladies and Gentlemen: Got a customer box, Tomcat 7.0.47 running on an AS/400, and I'm getting a lot of Nov 17, 2016 3:39:44 AM org.apache.coyote.ajp.AjpMessage processHeader SEVERE: Invalid message received with signature 18245 with occasional Nov 17, 2016 3:41:06 AM

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

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 James, On 11/17/16 12:52 PM, James H. H. Lampert wrote: > On 11/17/16, 9:34 AM, Christopher Schultz wrote: > >> Presumably, you have httpd out in front of your Tomcat >> instances? > > I wouldn't know. Tomcat is running by itself, rather than

Re: Sanity Check

-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 not

RE: Need Help on Tomcat 8.0.14.0 SSL Public Facing URL !!

Hi Violeta, Currently the existing configuration is as follows : 1) Server version: Apache Tomcat/8.0.14 Server built: Sep 24 2014 09:01:51 Server number: 8.0.14.0 OS Name:Linux OS Version: 3.10.0-229.el7.x86_64 JVM Version:1.8.0_51-b16 2)Tomcat is enabled with SSL and able

Re: Tomcat6 enabling SSL for JDBC during startup

On Thu, Nov 17, 2016 at 7:13 AM, Christopher Schultz < ch...@christopherschultz.net> wrote: > king for help in correcting the problems that have caused the > messages in the first place? > Chris - Both. I would like to know why they started appearing in the catalina logs and how to correct the