I'm not sure these properties can be made effective on the client side,
ex, AFAIK, MaxSize is there to block unexpectedly big (multi)parts on
the server side.
Di you know if JAXWS client uses these properties ?
Cheers, Sergey
On 26/08/16 10:11, David Karlsen wrote:
I have the following class:
https://gist.github.com/davidkarlsen/f669b1398a732c8c406e8d5faab2ab3f
Where I set the following props:
setCachedOutputStreamBusProperty( bus, "Threshold", Integer.toString(
1024*2014) ) ;
setCachedOutputStreamBusProperty( bus, "MaxSize", Integer.toString(
1024*1024 ) );
setCachedOutputStreamBusProperty( bus, "OutputDirectory",
SystemUtils.getJavaIoTmpDir().getAbsolutePath() );
HTTPConduit httpConduit = (HTTPConduit) clientConfiguration.getConduit();
httpConduit.getClient().setAllowChunking( false );
httpConduit.getClient().setChunkingThreshold( Integer.MAX_VALUE );
return fsDepot;
}
private void setCachedOutputStreamBusProperty( Bus bus, String property,
String value ) { bus.setProperty( "bus.io.CachedOutputStream." + property,
value ); }
But I still end in a out-of-heap situation.
Is it because I've effectively disabled chunking (the remote party
malfunctions and does not accept the request while using chunking).
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
