RE: Axis2 and oc4j deployment
Martin, Unfortunately, the (business) client's target environment uses oc4j 10.1.2, not 10.1.3. I noticed that the axis2 client (and others) were not even getting past the oc4j apache instance. After I disabled chunked encoding, the traffic passed through to the axis2 server and the client worked fine. Our local environments always worked. This may be related to a configuration issue with apache, so if anybody knows if there is something i should look at, I can investigate further. But, of course, you would expect that chucked encoding would be supported by oc4j enterprise out of the box, especially with a fairly recent release. HTTP/1.1, besides the chunked encoding, is working fine. The earlier posting I was referring to is: http://www.mail-archive.com/axis-user@ws.apache.org/msg23967.html Thanks, Nadeem From: Martin Gainty [mailto:[EMAIL PROTECTED] Sent: Sunday, November 25, 2007 8:21 PM To: axis-user@ws.apache.org Subject: RE: Axis2 and oc4j deployment oc4j claims support for for http 1.0 and http 1.1 (in particular chunked encoding) to quote "Only full HTTP/1.0 and HTTP/1.1 requests are generated. HTTP/1.1, HTTP/1.0 and HTTP/0.9 responses are recognized." http://www.oracle.com/technology/tech/java/oc4j/1013/how_to/how-to-httpc lient/doc/how-to-httpclient.html You can look at HTTP-version support by Oracle by querying the response headers http://download-east.oracle.com/docs/cd/A91202_01/901_doc/appdev.901/a89 852/utl_htt2.htm#1012294 Please let us know if this is not true with your installation Thank You Martin Gainty Etats Unis GMT+5 __ Disclaimer and confidentiality note Everything in this e-mail and any attachments relates to the official business of Sender. This transmission is of a confidential nature and Sender does not endorse distribution to any party other than intended recipient. Sender does not necessarily endorse content contained within this transmission. Subject: RE: Axis2 and oc4j deployment Date: Sun, 25 Nov 2007 07:40:46 -0500 From: [EMAIL PROTECTED] To: axis-user@ws.apache.org 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(, 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: axis-user@ws.apache.org 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 You keep typing, we keep giving. Download Messenger and join the i'm Initiative now. Join in! <http://im.live.com/messenger/im/home/?source=CRM_WL_joinnow>
RE: Axis2 and oc4j deployment
oc4j claims support for for http 1.0 and http 1.1 (in particular chunked encoding) to quote "Only full HTTP/1.0 and HTTP/1.1 requests are generated. HTTP/1.1, HTTP/1.0 and HTTP/0.9 responses are recognized." http://www.oracle.com/technology/tech/java/oc4j/1013/how_to/how-to-httpclient/doc/how-to-httpclient.html You can look at HTTP-version support by Oracle by querying the response headers http://download-east.oracle.com/docs/cd/A91202_01/901_doc/appdev.901/a89852/utl_htt2.htm#1012294Please let us know if this is not true with your installation Thank YouMartin GaintyEtats Unis GMT+5__Disclaimer and confidentiality noteEverything in this e-mail and any attachments relates to the official business of Sender. This transmission is of a confidential nature and Sender does not endorse distribution to any party other than intended recipient. Sender does not necessarily endorse content contained within this transmission. Subject: RE: Axis2 and oc4j deploymentDate: Sun, 25 Nov 2007 07:40:46 -0500From: [EMAIL PROTECTED]: axis-user@ws.apache.org 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(, 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 AMTo: [EMAIL PROTECTED]: 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.java:298) at org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:192) at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:77) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:327) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:206) at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:396) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:374) at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.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 _ You keep typing, we keep giving. Download Messenger and join the i’m Initiative now. http://im.live.com/messenger/im/home/?source=TAGLM
RE: Axis2 and oc4j deployment
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: axis-user@ws.apache.org 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
RE: Axis2 and oc4j deployment
The error comes right away, and there is no username/password needed. There were some earlier postings about changing to HTTP/1.0 from 1.1 to fix this problem (something to do with chunking), but that did not fix the problem in this case. -Original Message- From: Dimitris Mouchritsas [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 20, 2007 2:18 PM To: axis-user@ws.apache.org Subject: Re: Axis2 and oc4j deployment Maybe it's blocked from a firewall or something? Does the error come out right away or does it wait first? Also, if the web application requires some security then you might need to provide your credentials first (e.g. principal & password). You can view the wsdl before logging in the application? On Nov 20, 2007 9:46 AM, Hoda, Nadeem [USA] <[EMAIL PROTECTED]> wrote: > > > > 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.j > ava:298) > at > org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java > :192) at > org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:77) > at > org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessag > eWithCommons(CommonsHTTPTransportSender.java:327) > at > org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(Comm > onsHTTPTransportSender.java:206) at > org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:396) > at > org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOp > eration.java:374) > at > org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutI > nAxisOperation.java:211) > at > org.apache.axis2.client.OperationClient.execute(OperationClient.java:1 > 63) > > 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 > > > > > -- Dimitris Mouchritsas Computer Services - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2 and oc4j deployment
Maybe it's blocked from a firewall or something? Does the error come out right away or does it wait first? Also, if the web application requires some security then you might need to provide your credentials first (e.g. principal & password). You can view the wsdl before logging in the application? On Nov 20, 2007 9:46 AM, Hoda, Nadeem [USA] <[EMAIL PROTECTED]> wrote: > > > > 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.java:298) > at > org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:192) > at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:77) > at > org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:327) > at > org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:206) > at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:396) > at > org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:374) > at > org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.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 > > > > > -- Dimitris Mouchritsas Computer Services - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]