2.2.2.4 RefuseReason Enumeration
The RefuseReason enumeration describes the reason a requested neighbor connection has been denied.
-
<xs:simpleType name="RefuseReason"> <xs:restriction base="xs:string"> <xs:enumeration value="DuplicateNeighbor"> <xs:annotation> <xs:appinfo> <EnumerationValue xmlns="http://schemas.microsoft.com/2003/10/Serialization/">4</EnumerationValue> </xs:appinfo> </xs:annotation> </xs:enumeration> <xs:enumeration value="DuplicateNodeId"> <xs:annotation> <xs:appinfo> <EnumerationValue xmlns="http://schemas.microsoft.com/2003/10/Serialization/">5</EnumerationValue> </xs:appinfo> </xs:annotation> </xs:enumeration> <xs:enumeration value="NodeBusy"> <xs:annotation> <xs:appinfo> <EnumerationValue xmlns="http://schemas.microsoft.com/2003/10/Serialization/">6</EnumerationValue> </xs:appinfo> </xs:annotation> </xs:enumeration> </xs:restriction> </xs:simpleType> <xs:element name="RefuseReason" nillable="true" type="tns:RefuseReason"/>
|
Element |
Description |
|---|---|
|
DuplicateNeighbor |
A connection request by a node is refused because a connection between the two nodes already exists. A connection is deemed duplicate if the GUID part of the listen URI of the PeerNode matches. |
|
DuplicateNodeId |
The responding node already has a connection to a node with the same NodeId as the NodeId given in the corresponding Connect message. |
|
NodeBusy |
The responding node has already connected to the configured maximum number of nodes. |