Channel mychannel send transactions failed on orderer OrdererClient Reason timeout after 10000 ms

0 votes
I am using fabric-samples 2.2 "test-network" application. After starting up the network using fabric ca, I tried to connect from my sdk client application and send the transactions. But, I am getting error as it's unable to connect to orderer. I am getting following exception
```blockchainservice    |  at org.hyperledger.fabric.sdk.Channel.doSendTransaction(Channel.java:5704) ~[fabric-sdk-java-2.0.0.jar!/:na]
blockchainservice    |  ... 60 common frames omitted
blockchainservice    | Caused by: org.hyperledger.fabric.sdk.exception.TransactionException: Channel mychannel, send transactions failed on orderer OrdererClient{id: 10, channel: mychannel, name: orderer.example.com, url: grpcs://orderer.example.com:7050}. Reason:  timeout after 10000 ms.
blockchainservice    |  at org.hyperledger.fabric.sdk.OrdererClient.sendTransaction(OrdererClient.java:223) ~[fabric-sdk-java-2.0.0.jar!/:na]
blockchainservice    |  at org.hyperledger.fabric.sdk.Orderer.sendTransaction(Orderer.java:164) ~[fabric-sdk-java-2.0.0.jar!/:na]
blockchainservice    |  at org.hyperledger.fabric.sdk.Channel.doSendTransaction(Channel.java:5686) ~[fabric-sdk-java-2.0.0.jar!/:na]
```
This is happening only when I containerised my client application and trying to connect from it.
When ran the client application locally, everything works fine and blocks are getting committed to ledger.

Below is my client config file
```
---
name: test-network-org1
version: 1.0.0
client:
  organization: Org1
  connection:
    timeout:
      peer:
        endorser: '300'

channels:
  mychannel:
    orderers:
      - orderer.example.com
    peers:
      peer0.org1.example.com:
        endorsingPeer: true
        chaincodeQuery: true
        ledgerQuery: true
        eventSource: true
      peer0.org2.example.com:
        endorsingPeer: true
        chaincodeQuery: true
        ledgerQuery: true
        eventSource: true

organizations:
  Org1:
    mspid: Org1MSP
    peers:
      - peer0.org1.example.com
    certificateAuthorities:
      - ca.org1.example.com

orderers:
  orderer.example.com:
    url: grpcs://orderer.example.com:7050
    grpcOptions:
      ssl-target-name-override: orderer.example.com
      hostnameOverride: orderer.example.com
      request-timeout: 200000
    tlsCACerts:
      path: /opt/app/organizations/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem
peers:
  peer0.org1.example.com:
    url: grpcs://host.docker.internal:7051
    tlsCACerts:
      path: /opt/app/organizations/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/ca.crt
    grpcOptions:
      ssl-target-name-override: peer0.org1.example.com
      hostnameOverride: peer0.org1.example.com
      request-timeout: 120001
  peer0.org2.example.com:
    url: grpcs://host.docker.internal:9051
    tlsCACerts:
      path: /opt/app/organizations/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/tls/ca.crt
    grpcOptions:
      ssl-target-name-override: peer0.org2.example.com
      hostnameOverride: peer0.org2.example.com
      request-timeout: 120001
certificateAuthorities:
  ca.org1.example.com:
    url: https://host.docker.internal:7054
    caName: ca-org1
    tlsCACerts:
      path: /opt/app/organizations/fabric-ca/org1/ca-cert.pem
    httpOptions:
      verify: false
```
Highly Appreciate any help on this!
Jan 26, 2021 in Blockchain by menan

edited Mar 4 27 views

No answer to this question. Be the first to respond.

Your answer

Your name to display (optional):
Privacy: Your email address will only be used for sending these notifications.
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