Bug 333610 - "Invalid datagram packet received..." error is reported frequently when you keep the workbench alive but do nothing.
Summary: "Invalid datagram packet received..." error is reported frequently when you ...
Status: RESOLVED FIXED
Alias: None
Product: TCF
Classification: Tools
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux-GTK
: P3 normal (vote)
Target Milestone: 0.4.0   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-05 17:55 EST by Martin Oberhuber CLA
Modified: 2013-06-05 05:54 EDT (History)
1 user (show)

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 Martin Oberhuber CLA 2011-01-05 17:55:44 EST 
CQ:WIND00245807

On Redhat Linux, keep the workbench alive over the whole night and do nothing. 
Lots of errors get reported in the errorlog like this:

Invalid datagram packet received from /128.224.158.97/1534
Comment 1 Eugene Tarassov CLA 2011-01-05 18:28:59 EST 
This supposed to be fixed in revision 988, see
https://bugs.eclipse.org/bugs/show_bug.cgi?id=314876
Comment 2 Martin Oberhuber CLA 2011-01-06 17:17:07 EST 
I think this must be a different issue. The version of TCF used here is
   org.eclipse.tm.tcf.core (0.3.0.201011220947)
so bug 314876 should be fixed in there. I'll send Logs to you offline.
Comment 3 Eugene Tarassov CLA 2011-01-10 16:10:35 EST 
The error message is logged only once per host/port combination per Eclipse session. It is logged when large clock skew is detected between two host. Clock skew can have adverse effects on TCF discovery.

I have changed the discovery code to use time-to-live values instead of absolute timestamps in CONF_SLAVES_INFO packets. This should make the discovery insensitive to clock skew.

The changes are not 100% backward compatible: agents older then revision 1070 7/15/2010 will not be able to discover new agents.

Fixed.