Fabric-node-sdk 1 2 with Fabric 1 1

0 votes

I am using Fabric-node-sdk with Fabric 1.1 but I get this error:

[2018-08-01 11:48:41.498] [DEBUG] Helper - [NetworkConfig101.js]: _addPeersToChannel - peer1.org2.example.com - grpcs://x.x.x.x:8056

    [2018-08-01 11:48:41.498] [DEBUG] Helper - [NetworkConfig101.js]: getOrderer - name orderer.example.com

    [2018-08-01 11:48:41.504] [DEBUG] Helper - [crypto_ecdsa_aes]: ecdsa signature:  Signature {

      r: <BN: 18641b0400ca8526210ae69af03db05877e3e6a1109bcbae94b716259a973b11>,

      s: <BN: 6c4d65ef6d4088975f2d145b93c1420d5e15866da96733b213e3d699f0c9e2a9>,

      recoveryParam: 1 }

    [2018-08-01 11:48:41.569] [ERROR] Create-Channel - Error: 8 RESOURCE_EXHAUSTED: Sent message larger than max (2241 vs. 15)

        at createStatusError (D:\dev\hyperledger\fabric-samples-sdk\fabric-sdk-util\node_modules\fabric-client\node_modules\grpc\src\client.js:64:15)

        at ClientDuplexStream._emitStatusIfDone (D:\dev\hyperledger\fabric-samples-sdk\fabric-sdk-util\node_modules\fabric-client\node_modules\grpc\src\client.js:270:19)

        at ClientDuplexStream._readsDone (D:\dev\hyperledger\fabric-samples-sdk\fabric-sdk-util\node_modules\fabric-client\node_modules\grpc\src\client.js:236:8)

        at readCallback (D:\dev\hyperledger\fabric-samples-sdk\fabric-sdk-util\node_modules\fabric-client\node_modules\grpc\src\client.js:296:12)

    (node:1552) UnhandledPromiseRejectionWarning: Error: Failed to initialize the channel: Error: 8 RESOURCE_EXHAUSTED: Sent message larger than max (2241 vs. 15)

        at Object.createChannel (D:\dev\hyperledger\fabric-samples-sdk\fabric-sdk-util\sdk-util\create-channel.js:66:9)

        at <anonymous>

    (node:1552) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)

    (node:1552) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
Aug 10, 2018 in Blockchain by digger
• 26,740 points
879 views

1 answer to this question.

0 votes

The line

 grpc-max-send-message-length: 15

is used to load connection config. So delete this line and your error should be gone.

answered Aug 10, 2018 by slayer
• 29,370 points

Related Questions In Blockchain

0 votes
1 answer

Not Able to register a user with Hyperledger-Fabric v1.1 preview

The error: "Certificate not found with AKI 'e729224e8b3f31784c8a93c5b8ef6f4c1c91d9e6e577c45c33163609fe40011' ...READ MORE

answered Jun 16, 2018 in Blockchain by charlie_brown
• 7,720 points
1,885 views
0 votes
1 answer

Hyperledger Fabric query system chaincode using node SDK

The Fabric Node SDK actually provides a ...READ MORE

answered Nov 9, 2018 in Blockchain by Christine
• 15,790 points
1,202 views
0 votes
1 answer

Hyperledger Sawtooth vs Quorum in concurrency and speed Ask

Summary: Both should provide similar reliability of ...READ MORE

answered Sep 26, 2018 in IoT (Internet of Things) by Upasana
• 8,620 points
1,462 views
0 votes
1 answer

Invalid Batch or signature in Savtooth

This will solve your problem import org.apache.commons.codec.binary.Hex; Transaction txn ...READ MORE

answered Aug 1, 2018 in Blockchain by digger
• 26,740 points
1,025 views
+16 votes
4 answers
0 votes
1 answer

Hyperledger fabric node sdk deploy.js example failing

Have you installed couchdb? Install couchdb as ...READ MORE

answered Sep 17, 2018 in Blockchain by slayer
• 29,370 points
776 views
webinar REGISTER FOR FREE WEBINAR X
REGISTER NOW
webinar_success Thank you for registering Join Edureka Meetup community for 100+ Free Webinars each month JOIN MEETUP GROUP