4 Replies Latest reply on Jun 7, 2004 6:21 AM by minouche

    JMSException when starting JBoss server...

    helly15

      Hello everybody,

      I have a problem with Messagedrivenbeans: I included MDB in my application
      that is running on a JBoss Server. It is working fine on my local server,
      and also on some of my collegues machines it is working fine. But on some
      of my collegues machines the following exceptions are thrown when they
      start up the JBoss server on their machines:

      09:48:08,734 INFO [StatelessSessionContainer] Starting
      09:48:08,796 INFO [StatelessSessionInstancePool] Starting
      09:48:08,796 INFO [StatelessSessionInstancePool] Started
      09:48:08,796 INFO [StatelessSessionContainer] Started
      09:48:08,796 INFO [MessageDrivenContainer] Starting
      09:48:08,812 INFO [JMSContainerInvoker] Starting
      09:48:08,812 INFO [DLQHandler] Creating
      09:48:08,812 ERROR [DLQHandler] Initialization failed
      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:579)
      at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:192)
      at org.jboss.ejb.MessageDrivenContainer.startService(MessageDrivenContainer.java:220)
      at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:192)
      at sun.reflect.GeneratedMethodAccessor7.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:549)
      at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:966)
      at $Proxy11.start(Unknown Source)
      at org.jboss.system.ServiceController.start(ServiceController.java:392)
      at sun.reflect.GeneratedMethodAccessor6.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:549)
      at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
      at $Proxy28.start(Unknown Source)



      Can anybody tell me, what could be the cause for the exception? I compared my
      JBoss configuration files (jboss-service.xml, jbossmq-service.xml,
      jbossmq-destinations-service.xml, jms-ds.xml, jbossmq-service.xml) with
      theirs, and i have found no differences.


      Thank you in advance,
      best regards,
      Felix

        • 1. Re: JMSException when starting JBoss server...

          FAQ

          • 2. Re: JMSException when starting JBoss server...
            helly15

            Hello fellow developpers,

            today, I found out what the reason for the messagedrivenbean problem was,
            that I had: on those machines that had problems when they tried to start
            jboss, they had deleted the hsqldb-ds.xml file (which configures access to
            the hypersonic database that jboss uses to keep jms related data).

            allthough this problem is solved, i am worried now about the hypersonic database in my application. someone warned me, that this db is very unreliable and should never be used in a production application. i will have about 50-70 users using my application concurrently.
            do you think the hypersonic database will work ok under this load?

            have a nice day,
            regards,
            felix

            • 3. Re: JMSException when starting JBoss server...

              HSQL is more a 'demo' database. I won't suggest you to use it with that amount of users.

              Regards,

              Stephane

              • 4. Re: JMSException when starting JBoss server...

                I had XAConnectionFactory not bound Error while starting JBOSS and i found what was the problem :

                In hsqldb-ds.xml, i had put a different JNDI name than "DefaultDS" for hsql database.

                So i went back to "DefaultDS" JNDI name and it works now!

                Hope this will help