Hi emerson ; Yes , what you have done is correct. Btw you can do that w.o changing the stub as follows; stub._getServiceClient().getOptions().setProperty(org.apache.axis2.context.MessageContextConstants.HTTP_PROTOCOL_VERSION,org.apache.axis2.transport.http.HTTPConstants.HEADER_PROTOCOL_10);
Thanks Deepal > I found out that the problem is the load balances in one of the > servers, which doesn't accept HTTP 1.1. So, inside the stub i added: > > _operationClient.getOptions().setProperty(org.apache.axis2.context.MessageContextConstants.HTTP_PROTOCOL_VERSION,org.apache.axis2.transport.http.HTTPConstants.HEADER_PROTOCOL_10); > > > which made its trick :) > > thanks > emerson > > > On 18/01/07, emerson cargnin <[EMAIL PROTECTED]> wrote: > >> I have a web-service in two servers. One of then works fine from >> java/axis. The other service just gets a time-out. The problem is that >> both work well when I use SoapUI as the client. >> >> I then TCPMon'ed the calls and I found out that axis sent the request >> as chunked": >> >> So i presume one of the servers has its configuration to accept chunks >> and the other not. How can I configure axis to no send in chunks???? >> >> Call from Java Code (Axis) that doesn't work: >> ------------------------------------------------------------------------------------------------------------------------ >> >> POST /services/SapidSetting.asmx HTTP/1.1 >> SOAPAction: "https://x.xxx.com/Services/SapIdSetting/UpdateSapId"; >> User-Agent: Axis2 >> Host: xxx.xxxx.com:1112 >> Transfer-Encoding: chunked >> Content-Type: text/xml; charset=UTF-8 >> >> 203 >> >> <?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope >> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";><soapenv:Header><ns1:authentication >> >> xmlns:ns1="https://x.xxxxx.com/Services/SapIdSetting";><userName>y123</userName><Password>xxx</Password></ns1:authentication></soapenv:Header><soapenv:Body><ns1:UpdateSapId >> >> xmlns:ns1="https://x.xxxx.com/Services/SapIdSetting";><ns1:Input><username>[EMAIL >> >> PROTECTED]</username><SapId>1234</SapId></ns1:Input></ns1:UpdateSapId></soapenv:Body></soapenv:Envelope> >> >> 0 >> -------------------------------------------------------------------------------------------------------------------- >> >> >> >> >> For this request I get only this short answer: >> HTTP/1.1 100 Continue >> >> >> "Transfer-Encoding: chunked" header: >> Chunked Transfer Coding :The chunked encoding modifies the body of a >> message in order to transfer it as a series of chunks, each with its >> own size indicator, followed by an OPTIONAL trailer containing >> entity-header fields. This allows dynamically produced content to be >> transferred along with the information necessary for the recipient to >> verify that it has received the full message. >> >> 100 Continue: The client SHOULD continue with its request. This >> interim response is used to inform the client that the initial part of >> the request has been received and has not yet been rejected by the >> server. The client SHOULD continue by sending the remainder of the >> request or, if the request has already been completed, ignore this >> response. The server MUST send a final response after the request has >> been completed. >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- Thanks, Deepal ................................................................ "The highest tower is built one brick at a time" --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
