1 Reply Latest reply on Sep 9, 2009 6:10 PM by Gerald Turner

    http proxy error profile

    Sidney Zurch Novice

      Does this error profile suggest anything to anyone?

      The program sets endpoints dynamically and works correctly with two of four endpoints. The trace below is from one of the endpoints that fails.

      I don't recall seeing the "Squid" message on the endpoints that work. It appears that the client fails immediately without waiting for a response from the service.

      This is the latest JBossWS native stack installed in jboss-4.2.3.GA.

      16:45:16,158 TRACE SOAPMessageUnMarshallerHTTP:62 - Read input tream with metadata={Proxy-Connection=[close], Date=[Sun, 26 Apr 2009 20:44:35 GMT], Content-Type=[text/html], NoThrowOnError=true, ResponseCode=501, Content-Length=[1206], Expires=[Sun, 26 Apr 2009 20:44:35 GMT], ResponseCodeMessage=Not Implemented, X-Cache-Lookup=[NONE from [default_router]:3128], X-Squid-Error=[ERR_UNSUP_REQ 0], HEADER={SOAPAction="http://[service_Qname]", Content-Type=text/xml; charset=UTF-8}, Server=[squid/2.5.STABLE9], Mime-Version=[1.0], X-Cache=[MISS from [default_router]]}
      16:45:16,174 ERROR CommonClient:404 - Exception caught while preparing for) performing the invocation:
      java.io.IOException: Could not transmit message
       at org.jboss.ws.core.client.HTTPRemotingConnection.invoke(HTTPRemotingConnection.java:265)
       at org.jboss.ws.core.client.SOAPProtocolConnectionHTTP.invoke(SOAPProtocolConnectionHTTP.java:71)
       at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:340)
       at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:290)
       at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:170)
       at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150)
       at $Proxy26.quote(Unknown Source)
       at [test_op]([test_program].java:386)
       at ...
      Caused by: org.jboss.remoting.CannotConnectException: Can not connect http client invoker. Invalid HTTP server response [501] - Not Implemented. Response: Not Implemented/501.
       at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:348)
       at org.jboss.remoting.transport.http.HTTPClientInvoker.transport(HTTPClientInvoker.java:137)
       at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
       at org.jboss.remoting.Client.invoke(Client.java:1634)
       at org.jboss.remoting.Client.invoke(Client.java:548)
       at org.jboss.ws.core.client.HTTPRemotingConnection.invoke(HTTPRemotingConnection.java:243)
       ... 9 more
      Caused by: org.jboss.ws.WSException: Invalid HTTP server response [501] - Not Implemented
       at org.jboss.ws.core.soap.SOAPMessageUnMarshallerHTTP.read(SOAPMessageUnMarshallerHTTP.java:75)
       at org.jboss.remoting.transport.http.HTTPClientInvoker.readResponse(HTTPClientInvoker.java:518)
       at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:307)
       ... 14 more
      16:45:16,177 DEBUG MessageContextJAXWS:106 - Begin response processing