Hi Dan,
Your hint was really usefull! (I moved "sleep" after attachment consuming)
Now receive timeout works as it should.
Thanks,
Maciej
dkulp wrote:
>
>
> In your service, is the sleep before or after you "consume" the data from
> the
> MTOM attachments? That's actually an important distinction as the
> client
> would be waiting in a different area.
>
> If it's before consuming the streams from the MTOM, then the client is
> probably waiting on a write operation while streaming the data to the
> server.
> Thus, the receive timeout wouldn't apply.
>
> Looking at URLConnection, I don't see any way to set a timeout on the
> write
> side. :-(
>
> Basically, if the sleep occurs after you read in the entire stream of data
> for
> the mtom attachments, then it SHOULD work as you want.
>
> Dan
>
>
>
> On Wed April 22 2009 8:18:38 am XyLus wrote:
>> Hello All,
>>
>> I'd like to simulate latency in my upload service for test purpose ( I
>> send message using MTOM mechanism).
>>
>> I have just added Thread.sleep(latency) to service implementation method
>> and everything works till I send small request. However when I send 20 MB
>> message then inovcation does not times out, even when server simulate 5
>> minutes latency and client has following configuration:
>>
>> <http:conduit
>> name="{http://x.y.z/uploader}UploadServicePort.http-conduit";>
>>
>> <http:client AutoRedirect="true" ConnectionTimeout="10000"
>> ReceiveTimeout="10000" AllowChunking="false" />
>>
>> </http:conduit>
>>
>>
>> One more thing I've been testing it on my localbox ( client and server
>> are
>> hosted on the same box)
>>
>> Please let me know what should be changed in order to get timeouts for
>> BIG
>> message.
>> I hope it is not a bug in CXF itself.
>>
>>
>> Regards,
>> Maciej
>
> --
> Daniel Kulp
> [email protected]
> http://www.dankulp.com/blog
>
>
--
View this message in context:
http://www.nabble.com/How-to-simulate-service-latency--tp23175136p23251276.html
Sent from the cxf-user mailing list archive at Nabble.com.
