Ok, thanks. Thing is, while I was waiting an answer from here, I tried
the code on our Test Envirnoment AS. It is the next version, Sun Java
AS 9, which uses the Java EE 5 platform. Funny thing is ... it worked.
Just as-is, no changes, no NOTHING. Just deployed and tested, and all
the "lock-when-loaded" consistencies worked. (Even tested the
consistency doing a LOCK TABLE SHARE ROW EXCLUSIVE to see if the EJB
transaction would lock until available.)
So I assume it must be some weird bug, specific to the 8.1 AS version.
Should note that the JDBC pool is defined exactly the same in both
Only thing I haven't solved by now is that the CMP management for the
Sun AS is kind of dumb when using tables in schemas that are not in the
current connection's search_path. But that is another story ...
Oliver Jowett wrote:
> DanixDefcon5 wrote:
> > It says that the DataStore doesn't support locking for update at row
> > level.
> AFAIK the driver returns true from
> DatabaseMetaData.supportsSelectForUpdate(). I don't know what additional
> things the Sun implementation requires to support its "lock-when-loaded"
> mode. You will have to ask Sun.
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster
In response to
pgsql-jdbc by date
|Next:||From: Michael Guyver||Date: 2006-06-23 08:22:34|
|Subject: Re: Binary tx format for an array?|
|Previous:||From: Sebastiaan van Erk||Date: 2006-06-22 20:14:12|
|Subject: Re: Limit vs setMaxRows issue|