NSIS-ka
A free C++ implementation of NSIS protocols

{5} Assigned, Active Tickets by Owner (Full Description) (2 matches)

List tickets assigned, group by ticket owner. This report demonstrates the use of full-row display.

bless (1 match)

Ticket Summary Component Milestone Type Created
Description
#108 InvalidateRoutingState broken GIST defect Oct 17, 2008

r3544 fixes a minor part of this. The main problem is with the routing table "locking":

2008-10-17 01:17:31.681-4627- EVENT /4: GIST Processing API call received: InvalidateRoutingState msg#97 from NSLPID 1 at API interface address 0
2008-10-17 01:17:31.681-4627- DEBUG /4: GIST Processing InvalidateRoutingState received, carrying out the instructions
2008-10-17 01:17:31.681-4627- DEBUG /4: GIST Processing We are requested to put state to BAD, this means we put it to state DEAD
2008-10-17 01:17:31.682-4627- DEBUG /4: GIST Routing    Iterating over Routing Key table to find the entries we must apply InvalidateRoutingState
2008-10-17 01:17:31.682-4627- DEBUG /4: GIST Routing    Inspecting key
2008-10-17 01:17:31.682-4627- DEBUG /4: GIST Routing    Inspecting key
2008-10-17 01:17:31.682-4627- DEBUG /4: GIST Routing    Found a matching entry, Invalidating Routing State
2008-10-17 01:17:31.682-4627- DEBUG /4: GIST Routing    Routing state must be set to 'BAD', which means killing state
2008-10-17 01:17:31.683-4627- DEBUG /4: GIST Routing    No immediate re-installation is requested, just killing the state
2008-10-17 01:17:31.683-4627**ERROR**2: routingtable::locktable() Mutex Lock failed. Error: Success
2008-10-17 01:17:31.683-4627**ERROR**2: GIST Routing    You should ACQUIRE A LOCK PRIOR TO DELETING an entry!
2008-10-17 01:17:31.683-4627**ERROR**2: routingtable::unlocktable() Mutex Unlock failed. Error: Success

stud-lenk (1 match)

Ticket Summary Component Milestone Type Created
Description
#144 Add handling of NOTIFY PDUs for multicast (Sender-initiated) QoS-NSLP-Multicast task Dec 11, 2009

The QoS-NSLP should handle NOTIFY-PDUs for multicast properly.

Especially the Transient Error "0x08: Path truncated - Next peer dead" should remove the originating peer from the list of successor nodes and call NetworkNotification(bad, SII handle) in order to inform the GIST about the dead peer.

(In this case GIST should remove the specified peer from the list of multicast peers, see ticket #142).


Note: See TracReports for help on using and creating reports.