[INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building Bitrepository Client 1.7-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-client --- [INFO] Deleting /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/target [INFO] [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ bitrepository-client --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 4 resources [INFO] [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ bitrepository-client --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 130 source files to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/target/classes [WARNING] /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/src/main/java/org/bitrepository/commandline/utils/CommandLineArgumentsHandler.java: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/src/main/java/org/bitrepository/commandline/utils/CommandLineArgumentsHandler.java uses or overrides a deprecated API. [WARNING] /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/src/main/java/org/bitrepository/commandline/utils/CommandLineArgumentsHandler.java: Recompile with -Xlint:deprecation for details. [INFO] [INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ bitrepository-client --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/src/test/resources [INFO] [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ bitrepository-client --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 41 source files to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/target/test-classes [INFO] [INFO] --- maven-surefire-plugin:2.17:test (default-test) @ bitrepository-client --- [INFO] Surefire report directory: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/target/surefire-reports ------------------------------------------------------- T E S T S ------------------------------------------------------- Running TestSuite Configuring TestNG with: TestNG652Configurator Starting test project Core module test Suite: Surefire suite Starting testcase CommandLineTest Test starting: argumentsTesterUnknownArgument Description: Test the handling of arguments by the CommandLineArgumentHandler. Step: Validate arguments without any options. Test success: argumentsTesterUnknownArgument Test starting: argumentsTesterWrongArgument Description: Test the handling of arguments by the CommandLineArgumentHandler. Step: Validate the default options Test success: argumentsTesterWrongArgument Test starting: newArgumentTester Description: Test the handling of a new argument. Step: Test the option Test success: newArgumentTester Starting testcase GetChecksumsClientComponentTest Test starting: collectionIDIncludedInEventsTest Description: Tests the the client provides collectionID in events. Step: Set a 0.5 second operation timeout. Step: Start the operation Stimuli: Calling getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@638ef7ed, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@2415fc55[correlationID=dc2e27a1-8a8d-44ec-bce5-2be610f8d26a, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=collectionIDIncludedInEventsTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@24c22fe[fileID=, allFileIDs=true], checksumRequestForExistingFile=] Result: Received event: dc2e27a1: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums Step: Send positive responses from the pillar1 and a negative response from pillar2 Result: Received event: dc2e27a1: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: dc2e27a1: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE Result: Received event: dc2e27a1: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: dc2e27a1: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar1], Sending GetFileIDsRequest's Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@15a04efb[correlationID=dc2e27a1-8a8d-44ec-bce5-2be610f8d26a, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=collectionIDIncludedInEventsTest, to=, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@16c069df[fileID=, allFileIDs=true], minTimestamp=, maxTimestamp=, maxNumberOfResults=, checksumRequestForExistingFile=, resultAddress=] Step: Wait for 1 second Result: Received event: dc2e27a1: GET_CHECKSUMS: FAILED: , Failed to receive responses from all contributors before timeout(500ms). Missing contributors [Pillar1] Test success: collectionIDIncludedInEventsTest Starting testcase GetFileIDsClientComponentTest Test starting: collectionIDIncludedInEventsTest Description: Tests the the client provides collectionID in events. Step: Set a 0.5 second operation timeout. Step: Start the operation Stimuli: Calling getFileIDs(null, null, null, org.bitrepository.client.TestEventHandler@32c726ee) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@22f31dec[correlationID=f223ec2b-2324-4b19-9a5d-3d07d8b1328b, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=collectionIDIncludedInEventsTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@34c01041[fileID=, allFileIDs=true]] Result: Received event: f223ec2b: GET_FILE_IDS: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs Step: Send positive responses from the pillar1 and a negative response from pillar2 Result: Received event: f223ec2b: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: f223ec2b: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE Result: Received event: f223ec2b: GET_FILE_IDS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: f223ec2b: GET_FILE_IDS: REQUEST_SENT: ContributorID [Pillar1], Sending request for get fileIDs Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@36328d33[correlationID=f223ec2b-2324-4b19-9a5d-3d07d8b1328b, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=collectionIDIncludedInEventsTest, to=, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@2c4d1ac[fileID=, allFileIDs=true], minTimestamp=, maxTimestamp=, maxNumberOfResults=, resultAddress=] Step: Wait for 1 second Result: Received event: f223ec2b: GET_FILE_IDS: FAILED: , Failed to receive responses from all contributors before timeout(500ms). Missing contributors [Pillar1] Test success: collectionIDIncludedInEventsTest Test starting: conversationTimeoutTest Description: Tests the the client handles lack of IdentifyPillarResponses gracefully Step: Set a 100 ms ConversationTimeout. Step: Start the operation Stimuli: Calling getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@638ef7ed, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@e84a8e1[correlationID=e5709ed2-d0ff-4ccb-bbb5-ea6ff708c3dd, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=conversationTimeoutTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@2e554a3b[fileID=, allFileIDs=true], checksumRequestForExistingFile=] Result: Received event: e5709ed2: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums 02:18:51.443 WARN o.b.c.c.m.CollectionBasedConversationMediator - Failing timed out conversation e5709ed2-d0ff-4ccb-bbb5-ea6ff708c3dd (Age 1015ms) Result: Received event: e5709ed2: GET_CHECKSUMS: FAILED: , Failing timed out conversation e5709ed2-d0ff-4ccb-bbb5-ea6ff708c3dd Test success: conversationTimeoutTest Test starting: conversationTimeoutTest Description: Tests the the client handles lack of IdentifyPillarResponses gracefully Step: Set a 100 ms ConversationTimeout. Step: Start the operation Stimuli: Calling getFileIDs(null, null, null, org.bitrepository.client.TestEventHandler@32c726ee) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@3e8f7922[correlationID=c388d4ce-c158-4444-a776-39b101a66670, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=conversationTimeoutTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@63192798[fileID=, allFileIDs=true]] Result: Received event: c388d4ce: GET_FILE_IDS: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs 02:18:52.635 WARN o.b.c.c.m.CollectionBasedConversationMediator - Failing timed out conversation c388d4ce-c158-4444-a776-39b101a66670 (Age 1015ms) Result: Received event: c388d4ce: GET_FILE_IDS: FAILED: , Failing timed out conversation c388d4ce-c158-4444-a776-39b101a66670 Test success: conversationTimeoutTest Test starting: identificationFailureTest Description: Verify that the client works correctly when a contributor sends a failure response. Step: Start the operation. Stimuli: Calling getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@638ef7ed, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@e24ddd0[correlationID=4a49b789-5049-4f1b-9b8b-a7f521862f2a, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=identificationFailureTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@6f70f32f[fileID=, allFileIDs=true], checksumRequestForExistingFile=] Result: Received event: 4a49b789: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums Step: Send a identification response from contributor1 with a FAILURE response code. Result: Received event: 4a49b789: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE Step: Send a identification response from contributor2 with a IDENTIFICATION_POSITIVE response code . Result: Received event: 4a49b789: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: 4a49b789: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2] Result: Received event: 4a49b789: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar2], Sending GetFileIDsRequest's Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@5aabbb29[correlationID=4a49b789-5049-4f1b-9b8b-a7f521862f2a, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=identificationFailureTest, to=, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@72c927f1[fileID=, allFileIDs=true], minTimestamp=, maxTimestamp=, maxNumberOfResults=, checksumRequestForExistingFile=, resultAddress=] Step: Verify that the client continues to the performing phase. Step: Send a final response message from contributor2 Result: Received event: 4a49b789: GET_CHECKSUMS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false Result: Received event: 4a49b789: GET_CHECKSUMS: FAILED: , Failed operation. Cause(s): [4a49b789: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE] Test success: identificationFailureTest Test starting: identificationFailureTest Description: Verify that the client works correctly when a contributor sends a failure response. Step: Start the operation. Stimuli: Calling getFileIDs(null, null, null, org.bitrepository.client.TestEventHandler@32c726ee) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@5c371e13[correlationID=ab29c0f1-c052-46c0-816d-ba6dc55aa65d, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=identificationFailureTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@530a8454[fileID=, allFileIDs=true]] Result: Received event: ab29c0f1: GET_FILE_IDS: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs Step: Send a identification response from contributor1 with a FAILURE response code. Result: Received event: ab29c0f1: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE Step: Send a identification response from contributor2 with a IDENTIFICATION_POSITIVE response code . Result: Received event: ab29c0f1: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: ab29c0f1: GET_FILE_IDS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2] Result: Received event: ab29c0f1: GET_FILE_IDS: REQUEST_SENT: ContributorID [Pillar2], Sending request for get fileIDs Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@5215cd9a[correlationID=ab29c0f1-c052-46c0-816d-ba6dc55aa65d, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=identificationFailureTest, to=, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@36b6964d[fileID=, allFileIDs=true], minTimestamp=, maxTimestamp=, maxNumberOfResults=, resultAddress=] Step: Verify that the client continues to the performing phase. Step: Send a final response message from contributor2 Result: Received event: ab29c0f1: GET_FILE_IDS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false Result: Received event: ab29c0f1: GET_FILE_IDS: FAILED: , Failed operation. Cause(s): [ab29c0f1: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE] Test success: identificationFailureTest Test starting: identificationNegativeTest Description: Verify that the client works correctly when a contributor sends a negative response. Step: Start the operation. Stimuli: Calling getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@638ef7ed, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@4e558728[correlationID=34af0671-e6a2-4e54-bfcb-decc5b1b84cd, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=identificationNegativeTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@5eccd3b9[fileID=, allFileIDs=true], checksumRequestForExistingFile=] Result: Received event: 34af0671: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums Step: Send a identification response from contributor1 with a IDENTIFICATION_NEGATIVE response code . Result: Received event: 34af0671: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: IDENTIFICATION_NEGATIVE Step: Send a identification response from contributor2 with a IDENTIFICATION_POSITIVE response code . Result: Received event: 34af0671: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: 34af0671: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2] Result: Received event: 34af0671: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar2], Sending GetFileIDsRequest's Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@6ef7623[correlationID=34af0671-e6a2-4e54-bfcb-decc5b1b84cd, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=identificationNegativeTest, to=, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@64e1dd11[fileID=, allFileIDs=true], minTimestamp=, maxTimestamp=, maxNumberOfResults=, checksumRequestForExistingFile=, resultAddress=] Step: Verify that the client continues to the performing phase. Step: Send a final response message from contributor2 Result: Received event: 34af0671: GET_CHECKSUMS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false Result: Received event: 34af0671: GET_CHECKSUMS: FAILED: , Failed operation. Cause(s): [34af0671: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: IDENTIFICATION_NEGATIVE] Test success: identificationNegativeTest Test starting: identificationNegativeTest Description: Verify that the client works correctly when a contributor sends a negative response. Step: Start the operation. Stimuli: Calling getFileIDs(null, null, null, org.bitrepository.client.TestEventHandler@32c726ee) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@5e39850[correlationID=4318b1ee-9fc8-4e91-9ab8-67f7f0dc5b29, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=identificationNegativeTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@1603dc2f[fileID=, allFileIDs=true]] Result: Received event: 4318b1ee: GET_FILE_IDS: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs Step: Send a identification response from contributor1 with a IDENTIFICATION_NEGATIVE response code . Result: Received event: 4318b1ee: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: IDENTIFICATION_NEGATIVE Step: Send a identification response from contributor2 with a IDENTIFICATION_POSITIVE response code . Result: Received event: 4318b1ee: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: 4318b1ee: GET_FILE_IDS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2] Result: Received event: 4318b1ee: GET_FILE_IDS: REQUEST_SENT: ContributorID [Pillar2], Sending request for get fileIDs Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@61799544[correlationID=4318b1ee-9fc8-4e91-9ab8-67f7f0dc5b29, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=identificationNegativeTest, to=, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@78c1a023[fileID=, allFileIDs=true], minTimestamp=, maxTimestamp=, maxNumberOfResults=, resultAddress=] Step: Verify that the client continues to the performing phase. Step: Send a final response message from contributor2 Result: Received event: 4318b1ee: GET_FILE_IDS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false Result: Received event: 4318b1ee: GET_FILE_IDS: FAILED: , Failed operation. Cause(s): [4318b1ee: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: IDENTIFICATION_NEGATIVE] Test success: identificationNegativeTest Test starting: noContributorsRespondingTest Description: Tests the the client handles lack of a IdentifyResponse gracefully. More concrete this means that the occurrence of a identification timeout should be handled correctly Step: Set a 100 ms timeout for identifying contributors. Step: Start the operation. Stimuli: Calling getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@638ef7ed, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@6fd5717c[correlationID=c6720716-0fe7-4e20-9e58-3b65d602b451, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=noContributorsRespondingTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@7e2f86e6[fileID=, allFileIDs=true], checksumRequestForExistingFile=] Result: Received event: c6720716: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums Step: Wait for 1 second Result: Received event: c6720716: GET_CHECKSUMS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors The following contributors didn't respond: [Pillar1, Pillar2] Result: Received event: c6720716: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor Result: Received event: c6720716: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor Result: Received event: c6720716: GET_CHECKSUMS: FAILED: , Unable to continue operation, contributors unavailable. Test success: noContributorsRespondingTest Result: The following messages haven't been handled by the testcase: org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@6fd5717c[correlationID=c6720716-0fe7-4e20-9e58-3b65d602b451, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=noContributorsRespondingTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@7e2f86e6[fileID=, allFileIDs=true], checksumRequestForExistingFile=] 02:18:57.825 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@6fd5717c[correlationID=c6720716-0fe7-4e20-9e58-3b65d602b451, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=noContributorsRespondingTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@7e2f86e6[fileID=, allFileIDs=true], checksumRequestForExistingFile=] Test starting: noContributorsRespondingTest Description: Tests the the client handles lack of a IdentifyResponse gracefully. More concrete this means that the occurrence of a identification timeout should be handled correctly Step: Set a 100 ms timeout for identifying contributors. Step: Start the operation. Stimuli: Calling getFileIDs(null, null, null, org.bitrepository.client.TestEventHandler@32c726ee) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@3effd4f3[correlationID=ca7d3244-5a1a-43fe-bab1-e1df08e95891, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=noContributorsRespondingTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@41f4fe5[fileID=, allFileIDs=true]] Result: Received event: ca7d3244: GET_FILE_IDS: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs Step: Wait for 1 second Result: Received event: ca7d3244: GET_FILE_IDS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors The following contributors didn't respond: [Pillar1, Pillar2] Result: Received event: ca7d3244: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor Result: Received event: ca7d3244: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor Result: Received event: ca7d3244: GET_FILE_IDS: FAILED: , Unable to continue operation, contributors unavailable. Test success: noContributorsRespondingTest Result: The following messages haven't been handled by the testcase: org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@3effd4f3[correlationID=ca7d3244-5a1a-43fe-bab1-e1df08e95891, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=noContributorsRespondingTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@41f4fe5[fileID=, allFileIDs=true]] 02:18:58.088 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@3effd4f3[correlationID=ca7d3244-5a1a-43fe-bab1-e1df08e95891, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=noContributorsRespondingTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@41f4fe5[fileID=, allFileIDs=true]] Test starting: oneContributorNotRespondingTest Description: Verify that the client works correct without receiving identification responses from all contributors. Added fixture: Set the a identification timeout to 100 ms. Step: Start the operation. Stimuli: Calling getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@638ef7ed, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@53ed09e8[correlationID=4b016923-3f48-4bc7-921c-a19383f2b756, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=oneContributorNotRespondingTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@60859f5a[fileID=, allFileIDs=true], checksumRequestForExistingFile=] Result: Received event: 4b016923: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums Step: Send a identification response from contributor1. Result: Received event: 4b016923: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Step: Wait 1 second. Result: Received event: 4b016923: GET_CHECKSUMS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors The following contributors didn't respond: [Pillar2] Result: Received event: 4b016923: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor Result: Received event: 4b016923: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 4b016923: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar1], Sending GetFileIDsRequest's Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@33b92932[correlationID=4b016923-3f48-4bc7-921c-a19383f2b756, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=oneContributorNotRespondingTest, to=, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@3d7ed135[fileID=, allFileIDs=true], minTimestamp=, maxTimestamp=, maxNumberOfResults=, checksumRequestForExistingFile=, resultAddress=] Step: Verify that the client continues to the performing phase. Step: Send a final response upload message Result: Received event: 4b016923: GET_CHECKSUMS: COMPONENT_COMPLETE: ContributorID Pillar1, PartialResult=false Result: Received event: 4b016923: GET_CHECKSUMS: FAILED: , Failed operation. Cause(s): [4b016923: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor] Test success: oneContributorNotRespondingTest Test starting: oneContributorNotRespondingTest Description: Verify that the client works correct without receiving identification responses from all contributors. Added fixture: Set the a identification timeout to 100 ms. Step: Start the operation. Stimuli: Calling getFileIDs(null, null, null, org.bitrepository.client.TestEventHandler@32c726ee) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@2643d762[correlationID=338471af-7644-4d82-b676-2a4782aac960, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=oneContributorNotRespondingTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@6403e24c[fileID=, allFileIDs=true]] Result: Received event: 338471af: GET_FILE_IDS: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs Step: Send a identification response from contributor1. Result: Received event: 338471af: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Step: Wait 1 second. Result: Received event: 338471af: GET_FILE_IDS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors The following contributors didn't respond: [Pillar2] Result: Received event: 338471af: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor Result: Received event: 338471af: GET_FILE_IDS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 338471af: GET_FILE_IDS: REQUEST_SENT: ContributorID [Pillar1], Sending request for get fileIDs Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@39414242[correlationID=338471af-7644-4d82-b676-2a4782aac960, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=oneContributorNotRespondingTest, to=, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@7c43db0e[fileID=, allFileIDs=true], minTimestamp=, maxTimestamp=, maxNumberOfResults=, resultAddress=] Step: Verify that the client continues to the performing phase. Step: Send a final response upload message Result: Received event: 338471af: GET_FILE_IDS: COMPONENT_COMPLETE: ContributorID Pillar1, PartialResult=false Result: Received event: 338471af: GET_FILE_IDS: FAILED: , Failed operation. Cause(s): [338471af: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor] Test success: oneContributorNotRespondingTest Test starting: operationTimeoutTest Description: Tests the the client handles lack of final responses gracefully. Step: Set a 100 ms operation timeout. Step: Start the operation Stimuli: Calling getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@638ef7ed, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@4e49ce2b[correlationID=b636888b-2d88-4ee7-bd6a-6ce5e74dd4ee, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=operationTimeoutTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@136965e3[fileID=, allFileIDs=true], checksumRequestForExistingFile=] Result: Received event: b636888b: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums Step: Send positive responses from the pillar1 and a negative response from pillar2 Result: Received event: b636888b: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: b636888b: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE Result: Received event: b636888b: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: b636888b: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar1], Sending GetFileIDsRequest's Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@435cc7f9[correlationID=b636888b-2d88-4ee7-bd6a-6ce5e74dd4ee, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=operationTimeoutTest, to=, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@4364712f[fileID=, allFileIDs=true], minTimestamp=, maxTimestamp=, maxNumberOfResults=, checksumRequestForExistingFile=, resultAddress=] Step: Wait for 1 second Result: Received event: b636888b: GET_CHECKSUMS: FAILED: , Failed to receive responses from all contributors before timeout(100ms). Missing contributors [Pillar1] Test success: operationTimeoutTest Test starting: operationTimeoutTest Description: Tests the the client handles lack of final responses gracefully. Step: Set a 100 ms operation timeout. Step: Start the operation Stimuli: Calling getFileIDs(null, null, null, org.bitrepository.client.TestEventHandler@32c726ee) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@1391af3b[correlationID=1ae10c67-44f6-4a01-91b9-b37f8f99c20a, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=operationTimeoutTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@3762c4fc[fileID=, allFileIDs=true]] Result: Received event: 1ae10c67: GET_FILE_IDS: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs Step: Send positive responses from the pillar1 and a negative response from pillar2 Result: Received event: 1ae10c67: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 1ae10c67: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE Result: Received event: 1ae10c67: GET_FILE_IDS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 1ae10c67: GET_FILE_IDS: REQUEST_SENT: ContributorID [Pillar1], Sending request for get fileIDs Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@59fbb34[correlationID=1ae10c67-44f6-4a01-91b9-b37f8f99c20a, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=operationTimeoutTest, to=, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@1b6924cb[fileID=, allFileIDs=true], minTimestamp=, maxTimestamp=, maxNumberOfResults=, resultAddress=] Step: Wait for 1 second Result: Received event: 1ae10c67: GET_FILE_IDS: FAILED: , Failed to receive responses from all contributors before timeout(100ms). Missing contributors [Pillar1] Test success: operationTimeoutTest Test starting: getChecksumsDeliveredAtUrl Description: Tests the delivery of checksums from all pillars at a given URL. Step: Ensure the delivery file isn't already present on the http server Step: Request the delivery of the checksum of a file from all pillars. Stimuli: Calling getChecksums(null, default-test-file.txt, null, file:../bitrepository-core/src/test/resources/test-files//TEST-CHECKSUM-DELIVERY.xml, org.bitrepository.client.TestEventHandler@939ff41, TEST-AUDIT) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@6e0e5dec[correlationID=e80b55ff-cee9-40c8-9a1d-2979e4f42c1b, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=getChecksumsDeliveredAtUrl, to=, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@48a663e9[fileID=default-test-file.txt, allFileIDs=], checksumRequestForExistingFile=] Result: Received event: e80b55ff: GET_CHECKSUMS for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums Step: The pillar sends a response to the identify message. Result: Received event: e80b55ff: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: e80b55ff: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: e80b55ff: GET_CHECKSUMS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2, Pillar1] Result: Received event: e80b55ff: GET_CHECKSUMS for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending GetFileIDsRequest's Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@2d85fb64[correlationID=e80b55ff-cee9-40c8-9a1d-2979e4f42c1b, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=getChecksumsDeliveredAtUrl, to=, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@56476c16[fileID=default-test-file.txt, allFileIDs=], minTimestamp=, maxTimestamp=, maxNumberOfResults=, checksumRequestForExistingFile=, resultAddress=file:../bitrepository-core/src/test/resources/test-files//TEST-CHECKSUM-DELIVERY.xml-Pillar1] Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@497b560e[correlationID=e80b55ff-cee9-40c8-9a1d-2979e4f42c1b, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=getChecksumsDeliveredAtUrl, to=, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT, pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@39ffda4a[fileID=default-test-file.txt, allFileIDs=], minTimestamp=, maxTimestamp=, maxNumberOfResults=, checksumRequestForExistingFile=, resultAddress=file:../bitrepository-core/src/test/resources/test-files//TEST-CHECKSUM-DELIVERY.xml-Pillar2] Step: Sends a final response from each pillar Result: Received event: e80b55ff: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, NumberOfChecksums=0, PartialResult=false Result: Received event: e80b55ff: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2, NumberOfChecksums=0, PartialResult=false Result: Received event: e80b55ff: GET_CHECKSUMS for file default-test-file.txt: COMPLETE: Test success: getChecksumsDeliveredAtUrl Result: The following messages haven't been handled by the testcase: org.bitrepository.bitrepositorymessages.GetChecksumsRequest@497b560e[correlationID=e80b55ff-cee9-40c8-9a1d-2979e4f42c1b, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=getChecksumsDeliveredAtUrl, to=, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT, pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@39ffda4a[fileID=default-test-file.txt, allFileIDs=], minTimestamp=, maxTimestamp=, maxNumberOfResults=, checksumRequestForExistingFile=, resultAddress=file:../bitrepository-core/src/test/resources/test-files//TEST-CHECKSUM-DELIVERY.xml-Pillar2] 02:18:59.392 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: org.bitrepository.bitrepositorymessages.GetChecksumsRequest@497b560e[correlationID=e80b55ff-cee9-40c8-9a1d-2979e4f42c1b, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=getChecksumsDeliveredAtUrl, to=, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT, pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@39ffda4a[fileID=default-test-file.txt, allFileIDs=], minTimestamp=, maxTimestamp=, maxNumberOfResults=, checksumRequestForExistingFile=, resultAddress=file:../bitrepository-core/src/test/resources/test-files//TEST-CHECKSUM-DELIVERY.xml-Pillar2] Test starting: getChecksumsFromOtherCollection Description: Tests the getChecksums client will correctly try to get from a second collection if required Added fixture: Configure collection1 to contain both pillars and collection 2 to only contain pillar2 Step: Request the putting of a file through the PutClient for collection2 Stimuli: Calling getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@3cd26422, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@2eda072[correlationID=d362d87e-8044-4138-94c9-8e3dc80315bf, collectionID=SinglePillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=getChecksumsFromOtherCollection, to=Pillar2, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@3fa21d49[fileID=, allFileIDs=true], checksumRequestForExistingFile=] Result: Received event: d362d87e: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums Step: Send an identification response from pillar2. Result: Received event: d362d87e: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: d362d87e: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2] Result: Received event: d362d87e: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar2], Sending GetFileIDsRequest's Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@6e31d989[correlationID=d362d87e-8044-4138-94c9-8e3dc80315bf, collectionID=SinglePillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=getChecksumsFromOtherCollection, to=Pillar2, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@1b01a0d[fileID=, allFileIDs=true], minTimestamp=, maxTimestamp=, maxNumberOfResults=, checksumRequestForExistingFile=, resultAddress=] Step: Send a complete event from the pillar Result: Received event: d362d87e: GET_CHECKSUMS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false Result: Received event: d362d87e: GET_CHECKSUMS: COMPLETE: Test success: getChecksumsFromOtherCollection Test starting: getChecksumsFromSinglePillar Description: Tests that the client can retrieve checksums from a single pillar. Step: Request the delivery of the checksum of a file from pillar1. Stimuli: Calling getChecksums([ContributorQuery{componentID='Pillar1, minTimestamp=null, maxTimestamp=null, maxNumberOfResults=null}], default-test-file.txt, org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6003ad65[checksumType=MD5, checksumSalt=, otherChecksumType=], null, org.bitrepository.client.TestEventHandler@2ec99035, TEST-AUDIT) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@60743cdb[correlationID=fb589358-d484-4722-8055-ec3516380e74, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=getChecksumsFromSinglePillar, to=Pillar1, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@c02670f[fileID=default-test-file.txt, allFileIDs=], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6003ad65[checksumType=MD5, checksumSalt=, otherChecksumType=]] Result: Received event: fb589358: GET_CHECKSUMS for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums Step: Sends a response from pillar2. Step: Sends a response from pillar1. Result: Received event: fb589358: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: fb589358: GET_CHECKSUMS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: fb589358: GET_CHECKSUMS for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending GetFileIDsRequest's Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@7ca16adc[correlationID=fb589358-d484-4722-8055-ec3516380e74, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=getChecksumsFromSinglePillar, to=Pillar1, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@5ae1c281[fileID=default-test-file.txt, allFileIDs=], minTimestamp=, maxTimestamp=, maxNumberOfResults=, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6003ad65[checksumType=MD5, checksumSalt=, otherChecksumType=], resultAddress=] Step: Send a GetChecksumsFinalResponse to the client from pillar1 Result: Received event: fb589358: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, NumberOfChecksums=0, PartialResult=false Result: Received event: fb589358: GET_CHECKSUMS for file default-test-file.txt: COMPLETE: Test success: getChecksumsFromSinglePillar Test starting: testNoSuchFile Description: Testing how a request for a non-existing file is handled. Step: Setting up variables and such. Step: Request the delivery of the checksum of a file from the pillar(s). A callback listener should be supplied. Stimuli: Calling getChecksums(null, default-test-file.txt, null, null, org.bitrepository.client.TestEventHandler@28cd2c2, TEST-AUDIT) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@8e25d3f[correlationID=148c0aa2-0a7b-4a07-918b-74333860f312, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=testNoSuchFile, to=Pillar1, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@18a096b5[fileID=default-test-file.txt, allFileIDs=], checksumRequestForExistingFile=] Result: Received event: 148c0aa2: GET_CHECKSUMS for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums Step: The pillar sends a response to the identify message. Result: Received event: 148c0aa2: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 148c0aa2: GET_CHECKSUMS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 148c0aa2: GET_CHECKSUMS for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending GetFileIDsRequest's Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@1d4f5506[correlationID=148c0aa2-0a7b-4a07-918b-74333860f312, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=testNoSuchFile, to=Pillar1, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@7dee835[fileID=default-test-file.txt, allFileIDs=], minTimestamp=, maxTimestamp=, maxNumberOfResults=, checksumRequestForExistingFile=, resultAddress=] Step: Send a error that the file cannot be found. Result: Received event: 148c0aa2: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FILE_NOT_FOUND_FAILURE, No such file. Result: Received event: 148c0aa2: GET_CHECKSUMS for file default-test-file.txt: FAILED: , Failed operation. Cause(s): [148c0aa2: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FILE_NOT_FOUND_FAILURE, No such file.] Test success: testNoSuchFile Test starting: testPaging Description: Tests the GetChecksums client correctly handles functionality for limiting results, either by timestamp or result count. Step: Request checksums from with MinTimestamp, MaxTimestamp, MaxNumberOfResults set for both pillars . Stimuli: Calling getChecksums([ContributorQuery{componentID='Pillar1, minTimestamp=Sat Dec 19 02:19:00 CET 2015, maxTimestamp=Sat Dec 19 02:19:01 CET 2015, maxNumberOfResults=1}, ContributorQuery{componentID='Pillar2, minTimestamp=Sat Dec 19 02:19:01 CET 2015, maxTimestamp=Sat Dec 19 02:19:01 CET 2015, maxNumberOfResults=2}], null, null, null, org.bitrepository.client.TestEventHandler@638ef7ed, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@480cbe2e[correlationID=bf4e3116-f131-4fec-89ff-ef012e67f32a, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=testPaging, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@6c3f1658[fileID=, allFileIDs=true], checksumRequestForExistingFile=] Result: Received event: bf4e3116: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums Step: Send a IdentifyPillarsForGetChecksumsResponse from both pillars. Result: Received event: bf4e3116: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: bf4e3116: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: bf4e3116: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2, Pillar1] Result: Received event: bf4e3116: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending GetFileIDsRequest's Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@2de9ca6[correlationID=bf4e3116-f131-4fec-89ff-ef012e67f32a, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=testPaging, to=, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@59018eed[fileID=, allFileIDs=true], minTimestamp=2015-12-19T02:19:00.224+01:00, maxTimestamp=2015-12-19T02:19:01.124+01:00, maxNumberOfResults=1, checksumRequestForExistingFile=, resultAddress=] Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@2ee39e73[correlationID=bf4e3116-f131-4fec-89ff-ef012e67f32a, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=testPaging, to=, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@76973a6[fileID=, allFileIDs=true], minTimestamp=2015-12-19T02:19:01.124+01:00, maxTimestamp=2015-12-19T02:19:01.224+01:00, maxNumberOfResults=2, checksumRequestForExistingFile=, resultAddress=] Test success: testPaging Test starting: verifyGetChecksumsClientFromFactory Test success: verifyGetChecksumsClientFromFactory Starting testcase GetChecksumsCmdTest Test starting: checksumArgumentNonSaltAlgorithmWitoutSaltTest Description: Test MD5 checksum without salt -> no failure Test success: checksumArgumentNonSaltAlgorithmWitoutSaltTest Test starting: checksumArgumentSaltAlgorithmWithSaltTest Description: Test HMAC_SHA256 checksum with salt -> No failure Test success: checksumArgumentSaltAlgorithmWithSaltTest Test starting: defaultSuccessScenarioTest Description: Tests simplest arguments for running the CmdLineClient Test success: defaultSuccessScenarioTest Test starting: fileArgumentTest Description: Tests the argument for a specific file. Test success: fileArgumentTest Test starting: missingCollectionArgumentTest Description: Tests the scenario, where the collection arguments is missing. Takes the following arguments: -s The path to the directory with the settings files for the client -k The path to the file containing the private key. -v Makes the client more verbose -c The id for the collection to perform the operation on. -i The id for the file to perform the operation on. -p [OPTIONAL] The id of the pillar where the should be performed. If undefined the operations is performed on all pillars. -R [OPTIONAL] The algorithm of checksum to request in the response from the pillars. If no such argument is given, then the default from settings is retrieved. -S [OPTIONAL] The salt of checksum to request in the response. Requires the ChecksumType argument. Missing argument: Missing required option: c Test success: missingCollectionArgumentTest Test starting: specificPillarArgumentTest Description: Test argument for a specific pillar Test success: specificPillarArgumentTest Test starting: unknownPillarArgumentTest Description: Testing against a non-existing pillar id -> Should fail Invalid argument: Random1450487943759pillar is not a valid pillar for collection TwoPillarCollection The collection contains the following pillars: [Pillar1, Pillar2] Test success: unknownPillarArgumentTest Starting testcase GetFileClientComponentTest Test starting: chooseFastestPillarGetFileClient Description: Set the GetClient to retrieve a file as fast as possible, where it has to choose between to pillars with different times. The messages should be delivered at the same time. Step: Create a GetFileClient configured to use a fast and a slow pillar. Step: Defining the variables for the GetFileClient and defining them in the configuration Step: Make the GetClient ask for fastest pillar. Stimuli: Calling getFileFromFastestPillar(default-test-file.txt, file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileRequest@4e6280de[correlationID=9e94970d-9b5c-4124-a0ed-871f8db51386, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=chooseFastestPillarGetFileClient, to=, version=28, minVersion=24, auditTrailInformation=, fileID=default-test-file.txt] Result: Received event: 9e94970d: GET_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetFile Step: Three pillars send responses. First an average timeToDeliver, then a fast timeToDeliver and last a slow timeToDeliver. Result: Received event: 9e94970d: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID THE-AVERAGE-PILLAR Result: Received event: 9e94970d: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID THE-FAST-PILLAR Result: Received event: 9e94970d: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID THE-SLOW-PILLAR Result: Received event: 9e94970d: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [THE-FAST-PILLAR] Result: Received event: 9e94970d: GET_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID SelectedComponentInfo: componentID=THE-FAST-PILLAR, componentTopic=Pillar1_topic-cibuild01, Sending GetFileRequest to Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileRequest@5cf072ea[correlationID=9e94970d-9b5c-4124-a0ed-871f8db51386, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=chooseFastestPillarGetFileClient, to=, version=28, minVersion=24, auditTrailInformation=, pillarID=THE-FAST-PILLAR, fileID=default-test-file.txt, filePart=, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt] Test success: chooseFastestPillarGetFileClient Test starting: conversationTimeout Description: Tests the the GetFileClient handles lack of IdentifyPillarResponses gracefully Step: Set the number of pillars to 100ms and a 300 ms timeout for the conversation. Step: Request the delivery of a file from a specific pillar. A callback listener should be supplied. Stimuli: Calling getFileFromSpecificPillar(default-test-file.txt, file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, Pillar1) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileRequest@1203d787[correlationID=8054fe87-f30a-4e9c-b9c6-cf8d9e3c41a9, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=conversationTimeout, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, fileID=default-test-file.txt] Result: Received event: 8054fe87: GET_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetFile Step: The pillar sends a response to the identify message. Result: Received event: 8054fe87: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 8054fe87: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 8054fe87: GET_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID SelectedComponentInfo: componentID=Pillar1, componentTopic=Pillar1_topic-cibuild01, Sending GetFileRequest to Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileRequest@6f785a27[correlationID=8054fe87-f30a-4e9c-b9c6-cf8d9e3c41a9, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=conversationTimeout, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileID=default-test-file.txt, filePart=, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt] Step: Wait for 1 second 02:19:05.064 WARN o.b.c.c.m.CollectionBasedConversationMediator - Failing timed out conversation 8054fe87-f30a-4e9c-b9c6-cf8d9e3c41a9 (Age 1008ms) Result: Received event: 8054fe87: GET_FILE for file default-test-file.txt: FAILED: , Failing timed out conversation 8054fe87-f30a-4e9c-b9c6-cf8d9e3c41a9 Test success: conversationTimeout Test starting: failureDuringPerform Description: Verify that the GetFile reports a failed operation, in case of a component failing during the performing phase. Step: Request a getFile from the fastest pillar. Stimuli: Calling getFileFromFastestPillar(default-test-file.txt, file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileRequest@686fb58a[correlationID=52cad1d2-8395-46ae-a25f-91d550a48b8a, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=failureDuringPerform, to=, version=28, minVersion=24, auditTrailInformation=, fileID=default-test-file.txt] Result: Received event: 52cad1d2: GET_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetFile Step: Send a identification response from pillar1 and pillar2 with pillar1 the fastest. Result: Received event: 52cad1d2: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 52cad1d2: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: 52cad1d2: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 52cad1d2: GET_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID SelectedComponentInfo: componentID=Pillar1, componentTopic=Pillar1_topic-cibuild01, Sending GetFileRequest to Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileRequest@4be7acd9[correlationID=52cad1d2-8395-46ae-a25f-91d550a48b8a, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=failureDuringPerform, to=, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileID=default-test-file.txt, filePart=, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt] Step: Send a failure response from pillar1 Result: Received event: 52cad1d2: GET_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE Result: Received event: 52cad1d2: GET_FILE for file default-test-file.txt: FAILED: , Failed to get file from Pillar1, org.bitrepository.bitrepositoryelements.ResponseInfo@58afecfd[responseCode=FAILURE, responseText=] Test success: failureDuringPerform Test starting: getFileClientWithChecksumPillarInvolved Description: Verify that the GetFile works correctly when a checksum pillar respond. Step: Call getFile form fastest pillar. Stimuli: Calling getFileFromFastestPillar(default-test-file.txt, file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileRequest@7857cb1d[correlationID=e2dd2b92-48ff-4fe7-867a-0a4c33afb9ae, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=getFileClientWithChecksumPillarInvolved, to=, version=28, minVersion=24, auditTrailInformation=, fileID=default-test-file.txt] Result: Received event: e2dd2b92: GET_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetFile Step: Send a identification response from pillar1 with a REQUEST_NOT_SUPPORTED response code. Step: Send a identification response from pillar2 with a IDENTIFICATION_POSITIVE response code . Result: Received event: e2dd2b92: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: e2dd2b92: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2] Result: Received event: e2dd2b92: GET_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID SelectedComponentInfo: componentID=Pillar2, componentTopic=Pillar2_topic-cibuild01, Sending GetFileRequest to Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileRequest@7b54a0a4[correlationID=e2dd2b92-48ff-4fe7-867a-0a4c33afb9ae, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=getFileClientWithChecksumPillarInvolved, to=, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar2, fileID=default-test-file.txt, filePart=, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt] Step: Verify that the client continues to the performing phase. Step: Send a final response upload message Result: Received event: e2dd2b92: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2 Result: Received event: e2dd2b92: GET_FILE for file default-test-file.txt: COMPLETE: Test success: getFileClientWithChecksumPillarInvolved Test starting: getFileClientWithIdentifyTimeout Description: Verify that the GetFile works correct without receiving responses from all pillars. Added fixture: Set the identification timeout to 500ms Step: Call getFile form fastest pillar. Stimuli: Calling getFileFromFastestPillar(default-test-file.txt, file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileRequest@5a3be84[correlationID=bb198eed-5a09-4d60-ad1e-29997bfc78d4, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=getFileClientWithIdentifyTimeout, to=, version=28, minVersion=24, auditTrailInformation=, fileID=default-test-file.txt] Result: Received event: bb198eed: GET_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetFile Step: Send a identification response from pillar1. Result: Received event: bb198eed: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Step: Wait 1 second. Result: Received event: bb198eed: GET_FILE for file default-test-file.txt: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors The following contributors didn't respond: [Pillar2] Result: Received event: bb198eed: GET_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor Result: Received event: bb198eed: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: bb198eed: GET_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID SelectedComponentInfo: componentID=Pillar1, componentTopic=Pillar1_topic-cibuild01, Sending GetFileRequest to Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileRequest@6498d0d[correlationID=bb198eed-5a09-4d60-ad1e-29997bfc78d4, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=getFileClientWithIdentifyTimeout, to=, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileID=default-test-file.txt, filePart=, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt] Step: Verify that the client continues to the performing phase. Step: Send a final response upload message Result: Received event: bb198eed: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1 Result: Received event: bb198eed: GET_FILE for file default-test-file.txt: COMPLETE: Test success: getFileClientWithIdentifyTimeout Test starting: getFileFromOtherCollection Description: Tests the getFiles client will correctly try to get from a second collection if required Added fixture: Configure collection1 to contain both pillars and collection 2 to only contain pillar2 Step: Request the getting of a file through the client for collection2 Stimuli: Calling getFileFromFastestPillar(default-test-file.txt, file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileRequest@462b239f[correlationID=10b7dacb-7b8f-4af0-adbb-1cfdb2926358, collectionID=SinglePillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=getFileFromOtherCollection, to=Pillar2, version=28, minVersion=24, auditTrailInformation=, fileID=default-test-file.txt] Result: Received event: 10b7dacb: GET_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetFile Step: Send an identification response from pillar2. Result: Received event: 10b7dacb: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: 10b7dacb: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2] Result: Received event: 10b7dacb: GET_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID SelectedComponentInfo: componentID=Pillar2, componentTopic=Pillar2_topic-cibuild01, Sending GetFileRequest to Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileRequest@2d5e051e[correlationID=10b7dacb-7b8f-4af0-adbb-1cfdb2926358, collectionID=SinglePillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=getFileFromOtherCollection, to=Pillar2, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar2, fileID=default-test-file.txt, filePart=, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt] Step: Send a complete event from the pillar Result: Received event: 10b7dacb: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2 Result: Received event: 10b7dacb: GET_FILE for file default-test-file.txt: COMPLETE: Test success: getFileFromOtherCollection Test starting: getFileFromSpecificPillar Description: Tests that the GetClient client works correctly when requesting a file from a specific pillar Step: Request the delivery of a file from pillar2. Stimuli: Calling getFileFromSpecificPillar(default-test-file.txt, file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, Pillar2) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileRequest@c8531b9[correlationID=7cf2fe8e-8b97-462b-b874-fdaffdf01f74, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=getFileFromSpecificPillar, to=Pillar2, version=28, minVersion=24, auditTrailInformation=AuditTrailInfo for getFileFromSpecificPillarTest, fileID=default-test-file.txt] Result: Received event: 7cf2fe8e: GET_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetFile Step: Send a response from pillar1 Step: Send a response from pillar2 Result: Received event: 7cf2fe8e: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: 7cf2fe8e: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2] Result: Received event: 7cf2fe8e: GET_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID SelectedComponentInfo: componentID=Pillar2, componentTopic=Pillar2_topic-cibuild01, Sending GetFileRequest to Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileRequest@5e976553[correlationID=7cf2fe8e-8b97-462b-b874-fdaffdf01f74, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=getFileFromSpecificPillar, to=Pillar2, version=28, minVersion=24, auditTrailInformation=AuditTrailInfo for getFileFromSpecificPillarTest, pillarID=Pillar2, fileID=default-test-file.txt, filePart=, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt] Step: Send a GetFileProgressResponse. Result: Received event: 7cf2fe8e: GET_FILE for file default-test-file.txt: PROGRESS: ContributorID Pillar2, First test progress response message Step: Send a GetFileFinalResponse. Result: Received event: 7cf2fe8e: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2 Result: Received event: 7cf2fe8e: GET_FILE for file default-test-file.txt: COMPLETE: Test success: getFileFromSpecificPillar Test starting: getFileFromSpecificPillarWithFilePart Description: Tests that the GetClient client works for a single pillar participates. Also validate, that the 'FilePart' can be used. Step: Set the number of pillars to 1 Step: Request the delivery of a file from a specific pillar. A callback listener should be supplied. Stimuli: Calling getFileFromSpecificPillar(default-test-file.txt, file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, Pillar1) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileRequest@3c5bb37d[correlationID=7aeeb057-4e64-41dd-b2ff-57d46e5c2f57, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=getFileFromSpecificPillarWithFilePart, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, fileID=default-test-file.txt] Result: Received event: 7aeeb057: GET_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetFile Step: The pillar sends a response to the identify message. Result: Received event: 7aeeb057: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 7aeeb057: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 7aeeb057: GET_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID SelectedComponentInfo: componentID=Pillar1, componentTopic=Pillar1_topic-cibuild01, Sending GetFileRequest to Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileRequest@25fcdcc6[correlationID=7aeeb057-4e64-41dd-b2ff-57d46e5c2f57, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=getFileFromSpecificPillarWithFilePart, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileID=default-test-file.txt, filePart=org.bitrepository.bitrepositoryelements.FilePart@180fb796[partOffSet=1, partLength=10], fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt] Step: The pillar sends a getFile response to the GetClient. Result: Received event: 7aeeb057: GET_FILE for file default-test-file.txt: PROGRESS: ContributorID Pillar1, First test progress response message Step: The file is uploaded to the indicated url and the pillar sends a final response upload message Result: Received event: 7aeeb057: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1 Result: Received event: 7aeeb057: GET_FILE for file default-test-file.txt: COMPLETE: Test success: getFileFromSpecificPillarWithFilePart Test starting: noIdentifyResponse Description: Tests the the GetFileClient handles lack of IdentifyPillarResponses gracefully Step: Set a 500 ms timeout for identifying pillar. Step: Make the GetClient ask for fastest pillar. Stimuli: Calling getFileFromFastestPillar(default-test-file.txt, file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileRequest@6ffa8126[correlationID=06bcc346-ada7-438b-826b-a5214444c6b4, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=noIdentifyResponse, to=, version=28, minVersion=24, auditTrailInformation=, fileID=default-test-file.txt] Result: Received event: 06bcc346: GET_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetFile Step: Wait for 1 seconds Result: Received event: 06bcc346: GET_FILE for file default-test-file.txt: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors The following contributors didn't respond: [Pillar1, Pillar2] Result: Received event: 06bcc346: GET_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor Result: Received event: 06bcc346: GET_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor Result: Received event: 06bcc346: GET_FILE for file default-test-file.txt: FAILED: , Unable to continue operation, contributors unavailable. Test success: noIdentifyResponse Test starting: singleComponentFailureDuringIdentify Description: Verify that the GetFile reports a complete (not failed), in case of a component failing during the identify phase. Step: Call getFile from the fastest pillar. Stimuli: Calling getFileFromFastestPillar(default-test-file.txt, file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileRequest@57fae911[correlationID=a763ac2d-05a7-4acf-994d-e127f3b5ce91, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=singleComponentFailureDuringIdentify, to=, version=28, minVersion=24, auditTrailInformation=, fileID=default-test-file.txt] Result: Received event: a763ac2d: GET_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetFile Step: Send a identification response from pillar1 with a IDENTIFICATION_NEGATIVE response code . Result: Received event: a763ac2d: GET_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: IDENTIFICATION_NEGATIVE Step: Send a identification response from pillar2 with a IDENTIFICATION_POSITIVE response code . Result: Received event: a763ac2d: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: a763ac2d: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2] Result: Received event: a763ac2d: GET_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID SelectedComponentInfo: componentID=Pillar2, componentTopic=Pillar2_topic-cibuild01, Sending GetFileRequest to Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileRequest@28941a68[correlationID=a763ac2d-05a7-4acf-994d-e127f3b5ce91, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=singleComponentFailureDuringIdentify, to=, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar2, fileID=default-test-file.txt, filePart=, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt] Step: Verify that the client continues to the performing phase. Step: Send a final response upload message Result: Received event: a763ac2d: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2 Result: Received event: a763ac2d: GET_FILE for file default-test-file.txt: COMPLETE: Test success: singleComponentFailureDuringIdentify Test starting: testNoSuchFileMultiplePillars Description: Testing how a request for a non-existing file is handled when all pillars miss the file. Step: Use the default 2 pillars. Step: Call getFileFromFastestPillar. Stimuli: Calling getFileFromFastestPillar(ERROR-NO-SUCH-FILE-ERROR, file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileRequest@21202507[correlationID=1f21abcd-309a-45db-a504-844ca66f66c2, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=testNoSuchFileMultiplePillars, to=, version=28, minVersion=24, auditTrailInformation=, fileID=ERROR-NO-SUCH-FILE-ERROR] Result: Received event: 1f21abcd: GET_FILE for file ERROR-NO-SUCH-FILE-ERROR: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetFile Step: Both pillars sends a FILE_NOT_FOUND response Result: Received event: 1f21abcd: GET_FILE for file ERROR-NO-SUCH-FILE-ERROR: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FILE_NOT_FOUND_FAILURE, File ERROR-NO-SUCH-FILE-ERROR not present on this pillar Result: Received event: 1f21abcd: GET_FILE for file ERROR-NO-SUCH-FILE-ERROR: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: FILE_NOT_FOUND_FAILURE, File ERROR-NO-SUCH-FILE-ERRORnot present on this pillar Result: Received event: 1f21abcd: GET_FILE for file ERROR-NO-SUCH-FILE-ERROR: FAILED: , Unable to continue operation, contributors unavailable. Test success: testNoSuchFileMultiplePillars Test starting: testNoSuchFileSpecificPillar Description: Testing how a request for a non-existing file is handled on a specific pillar request. Step: Define 1 pillar. Step: Call getFileFromSpecificPillar. Stimuli: Calling getFileFromSpecificPillar(ERROR-NO-SUCH-FILE-ERROR, file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, Pillar1) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileRequest@6c6c93f8[correlationID=2a28f7d5-0421-4349-9e48-70f1e4ed0ffd, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=testNoSuchFileSpecificPillar, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, fileID=ERROR-NO-SUCH-FILE-ERROR] Result: Received event: 2a28f7d5: GET_FILE for file ERROR-NO-SUCH-FILE-ERROR: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetFile Step: The specified pillars sends a FILE_NOT_FOUND response Result: Received event: 2a28f7d5: GET_FILE for file ERROR-NO-SUCH-FILE-ERROR: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FILE_NOT_FOUND_FAILURE, File ERROR-NO-SUCH-FILE-ERROR not present on this pillar Pillar1 Result: Received event: 2a28f7d5: GET_FILE for file ERROR-NO-SUCH-FILE-ERROR: FAILED: , Unable to continue operation, contributors unavailable. Test success: testNoSuchFileSpecificPillar Test starting: verifyGetFileClientFromFactory Test success: verifyGetFileClientFromFactory Test starting: getFileIDsDeliveredAtUrl Description: Tests the delivery of fileIDs from a pillar at a given URL. Step: Initialise the variables for this test. Step: Request the delivery of the file ids of a file from the pillar(s). A callback listener should be supplied. Stimuli: Calling getFileIDs(null, default-test-file.txt, file:../bitrepository-core/src/test/resources/test-files//TEST-FILE-IDS-DELIVERY.xml, org.bitrepository.client.TestEventHandler@32c726ee) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@12ebcdf6[correlationID=ad6f04d9-4667-47ee-a75b-bef102e23cf6, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=getFileIDsDeliveredAtUrl, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@30dd23e2[fileID=default-test-file.txt, allFileIDs=]] Result: Received event: ad6f04d9: GET_FILE_IDS for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs Step: The pillar sends a response to the identify message. Result: Received event: ad6f04d9: GET_FILE_IDS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: ad6f04d9: GET_FILE_IDS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: ad6f04d9: GET_FILE_IDS for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for get fileIDs Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@75693526[correlationID=ad6f04d9-4667-47ee-a75b-bef102e23cf6, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=getFileIDsDeliveredAtUrl, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@39a1c200[fileID=default-test-file.txt, allFileIDs=], minTimestamp=, maxTimestamp=, maxNumberOfResults=, resultAddress=file:../bitrepository-core/src/test/resources/test-files//TEST-FILE-IDS-DELIVERY.xml-Pillar1] Step: The pillar sends a getFileIDsProgressResponse to the GetFileIDsClient. Result: Received event: ad6f04d9: GET_FILE_IDS for file default-test-file.txt: PROGRESS: ContributorID Pillar1, First test progress response message Step: The resulting file is uploaded to the indicated url and the pillar sends a final response upload message Result: Received event: ad6f04d9: GET_FILE_IDS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, PartialResult=false Result: Received event: ad6f04d9: GET_FILE_IDS for file default-test-file.txt: COMPLETE: Step: Receive and validate event results for the pillar. Test success: getFileIDsDeliveredAtUrl Test starting: getFileIDsDeliveredThroughMessage Description: Tests the delivery of fileIDs from a pillar at a given URL. Step: Initialise the variables for this test. Step: Ensure the delivery file isn't already present on the http server Step: Request the delivery of the file ids of a file from the pillar(s). A callback listener should be supplied. Stimuli: Calling getFileIDs(null, default-test-file.txt, null, org.bitrepository.client.TestEventHandler@32c726ee) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@4c231f62[correlationID=e444c9f1-cf10-4e32-9189-8e0a00d13d51, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=getFileIDsDeliveredThroughMessage, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@6888746c[fileID=default-test-file.txt, allFileIDs=]] Result: Received event: e444c9f1: GET_FILE_IDS for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs Step: The pillar sends a response to the identify message. Result: Received event: e444c9f1: GET_FILE_IDS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: e444c9f1: GET_FILE_IDS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: e444c9f1: GET_FILE_IDS for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for get fileIDs Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@6d3194ff[correlationID=e444c9f1-cf10-4e32-9189-8e0a00d13d51, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=getFileIDsDeliveredThroughMessage, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@393d4e34[fileID=default-test-file.txt, allFileIDs=], minTimestamp=, maxTimestamp=, maxNumberOfResults=, resultAddress=] Step: The pillar sends a getFileIDsProgressResponse to the GetFileIDsClient. Result: Received event: e444c9f1: GET_FILE_IDS for file default-test-file.txt: PROGRESS: ContributorID Pillar1, First test progress response message Step: The resulting file is uploaded to the indicated url and the pillar sends a final response upload message Result: Received event: e444c9f1: GET_FILE_IDS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, NumberOfFileIDs=1, PartialResult=false Result: Received event: e444c9f1: GET_FILE_IDS for file default-test-file.txt: COMPLETE: Step: Receive and validate event results for the pillar. Test success: getFileIDsDeliveredThroughMessage Test starting: getFileIDsFromOtherCollection Description: Tests the getFileIDs client will correctly try to get from a second collection if required Added fixture: Configure collection1 to contain both pillars and collection 2 to only contain pillar2 Step: Request the putting of a file through the PutClient for collection2 Stimuli: Calling getFileIDs(null, default-test-file.txt, null, org.bitrepository.client.TestEventHandler@4628f386) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@38224635[correlationID=4e92339c-d362-40cc-b12b-92bb66f28623, collectionID=SinglePillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=getFileIDsFromOtherCollection, to=Pillar2, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@7385a72f[fileID=default-test-file.txt, allFileIDs=]] Result: Received event: 4e92339c: GET_FILE_IDS for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs Step: Send an identification response from pillar2. Result: Received event: 4e92339c: GET_FILE_IDS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: 4e92339c: GET_FILE_IDS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2] Result: Received event: 4e92339c: GET_FILE_IDS for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar2], Sending request for get fileIDs Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@5e445ffe[correlationID=4e92339c-d362-40cc-b12b-92bb66f28623, collectionID=SinglePillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=getFileIDsFromOtherCollection, to=Pillar2, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@74fda9ed[fileID=default-test-file.txt, allFileIDs=], minTimestamp=, maxTimestamp=, maxNumberOfResults=, resultAddress=] Step: Send a complete event from the pillar Result: Received event: 4e92339c: GET_FILE_IDS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false Result: Received event: 4e92339c: GET_FILE_IDS for file default-test-file.txt: COMPLETE: Test success: getFileIDsFromOtherCollection Test starting: testNoSuchFile Description: Testing how a request for a non-existing file is handled. Step: Setting up variables and such. Step: Request the delivery of the file id of a file from the pillar(s). A callback listener should be supplied. Stimuli: Calling getFileIDs(null, default-test-file.txt, file:../bitrepository-core/src/test/resources/test-files//TEST-FILE-IDS-DELIVERY.xml, org.bitrepository.client.TestEventHandler@32c726ee) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@66c88fce[correlationID=13e1560b-ea54-41c9-84a8-6e5fc3e7591c, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=testNoSuchFile, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@6ccfce5a[fileID=default-test-file.txt, allFileIDs=]] Result: Received event: 13e1560b: GET_FILE_IDS for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs Step: The pillar sends a response to the identify message. Result: Received event: 13e1560b: GET_FILE_IDS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 13e1560b: GET_FILE_IDS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 13e1560b: GET_FILE_IDS for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for get fileIDs Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@14f03f2[correlationID=13e1560b-ea54-41c9-84a8-6e5fc3e7591c, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=testNoSuchFile, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@235b4aea[fileID=default-test-file.txt, allFileIDs=], minTimestamp=, maxTimestamp=, maxNumberOfResults=, resultAddress=file:../bitrepository-core/src/test/resources/test-files//TEST-FILE-IDS-DELIVERY.xml-Pillar1] Step: Send a error that the file cannot be found. Result: Received event: 13e1560b: GET_FILE_IDS for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FILE_NOT_FOUND_FAILURE, No such file. Result: Received event: 13e1560b: GET_FILE_IDS for file default-test-file.txt: FAILED: , Failed operation. Cause(s): [13e1560b: GET_FILE_IDS for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FILE_NOT_FOUND_FAILURE, No such file.] Test success: testNoSuchFile Test starting: testPaging Description: Tests the GetFileIDs client correctly handles functionality for limiting results, either by timestamp or result count. Step: Request fileIDs from with MinTimestamp, MaxTimestamp, MaxNumberOfResults set for both pillars . Stimuli: Calling getFileIDs([ContributorQuery{componentID='Pillar1, minTimestamp=Sat Dec 19 02:19:08 CET 2015, maxTimestamp=Sat Dec 19 02:19:09 CET 2015, maxNumberOfResults=1}, ContributorQuery{componentID='Pillar2, minTimestamp=Sat Dec 19 02:19:09 CET 2015, maxTimestamp=Sat Dec 19 02:19:09 CET 2015, maxNumberOfResults=2}], null, null, org.bitrepository.client.TestEventHandler@32c726ee) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@72b4ecb2[correlationID=98435ed3-0114-4182-a3ae-19f24955b487, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=testPaging, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@457dc809[fileID=, allFileIDs=true]] Result: Received event: 98435ed3: GET_FILE_IDS: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs Step: Send a IdentifyPillarsForGetFileIDsResponse from both pillars. Result: Received event: 98435ed3: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 98435ed3: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: 98435ed3: GET_FILE_IDS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2, Pillar1] Result: Received event: 98435ed3: GET_FILE_IDS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for get fileIDs Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@6abbdcde[correlationID=98435ed3-0114-4182-a3ae-19f24955b487, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=testPaging, to=, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@41ad6c00[fileID=, allFileIDs=true], minTimestamp=2015-12-19T02:19:08.880+01:00, maxTimestamp=2015-12-19T02:19:09.780+01:00, maxNumberOfResults=1, resultAddress=] Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@2a10407e[correlationID=98435ed3-0114-4182-a3ae-19f24955b487, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=testPaging, to=, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@6edc8385[fileID=, allFileIDs=true], minTimestamp=2015-12-19T02:19:09.780+01:00, maxTimestamp=2015-12-19T02:19:09.880+01:00, maxNumberOfResults=2, resultAddress=] Test success: testPaging Test starting: verifyGetFileIDsClientFromFactory Test success: verifyGetFileIDsClientFromFactory Starting testcase PutFileCmdTest Test starting: checksumArgumentNonSaltAlgorithmWitoutSaltTest Description: Test MD5 checksum without salt -> no failure Test success: checksumArgumentNonSaltAlgorithmWitoutSaltTest Test starting: checksumArgumentSaltAlgorithmWithSaltTest Description: Test HMAC_SHA256 checksum with salt -> No failure Test success: checksumArgumentSaltAlgorithmWithSaltTest Test starting: defaultSuccessScenarioTest Description: Tests simplest arguments for running the CmdLineClient Test success: defaultSuccessScenarioTest Test starting: missingChecksumWhenFileArgumentTest Description: Tests the scenario, where no checksum argument is given, but a file is given. Test success: missingChecksumWhenFileArgumentTest Test starting: missingChecksumWhenURLArgumentTest Description: Tests the scenario, where no checksum argument is given, but a URL is given. Invalid argument: The URL argument requires also the checksum argument (-c). Test success: missingChecksumWhenURLArgumentTest Test starting: missingCollectionArgumentTest Description: Tests the scenario, where the collection arguments is missing. Takes the following arguments: -s The path to the directory with the settings files for the client -k The path to the file containing the private key. -v Makes the client more verbose -c The id for the collection to perform the operation on. -i The id for the file to perform the operation on. -p [OPTIONAL] The id of the pillar where the should be performed. If undefined the operations is performed on all pillars. -f The path to the file, which is wanted to be put. Is required, unless a URL is given. -u The URL for the file to be put. Is required, unless the actual file is given. -C The checksum for the file to be retreived. Required if using an URL. -R [OPTIONAL] The algorithm of checksum to request in the response from the pillars. -S [OPTIONAL] The salt of checksum to request in the response. Requires the ChecksumType argument. -d If this argument is present, then the file will be removed from the server, when the operation is complete. Missing argument: Missing required option: c Test success: missingCollectionArgumentTest Test starting: missingFileIDWhenFileArgumentTest Description: Tests the scenario, where no checksum argument is given, but a URL is given. Test success: missingFileIDWhenFileArgumentTest Test starting: missingFileIDWhenURLArgumentTest Description: Tests the scenario, where no checksum argument is given, but a URL is given. Invalid argument: The URL argument requires also the argument for the ID of the file (-i). Test success: missingFileIDWhenURLArgumentTest Test starting: missingFileOrURLArgumentTest Description: Tests the scenario, where no arguments for file or url is given. Invalid argument: Requires either the file argument (-f) or the URL argument (-u). Test success: missingFileOrURLArgumentTest Test starting: specificPillarArgumentTest Description: Test argument for a specific pillar Test success: specificPillarArgumentTest Test starting: unknownPillarArgumentTest Description: Testing against a non-existing pillar id -> Should fail Invalid argument: Random1450487952499pillar is not a valid pillar for collection TwoPillarCollection The collection contains the following pillars: [Pillar1, Pillar2] Test success: unknownPillarArgumentTest Test starting: urlSuccessScenarioTest Description: Tests arguments for putting a file on a given URL Test success: urlSuccessScenarioTest Starting testcase DeleteFileCmdTest Test starting: checksumArgumentNonSaltAlgorithmWitoutSaltTest Description: Test MD5 checksum without salt -> no failure Test success: checksumArgumentNonSaltAlgorithmWitoutSaltTest Test starting: checksumArgumentSaltAlgorithmWithSaltTest Description: Test HMAC_SHA256 checksum with salt -> No failure Test success: checksumArgumentSaltAlgorithmWithSaltTest Test starting: defaultSuccessScenarioTest Description: Tests simplest arguments for running the CmdLineClient Test success: defaultSuccessScenarioTest Test starting: missingCollectionArgumentTest Description: Tests the scenario, where the collection arguments is missing. Takes the following arguments: -s The path to the directory with the settings files for the client -k The path to the file containing the private key. -v Makes the client more verbose -c The id for the collection to perform the operation on. -i The id for the file to perform the operation on. -p [OPTIONAL] The id of the pillar where the should be performed. If undefined the operations is performed on all pillars. -C [OPTIONAL] The checksum of the file to be delete. -R [OPTIONAL] The algorithm of checksum to request in the response from the pillars. -S [OPTIONAL] The salt of checksum to request in the response. Requires the ChecksumType argument. Missing argument: Missing required option: c Test success: missingCollectionArgumentTest Test starting: missingFileIDArgumentTest Description: Tests the scenario, where no arguments for file id argument is given. Takes the following arguments: -s The path to the directory with the settings files for the client -k The path to the file containing the private key. -v Makes the client more verbose -c The id for the collection to perform the operation on. -i The id for the file to perform the operation on. -p [OPTIONAL] The id of the pillar where the should be performed. If undefined the operations is performed on all pillars. -C [OPTIONAL] The checksum of the file to be delete. -R [OPTIONAL] The algorithm of checksum to request in the response from the pillars. -S [OPTIONAL] The salt of checksum to request in the response. Requires the ChecksumType argument. Missing argument: Missing required option: i Test success: missingFileIDArgumentTest Test starting: missingPillarArgumentTest Description: Tests the different scenarios, with the pillar argument. Invalid argument: The pillar argument -p must defined for the delete operation, only single pillar deletes are allowed Test success: missingPillarArgumentTest Test starting: unknownPillarArgumentTest Step: Testing against a non-existing pillar id Invalid argument: Random1450487954550pillar is not a valid pillar for collection TwoPillarCollection The collection contains the following pillars: [Pillar1, Pillar2] Test success: unknownPillarArgumentTest Starting testcase GetFileCmdTest Test starting: defaultSuccessScenarioTest Description: Tests simplest arguments for running the CmdLineClient Test success: defaultSuccessScenarioTest Test starting: missingCollectionArgumentTest Description: Tests the scenario, where the collection arguments is missing. Takes the following arguments: -s The path to the directory with the settings files for the client -k The path to the file containing the private key. -v Makes the client more verbose -c The id for the collection to perform the operation on. -i The id for the file to perform the operation on. -p [OPTIONAL] The id of the pillar where the should be performed. If undefined the operations is performed on all pillars. -l [OPTIONAL] The location where the file should be placed (either total path or directory). If no argument, then in the directory where the script is located. Missing argument: Missing required option: c Test success: missingCollectionArgumentTest Test starting: missingFileIDArgumentTest Description: Tests the scenario, where no arguments for file id argument is given. Takes the following arguments: -s The path to the directory with the settings files for the client -k The path to the file containing the private key. -v Makes the client more verbose -c The id for the collection to perform the operation on. -i The id for the file to perform the operation on. -p [OPTIONAL] The id of the pillar where the should be performed. If undefined the operations is performed on all pillars. -l [OPTIONAL] The location where the file should be placed (either total path or directory). If no argument, then in the directory where the script is located. Missing argument: Missing required option: i Test success: missingFileIDArgumentTest Test starting: specificPillarArgumentTest Description: Test argument for a specific pillar Test success: specificPillarArgumentTest Test starting: unknownPillarArgumentTest Description: Testing against a non-existing pillar id -> Should fail Invalid argument: Random1450487955595pillar is not a valid pillar for collection TwoPillarCollection The collection contains the following pillars: [Pillar1, Pillar2] Test success: unknownPillarArgumentTest Starting testcase PutFileClientComponentTest Test starting: defaultReturnChecksumsWithChecksumPillar Description: Tests that PutClient handles the presence of a ChecksumPillar correctly, when a return checksum of default type is requested (which a checksum pillar can provide). Step: Call putFile while requesting a salted checksum to be returned. Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6a837740[checksumType=MD5, checksumSalt=, otherChecksumType=], org.bitrepository.client.TestEventHandler@740639ba, TEST-AUDIT-TRAIL) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@3d1cb317[correlationID=d727b017-e706-49a5-9e20-564585a9490c, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=defaultReturnChecksumsWithChecksumPillar, to=, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, fileID=default-test-file.txt, fileSize=0] Result: Received event: d727b017: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file Step: Send an identification response with a PillarChecksumSpec element set, indicating that this is a checksum pillar. Result: Received event: d727b017: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Step: Send an normal identification response from pillar2. Result: Received event: d727b017: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: d727b017: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2, Pillar1] Result: Received event: d727b017: PUT_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for put file Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@46b5b238[correlationID=d727b017-e706-49a5-9e20-564585a9490c, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=defaultReturnChecksumsWithChecksumPillar, to=, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=, checksumRequestForNewFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6a837740[checksumType=MD5, checksumSalt=, otherChecksumType=]] Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@29eeb1bb[correlationID=d727b017-e706-49a5-9e20-564585a9490c, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=defaultReturnChecksumsWithChecksumPillar, to=, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, pillarID=Pillar2, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=, checksumRequestForNewFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6a837740[checksumType=MD5, checksumSalt=, otherChecksumType=]] Test success: defaultReturnChecksumsWithChecksumPillar Test starting: fileExistsOnPillarChecksumFromPillarNoClientChecksum Description: Tests that PutClient handles the presence of a file correctly, when the pillar returns a checksum but the putFile was called without a checksum. Step: Call putFile. Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, null, org.bitrepository.client.TestEventHandler@3dd4d6e6, TEST-AUDIT-TRAIL) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@576c8cea[correlationID=17c4b1b1-4a80-45cb-b5dd-ecdda6eaebda, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=fileExistsOnPillarChecksumFromPillarNoClientChecksum, to=, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, fileID=default-test-file.txt, fileSize=0] Result: Received event: 17c4b1b1: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file Step: Send a DUPLICATE_FILE_FAILURE response with a random checksum. Result: Received event: 17c4b1b1: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: DUPLICATE_FILE_FAILURE, Received negative response from component Pillar1: org.bitrepository.bitrepositoryelements.ResponseInfo@d2eb3a0[responseCode=DUPLICATE_FILE_FAILURE, responseText=Testing the handling of 'DUPLICATE FILE' identification.] (existing file checksum does not match) Result: Received event: 17c4b1b1: PUT_FILE for file default-test-file.txt: FAILED: , Can not put file default-test-file.txt, as an different file already exists on pillar Pillar1 Test success: fileExistsOnPillarChecksumFromPillarNoClientChecksum Test starting: fileExistsOnPillarDifferentChecksumFromPillar Description: Tests that PutClient handles the presence of a file correctly, when the pillar returns a checksum different from the file being put. Step: Call putFile. Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@7d69bb0e[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@63f70fd7[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={-70}, calculationTimestamp=2015-12-19T02:19:16.240+01:00], null, org.bitrepository.client.TestEventHandler@2d9cde8, TEST-AUDIT-TRAIL) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@7d2b2f3a[correlationID=08c9b5be-1cc9-4b69-8e5e-e9c37f1f8e8e, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=fileExistsOnPillarDifferentChecksumFromPillar, to=, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, fileID=default-test-file.txt, fileSize=0] Result: Received event: 08c9b5be: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file Step: Send a DUPLICATE_FILE_FAILURE response with a random checksum. Result: Received event: 08c9b5be: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: DUPLICATE_FILE_FAILURE, Received negative response from component Pillar1: org.bitrepository.bitrepositoryelements.ResponseInfo@5a025435[responseCode=DUPLICATE_FILE_FAILURE, responseText=Testing the handling of 'DUPLICATE FILE' identification.] (existing file checksum does not match) Result: Received event: 08c9b5be: PUT_FILE for file default-test-file.txt: FAILED: , Can not put file default-test-file.txt, as an different file already exists on pillar Pillar1 Test success: fileExistsOnPillarDifferentChecksumFromPillar Test starting: fileExistsOnPillarNoChecksumFromPillar Description: Tests that PutClient handles the presence of a file correctly, when the pillar doesn't return a checksum in the identification response. Step: Call putFile. Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, null, org.bitrepository.client.TestEventHandler@4924c27e, TEST-AUDIT-TRAIL) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@7b04dba0[correlationID=cb679f64-1ffc-46ed-89cd-6a95fd1ac989, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=fileExistsOnPillarNoChecksumFromPillar, to=, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, fileID=default-test-file.txt, fileSize=0] Result: Received event: cb679f64: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file Step: Send a DUPLICATE_FILE_FAILURE response without a checksum. Result: Received event: cb679f64: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: DUPLICATE_FILE_FAILURE, Received negative response from component Pillar1: org.bitrepository.bitrepositoryelements.ResponseInfo@57916acc[responseCode=DUPLICATE_FILE_FAILURE, responseText=Testing the handling of 'DUPLICATE FILE' identification.] Result: Received event: cb679f64: PUT_FILE for file default-test-file.txt: FAILED: , Can not put file default-test-file.txt, as an file already exists on pillar Pillar1 Test success: fileExistsOnPillarNoChecksumFromPillar Test starting: noPillarsResponding Description: Tests the handling of missing identification responses from all pillar Added fixture: Sets the identification timeout to 100 ms. Step: Request the putting of a file through the PutClient Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, null, org.bitrepository.client.TestEventHandler@7c96249e, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@2dfb8de3[correlationID=21afad24-300a-4790-b581-3a8f596e9e2d, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=noPillarsResponding, to=, version=28, minVersion=24, auditTrailInformation=, fileID=default-test-file.txt, fileSize=0] Result: Received event: 21afad24: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file Step: Do not respond. Just await the timeout. Result: Received event: 21afad24: PUT_FILE for file default-test-file.txt: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors The following contributors didn't respond: [Pillar1, Pillar2] Result: Received event: 21afad24: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor Result: Received event: 21afad24: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor Result: Received event: 21afad24: PUT_FILE for file default-test-file.txt: FAILED: , Unable to continue operation, contributors unavailable. Test success: noPillarsResponding Test starting: noReturnChecksumsWithChecksumPillar Description: Tests that PutClient handles the presence of a ChecksumPillar correctly, when no return checksum is requested. Step: Call putFile while requesting a salted checksum to be returned. Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, null, org.bitrepository.client.TestEventHandler@7e532896, TEST-AUDIT-TRAIL) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@7a60c431[correlationID=cd7aaa24-8d94-4e24-83ea-d4356efefd8f, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=noReturnChecksumsWithChecksumPillar, to=, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, fileID=default-test-file.txt, fileSize=0] Result: Received event: cd7aaa24: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file Step: Send an identification response with a PillarChecksumSpec element set, indicating that this is a checksum pillar. Result: Received event: cd7aaa24: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Step: Send an normal identification response from pillar2. Result: Received event: cd7aaa24: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: cd7aaa24: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2, Pillar1] Result: Received event: cd7aaa24: PUT_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for put file Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@28b1ccd1[correlationID=cd7aaa24-8d94-4e24-83ea-d4356efefd8f, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=noReturnChecksumsWithChecksumPillar, to=, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=, checksumRequestForNewFile=] Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@548cc4ba[correlationID=cd7aaa24-8d94-4e24-83ea-d4356efefd8f, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=noReturnChecksumsWithChecksumPillar, to=, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, pillarID=Pillar2, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=, checksumRequestForNewFile=] Test success: noReturnChecksumsWithChecksumPillar Test starting: normalPutFile Description: Tests the PutClient. Makes a whole conversation for the put client for a 'good' scenario. Added fixture: Initialise the number of pillars to one Step: Ensure that the test-file is placed on the HTTP server. Step: Request the delivery of a file from a specific pillar. A callback listener should be supplied. Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, null, org.bitrepository.client.TestEventHandler@69a4249, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@82560b6[correlationID=db0c8ec8-ab78-441a-86e0-7f9e64d1081b, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=normalPutFile, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, fileID=default-test-file.txt, fileSize=0] Result: Received event: db0c8ec8: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file Step: Make response for the pillar. Result: Received event: db0c8ec8: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: db0c8ec8: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: db0c8ec8: PUT_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for put file Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@5686f018[correlationID=db0c8ec8-ab78-441a-86e0-7f9e64d1081b, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=normalPutFile, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=, checksumRequestForNewFile=] Step: Validate the steps of the PutClient by going through the events. Step: The pillar sends a progress response to the PutClient. Result: Received event: db0c8ec8: PUT_FILE for file default-test-file.txt: PROGRESS: ContributorID Pillar1, First test progress response message Step: Send a final response message to the PutClient. Result: Received event: db0c8ec8: PUT_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, requestedChecksumResult=null Result: Received event: db0c8ec8: PUT_FILE for file default-test-file.txt: COMPLETE: Test success: normalPutFile Test starting: onePillarPutRetryFailure Reference: BITMAG-810 Reference client should be able to retry failed file transfers Description: Tests that a putfile attempt failing due to FILE_TRANSFER_FAILURE is only attempted the maximum allowed attempts Added fixture: Sets the identification timeout to 3 sec, allow two retries and only register one pillar. Step: Request the putting of a file through the PutClient Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, null, org.bitrepository.client.TestEventHandler@6dd1e22, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@1b9df329[correlationID=61ecd007-edcb-46d1-bbab-88ad14570830, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarPutRetryFailure, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, fileID=default-test-file.txt, fileSize=0] Result: Received event: 61ecd007: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file Step: Send an identification response from the one pillar. Result: Received event: 61ecd007: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 61ecd007: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 61ecd007: PUT_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for put file Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@599308d0[correlationID=61ecd007-edcb-46d1-bbab-88ad14570830, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarPutRetryFailure, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=, checksumRequestForNewFile=] Step: The client should proceed to send a putFileOperation request to the responding pillar. Step: Send a PutFileFinalResponse indicating a FILE_TRANSFER_FAILURE Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@375121ce[correlationID=61ecd007-edcb-46d1-bbab-88ad14570830, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarPutRetryFailure, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=, checksumRequestForNewFile=] Result: Received event: 61ecd007: PUT_FILE for file default-test-file.txt: WARNING: ContributorID Pillar1, Retrying putfile (attempt number 2) Step: Send a PutFileFinalResponse indicating a FILE_TRANSFER_FAILURE for the second put attempt Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@43a188b6[correlationID=61ecd007-edcb-46d1-bbab-88ad14570830, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarPutRetryFailure, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=, checksumRequestForNewFile=] Result: Received event: 61ecd007: PUT_FILE for file default-test-file.txt: WARNING: ContributorID Pillar1, Retrying putfile (attempt number 3) Step: Send a PutFileFinalResponse indicating a FILE_TRANSFER_FAILURE for the third put attempt Result: Received event: 61ecd007: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FILE_TRANSFER_FAILURE Result: Received event: 61ecd007: PUT_FILE for file default-test-file.txt: FAILED: , Failed operation. Cause(s): [61ecd007: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FILE_TRANSFER_FAILURE] Test success: onePillarPutRetryFailure Test starting: onePillarPutRetrySuccess Reference: BITMAG-810 Reference client should be able to retry failed file transfers Description: Tests the handling of a failed transmission when retry is allowed Added fixture: Sets the identification timeout to 3 sec, allow two retries and only register one pillar. Step: Request the putting of a file through the PutClient Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, null, org.bitrepository.client.TestEventHandler@414cf106, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@b24fff1[correlationID=c49128e3-e868-4faf-8fd2-d1ffdbc19d92, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarPutRetrySuccess, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, fileID=default-test-file.txt, fileSize=0] Result: Received event: c49128e3: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file Step: Send an identification response from the one pillar. Result: Received event: c49128e3: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: c49128e3: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: c49128e3: PUT_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for put file Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@57e8e8d6[correlationID=c49128e3-e868-4faf-8fd2-d1ffdbc19d92, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarPutRetrySuccess, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=, checksumRequestForNewFile=] Step: The client should proceed to send a putFileOperation request to the responding pillar. Step: Send a PutFileFinalResponse indicating a FILE_TRANSFER_FAILURE Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@710ae7ec[correlationID=c49128e3-e868-4faf-8fd2-d1ffdbc19d92, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarPutRetrySuccess, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=, checksumRequestForNewFile=] Result: Received event: c49128e3: PUT_FILE for file default-test-file.txt: WARNING: ContributorID Pillar1, Retrying putfile (attempt number 2) Step: A new PutFileRequest is send, pillar responds with success Result: Received event: c49128e3: PUT_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, requestedChecksumResult=null Result: Received event: c49128e3: PUT_FILE for file default-test-file.txt: COMPLETE: Test success: onePillarPutRetrySuccess Test starting: onePillarRespondingWithPartialPutAllowed Reference: BITMAG-598 It should be possible to putFiles, even though only a subset of the pillars are available Description: Tests the handling of missing identification responses from one pillar, when partial put are allowed Added fixture: Sets the identification timeout to 100 ms and allow partial puts. Step: Request the putting of a file through the PutClient Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, null, org.bitrepository.client.TestEventHandler@33f2ccd1, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@323e5176[correlationID=cd7cfe8d-9f2b-485e-97bd-837645cd9fbe, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarRespondingWithPartialPutAllowed, to=, version=28, minVersion=24, auditTrailInformation=, fileID=default-test-file.txt, fileSize=0] Result: Received event: cd7cfe8d: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file Step: Only send an identification response from one pillar. Result: Received event: cd7cfe8d: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Step: Await the timeout. Result: Received event: cd7cfe8d: PUT_FILE for file default-test-file.txt: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors The following contributors didn't respond: [Pillar2] Result: Received event: cd7cfe8d: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor Result: Received event: cd7cfe8d: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: cd7cfe8d: PUT_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for put file Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@4df50388[correlationID=cd7cfe8d-9f2b-485e-97bd-837645cd9fbe, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarRespondingWithPartialPutAllowed, to=, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=, checksumRequestForNewFile=] Step: The client should proceed to send a putFileOperation request to the responding pillar. Step: Send a pillar complete event Result: Received event: cd7cfe8d: PUT_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, requestedChecksumResult=null Result: Received event: cd7cfe8d: PUT_FILE for file default-test-file.txt: FAILED: , Failed operation. Cause(s): [cd7cfe8d: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor] Test success: onePillarRespondingWithPartialPutAllowed Test starting: onePillarRespondingWithPartialPutDisallowed Description: Tests the handling of missing identification responses from one pillar, when partial put are allowed Added fixture: Sets the identification timeout to 100 ms and disallow partial puts. Step: Request the putting of a file through the PutClient Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, null, org.bitrepository.client.TestEventHandler@30511454, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@55c596aa[correlationID=6cfc2d50-946d-432a-82f8-ebbfdbca5b15, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarRespondingWithPartialPutDisallowed, to=, version=28, minVersion=24, auditTrailInformation=, fileID=default-test-file.txt, fileSize=0] Result: Received event: 6cfc2d50: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file Step: Only send an identification response from one pillar. Result: Received event: 6cfc2d50: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Step: Await the timeout. Result: Received event: 6cfc2d50: PUT_FILE for file default-test-file.txt: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors The following contributors didn't respond: [Pillar2] Result: Received event: 6cfc2d50: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor Result: Received event: 6cfc2d50: PUT_FILE for file default-test-file.txt: FAILED: , Unable to continue operation, contributors unavailable. Test success: onePillarRespondingWithPartialPutDisallowed Test starting: putClientOperationTimeout Description: Tests the handling of a failed operation for the PutClient Step: Initialise the number of pillars and the PutClient. Sets the operation timeout to 100 ms. Step: Request the putting of a file through the PutClient Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, null, org.bitrepository.client.TestEventHandler@399e59d7, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@6c520c71[correlationID=5ee47121-ca11-48b5-b5a2-ca29c85c101e, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=putClientOperationTimeout, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, fileID=default-test-file.txt, fileSize=0] Result: Received event: 5ee47121: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file Step: Make response for the pillar. Result: Received event: 5ee47121: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 5ee47121: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 5ee47121: PUT_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for put file Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@2a04cf8a[correlationID=5ee47121-ca11-48b5-b5a2-ca29c85c101e, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=putClientOperationTimeout, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=, checksumRequestForNewFile=] Step: Validate the steps of the PutClient by going through the events. Step: Do not respond. Just await the timeout. Result: Received event: 5ee47121: PUT_FILE for file default-test-file.txt: FAILED: , Failed to receive responses from all contributors before timeout(100ms). Missing contributors [Pillar1] Test success: putClientOperationTimeout Test starting: putClientPillarOperationFailed Description: Tests the handling of a operation failure for the PutClient. Step: Initialise the number of pillars to one Step: Ensure that the test-file is placed on the HTTP server. Step: Request the delivery of a file from a specific pillar. A callback listener should be supplied. Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, null, org.bitrepository.client.TestEventHandler@44a2f289, TEST-AUDIT-TRAIL) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@6aae4199[correlationID=c8cd18f1-f88a-43c1-a063-1945c3d1dd77, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=putClientPillarOperationFailed, to=Pillar1, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, fileID=default-test-file.txt, fileSize=0] Result: Received event: c8cd18f1: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file Step: Send pillar response. Result: Received event: c8cd18f1: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: c8cd18f1: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: c8cd18f1: PUT_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for put file Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@2cb6bc65[correlationID=c8cd18f1-f88a-43c1-a063-1945c3d1dd77, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=putClientPillarOperationFailed, to=Pillar1, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=, checksumRequestForNewFile=] Step: Validate the steps of the PutClient by going through the events. Step: Send a failed response message to the PutClient. Result: Received event: c8cd18f1: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE, Verifying that a failure can be understood! Result: Received event: c8cd18f1: PUT_FILE for file default-test-file.txt: FAILED: , Failed operation. Cause(s): [c8cd18f1: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE, Verifying that a failure can be understood!] Test success: putClientPillarOperationFailed Test starting: putToOtherCollection Reference: BITMAG-925 Client will always try to put to the pillars defined in the first collection Description: Tests the putFIle client will correctly try to put to a second collection if required Added fixture: Sets the identification timeout to 3 sec, allow two retries and only register one pillar. Added fixture: Configure collection1 to contain both pillars and collection 2 to only contain pillar2 Step: Request the putting of a file through the PutClient for collection2 Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, null, org.bitrepository.client.TestEventHandler@6e0c20b8, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@1a70d5df[correlationID=85f0ede1-4add-4365-be94-b8bff3bf9f9c, collectionID=SinglePillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=putToOtherCollection, to=Pillar2, version=28, minVersion=24, auditTrailInformation=, fileID=default-test-file.txt, fileSize=0] Result: Received event: 85f0ede1: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file Step: Send an identification response from pillar2. Result: Received event: 85f0ede1: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: 85f0ede1: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2] Result: Received event: 85f0ede1: PUT_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar2], Sending request for put file Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@3de2e589[correlationID=85f0ede1-4add-4365-be94-b8bff3bf9f9c, collectionID=SinglePillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=putToOtherCollection, to=Pillar2, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar2, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=, checksumRequestForNewFile=] Step: Send a put complete event from the pillar Result: Received event: 85f0ede1: PUT_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2, requestedChecksumResult=null Result: Received event: 85f0ede1: PUT_FILE for file default-test-file.txt: COMPLETE: Test success: putToOtherCollection Test starting: saltedReturnChecksumsWithChecksumPillar Description: Tests that PutClient handles the presence of a ChecksumPillar correctly, when a salted return checksum (which a checksum pillar can't provide) is requested. Reference: BITMAG-677put, replace and delete clients fails if return checksums are requested and a checksumpillar is involved Step: Call putFile while requesting a salted checksum to be returned. Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@596ecd6c[checksumType=HMAC_MD5, checksumSalt={-86}, otherChecksumType=], org.bitrepository.client.TestEventHandler@68fd7df, TEST-AUDIT-TRAIL) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@735666c4[correlationID=893ee7be-27d3-40d6-ab0f-366b513e67fd, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=saltedReturnChecksumsWithChecksumPillar, to=, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, fileID=default-test-file.txt, fileSize=0] Result: Received event: 893ee7be: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file Step: Send an identification response with a PillarChecksumSpec element set, indicating that this is a checksum pillar. Result: Received event: 893ee7be: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Step: Send an normal identification response from pillar2. Result: Received event: 893ee7be: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: 893ee7be: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2] Result: Received event: 893ee7be: PUT_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for put file Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@1fb89238[correlationID=893ee7be-27d3-40d6-ab0f-366b513e67fd, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=saltedReturnChecksumsWithChecksumPillar, to=, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=, checksumRequestForNewFile=] Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@5f18a74d[correlationID=893ee7be-27d3-40d6-ab0f-366b513e67fd, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=saltedReturnChecksumsWithChecksumPillar, to=, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, pillarID=Pillar2, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=, checksumRequestForNewFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@596ecd6c[checksumType=HMAC_MD5, checksumSalt={-86}, otherChecksumType=]] Test success: saltedReturnChecksumsWithChecksumPillar Test starting: sameFileExistsOnOnePillar Description: Tests that PutClient handles the presence of a file correctly, when the pillar returns a checksum equal the file being put (idempotent). Step: Call putFile. Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@56d87044[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@3b5c6eee[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-12-19T02:19:18.440+01:00], null, org.bitrepository.client.TestEventHandler@4526b3d5, TEST-AUDIT-TRAIL) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@47120b41[correlationID=e6d3ed7a-b697-4667-a79f-523d88c5dfa9, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=sameFileExistsOnOnePillar, to=, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, fileID=default-test-file.txt, fileSize=0] Result: Received event: e6d3ed7a: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file Step: Send a DUPLICATE_FILE_FAILURE response with a checksum equal to the one supplied to the client. Result: Received event: e6d3ed7a: PUT_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, requestedChecksumResult=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@7a668497[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2df9d099[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-12-19T02:19:18.443+01:00], File already existed on Pillar1 Step: Send an identification response from the second pillar. Result: Received event: e6d3ed7a: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: e6d3ed7a: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2] Result: Received event: e6d3ed7a: PUT_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar2], Sending request for put file Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@6cb62e90[correlationID=e6d3ed7a-b697-4667-a79f-523d88c5dfa9, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=sameFileExistsOnOnePillar, to=, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, pillarID=Pillar2, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@56d87044[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@3b5c6eee[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-12-19T02:19:18.440+01:00], checksumRequestForNewFile=] Step: The client should proceed to send a putFileOperation request to the second pillar. Step: Send a pillar complete event Result: Received event: e6d3ed7a: PUT_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2, requestedChecksumResult=null Result: Received event: e6d3ed7a: PUT_FILE for file default-test-file.txt: COMPLETE: Test success: sameFileExistsOnOnePillar Test starting: verifyPutClientFromFactory Description: Testing the initialization through the ModifyComponentFactory. Step: Use the ModifyComponentFactory to instantiate a PutFileClient. Test success: verifyPutClientFromFactory Starting testcase ReplaceFileCmdTest Test starting: URLSuccessScenarioTest Description: Tests the scenario, where a URL instead of a file is used for the replacement file. Test success: URLSuccessScenarioTest Test starting: bothFileAndURLArgumentTest Description: Tests the scenario, where both arguments for file or url is given. Invalid argument: Cannot take both a file (-f) and an URL (-u) as argument. Test success: bothFileAndURLArgumentTest Test starting: checksumArgumentNonSaltAlgorithmWitoutSaltTest Description: Test MD5 checksum without salt -> no failure Test success: checksumArgumentNonSaltAlgorithmWitoutSaltTest Test starting: checksumArgumentSaltAlgorithmWithSaltTest Description: Test HMAC_SHA256 checksum with salt -> No failure Test success: checksumArgumentSaltAlgorithmWithSaltTest Test starting: defaultSuccessScenarioTest Description: Tests simplest arguments for running the CmdLineClient Test success: defaultSuccessScenarioTest Test starting: missingChecksumForExistingFileWhenUsingFileArgumentTest Description: Tests the scenario, where no checksum argument is given, but a File is given. Invalid argument: Checksum argument (-C) are mandatory for Replace and replace operations as defined in RepositorySettings. Test success: missingChecksumForExistingFileWhenUsingFileArgumentTest Test starting: missingChecksumForExistingFileWhenUsingURLArgumentTest Description: Tests the scenario, where no checksum argument is given, but a URL is given. Invalid argument: Checksum argument (-C) are mandatory for Replace and replace operations as defined in RepositorySettings. Test success: missingChecksumForExistingFileWhenUsingURLArgumentTest Test starting: missingChecksumForNewFileWhenUsingFileArgumentTest Description: Tests the scenario, where no checksum argument is given, but a File is given. Test success: missingChecksumForNewFileWhenUsingFileArgumentTest Test starting: missingChecksumForNewFileWhenUsingURLArgumentTest Description: Tests the scenario, where no checksum argument is given, but a URL is given. Invalid argument: The URL argument requires also the checksum argument for the file to replace with (-r). Test success: missingChecksumForNewFileWhenUsingURLArgumentTest Test starting: missingCollectionArgumentTest Description: Tests the scenario, where the collection arguments is missing. Takes the following arguments: -s The path to the directory with the settings files for the client -k The path to the file containing the private key. -v Makes the client more verbose -c The id for the collection to perform the operation on. -i The id for the file to perform the operation on. -p [OPTIONAL] The id of the pillar where the should be performed. If undefined the operations is performed on all pillars. -C [OPTIONAL] The checksum of the file to be replaced. -f The path to the new file for the replacement. Required unless using the URL argument. -u The URL for the file to be retreived. Is required, unless the actual file is given. -r The checksum for the file to replace with. Required when using the URL argument. -R [OPTIONAL] The algorithm of checksum to request in the response from the pillars. -S [OPTIONAL] The salt of checksum to request in the response. Requires the ChecksumType argument. -d If this argument is present, then the file will be removed from the server, when the operation is complete. Missing argument: Missing required option: c Test success: missingCollectionArgumentTest Test starting: missingFileIDWhenFileArgumentTest Description: Tests the scenario, where no checksum argument is given, but a URL is given. Test success: missingFileIDWhenFileArgumentTest Test starting: missingFileIDWhenURLArgumentTest Description: Tests the scenario, where no checksum argument is given, but a URL is given. Invalid argument: The URL argument requires also the argument for the ID of the file (-i). Test success: missingFileIDWhenURLArgumentTest Test starting: missingFileOrURLArgumentTest Description: Tests the scenario, where no arguments for file or url is given. Invalid argument: Requires either the file argument (-f) or the URL argument (-u). Test success: missingFileOrURLArgumentTest Test starting: missingPillarArgumentTest Description: Tests the different scenarios, with the pillar argument. Invalid argument: The pillar argument (-p) must defined for the Replace operation, only single pillar Replaces are allowed Test success: missingPillarArgumentTest Test starting: unknownPillarArgumentTest Step: Testing against a non-existing pillar id Invalid argument: Random1450487961060pillar is not a valid pillar for collection TwoPillarCollection The collection contains the following pillars: [Pillar1, Pillar2] Test success: unknownPillarArgumentTest Starting testcase NegativeResponseExceptionTest Test starting: testNegativeResponse Description: Test the instantiation of the exception Step: Setup Step: Try to throw such an exception with the response code Test success: testNegativeResponse Starting testcase ReplaceFileClientComponentTest Test starting: replaceClientIdentificationTimeout Description: Tests the handling of a failed identification for the ReplaceClient Step: Initialise the number of pillars and the DeleteClient. Sets the identification timeout to 100 ms. Step: Request a file to be replaced on the default pillar. Stimuli: replaceFile(default-test-file.txt, Pillar1, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@3592e216[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1cfa118b[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@e59eac7[checksumType=SHA1, checksumSalt=, otherChecksumType=], file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, 10, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@31ae2cf[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1cfa118b[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@e59eac7[checksumType=SHA1, checksumSalt=, otherChecksumType=], org.bitrepository.client.TestEventHandler@21ba22e8, null Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileRequest@6d80091d[correlationID=47a98dd8-b84f-4c13-ba69-13c8502d3ca7, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-ReplaceFileClientComponentTest-cibuild01, from=replaceClientIdentificationTimeout, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, fileID=default-test-file.txt, fileSize=] Result: Received event: 47a98dd8: REPLACE_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for replace file Step: Do not respond. Just await the timeout. Result: Received event: 47a98dd8: REPLACE_FILE for file default-test-file.txt: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors The following contributors didn't respond: [Pillar1] Result: Received event: 47a98dd8: REPLACE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor Result: Received event: 47a98dd8: REPLACE_FILE for file default-test-file.txt: FAILED: , Unable to continue operation, contributors unavailable. Test success: replaceClientIdentificationTimeout Test starting: replaceClientOperationTimeout Description: Tests the handling of a failed operation for the ReplaceClient Step: Initialise the number of pillars and the DeleteClient. Sets the operation timeout to 100 ms. Step: Request a file to be replaced on the default pillar. Stimuli: replaceFile(default-test-file.txt, Pillar1, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@4e1e9826[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@d434ffe[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7b165203[checksumType=SHA1, checksumSalt=, otherChecksumType=], file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, 10, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@21a86899[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@d434ffe[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7b165203[checksumType=SHA1, checksumSalt=, otherChecksumType=], org.bitrepository.client.TestEventHandler@1b4d1b22, null Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileRequest@ce69b0a[correlationID=3a349298-2823-4102-8dfc-bf982375bcc3, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-ReplaceFileClientComponentTest-cibuild01, from=replaceClientOperationTimeout, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, fileID=default-test-file.txt, fileSize=] Result: Received event: 3a349298: REPLACE_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for replace file Step: Make response for the pillar. Result: Received event: 3a349298: REPLACE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 3a349298: REPLACE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 3a349298: REPLACE_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for replace file Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.ReplaceFileRequest@27a71243[correlationID=3a349298-2823-4102-8dfc-bf982375bcc3, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-ReplaceFileClientComponentTest-cibuild01, from=replaceClientOperationTimeout, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@4e1e9826[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@d434ffe[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7b165203[checksumType=SHA1, checksumSalt=, otherChecksumType=], fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=10, checksumDataForNewFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@21a86899[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@d434ffe[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], checksumRequestForNewFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7b165203[checksumType=SHA1, checksumSalt=, otherChecksumType=]] Step: Validate the steps of the ReplaceClient by going through the events. Step: Do not respond. Just await the timeout. Result: Received event: 3a349298: REPLACE_FILE for file default-test-file.txt: FAILED: , Failed to receive responses from all contributors before timeout(100ms). Missing contributors [Pillar1] Test success: replaceClientOperationTimeout Test starting: replaceClientPillarFailed Description: Tests the handling of a operation failure for the ReplaceClient. Step: Initialise the number of pillars to one Step: Request a file to be replaced on the default pillar. Stimuli: replaceFile(default-test-file.txt, Pillar1, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@38f96672[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6c2b5639[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@278f591a[checksumType=SHA1, checksumSalt=, otherChecksumType=], file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, 0, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@67d8431d[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6c2b5639[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@278f591a[checksumType=SHA1, checksumSalt=, otherChecksumType=], org.bitrepository.client.TestEventHandler@14616362, null Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileRequest@224d7549[correlationID=6657600e-1800-4522-b9c4-7a4947597045, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-ReplaceFileClientComponentTest-cibuild01, from=replaceClientPillarFailed, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, fileID=default-test-file.txt, fileSize=] Result: Received event: 6657600e: REPLACE_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for replace file Step: Make response for the pillar. Result: Received event: 6657600e: REPLACE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 6657600e: REPLACE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 6657600e: REPLACE_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for replace file Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.ReplaceFileRequest@5a32cbdf[correlationID=6657600e-1800-4522-b9c4-7a4947597045, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-ReplaceFileClientComponentTest-cibuild01, from=replaceClientPillarFailed, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@38f96672[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6c2b5639[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@278f591a[checksumType=SHA1, checksumSalt=, otherChecksumType=], fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@67d8431d[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6c2b5639[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], checksumRequestForNewFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@278f591a[checksumType=SHA1, checksumSalt=, otherChecksumType=]] Step: Validate the steps of the ReplaceClient by going through the events. Step: Send a failed response message to the ReplaceClient. Result: Received event: 6657600e: REPLACE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE, Verifying that a failure can be understood! Result: Received event: 6657600e: REPLACE_FILE for file default-test-file.txt: FAILED: , Failed operation. Cause(s): [6657600e: REPLACE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE, Verifying that a failure can be understood!] Test success: replaceClientPillarFailed Test starting: replaceClientTester Description: Tests the ReplaceFileClient. Makes a whole conversation for the replace client for a 'good' scenario. Step: Initialise the number of pillars to one Step: Request a file to be replaced on all pillars (which means only the default pillar). Stimuli: replaceFile(default-test-file.txt, Pillar1, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@76b328e9[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@431fc271[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6b02fa60[checksumType=SHA1, checksumSalt=, otherChecksumType=], file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, 10, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@4090f46c[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@431fc271[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6b02fa60[checksumType=SHA1, checksumSalt=, otherChecksumType=], org.bitrepository.client.TestEventHandler@2f8b78f7, null Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileRequest@123a3b3d[correlationID=4bbcc903-e1d6-42c5-b607-1d1cdecf9571, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-ReplaceFileClientComponentTest-cibuild01, from=replaceClientTester, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, fileID=default-test-file.txt, fileSize=] Result: Received event: 4bbcc903: REPLACE_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for replace file Step: Make response for the pillar. Result: Received event: 4bbcc903: REPLACE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 4bbcc903: REPLACE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 4bbcc903: REPLACE_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for replace file Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.ReplaceFileRequest@2963a8da[correlationID=4bbcc903-e1d6-42c5-b607-1d1cdecf9571, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-ReplaceFileClientComponentTest-cibuild01, from=replaceClientTester, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@76b328e9[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@431fc271[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6b02fa60[checksumType=SHA1, checksumSalt=, otherChecksumType=], fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=10, checksumDataForNewFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@4090f46c[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@431fc271[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], checksumRequestForNewFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6b02fa60[checksumType=SHA1, checksumSalt=, otherChecksumType=]] Step: Validate the steps of the ReplaceClient by going through the events. Step: The pillar sends a progress response to the ReplaceClient. Result: Received event: 4bbcc903: REPLACE_FILE for file default-test-file.txt: PROGRESS: ContributorID Pillar1, First test progress response message Step: Send a final response message to the ReplaceClient. Result: Received event: 4bbcc903: REPLACE_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, checksum for new file: 'org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@4090f46c[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@431fc271[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00]',checksum for replaced file: 'null' Result: Received event: 4bbcc903: REPLACE_FILE for file default-test-file.txt: COMPLETE: Test success: replaceClientTester Test starting: saltedReturnChecksumsForNewFileWithChecksumPillar Description: Tests that the ReplaceClient handles the presence of a ChecksumPillar correctly, when a salted return checksum (which a checksum pillar can't provide) is requested for the new file. Step: Call replaceFile while requesting a salted checksum to be returned. Stimuli: replaceFile(default-test-file.txt, Pillar1, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@2e6fabf5[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@581b72a5[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], null, file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, 0, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@7fab829a[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@581b72a5[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2ff74dc2[checksumType=MD5, checksumSalt={-86}, otherChecksumType=], org.bitrepository.client.TestEventHandler@7c946bca, null Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileRequest@7f99a0a7[correlationID=64fff9f2-b1db-4ac1-9354-2e9a05bb348d, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-ReplaceFileClientComponentTest-cibuild01, from=saltedReturnChecksumsForNewFileWithChecksumPillar, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, fileID=default-test-file.txt, fileSize=] Result: Received event: 64fff9f2: REPLACE_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for replace file Step: Send an identification response with a PillarChecksumSpec element set, indicating that this is a checksum pillar. Result: Received event: 64fff9f2: REPLACE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 64fff9f2: REPLACE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 64fff9f2: REPLACE_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for replace file Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.ReplaceFileRequest@49099d93[correlationID=64fff9f2-b1db-4ac1-9354-2e9a05bb348d, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-ReplaceFileClientComponentTest-cibuild01, from=saltedReturnChecksumsForNewFileWithChecksumPillar, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@2e6fabf5[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@581b72a5[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], checksumRequestForExistingFile=, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@7fab829a[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@581b72a5[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], checksumRequestForNewFile=] Test success: saltedReturnChecksumsForNewFileWithChecksumPillar Test starting: verifyReplaceFileClientFromFactory Description: Testing the initialization through the ModifyComponentFactory. Step: Use the ModifyComponentFactory to instantiate a ReplaceFileClient. Test success: verifyReplaceFileClientFromFactory Starting testcase UnexpectedResponseExceptionTest Test starting: testUnexpectedResponse Description: Test the instantiation of the exception Step: Setup Step: Try to throw such an exception Step: Throw the exception with an embedded exception Test success: testUnexpectedResponse Starting testcase AuditTrailQueryTest Test starting: testBothSequenceNumberFailure Description: Test the creation of a AuditTrailQuery with both SequenceNumber, where max is smalle than min. Test success: testBothSequenceNumberFailure Test starting: testBothSequenceNumberSuccess Description: Test the creation of a AuditTrailQuery with both SequenceNumber, where max is larger than min. Test success: testBothSequenceNumberSuccess Test starting: testNoSequenceNumbers Description: Test that a AuditTrailQuery can be created without any sequence numbers. Test success: testNoSequenceNumbers Test starting: testOnlyMinSequenceNumber Description: Test the creation of a AuditTrailQuery with only the minSequenceNumber Test success: testOnlyMinSequenceNumber Starting testcase GetStatusClientComponentTest Test starting: getAllStatuses Description: Tests the simplest case of getting status for all contributers. Step: Create a GetStatusClient. Step: Retrieve from all contributors in the collection Stimuli: Calling getAuditTrails() Result: Received event: 228f0a66: GET_STATUS: IDENTIFY_REQUEST_SENT: , Identifying contributors for getting status Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetStatusRequest@1361ca55[correlationID=228f0a66-122a-4552-be40-3a0a8202722c, collectionID=, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetStatusClientComponentTest-cibuild01, from=getAllStatuses, to=, version=28, minVersion=24, auditTrailInformation=] Step: Send a identifyResponse from each pillar Result: Received event: 228f0a66: GET_STATUS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 228f0a66: GET_STATUS: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: 228f0a66: GET_STATUS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2] Result: Received event: 228f0a66: GET_STATUS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending GetStatusRequest Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetStatusRequest@441b598f[correlationID=228f0a66-122a-4552-be40-3a0a8202722c, collectionID=, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetStatusClientComponentTest-cibuild01, from=getAllStatuses, to=, version=28, minVersion=24, auditTrailInformation=, contributor=Pillar1] Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetStatusRequest@472bc276[correlationID=228f0a66-122a-4552-be40-3a0a8202722c, collectionID=, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetStatusClientComponentTest-cibuild01, from=getAllStatuses, to=, version=28, minVersion=24, auditTrailInformation=, contributor=Pillar2] Step: Send a final response from pillar 1 Result: Received event: 228f0a66: GET_STATUS: COMPONENT_COMPLETE: ContributorID Pillar1, resulting status: org.bitrepository.bitrepositoryelements.ResultingStatus@557e3e77[statusInfo=org.bitrepository.bitrepositoryelements.StatusInfo@2ebf0e46[statusCode=OK, statusText=Everythings fine..], statusTimestamp=2015-12-19T02:19:22.319+01:00] Step: Send a final response from pillar 2 Result: Received event: 228f0a66: GET_STATUS: COMPONENT_COMPLETE: ContributorID Pillar2, resulting status: org.bitrepository.bitrepositoryelements.ResultingStatus@634d8b77[statusInfo=org.bitrepository.bitrepositoryelements.StatusInfo@3d3b76da[statusCode=OK, statusText=Everythings fine..], statusTimestamp=2015-12-19T02:19:22.320+01:00] Result: Received event: 228f0a66: GET_STATUS: COMPLETE: Test success: getAllStatuses Test starting: incompleteSetOfIdendifyResponses Description: Verify that the GetStatus client works correct without receiving responses from all contributers. Step: Configure 1 second timeout for identifying contributers. The default 2 contributers collection is used Stimuli: Calling getAuditTrails() Result: Received event: f379f5c3: GET_STATUS: IDENTIFY_REQUEST_SENT: , Identifying contributors for getting status Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetStatusRequest@47081932[correlationID=f379f5c3-6cac-4390-9975-3e03792cd2a0, collectionID=, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetStatusClientComponentTest-cibuild01, from=incompleteSetOfIdendifyResponses, to=, version=28, minVersion=24, auditTrailInformation=] Step: Send a identifyResponse from pillar 1 Result: Received event: f379f5c3: GET_STATUS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Step: Wait for timeout event Result: Received event: f379f5c3: GET_STATUS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors The following contributors didn't respond: [Pillar2] Result: Received event: f379f5c3: GET_STATUS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor Result: Received event: f379f5c3: GET_STATUS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: f379f5c3: GET_STATUS: REQUEST_SENT: ContributorID [Pillar1], Sending GetStatusRequest Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetStatusRequest@7e150b26[correlationID=f379f5c3-6cac-4390-9975-3e03792cd2a0, collectionID=, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetStatusClientComponentTest-cibuild01, from=incompleteSetOfIdendifyResponses, to=, version=28, minVersion=24, auditTrailInformation=, contributor=Pillar1] Test success: incompleteSetOfIdendifyResponses Test starting: verifyGetStatusClientFromFactory Test success: verifyGetStatusClientFromFactory Starting testcase DeleteFileClientComponentTest Test starting: deleteClientIdentificationTimeout Description: Tests the handling of a failed identification for the DeleteClient Step: Initialise the number of pillars and the DeleteClient. Sets the identification timeout to 1 sec. Step: Request a file to be deleted on the default pillar. Stimuli: Calling deleteFile(default-test-file.txt, Pillar1, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@1ff55ec8[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@318da38[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6cc86309[checksumType=SHA1, checksumSalt=, otherChecksumType=], eventHandler, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@7c3ed6f1[correlationID=dd85d47c-8a93-4f9f-b0c8-f2ac139bc9cc, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientIdentificationTimeout, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, fileID=default-test-file.txt] Result: Received event: dd85d47c: DELETE_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for delete file Step: Do not respond. Just await the timeout. Result: Received event: dd85d47c: DELETE_FILE for file default-test-file.txt: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors The following contributors didn't respond: [Pillar1] Result: Received event: dd85d47c: DELETE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor Result: Received event: dd85d47c: DELETE_FILE for file default-test-file.txt: FAILED: , Unable to continue operation, contributors unavailable. Test success: deleteClientIdentificationTimeout Test starting: deleteClientOperationTimeout Description: Tests the handling of a failed operation for the DeleteClient Step: Initialise the number of pillars and the DeleteClient. Sets the operation timeout to 100 ms. Step: Request a file to be deleted on the default pillar. Stimuli: Calling deleteFile(default-test-file.txt, Pillar1, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@4e9c2f21[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@370a59d4[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6668a3d4[checksumType=SHA1, checksumSalt=, otherChecksumType=], eventHandler, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@f95d318[correlationID=2a8bac74-bb2d-4164-9e7a-f625cd122235, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientOperationTimeout, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, fileID=default-test-file.txt] Result: Received event: 2a8bac74: DELETE_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for delete file Step: Make response for the pillar. Result: Received event: 2a8bac74: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 2a8bac74: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 2a8bac74: DELETE_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for deleting file Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.DeleteFileRequest@457e29ca[correlationID=2a8bac74-bb2d-4164-9e7a-f625cd122235, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientOperationTimeout, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@4e9c2f21[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@370a59d4[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6668a3d4[checksumType=SHA1, checksumSalt=, otherChecksumType=]] Step: Validate the steps of the DeleteClient by going through the events. Step: Do not respond. Just await the timeout. Result: Received event: 2a8bac74: DELETE_FILE for file default-test-file.txt: FAILED: , Failed to receive responses from all contributors before timeout(100ms). Missing contributors [Pillar1] Test success: deleteClientOperationTimeout Test starting: deleteClientOtherPillarFailedDuringIdentification Description: Tests the handling of a identification failure for a pillar for the DeleteClient. Step: Request a file to be deleted on the pillar1. Stimuli: Calling deleteFile(default-test-file.txt, Pillar1, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@7417b08f[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7dbee2b6[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-12-19T02:19:25.099+01:00], null, eventHandler, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@57bae294[correlationID=24efdcbf-69a4-4451-9603-8d37e38b84bc, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientOtherPillarFailedDuringIdentification, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, fileID=default-test-file.txt] Result: Received event: 24efdcbf: DELETE_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for delete file Step: Send a failed response from pillar2. Step: Send a ok response from pillar1. Result: Received event: 24efdcbf: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 24efdcbf: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 24efdcbf: DELETE_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for deleting file Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.DeleteFileRequest@127a77db[correlationID=24efdcbf-69a4-4451-9603-8d37e38b84bc, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientOtherPillarFailedDuringIdentification, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@7417b08f[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7dbee2b6[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-12-19T02:19:25.099+01:00], checksumRequestForExistingFile=] Step: Send a final response message from pillar 1 to the DeleteClient. Result: Received event: 24efdcbf: DELETE_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, DeleteFileResult=null Result: Received event: 24efdcbf: DELETE_FILE for file default-test-file.txt: COMPLETE: Test success: deleteClientOtherPillarFailedDuringIdentification Test starting: deleteClientPillarFailedDuringPerform Description: Tests the handling of a operation failure for the DeleteClient. Step: Initialise the number of pillars to one Step: Request a file to be deleted on the default pillar. Stimuli: Calling deleteFile(default-test-file.txt, Pillar1, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@11606071[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2dfe32d6[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@74352685[checksumType=SHA1, checksumSalt=, otherChecksumType=], eventHandler, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@68547c81[correlationID=ddec7ea1-0230-4c5f-8151-0c57c120f759, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientPillarFailedDuringPerform, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, fileID=default-test-file.txt] Result: Received event: ddec7ea1: DELETE_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for delete file Step: Make response for the pillar. Result: Received event: ddec7ea1: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: ddec7ea1: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: ddec7ea1: DELETE_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for deleting file Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.DeleteFileRequest@26110f12[correlationID=ddec7ea1-0230-4c5f-8151-0c57c120f759, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientPillarFailedDuringPerform, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@11606071[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2dfe32d6[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@74352685[checksumType=SHA1, checksumSalt=, otherChecksumType=]] Step: Validate the steps of the DeleteClient by going through the events. Step: Send a failed response message to the DeleteClient. Result: Received event: ddec7ea1: DELETE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE, Verifying that a failure can be understood! Result: Received event: ddec7ea1: DELETE_FILE for file default-test-file.txt: FAILED: , Failed operation. Cause(s): [ddec7ea1: DELETE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE, Verifying that a failure can be understood!] Test success: deleteClientPillarFailedDuringPerform Test starting: deleteClientSpecifiedPillarFailedDuringIdentification Description: Tests the handling of a identification failure for a pillar for the DeleteClient. Step: Request a file to be deleted on the pillar1. Stimuli: Calling deleteFile(default-test-file.txt, Pillar1, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@2ab826c0[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7d07c7a3[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-12-19T02:19:26.528+01:00], null, eventHandler, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@3bec3feb[correlationID=6a5140d6-ec67-40a0-a392-b382063d182e, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientSpecifiedPillarFailedDuringIdentification, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, fileID=default-test-file.txt] Result: Received event: 6a5140d6: DELETE_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for delete file Step: Send a failed response from pillar1. Result: Received event: 6a5140d6: DELETE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: IDENTIFICATION_NEGATIVE Result: Received event: 6a5140d6: DELETE_FILE for file default-test-file.txt: FAILED: , Can not continue with delete operation, as Pillar1 is unable to perform the deletion. Test success: deleteClientSpecifiedPillarFailedDuringIdentification Test starting: deleteClientTester Description: Tests the DeleteClient. Makes a whole conversation for the delete client for a 'good' scenario. Step: Initialise the number of pillars to one Step: Request a file to be deleted on all pillars (which means only the default pillar). Stimuli: Calling deleteFile(default-test-file.txt, Pillar1, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@60bb53c8[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7b59e106[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@4f72b9db[checksumType=SHA1, checksumSalt=, otherChecksumType=], eventHandler, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@3b688205[correlationID=37d601ea-fcb7-4339-98a3-ab79ac09ec1e, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientTester, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, fileID=default-test-file.txt] Result: Received event: 37d601ea: DELETE_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for delete file Step: Make response for the pillar. Result: Received event: 37d601ea: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 37d601ea: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 37d601ea: DELETE_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for deleting file Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.DeleteFileRequest@3592235a[correlationID=37d601ea-fcb7-4339-98a3-ab79ac09ec1e, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientTester, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@60bb53c8[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7b59e106[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@4f72b9db[checksumType=SHA1, checksumSalt=, otherChecksumType=]] Step: Validate the steps of the DeleteClient by going through the events. Step: The pillar sends a progress response to the DeleteClient. Result: Received event: 37d601ea: DELETE_FILE for file default-test-file.txt: PROGRESS: ContributorID Pillar1, First test progress response message Step: Send a final response message to the DeleteClient. Result: Received event: 37d601ea: DELETE_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, DeleteFileResult=null Result: Received event: 37d601ea: DELETE_FILE for file default-test-file.txt: COMPLETE: Test success: deleteClientTester Test starting: deleteOnChecksumPillar Description: Verify that the DeleteClient works correctly when a checksum pillar is present. Step: Request a file to be deleted on the pillar1. Stimuli: Calling deleteFile(default-test-file.txt, Pillar1, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@73a525c6[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2d313cad[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-12-19T02:19:26.801+01:00], null, eventHandler, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@1479279c[correlationID=01dd5c68-457a-4e80-adb0-85aafa6a199a, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteOnChecksumPillar, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, fileID=default-test-file.txt] Result: Received event: 01dd5c68: DELETE_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for delete file Step: Send an identification response from pillar2. Step: Send a response from pillar1 with PillarChecksumSpec element set, indicating that this is a checksum pillar. Result: Received event: 01dd5c68: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 01dd5c68: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 01dd5c68: DELETE_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for deleting file Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.DeleteFileRequest@6a37a2d8[correlationID=01dd5c68-457a-4e80-adb0-85aafa6a199a, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteOnChecksumPillar, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@73a525c6[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2d313cad[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-12-19T02:19:26.801+01:00], checksumRequestForExistingFile=] Test success: deleteOnChecksumPillar Test starting: deleteOnChecksumPillarWithDefaultReturnChecksumType Description: Verify that the DeleteClient works correctly when a return checksum of the default typeis requested. Step: Request a file to be deleted on the pillar1. The call should include a request for a check sum of the default type Stimuli: Calling deleteFile(default-test-file.txt, Pillar1, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@3a4f4ec9[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@40a75caf[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-12-19T02:19:29.002+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2f816d78[checksumType=MD5, checksumSalt=, otherChecksumType=], eventHandler, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@556389bb[correlationID=4b880c15-2289-41d2-b84c-c2a98da2c671, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteOnChecksumPillarWithDefaultReturnChecksumType, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, fileID=default-test-file.txt] Result: Received event: 4b880c15: DELETE_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for delete file Step: Send a response from pillar1 with PillarChecksumSpec element set, indicating that this is a checksum pillar. Result: Received event: 4b880c15: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 4b880c15: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 4b880c15: DELETE_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for deleting file Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.DeleteFileRequest@6f22c8e0[correlationID=4b880c15-2289-41d2-b84c-c2a98da2c671, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteOnChecksumPillarWithDefaultReturnChecksumType, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@3a4f4ec9[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@40a75caf[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-12-19T02:19:29.002+01:00], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2f816d78[checksumType=MD5, checksumSalt=, otherChecksumType=]] Test success: deleteOnChecksumPillarWithDefaultReturnChecksumType Test starting: deleteOnChecksumPillarWithSaltedReturnChecksumType Description: Verify that the DeleteClient works correctly when a return checksum with a salt is requested. Step: Request a file to be deleted on the pillar1. The call should include a request for a salted check sum Stimuli: Calling deleteFile(default-test-file.txt, Pillar1, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@70164894[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@a25f849[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-12-19T02:19:29.177+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@3d63158f[checksumType=MD5, checksumSalt={-86}, otherChecksumType=], eventHandler, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@5ed6eedb[correlationID=a4747f7d-d4d9-4ca3-9aeb-9027b675ebff, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteOnChecksumPillarWithSaltedReturnChecksumType, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, fileID=default-test-file.txt] Result: Received event: a4747f7d: DELETE_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for delete file Step: Send a response from pillar1 with PillarChecksumSpec element set, indicating that this is a checksum pillar. Result: Received event: a4747f7d: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: a4747f7d: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: a4747f7d: DELETE_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for deleting file Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.DeleteFileRequest@39041b0c[correlationID=a4747f7d-d4d9-4ca3-9aeb-9027b675ebff, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteOnChecksumPillarWithSaltedReturnChecksumType, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@70164894[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@a25f849[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-12-19T02:19:29.177+01:00], checksumRequestForExistingFile=] Test success: deleteOnChecksumPillarWithSaltedReturnChecksumType Test starting: fileAlreadyDeletedFromPillar Description: Test that a delete on a pillar completes successfully when the file is missing (has already been deleted). This is a test of the Idempotent behaviour of the delete client Step: Request a file to be deleted on pillar1. Stimuli: Calling deleteFile(default-test-file.txt, Pillar1, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@48b0123a[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1be36b12[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-12-19T02:19:29.417+01:00], null, eventHandler, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@6f942437[correlationID=88493177-aebc-418a-a8ca-fa6e1dcc5d26, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=fileAlreadyDeletedFromPillar, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, fileID=default-test-file.txt] Result: Received event: 88493177: DELETE_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for delete file Step: Send a identify response from Pillar1 with a missing file response. Result: Received event: 88493177: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 88493177: DELETE_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, DeleteFileResult=null Result: Received event: 88493177: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [] Result: Received event: 88493177: DELETE_FILE for file default-test-file.txt: COMPLETE: Step: The client should then continue to the performing phase and finish immediately as the pillar has already had the file removed apparently . Step: Send a identify response from Pillar2 Test success: fileAlreadyDeletedFromPillar Test starting: verifyDeleteClientFromFactory Description: Testing the initialization through the ModifyComponentFactory. Step: Use the ModifyComponentFactory to instantiate a PutFileClient. Test success: verifyDeleteClientFromFactory Starting testcase GetFileIDsCmdTest Test starting: defaultSuccessScenarioTest Description: Tests simplest arguments for running the CmdLineClient Test success: defaultSuccessScenarioTest Test starting: fileArgumentTest Description: Tests the argument for a specific file. Test success: fileArgumentTest Test starting: missingCollectionArgumentTest Description: Tests the scenario, where the collection arguments is missing. Takes the following arguments: -s The path to the directory with the settings files for the client -k The path to the file containing the private key. -v Makes the client more verbose -c The id for the collection to perform the operation on. -i The id for the file to perform the operation on. -p [OPTIONAL] The id of the pillar where the should be performed. If undefined the operations is performed on all pillars. Missing argument: Missing required option: c Test success: missingCollectionArgumentTest Test starting: specificPillarArgumentTest Description: Test argument for a specific pillar Test success: specificPillarArgumentTest Test starting: unknownPillarArgumentTest Description: Testing against a non-existing pillar id -> Should fail Invalid argument: Random1450487971006pillar is not a valid pillar for collection TwoPillarCollection The collection contains the following pillars: [Pillar1, Pillar2] Test success: unknownPillarArgumentTest Starting testcase ChecksumExtractionUtilsTest Test starting: testDefaultChecksumSpec Description: Test that the default checksum is retrieved when no arguments are given. Test success: testDefaultChecksumSpec Test starting: testDefaultChecksumSpecWithSaltArgument Description: Test that the HMAC version of default checksum is retrieved when the salt arguments are given. Test success: testDefaultChecksumSpecWithSaltArgument Test starting: testNonSaltChecksumSpecWithSaltArgument Description: Test that a salt checksum type is retrieved even though a non-salt checksum algorithm it is given as argument, but a salt argument also is given. Test success: testNonSaltChecksumSpecWithSaltArgument Test starting: testNonSaltChecksumSpecWithoutSaltArgument Description: Test that a non-salt checksum type is retrieved when it is given as argument, and no salt arguments are given. Test success: testNonSaltChecksumSpecWithoutSaltArgument Test starting: testSaltChecksumSpecWithSaltArgument Description: Test that a salt checksum type is retrieved when the salt checksum algorithm it is given as argument, and a salt argument also is given. Test success: testSaltChecksumSpecWithSaltArgument Test starting: testSaltChecksumSpecWithoutSaltArgument Description: Test that a non-salt checksum type is retrieved even though a salt checksum algorithm it is given as argument, but no salt argument also is given. Test success: testSaltChecksumSpecWithoutSaltArgument Starting testcase AuditTrailClientComponentTest Test starting: getAllAuditTrailsTest Description: Tests the simplest case of getting all audit trail event for all contributers. Step: Create a AuditTrailClient. Step: Retrieve all audit trails from the collection by calling with a null componentQueries array Stimuli: Calling getAuditTrails(null, default-test-file.txt, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@2ba6f3f5[correlationID=f81b891f-cca2-40b8-b1a0-bd799c593673, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=getAllAuditTrailsTest, to=, version=28, minVersion=24, auditTrailInformation=] Result: Received event: f81b891f: GET_AUDIT_TRAILS for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails Step: Send a identifyResponse from each pillar Result: Received event: f81b891f: GET_AUDIT_TRAILS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: f81b891f: GET_AUDIT_TRAILS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: f81b891f: GET_AUDIT_TRAILS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2] Result: Received event: f81b891f: GET_AUDIT_TRAILS for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for audit trails Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@6f1a373d[correlationID=f81b891f-cca2-40b8-b1a0-bd799c593673, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=getAllAuditTrailsTest, to=, version=28, minVersion=24, auditTrailInformation=, contributor=Pillar1, fileID=default-test-file.txt, minSequenceNumber=, maxSequenceNumber=, minTimestamp=, maxTimestamp=, maxNumberOfResults=, resultAddress=] Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@69d02f87[correlationID=f81b891f-cca2-40b8-b1a0-bd799c593673, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=getAllAuditTrailsTest, to=, version=28, minVersion=24, auditTrailInformation=, contributor=Pillar2, fileID=default-test-file.txt, minSequenceNumber=, maxSequenceNumber=, minTimestamp=, maxTimestamp=, maxNumberOfResults=, resultAddress=] Step: Send a final response from pillar 1 Result: Received event: f81b891f: GET_AUDIT_TRAILS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, NumberOfAuditTrailEvents=2, PartialResult=false Step: Send a final response from pillar 2 Result: Received event: f81b891f: GET_AUDIT_TRAILS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2, NumberOfAuditTrailEvents=2, PartialResult=false Result: Received event: f81b891f: GET_AUDIT_TRAILS for file default-test-file.txt: COMPLETE: Test success: getAllAuditTrailsTest Test starting: getSomeAuditTrailsTest Description: Tests the client maps a AuditTrail query correctly to a GetAuditTrail request. Step: Request audit trails from pillar 1 with both min and max sequence number set. Stimuli: Calling getAuditTrails([AuditTrailQuery{componentID='Pillar1, minTimestamp=null, maxTimestamp=null, maxNumberOfResults=10000}minSequenceNumber=1, maxSequenceNumber=3}], null, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@11e32a5e[correlationID=ab6a6034-2a98-4d2b-92cd-d3fe67f22e8f, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=getSomeAuditTrailsTest, to=Pillar1, version=28, minVersion=24, auditTrailInformation=] Result: Received event: ab6a6034: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails Step: Send a identifyResponse from pillar1 Result: Received event: ab6a6034: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: ab6a6034: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: ab6a6034: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1], Sending request for audit trails Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@9ed2b30[correlationID=ab6a6034-2a98-4d2b-92cd-d3fe67f22e8f, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=getSomeAuditTrailsTest, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, contributor=Pillar1, fileID=, minSequenceNumber=1, maxSequenceNumber=3, minTimestamp=, maxTimestamp=, maxNumberOfResults=10000, resultAddress=] Step: Verify no request is sent to pillar2 Step: Send a final response from pillar 1 Result: Received event: ab6a6034: GET_AUDIT_TRAILS: COMPONENT_COMPLETE: ContributorID Pillar1, NumberOfAuditTrailEvents=2, PartialResult=false Result: Received event: ab6a6034: GET_AUDIT_TRAILS: COMPLETE: Test success: getSomeAuditTrailsTest Test starting: incompleteSetOfFinalResponsesTest Description: Verify that the GetAuditTrail client works correct without receiving responses from all contributers. Step: Configure 500 ms second timeout for the operation itself. The default 2 contributers collection is used Stimuli: Calling getAuditTrails(null, null, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@3c87c0cd[correlationID=e90f220c-4a73-4507-9657-cc9aba1085eb, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=incompleteSetOfFinalResponsesTest, to=, version=28, minVersion=24, auditTrailInformation=] Result: Received event: e90f220c: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails Step: Send a identifyResponse from each of the two pillars Result: Received event: e90f220c: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: e90f220c: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: e90f220c: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2] Result: Received event: e90f220c: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for audit trails Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@57b3ac6e[correlationID=e90f220c-4a73-4507-9657-cc9aba1085eb, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=incompleteSetOfFinalResponsesTest, to=, version=28, minVersion=24, auditTrailInformation=, contributor=Pillar1, fileID=, minSequenceNumber=, maxSequenceNumber=, minTimestamp=, maxTimestamp=, maxNumberOfResults=, resultAddress=] Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@55b08ffd[correlationID=e90f220c-4a73-4507-9657-cc9aba1085eb, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=incompleteSetOfFinalResponsesTest, to=, version=28, minVersion=24, auditTrailInformation=, contributor=Pillar2, fileID=, minSequenceNumber=, maxSequenceNumber=, minTimestamp=, maxTimestamp=, maxNumberOfResults=, resultAddress=] Test success: incompleteSetOfFinalResponsesTest Result: The following messages haven't been handled by the testcase: org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@55b08ffd[correlationID=e90f220c-4a73-4507-9657-cc9aba1085eb, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=incompleteSetOfFinalResponsesTest, to=, version=28, minVersion=24, auditTrailInformation=, contributor=Pillar2, fileID=, minSequenceNumber=, maxSequenceNumber=, minTimestamp=, maxTimestamp=, maxNumberOfResults=, resultAddress=] 02:19:33.634 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@55b08ffd[correlationID=e90f220c-4a73-4507-9657-cc9aba1085eb, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=incompleteSetOfFinalResponsesTest, to=, version=28, minVersion=24, auditTrailInformation=, contributor=Pillar2, fileID=, minSequenceNumber=, maxSequenceNumber=, minTimestamp=, maxTimestamp=, maxNumberOfResults=, resultAddress=] Test starting: negativeGetAuditTrailsResponseTest Description: Verify that the GetAuditTrail client works correct when receiving a negative GetAuditTrails response from one contributers. Step: Create a AuditTrailClient. Step: Retrieve all audit trails from the collection by calling with a null componentQueries array Stimuli: Calling getAuditTrails(null, null, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@34feaae[correlationID=fe32e698-1cf2-4de4-a266-d5435824bdff, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=negativeGetAuditTrailsResponseTest, to=, version=28, minVersion=24, auditTrailInformation=] Result: Received event: fe32e698: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails Step: Send a identifyResponse from each of the two pillars Result: Received event: fe32e698: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: fe32e698: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: fe32e698: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2, Pillar1] Result: Received event: fe32e698: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for audit trails Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@7ea20d2b[correlationID=fe32e698-1cf2-4de4-a266-d5435824bdff, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=negativeGetAuditTrailsResponseTest, to=, version=28, minVersion=24, auditTrailInformation=, contributor=Pillar1, fileID=, minSequenceNumber=, maxSequenceNumber=, minTimestamp=, maxTimestamp=, maxNumberOfResults=, resultAddress=] Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@24482cb[correlationID=fe32e698-1cf2-4de4-a266-d5435824bdff, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=negativeGetAuditTrailsResponseTest, to=, version=28, minVersion=24, auditTrailInformation=, contributor=Pillar2, fileID=, minSequenceNumber=, maxSequenceNumber=, minTimestamp=, maxTimestamp=, maxNumberOfResults=, resultAddress=] Step: Send a failed response from pillar 1 Result: Received event: fe32e698: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE, GetAuditTrails failed Step: Send a final response from pillar 2 Result: Received event: fe32e698: GET_AUDIT_TRAILS: COMPONENT_COMPLETE: ContributorID Pillar2, NumberOfAuditTrailEvents=2, PartialResult=false Result: Received event: fe32e698: GET_AUDIT_TRAILS: FAILED: , Failed operation. Cause(s): [fe32e698: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE, GetAuditTrails failed] Test success: negativeGetAuditTrailsResponseTest Test starting: noFinalResponsesTest Description: Tests the the AuditTrailClient handles lack of Final Responses gracefully Step: Set a 100 ms timeout for the operation. Step: Make the client ask for all audit trails. Stimuli: Calling getAuditTrails(null, null, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@8431d16[correlationID=775dc3ad-e0f5-474e-b265-00d09d3498f2, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noFinalResponsesTest, to=, version=28, minVersion=24, auditTrailInformation=] Result: Received event: 775dc3ad: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails Step: Send a identifyResponse from each of the two pillars Result: Received event: 775dc3ad: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 775dc3ad: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: 775dc3ad: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2] Result: Received event: 775dc3ad: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for audit trails Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@56835157[correlationID=775dc3ad-e0f5-474e-b265-00d09d3498f2, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noFinalResponsesTest, to=, version=28, minVersion=24, auditTrailInformation=, contributor=Pillar1, fileID=, minSequenceNumber=, maxSequenceNumber=, minTimestamp=, maxTimestamp=, maxNumberOfResults=, resultAddress=] Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@46384d3c[correlationID=775dc3ad-e0f5-474e-b265-00d09d3498f2, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noFinalResponsesTest, to=, version=28, minVersion=24, auditTrailInformation=, contributor=Pillar2, fileID=, minSequenceNumber=, maxSequenceNumber=, minTimestamp=, maxTimestamp=, maxNumberOfResults=, resultAddress=] Step: Wait for 1 second Result: Received event: 775dc3ad: GET_AUDIT_TRAILS: FAILED: , Failed to receive responses from all contributors before timeout(100ms). Missing contributors [Pillar1, Pillar2] Test success: noFinalResponsesTest Result: The following messages haven't been handled by the testcase: org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@56835157[correlationID=775dc3ad-e0f5-474e-b265-00d09d3498f2, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noFinalResponsesTest, to=, version=28, minVersion=24, auditTrailInformation=, contributor=Pillar1, fileID=, minSequenceNumber=, maxSequenceNumber=, minTimestamp=, maxTimestamp=, maxNumberOfResults=, resultAddress=] 02:19:33.940 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@56835157[correlationID=775dc3ad-e0f5-474e-b265-00d09d3498f2, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noFinalResponsesTest, to=, version=28, minVersion=24, auditTrailInformation=, contributor=Pillar1, fileID=, minSequenceNumber=, maxSequenceNumber=, minTimestamp=, maxTimestamp=, maxNumberOfResults=, resultAddress=] Result: The following messages haven't been handled by the testcase: org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@46384d3c[correlationID=775dc3ad-e0f5-474e-b265-00d09d3498f2, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noFinalResponsesTest, to=, version=28, minVersion=24, auditTrailInformation=, contributor=Pillar2, fileID=, minSequenceNumber=, maxSequenceNumber=, minTimestamp=, maxTimestamp=, maxNumberOfResults=, resultAddress=] 02:19:33.940 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@46384d3c[correlationID=775dc3ad-e0f5-474e-b265-00d09d3498f2, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noFinalResponsesTest, to=, version=28, minVersion=24, auditTrailInformation=, contributor=Pillar2, fileID=, minSequenceNumber=, maxSequenceNumber=, minTimestamp=, maxTimestamp=, maxNumberOfResults=, resultAddress=] Test starting: progressEventsTest Description: Tests that progress events are handled correctly. Step: Create a AuditTrailClient. Step: Retrieve all audit trails from the collection by calling with a null componentQueries array Stimuli: Calling getAuditTrails(null, null, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@67b95f82[correlationID=77aeae3a-6101-4d35-a57c-9a971e595b15, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=progressEventsTest, to=, version=28, minVersion=24, auditTrailInformation=] Result: Received event: 77aeae3a: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails Step: Send a identifyResponse from each of the two pillars Result: Received event: 77aeae3a: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 77aeae3a: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: 77aeae3a: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2, Pillar1] Result: Received event: 77aeae3a: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for audit trails Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@7d254adc[correlationID=77aeae3a-6101-4d35-a57c-9a971e595b15, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=progressEventsTest, to=, version=28, minVersion=24, auditTrailInformation=, contributor=Pillar1, fileID=, minSequenceNumber=, maxSequenceNumber=, minTimestamp=, maxTimestamp=, maxNumberOfResults=, resultAddress=] Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@504d4fb5[correlationID=77aeae3a-6101-4d35-a57c-9a971e595b15, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=progressEventsTest, to=, version=28, minVersion=24, auditTrailInformation=, contributor=Pillar2, fileID=, minSequenceNumber=, maxSequenceNumber=, minTimestamp=, maxTimestamp=, maxNumberOfResults=, resultAddress=] Step: Send a progress accepted response from pillar 1 Result: Received event: 77aeae3a: GET_AUDIT_TRAILS: PROGRESS: ContributorID Pillar1, GetAuditTrails request accepted Step: Send a general progress response from pillar 2 Result: Received event: 77aeae3a: GET_AUDIT_TRAILS: PROGRESS: ContributorID Pillar2, Still progressing Test success: progressEventsTest Test starting: verifyAuditTrailClientFromFactory Test success: verifyAuditTrailClientFromFactory Result: Received event: e90f220c: GET_AUDIT_TRAILS: FAILED: , Failed to receive responses from all contributors before timeout(500ms). Missing contributors [Pillar1, Pillar2] Test starting: collectionIDIncludedInEventsTest Description: Tests the the client provides collectionID in events. Step: Set a 0.5 second operation timeout. Step: Start the operation Stimuli: Calling getAuditTrails(null, null, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@4ebea736[correlationID=a2353b76-49ae-4cc8-95f7-437a46fec969, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=collectionIDIncludedInEventsTest, to=, version=28, minVersion=24, auditTrailInformation=] Result: Received event: a2353b76: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails Step: Send positive responses from the pillar1 and a negative response from pillar2 Result: Received event: a2353b76: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: a2353b76: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE Result: Received event: a2353b76: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: a2353b76: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1], Sending request for audit trails Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@5fe91e94[correlationID=a2353b76-49ae-4cc8-95f7-437a46fec969, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=collectionIDIncludedInEventsTest, to=, version=28, minVersion=24, auditTrailInformation=, contributor=Pillar1, fileID=, minSequenceNumber=, maxSequenceNumber=, minTimestamp=, maxTimestamp=, maxNumberOfResults=, resultAddress=] Step: Wait for 1 second Result: Received event: a2353b76: GET_AUDIT_TRAILS: FAILED: , Failed to receive responses from all contributors before timeout(500ms). Missing contributors [Pillar1] Test success: collectionIDIncludedInEventsTest Test starting: conversationTimeoutTest Description: Tests the the client handles lack of IdentifyPillarResponses gracefully Step: Set a 100 ms ConversationTimeout. Step: Start the operation Stimuli: Calling getAuditTrails(null, null, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@75ee772a[correlationID=7d82db75-a295-4eb1-b860-0ff627b4ac6a, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=conversationTimeoutTest, to=, version=28, minVersion=24, auditTrailInformation=] Result: Received event: 7d82db75: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails 02:19:35.787 WARN o.b.c.c.m.CollectionBasedConversationMediator - Failing timed out conversation 7d82db75-a295-4eb1-b860-0ff627b4ac6a (Age 1008ms) Result: Received event: 7d82db75: GET_AUDIT_TRAILS: FAILED: , Failing timed out conversation 7d82db75-a295-4eb1-b860-0ff627b4ac6a Test success: conversationTimeoutTest Test starting: identificationFailureTest Description: Verify that the client works correctly when a contributor sends a failure response. Step: Start the operation. Stimuli: Calling getAuditTrails(null, null, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@3af3c661[correlationID=81013a6d-b0ba-444f-849d-7ebe3a2160a9, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=identificationFailureTest, to=, version=28, minVersion=24, auditTrailInformation=] Result: Received event: 81013a6d: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails Step: Send a identification response from contributor1 with a FAILURE response code. Result: Received event: 81013a6d: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE Step: Send a identification response from contributor2 with a IDENTIFICATION_POSITIVE response code . Result: Received event: 81013a6d: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: 81013a6d: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2] Result: Received event: 81013a6d: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar2], Sending request for audit trails Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@66a17a8f[correlationID=81013a6d-b0ba-444f-849d-7ebe3a2160a9, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=identificationFailureTest, to=, version=28, minVersion=24, auditTrailInformation=, contributor=Pillar2, fileID=, minSequenceNumber=, maxSequenceNumber=, minTimestamp=, maxTimestamp=, maxNumberOfResults=, resultAddress=] Step: Verify that the client continues to the performing phase. Step: Send a final response message from contributor2 Result: Received event: 81013a6d: GET_AUDIT_TRAILS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false Result: Received event: 81013a6d: GET_AUDIT_TRAILS: FAILED: , Failed operation. Cause(s): [81013a6d: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE] Test success: identificationFailureTest Test starting: identificationNegativeTest Description: Verify that the client works correctly when a contributor sends a negative response. Step: Start the operation. Stimuli: Calling getAuditTrails(null, null, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@4d00d0dc[correlationID=6a2f26a9-aa0a-4907-be01-0471c212a6d4, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=identificationNegativeTest, to=, version=28, minVersion=24, auditTrailInformation=] Result: Received event: 6a2f26a9: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails Step: Send a identification response from contributor1 with a IDENTIFICATION_NEGATIVE response code . Result: Received event: 6a2f26a9: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: IDENTIFICATION_NEGATIVE Step: Send a identification response from contributor2 with a IDENTIFICATION_POSITIVE response code . Result: Received event: 6a2f26a9: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: 6a2f26a9: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2] Result: Received event: 6a2f26a9: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar2], Sending request for audit trails Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@385bbcc9[correlationID=6a2f26a9-aa0a-4907-be01-0471c212a6d4, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=identificationNegativeTest, to=, version=28, minVersion=24, auditTrailInformation=, contributor=Pillar2, fileID=, minSequenceNumber=, maxSequenceNumber=, minTimestamp=, maxTimestamp=, maxNumberOfResults=, resultAddress=] Step: Verify that the client continues to the performing phase. Step: Send a final response message from contributor2 Result: Received event: 6a2f26a9: GET_AUDIT_TRAILS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false Result: Received event: 6a2f26a9: GET_AUDIT_TRAILS: FAILED: , Failed operation. Cause(s): [6a2f26a9: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: IDENTIFICATION_NEGATIVE] Test success: identificationNegativeTest Test starting: noContributorsRespondingTest Description: Tests the the client handles lack of a IdentifyResponse gracefully. More concrete this means that the occurrence of a identification timeout should be handled correctly Step: Set a 100 ms timeout for identifying contributors. Step: Start the operation. Stimuli: Calling getAuditTrails(null, null, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@12953bf1[correlationID=82cc5278-447d-479a-9851-378de063129c, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noContributorsRespondingTest, to=, version=28, minVersion=24, auditTrailInformation=] Result: Received event: 82cc5278: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails Step: Wait for 1 second Result: Received event: 82cc5278: GET_AUDIT_TRAILS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors The following contributors didn't respond: [Pillar1, Pillar2] Result: Received event: 82cc5278: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor Result: Received event: 82cc5278: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor Result: Received event: 82cc5278: GET_AUDIT_TRAILS: FAILED: , Unable to continue operation, contributors unavailable. Test success: noContributorsRespondingTest Result: The following messages haven't been handled by the testcase: org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@12953bf1[correlationID=82cc5278-447d-479a-9851-378de063129c, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noContributorsRespondingTest, to=, version=28, minVersion=24, auditTrailInformation=] 02:19:38.282 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@12953bf1[correlationID=82cc5278-447d-479a-9851-378de063129c, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noContributorsRespondingTest, to=, version=28, minVersion=24, auditTrailInformation=] Test starting: oneContributorNotRespondingTest Description: Verify that the client works correct without receiving identification responses from all contributors. Added fixture: Set the a identification timeout to 100 ms. Step: Start the operation. Stimuli: Calling getAuditTrails(null, null, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@4e92cf86[correlationID=2dc9b184-a4fd-4f1b-834f-ee0858392516, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=oneContributorNotRespondingTest, to=, version=28, minVersion=24, auditTrailInformation=] Result: Received event: 2dc9b184: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails Step: Send a identification response from contributor1. Result: Received event: 2dc9b184: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Step: Wait 1 second. Result: Received event: 2dc9b184: GET_AUDIT_TRAILS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors The following contributors didn't respond: [Pillar2] Result: Received event: 2dc9b184: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor Result: Received event: 2dc9b184: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 2dc9b184: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1], Sending request for audit trails Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@1c6c2441[correlationID=2dc9b184-a4fd-4f1b-834f-ee0858392516, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=oneContributorNotRespondingTest, to=, version=28, minVersion=24, auditTrailInformation=, contributor=Pillar1, fileID=, minSequenceNumber=, maxSequenceNumber=, minTimestamp=, maxTimestamp=, maxNumberOfResults=, resultAddress=] Step: Verify that the client continues to the performing phase. Step: Send a final response upload message Result: Received event: 2dc9b184: GET_AUDIT_TRAILS: COMPONENT_COMPLETE: ContributorID Pillar1, PartialResult=false Result: Received event: 2dc9b184: GET_AUDIT_TRAILS: FAILED: , Failed operation. Cause(s): [2dc9b184: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor] Test success: oneContributorNotRespondingTest Test starting: operationTimeoutTest Description: Tests the the client handles lack of final responses gracefully. Step: Set a 100 ms operation timeout. Step: Start the operation Stimuli: Calling getAuditTrails(null, null, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@4279aac1[correlationID=84160041-08bd-48dd-8bc6-e37593f0d754, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=operationTimeoutTest, to=, version=28, minVersion=24, auditTrailInformation=] Result: Received event: 84160041: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails Step: Send positive responses from the pillar1 and a negative response from pillar2 Result: Received event: 84160041: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 84160041: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE Result: Received event: 84160041: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 84160041: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1], Sending request for audit trails Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@1c578bb6[correlationID=84160041-08bd-48dd-8bc6-e37593f0d754, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=operationTimeoutTest, to=, version=28, minVersion=24, auditTrailInformation=, contributor=Pillar1, fileID=, minSequenceNumber=, maxSequenceNumber=, minTimestamp=, maxTimestamp=, maxNumberOfResults=, resultAddress=] Step: Wait for 1 second Result: Received event: 84160041: GET_AUDIT_TRAILS: FAILED: , Failed to receive responses from all contributors before timeout(100ms). Missing contributors [Pillar1] Test success: operationTimeoutTest Finished testcase Finished suite Finished project Tests run: 156, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 59.237 sec - in TestSuite Results : Tests run: 156, Failures: 0, Errors: 0, Skipped: 0 [JENKINS] Recording test results [INFO] [INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ bitrepository-client --- [INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/target/bitrepository-client-1.7-SNAPSHOT.jar [INFO] [INFO] --- maven-jar-plugin:2.4:test-jar (default) @ bitrepository-client --- [INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/target/bitrepository-client-1.7-SNAPSHOT-tests.jar [INFO] [INFO] --- maven-source-plugin:2.2.1:jar-no-fork (attach-sources-no-fork) @ bitrepository-client --- [INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/target/bitrepository-client-1.7-SNAPSHOT-sources.jar [INFO] [INFO] --- maven-assembly-plugin:2.4:single (make-assembly) @ bitrepository-client --- [INFO] Reading assembly descriptor: src/main/assembly/assembly.xml [INFO] Building tar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/target/bitrepository-client-1.7-SNAPSHOT-distribution.tar.gz [INFO] [INFO] --- maven-install-plugin:2.5.1:install (default-install) @ bitrepository-client --- [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/target/bitrepository-client-1.7-SNAPSHOT.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-client/1.7-SNAPSHOT/bitrepository-client-1.7-SNAPSHOT.jar [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-client/1.7-SNAPSHOT/bitrepository-client-1.7-SNAPSHOT.pom [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/target/bitrepository-client-1.7-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-client/1.7-SNAPSHOT/bitrepository-client-1.7-SNAPSHOT-tests.jar [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/target/bitrepository-client-1.7-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-client/1.7-SNAPSHOT/bitrepository-client-1.7-SNAPSHOT-sources.jar [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/target/bitrepository-client-1.7-SNAPSHOT-distribution.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-client/1.7-SNAPSHOT/bitrepository-client-1.7-SNAPSHOT-distribution.tar.gz [JENKINS] Archiving disabled