Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Report Timed out problem when send transactions to network #16

Open
z21921 opened this issue Jul 27, 2017 · 1 comment
Open

Report Timed out problem when send transactions to network #16

z21921 opened this issue Jul 27, 2017 · 1 comment

Comments

@z21921
Copy link

z21921 commented Jul 27, 2017

  1. PTE level: commit a15e57f
  2. Fabric level 1.0GA

Problems:
I create/join/install/instaniate network.
Then I use runCases-constant-i.zvm to send request.

PTE report following problems:

info: [PTE 0 main]: stderr: error: [Peer.js]: sendProposal - timed out after:45000

info: [PTE 0 main]: stderr: error: [Peer.js]: sendProposal - timed out after:45000
error: [client-utils.js]: sendPeersProposal - Promise is rejected: Error: REQUEST_TIMEOUT
at Timeout._onTimeout (/root/gopath/src/github.com/hyperledger/fabric-sdk-node/node_modules/fabric-client/lib/Peer.js:100:19)
at ontimeout (timers.js:365:14)
at tryOnTimeout (timers.js:237:5)

@dongmingh
Copy link
Owner

What is your network configuration and which org were the chaincode installed and instantiated?
If the chaincode is not instantiated on all org, it will take some time for all peers to synch-up. Before synch-up, the transaction will timeout with the message you reported.
If this is the case, run a short query against all org until you see all transaction go thru, then you can run your test cases.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants