Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 333610

Summary:	"Invalid datagram packet received..." error is reported frequently when you keep the workbench alive but do nothing.
Product:	[Tools] TCF	Reporter:	Martin Oberhuber <mober.at+eclipse>
Component:	Core	Assignee:	Project Inbox <tcf.core-inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	eugene
Version:	unspecified
Target Milestone:	0.4.0
Hardware:	PC
OS:	Linux-GTK
Whiteboard:

Description Martin Oberhuber

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

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

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

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.