[jboss-dev] Howto debug jndi lookup issues?

Andrew Lee Rubinger andrew.rubinger at redhat.com
Mon Dec 7 11:36:02 EST 2009

My money here is that you are missing the ObjectFactory from your client 
ClassPath: the symptom of this is a CCE from javax.naming.Reference.


On 12/07/2009 11:29 AM, Thomas Diesler wrote:
> Folks,
> java.lang.ClassCastException: javax.naming.Reference cannot be cast to
> org.jboss.test.osgi.jbosgi58.ejb.StatelessBean
>       at
> org.jboss.test.osgi.jbosgi58.OSGI58TestCase.testEJB(OSGI58TestCase.java:54)
> a JNDI client lookup may fail for various reasons . AFAIK, the above CCE
> happens because there is some calss missing on the client classpath.
> JNDI gives up internally and simply returns the reference.
> To solve the problem I could do
> <dependency>
> <groupId>org.jboss.jbossas</groupId>
> <artifactId>jboss-as-client</artifactId>
> <version>6.0.0.M1</version>
> <type>pom</type>
> </dependency>
> but this gives me an insanely big dependency tree
> (http://pastebin.com/m3776fc85). I'd much rather find out, what exactly
> is missing and use a client that contains just that.
> Is there a way to debug these kind of JNDI client issues?
> cheers
> -thomas

Andrew Lee Rubinger
Sr. Software Engineer
JBoss by Red Hat

More information about the jboss-development mailing list