1 Reply Latest reply on Dec 28, 2010 8:55 AM by nprasanna

    Quickstart helloworld Problem - JBoss SOA 5

    nprasanna

      Hi,

      I'm new to JBoss SOA. I have successfully installed JBoss SOA 5 (JBoss AS 5.1) in my linux system. But when I try to run the helloworld esb example, I get all the problems.

       

      As said in the getting started guide, I changed the quickstarts/conf/quickstart.properties to include the jboss App server location and configuration name.

       

      After building and deploying it(ant deploy command), I'm unable to execute 'ant runtest' command successfully. It throws the following exceptions

      [echo] Runs Test JMS Sender     [java] Exception in thread "main" javax.naming.CommunicationException: Could not obtain connection to any of these urls: 127.0.0.1:1099 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 /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]]]     [java]    at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1763)     [java]    at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:693)     [java]    at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)     [java]    at javax.naming.InitialContext.lookup(InitialContext.java:392)     [java]    at org.jboss.soa.esb.samples.quickstart.helloworld.test.SendJMSMessage.setupConnection(SendJMSMessage.java:52)     [java]    at org.jboss.soa.esb.samples.quickstart.helloworld.test.SendJMSMessage.main(SendJMSMessage.java:81)     [java] 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]]     [java]    at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:335)     [java]    at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1734)     [java]    ... 5 more     [java] Caused by: javax.naming.ServiceUnavailableException: Failed to connect to server /127.0.0.1:1099 [Root exception is java.net.ConnectException: Connection refused]     [java]    at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:305)     [java]    ... 6 more     [java] Caused by: java.net.ConnectException: Connection refused     [java]    at java.net.PlainSocketImpl.socketConnect(Native Method)     [java]    at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)     [java]    at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)     [java]    at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)     [java]    at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)     [java]    at java.net.Socket.connect(Socket.java:529)     [java]    at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:97)     [java]    at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:82)     [java]    at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:301)     [java]    ... 6 more BUILD FAILED

      Where do I change 127.0.0.1 to the multicast ip address that I want it to be in? I have gone through all the previous similar threads here and tried the suggested solutions like editing jndi.properties, jboss-esb.xml, setting classpath etc.. But none of them work. I'm at a loss as to what is to be done now. Please suggest me a solution

        • 1. Re: Quickstart helloworld Problem - JBoss SOA 5
          nprasanna

          Hello,

          The Problem is somewhat fixed now. I just edited the SendJMSMessage.java(present inside helloworld/quickstart/src folder) file and changed the jndi to the address required and it worked like a charm!

           

          But this doesnt seem to be an elegant solution. Is there a configuration file where I can set the JNDI provider URL?

          1 of 1 people found this helpful