Thanks Armin,
I have set the exhaust pool = 2 (to grow). I do close the PB instances
after use. Wondering if anybody have experienced this problem, Iam using
1.0 rc4 . Is there a way to debug ?. The CPU utilization grows too high on
a big machine which almost disables anyother user to do anything on that
machine. Maybe it is something else, Iam trying to debug as much possible.
Thanks n Rgds,
Zabi.
Armin Waibel <[EMAIL PROTECTED]>
06/10/2004 07:08 AM
Please respond to OJB Users List
To: OJB Users List <[EMAIL PROTECTED]>
cc:
Subject: Re: Not responding : peculiar problem on Solaris
Hi Zabi,
hard to find out what's going wrong. Does it seems to be a deadlock? Do
you change the pool behaviour (e.g. exhausted pool wait for returned
connections - default behaviour is throw an exception)
> On every request, the persistence broker creates many database
> connections are created and they all remain INACTIVE except only one
which
> serves the request.
This sounds strange. Do you immediately close each PB instance after use?
regards,
Armin
Zabiullah SS wrote:
> Hi all,
>
> Our web application runs under tomcat4.1.27, using OJB 1.0 and JDK
1.4.2,
> the system connects to Oracle database (8.1.7) to read records, Each
> request (say a study download) submit spawns a thread and reads data
from
> database to write into a file. Each Query will fetch 20000 records and
> each request (one study) submit will have 80 queries (but run
sequentially
> ).
>
> If two or more web users try to perform the same functionality the
system
> hangs and never returns (until i kill the process). I use connection and
> broker pooling.
>
> 1) Each thread uses a persistence broker and it is closed after each
> query.
> 2) Behaviour is observed only on solaris (SMP - 20 cpu/20GB RAM). On a
> small machine Linux (1 CPU/1 GB RAM) it works fine though slow.
>
> Also on a side note
>
> On every request, the persistence broker creates many database
> connections are created and they all remain INACTIVE except only one
which
> serves the request.
>
> Iam unable to debug, i tried looking (catalina) logs it doesn't provide
> much information. How do i debug this problem ?.
>
> Please Help. Appreciate it.
>
> Rgds
> Zabi.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
