Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 24059 - [CVS Core] Problems encountered performing commit: IO Interrupted
Summary: [CVS Core] Problems encountered performing commit: IO Interrupted
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Team (show other bugs)
Version: 2.0.1   Edit
Hardware: PC Windows 2000
: P2 normal (vote)
Target Milestone: 2.1 M2   Edit
Assignee: Michael Valenta CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-09-24 18:49 EDT by IH CLA
Modified: 2002-10-04 10:04 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description IH CLA 2002-09-24 18:49:16 EDT
I selected a folder containing about 1000 jsps in sub-directories.  I rc'ed and
committed the folder.  The progress bar comes up and shows the name of the first
file to be committed.  The bar goes to about 50% and then a message comes up
after a while that says "Problems encountered performing commit.  Reason: IO
Interrupted".

The cvs console says the following:

***
cvs ci -m "#29415 #
localized javascript library" "docroot"
failed due to an internal error (took 1:02.299)
***

The .log file doesn't contain any output during the time period when this error
occurs.  Selecting less and individual files results in commits.
Comment 1 Michael Valenta CLA 2002-09-24 20:08:14 EDT
The I/O interupted exception occurs because the server took longer than 60 
seconds to provide a response (unless you've shorted the timeout value in the 
CVS preferences). I'm not sure why this happened in this particular situation. 
Could you answer the following questions:

- What Eclips version are you using (the version field says 2.0.1. I just want 
to confirm this)?
- What CVS server version are you using?
- What do you mean by "rc'ed"?
- Did you shorten the timeout in the CVS preferences?
- How many changes were there in the 1000 files?
Comment 2 IH CLA 2002-09-25 13:20:21 EDT
Yeah the 60 second timeout was the problem.  We have integration with another
product which monitors the checkin's and it can take a good 17 seconds per
commit and this caused the timeout.  I think a more appropriate error message
like "Your commit timed out, try increasing your cvs timeout value" would be
very helpful.

I am using 2.0.1, cvs server is 1.11.1.1p1 or something close to that.  rc=
right click.
Comment 3 Michael Valenta CLA 2002-09-25 16:35:50 EDT
We should improve this message
Comment 4 Michael Valenta CLA 2002-10-04 10:04:03 EDT
Fix released to HEAD