3 Replies Latest reply on Sep 1, 2005 12:48 PM by David

    Problem starting service jboss.jms:alias=QueueConnectionFact

    John Schult Newbie

      I am getting the same thing. I have tried to following configurations:

      OS X 10.4
      JDK 1.5.0_02
      JBoss 4.0.3.RC2

      Fedora Core 4
      JDK 1.5.0_04
      JBoss 4.0.3.RC2

        • 1. Re: Problem starting service jboss.jms:alias=QueueConnection
          John Schult Newbie

          I should also note that this was installed using the JNLP installer and by selecting the ejb3.0 configuration.

          Since then I have installed the EJB 3.0 RC1 with 4.0.2 per the instructions and it works fine on Fedora Core 4 with JDK 5.

          • 2. Re: Problem starting service jboss.jms:alias=QueueConnection
            John Schult Newbie

            I found the problem... and it only seems to happen when you use the JNLP installer. To fix it:


            1. Edit the $JBOSS_HOME/servers/default/deploy/jms/uil2-service.xml file. At the end of the file you will see the following:
             <mbean code="org.jboss.naming.NamingAlias"
             name="jboss.mq:service=InvocationLayer,type=UIL2XA,alias=UIL2XAConnectionFactory">
             <attribute name="FromName">UIL2XAConnectionFactory</attribute>
             <attribute name="ToName">XAConnectionFactory</attribute>
             <depends>jboss:service=Naming</depends>
             </mbean>
            
             <!--
             Two JNDI bindings that act like jms client connections remotely
             but have j2ee defined semantics inside JBoss
             -->
             <mbean code="org.jboss.naming.LinkRefPairService"
             name="jboss.jms:alias=QueueConnectionFactory">
             <attribute name="JndiName">QueueConnectionFactory</attribute>
             <attribute name="RemoteJndiName">ConnectionFactory</attribute>
             <attribute name="LocalJndiName">java:/JmsXA</attribute>
            
             </mbean>
             <mbean code="org.jboss.naming.LinkRefPairService"
             name="jboss.jms:alias=TopicConnectionFactory">
             <attribute name="JndiName">TopicConnectionFactory</attribute>
             <attribute name="RemoteJndiName">ConnectionFactory</attribute>
             <attribute name="LocalJndiName">java:/JmsXA</attribute>
             </mbean>
            

            2. If you notice, the following element is missing from the last two (2) mbean elements.
            <depends>jboss:service=Naming</depends>

            3. Simply add the above element to each mbean element, save the file, and restart JBoss 4.0.3.