I was just trying to debug the nodes an I found out the following thing which surprised me:
1. Publish Mechanishm
I have used network Id’s
FileSharingApplication: 126.96.36.199 // Start of Publish
DocumentStored:188.8.131.52 // Place where document is store
ResultMessage: 184.108.40.206 // Notification where it is stored
The question over here is that why is the “resultMessage” always sent to “220.127.116.11”…No matter what? How does the original node which is “18.104.22.168” (specifically in this case informed that it is published).
The problem gets really difficult when I debug lookup mechanism
2. Lookup Mechanism
FileSharingApplication: 22.214.171.124 // Start of Publish
Finds the file : 126.96.36.199 // Place where document is stored just retrieves it
ResultMessage/Store Document: 188.8.131.52 // Retrieves it and stores it
So over here always the document is getting stored on “184.108.40.206” which apparently I think is the localhost. So the problem here is that every lookup mechanism stores the document at this node and just in case in my scenario if I have a cache then there is just 1 cache in the whole network if this is to happen.
Please let me know what exactly is happening..Hoping to hear from you..!
I just checked everything. The used nodes look fine. Perhaps you have used a wrong field in your output, the analyzer gets more than one node as result (everytime for example also the initiator of a lookup). To check it, you can use the SimpleNetLayer, there you have integers as net ids (0, 1, 2, …), so it is easier to have an overview.