Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 327295 - Not-serializeable remote exceptions lead to time out
Summary: Not-serializeable remote exceptions lead to time out
Status: CLOSED FIXED
Alias: None
Product: EMF
Classification: Modeling
Component: cdo.net4j (show other bugs)
Version: 4.0   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Eike Stepper CLA
QA Contact: Eike Stepper CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-08 01:46 EDT by Eike Stepper CLA
Modified: 2011-06-23 03:42 EDT (History)
0 users

See Also:

Attachments
Patch v1 - for future reference (5.56 KB, patch)
2010-10-08 01:47 EDT, Eike Stepper CLA 		no flags Details | Diff
View All 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 Eike Stepper CLA 2010-10-08 01:46:44 EDT 
If on the server during indication processing an exception is thrown that carries data elements that are not serializeable, then the following method can not properly finish:

org.eclipse.net4j.signal.RemoteExceptionRequest.requesting(ExtendedDataOutputStream)

That leads to timeouts on the client because the channel is not canceled.
Comment 1 Eike Stepper CLA 2010-10-08 01:47:56 EDT 
Created attachment 180469 [details]
Patch v1 - for future reference
Comment 2 Eike Stepper CLA 2010-10-08 01:48:14 EDT 
Committed to HEAD
Comment 3 Eike Stepper CLA 2011-06-23 03:42:09 EDT 
Available in R20110608-1407