1 Reply Latest reply on Mar 3, 2009 5:11 AM by Kevin Conner

    management.esb is binding at 127.0.0.1

    Eric Cartman Newbie


      Hi,

      I'm running Jboss at a specific IP with "run.sh -b myip"

      I've replaced jboss.esb.bind.address witth jboss.bind.address.

      I'm still receiveing exceptions from management.esb, whose binding at 127.0.0.1.

      Example

      Caused by: javax.naming.CommunicationException: Failed to connect to server 127.0.0.1:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server 127.0.0.1:1099 [Root exception is java.net.ConnectException: Connection refused]]
       at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:274)
       at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1533)
       ... 27 more
      Caused by: javax.naming.ServiceUnavailableException: Failed to connect to server 127.0.0.1:1099 [Root exception is java.net.ConnectException: Connection refused]
       at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:248)
       ... 28 more
      Caused by: java.net.ConnectException: Connection refused
       at java.net.PlainSocketImpl.socketConnect(Native Method)
       at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
       at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
       at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
       at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
       at java.net.Socket.connect(Socket.java:520)
       at java.net.Socket.connect(Socket.java:470)
       at java.net.Socket.<init>(Socket.java:367)
       at java.net.Socket.<init>(Socket.java:267)
       at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:84)
       at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:77)
       at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:244)
       ... 28 more
      


      org.jboss.soa.esb.couriers.CourierServiceBindException: Failed to get JMS Session from pool.
       at org.jboss.internal.soa.esb.couriers.JmsCourier.getJmsSession(JmsCourier.java:164)
       at org.jboss.internal.soa.esb.couriers.JmsCourier.createMessageProducer(JmsCourier.java:332)
       at org.jboss.internal.soa.esb.couriers.JmsCourier.deliver(JmsCourier.java:188)
       at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.deliver(TwoWayCourierImpl.java:189)
       at org.jboss.soa.esb.monitoring.client.DataCollectorAction.collectStatistics(DataCollectorAction.java:91)
       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
       at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
       at java.lang.reflect.Method.invoke(Method.java:585)
       at org.jboss.soa.esb.listeners.message.ActionProcessorMethodInfo.processMethods(ActionProcessorMethodInfo.java:102)
       at org.jboss.soa.esb.listeners.message.OverriddenActionLifecycleProcessor.process(OverriddenActionLifecycleProcessor.java:74)
       at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:633)
       at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:585)
       at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:419)
       at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:548)
       at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
       at java.lang.Thread.run(Thread.java:595)
      Caused by: org.jboss.internal.soa.esb.rosetta.pooling.ConnectionException: Unexpected exception accessing Naming Context
       at org.jboss.internal.soa.esb.rosetta.pooling.JmsConnectionPool.getSession(JmsConnectionPool.java:216)
       at org.jboss.internal.soa.esb.couriers.JmsCourier.getJmsSession(JmsCourier.java:158)
       ... 17 more
      Caused by: org.jboss.soa.esb.helpers.NamingContextException: Failed to create Naming Context
       at org.jboss.soa.esb.helpers.NamingContextPool.createContext(NamingContextPool.java:365)
       at org.jboss.soa.esb.helpers.NamingContextPool.getContext(NamingContextPool.java:304)
       at org.jboss.soa.esb.helpers.NamingContextPool.getContext(NamingContextPool.java:159)
       at org.jboss.soa.esb.helpers.NamingContextPool.getNamingContext(NamingContextPool.java:410)
       at org.jboss.internal.soa.esb.rosetta.pooling.JmsConnectionPool.initConnection(JmsConnectionPool.java:498)
       at org.jboss.internal.soa.esb.rosetta.pooling.JmsConnectionPool.getSession(JmsConnectionPool.java:214)
       ... 18 more
      



      Why ????


      Thanks,
      Eric