Hi Aaron,
Friday, September 29, 2000, 9:27:42 PM, Aaron Mulder wrote:
AM> On Fri, 29 Sep 2000, Oleg Nitz wrote:
>> AM> I think the garbage collection setting in the pool is the best
>> AM> bet,
>> Would it work for database vendor XADataSource implementations?
>> I guess, no.
AM> Well, it would return the vendor's XAConnection to the pool. It
AM> cannot identify any Connections outstanding from the XAConnection and
AM> close them, but at least the XAConnection will be reused.
That's great, really.
Can anyone consult me on the following question.
Castor JDO in EJB environment behaves as follows (Assaf Arkin's
authority in Transation Manager questions makes me think that it is
a valid behavior):
1) registers as Synchronization with TransactionManager;
2) gets Connections from DataSource during the transaction as needed
and performs some database operations;
3) on beforeCompletion performs all other database operations;
4) on afterCompletion if STATUS_COMMITTED, closes the Connections,
otherwise does nothing (if I understand correctly, the Connections
should be committed or rolled back before afterCompletion by the
TransactionManager. But who closes them in case of rollback?).
I am not sure that it works now with jBoss+Minerva, before last
Aaron's modifications it didn't.
I hope now it does (will check tomorrow).
Anyway, comments are appreciated.
But I foresee the next problem. For HIGH/LOW key generator I would
like to get the additional Connection, to write new value to the
database table holding occupied key values and to commit
this modification *immediately*, whether the main transaction will
commit or rollback. Is it possible with EJB CMT?
Can I call conn.commit() inside it so that it will be actually
performed on the database even in the case of the rollback of
the method's transaction?
Note, that the action would be performed not by the bean, but by
the resource manager.
Sorry, if the question is stupid, but you, EJB gurus should get
used to such questions a while ago ;-)
Regards,
Oleg
