AW: AW: [tomcat 5.5.26] why are not all log4j.properties files parsed

2013-03-28 Thread Stadelmann Josef
Hi Chris my comment+++ -Ursprüngliche Nachricht- Von: Christopher Schultz [mailto:ch...@christopherschultz.net] Gesendet: Mittwoch, 27. März 2013 19:35 An: Tomcat Users List Betreff: Re: AW: [tomcat 5.5.26] why are not all log4j.properties files parsed -BEGIN PGP SIGNED

Tomcat JDBC Connection Pool - Deadlock

2013-03-28 Thread amit shah
Hello, I am using the tomcat jdbc connection pool independently in my web application which is deployed on glassfish web server. While performing a database operation, our application goes into a deadlock state. The two threads involved in the deadlock have the below traces (from a thread

RE: Tomcat JDBC Connection Pool - Deadlock

2013-03-28 Thread Caldarale, Charles R
From: amit shah [mailto:amits...@gmail.com] To: Tomcat Users List; d...@tomcat.apache.org Do not cross-post. This belongs only on the users list. Read (and follow) the mailing list usage rules. Subject: Tomcat JDBC Connection Pool - Deadlock The two threads involved in the deadlock have

Re: AW: AW: [tomcat 5.5.26] why are not all log4j.properties files parsed

2013-03-28 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Josef, On 3/28/13 5:54 AM, Stadelmann Josef wrote: -Ursprüngliche Nachricht- Von: Christopher Schultz [mailto:ch...@christopherschultz.net] Yeah, that'll do it: log4j is probably only being initialized once because you have it in a

Re: Tomcat JDBC Connection Pool - Deadlock

2013-03-28 Thread amit shah
I copied the dev group too since it involved technical details (thread dumps, source code etc). Sorry if that sounds incorrect. The traces I added are not incomplete. They are the ones we generated through the jmx api - ManagementFactory.getThreadMXBean().dumpAllThreads(true, true); On Thu, Mar

Re: Apache Tomcat 7.0.035 and IPv6 environment

2013-03-28 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Geet, On 3/28/13 1:32 AM, Geett Chanddra Singha wrote: Thanks Konstantin Kolinko! It will be great help for me if you could provide steps to configure the same or documents, where in I could get configuration steps. Well, you could search

RE: Tomcat JDBC Connection Pool - Deadlock

2013-03-28 Thread Caldarale, Charles R
From: amit shah [mailto:amits...@gmail.com] Subject: Re: Tomcat JDBC Connection Pool - Deadlock I copied the dev group too since it involved technical details (thread dumps, source code etc). Sorry if that sounds incorrect. It was incorrect, as is your top-posting. Don't do either. The

Re: Tomcat JDBC Connection Pool - Deadlock

2013-03-28 Thread Daniel Mikusa
On Mar 28, 2013, at 8:27 AM, amit shah wrote: Hello, I am using the tomcat jdbc connection pool independently in my web Because you are using this independently you are going to need to tell us the version of the connection pool that you have included with your application. Also, a

Re: Tomcat support for JNDIRealm LDAPS connections

2013-03-28 Thread Felix Schumacher
Hi Jon, first of all, it seems that you have hijacked a thread by replying to a mail from this mailing list and changing the subject of the thread. That might be a reason, why you have not got any answers to your question yet. Am 27.03.2013 17:03, schrieb Wilmoth, Jon: After searching

AW: AW: AW: [tomcat 5.5.26] why are not all log4j.properties files parsed

2013-03-28 Thread Stadelmann Josef
Hi Chris are you in fact saying that we can use the latest Tomcat on OpenVMS Itanium 8.4 given this OpenVMS has yet a oracle/hp java jdk 1.6.0-04 installed? any references for that Josef -Ursprüngliche Nachricht- Von: Christopher Schultz [mailto:ch...@christopherschultz.net]

RE: Adding Content-Length response header

2013-03-28 Thread Leo Donahue - RDSA IT
-Original Message- From: Christopher Schultz [mailto:ch...@christopherschultz.net] Subject: Adding Content-Length response header -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 All, Here's the situation I have: I've got a response that I'm fairly sure fits into the response's buffer

RE: Velocity Logging

2013-03-28 Thread Bruce Pease
Since we are not using velocity we were able to remove the velocity libraries, and this issue was resolved. -Original Message- From: Christopher Schultz [mailto:ch...@christopherschultz.net] Sent: Wednesday, March 27, 2013 2:38 PM To: Tomcat Users List Subject: Re: Velocity Logging

RE: AW: AW: [tomcat 5.5.26] why are not all log4j.properties files parsed

2013-03-28 Thread Caldarale, Charles R
From: Stadelmann Josef [mailto:josef.stadelm...@axa-winterthur.ch] Subject: AW: AW: AW: [tomcat 5.5.26] why are not all log4j.properties files parsed are you in fact saying that we can use the latest Tomcat on OpenVMS Itanium 8.4 given this OpenVMS has yet a oracle/hp java jdk 1.6.0-04

Re: Can ClientAbortException be circumvented?

2013-03-28 Thread Thad Humphries
On Wed, Mar 27, 2013 at 6:09 PM, Christopher Schultz ch...@christopherschultz.net wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Thad, On 3/27/13 5:20 PM, Thad Humphries wrote: On Tue, Mar 26, 2013 at 3:56 PM, Christopher Schultz ch...@christopherschultz.net wrote: Thad,

Apache Accessing Tomcat Issue

2013-03-28 Thread Chris Arnold
Apache Tomcat/7.0.30 on SLES11 SP2. I am trying to configure access to a webapp using http://share.domain.com. This webapp uses port 8080 and works fine from inside the LAN. However, we have an apache2 server acting as a proxy and we want users to not have to type in a port number. Now when

RE: Tomcat support for JNDIRealm LDAPS connections

2013-03-28 Thread Wilmoth, Jon
Thanks Felix. You're correct for a single auth SSL connection the password was not required (I assume a mutual auth connection would work as well if the keystore for the client cert was physically different). I assumed that since it was provided in the connector config

Re: Adding Content-Length response header

2013-03-28 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Konstantin, On 3/26/13 11:08 AM, Konstantin Kolinko wrote: 2. Are you interested in GET/POST requests, or HEAD requests? HEAD requests were fixed by this commit, from 5 days ago http://svn.apache.org/r1459087 I am dealing almost entirely