JBoss 5.1 throws NameNotFoundException while starting up

[Ananth Vasudevan]

Hi,

I'm migrating from JBOSS 4.0.3 to 5.1. I'm encountering a NameNotFoundException when it starts the JMSSenderService which
is a MBean defined in jboss-service.xml.

- JBoss server is using the "all" configuration
- JBoss 5.1 is running on Linux using JDK 1.6.0_20

I've posted the start up logs from the JBoss server, contents from the jboss-service.xml, where this MBean is referenced
and here's the line where the exception is thrown:

TopicConnectionFactory topicConnectionFactory = (TopicConnectionFactory)ctx.lookup(java:/ConnectionFactory);

Anybody has any ideas has to how to solve this problem? JBoss does not start and throws a lot of exceptions because of this exception.
Please let me know, if you need any additional information to diagonize this problem.

<!-- ============================================================= -->
	<!-- MBean: JMSService                                       -->
	<!-- ============================================================= -->
	<mbean code="com.aa.cc.bl.jms.service.JMSService"
		name="com.aa.cc.bl.jms.service:service=JMSService">

		<attribute name="JndiName">java:/aa/cc/jms/objects/JMSSender</attribute>
		<!--
			If you set the next two attributes to 0, or atleast the second is 0 ,
			then no pool for JMSSender objects will be created, but a single JMSSender object.
		-->
		<attribute name="MinPoolSize">6</attribute>
		<attribute name="MaxPoolSize">10</attribute>
		<!--
			Set this attribute to true if your JMS Server is deployed as HASingleton service
			and your topics are bound to the HAJNDI or to false if you have separate JMS Server
			on each node and your topics are bound to the local JNDI for each node.
		-->
		<attribute name="UseHAJNDI">false</attribute>
		<attribute name="TopicConnectionFactoryJNDIName">java:/ConnectionFactory</attribute>
		<attribute name="TopicsJNDINames">
			ServletTopicJNDIName 				= topic/AA_SERVLET_EVENT_LISTENER_TOPIC;
			NotificationTopicJNDIName 			= topic/AA_EVENT_NOTIFICATION_TOPIC;
		</attribute>
		
	</mbean>
	
	
	
	

	
	
	=========================================================================
	
	  JBoss Bootstrap Environment
	
	  JBOSS_HOME: /opt/jboss
	
	  JAVA: /opt/java/bin/java
	
	  JAVA_OPTS: -Dprogram.name=run.sh -server -Xms128m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.preferIPv4Stack=true
	
	  CLASSPATH: /opt/jboss/bin/run.jar:/opt/java/lib/tools.jar
	
	=========================================================================
	
	
	16:55:00,463 INFO  [ServerImpl] Starting JBoss (Microcontainer)...
	16:55:00,465 INFO  [ServerImpl] Release ID: JBoss [The Oracle] 5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221634)
	16:55:00,465 INFO  [ServerImpl] Bootstrap URL: null
	16:55:00,465 INFO  [ServerImpl] Home Dir: /opt/jboss-5.1.0.GA
	16:55:00,465 INFO  [ServerImpl] Home URL: file:/opt/jboss-5.1.0.GA/
	16:55:00,466 INFO  [ServerImpl] Library URL: file:/opt/jboss-5.1.0.GA/lib/
	16:55:00,466 INFO  [ServerImpl] Patch URL: null
	16:55:00,467 INFO  [ServerImpl] Common Base URL: file:/opt/jboss-5.1.0.GA/common/
	16:55:00,467 INFO  [ServerImpl] Common Library URL: file:/opt/jboss-5.1.0.GA/common/lib/
	16:55:00,467 INFO  [ServerImpl] Server Name: all
	16:55:00,467 INFO  [ServerImpl] Server Base Dir: /opt/jboss-5.1.0.GA/server
	16:55:00,467 INFO  [ServerImpl] Server Base URL: file:/opt/jboss-5.1.0.GA/server/
	16:55:00,468 INFO  [ServerImpl] Server Config URL: file:/opt/jboss-5.1.0.GA/server/all/conf/
	16:55:00,468 INFO  [ServerImpl] Server Home Dir: /opt/jboss-5.1.0.GA/server/all
	16:55:00,468 INFO  [ServerImpl] Server Home URL: file:/opt/jboss-5.1.0.GA/server/all/
	16:55:00,468 INFO  [ServerImpl] Server Data Dir: /opt/jboss-5.1.0.GA/server/all/data
	16:55:00,468 INFO  [ServerImpl] Server Library URL: file:/opt/jboss-5.1.0.GA/server/all/lib/
	16:55:00,469 INFO  [ServerImpl] Server Log Dir: /opt/jboss-5.1.0.GA/server/all/log
	16:55:00,469 INFO  [ServerImpl] Server Native Dir: /opt/jboss-5.1.0.GA/server/all/tmp/native
	16:55:00,469 INFO  [ServerImpl] Server Temp Dir: /opt/jboss-5.1.0.GA/server/all/tmp
	16:55:00,469 INFO  [ServerImpl] Server Temp Deploy Dir: /opt/jboss-5.1.0.GA/server/all/tmp/deploy
	16:55:01,836 INFO  [ServerImpl] Starting Microcontainer, bootstrapURL=file:/opt/jboss-5.1.0.GA/server/all/conf/bootstrap.xml
	16:55:02,835 INFO  [VFSCacheFactory] Initializing VFSCache [org.jboss.virtual.plugins.cache.CombinedVFSCache]
	16:55:02,838 INFO  [VFSCacheFactory] Using VFSCache [CombinedVFSCache[real-cache: null]]
	16:55:03,810 INFO  [CopyMechanism] VFS temp dir: /opt/jboss-5.1.0.GA/server/all/tmp
	16:55:03,811 INFO  [ZipEntryContext] VFS force nested jars copy-mode is enabled.
	16:55:07,311 INFO  [ServerInfo] Java version: 1.6.0_20,Sun Microsystems Inc.
	16:55:07,313 INFO  [ServerInfo] Java Runtime: Java(TM) SE Runtime Environment (build 1.6.0_20-b02)
	16:55:07,313 INFO  [ServerInfo] Java VM: Java HotSpot(TM) Server VM 16.3-b01,Sun Microsystems Inc.
	16:55:07,313 INFO  [ServerInfo] OS-System: Linux 2.6.18-194.3.1.el5,i386
	16:55:07,314 INFO  [ServerInfo] VM arguments: -Dprogram.name=run.sh -Xms128m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.preferIPv4Stack=true -Djava.endorsed.dirs=/opt/jboss/lib/endorsed
	16:55:07,390 INFO  [JMXKernel] Legacy JMX core initialized
	16:55:14,839 INFO  [ProfileServiceBootstrap] Loading profile: ProfileKey@155e3ab[domain=default, server=default, name=all]
	16:55:20,533 INFO  [WebService] Using RMI server codebase: http://127.0.0.1:8083/
	16:55:20,951 INFO  [Naming] Started jndi bootstrap jnpPort=1099, rmiPort=1098, backlog=50, bindAddress=/127.0.0.1, Client SocketFactory=null, Server SocketFactory=org.jboss.net.sockets.DefaultSocketFactory@e048aaa4[bindAddress=/127.0.0.1]
	16:55:22,324 INFO  [MainDeployer] deploy, url=file:/opt/jboss-5.1.0.GA/server/all/deploy/ROOT.war/
	16:55:22,508 INFO  [MainDeployer] deploy, url=file:/opt/jboss-5.1.0.GA/server/all/deploy/access-bcc.war
	16:55:22,600 INFO  [MainDeployer] deploy, url=file:/opt/jboss-5.1.0.GA/server/all/deploy/admin-console.war/
	16:55:23,681 INFO  [MainDeployer] deploy, url=file:/opt/jboss-5.1.0.GA/server/all/deploy/cache-invalidation-service.xml
	16:55:23,740 INFO  [MainDeployer] deploy, url=file:/opt/jboss-5.1.0.GA/server/all/deploy/bcc.ear
	16:55:26,734 INFO  [DatasourcesService] Applying datasources configuration: Default
	16:55:26,735 INFO  [MainDeployer] deploy, url=file:/opt/jboss-5.1.0.GA/server/all/datasources/postgresql-ds.xml
	16:55:26,745 INFO  [MainDeployer] deploy, url=file:/opt/jboss-5.1.0.GA/server/all/datasources/quartz-ds.xml
	16:55:26,795 INFO  [MainDeployer] deploy, url=file:/opt/jboss-5.1.0.GA/server/all/datasources/cluster-ds.xml
	16:55:26,967 INFO  [JMSSenderService] Starting JMSSender service
	16:55:26,994 ERROR [STDERR] javax.naming.NameNotFoundException: ConnectionFactory not bound
	16:55:26,995 ERROR [STDERR]     at org.jnp.server.NamingServer.getBinding(NamingServer.java:514)
	16:55:26,995 ERROR [STDERR]     at org.jnp.server.NamingServer.getBinding(NamingServer.java:522)
	16:55:26,995 ERROR [STDERR]     at org.jnp.server.NamingServer.getObject(NamingServer.java:528)
	16:55:26,995 ERROR [STDERR]     at org.jnp.server.NamingServer.lookup(NamingServer.java:281)
	16:55:26,995 ERROR [STDERR]     at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:610)
	16:55:26,995 ERROR [STDERR]     at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:572)
	16:55:26,995 ERROR [STDERR]     at javax.naming.InitialContext.lookup(InitialContext.java:392)
	16:55:26,995 ERROR [STDERR]     at com.aa.cc.bl.jms.objects.JMSSenderObject.initJMS(JMSSenderObject.java:401)
	16:55:26,999 ERROR [STDERR]     at com.aa.cc.bl.jms.objects.JMSSenderObject.<init>(JMSSenderObject.java:117)
	16:55:26,999 ERROR [STDERR]     at com.aa.cc.bl.jms.objects.JMSSenderObjectsPool.init(JMSSenderObjectsPool.java:62)
	16:55:27,000 ERROR [STDERR]     at com.aa.cc.bl.jms.objects.JMSSenderManager.<init>(JMSSenderManager.java:51)
	16:55:27,000 ERROR [STDERR]     at com.aa.cc.bl.jms.service.JMSSenderService.startService(JMSService.java:194)
	16:55:27,000 ERROR [STDERR]     at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:376)
	16:55:27,000 ERROR [STDERR]     at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:269)
	16:55:27,000 ERROR [STDERR]     at com.aa.cc.bl.jms.service.JMSSenderService.invoke(JMSSenderService.java:395)
	16:55:27,000 ERROR [STDERR]     at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
	16:55:27,000 ERROR [STDERR]     at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
	16:55:27,001 ERROR [STDERR]     at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:206)
	16:55:27,001 ERROR [STDERR]     at $Proxy38.start(Unknown Source)

[Ananth Vasudevan]

Corrected the code posted above (Included double quotes for lookup, otherwisem it wouldn't compile):

TopicConnectionFactory topicConnectionFactory = (TopicConnectionFactory)ctx.lookup("java:/ConnectionFactory"); 

Any help is greatly appreciated.

[Peter Johnson]

Are you saying that you added the com.aa.cc.bl.jms.service:service=JMSService mbean declaration to jboss-service.xml? That will not work in AS 5.x because AS 5.x uses JBoss Messaging (unlike 4.x which used JBossMQ) and Messaging is not based on JMX. I think that you are going to have to look at the Messaging documentation and find out how you can do the things that the com.aa.cc.bl.jms.service:service=JMSService mbean did using the new mechanisms for configuring Messaging. At minimum you will have to change you mbean to be a pojo bean managed by the microcontainer.

[Ananth Vasudevan]

Thanks for the quick response.
Yes. The JMSService mbean declaration is in jboss-service.xml.
Thanks for the pointer. I'll try to make the changes for JBoss Messaging and post an update.

[Ananth Vasudevan]

peter,
Quick Question: Is JBoss Messaging bundled with JBoss 5.1GA or should I install it on top of Jboss 5.1?

[Jaikiran Pai]

JBoss Messaging comes bundled with AS5.