Is there a way to enable the full stack trace of an exception generated by an ejb to
the client? Here is an example of a FinderException on an entity bean that does
not show the execution path to the entity bean finder method implementation. Is
there a way to enable the full exception stack trace on the client side?
The finder exception trace I see on the client side is:
javax.ejb.FinderException: javax.naming.NameNotFoundException:
com.dscape.projects.documents.ejb.ProjectDirContext not bound
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:245)
at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:220)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:122)
at org.jboss.ejb.plugins.jrmp.server.JRMPContainerInvoker_Stub.invokeHome(Unknown
Source)
at org.jboss.ejb.plugins.jrmp.interfaces.HomeProxy.invoke(HomeProxy.java:221)
at $Proxy0.findByProjectName(Unknown Source)
at
com.dscape.test.projects.tstProjectDirectoryEJB.run(tstProjectDirectoryEJB.java:120)
at java.lang.Thread.run(Thread.java:484)
while the server side trace is:
javax.naming.NameNotFoundException:
com.dscape.projects.documents.ejb.ProjectDirContext not bound
at org.jnp.server.NamingServer.getBinding(NamingServer.java:474)
at org.jnp.server.NamingServer.getBinding(NamingServer.java:482)
at org.jnp.server.NamingServer.getObject(NamingServer.java:488)
at org.jnp.server.NamingServer.lookup(NamingServer.java:254)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:295)
at javax.naming.InitialContext.lookup(InitialContext.java:354)
at
com.dscape.projects.documents.ejb.ProjectDirectoryBean.findDirContext(ProjectDirectoryBean.java:391)
at
com.dscape.projects.documents.ejb.ProjectDirectoryBean.ejbFindByPrimaryKey(ProjectDirectoryBean.java:301)
at
com.dscape.projects.documents.ejb.ProjectDirectoryBean.ejbFindByProjectName(ProjectDirectoryBean.java:325)
at java.lang.reflect.Method.invoke(Native Method)
at
org.jboss.ejb.plugins.BMPPersistenceManager.callFinderMethod(BMPPersistenceManager.java:410)
at
org.jboss.ejb.plugins.BMPPersistenceManager.findEntity(BMPPersistenceManager.java:195)
at org.jboss.ejb.EntityContainer.find(EntityContainer.java:419)
at java.lang.reflect.Method.invoke(Native Method)
at
org.jboss.ejb.EntityContainer$ContainerInterceptor.invokeHome(EntityContainer.java:639)
at
org.jboss.ejb.plugins.EntitySynchronizationInterceptor.invokeHome(EntitySynchronizationInterceptor.java:160)
at
org.jboss.ejb.plugins.EntityInstanceInterceptor.invokeHome(EntityInstanceInterceptor.java:86)
at org.jboss.ejb.plugins.TxInterceptorCMT.invokeNext(TxInterceptorCMT.java:135)
at
org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:343)
at org.jboss.ejb.plugins.TxInterceptorCMT.invokeHome(TxInterceptorCMT.java:86)
at org.jboss.ejb.plugins.SecurityInterceptor.invokeHome(SecurityInterceptor.java:126)
at org.jboss.ejb.plugins.LogInterceptor.invokeHome(LogInterceptor.java:106)
at org.jboss.ejb.EntityContainer.invokeHome(EntityContainer.java:316)
at
org.jboss.ejb.plugins.jrmp.server.JRMPContainerInvoker.invokeHome(JRMPContainerInvoker.java:143)
at java.lang.reflect.Method.invoke(Native Method)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:241)
at sun.rmi.transport.Transport$1.run(Transport.java:142)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:139)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:443)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:643)
at java.lang.Thread.run(Thread.java:484)
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
