search

hyperledger-archives / fabric

THIS IS A READ-ONLY historic repository. Current development is at https://gerrit.hyperledger.org/r/#/admin/projects/fabric . pull requests not accepted
https://gerrit.hyperledger.org/
Apache License 2.0
1.17k stars 1.01k forks source link

Error:Failed to execute transaction or query #2375

Open dongmingh opened 8 years ago

dongmingh commented 8 years ago

Description

commit level: master branch from Gerrit commit f1b6762f569852f1fa75bd9a280507c3178fbe6d

issue: 4-peer network with PBFT-batch, security and privacy enabled chaincode: example02 transactions generated from SoapUI to query the same key, say a, repeatedly with 1 thread only, no error message with multi-threads, say 100, see the following message frequently:

14:16:17.153 [rest] processChaincodeInvokeOrQuery -> ERRO 5483 Error when querying chaincode: Error:Failed to execute transaction or query(Error sending QUERY: txid:ca978112ca1bbdcafac231b39a23dc4da786eff8147c4e72b9807785afee48bb exists)

The same error message shown on the log if use jMeter.

Describe How to Reproduce

  1. use local_fabric.sh to setup a 4-peer network pbft-batch, security and privacy enabled
  2. use and application, e.g., SoapUI or jMeter, to generate query with multi-thread
  3. check logs for the error message.
dongmingh commented 8 years ago

http://gerrit.hyperledger.org/r/313 makes TXIDs no longer unique but one side effect of this is concurrent queries will fail

ghost commented 8 years ago

You should deploy chaincode with security and privacy.

rameshthoomu commented 8 years ago

@scorpiovn : security and privacy enabled on peers. Seems this is a new issue after merge http://gerrit.hyperledger.org/r/313 patchset. @muralisrini do you have any inputs on this?

christo4ferris commented 8 years ago

@dongmingh we've migrated to using Jira for issue tracking, please open an issue there and close this one. You'll need a Linux Foundation ID to login. Thanks

nickmelis commented 7 years ago

Is this issue still open? I'm hitting the same problem in 0.6. Can anyone point me to the related JIRA issue please?