Re: Error: could not assemble transaction: ProposalResponsePayloads do not match


Kimheng SOK
 

I got this error often, the reason is all the peer node execute their own chaincode individually and even if the result is successful, it doesn't means that all the payload are the same. By looking at the payload we can see that the output from different peer are different. So to solve the problem is to find the root cause inside our chaincode that make the different output. Normally I try to print the output step by step to see where there is the problem and solve it.

I used Nodejs chaincode, so console.log and console.info is what help me to see the inequality of the output, and then using docker logs ChaincodeContainerID to view the output.

On Wed, Jan 29, 2020 at 1:29 AM Siddharth Jain <siddjain@...> wrote:
could anyone point us to the code where the response payload is generated? is there any doc explaining what the response payload is? its a byte array but what does it contain?


From: Siddharth Jain <siddjain@...>
Sent: Monday, January 27, 2020 5:17 PM
To: fabric@... <fabric@...>
Subject: Error: could not assemble transaction: ProposalResponsePayloads do not match
 
we get this error when trying to invoke the chaincode on a network of 3 peers. However, we have verified if we invoke the chaincode individually on the peer nodes, all of them respond with Chaincode invoke successful. result: status:200. does anyone have any idea what could be wrong here?

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