Truncated output from executeCommand

Dear all,

I kick off a unix shell script with executeCommand and then capture standard output and error with getInputStream and getStderrInputStream.  Often I find that the output from the script (around 8833 bytes) is truncated; it's as though the channel gets closed once the script completes executing, irrespective of whether data's still waiting on the stream.

I notice that there's an unacknowledged bug describing the problem here:

http://sourceforge.net/tracker/index.php?func=detail&aid=943938&group_id=60894&atid=495562

How are you all dealing with this?  An alternative could be to use startShell, but then how can I judge when to explicitly close the session? 

Cheers,
David


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id396&op=click