Hi Eugene,
Thanks for your consideration. Looking at this traceback from the 1st of the errors reported:
Exception:
java.io.IOException: Network is down
at java.net.PlainDatagramSocketImpl.send(PlainDatagramSocketImpl.java:-2)
at java.net.DatagramSocket.send(DatagramSocket.java:676)
at org.eclipse.tcf.internal.services.local.LocatorService.sendDatagramPacket(LocatorService.java:771)
at org.eclipse.tcf.internal.services.local.LocatorService.sendEmptyPacket(LocatorService.java:889)
at org.eclipse.tcf.internal.services.local.LocatorService.sendAll(LocatorService.java:899)
at org.eclipse.tcf.internal.services.local.LocatorService.refresh_timer(LocatorService.java:560)
In some sense you are right, the external network is down. On the other hand, isn’t it the purpose of LocatorService and its refreshTimer to detect changes in network and peer availability?
So I would have expected exceptions to be caught and processed by TCF internally (eg marking the respective network as unavailable), rather than exposing them in the error log … am I wrong on these assumptions ?
Martin Oberhuber, SMTS / Product Owner – Development Tools, Wind
River
From:
<tcf-dev-bounces@xxxxxxxxxxx> on behalf of "eugene.tarassov@xxxxxxxxxx" <eugene.tarassov@xxxxxxxxxx>
Reply-To: TCF Development <tcf-dev@xxxxxxxxxxx>
Date: Monday 15 May 2017 at 20:25
To: TCF Development <tcf-dev@xxxxxxxxxxx>
Subject: Re: [tcf-dev] FW: [aeri] Weekly Problem Digest for Target Communication Framework
Hi Martin,
There is not enough data to tell what’s going on with these errors.
Most probably, they are just side effects of some external problems, like network errors.
Regards,
Eugene
From: tcf-dev-bounces@xxxxxxxxxxx [mailto:tcf-dev-bounces@xxxxxxxxxxx]
On Behalf Of Oberhuber, Martin
Sent: Monday, May 15, 2017 12:45 AM
To: TCF Development
Subject: [tcf-dev] FW: [aeri] Weekly Problem Digest for Target Communication Framework
Hi TCF committers,
The exceptions shown below are logged into the user’s error log, and can cause user confusion (because the error reporter may kick in). Can we fix some of these for the upcoming 1.5 Oxygen
release? Can we at least track them with Bugzilla’s where we document what’s going on?
Martin Oberhuber, SMTS / Product Owner – Development Tools, Wind
River
New problems reported last week
Congrats, no problems in this section!
Active problems last month
Problem Resolution Statistics
Problem Resolutions
|
Count
|
AUTO_CLOSED:
|
7
|
FIXED:
|
2
|
UNRESOLVED:
|
33
|
To remove a problem from this report, visit its web page and set its resolution to something else than 'unresolved'.
Your friendly error-reports-bot
--
You are receiving this email because you are subscribed to digest of Target Communication Framework. To alter your subscriptions, contact your administrator.
Do you develop Eclipse plug-ins yourself? Get your personal error reporting server
for free!
This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy,
or forward this email message or any attachments. Delete this email message and any attachments immediately.