Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
I
iotivity-classic
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 3,289
    • Issues 3,289
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • IoTivity
  • iotivity-classic
  • Issues
  • #73

Closed
Open
Opened Dec 05, 2014 by Rami Alshafi@ramiOwner

Duplicated discovered resource

(This is on master, due to the date of creating the bug)
The problem was found when tested slow response using simpleclient and simpleserver.
I changed LowQoS to HighQoS for both client and server.
Start server, then start client.
The client found 5 identical resources while there was only one resource in the subnet.
Identical means same URI, same IP and port, same resource types and same interfaces. The resource handles are different.
LowQos client didn't have this issue.
Client log is attached.


JIRA migration meta data

  • JIRA Issue ID: IOT-106
  • Reporter: mytung
  • Assignee: yalmousa
  • Creator: mytung
  • Created at: 2014-12-05T00:04:17.000-0800
  • Found in Version: 12/04/2014
  • Fix in Version: None
  • Issue Severity: Major
  • Reproducibility: Always (100%)
  • Operating System: Ubuntu
  • Hardware/ OEM Platform: None
  • External URL: None
  • Bugzilla ID: None
  • Product: None
  • Status: Closed
  • Components: Build System
  • Priority: P2
  • Due Date: None
  • Issue Type: Bug
    END of JIRA migration meta data

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: iotivity/iotivity-classic#73