tion stays outside of the
> pool for to long. In some cases this is adequate.
>
>
Thanks a lot for your help, I'm going to read up about that !
Raphael
--
View this message in context:
http://www.nabble.com/Blocked-threads-in-Tomcat-web-app-tp2445768
On 13.07.2009 11:31, Raphael Neve wrote:
>
> Rainer Jung-3 wrote:
>>
>> [...]
>>
>> Yup, and the code run by the finalizer makes a network call (likely to
>> the database), which seems to be a very bad pattern. Finalizers are not
>> a great idea by themselves, but one needs to keep them as simple
aphael
--
View this message in context:
http://www.nabble.com/Blocked-threads-in-Tomcat-web-app-tp24457682p24458570.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubs
On 13.07.2009 11:05, Raphael Neve wrote:
>
> Rainer Jung-3 wrote:
>> TP-Processor16 owns lock at 0x73a71c40 and thus blocks TP12, TP5 and TP1.
>>
>> TP16 and TP2 both wait for lock 0x73a71dd0. The thread holding this lock
>> is not in your dump.
>>
>> Since the lock is of type
>> org.firebirdsql.g
, is that right ? The next question of course is : what is
making the finalizer keep that lock ?
Thanks for your insight,
Raphael
http://www.nabble.com/file/p24458247/thread%2Bdump.txt thread+dump.txt
--
View this message in context:
http://www.n
On 13.07.2009 10:12, Raphael Neve wrote:
> Hello all,
>
> I have a problem with a web application using Tomcat 5.5.27 under Fedora
> Linux and database Firebird 2.1.
>
> The application runs fine for a day or so, then I begin getting blocked
> threads. Eventually, the heap space runs out and the
ction to the database,
how can they be blocking each other ?
Thanks for any help, suggestions, etc !
Raphael Neve
--
View this message in context:
http://www.nabble.com/Blocked-threads-in-Tomcat-web-app-tp24457682p24457682.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
---
