[ 
https://issues.apache.org/jira/browse/AXIS2C-1535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Lazarski resolved AXIS2C-1535.
-------------------------------------
    Fix Version/s: 2.0.0
                       (was: 1.7.0)
       Resolution: Fixed

Now when a timeout or connection error occurs, the HTTP sender sets status code 
408 (Request Timeout) before returning failure, so clients can detect this via 
axis2_svc_client_get_http_status_code().

> Getting HTTP Status Code as 0 instead of 408
> --------------------------------------------
>
>                 Key: AXIS2C-1535
>                 URL: https://issues.apache.org/jira/browse/AXIS2C-1535
>             Project: Axis2-C
>          Issue Type: Bug
>          Components: core/clientapi
>         Environment: Fedora 12 (kernel version 2.6.31.5-127.fc12.x86_64). gcc 
> version 4.4.2
>            Reporter: Girish Kumar
>            Priority: Major
>             Fix For: 2.0.0
>
>
> I am using WSF CPP 2.1.0 version to build a web service client which I 
> believe is internally build on top of AXIS2C 1.6.0 version. I am observing 
> that Axis is returning HTTP Status Code of web service operation as 0 
> whenever remote Web Server is not reachable or operation times out. It should 
> instead return 408 code in such scenario. Correct status code of 200 is 
> returned for successful operation.
> I am using following code snippet to get the HTTP Status Code.
> MyServiceStub *myService = new MyServiceStub(axis2ClientHomeString, 
> serviceUriString);
> MyInputObject myInput;
> // Setting input parameters here...
> MyFaultObject myFault;
> MyOutputObject *myOutput = myService->MyOperation(&myInput, &myFault);
> int httpStatusCode = axis2_svc_client_get_http_status_code( 
> myService->getServiceClient()->getAxis2SvcClient(), Environment::getEnv());



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to