Bugzilla – Bug 4794
gass_server_ez consumes all cpu when transfering certain files
Last modified: 2006-10-23 11:33:30
You need to
before you can comment on or make changes to this bug.
I've found some text files that cause the gass_server_ez module to eat up all
the available cpu and never complete the transfer. The distinguishing
characteristic apppears to be that the text files have a few 600-character long
lines. When one of those lines spans the 1MB size mark of the file, the server
stops receiving the file, the client hangs, and the server consumes all of the
cpu. The line before the long line is the last thing written to disk. The
server still responds to other transfer requests.
When I break the long lines of these files into lengths shorter than 80
characters, the problem goes away. 12-15MB binary files transfer just fine as
I'm using globus-gass-server and globus-url-copy. Globus 4.0.1 and 4.0.3 show
I will post one of the files that causes the problem.
Bugzilla doesn't like 1MB+ files, apparently. Is there some other way I can
send you the file?
Can you send a link or a program to generate such a test file. Also, are you
using some particular options with the GASS server program?
Here's a link to a file that causes the problem:
Also, the problem only happens if I go local -> remote, like so:
I'm starting globus-gass-server with no command-line arguments.
Created an attachment (id=1095) [details]
New GASS Transfer Package
Attaching an update to the GASS Transfer implementation which I think fixes
That did the trick. The files transfer just fine now.
Committed to trunk and 4.0 branch. Advisory info at