04:03:33,724 INFO [STDOUT] at org.jboss.mx.server.Invocation.invoke(Invocation.java:72) | 04:03:33,724 INFO [STDOUT] at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249) | 04:03:33,724 INFO [STDOUT] at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644) | 04:03:33,734 INFO [STDOUT] at org.jboss.invocation.local.LocalInvoker$MBeanServerAction.invoke(LocalInvoker.java:15 | 5) | 04:03:33,734 INFO [STDOUT] at org.jboss.invocation.local.LocalInvoker.invoke(LocalInvoker.java:104) | 04:03:33,734 INFO [STDOUT] at org.jboss.invocation.InvokerInterceptor.invokeLocal(InvokerInterceptor.java:179) | 04:03:33,734 INFO [STDOUT] at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:165)
Looking at the above lines in stack trace, tells me that there is local invocation of the bean being tried. The exception is right , check your deployment descriptor, especially jboss.xml for the jndi you are supposed to use for the remote lookup. HTH, Vikram. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3882676#3882676 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3882676 ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
