2 Replies Latest reply on Feb 25, 2010 11:03 AM by Andreas Sander

    ConnectException when deploying to non-clustered server

    Andreas Sander Newbie

      Hello,

       

      I have two installations of JBoss 4.2.2GA. One of the installation is clustered and the other is not. Both installations startup without any error messages if no application is deployed. If I deploy my application to the clustered installation, everything works fine. If I try to deploy the same ear file to the non clustered application, I get this error message:

       

      2010-02-25 11:05:35,125 INFO  [org.jboss.ejb3.EJBContainer] STARTED EJB: de.mycompany.Myproject.bf.alarm.MDBAlarm ejbName: MDBAlarm
      2010-02-25 11:05:41,187 WARN  [org.jboss.ejb3.mdb.MessagingContainer] Could not find the queue destination-jndi-name=queue/MyProjectAlarmQueue
      2010-02-25 11:05:47,359 WARN  [org.jboss.ejb3.mdb.MessagingContainer] destination not found: queue/MyProjectAlarmQueue reason: javax.naming.CommunicationException: Could not obtain connection to any of these urls: 0.0.0.0:1100 and discovery failed with error: javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out] [Root exception is javax.naming.CommunicationException: Failed to connect to server 0.0.0.0:1100 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server 0.0.0.0:1100 [Root exception is java.net.ConnectException: Connection refused: connect]]]
      2010-02-25 11:05:47,359 WARN  [org.jboss.ejb3.mdb.MessagingContainer] creating a new temporary destination: queue/MyProjectAlarmQueue
      2010-02-25 11:05:47,375 WARN  [org.jboss.system.ServiceController] Problem starting service jboss.j2ee:ear=MyProject.ear,jar=MyProjectEJB.jar,name=MDBAlarm,service=EJB3
      javax.management.InstanceNotFoundException: jboss.mq:service=DestinationManager is not registered.
          at org.jboss.mx.server.registry.BasicMBeanRegistry.get(BasicMBeanRegistry.java:523)
          at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:653)
          at org.jboss.ejb3.JmxClientKernelAbstraction.invoke(JmxClientKernelAbstraction.java:44)
          at org.jboss.ejb3.jms.DestinationManagerJMSDestinationFactory.createDestination(DestinationManagerJMSDestinationFactory.java:75)
          at org.jboss.ejb3.mdb.MessagingContainer.createTemporaryDestination(MessagingContainer.java:573)

       

       

       

      It seems that there is a configuration error in the non clustered JBoss server but I have not clue where to search for it.

       

      I would be glad for any hint.

       

      Regards

      Andreas

        • 1. Re: ConnectException when deploying to non-clustered server
          jaikiran pai Master

          asander wrote:

           

          queue/MyProjectAlarmQueue reason: javax.naming.CommunicationException: Could not obtain connection to any of these urls: 0.0.0.0:1100 and discovery failed with error: javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out] [Root exception is javax.naming.CommunicationException: Failed to connect to server 0.0.0.0:1100 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server 0.0.0.0:1100 [Root exception is java.net.ConnectException: Connection refused: connect]]]
          2010-02-25 11:05:47,359 WARN  [org.jboss.ejb3.mdb.MessagingContainer] creating a new temporary destination: queue/MyProjectAlarmQueue

          Are you packaging any jndi.properties file in your application?

          • 2. Re: ConnectException when deploying to non-clustered server
            Andreas Sander Newbie

            jaikiran schrieb:

             

             

            Are you packaging any jndi.properties file in your application?


            No, there is no jndi.properties file in the application.