Sent: Friday, April 16, 2010 4:10 PM
To: Tomcat Users List
Subject: Re: Hung threads
2010/4/16 Jeffrey Janner
> Well, it's definitely deadlocking once it hits the maxThreads limit.
The worker is returned to the workers pool by an
AprEndpoint.recycleWorkerThread(..) call. If that call is sk
And the solution to the attachment issue is removing the PGP signing stuff from
your message in my reply.
-Original Message-
From: Jeffrey Janner [mailto:jeffrey.jan...@polydyne.com]
Sent: Saturday, April 17, 2010 1:04 PM
To: Tomcat Users List
Subject: RE: Hung threads
Chris -
I
riginal Message-
From: Konstantin Kolinko [mailto:knst.koli...@gmail.com]
Sent: Friday, April 16, 2010 4:10 PM
To: Tomcat Users List
Subject: Re: Hung threads
2010/4/16 Jeffrey Janner
> Well, it's definitely deadlocking once it hits the maxThreads limit.
The worker is r
mailto:ch...@christopherschultz.net]
Sent: Friday, April 16, 2010 3:50 PM
To: Tomcat Users List
Subject: Re: Hung threads
Jeffrey,
BTW your mailer and/or mail exchanger sucks... it puts your message into
the html-only portion of a multipart/alternative message which means
that basically your m
2010/4/16 Jeffrey Janner
> Well, it's definitely deadlocking once it hits the maxThreads limit.
The worker is returned to the workers pool by an
AprEndpoint.recycleWorkerThread(..) call. If that call is skipped, the
workers will leak. That is theoretically. I do not remember any
reports on such a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeffrey,
BTW your mailer and/or mail exchanger sucks... it puts your message into
the html-only portion of a multipart/alternative message which means
that basically your messages don't show up properly. Instead, I see the
"confidential warning" that
ursday, April 15, 2010 11:42 AM
To: Tomcat Users List
Subject: Re: Hung threads
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Konstantin,
On 4/15/2010 10:19 AM, Konstantin Kolinko wrote:
> +1.
> If it is stuck there, it will not accept any more incoming requests.
Thanks for the confirmation
uming
it's the same base version, such as upgrading from 5.5.20 to 5.5.30).
-Original Message-
From: Konstantin Kolinko [mailto:knst.koli...@gmail.com]
Sent: Thursday, April 15, 2010 9:20 AM
To: Tomcat Users List
Subject: Re: Hung threads
2010/4/13 Christopher Schultz:
-BEGI
code.
Thanks for the sympathy.
Jeff
-Original Message-
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Sent: Thursday, April 15, 2010 11:42 AM
To: Tomcat Users List
Subject: Re: Hung threads
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Konstantin,
On 4/15/2010 10:19 AM, Kons
installer version out there for that.
Jeff
-Original Message-
From: Konstantin Kolinko [mailto:knst.koli...@gmail.com]
Sent: Thursday, April 15, 2010 9:20 AM
To: Tomcat Users List
Subject: Re: Hung threads
2010/4/13 Christopher Schultz :
> -BEGIN PGP SIGNED MESSAGE-
> Has
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Konstantin,
On 4/15/2010 10:19 AM, Konstantin Kolinko wrote:
> +1.
> If it is stuck there, it will not accept any more incoming requests.
Thanks for the confirmation that Jeffrey is deadlocked.
> It might be that you bumped into BZ 48843
> https://i
2010/4/13 Christopher Schultz :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Jeff,
>
> Okay, you're running into the limits of my knowledge of the APR
> connector's internals.
>
> On 4/13/2010 1:24 PM, Jeffrey Janner wrote:
>> "http-172.16.27.1-443-Acceptor-0" daemon prio=6 tid=0x6425c400
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeff,
Okay, you're running into the limits of my knowledge of the APR
connector's internals.
On 4/13/2010 1:24 PM, Jeffrey Janner wrote:
> "http-172.16.27.1-443-Acceptor-0" daemon prio=6 tid=0x6425c400 nid=0xb6c4 in
> Object.wait() [0x65d7f000]
>
You're right, that was weird. Not sure what did that. It wasn't that way in
the original file. And it wasn't that way before I hit send. Here's the rest of
the dump, picking up from just before "encoding":
"RMI Scheduler(0)" daemon prio=6 tid=0x64885400 nid=0xaa8c waiting on condition
[0x6707
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeffrey,
On 4/13/2010 12:46 PM, Jeffrey Janner wrote:
> "http-172.16.27.1-443-Poller-7" daemon prio=6
> tid=0x649cnVVpEWVZadmQxSnJTbEpXDQpWVnBFV1ZaYWRtUXhTbkpUYkVwWERRcFdWbkJGVjFaYVlXUnRVWGhU
> YmtwVVlrVndXRVJSY0ZkV2JrSkdWakZhWVZsWFVuUlZXR2hVDQpZbXR3
HTTPS inside the app.
Unfortunately, doesn't appear to be available in 5.5.x.
And before the inevitable, the available heap looked just fine.
-Original Message-
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Sent: Tuesday, April 13, 2010 11:24 AM
To: Tomcat Users List
Subject
Thanks, but is not available in 5.5 -- at least according to
the documentation.
-Original Message-
From: Filip Hanik - Dev Lists [mailto:devli...@hanik.com]
Sent: Tuesday, April 13, 2010 11:03 AM
To: Tomcat Users List
Subject: Re: Hung threads
Looks like just idle threads, not really a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeff,
On 4/13/2010 12:10 PM, Jeffrey Janner wrote:
> Sorry I was extremely clear. My config has each customer in a
> separate service structure, so each get his own set of connectors
> (IPs).
Gotcha.
> Yes, I am unable to get a response on this s
[mailto:ch...@christopherschultz.net]
Sent: Tuesday, April 13, 2010 10:45 AM
To: Tomcat Users List
Subject: Re: Hung threads
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeffrey,
On 4/13/2010 10:44 AM, Jeffrey Janner wrote:
> I had a connector go from minimal connections (restart) to all thre
Looks like just idle threads, not really a problem
If you want the thread pool to shrink and stop idle threads, use an
element in server.xml
Filip
On 04/13/2010 08:50 AM, Jeffrey Janner wrote:
Before someone asks for it:
-Original Message-
From: Jeffrey Janner [mailto:jeffrey
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeffrey,
On 4/13/2010 10:44 AM, Jeffrey Janner wrote:
> I had a connector go from minimal connections (restart) to all threads
> hung overnight.
>
> The current thread dump shows the threads as follows:
>
> "http-172.16.27.1-443-150" daemon prio=6 t
Before someone asks for it:
-Original Message-
From: Jeffrey Janner [mailto:jeffrey.jan...@polydyne.com]
Sent: Tuesday, April 13, 2010 9:44 AM
To: Tomcat Users List
Subject: Hung threads
I had a connector go from minimal connections (restart) to all threads
hung overnight.
The curr
22 matches
Mail list logo