Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 357187 - timeout is not adjusted to new blob feature
Summary: timeout is not adjusted to new blob feature
Status: CLOSED FIXED
Alias: None
Product: EMF
Classification: Modeling
Component: cdo.net4j (show other bugs)
Version: 4.2   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Eike Stepper CLA
QA Contact: Eike Stepper CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-09 02:50 EDT by georgehill CLA
Modified: 2013-06-27 03:29 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description georgehill CLA 2011-09-09 02:50:37 EDT 
Build Identifier: 20110615-0604

there is another issue: I had to increase the timeout from 10 to e.g. 200 seconds, otherwise I cannot upload large Blobs since a timeout occurs on server side.  A workaround is to increase this timeout manually using CDOSession.options.setCommitTimeout(200). Solution should be that the timeout is reset on each received TCP packet of the blob data.

Reproducible: Always

Steps to Reproduce:
1. Add a very large blob
2. commit, and you get the error at the end when blob is "successfully" uploaded but the 10 secs default timeout are passed.
Comment 1 Eike Stepper CLA 2012-08-14 22:49:37 EDT 
Moving all open issues to 4.2. Open bugs can be ported to 4.1 maintenance after they've been fixed in master.
Comment 2 Eike Stepper CLA 2012-09-21 03:52:52 EDT 
I think this has been fixed with commit 661d7d2e8bb433cfa71ce43e2a8c63e383930ca7.
Comment 3 Eike Stepper CLA 2013-06-27 03:29:56 EDT 
Available in R20130613-1157 (4.2)