RE: log4j2 configuration in tomcat 8.5.5

2016-09-21 Thread Chen Levy
Bill, From: Mark Thomas Sent: Wednesday, September 21, 2016 17:58 To: Tomcat Users List Subject: Re: log4j2 configuration in tomcat 8.5.5 On 21/09/2016 22:49, Bill Phillips wrote: > My team has elected me to upgrade Tomcat from 7.X to 8.5.5+ on our very > old and very large web application. > >

Re: TLS 1.2 Handshake on Tomcat 7.0.39 Getting Internal Error: Key format must be RAW

2016-09-21 Thread Igor Cicimov
On 20 Sep 2016 2:45 am, "Dono Harjanto" wrote: > > Hi All, > > > We have a web app deployed on 3 different servers, all running Tomcat 7.0.39 and Java 8 (update 101/102). Here is the operating system on each server: > > - Production: CentOS 6.4 > > - Staging 1: CentOS

Re: log4j2 configuration in tomcat 8.5.5

2016-09-21 Thread Mark Thomas
On 21/09/2016 22:49, Bill Phillips wrote: > My team has elected me to upgrade Tomcat from 7.X to 8.5.5+ on our very > old and very large web application. > > Under Tomcat 7.x, this application uses the tomcat-juli-adapters to replace > JULI with log4j1.16. Worked like a charm for years. > > >

log4j2 configuration in tomcat 8.5.5

2016-09-21 Thread Bill Phillips
My team has elected me to upgrade Tomcat from 7.X to 8.5.5+ on our very old and very large web application. Under Tomcat 7.x, this application uses the tomcat-juli-adapters to replace JULI with log4j1.16. Worked like a charm for years. Under Tomcat 8.5.5, I'm getting exceptions such as:

RE: AT WITS END regarding JVM arguments

2016-09-21 Thread Jeffrey Janner
Sorry for reviving an old thread, but this one caught my eye and I just had to make some, admittedly off-topic, comments per the concept of assumptions that pervaded a number of the posts here. 1) Having worked with all manner of IBM systems, as well as some environments you guys probably

RE: Apache TomCat 5.5

2016-09-21 Thread Jeffrey Janner
Mary - First, sorry for the top-post. I noticed in your original post that you have upgraded to the latest Java 8, and nearly latest Windows version (at least new than the release available when Tomcat 5.5 was first available). I don't understand why you can't just go ahead and upgrade to the

RE: TLS 1.2 Handshake on Tomcat 7.0.39 Getting Internal Error: Key format must be RAW

2016-09-21 Thread Dono Harjanto
Jose, > -Original Message- > From: Jose María Zaragoza [mailto:demablo...@gmail.com] > Sent: Wednesday, September 21, 2016 11:46 AM > To: Tomcat Users List > Subject: Re: TLS 1.2 Handshake on Tomcat 7.0.39 Getting Internal Error: Key > format must be RAW > >

RE: TLS 1.2 Handshake on Tomcat 7.0.39 Getting Internal Error: Key format must be RAW

2016-09-21 Thread Dono Harjanto
Ron, > -Original Message- > From: André Warnier (tomcat) [mailto:a...@ice-sa.com] > Sent: Wednesday, September 21, 2016 10:17 AM > To: users@tomcat.apache.org > Subject: Re: TLS 1.2 Handshake on Tomcat 7.0.39 Getting Internal Error: Key > format must be RAW > > On 21.09.2016 18:49,

Re: TLS 1.2 Handshake on Tomcat 7.0.39 Getting Internal Error: Key format must be RAW

2016-09-21 Thread Jose María Zaragoza
2016-09-21 19:16 GMT+02:00 André Warnier (tomcat) : > On 21.09.2016 18:49, Christopher Schultz wrote: >> >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA256 >> >> Ron, >> >> On 9/21/16 11:58 AM, Roskens, Ronald wrote: -Original Message- From: Christopher

Re: TLS 1.2 Handshake on Tomcat 7.0.39 Getting Internal Error: Key format must be RAW

2016-09-21 Thread tomcat
On 21.09.2016 18:49, Christopher Schultz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Ron, On 9/21/16 11:58 AM, Roskens, Ronald wrote: -Original Message- From: Christopher Schultz [mailto:ch...@christopherschultz.net] Sent: Wednesday, September 21, 2016 9:40 AM To: Tomcat

Re: TLS 1.2 Handshake on Tomcat 7.0.39 Getting Internal Error: Key format must be RAW

2016-09-21 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Ron, On 9/21/16 11:58 AM, Roskens, Ronald wrote: >> -Original Message- From: Christopher Schultz >> [mailto:ch...@christopherschultz.net] Sent: Wednesday, September >> 21, 2016 9:40 AM To: Tomcat Users List Subject: Re: TLS 1.2 >> Handshake

Re: Apache TomCat 5.5

2016-09-21 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Mary, On 9/21/16 10:51 AM, Pham, Mary (NIH/OD/ORS) [E] wrote: > Thank you. Chris, Chuck, Andre, Mark who had answered and I've > done this far. My report. > > - I installed the "URL rewrite" module on IIS 7. To make short, > it worked. http to

RE: TLS 1.2 Handshake on Tomcat 7.0.39 Getting Internal Error: Key format must be RAW

2016-09-21 Thread Roskens, Ronald
> -Original Message- > From: Christopher Schultz [mailto:ch...@christopherschultz.net] > Sent: Wednesday, September 21, 2016 9:40 AM > To: Tomcat Users List > Subject: Re: TLS 1.2 Handshake on Tomcat 7.0.39 Getting Internal Error: Key > format must be RAW > > This may be the most

RE: Apache TomCat 5.5

2016-09-21 Thread Pham, Mary (NIH/OD/ORS) [E]
Thank you. Chris, Chuck, Andre, Mark who had answered and I've done this far. My report. - I installed the "URL rewrite" module on IIS 7. To make short, it worked. http to https redirected then enforced hsts on the IIS site. - but broke all the scripts run on Tomcat due to Strick Transport

Re: TLS 1.2 Handshake on Tomcat 7.0.39 Getting Internal Error: Key format must be RAW

2016-09-21 Thread tomcat
On 21.09.2016 16:40, Christopher Schultz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 André, On 9/20/16 7:51 PM, André Warnier (tomcat) wrote: On 20.09.2016 19:21, Dono Harjanto wrote: Hi André, -Original Message- From: André Warnier (tomcat) [mailto:a...@ice-sa.com]

Re: TLS 1.2 Handshake on Tomcat 7.0.39 Getting Internal Error: Key format must be RAW

2016-09-21 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 André, On 9/20/16 7:51 PM, André Warnier (tomcat) wrote: > On 20.09.2016 19:21, Dono Harjanto wrote: >> Hi André, >> >>> -Original Message- From: André Warnier (tomcat) >>> [mailto:a...@ice-sa.com] Sent: Tuesday, September 20, 2016 12:13

AW: Tomcat 7.0.65 + Java 6 Update 121 64-bit - Cipher Suite Names

2016-09-21 Thread Kreuser, Peter
Roman, >I know it did not worked because as soon as I add the ciphers entry to the >SSL HTTPS connector in the server.xml file, it tells me that value is not >supported. > >On Wed, Sep 21, 2016 at 6:45 PM, Mark Thomas wrote: > >> On 21/09/2016 11:22, Román Valoria wrote: >> >

Re: Tomcat 7.0.65 + Java 6 Update 121 64-bit - Cipher Suite Names

2016-09-21 Thread Román Valoria
I know it did not worked because as soon as I add the ciphers entry to the SSL HTTPS connector in the server.xml file, it tells me that value is not supported. On Wed, Sep 21, 2016 at 6:45 PM, Mark Thomas wrote: > On 21/09/2016 11:22, Román Valoria wrote: > > Before anyone

Re: Tomcat 7.0.65 + Java 6 Update 121 64-bit - Cipher Suite Names

2016-09-21 Thread Harrie Robins
Please see: https://community.qualys.com/thread/11882 Disable the weak ciphers. The Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy is needed when you want to run AES256 (you want this). Regards, Harrie On 21 September 2016 at 12:18, Román Valoria

AW: Tomcat 7.0.65 + Java 6 Update 121 64-bit - Cipher Suite Names

2016-09-21 Thread Kreuser, Peter
Roman, > On 21/09/2016 11:22, Román Valoria wrote: > > Before anyone tells me, I cannot upgrade either Tomcat or Java to the > > latest major release. > > > > My setup is running on Windows Server 2008 R2 64-bit OS. > > What configuration have you tried? > > How do you know it didn't work? >

Re: Tomcat 7.0.65 + Java 6 Update 121 64-bit - Cipher Suite Names

2016-09-21 Thread Mark Thomas
On 21/09/2016 11:22, Román Valoria wrote: > Before anyone tells me, I cannot upgrade either Tomcat or Java to the > latest major release. > > My setup is running on Windows Server 2008 R2 64-bit OS. What configuration have you tried? How do you know it didn't work? Mark > > On Wed, Sep 21,

Re: Tomcat 7.0.65 + Java 6 Update 121 64-bit - Cipher Suite Names

2016-09-21 Thread Román Valoria
Before anyone tells me, I cannot upgrade either Tomcat or Java to the latest major release. My setup is running on Windows Server 2008 R2 64-bit OS. On Wed, Sep 21, 2016 at 6:18 PM, Román Valoria wrote: > Dear all: > > I need to configure Tomcat 7.0.65 with Java 6, both

Tomcat 7.0.65 + Java 6 Update 121 64-bit - Cipher Suite Names

2016-09-21 Thread Román Valoria
Dear all: I need to configure Tomcat 7.0.65 with Java 6, both 64-bit. I have managed to make it work with update 121 in using the SSL protocol TLS 1.2. Now I need to exert some control over the cipher suites used on that protocol. I am unable to come up with the list of supported cipher suite

Re: NPE in SecureNioChannel (TC 8.5.5)

2016-09-21 Thread Rémy Maucherat
2016-09-20 21:51 GMT+02:00 Colin Ingarfield : > Hello, > > A thread from a day or two ago mentioned a NPE in SecureNioChannel > when the connector is configured with Http11NioProtocol. OP mentioned > using Http11Nio2Protocol resolves the issue. I am also seeing this >