|
Hi Bryan,
This problem of yours looks very much like a
problem we once had with BAS app-server from Borland. The problem was that BAS
expected "exclusive" rights to its underlying datasource, but didn't have it.
(other apps. used the DB as well). Changing comiit option from
"exclusive" to "non-exclusive" solved our problem. I think you can
do this in JBoss by setting commit-option !=A in jboss.xml.
Regards
-Kris
----- Original Message -----
Sent: Saturday, January 19, 2002 2:20
AM
Subject: [JBoss-user] Someone PLEASE
advise re: Client UserTransactions never commiting
I am hoping someone can help me solve a problem I'm having with
JBoss
2.4.4 (using RedHat Linux 7.1 and PostgreSQL 7.0.2).
My
client application manipulates several entity beans. I know that a
better
design would be to use a session facade, but that's not an option
in the
short term.
In any case -- I've introduced the use of UserTransaction
from the
client. I obtain a UserTransaction and call "begin". Then I
manipulate
my entity beans. Finally, I call "UserTransaction.commit()".
My changes are being written to the database, but, they are not being
commited. I know this because when my application tries to read the
values back, the new values are shown. But another application,
connecting directly to PostgreSQL, shows the old values. Lastly, when I
restart JBoss or reload the EAR file, all the old values come back.
My CMP beans are marked as "Requires" a transaction.
Can
anyone please help me deduce what's going wrong, and why my commit()
calls
don't seem to be doing anything?
Thank you,
Bryan
|
