-
Bug
-
Resolution: Done
-
Blocker
-
7.1.0.DR8, 7.1.0.DR9
-
None
-
Regression, Blocks Testing
-
-
-
-
-
-
-
When trying to use jboss-remote-naming with dependencies taken from EAP 7.1.0.DR8, that means with Remoting 5, everything fails with:
javax.naming.NamingException: Failed to create remoting connection [Root exception is java.lang.NoClassDefFoundError: org/jboss/remoting3/Remoting]
at org.jboss.naming.remote.client.ClientUtil.namingException(ClientUtil.java:51)
at org.jboss.naming.remote.client.InitialContextFactory.getInitialContext(InitialContextFactory.java:152)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:313)
at javax.naming.InitialContext.init(InitialContext.java:244)
at javax.naming.InitialContext.<init>(InitialContext.java:216)
at org.jboss.qa.ejbclient.jndi.InitialContextDirectoryRemoteNaming.<init>(InitialContextDirectoryRemoteNaming.java:40)
at org.jboss.qa.ejbclient.jndi.InitialContextDirectory$Supplier.get(InitialContextDirectory.java:50)
... 124 more
Caused by: java.lang.NoClassDefFoundError: org/jboss/remoting3/Remoting
at org.jboss.naming.remote.client.EndpointCache.get(EndpointCache.java:47)
at org.jboss.naming.remote.client.InitialContextFactory.createEndpoint(InitialContextFactory.java:226)
at org.jboss.naming.remote.client.InitialContextFactory.getOrCreateEndpoint(InitialContextFactory.java:207)
at org.jboss.naming.remote.client.InitialContextFactory.getOrCreateNamingStore(InitialContextFactory.java:170)
at org.jboss.naming.remote.client.InitialContextFactory.getInitialContext(InitialContextFactory.java:146)
... 130 more
Caused by: java.lang.ClassNotFoundException: org.jboss.remoting3.Remoting
at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
... 135 more
Note that jboss-remote-naming is deprecated and will possibly be removed altogether, that discussion is still ongoing.
- is duplicated by
-
JBEAP-7259 Remote client fails to lookup objects from JNDI due to java.lang.ClassNotFoundException: org.jboss.remoting3.Remoting
-
- Closed
-
- is related to
-
JBEAP-7273 Content of jboss-client.jar does not provide required features
-
- Closed
-
-
JBEAP-7493 JMS bridge not able to lookup remote destination
-
- Closed
-