Sunday, March 25, 2001 04:51 AM
Generally, with J2EE unsaved changes are discarted, to enforce transactionality.
If the ejbSvr crashes first, the connection to the db is lost, then the db rolls back the active transactions and the server becomes not reachable, the client should get a RemoteException.
If is the dbSvr to crash first, all the changes are lost and all uncommitted modification too (but this depends from the databases behaviour). Then the AppSvr gets a SQLException and wraps it in a RemoteException to the client.
I assume that uncommitted data are stored in some temporary structure in the db. A bad database could for example corrupt touched data...
In both cases, uncommitted modifications must rationally roll back, even if dbSvr and ejbSvr crash together.
The existence of more or less log files depends on the Application Server that you are using. On WebLogic there's a log to check the jdbc activity too.