9 Replies Latest reply on Dec 1, 2008 6:50 AM by kconner

    Binding an address causes error

      Hi everyone,

      I have the following problem. When I launch JBossESB with --host= command line switch, my ESB project fails to load with

      ERROR [URLDeploymentScanner] Incomplete Deployment listing:
      
      --- MBeans waiting for other MBeans ---
      ObjectName: jboss.esb:deployment=StaticDataService.esb
       State: FAILED
      
      --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
      ObjectName: jboss.esb:deployment=StaticDataService.esb
       State: FAILED


      Everything works just fine when no switches are supplied. What could be wrong?

        • 1. Re: Binding an address causes error
          kconner

          No idea, what is in the logs? What is the reason for the failure?

          • 2. Re: Binding an address causes error

            This is what I found in the server log:

            Reason: org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleException: Unexpected naming context exception from prepareMessageReceiver

            What's that? :)

            • 3. Re: Binding an address causes error
              kconner

              It's an unexpected naming context exception from prepareMessageReceiver of course ;)

              Are you saying that this is all that is in the logs and that there is no further information? What is the real reason for the failure?

              If you want a very wild guess then you have something that is explicitly specifying its JNDI context to 127.0.0.1 and that this is no longer available now that you have bound it to another port. Of course this is just a wild guess and may not be correct.

              It may also help if you can tell us what version of the software you are running, just in case it is relevant.

              • 4. Re: Binding an address causes error

                OK, OK, I get it.

                The further study of the logs revealed to me that there had been

                javax.naming.CommunicationException: Failed to connect to server localhost:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server localhost:1099 [Root exception is java.net.ConnectException: Connection refused: connect]]


                But can you tell me the difference between a locally running JBoss and the one bound to a certain IP/hostname? I swear there are no applications using the port in question. There is no firewall either.

                The JBoss version is 4.2.1. :)

                • 5. Re: Binding an address causes error

                  The error is reproducible on different computers. I'm tempted to think that there's something in configuration files that holds the keys to the solution but I still have no idea.

                  • 6. Re: Binding an address causes error
                    kconner

                    If you are using ESB 4.2.1 then it does not have support for properties and, therefore, will not work with -b.

                    This was addressed in https://jira.jboss.org/jira/browse/JBESB-1309 nearly a year ago.

                    Can you update to a later version?

                    • 7. Re: Binding an address causes error
                      kconner

                      You should also look for any references to localhost in your jboss-esb.xml files.

                      In general you should not be specifying the JNDI parameters so that they can default to those used by the current server, that is unless you are deliberately referencing a remote JNDI server :)

                      • 8. Re: Binding an address causes error

                        The issue is successfully resolved. :) It was all about configuration files where localhost was specified everywhere.

                        Sorry to have disturbed you, lads.

                        • 9. Re: Binding an address causes error
                          kconner

                           

                          "hiningenteki" wrote:
                          Sorry to have disturbed you, lads.

                          No problems, thanks for letting us know that it is resolved.