Re: peer discovery/collection errors when calling chaincode from nodejs client


Simeon MacMillen
 

Hi Mark,

Thank you for your response and for your helpful direction!  The explicit designation of endorsing peer at transaction submit was exactly what I was looking for.  After adapting this, I was able to successfully resolve the write transactions through the Dockerized client.

Sincerely,
Simeon MacMillen

On 3/25/21 2:42 PM, Mark Lewis wrote:
You might need to set some discovery interests for the private data collections you are using. See the "using chaincode to chaincode calls and collections" section on this page for details:

https://hyperledger.github.io/fabric-sdk-node/release-2.2/tutorial-discovery-fabric-network.html

You can also explicitly specify the endorsing organizations to use for a given transaction submit:

https://hyperledger.github.io/fabric-sdk-node/release-2.2/module-fabric-network.Transaction.html#setEndorsingOrganizations

Join fabric@lists.hyperledger.org to automatically receive all group messages.