Rainer Jung-3 wrote:
>
>
> You might want to look at Bloch's book "Effective Java", which has a
> section called "Avoid finalizers". The page
>
> http://java.sun.com/developer/technicalArticles/javase/finalization/
>
> also has some introductory material.
>
> The dbcp pool for instance has
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
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 as
> possible. Doing network communication in
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
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.gds.impl.wire.isc_db_handle_impl, it seems eith
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
