Bug 1201358

Summary:	[GSS](6.4.z) java.lang.ClassNotFoundException: org.jboss.naming.remote.client.InitialContextFactory
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Tom Ross <tom.ross>
Component:	JMS	Assignee:	baranowb <bbaranow>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Miroslav Novak <mnovak>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.3.3	CC:	bbaranow, bmaxwell, cdewolf, istudens, jawilson, msvehla, okalman, rsvoboda, tom.ross
Target Milestone:	CR1
Target Release:	EAP 6.4.4
Hardware:	Unspecified
OS:	Unspecified
URL:	https://github.com/jbossas/jboss-eap/pull/2378
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-01-17 10:54:04 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1235744

Description Tom Ross 2015-03-12 14:34:21 UTC

To reproduce this issue follow the steps:

 - setup JMS bridge between two JBoss EAP instances
 - once JMS bridge is running, login into jboss-cli and stop the bridge
 - restart the bridge fro jboss-cli

The following exception appears in the serve log file.

10:12:59,414 INFO  [org.hornetq.jms.server] (pool-9-thread-1) HQ121000: Failed to set up JMS bridge connections. Most probably the source or target servers are unavailable. Will retry after a pause of 60,000 ms
10:13:59,416 WARN  [org.hornetq.jms.server] (pool-9-thread-1) HQ122010: Failed to connect JMS Bridge: javax.naming.NamingException: JBAS011843: Failed instantiate InitialContextFactory org.jboss.naming.remote.client.InitialContextFactory from classloader ModuleClassLoader for Module "org.jboss.as.controller:main" from local module loader @543a2dec (finder: local module finder @379d0c27 (roots: /Volumes/RedHat/Work/JBoss/EAP/JBoss-6/current/home/modules,/Volumes/RedHat/Work/JBoss/EAP/JBoss-6/current/home/modules/system/layers/base)) [Root exception is java.lang.ClassNotFoundException: org.jboss.naming.remote.client.InitialContextFactory from [Module "org.jboss.as.controller:main" from local module loader @543a2dec (finder: local module finder @379d0c27 (roots: /Volumes/RedHat/Work/JBoss/EAP/JBoss-6/current/home/modules,/Volumes/RedHat/Work/JBoss/EAP/JBoss-6/current/home/modules/system/layers/base))]]
	at org.jboss.as.naming.InitialContext.getDefaultInitCtx(InitialContext.java:126)
	at org.jboss.as.naming.InitialContext.init(InitialContext.java:107)
	at javax.naming.ldap.InitialLdapContext.<init>(InitialLdapContext.java:153) [rt.jar:1.7.0_75]
	at org.jboss.as.naming.InitialContext.<init>(InitialContext.java:98)
	at org.jboss.as.naming.InitialContextFactory.getInitialContext(InitialContextFactory.java:44)
	at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684) [rt.jar:1.7.0_75]
	at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:307) [rt.jar:1.7.0_75]
	at javax.naming.InitialContext.init(InitialContext.java:242) [rt.jar:1.7.0_75]
	at javax.naming.InitialContext.<init>(InitialContext.java:216) [rt.jar:1.7.0_75]
	at org.hornetq.jms.bridge.impl.JNDIFactorySupport.createObject(JNDIFactorySupport.java:55)
	at org.hornetq.jms.bridge.impl.JNDIDestinationFactory.createDestination(JNDIDestinationFactory.java:40)
	at org.hornetq.jms.bridge.impl.JMSBridgeImpl.setupJMSObjects(JMSBridgeImpl.java:1236)
	at org.hornetq.jms.bridge.impl.JMSBridgeImpl.setupJMSObjectsWithRetry(JMSBridgeImpl.java:1474)
	at org.hornetq.jms.bridge.impl.JMSBridgeImpl.access$2200(JMSBridgeImpl.java:79)
	at org.hornetq.jms.bridge.impl.JMSBridgeImpl$FailureHandler.run(JMSBridgeImpl.java:2082)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_75]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_75]
	at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_75]
Caused by: java.lang.ClassNotFoundException: org.jboss.naming.remote.client.InitialContextFactory from [Module "org.jboss.as.controller:main" from local module loader @543a2dec (finder: local module finder @379d0c27 (roots: /Volumes/RedHat/Work/JBoss/EAP/JBoss-6/current/home/modules,/Volumes/RedHat/Work/JBoss/EAP/JBoss-6/current/home/modules/system/layers/base))]
	at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:213) [jboss-modules.jar:1.3.5.Final-redhat-1]
	at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:459) [jboss-modules.jar:1.3.5.Final-redhat-1]
	at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:408) [jboss-modules.jar:1.3.5.Final-redhat-1]
	at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:389) [jboss-modules.jar:1.3.5.Final-redhat-1]
	at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:134) [jboss-modules.jar:1.3.5.Final-redhat-1]
	at java.lang.Class.forName0(Native Method) [rt.jar:1.7.0_75]
	at java.lang.Class.forName(Class.java:274) [rt.jar:1.7.0_75]
	at org.jboss.as.naming.InitialContext.getDefaultInitCtx(InitialContext.java:121)
	... 17 more

Comment 12 Miroslav Novak 2015-09-25 14:39:43 UTC

I've manged to reproduce the issue with EAP 6.3.1.CP. EAP 6.4.4.CP.CR3 does not contain the issue. Setting as verified.

Note:
For the JMSBridgeManagementTestCase test which is intermittently failing new bz#1266498 was reported.

Comment 13 Petr Penicka 2017-01-17 10:54:04 UTC

Retroactively bulk-closing issues from released EAP 6.4 cumulative patches.

Comment 14 Petr Penicka 2017-01-17 10:55:32 UTC

Retroactively bulk-closing issues from released EAP 6.4 cumulative patches.

Comment 15 Red Hat Bugzilla 2023-09-14 02:56:07 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days