Thanks,
Krystian

> -----Original Message-----
> From: Michele Mazzucco [mailto:[EMAIL PROTECTED]
> Sent: 28 April 2008 15:43
> To: [email protected]
> Subject: RE: Axis + Jetty disable chunking
> 
> On Mon, 2008-04-28 at 15:27 +0100, Krystian Szczesny wrote:
> > Hi Michele,
> >
> > I am trying to disable Chunking, so
> > <parameter name="Transfer-Encoding">chunked</parameter>
> > won't help. I've been googling for other values of Transfer-Encoding
> > parameter but found none. From HTTP 1.1 specs I can see that this
> > parameter is for chunking only.
> 
> Indeed by commenting out that line chunking should be disabled.
[Krystian Szczesny]  But client receives chunked response, so it's not
it

> >
> > Where can I set
> > options.setProperty(HTTPConstants.CHUNKED, Boolean.FALSE);
> > ?
> >
> > I've looked through my auto generated stubs and there are no options
> > there.
> 
> Should be something similar to:
> stub.getOptions().setProperty(...)
[Krystian Szczesny]  No there's nothing like that. My methods are called
with xml message as a parameter (OMElement).

> 
> > Correct me if I'm wrong but isn't this for client only?
> 
> Yes, it is.
> http://wso2.org/library/209
> http://wso2.org/library/230
> 
> > Like I've said earlier, I can't change client code.
> 
> Try to check this out
> http://www.mail-archive.com/[email protected]/msg17471.html
> 
> Finally, as last options, you can try this:
> - Let your service implement the Lifecycle interface
> - inside the init(ServiceContext context) method:
> 
>
context.getConfigurationContext.setProperty(HTTPConstants.CHUNKED,Boole
> an.FALSE);
> 
[Krystian Szczesny]  Sorry Michele, but are you serious about that? It
looks a little bit like guessing... I am going to try it, but am very
sceptical...

Thanks anyway

> 
> Michele
> 
> 
> 
> >
> > Best regards,
> > Krystian
> >
> > > -----Original Message-----
> > > From: Michele Mazzucco [mailto:[EMAIL PROTECTED]
> > > Sent: 28 April 2008 15:07
> > > To: [email protected]
> > > Subject: Re: Axis + Jetty disable chunking
> > >
> > > There's another parameter you can set:
> > >
> > > <parameter name="Transfer-Encoding">chunked</parameter>
> > >
> > > You can also enable/disable it at runtime:
> > > options.setProperty(HTTPConstants.CHUNKED, Boolean.FALSE);
> > >
> > > Michele
> > >
> > >
> > > On 28 Apr 2008, at 12:14, Krystian Szczesny wrote:
> > >
> > > > Hi,
> > > >
> > > > I've got an Axis2 1.3 deployed on Jetty 6.1.5.
> > > > I'm having some performance issues with this setup: response is
> > > > chunked and time between the chunks is about 60-70ms[!!!].
> > > > I wanted to disable the chunking so I've set my axis2.xml file
to
> > > > look like this:
> > > >
> > > >     <transportSender name="http"
> > > >
> > > >
> class="org.apache.axis2.transport.http.CommonsHTTPTransportSender">
> > > >         <parameter name="PROTOCOL"
> > locked="true">HTTP/1.0</parameter>
> > > >     </transportSender>
> > > >
> > > >     <transportSender name="https"
> > > >
> > > >
> class="org.apache.axis2.transport.http.CommonsHTTPTransportSender">
> > > >         <parameter name="PROTOCOL"
> > locked="true">HTTP/1.0</parameter>
> > > >     </transportSender>
> > > >
> > > > Unfortunately I am still receiving HTTP/1.1 chunked responses.
> > > >
> > > > Have you got any idea about what to set to disable chunking?
> > > > I am not using Axis2 client so forget about setting the options
> :/
> > > >
> > > > I spoke with folks from Jetty support mailing list and they've
> told
> > > > me, that Jetty will send chunked response if it doesn't know the
> > > > content length at the time of sending the message.
> > > >
> > > > If the settings I've pasted above were working, then I guess
> Jetty
> > > > would receive a full message so it should know the content
> length.
> > > >
> > > > Am I missing something here?
> > > >
> > > > Best regards,
> > > > Krystian
> > > >
> > > > P.s.
> > > > Sorry for the crap below, I can't disable it for external
> messages
> > > >
> > > > --
> > > > Krystian Szczesny
> > > > This e-mail and any attachments are confidential and may also be
> > > > legally
> > > > privileged and/or copyright material of Intec Telecom Systems
PLC
> > > > (or its
> > > > affiliated companies). If you are not an intended or authorised
> > > > recipient
> > > > of this e-mail or have received it in error, please delete it
> > > > immediately
> > > > and notify the sender by e-mail. In such a case, reading,
> > > reproducing,
> > > > printing or further dissemination of this e-mail or its contents
> is
> > > > strictly
> > > > prohibited and may be unlawful.
> > > > Intec Telecom Systems PLC does not represent or warrant that an
> > > > attachment
> > > > hereto is free from computer viruses or other defects. The
> opinions
> > > > expressed in this e-mail and any attachments may be those of the
> > > > author and
> > > > are not necessarily those of Intec Telecom Systems PLC.
> > >
> > >
> > >
-------------------------------------------------------------------
> --
> > > 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]
> >
> 
> 
> ---------------------------------------------------------------------
> 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]

Reply via email to