Hi Pier,

----- Original Message -----
From: "Pierfranco Lai" <[EMAIL PROTECTED]>
To: "'OJB Users List'" <[EMAIL PROTECTED]>
Sent: Wednesday, May 28, 2003 6:02 PM
Subject: OJB System Test ISSUES


>
> I've developed a application with Struts, OJB rc3, Oracle App Serv
OC4J 903
> and Oracle 8 DB.
>
> Now I'm stress-testing the application with JMeter: 5 concurrent users
with
> 3 different http request.
>
> Some questions:
>
> 1)
> It seems that the begin, commit and abort transaction funct have
effect to
> all the connections of the pool of the PB.
How does it effect all connections?

> That's correct?
I don't hope so ;-)

> I've followed a previous suggestion (open a PB before the
> begin-tras and close it after the commit) but I does not work
correcly.

OJB was shipped with a simple multithreaded test. This test
does not point out any problems.
call 'bin\build.bat perf-test'

Do you use OJB within EJB's?

>
> 2)
> If a connection-pool is full, how can I prevent any operation before?
I
> mean: can I check if the broker can perform a query or an insert
before to
> do that?
(Don't know if I understand your question)
No, but you can setup different scenarios when pool is
exhausted:
- throw exception
- wait for next returned connection (recommended
only for multithreaded environments)
- grow

regards,
Armin

>
> Thanks
> Pier
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to