Hi again,
hmm, looks fine for me.
Could you post your OJB.properties file please.
> > > > > the ConnectionFactoryClass to ConnectionFactoryNotPooledImpl
> > > > > instead of
> > > > > the ConnectionFactoryManagedImpl (to make sure connections get
what I don't understand is that these implementation classes do
not exist in 0.9.7?
> We do not use a pooling ConnectionFactory, and already tried the
> ConnectionFactoryNotPooledImpl as mentoined earlier (see below):
ok, how do you lookup connections? Using DataSource from your appServer
or using 'direct' connections from the DriverManager?
regards,
Armin
----- Original Message -----
From: "J Pielage" <[EMAIL PROTECTED]>
To: "OJB Users List" <[EMAIL PROTECTED]>
Sent: Wednesday, June 18, 2003 1:01 PM
Subject: Re: Troubles with Websphere / OJB / Oracle application
> Hi Armin,
>
>
> The code which get's called in our stress test looks like this:
>
> public static Medewerker getMedewerkerByLogin(String login) {
> Criteria crit = new Criteria();
> crit.addEqualTo("login", login);
> return (Medewerker) OJBHelper.getObjectByQuery(Medewerker.class,
> crit);
> }
>
> This uses the getObjectByQuery method in an class OJBHelper which
looks
> like this:
>
> /**
> * Roept de getObjectByQuery methode van de PersistenceBroker aan
> * @param ojbClass OJB class
> * @param criteria Query criteria
> * @return Object
> */
> public static Object getObjectByQuery(Class ojbClass, Criteria
> criteria) {
> PersistenceBroker broker = null;
> Object retval = null;
>
> try {
> Query q = QueryFactory.newQuery(ojbClass, criteria);
>
> // run query
> broker = PersistenceBrokerFactory.defaultPersistenceBroker();
> retval = broker.getObjectByQuery(q);
>
> } finally {
> if (broker != null) {
> broker.close();
> }
> }
>
> return retval;
> }
>
> We do not use a pooling ConnectionFactory, and already tried the
> ConnectionFactoryNotPooledImpl as mentoined earlier (see below):
>
> > > > > We tried several settings in the OJB.properties file,
> > > > > especially setting
> > > > > the ConnectionFactoryClass to ConnectionFactoryNotPooledImpl
> > > > > instead of
> > > > > the ConnectionFactoryManagedImpl (to make sure connections get
> > closed,
> > > > > that is returned to the data source connection pool) but that
> > didn't
> > > > > help.
>
> Thanks, Jeroen
>
>
>
>
> Armin Waibel wrote:
> >
> > Hi,
> >
> > could you post the code for the stress test or
> > some pseudo code to see how you get broker
> > instances, ...?
> >
> > > We use an Oracle (9.0.1) connection pooled datasource from OJB
> >
> > If using DataSource from the appServer don't use a pooling
> > ConnectionFactory in OJB too. In current version OJB never
> > pools connections obtained via DataSource, in 0.9.7 I
> > think you should use ConnectionFactoryNotPooledImpl.
> >
> > Do you have tried to increase the max connections
> > limit (e.g. double the number of connections the test pass
> > with jdbc)?
> >
> > regards,
> > Armin
> >
> > ----- Original Message -----
> > From: "J Pielage" <[EMAIL PROTECTED]>
> > To: "OJB Users List" <[EMAIL PROTECTED]>
> > Sent: Wednesday, June 18, 2003 11:43 AM
> > Subject: Re: Troubles with Websphere / OJB / Oracle application
> >
> > > Hi Thomas,
> > >
> > > Thanks for the quick response, really appreciate it!
> > >
> > > We are currently re-checking if all the brokers get closed, we
> > normally
> > > do that in finally blocks, well, everything seems to be allright
so
> > far.
> > >
> > > We singled out a single simple query functionality in our app for
the
> > > stress testing, and I already verified that any brokers that are
used
> > in
> > > this case are properly closed. So that doesn't seem to be the
> > problem...
> > >
> > > BTW, forgot to mention, we are using the odmg api for inserts,
> > deletes,
> > > and updates, but using the PersistenceBroker for running queries.
(We
> > > read-lock any objects that get returned by the brokers inside odmg
> > > transactions.)
> > >
> > >
> > > Jeroen
> > >
> > >
> > >
> > > Mahler Thomas wrote:
> > > >
> > > > Hi jeroen,
> > > >
> > > > are you sure you properly close all broker instances after
usage?
> > > > If you don't close broker instances after usage they are not
made
> > available
> > > > to the pool and thus a shortage of available db connections is
> > likely to
> > > > happen!
> > > >
> > > > cheers,
> > > > Thomas
> > > >
> > > > > -----Original Message-----
> > > > > From: J Pielage [mailto:[EMAIL PROTECTED]
> > > > > Sent: Wednesday, June 18, 2003 10:28 AM
> > > > > To: OJB Users List
> > > > > Subject: Troubles with Websphere / OJB / Oracle application
> > > > >
> > > > >
> > > > > Hi all,
> > > > >
> > > > > We are stress testing an J2EE application on Websphere App
> > > > > Server 4.0.3
> > > > > and running into problems. We use OJB v 0.9.7 for the data
layer,
> > > > > instead of entity EJB's. The OJB functionality is called from
> > > > > a layer of
> > > > > stateless session EJB's.
> > > > >
> > > > > The problem is that, when running requests from different
> > > > > clients at the
> > > > > same time, numerous requests to the database time out, likely
> > > > > because of
> > > > > problems with getting a database connection.
> > > > > We use an Oracle (9.0.1) connection pooled datasource from
OJB.
> > When
> > > > > stress testing normal JDBC calls (not involving OJB) using the
> > same
> > > > > datasource, we experience no problems.
> > > > >
> > > > > So the problem is maybe in the configuration of the OJB layer.
> > > > > We tried several settings in the OJB.properties file,
> > > > > especially setting
> > > > > the ConnectionFactoryClass to ConnectionFactoryNotPooledImpl
> > > > > instead of
> > > > > the ConnectionFactoryManagedImpl (to make sure connections get
> > closed,
> > > > > that is returned to the data source connection pool) but that
> > didn't
> > > > > help.
> > > > >
> > > > > We are currently running late with our project and running
> > > > > out of ideas,
> > > > > so if any of you could give us timely advice on this one, it
would
> > be
> > > > > deeply appreciated. Especially, if you have experiences with a
> > > > > production system with a similar architecture, it would be
> > > > > very helpful
> > > > > to know how you did configure OJB.
> > > > >
> > > > > Thanks!
> > > > >
> > > > > Jeroen Pielage
> > > > > TNO
> > > > > the Netherlands
> > > > >
> > > >
> >
> ---------------------------------------------------------------------
> > > > > 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]
> > >
> >
> ---------------------------------------------------------------------
> > > 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]
>
> ---------------------------------------------------------------------
> 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]
