-
Bug
-
Resolution: Done
-
Blocker
-
13.0.0.Beta1
-
None
Upon attempting to lookup a remote EJB using jboss-ejb-client 2 with remote-naming context, the following exception is produced clientside:
Exception in thread "main" org.jboss.naming.remote.protocol.NamingIOException: Failed to lookup [Root exception is java.io.IOException: java.lang.ClassNotFoundException: javax.naming.CompositeName from [Module "org.wildfly.extension.io" version 5.0.0.Beta3 from local module loader @490caf5f (finder: local module finder @6337c201 (roots: /home/mjurc/testing/wildfly/build/target/wildfly-13.0.0.Alpha1-SNAPSHOT/modules,/home/mjurc/testing/wildfly/build/target/wildfly-13.0.0.Alpha1-SNAPSHOT/modules/system/layers/base))]] at org.jboss.naming.remote.client.ClientUtil.namingException(ClientUtil.java:49) at org.jboss.naming.remote.protocol.v1.Protocol$1.execute(Protocol.java:104) at org.jboss.naming.remote.protocol.v1.RemoteNamingStoreV1.lookup(RemoteNamingStoreV1.java:95) at org.jboss.naming.remote.client.HaRemoteNamingStore$1.operation(HaRemoteNamingStore.java:276) at org.jboss.naming.remote.client.HaRemoteNamingStore.namingOperation(HaRemoteNamingStore.java:137) at org.jboss.naming.remote.client.HaRemoteNamingStore.lookup(HaRemoteNamingStore.java:272) at org.jboss.naming.remote.client.RemoteContext.lookupInternal(RemoteContext.java:104) at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:93) at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:146) at javax.naming.InitialContext.lookup(InitialContext.java:417) at client.Client.main(Client.java:22) Caused by: java.io.IOException: java.lang.ClassNotFoundException: javax.naming.CompositeName from [Module "org.wildfly.extension.io" version 5.0.0.Beta3 from local module loader @490caf5f (finder: local module finder @6337c201 (roots: /home/mjurc/testing/wildfly/build/target/wildfly-13.0.0.Alpha1-SNAPSHOT/modules,/home/mjurc/testing/wildfly/build/target/wildfly-13.0.0.Alpha1-SNAPSHOT/modules/system/layers/base))] at org.wildfly.naming.client.remote.RemoteServerTransport.handleLookup(RemoteServerTransport.java:177) at org.wildfly.naming.client.remote.RemoteServerTransport$1.handleMessage(RemoteServerTransport.java:106) at org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$handleMessageData$3(RemoteConnectionChannel.java:430) at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:926) at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) at java.lang.Thread.run(Thread.java:844) Caused by: java.lang.ClassNotFoundException: javax.naming.CompositeName from [Module "org.wildfly.extension.io" version 5.0.0.Beta3 from local module loader @490caf5f (finder: local module finder @6337c201 (roots: /home/mjurc/testing/wildfly/build/target/wildfly-13.0.0.Alpha1-SNAPSHOT/modules,/home/mjurc/testing/wildfly/build/target/wildfly-13.0.0.Alpha1-SNAPSHOT/modules/system/layers/base))] at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:255) at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:410) at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:374) at org.jboss.marshalling.AbstractClassResolver.loadClass(AbstractClassResolver.java:123) at org.jboss.marshalling.AbstractClassResolver.resolveClass(AbstractClassResolver.java:104) at org.jboss.marshalling.river.RiverUnmarshaller.doReadClassDescriptor(RiverUnmarshaller.java:1022) at org.jboss.marshalling.river.RiverUnmarshaller.doReadNewObject(RiverUnmarshaller.java:1351) at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:272) at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:205) at org.jboss.marshalling.AbstractObjectInput.readObject(AbstractObjectInput.java:76) at org.wildfly.naming.client.remote.RemoteServerTransport.handleLookup(RemoteServerTransport.java:170) ... 8 more
This is a regression compared to WildFly 12, therefore I am marking this issue as a blocker.
- is caused by
-
WFCORE-3705 Allow dependencies on JDK modules
- Resolved
-
WFNC-55 Naming Client must always set thread context class loader
- Resolved
-
WFLY-12162 Upgrade Naming Client to 1.0.11.Final
- Closed
- is related to
-
WFCORE-4531 Eliminate WF naming workaround
- Closed