2 Replies Latest reply on May 7, 2004 3:02 AM by robinpaul

    Error creating the dlq connection: XAConnectionFactory not b

    robinpaul
    robinpaul May 6, 2004 1:06 PM

      Hi

      I have problem deploying my MDB in Jboss 3.2.3 Setup when i try to deploy it after switching the standard jdbc provider to Oracle. It thows the following Exception

      2004-05-06 23:00:28,500 INFO [org.jboss.ejb.EjbModule] Deploying TextMDB
      2004-05-06 23:00:28,875 ERROR [org.jboss.ejb.plugins.jms.DLQHandler] Initialization failed
      javax.jms.JMSException: Error creating the dlq connection: XAConnectionFactory not bound
      at org.jboss.ejb.plugins.jms.DLQHandler.createService(DLQHandler.java:169)
      at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:158)
      at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerCreate(JMSContainerInvoker.java:458)
      at org.jboss.ejb.plugins.jms.JMSContainerInvoker.startService(JMSContainerInvoker.java:674)
      at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:192)
      at org.jboss.ejb.MessageDrivenContainer.startService(MessageDrivenContainer.java:234)
      at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:192)
      at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:324)
      at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546)
      at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:976)
      at $Proxy14.start(Unknown Source)
      at org.jboss.system.ServiceController.start(ServiceController.java:394)

      The same MDB gets deployed in case of hsql which comes by default with JBoss.

      My JDBC xmls are as shown below

      oracle-jdbc2-service.xml

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

      <!-- $Id: oracle-jdbc2-service.xml,v 1.1.2.1 2003/08/23 22:21:28 ejort Exp $ -->



      <!-- ==================================================================== -->
      <!-- Persistence and caching using Oracle -->
      <!-- IMPORTANT: Remove hsqldb-jdbc2-service.xml -->
      <!-- ==================================================================== -->

      <!--
      | The destination manager is the core service within JBossMQ
      -->

      <depends optional-attribute-name="MessageCache">jboss.mq:service=MessageCache
      <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.
      -->

      1
      2
      jboss.mq:service=PersistenceManager


      <!-- The PersistenceManager is used to store messages to disk. -->
      <!--
      | The jdbc2 PersistenceManager is the new improved JDBC implementation.
      | This implementation allows you to control how messages are stored in
      | the database.
      |
      | This jdbc2 PM configuration has been tested against Oracle
      -->

      <depends optional-attribute-name="ConnectionManager">jboss.jca:service=LocalTxCM,name=DefaultDS

      BLOB_TYPE=BINARYSTREAM_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=? WHERE MESSAGEID=? AND DESTINATION=?
      UPDATE_MESSAGE = UPDATE JMS_MESSAGES SET MESSAGEBLOB=? WHERE MESSAGEID=? AND DESTINATION=?
      UPDATE_MARKED_MESSAGES = UPDATE JMS_MESSAGES SET TXID=?, TXOP=? WHERE TXOP=?
      UPDATE_MARKED_MESSAGES_WITH_TX = UPDATE JMS_MESSAGES SET TXID=?, TXOP=? WHERE TXOP=? AND TXID=?
      DELETE_MARKED_MESSAGES_WITH_TX = DELETE FROM JMS_MESSAGES WHERE TXID IN (SELECT TXID FROM JMS_TRANSACTIONS) AND TXOP=?
      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(255) NOT NULL, TXID INTEGER, TXOP CHAR(1), \
      MESSAGEBLOB BLOB, PRIMARY KEY (MESSAGEID, DESTINATION) )
      CREATE_TX_TABLE = CREATE TABLE JMS_TRANSACTIONS ( TXID INTEGER )
      CREATE_TABLES_ON_STARTUP = TRUE





      and oracle-xa-ds.xml is as follows

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

      <!-- ===================================================================== -->
      <!-- -->
      <!-- JBoss Server Configuration -->
      <!-- -->
      <!-- ===================================================================== -->

      <!-- $Id: oracle-xa-ds.xml,v 1.1.2.13 2003/09/18 23:51:39 ejort Exp $ -->

      <!-- ===================================================================== -->
      <!-- ATTENTION: DO NOT FORGET TO SET Pad=true IN transaction-service.xml -->
      <!-- ===================================================================== -->


      <xa-datasource>
      <jndi-name>DefaultDS</jndi-name>
      <track-connection-by-tx>true</track-connection-by-tx>
      <isSameRM-override-value>false</isSameRM-override-value>
      <xa-datasource-class>oracle.jdbc.xa.client.OracleXADataSource</xa-datasource-class>
      <xa-datasource-property name="URL">jdbc:oracle:thin:@10.21.2.7:1521:sun8</xa-datasource-property>
      <xa-datasource-property name="User">Revera</xa-datasource-property>
      <xa-datasource-property name="Password">revera</xa-datasource-property>
      <!-- Uses the pingDatabase method to check a connection is still valid before handing it out from the pool -->
      <!--valid-connection-checker-class-name>org.jboss.resource.adapter.jdbc.vendor.OracleValidConnectionChecker</valid-connection-checker-class-name-->
      <!-- Checks the Oracle error codes and messages for fatal errors -->
      <!--exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.OracleExceptionSorter</exception-sorter-class-name-->
      <!-- Oracles XA datasource cannot reuse a connection outside a transaction once enlisted in a global transaction and vice-versa -->
      <no-tx-separate-pools/>
      </xa-datasource>


      <depends optional-attribute-name="TransactionManagerService">jboss:service=TransactionManager




      The relevent portions from the server.log file is as shown

      2004-05-06 23:00:15,000 INFO [org.jboss.jmx.adaptor.snmp.agent.SnmpAgentService] Started jboss.jmx:name=SnmpAgent,service=snmp,type=adaptor
      2004-05-06 23:00:15,062 INFO [org.jboss.deployment.MainDeployer] Deployed package: file:/L:/jboss-3.2.3/server/default/deploy/snmp-adaptor.sar/
      2004-05-06 23:00:15,156 INFO [org.jboss.deployment.MainDeployer] Starting deployment of package: file:/L:/jboss-3.2.3/server/default/deploy/uuid-key-generator.sar
      2004-05-06 23:00:15,421 INFO [org.jboss.ejb.plugins.keygenerator.uuid.UUIDKeyGeneratorFactoryService] Started jboss:service=UUIDKeyGeneratorFactory
      2004-05-06 23:00:15,484 INFO [org.jboss.deployment.MainDeployer] Deployed package: file:/L:/jboss-3.2.3/server/default/deploy/uuid-key-generator.sar
      2004-05-06 23:00:15,562 INFO [org.jboss.deployment.MainDeployer] Starting deployment of package: file:/L:/jboss-3.2.3/server/default/deploy/jboss-local-jdbc.rar
      2004-05-06 23:00:15,812 INFO [org.jboss.resource.RARDeployer] nested deployment: file:/L:/jboss-3.2.3/server/default/tmp/deploy/tmp39223jboss-local-jdbc.rar-contents/jboss-local-jdbc.jar
      2004-05-06 23:00:16,015 INFO [org.jboss.deployment.MainDeployer] Deployed package: file:/L:/jboss-3.2.3/server/default/deploy/jboss-local-jdbc.rar
      2004-05-06 23:00:16,093 INFO [org.jboss.deployment.MainDeployer] Starting deployment of package: file:/L:/jboss-3.2.3/server/default/deploy/jboss-xa-jdbc.rar
      2004-05-06 23:00:16,296 INFO [org.jboss.resource.RARMetaData] Loading JBoss Resource Adapter for JDBC 2 XA drivers
      2004-05-06 23:00:16,343 INFO [org.jboss.resource.RARMetaData] Required license terms present. See deployment descriptor.
      2004-05-06 23:00:16,437 INFO [org.jboss.resource.RARDeployer] nested deployment: file:/L:/jboss-3.2.3/server/default/tmp/deploy/tmp39224jboss-xa-jdbc.rar-contents/jboss-xa-jdbc.jar
      2004-05-06 23:00:16,593 INFO [org.jboss.deployment.MainDeployer] Deployed package: file:/L:/jboss-3.2.3/server/default/deploy/jboss-xa-jdbc.rar
      2004-05-06 23:00:16,671 INFO [org.jboss.deployment.MainDeployer] Starting deployment of package: file:/L:/jboss-3.2.3/server/default/deploy/jms/jms-ra.rar
      2004-05-06 23:00:16,875 INFO [org.jboss.resource.RARDeployer] nested deployment: file:/L:/jboss-3.2.3/server/default/tmp/deploy/tmp39225jms-ra.rar-contents/jms-ra.jar
      2004-05-06 23:00:17,046 INFO [org.jboss.deployment.MainDeployer] Deployed package: file:/L:/jboss-3.2.3/server/default/deploy/jms/jms-ra.rar
      2004-05-06 23:00:17,125 INFO [org.jboss.deployment.MainDeployer] Starting deployment of package: file:/L:/jboss-3.2.3/server/default/deploy/jms/jms-ds.xml
      2004-05-06 23:00:17,703 INFO [org.jboss.jms.jndi.JMSProviderLoader] Bound adapter to java:/DefaultJMSProvider
      2004-05-06 23:00:17,750 INFO [org.jboss.jms.jndi.JMSProviderLoader] Started jboss.mq:service=JMSProviderLoader,name=JBossMQProvider
      2004-05-06 23:00:17,828 INFO [org.jboss.jms.asf.ServerSessionPoolLoader] pool factory StdJMSPool bound to java:/StdJMSPool
      2004-05-06 23:00:17,875 INFO [org.jboss.jms.asf.ServerSessionPoolLoader] Started jboss.mq:service=ServerSessionPoolMBean,name=StdJMSPool
      2004-05-06 23:00:17,984 INFO [org.jboss.resource.connectionmanager.RARDeployment] Started jboss.jca:service=ManagedConnectionFactory,name=JmsXA
      2004-05-06 23:00:18,046 INFO [org.jboss.resource.connectionmanager.JBossManagedConnectionPool] Started jboss.jca:service=ManagedConnectionPool,name=JmsXA
      2004-05-06 23:00:18,156 INFO [org.jboss.deployment.MainDeployer] Deployed package: file:/L:/jboss-3.2.3/server/default/deploy/jms/jms-ds.xml
      2004-05-06 23:00:18,234 INFO [org.jboss.deployment.MainDeployer] Starting deployment of package: file:/L:/jboss-3.2.3/server/default/deploy/oracle-xa-ds.xml
      2004-05-06 23:00:18,593 INFO [org.jboss.resource.connectionmanager.RARDeployment] Started jboss.jca:service=ManagedConnectionFactory,name=DefaultDS
      2004-05-06 23:00:18,671 INFO [org.jboss.resource.connectionmanager.JBossManagedConnectionPool] Started jboss.jca:service=ManagedConnectionPool,name=DefaultDS
      2004-05-06 23:00:18,734 INFO [org.jboss.resource.adapter.jdbc.xa.oracle.OracleXAExceptionFormatter] Started jboss.jca:service=OracleXAExceptionFormatter
      2004-05-06 23:00:18,781 INFO [org.jboss.deployment.MainDeployer] Deployed package: file:/L:/jboss-3.2.3/server/default/deploy/oracle-xa-ds.xml
      2004-05-06 23:00:18,890 INFO [org.jboss.deployment.MainDeployer] Starting deployment of package: file:/L:/jboss-3.2.3/server/default/deploy/cache-invalidation-service.xml
      2004-05-06 23:00:19,171 INFO [org.jboss.cache.invalidation.InvalidationManager] Starting Invalidation Manager jboss.cache:service=InvalidationManager
      2004-05-06 23:00:19,218 INFO [org.jboss.cache.invalidation.InvalidationManager] Started jboss.cache:service=InvalidationManager
      2004-05-06 23:00:19,281 INFO [org.jboss.deployment.MainDeployer] Deployed package: file:/L:/jboss-3.2.3/server/default/deploy/cache-invalidation-service.xml
      2004-05-06 23:00:19,437 INFO [org.jboss.deployment.MainDeployer] Starting deployment of package: file:/L:/jboss-3.2.3/server/default/deploy/client-deployer-service.xml
      2004-05-06 23:00:19,703 INFO [org.jboss.deployment.MainDeployer] Adding deployer: org.jboss.deployment.ClientDeployer@f0cb3c
      2004-05-06 23:00:19,765 INFO [org.jboss.deployment.ClientDeployer] Started jboss.j2ee:service=ClientDeployer
      2004-05-06 23:00:19,828 INFO [org.jboss.deployment.MainDeployer] Deployed package: file:/L:/jboss-3.2.3/server/default/deploy/client-deployer-service.xml
      2004-05-06 23:00:19,921 INFO [org.jboss.deployment.MainDeployer] Starting deployment of package: file:/L:/jboss-3.2.3/server/default/deploy/jms/jbossmq-destinations-service.xml
      2004-05-06 23:00:20,390 INFO [org.jboss.deployment.MainDeployer] Deployed package: file:/L:/jboss-3.2.3/server/default/deploy/jms/jbossmq-destinations-service.xml
      2004-05-06 23:00:20,515 INFO [org.jboss.deployment.MainDeployer] Starting deployment of package: file:/L:/jboss-3.2.3/server/default/deploy/jms/jbossmq-service.xml
      2004-05-06 23:00:21,046 INFO [org.jboss.mq.sm.file.DynamicStateManager] Started jboss.mq:service=StateManager
      2004-05-06 23:00:21,140 INFO [org.jboss.deployment.MainDeployer] Deployed package: file:/L:/jboss-3.2.3/server/default/deploy/jms/jbossmq-service.xml
      2004-05-06 23:00:21,218 INFO [org.jboss.deployment.MainDeployer] Starting deployment of package: file:/L:/jboss-3.2.3/server/default/deploy/jms/jvm-il-service.xml
      2004-05-06 23:00:21,484 INFO [org.jboss.deployment.MainDeployer] Deployed package: file:/L:/jboss-3.2.3/server/default/deploy/jms/jvm-il-service.xml
      2004-05-06 23:00:21,562 INFO [org.jboss.deployment.MainDeployer] Starting deployment of package: file:/L:/jboss-3.2.3/server/default/deploy/jms/oil-service.xml
      2004-05-06 23:00:21,843 INFO [org.jboss.deployment.MainDeployer] Deployed package: file:/L:/jboss-3.2.3/server/default/deploy/jms/oil-service.xml
      2004-05-06 23:00:21,921 INFO [org.jboss.deployment.MainDeployer] Starting deployment of package: file:/L:/jboss-3.2.3/server/default/deploy/jms/oil2-service.xml
      2004-05-06 23:00:22,218 INFO [org.jboss.deployment.MainDeployer] Deployed package: file:/L:/jboss-3.2.3/server/default/deploy/jms/oil2-service.xml
      2004-05-06 23:00:22,296 INFO [org.jboss.deployment.MainDeployer] Starting deployment of package: file:/L:/jboss-3.2.3/server/default/deploy/jms/oracle-jdbc2-service.xml
      2004-05-06 23:00:22,718 INFO [org.jboss.mq.server.MessageCache] Started jboss.mq:service=MessageCache
      2004-05-06 23:00:22,796 INFO [org.jboss.deployment.MainDeployer] Deployed package: file:/L:/jboss-3.2.3/server/default/deploy/jms/oracle-jdbc2-service.xml
      2004-05-06 23:00:22,890 INFO [org.jboss.deployment.MainDeployer] Starting deployment of package: file:/L:/jboss-3.2.3/server/default/deploy/jms/rmi-il-service.xml
      2004-05-06 23:00:23,203 INFO [org.jboss.deployment.MainDeployer] Deployed package: file:/L:/jboss-3.2.3/server/default/deploy/jms/rmi-il-service.xml
      2004-05-06 23:00:23,281 INFO [org.jboss.deployment.MainDeployer] Starting deployment of package: file:/L:/jboss-3.2.3/server/default/deploy/jms/uil2-service.xml
      2004-05-06 23:00:23,765 INFO [org.jboss.naming.NamingAlias] Bound link UILConnectionFactory to UIL2ConnectionFactory
      2004-05-06 23:00:23,812 INFO [org.jboss.naming.NamingAlias] Started jboss.mq:service=InvocationLayer,type=UIL
      2004-05-06 23:00:23,859 INFO [org.jboss.naming.NamingAlias] Bound link UILXAConnectionFactory to UIL2XAConnectionFactory
      2004-05-06 23:00:23,906 INFO [org.jboss.naming.NamingAlias] Started jboss.mq:service=InvocationLayer,type=UILXA
      2004-05-06 23:00:23,968 INFO [org.jboss.deployment.MainDeployer] Deployed package: file:/L:/jboss-3.2.3/server/default/deploy/jms/uil2-service.xml
      2004-05-06 23:00:24,062 INFO [org.jboss.deployment.MainDeployer] Starting deployment of package: file:/L:/jboss-3.2.3/server/default/deploy/mail-service.xml
      2004-05-06 23:00:24,687 INFO [org.jboss.mail.MailService] Mail Service bound to java:/Mail
      2004-05-06 23:00:24,734 INFO [org.jboss.mail.MailService] Started jboss:service=Mail
      2004-05-06 23:00:24,796 INFO [org.jboss.deployment.MainDeployer] Deployed package: file:/L:/jboss-3.2.3/server/default/deploy/mail-service.xml
      2004-05-06 23:00:24,875 INFO [org.jboss.deployment.MainDeployer] Starting deployment of package: file:/L:/jboss-3.2.3/server/default/deploy/properties-service.xml
      2004-05-06 23:00:25,140 INFO [org.jboss.varia.property.PropertyEditorManagerService] Started jboss:type=Service,name=PropertyEditorManager
      2004-05-06 23:00:25,187 INFO [org.jboss.varia.property.SystemPropertiesService] Started jboss:type=Service,name=SystemProperties
      2004-05-06 23:00:25,265 INFO [org.jboss.deployment.MainDeployer] Deployed package: file:/L:/jboss-3.2.3/server/default/deploy/properties-service.xml
      2004-05-06 23:00:25,343 INFO [org.jboss.deployment.MainDeployer] Starting deployment of package: file:/L:/jboss-3.2.3/server/default/deploy/schedule-manager-service.xml
      2004-05-06 23:00:25,593 INFO [org.jboss.deployment.MainDeployer] Deployed package: file:/L:/jboss-3.2.3/server/default/deploy/schedule-manager-service.xml
      2004-05-06 23:00:25,671 INFO [org.jboss.deployment.MainDeployer] Starting deployment of package: file:/L:/jboss-3.2.3/server/default/deploy/scheduler-service.xml
      2004-05-06 23:00:25,921 INFO [org.jboss.deployment.MainDeployer] Deployed package: file:/L:/jboss-3.2.3/server/default/deploy/scheduler-service.xml
      2004-05-06 23:00:25,984 INFO [org.jboss.deployment.MainDeployer] Starting deployment of package: file:/L:/jboss-3.2.3/server/default/deploy/sqlexception-service.xml
      2004-05-06 23:00:26,281 INFO [org.jboss.deployment.MainDeployer] Deployed package: file:/L:/jboss-3.2.3/server/default/deploy/sqlexception-service.xml
      2004-05-06 23:00:26,359 INFO [org.jboss.deployment.MainDeployer] Starting deployment of package: file:/L:/jboss-3.2.3/server/default/deploy/transaction-service.xml
      2004-05-06 23:00:26,765 INFO [org.jboss.resource.connectionmanager.CachedConnectionManager] Started jboss.jca:service=CachedConnectionManager
      2004-05-06 23:00:26,843 INFO [org.jboss.security.plugins.JaasSecurityManagerService] Created securityMgr=org.jboss.security.plugins.JaasSecurityManager@4d5575
      2004-05-06 23:00:26,906 INFO [org.jboss.security.plugins.JaasSecurityManagerService] setCachePolicy, c=org.jboss.util.TimedCachePolicy@63a1ae
      2004-05-06 23:00:26,953 INFO [org.jboss.security.plugins.JaasSecurityManagerService] Added JmsXARealm, org.jboss.security.plugins.SecurityDomainContext@10bc995 to map
      2004-05-06 23:00:27,093 INFO [org.jboss.resource.adapter.jms.JmsManagedConnectionFactory.JmsXA] Bound connection factory for resource adapter for ConnectionManager 'jboss.jca:service=TxCM,name=JmsXA to JNDI name 'java:/JmsXA'
      2004-05-06 23:00:27,187 INFO [org.jboss.resource.connectionmanager.TxConnectionManager] Started jboss.jca:service=TxCM,name=JmsXA
      2004-05-06 23:00:27,281 INFO [org.jboss.resource.adapter.jdbc.xa.XAManagedConnectionFactory.DefaultDS] Bound connection factory for resource adapter for ConnectionManager 'jboss.jca:service=XATxCM,name=DefaultDS to JNDI name 'java:/DefaultDS'
      2004-05-06 23:00:27,375 INFO [org.jboss.resource.connectionmanager.TxConnectionManager] Started jboss.jca:service=XATxCM,name=DefaultDS
      2004-05-06 23:00:27,437 INFO [org.jboss.deployment.MainDeployer] Deployed package: file:/L:/jboss-3.2.3/server/default/deploy/transaction-service.xml
      2004-05-06 23:00:27,515 INFO [org.jboss.deployment.MainDeployer] Starting deployment of package: file:/L:/jboss-3.2.3/server/default/deploy/user-service.xml
      2004-05-06 23:00:27,765 INFO [org.jboss.deployment.MainDeployer] Deployed package: file:/L:/jboss-3.2.3/server/default/deploy/user-service.xml
      2004-05-06 23:00:27,828 INFO [org.jboss.deployment.MainDeployer] Starting deployment of package: file:/L:/jboss-3.2.3/server/default/deploy/TextMDB.jar
      2004-05-06 23:00:28,500 INFO [org.jboss.ejb.EjbModule] Deploying TextMDB
      2004-05-06 23:00:28,875 ERROR [org.jboss.ejb.plugins.jms.DLQHandler] Initialization failed
      javax.jms.JMSException: Error creating the dlq connection: XAConnectionFactory not bound
      at org.jboss.ejb.plugins.jms.DLQHandler.createService(DLQHandler.java:169)
      at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:158)
      at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerCreate(JMSContainerInvoker.java:458)
      at org.jboss.ejb.plugins.jms.JMSContainerInvoker.startService(JMSContainerInvoker.java:674)
      at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:192)
      at org.jboss.ejb.MessageDrivenContainer.startService(MessageDrivenContainer.java:234)
      at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:192)
      at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)

      I have gone thru the message archives and i have seen many people have faced this problem but a solution for this problem is nowhere mentioned. I am trying to solve this problem for the last 3 days. I would be very greatful if someone can please help me out of this.

      • 3830 Views
      • Tags: