FGJ-51: Increase default proposal timeout

The response for the first proposal arriving at a given chaincode on a given peer can take significantly longer as the chaincode container needs to be built and started. With the previous default timeout, intermittent failures were observed in automated scenario testing. Change-Id: I38491f2d9634720583968f833d0ddd2defc29ff1 Signed-off-by: Mark S. Lewis <mark_lewis@uk.ibm.com>
hyperledger · Oct 16, 2019 · c643cbc · c643cbc
1 parent a839010
commit c643cbc
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/src/main/java/org/hyperledger/fabric/sdk/helper/Config.java b/src/main/java/org/hyperledger/fabric/sdk/helper/Config.java
@@ -138,7 +138,7 @@ private Config() {
             /**
              * Timeout settings
              **/
-            defaultProperty(PROPOSAL_WAIT_TIME, "35000");
+            defaultProperty(PROPOSAL_WAIT_TIME, "120000");
             defaultProperty(CHANNEL_CONFIG_WAIT_TIME, "15000");
             defaultProperty(ORDERER_RETRY_WAIT_TIME, "200");
             defaultProperty(ORDERER_WAIT_TIME, "10000");

diff --git a/src/test/cirun.sh b/src/test/cirun.sh
@@ -20,7 +20,7 @@ export ORG_HYPERLEDGER_FABRIC_SDK_LOGLEVEL=TRACE
 export ORG_HYPERLEDGER_FABRIC_CA_SDK_LOGLEVEL=TRACE
 export ORG_HYPERLEDGER_FABRIC_SDK_LOG_EXTRALOGLEVEL=10
 
-export ORG_HYPERLEDGER_FABRIC_SDK_PROPOSAL_WAIT_TIME=55000
+#export ORG_HYPERLEDGER_FABRIC_SDK_PROPOSAL_WAIT_TIME=55000
 export ORG_HYPERLEDGER_FABRIC_SDK_CHANNELCONFIG_WAIT_TIME=20000
 export ORG_HYPERLEDGER_FABRIC_SDK_CLIENT_TRANSACTION_CLEANUP_UP_TIMEOUT_WAIT_TIME=65000
 export ORG_HYPERLEDGER_FABRIC_SDK_ORDERER_ORDERERWAITTIMEMILLISECS=180000