Is there a known problem with the way JRun handles rollbacks in multibean
transactions?
I've been reading some recent posts on the Allaire message boards and am
having the same problem I see there.
One session bean calls two entity beans. All are set to required in
ejb.xml. When an error occurs in the second entity bean, the first entity
bean has already had its ejbStore called and if we check the database after
the error, the record has persisted. If we use the sun jdbc-odbc driver (to
an MS SQL 7 db), then the db connection hangs (never writes but we lose the
connection). If we use the type 4 driver supplied with the enterprise
server, the transaction goes through as mentioned above.
We've tried setting the two entity beans to mandatory and the session bean
to NotSupported and indeed get a transaction error indicating that we needed
to already be in a transaction.
Here's some of the specifics:
Win2k
MS SQLServer 7 DB
JRun 3.0 sp2
Type 4 JDBC driver for ms sqlserver
Thanks for any help. If anyone has actually achieved the above scenario
it'd at least be nice to know that.
Terry D
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
