there any transactional log file used? (EJB)
Answer Actually,
if your EJB server crashes, you will not even be able to make
a connection to the server to perform a bean lookup, as the server will no longer
be listening on the port for incoming JNDI lookup requests.
You will lose any
data that wasn't committed prior to the crash. This is where you should start
looking into clustering your EJB server.
Another Answer
Hi, Any unsaved and uncommitted changes are lost the moment your EJB Server
crashes. If your database also crashes, then all the
saved changes are also lost
unless you have some backup or some recovery mechanism to retrieve the data.
So consider database replication and EJB Clustering for such scenarios, though
the occurrence of such a thing is very very rare. All database have the concept of
log files(for example oracle have redo log files concept).
So if data bases crashes
then on starting up they fill look up the log files to perform all pending jobs. But
is EJB crashes, It depend upon the container how frequently it passivates or how
frequently it refreshes the data with Database.
Do'stlaringiz bilan baham: