How to make EJB exception stack traces show line numbers?

[Yuriy Zilbergleyt]

Hi,

I'm getting a RemoteException from a call to an EJB I've deployed on a weblogic server. It's wrapping a NullPointerException, but the stack trace only tells me (UnknownSource) instead of the line number for the bean method where the exception originates. All the weblogic class methods in the stack traces have line numbers. Is there anything I can do to show me the line number of the bean code that throws the exception?

Exception in thread "main" java.rmi.ServerException: RemoteException occurred in server thread; nested exception is: 
java.rmi.RemoteException: EJB Exception: ; nested exception is: 
java.lang.NullPointerException
at com.sun.corba.se.impl.javax.rmi.CORBA.Util.mapSystemException(Unknown Source)
at javax.rmi.CORBA.Util.mapSystemException(Unknown Source)
at com.mgb.vem.beans._LucyReceiverRemote_Stub.receiveMessages(Unknown Source)
at test.LucyReceiverBeanTest.main(LucyReceiverBeanTest.java:30)
Caused by: java.rmi.RemoteException: EJB Exception: ; nested exception is: 
java.lang.NullPointerException
at weblogic.ejb20.internal.EJBRuntimeUtils.throwRemoteException(EJBRuntimeUtils.java:95)
at weblogic.ejb20.internal.BaseEJBObject.handleSystemException(BaseEJBObject.java:713)
at weblogic.ejb20.internal.BaseEJBObject.handleSystemException(BaseEJBObject.java:681)
at weblogic.ejb20.internal.BaseEJBObject.postInvoke1(BaseEJBObject.java:447)
at weblogic.ejb20.internal.BaseEJBObject.postInvokeTxRetry(BaseEJBObject.java:374)
at com.mgb.vem.beans.LucyReceiverBean_rhqidg_EOImpl.receiveMessages(LucyReceiverBean_rhqidg_EOImpl.java:74)
at com.mgb.vem.beans.LucyReceiverBean_rhqidg_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.activation.ActivatableServerRef.invoke(ActivatableServerRef.java:85)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:393)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:389)
at weblogic.rmi.internal.BasicServerRef.access$300(BasicServerRef.java:56)
at weblogic.rmi.internal.BasicServerRef$BasicExecuteRequest.run(BasicServerRef.java:903)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
Caused by: java.lang.NullPointerException
at com.mgb.vem.beans.LucyReceiverBean.receiveMessages(Unknown Source)
at com.mgb.vem.beans.LucyReceiverBean_rhqidg_EOImpl.receiveMessages(LucyReceiverBean_rhqidg_EOImpl.java:60)
... 10 more

[Eduardo Dela Rosa]

Hi,

Unknown Source appears in the stack trace of exceptions when the actual
Java code is compiled using the -g:none flag, as in

  javac -g:none Source.java  

By default, debugging info is on unless you override that setting.

If you compile your Java source codes without that flag, you'd see the
line number corresponding to the code where the exception was thrown.

In other words, download the Sun JDK API source codes and recompile them
the normal way. You shouldn't have problem about the licensing since you
are not modifying anything in any of the codes.


HTH.

[Yuriy Zilbergleyt]

Thank you for the reply, Eduardo!

The "Unknown Source" actually shows up for the bean class that I wrote myself. I compiled it using ANT in the following way:

<javac source="1.4" srcdir="${src}" destdir="${build}" debug="true" debuglevel="lines">
<classpath refid="classpath.all"/>
</javac>

How could the way that Sun's API are compiled affect the way that my own classes show up in the stack trace?

Thank you,
Yuriy Zilbergleyt