Lennart,
I think I found out the reason being that:
After the first time I run the client to update the record, and before I run
it the second time, I did open up the table manually (through the DBMS) to
delete the record. Somehow if I delete the record manually, the client will
throw the error if it tries to update the same record the second time, which
is now, non-existent. Seems like jBoss is still keeping reference or cache
to that record. I'm still new to this, and don't really know what's in jBoss
design, so this is only my guess. Anyone can enlighten me on this ? Thanks!
ChetHong
> -----Original Message-----
> From: Lennart Petersson [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, June 19, 2001 6:59 PM
> To: [EMAIL PROTECTED]
> Subject: SV: [JBoss-user] Weird problem with transaction -
> more info for
> questions
>
>
> Turn on sql debug. It may be done globally in
> conf/standardjaws.xml (look for debug tag in the beginning of
> the file). Run your application and then look for messages in
> log/server.log. Mail again if that does not bring up any ideas.
>
> /Lennart
>
>
>
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-user
>
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user