ChaincodeServer grpc.max_receive_message_length and grpc.max_send_message_length arguments

[alexanderlamb]

I'm having trouble passing grpc.max_receive_message_length and grpc.max_send_message_length arguments into a chaincode instance running as a server.

I've tried adding them to the cli command but haven't had any luck:
./src/chaincode.js --peer.address=0.0.0.0:9999 --grpc.max_receive_message_length=104857600 --grpc.max_send_message_length=104857600

I was wonder if someone could confirm that this functionality has been implemented yet, or if there's an alternative way to pass these values.

[jcastrence]

Assuming this isn't a fabric-samples chaincode, is there anywhere else in the chaincode that might overwrite the grpc message length variables?

[mbwhite]

Hello @alexanderlamb

Firstly - could briefly describe what problem you ran into that means you need to up this limit? Where you sending a transaction function with a large payload?

Java Chaincode does seem to have these options available - it defaults to 100Mb for max-message-size.
This does need setting both sides I believe (based on grpc documentation).

Node chaincode has this missing I believe.

[alexanderlamb]

Hello @alexanderlamb

Firstly - could briefly describe what problem you ran into that means you need to up this limit? Where you sending a transaction function with a large payload?

Java Chaincode does seem to have these options available - it defaults to 100Mb for max-message-size. This does need setting both sides I believe (based on grpc documentation).

Node chaincode has this missing I believe.

Hi @mbwhite,

Our payload size can become quite large yes. We're easily bumping up against the limit as it currently stands. As a temporary fix, we've forked this repo and bumped up the limit to 100Mb and can confirm its working.

Also, this may be a separate conversation, but this issue was discovered when stream.cancel() was being called when it no longer existed.

fabric-chaincode-node/libraries/fabric-shim/lib/handler.js

Line 372 in 671a544

stream.cancel();

2022-03-29T18:50:25.937Z error [c-api:_]                                          uncaughtException: stream.cancel is not a function
TypeError: stream.cancel is not a function
    at ServerDuplexStreamImpl.<anonymous> (/home/node/app/node_modules/@arise-travel/fabric-shim/lib/handler.js:372:20)
    at ServerDuplexStreamImpl.emit (node:events:394:28)
    at ServerDuplexStreamImpl.emit (node:domain:475:12)
    at endReadableNT (node:internal/streams/readable:1331:12)
    at processTicksAndRejections (node:internal/process/task_queues:83:21) 

[denyeart]

Fixed in node chaincode v2.5.4, the grpc parameters passed at chaincode startup will now be honored.