| [glassfish-dev] What are the possible causes of remote JNDI lookup failures like https://github.com/eclipse-ee4j/glassfish/issues/25190? |
Hi,
Could the jndi lookup failure in
https://github.com/eclipse-ee4j/glassfish/issues/25190 be caused
by deployment descriptors not being correct? Could it also be
caused by classnotfound exceptions? Note that the included JNDI
lookup exception doesn't include the cause (the cause should at
least be logged I think if there is an exception caught but
ignored).
From the exception call stack included:
"
Suppressed: javax.naming.NamingException: Exception resolving Ejb for 'Remote ejb-ref name=ejb/Stateless3VehicleBean,Remote 3.x interface =com.sun.ts.tests.common.vehicle.stateless3.Stateless3VehicleIF,ejb-link=Stateless3VehicleBean,lookup=,mappedName=,jndi-name=,refType=Session' . Actual (possibly internal) Remote JNDI name used for lookup is '#com.sun.ts.tests.common.vehicle.stateless3.Stateless3VehicleIF' [Root exception is javax.naming.NamingException: Lookup failed for #com.sun.ts.tests.common.vehicle.stateless3.Stateless3VehicleIF in SerialContext[myEnv={java.naming.factory.initial=com.sun.enterprise.naming.impl.SerialInitContextFactory, java.naming.factory.url.pkgs=com.sun.enterprise.naming, java.naming.factory.state=com.sun.corba.ee.impl.presentation.rmi.JNDIStateFactoryImpl}] [Root exception is javax.naming.NameNotFoundException: #com.sun.ts.tests.common.vehicle.stateless3.Stateless3VehicleIF not found]]
"
Other thoughts on the cause?
Scott