MDB issue in Weblogic 10.0.2, but working fine in 8.1

Question

Hello,
I have multiple MDB's (EJB 2.1) working fine in Weblogic 8.1 and we are now moving to Weblogic 10.0.2. If I understand EJB2.1 is still supported in Weblogic 10.0.2 so deployed the same EAR files in weblogic 10.0.2 successfully.
Then I have configured the Connection Factory, Queues etc in console (grouping as subdeployments) and now when the application server starts up its throwing the following warning
<Mar 2, 2010 12:10:05 PM EST> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: ReportingMessageListener is unable to connect to the JMS destination: ReportingQueue. The Error was:[EJB:011013]The Message-Driven EJB attempted to connect to the JMS connection factory with the JNDI name: MPConnectionFactory. However, the object with the JNDI name: MPConnectionFactory is not a JMS connection factory. NestedException Message is :weblogic.jms.client.JMSConnectionFactory>
Not sure why its unable to connect to my connection factory. I am pasting all the entries and let me know if I am missing anything.
Here's my weblogic-ejb-jar entry
<weblogic-enterprise-bean>
<ejb-name>ReportingMessageListener</ejb-name>
<message-driven-descriptor>
<destination-jndi-name>ReportingQueue</destination-jndi-name>
<connection-factory-jndi-name>MPConnectionFactory</connection-factory-jndi-name>
</message-driven-descriptor>
<reference-descriptor>
<resource-description>
<res-ref-name>jdbc/REPORTING_USER</res-ref-name>
<jndi-name>REPORTING_USER</jndi-name>
</resource-description>
<ejb-local-reference-description>
<ejb-ref-name>ejb/ReportingFacadeLocal</ejb-ref-name>
<jndi-name>ReportingFacadeLocal</jndi-name>
</ejb-local-reference-description>
</reference-descriptor>
here's my entry in weblogic config.xml file
<jms-server>
<name>ManagedPayJMSServer</name>
<target>AdminServer</target>
<persistent-store>ManagedPayFileStore</persistent-store>
<temporary-template-resource xsi:nil="true"></temporary-template-resource>
<temporary-template-name xsi:nil="true"></temporary-template-name>
</jms-server>
<jms-system-resource>
<name>MP JMS Module</name>
<target>AdminServer</target>
<sub-deployment>
<name>MP-JMS</name>
<target>ManagedPayJMSServer</target>
</sub-deployment>
<descriptor-file-name>jms/mp_jms_module-2983-jms.xml</descriptor-file-name>
</jms-system-resource>
Entries in jms config file
<?xml version='1.0' encoding='UTF-8'?>
<weblogic-jms xmlns="http://www.bea.com/ns/weblogic/90" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xsi:schemaLocation="http://www.bea.com/ns/weblogic/920 http://www.bea.com/ns/weblogic/920.xsd">
<connection-factory name="*MPConnectionFactory*">
<sub-deployment-name>MP-JMS</sub-deployment-name>
<jndi-name>MPConnectionFactory</jndi-name>
<security-params>
<attach-jmsx-user-id>false</attach-jmsx-user-id>
</security-params>
</connection-factory>
<queue name="*ReportingQueue*">
<sub-deployment-name>MP-JMS</sub-deployment-name>
<jndi-name>ReportingQueue</jndi-name>
</queue>
</weblogic-jms>
Thanks,

Answer 1

Does your MDB require transactions ? If so you need to XA enable the connection factory. Looks like you are using a transactional MDB with non XA connection factory.