Bruno CROS wrote:
Hi,
Well, i just want to mesure the time a sql statement takes to be post (sql
commit too). I looked a bit in broker.accesslayer package and in
StatementForClassImpl.java. Is it the right place to do this ?
I would recommend to have a look in class JdbcAccessImpl to clock q
Hi Bruno,
Bruno CROS wrote:
Hi,
Ye, we get rid of those dead locks.
Congratulation!
Actually, OJB does not cause anything to have Oracle dead locks!!
Phew!
Many
applications can have dead locks without any lines of bad (OJB) code.
Bad locks are generated when oracle can 't do simp
Hi,
mananthakris wrote:
We are planning to upgrade to the latest ojb. Will let you know how it is
doing after that.
Attached is the jdbc descriptor we are using till now
The jdbc-connection-descriptor seems ok.
Also we are facing the problem of running out of connections in the pool
sometim
Hi Bernd,
Längerich wrote:
"Ingrid" Längerich writes:
The code I tried is like this:
OK, I found out that
Iterator it = masterbroker.getReportQueryIteratorByQuery(masterquery);
Collection taids = new Vector();
while (it.hasNext()) {
Object obj = ((Object[])it.nex
Hi,
mananthakris wrote:
Turned out that at one place the new jar wasn't copied over. The error is
gone now when that was corrected.
mananthakris wrote:
Hi,
Migrating to ojb 1.0.4 from ojb.1.0.rc4 gives error while trying to get
Implementation class for odmg-api.
Does ODMGFactory no longer exi
Turned out that at one place the new jar wasn't copied over. The error is
gone now when that was corrected.
mananthakris wrote:
>
> Hi,
> Migrating to ojb 1.0.4 from ojb.1.0.rc4 gives error while trying to get
> Implementation class for odmg-api.
>
> Does ODMGFactory no longer exist? We use to
Hi,
Well, i just want to mesure the time a sql statement takes to be post (sql
commit too). I looked a bit in broker.accesslayer package and in
StatementForClassImpl.java. Is it the right place to do this ?
May be someone wrote an implementation?
Working with 1.0.4
Thanks for advices.
Re
Hi,
Ye, we get rid of those dead locks.
Actually, OJB does not cause anything to have Oracle dead locks!! Many
applications can have dead locks without any lines of bad (OJB) code.
Bad locks are generated when oracle can 't do simple operations as UPDATE OR
DELETE, when time to verify forei