Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[dsdp-tcf-dev] [Bug 309520] New: TCF locator should not report UnknownHostException 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=309520 
Product/Component: Target Management / TCF

           Summary: TCF locator should not report UnknownHostException
    Classification: DSDP
           Product: Target Management
           Version: unspecified
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P3
         Component: TCF
        AssignedTo: dsdp.tm.tcf-inbox@xxxxxxxxxxx
        ReportedBy: uwe.stieber@xxxxxxxxxxxxx
         QAContact: martin.oberhuber@xxxxxxxxxxxxx


Created an attachment (id=165118)
 --> (https://bugs.eclipse.org/bugs/attachment.cgi?id=165118)
Endless UnknownHostExceptions

The locator service should not report execeptions like

!ENTRY org.eclipse.tm.tcf 4 0 2010-04-16 14:38:47.068
!MESSAGE Invalid datagram packet received
!STACK 0
java.net.UnknownHostException: cav_cn56xx: cav_cn56xx
    at java.net.InetAddress.getAllByName0(InetAddress.java:1128)
    at java.net.InetAddress.getAllByName0(InetAddress.java:1098)
    at java.net.InetAddress.getAllByName(InetAddress.java:1061)
    at java.net.InetAddress.getByName(InetAddress.java:958)
    at
org.eclipse.tm.internal.tcf.services.local.LocatorService.handlePeerInfoPacket(LocatorService.java:694)
    at
org.eclipse.tm.internal.tcf.services.local.LocatorService.handleDatagramPacket(LocatorService.java:639)
    at
org.eclipse.tm.internal.tcf.services.local.LocatorService.access$3(LocatorService.java:620)
    at
org.eclipse.tm.internal.tcf.services.local.LocatorService$2$1.run(LocatorService.java:180)
    at org.eclipse.tm.tcf.protocol.Protocol$3.run(Protocol.java:209)
    at org.eclipse.tm.tcf.EventQueue.run(EventQueue.java:100)
    at java.lang.Thread.run(Thread.java:595)

Just ignore them, throw away the packet or something similar. At least there
should be a property where it can be configured to swallow exceptions about
invalid peers in the discovery. This messages are of no use to the user and
just blow up the error log, leading to a very bad user experience and feedback
for the integrating products. See the attached .log for an example.

-- 
Configure bugmail: https://bugs.eclipse.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

Back to the top