javax.naming.NameNotFoundException: ConnectionFactory not bo

[cunparis]

I'm using JBoss 3.0 and am following the QuickStart Guide. I am getting this exception:

javax.naming.NameNotFoundException: ConnectionFactory not bound

I can't figure out why. The quickstart doesn't mention any configuration to do, and I can see the ConnectionFactory is defined in the XML files. Here is my jbossmq-service.xml file:

<?xml version="1.0" encoding="UTF-8"?>

<!-- $Id: jbossmq-service.xml,v 1.1.2.3 2002/05/09 04:25:10 chirino Exp $ -->



<!-- ==================================================================== -->
<!-- JBossMQ -->
<!-- ==================================================================== -->


<!-- ==================================================================== -->
<!-- Invocation Layers -->
<!-- ==================================================================== -->
<!--
| InvocationLayers are the different transport methods that can
| be used to access the server.
-->


<depends optional-attribute-name="Invoker">jboss.mq:service=Invoker
java:/ConnectionFactory
java:/XAConnectionFactory
0



<depends optional-attribute-name="Invoker">jboss.mq:service=Invoker
RMIConnectionFactory
RMIXAConnectionFactory
60000



<depends optional-attribute-name="Invoker">jboss.mq:service=Invoker
ConnectionFactory
XAConnectionFactory
8090
60000
true



<depends optional-attribute-name="Invoker">jboss.mq:service=Invoker
UILConnectionFactory
UILXAConnectionFactory
8091
60000
true


<!-- ==================================================================== -->
<!-- JBossMQ Interceptor chain configuration -->
<!-- ==================================================================== -->
<!-- To tune performance, you can have the Invoker skip over the TracingInterceptor -->
<!-- and/or the SecurityManager, but then you loose the ability to trace and/or enforce security. -->

<depends optional-attribute-name="NextInterceptor">jboss.mq:service=TracingInterceptor



org.jboss.mq.server.TracingInterceptor
<depends optional-attribute-name="NextInterceptor">jboss.mq:service=SecurityManager



<depends optional-attribute-name="NextInterceptor">jboss.mq:service=DestinationManager



<depends optional-attribute-name="PersistenceManager">jboss.mq:service=PersistenceManager
<depends optional-attribute-name="StateManager">jboss.mq:service=StateManager


<!--
| The MessageCache decides where to put JBossMQ message that
| are sitting around waiting to be consumed by a client.
|
| The memory marks are in Megabytes. Once the JVM memory usage hits
| the high memory mark, the old messages in the cache will start getting
| stored in the DataDirectory. As memory usage gets closer to the
| Max memory mark, the amount of message kept in the memory cache aproaches 0.
-->

500
600
<depends optional-attribute-name="CacheStore">jboss.mq:service=CacheStore


<!--
| The CacheStore decides where to store JBossMQ message that
| that the MessageCache has decided to move in secondary storage.
-->

tmp/jbossmq


<!--
| The StateManager is used to keep JMS persistent state data.
| For example: what durable subscriptions are active.
-->

<!-- This file is pulled from the configuration URL of the server -->
jbossmq-state.xml


<!-- The PersistenceManager is used to store messages to disk. -->

db/jbossmq/file
<depends optional-attribute-name="MessageCache">jboss.mq:service=MessageCache


<!--
| The jdbc2 PersistenceManager is the new improved JDBC implementation.
| This implementation allows you to control how messages are stored in
| the database.
|
| Use this PM if you want the reliablity a relational database can offer
| you. The default configuration is known to work with hsqldb, other databases
| will requrie teaking of the SqlProperties.
-->
<!--

<depends optional-attribute-name="MessageCache">jboss.mq:service=MessageCache
<depends optional-attribute-name="DataSource">jboss.jca:service=LocalTxDS,name=hsqldbDS
jboss.jca:service=LocalTxCM,name=hsqldbDS

BLOB_TYPE=OBJECT_BLOB
INSERT_TX = INSERT INTO JMS_TRANSACTIONS (TXID) values(?)
INSERT_MESSAGE = INSERT INTO JMS_MESSAGES (MESSAGEID, DESTINATION, MESSAGEBLOB, TXID, TXOP) VALUES(?,?,?,?,?)
SELECT_ALL_UNCOMMITED_TXS = SELECT TXID FROM JMS_TRANSACTIONS
SELECT_MAX_TX = SELECT MAX(TXID) FROM JMS_MESSAGES
SELECT_MESSAGES_IN_DEST = SELECT MESSAGEID, MESSAGEBLOB FROM JMS_MESSAGES WHERE DESTINATION=?
SELECT_MESSAGE = SELECT MESSAGEID, MESSAGEBLOB FROM JMS_MESSAGES WHERE MESSAGEID=? AND DESTINATION=?
MARK_MESSAGE = UPDATE JMS_MESSAGES SET (TXID, TXOP) VALUES(?,?) WHERE MESSAGEID=? AND DESTINATION=?
DELETE_ALL_MESSAGE_WITH_TX = DELETE FROM JMS_MESSAGES WHERE TXID=?
DELETE_TX = DELETE FROM JMS_TRANSACTIONS WHERE TXID = ?
DELETE_MARKED_MESSAGES = DELETE FROM JMS_MESSAGES WHERE TXID=? AND TXOP=?
DELETE_MESSAGE = DELETE FROM JMS_MESSAGES WHERE MESSAGEID=? AND DESTINATION=?
CREATE_MESSAGE_TABLE = CREATE TABLE JMS_MESSAGES ( MESSAGEID INTEGER NOT NULL, \
DESTINATION VARCHAR(50) NOT NULL, TXID INTEGER, TXOP CHAR(1), \
MESSAGEBLOB OBJECT, PRIMARY KEY (MESSAGEID, DESTINATION) )
CREATE_TX_TABLE = CREATE TABLE JMS_TRANSACTIONS ( TXID INTEGER )


-->

<!-- ==================================================================== -->
<!-- System Destinations -->
<!-- ==================================================================== -->

<!-- Dead Letter Queue -->

<depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager
<depends optional-attribute-name="SecurityManager">jboss.mq:service=SecurityManager

[cunparis]

It started working, without any XML config file changes. I think it had to do with restarting the server but I'm not sure.

[aramir]

Hi! I've the same problem. When I run my client app, then I'll get exception: javax.naming.NameNotFoundException: QueueConnectionFactory not bound

Is there any problem with .xml config file? Where is the problem?

Thanks.

[larsinge]

Try to connect to the "java:/ConnectionFactory".

[pearlo]

Use JNDIVIEW accessible from the http://localhost:1099/jmx-console to get the hierarchical listing of the Bound JNDI. In version 3.0.2 we already have queues "A","B", etc under the hive "queue" therefore
the JNDI Name for the queue becomes "queue/A" which can be used as
............
Queue q = (Queue)ctx.lookup("queue/A");
............
similarly you can exactly get the correct JNDI name for your custom queue. I must mention I am using JBoss 3.0.2.

Hope this helps

Rgds

Muthukumaran

[suvankar17]

Dear friends,
Please dont alter any xml config file in your Jboss3.0.0, the solution to your problem is


InitialContext ctx = new InitialContext();
TopicConnectionFactory topicConnectionFactory = null;
TopicConnection topicConnection = null;
TopicSession topicSession = null;
Topic topic = null;
TopicSubscriber topicSubscriber = null;
ObjectMessage message = null;
topicConnectionFactory = (TopicConnectionFactory)ctx.lookup("ConnectionFactory");
System.out.println("Got topic Factory");
topic = (Topic)ctx.lookup("topic/TEST_TOPIC");
System.out.println("Got queue");


Do not make a lookup on "TopicConnectionFactory" or "QueueConnectionFactory"...instead make a lookup with "ConnectionFactory".


I hope it helps you.

Regards,
Suv