Losing SFSB after exception thrown - how can I avoid this?

Question

I am using Sun Java System Application Server 9.0
I am using a State Full Session Bean (SFSB) via a Remote Business Interface. In this SFSB I do a �try/catch� to perform an update on an entity with child entities. My catches look for an OptimisticLockException and any other exception. When Oracle throws an OptimisticLockException the catch does not recognize this and catches the any other exception. In both case another exception is thrown, see below for the code. But when this happens the SFSB is destroyed and no longer available causing the client to fail when it tries to use one of the SFSB�s business interface methods.
Can anyone please tell me how I avoid losing the SFSB or how to reload it automatically and quickly?
A plus would be can you tell me why the Oracle exception is not caught by the correct catch? The full exception is oracle.toplink.essentials.exceptions.OptimisticLockException and I have no idea whether is a subclass of another exception type.
} catch (OptimisticLockException ole) {
     Debug.debugPrintln("OrderControllerBean.updateOrder() - optimistic lock exception: " + ole.getMessage());
     throw new EntityAlreadyUpdatedDeleted("Order number: "
                    + oldOrderHeader.getOrderNumber()
                    + "cannot be updated because it has changed or been deleted since you last looked at it");
} catch (Exception ex) {
     Debug.debugPrintln("OrderControllerBean.updateOrder() - other exception persist failed orderNumber: "
                    + oldOrderHeader.getOrderNumber()
                    + " exception: " + ex.getMessage());
     throw new EJBException(ex);
Many thanx����.
Edited by: jdraven on Mar 27, 2008 11:06 PM

Answer 1

No worries!
Thank you for sharing the solution to your problem with the community!
Kameralina
Ask NI (ni.com/ask)
Search The KnowledgeBase
NI Developer Zone
Measure It. Fix It. ni.com/greenengineering/
NI Vision ni.com/vision/