I suspect you are using a version that only warns you the first time it
notices.
I'd advise you to use the same datasource for all ejbs unless you are
really accessing different databases or one datasource is used only for
"read-only". Otherwise you can possibly have work in one datasource
commit
DS> Was this checked before or after my massive check in
DS> yesterday? I know you wrote the 29th, but I want to
DS> be sure as I messed with most of the interceptors.
10/29/2002 around 2pm EST.
Michael
---
This sf.net email is sponsored by:
DJ> This is pretty strange. You should be getting this
DJ> consistently (if you are really using 2 resource managers
DJ> in one transaction, one of them being only local tx
DJ> capable) or never (if there is only one, for instance your
DJ> only datasource).
I didn't think to mention my datasourc
I've been wrong before, but this should have nothing to do with the
interceptors. It should depend only on the tm and the XAResource
isSameRM() implementation.
david jencks
On 2002.10.31 17:46:51 -0500 Dain Sundstrom wrote:
> Was this checked before or after my massive check in yesterday? I kno
This is pretty strange. You should be getting this consistently (if you
are really using 2 resource managers in one transaction, one of them being
only local tx capable) or never (if there is only one, for instance your
only datasource).
If you can pin down anything else about how to make this ha
Was this checked before or after my massive check in yesterday? I know
you wrote the 29th, but I want to be sure as I messed with most of the
interceptors.
-dain
David Jencks wrote:
This is pretty strange. You should be getting this consistently (if you
are really using 2 resource managers in
