Over the past several years that this feature has been supported, all web services have returned chunks of 64K or less.  Now suddenly there is one returning 4,193,792 bytes. Since its often difficult to recreate SOAPCALL issues, I added the trace to (DBGLOG) help determine if this is a normal conditiion, and to help pinpoint problems. For instance, say there is a core trying to read a chunk larger than supported by StringBuffer