This week's giveaway is in the EJB and other Java EE Technologies forum. We're giving away four copies of EJB 3 in Action and have Debu Panda, Reza Rahman, Ryan Cuprak, and Michael Remijan on-line! See this thread for details.
Whenever any unchecked runtime exeption (For Ex Nullpointer) is thrown from beyond the EJB layer in our application, it is getting converted to Corba Unknown Exception (org.omg.CORBA.portable.UnknownException) and shown to the user on the error screen.
This is misleading as the actual error gets lost. This happens in WSAD as well as WAS server (Version 5.1) where the application is deployed.
Early investigation shows that there is some problem with the stubs and ties being generated by websphere.
Has anybody faced similar problem using Websphere 5.1 and is there a fix or workaround.
Thanks for your response. The exceptions I am talking about would come under the 18.2.2 System exceptions section of the specs.
What is happening is, if a NullPointer comes for some unknown reason, it is to be thrown as is .. it gets propagated across the tiers of the application till it reaches EJB stubs and skeleton, which are supposed to convert it to remote exception.
"The Container catches a non-application exception; logs it (which can result in alerting the SystemAdministrator); and, unless the bean is a message-driven bean, throws the java.rmi.RemoteException(or subclass thereof) to the client if the client is a remote client, or throws the javax.ejb.EJBException (or subclass thereof) to the client if the client is a local client. TheBean Provider can rely on the Container to perform the following tasks when catching a non-applicationexception: The transaction in which the bean method participated will be rolled back. No other method will be invoked on an instance that threw a non-application exception.
But sth goes wrong, and all we get is Corba Unknown Exception (org.omg.CORBA.portable.UnknownException)