2 Replies Latest reply on May 29, 2009 3:17 PM by Alex Dorandish

    ESB WS is causing connection refuse when a remote WS client

    Alex Dorandish Newbie

      I have two Virtual Machines.

      * VM(1): ESB 4.5 with JRE 1.6
      * VM(2): JBoss Application Server 5.0 with JRE 1.6

      I have created a WS that natively talks to an ESB service and deployed it on ESB 4.5. It works perfectly fine when my WS client is on the same machine as ESB is on (VM(1))

      The moment I move that client to my VM(2) and deploy it to JBoss Application Server 5.0 it throws connection refuse.

      Then to make sure this does not have anything to do with my code I installed the sample WS wrapper which says Hello and Adios from the samples on my ESB 4.5.

      I get the same error.

      Here is the error message:

      com.sun.xml.ws.client.ClientTransportException: HTTP transport error: java.net.ConnectException: Connection refused
       at com.sun.xml.ws.transport.http.client.HttpClientTransport.getOutput(HttpClientTransport.java:131)
       at com.sun.xml.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:151)
       at com.sun.xml.ws.transport.http.client.HttpTransportPipe.processRequest(HttpTransportPipe.java:93)
       at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:598)
       at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:557)
       at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:542)
       at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:439)
       at com.sun.xml.ws.client.Stub.process(Stub.java:222)
       at com.sun.xml.ws.client.sei.SEIStub.doProcess(SEIStub.java:135)
       at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:109)
       at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:89)
       at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:118)
       at $Proxy30.sayGoodbye(Unknown Source)
       at _testapp.Main.main(Main.java:27)
      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.Socket.connect(Socket.java:520)
       at java.net.Socket.connect(Socket.java:470)
       at sun.net.NetworkClient.doConnect(NetworkClient.java:157)
       at sun.net.www.http.HttpClient.openServer(HttpClient.java:388)
       at sun.net.www.http.HttpClient.openServer(HttpClient.java:523)
       at sun.net.www.http.HttpClient.<init>(HttpClient.java:231)
       at sun.net.www.http.HttpClient.New(HttpClient.java:304)
       at sun.net.www.http.HttpClient.New(HttpClient.java:321)
       at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:813)
       at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:792)
       at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:690)
       at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:857)
       at com.sun.xml.ws.transport.http.client.HttpClientTransport.getOutput(HttpClientTransport.java:119)


      * There are no firewalls active
      * There are no network access restrictions

      The I deployed a regular web service to the ESB as web app and I can successfully call it. Weird, eh?

      What seems to be the problem?