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/[email protected]/msg23967.html
 
Thanks, 
 
Nadeem

________________________________

From: Martin Gainty [mailto:[EMAIL PROTECTED] 
Sent: Sunday, November 25, 2007 8:21 PM
To: [email protected]
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: [email protected]
        
        
         
        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: [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
        
        
         
         
         


________________________________

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>  

Reply via email to