-
Notifications
You must be signed in to change notification settings - Fork 224
Open
Labels
Description
Ran into an issue today with this demo. Making a note of it:
Successfully queried existing chaincode state: request={"chaincodeID":"324b2c4838021d6fdb678ed9a6259a9926fadb0c4b7d83f1419a79fa83260680","fcn":"query","args":["GetCompany","dale"]}, r
esponse={"result":{"type":"Buffer","data":[123,34,105,100,34,58,34,100,97,108,101,34,44,34,112,114,101,102,105,120,34,58,34,100,97,108,101,48,48,48,65,34,44,34,99,97,115,104,66,97,108
,97,110,99,101,34,58,49,101,43,48,55,44,34,97,115,115,101,116,73,100,115,34,58,110,117,108,108,125]}}, value={"id":"dale","prefix":"dale000A","cashBalance":1e+07,"assetIds":null}
company {"id":"dale","prefix":"dale000A","cashBalance":1e+07,"assetIds":null}
chainstats block 3 failure :(
status code: 500
headers: null
message: Error: connect ETIMEDOUT 169.46.12.196:5001
C:\Users\IBM_ADMIN\Documents\obc\git\demos\cp-web\node_modules\async\dist\async.js:985
if (fn === null) throw new Error("Callback was already called.");
^
Error: Callback was already called.
at C:\Users\IBM_ADMIN\Documents\obc\git\demos\cp-web\node_modules\async\dist\async.js:985:32
at failure (C:\Users\IBM_ADMIN\Documents\obc\git\demos\cp-web\utils\ws_part2.js:218:29)
at ClientRequest.<anonymous> (C:\Users\IBM_ADMIN\Documents\obc\git\demos\cp-web\utils\ws_part2.js:239:29)
at emitOne (events.js:96:13)
at ClientRequest.emit (events.js:188:7)
at TLSSocket.socketErrorListener (_http_client.js:310:9)
at emitOne (events.js:96:13)
at TLSSocket.emit (events.js:188:7)
at emitErrorNT (net.js:1276:8)
at _combinedTickCallback (internal/process/next_tick.js:74:11)
at process._tickCallback (internal/process/next_tick.js:98:9)