MDB does not work with JBoss 3.2.0 Tomcat

[richaud]

I have a MDB connected to "testQueue" that used to work with JBoss 3.0.6. I decided to switch from JBoss 3.0.6 to the latest JBoss 3.2.0 integrated with Catalina/Tomcat 4.x.

I redeployed my EJB ejar file to de deploy dir (default configuration for the server). Now I get always the same exception after deployment of my jar file:

javax.jms.JMSException: Error creating the dlq connection: XAConnectionFactory not bound
at org.jboss.ejb.plugins.jms.DLQHandler.createService(DLQHandler.java:152)
at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:158)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerCreate(JMSContainerInvoker.java:394)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker.startService(JMSContainerInvoker.java:553)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker$ExceptionListenerImpl.onException(JMSContainerInvoker.java:1053
)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker$1.run(JMSContainerInvoker.java:565)
11:33:13,807 INFO [JMSContainerInvoker] Trying to reconnect to JMS provider


Many thanks for your help.

Olivier.
[e-mail]

[adrian.brock]

Why is XAConnectionFactory not bound?

Regards,
Adrian

[richaud]

I don't know why I get this error.

FYI, here are some parts of my configuration files :

In the default/deploy directory, jbossmq-destinations-service.xml:
...

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








...

My ejb-jar.xml located in my META-INF directory:
...

<message-driven >
<![CDATA[]]>

<ejb-name>MailDispatcher</ejb-name>

<ejb-class>fr.ods.ejb.MailDispatcherBean</ejb-class>

<transaction-type>Bean</transaction-type>
<acknowledge-mode>Auto-acknowledge</acknowledge-mode>
<message-driven-destination>
<destination-type>javax.jms.Queue</destination-type>
<subscription-durability>NonDurable</subscription-durability>
</message-driven-destination>

</message-driven>

....


My jboss.xml file located in my META-INF directory:
...
<message-driven>
<ejb-name>MailDispatcher</ejb-name>
<destination-jndi-name>queue/testQueue</destination-jndi-name>
</message-driven>
...

[adrian.brock]

Your problem is the mdb is trying to connect
to the jms server, but the connection factory
is not bound into jndi.

Look further back in the log for errors.

The default config for mdb connections is at the top of
jms-service.xml
The connection factories are configured at the
start of jbossmq-service.xml

Regards,
Adrian

[richaud]

Surprisingly, I did not find in the jboss version I have (jboss-3.2.0_tomcat_4.1.24) the file you're mentionning (jms-service.xml), file that was indeed present in the jboss3.0.6 version I previously used. This file appears in all the various 3.0.6 configuration but is absent from my new 3.2.0 version.

I copied the old jms-service.xml file to the deploy directory. Nothing except a new error.

Thanks.

Olivier.

PS: for those who are insterested, I can send a zip file of my server.log

[adrian.brock]

Sorry it is called jms-ds.xml in 3.2

Why don't you attach the server.log?

But before doing that, have a look at
JNDIView at http://localhost:8080/jmx-console
you should have java:/XAConnectionFactory

Regards,
Adrian

[richaud]

Sorry, here is my server.log.

I found the jms-ds.xml file that replaces jms-service.xml. I took a look at the entries, and all looks fine, but I'm not an expert...

[adrian.brock]

JBossMQ is not starting because
the persistence manager uses
jboss.jca:service=LocalTxCM,name=DefaultDS

But you have changed the name to
jboss.jca:service=LocalTxCM,name=RichaudNet

You didn't mention the big "incompleteDeployments"
exception

Regards,
Adrian

[richaud]

Many many thanks for your help.

Olivier.