Upon digging deeper, looks like oc4j's apache instance (10.1.2 enterprise deployment) does not accept "chunked" requests, so the following addition to the client code: stub._getServiceClient().getOptions(). setProperty(org.apache.axis2.transport.http.HTTPConstants.CHUNKED, Boolean.FALSE);
fixed the problem. There were earlier posts stating that changing to HTTP/1.0 from HTTP/1.1 would fix this problem, but that did not work in our case. Thanks, Nadeem ________________________________ From: Hoda, Nadeem [USA] [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 20, 2007 11:46 AM To: [email protected] Subject: Axis2 and oc4j deployment Folks, We are deploying our Axis2 services on oc4j 1012 (simplest service possible, based on /samples/quickstart [code first]). Locally (even if we access from a different machine), the services work pefectly, but the "dev" environment deployment is failing with the following error (via Axis2 client): org.apache.axis2.AxisFault: Transport error: 503 Error: Service Unavailable at org.apache.axis2.transport.http.HTTPSender.handleResponse(HTTPSender.jav a:298) at org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:1 92) at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:77) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageW ithCommons(CommonsHTTPTransportSender.java:327) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(Common sHTTPTransportSender.java:206) at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:396) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOper ation.java:374) at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInA xisOperation.java:211) at org.apache.axis2.client.OperationClient.execute(OperationClient.java:163 ) The WSDL is easily assessible through the browser, so the port, etc, are correct. I have tried multiple web service clients, and they all fail. Can anyone provide guidance? Thanks, Nadeem
