|
From: David RR W. \(XML\) <da...@dr...> - 2006-03-17 17:10:08
|
<div>Folks,</div> <div> </div> <div>We've spent this week profiling Hermes 1.0.1 interchanges.</div> <div> </div> <div>If you are sending payloads under 2MB - then everything works well.</div> <div> </div> <div>Transmission and handling times are in a few seconds range.</div> <div> </div> <div>However - for the 20MB payload we have something very strange is </div> <div>happening.</div> <div> </div> <div>Hermes takes only a few seconds to both package the payload, and then inititiate the httpSend, and similarly - when it receives it - just a few seconds to handle the incoming message.</div> <div> </div> <div>In between however - the machine sits there for TWENTY MINUTES - doing nothing of much at all - almost no CPU use, and no disk I/O, little network activity. Eventually the payload crosses over the Apache SOAP interface and is delivered.</div> <div> </div> <div>Using just a plain WSDL SOAP send - then the same payload takes only a minute to transfer.</div> <div> </div> <div>It's almost as if there is some delay timer somewhere?</div> <div> </div> <div>Has anyone experienced this with Hermes / Apache? Is there some parameter to set somewhere to remove this huge delay? Apache or Hermes settings?</div> <div> </div> <div>Can anyone suggest somewhere to look / change to isolate the problem area?</div> <div> </div> <div>We've traced all the execution classes and methods we think make sense - and all seem normal.</div> <div> </div> <div>What are we missing here?</div> <div> </div> <div>Thanks, DW</div> <div> </div> |