In case there is a database failure in CMP entity bean, or the database is down for sometime and a transaction is made by a user, then it should log that the database was down for some �X� reason in a flat file. But in CMP there is a problem that it always abstracts the Database failure issues. Suppose a transaction is made, then the session bean tries to call the finder methods or create method on entity bean � Which simply in CMP throw a FinderException or CreateException and not the SQLException, (But its possible in BMP where we manually establish the database connection by writing the JDBC code) bcos SQL related issues are handled internally by the server� I would appreciate if anyone could let me know the possible errors in case of a database connectivity problem. Also, how should one catch those errors.
Joined: Aug 05, 2005
Sounds like this is something that should be found in the server/container documentation.