[INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building Bitrepository Client 1.6-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 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 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 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@6050462a) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@426e505c[correlationID=449eb7d2-775d-4968-b9f7-18bca3d250b2, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=collectionIDIncludedInEventsTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@614aeccc[fileID=, allFileIDs=true]] Result: Received event: 449eb7d2: 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: 449eb7d2: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 449eb7d2: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE Result: Received event: 449eb7d2: GET_FILE_IDS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 449eb7d2: GET_FILE_IDS: REQUEST_SENT: ContributorID [Pillar1], Sending request for get fileIDs Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@56ba8773[correlationID=449eb7d2-775d-4968-b9f7-18bca3d250b2, 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@6ceb7b5e[fileID=, allFileIDs=true], minTimestamp=, maxTimestamp=, maxNumberOfResults=, resultAddress=] Step: Wait for 1 second Result: Received event: 449eb7d2: 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 getFileIDs(null, null, null, org.bitrepository.client.TestEventHandler@6050462a) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@834831b[correlationID=4767afcf-0921-4a9b-a9c6-09733a3ad6e6, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=conversationTimeoutTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@234a8f27[fileID=, allFileIDs=true]] Result: Received event: 4767afcf: GET_FILE_IDS: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs 02:18:43.735 WARN o.b.c.c.m.CollectionBasedConversationMediator - Failing timed out conversation 4767afcf-0921-4a9b-a9c6-09733a3ad6e6 (Age 1009ms) Result: Received event: 4767afcf: GET_FILE_IDS: FAILED: , Failing timed out conversation 4767afcf-0921-4a9b-a9c6-09733a3ad6e6 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 getFileIDs(null, null, null, org.bitrepository.client.TestEventHandler@6050462a) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@3491e86e[correlationID=a4664d5b-c909-49e7-98c3-dc8d9ece2f8c, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=identificationFailureTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@68f32020[fileID=, allFileIDs=true]] Result: Received event: a4664d5b: 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: a4664d5b: 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: a4664d5b: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: a4664d5b: GET_FILE_IDS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2] Result: Received event: a4664d5b: GET_FILE_IDS: REQUEST_SENT: ContributorID [Pillar2], Sending request for get fileIDs Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@19b047fe[correlationID=a4664d5b-c909-49e7-98c3-dc8d9ece2f8c, 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@22590e3e[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: a4664d5b: GET_FILE_IDS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false Result: Received event: a4664d5b: GET_FILE_IDS: FAILED: , Failed operation. Cause(s): [a4664d5b: 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 getFileIDs(null, null, null, org.bitrepository.client.TestEventHandler@6050462a) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@5e8cda75[correlationID=80db65f1-3aa9-410b-a9ca-731a0a1072e6, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=identificationNegativeTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@3f049056[fileID=, allFileIDs=true]] Result: Received event: 80db65f1: 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: 80db65f1: 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: 80db65f1: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: 80db65f1: GET_FILE_IDS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2] Result: Received event: 80db65f1: GET_FILE_IDS: REQUEST_SENT: ContributorID [Pillar2], Sending request for get fileIDs Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@3e1a3801[correlationID=80db65f1-3aa9-410b-a9ca-731a0a1072e6, 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@6fd12c5[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: 80db65f1: GET_FILE_IDS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false Result: Received event: 80db65f1: GET_FILE_IDS: FAILED: , Failed operation. Cause(s): [80db65f1: 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 getFileIDs(null, null, null, org.bitrepository.client.TestEventHandler@6050462a) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@1ba359bd[correlationID=2cc7f734-6333-42d3-bde4-be6641c8e756, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=noContributorsRespondingTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@62e93c3a[fileID=, allFileIDs=true]] Result: Received event: 2cc7f734: GET_FILE_IDS: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs Step: Wait for 1 second Result: Received event: 2cc7f734: GET_FILE_IDS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors The following contributors didn't respond: [Pillar1, Pillar2] Result: Received event: 2cc7f734: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor Result: Received event: 2cc7f734: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor Result: Received event: 2cc7f734: 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@1ba359bd[correlationID=2cc7f734-6333-42d3-bde4-be6641c8e756, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=noContributorsRespondingTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@62e93c3a[fileID=, allFileIDs=true]] 02:18:49.916 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@1ba359bd[correlationID=2cc7f734-6333-42d3-bde4-be6641c8e756, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=noContributorsRespondingTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@62e93c3a[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 getFileIDs(null, null, null, org.bitrepository.client.TestEventHandler@6050462a) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@5f254608[correlationID=5650804c-9b7f-4b1f-9280-57a44c466ab7, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=oneContributorNotRespondingTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@2eeb0f9b[fileID=, allFileIDs=true]] Result: Received event: 5650804c: GET_FILE_IDS: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs Step: Send a identification response from contributor1. Result: Received event: 5650804c: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Step: Wait 1 second. Result: Received event: 5650804c: GET_FILE_IDS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors The following contributors didn't respond: [Pillar2] Result: Received event: 5650804c: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor Result: Received event: 5650804c: GET_FILE_IDS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 5650804c: GET_FILE_IDS: REQUEST_SENT: ContributorID [Pillar1], Sending request for get fileIDs Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@47b260eb[correlationID=5650804c-9b7f-4b1f-9280-57a44c466ab7, 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@4975966d[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: 5650804c: GET_FILE_IDS: COMPONENT_COMPLETE: ContributorID Pillar1, PartialResult=false Result: Received event: 5650804c: GET_FILE_IDS: FAILED: , Failed operation. Cause(s): [5650804c: 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 getFileIDs(null, null, null, org.bitrepository.client.TestEventHandler@6050462a) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@54d1608f[correlationID=02607c04-0350-4d77-ba82-140e9496d6df, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=operationTimeoutTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@7e7fe6d[fileID=, allFileIDs=true]] Result: Received event: 02607c04: 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: 02607c04: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 02607c04: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE Result: Received event: 02607c04: GET_FILE_IDS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 02607c04: GET_FILE_IDS: REQUEST_SENT: ContributorID [Pillar1], Sending request for get fileIDs Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@24386839[correlationID=02607c04-0350-4d77-ba82-140e9496d6df, 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@7b32b129[fileID=, allFileIDs=true], minTimestamp=, maxTimestamp=, maxNumberOfResults=, resultAddress=] Step: Wait for 1 second Result: Received event: 02607c04: GET_FILE_IDS: FAILED: , Failed to receive responses from all contributors before timeout(100ms). Missing contributors [Pillar1] Test success: operationTimeoutTest 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: Random1449191933008pillar 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@5cffec7[correlationID=29235e92-a570-49da-b993-f98604401e3c, 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: 29235e92: 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: 29235e92: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID THE-AVERAGE-PILLAR Result: Received event: 29235e92: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID THE-FAST-PILLAR Result: Received event: 29235e92: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID THE-SLOW-PILLAR Result: Received event: 29235e92: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [THE-FAST-PILLAR] Result: Received event: 29235e92: 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@e07b4db[correlationID=29235e92-a570-49da-b993-f98604401e3c, 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@38e00b47[correlationID=12c7743d-a36f-4a49-b852-b11094c1cc01, 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: 12c7743d: 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: 12c7743d: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 12c7743d: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 12c7743d: 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@425b5fe2[correlationID=12c7743d-a36f-4a49-b852-b11094c1cc01, 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:18:54.528 WARN o.b.c.c.m.CollectionBasedConversationMediator - Failing timed out conversation 12c7743d-a36f-4a49-b852-b11094c1cc01 (Age 1010ms) Result: Received event: 12c7743d: GET_FILE for file default-test-file.txt: FAILED: , Failing timed out conversation 12c7743d-a36f-4a49-b852-b11094c1cc01 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@16e907b6[correlationID=23ccb9b2-e86d-4da4-bf89-1bfe2e9e21e1, 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: 23ccb9b2: 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: 23ccb9b2: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 23ccb9b2: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: 23ccb9b2: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 23ccb9b2: 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@23ec2bdc[correlationID=23ccb9b2-e86d-4da4-bf89-1bfe2e9e21e1, 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: 23ccb9b2: GET_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE Result: Received event: 23ccb9b2: GET_FILE for file default-test-file.txt: FAILED: , Failed to get file from Pillar1, org.bitrepository.bitrepositoryelements.ResponseInfo@631944d4[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@4cd5fc46[correlationID=2a857d79-86a8-4a45-b372-6e2bd145d8ca, 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: 2a857d79: 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: 2a857d79: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: 2a857d79: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2] Result: Received event: 2a857d79: 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@3221588e[correlationID=2a857d79-86a8-4a45-b372-6e2bd145d8ca, 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: 2a857d79: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2 Result: Received event: 2a857d79: 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@4a0c3aa8[correlationID=f986d617-75a5-4d1d-a01b-ecba7925bfe5, 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: f986d617: 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: f986d617: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Step: Wait 1 second. Result: Received event: f986d617: 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: f986d617: GET_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor Result: Received event: f986d617: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: f986d617: 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@4d4a0b9b[correlationID=f986d617-75a5-4d1d-a01b-ecba7925bfe5, 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: f986d617: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1 Result: Received event: f986d617: 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@181098bf[correlationID=8bd4be18-20e9-441c-a416-9ae97bbcd058, 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: 8bd4be18: 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: 8bd4be18: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: 8bd4be18: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2] Result: Received event: 8bd4be18: 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@6a552721[correlationID=8bd4be18-20e9-441c-a416-9ae97bbcd058, 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: 8bd4be18: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2 Result: Received event: 8bd4be18: 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@360a3106[correlationID=c1bba5ad-c919-4f04-9bef-b1dbb1d563b6, 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: c1bba5ad: 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: c1bba5ad: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: c1bba5ad: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2] Result: Received event: c1bba5ad: 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@7e9a836[correlationID=c1bba5ad-c919-4f04-9bef-b1dbb1d563b6, 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: c1bba5ad: GET_FILE for file default-test-file.txt: PROGRESS: ContributorID Pillar2, First test progress response message Step: Send a GetFileFinalResponse. Result: Received event: c1bba5ad: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2 Result: Received event: c1bba5ad: 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@44864ebe[correlationID=b21214a1-d480-42ba-b8a9-d898278844f4, 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: b21214a1: 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: b21214a1: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: b21214a1: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: b21214a1: 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@408f70ab[correlationID=b21214a1-d480-42ba-b8a9-d898278844f4, 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@5383bf08[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: b21214a1: 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: b21214a1: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1 Result: Received event: b21214a1: 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@215a329c[correlationID=6a19d0bf-ce1e-4107-bc02-0ffa87d99ca2, 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: 6a19d0bf: GET_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetFile Step: Wait for 1 seconds Result: Received event: 6a19d0bf: 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: 6a19d0bf: GET_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor Result: Received event: 6a19d0bf: GET_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor Result: Received event: 6a19d0bf: 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@71eafb64[correlationID=785e99b4-0a95-4f8c-bb4e-15bf607deefd, 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: 785e99b4: 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: 785e99b4: 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: 785e99b4: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: 785e99b4: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2] Result: Received event: 785e99b4: 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@727f36dd[correlationID=785e99b4-0a95-4f8c-bb4e-15bf607deefd, 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: 785e99b4: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2 Result: Received event: 785e99b4: 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@22cb8e5f[correlationID=e32c1449-4f05-4191-be30-1e784324b40b, 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: e32c1449: 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: e32c1449: 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: e32c1449: 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: e32c1449: 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@5e198c40[correlationID=b28cb24b-8485-4a5f-96f0-14f3e893c755, 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: b28cb24b: 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: b28cb24b: 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: b28cb24b: 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@6050462a) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@542754be[correlationID=7d3c2e16-3a34-494a-8546-e25070c01b66, 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@af57949[fileID=default-test-file.txt, allFileIDs=]] Result: Received event: 7d3c2e16: 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: 7d3c2e16: GET_FILE_IDS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 7d3c2e16: GET_FILE_IDS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 7d3c2e16: 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@5186b78a[correlationID=7d3c2e16-3a34-494a-8546-e25070c01b66, 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@3f6a9ba0[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: 7d3c2e16: 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: 7d3c2e16: GET_FILE_IDS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, PartialResult=false Result: Received event: 7d3c2e16: 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@6050462a) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@539bb233[correlationID=15f42b33-8705-4b7f-aeba-bbe96e7756e8, 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@21b2579d[fileID=default-test-file.txt, allFileIDs=]] Result: Received event: 15f42b33: 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: 15f42b33: GET_FILE_IDS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 15f42b33: GET_FILE_IDS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 15f42b33: 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@796613b7[correlationID=15f42b33-8705-4b7f-aeba-bbe96e7756e8, 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@77622c82[fileID=default-test-file.txt, allFileIDs=], minTimestamp=, maxTimestamp=, maxNumberOfResults=, resultAddress=] Step: The pillar sends a getFileIDsProgressResponse to the GetFileIDsClient. Result: Received event: 15f42b33: 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: 15f42b33: GET_FILE_IDS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, NumberOfFileIDs=1, PartialResult=false Result: Received event: 15f42b33: 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@6167a456) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@54eb2bf6[correlationID=9978b897-b3b6-42c6-9e76-3b17b6c07baf, 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@6d01f2e5[fileID=default-test-file.txt, allFileIDs=]] Result: Received event: 9978b897: 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: 9978b897: GET_FILE_IDS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: 9978b897: GET_FILE_IDS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2] Result: Received event: 9978b897: 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@3a7d6976[correlationID=9978b897-b3b6-42c6-9e76-3b17b6c07baf, 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@37c45154[fileID=default-test-file.txt, allFileIDs=], minTimestamp=, maxTimestamp=, maxNumberOfResults=, resultAddress=] Step: Send a complete event from the pillar Result: Received event: 9978b897: GET_FILE_IDS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false Result: Received event: 9978b897: 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@6050462a) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@5a079446[correlationID=20c17963-3f22-46e7-ad46-d7e2f201c840, 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@694c0ed1[fileID=default-test-file.txt, allFileIDs=]] Result: Received event: 20c17963: 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: 20c17963: GET_FILE_IDS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 20c17963: GET_FILE_IDS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 20c17963: 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@4d071e4b[correlationID=20c17963-3f22-46e7-ad46-d7e2f201c840, 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@2b441609[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: 20c17963: GET_FILE_IDS for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FILE_NOT_FOUND_FAILURE, No such file. Result: Received event: 20c17963: GET_FILE_IDS for file default-test-file.txt: FAILED: , Failed operation. Cause(s): [20c17963: 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=Fri Dec 04 02:18:58 CET 2015, maxTimestamp=Fri Dec 04 02:18:59 CET 2015, maxNumberOfResults=1}, ContributorQuery{componentID='Pillar2, minTimestamp=Fri Dec 04 02:18:59 CET 2015, maxTimestamp=Fri Dec 04 02:18:59 CET 2015, maxNumberOfResults=2}], null, null, org.bitrepository.client.TestEventHandler@6050462a) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@1be3a294[correlationID=b8764796-4d57-41e9-986e-330e84950c56, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=testPaging, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@33502cfe[fileID=, allFileIDs=true]] Result: Received event: b8764796: GET_FILE_IDS: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs Step: Send a IdentifyPillarsForGetFileIDsResponse from both pillars. Result: Received event: b8764796: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: b8764796: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: b8764796: GET_FILE_IDS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2, Pillar1] Result: Received event: b8764796: GET_FILE_IDS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for get fileIDs Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@1728d307[correlationID=b8764796-4d57-41e9-986e-330e84950c56, 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@252d2ac0[fileID=, allFileIDs=true], minTimestamp=2015-12-04T02:18:58.692+01:00, maxTimestamp=2015-12-04T02:18:59.592+01:00, maxNumberOfResults=1, resultAddress=] Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@3f0b5619[correlationID=b8764796-4d57-41e9-986e-330e84950c56, 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@67afc9b6[fileID=, allFileIDs=true], minTimestamp=2015-12-04T02:18:59.592+01:00, maxTimestamp=2015-12-04T02:18:59.692+01:00, maxNumberOfResults=2, resultAddress=] Test success: testPaging Test starting: verifyGetFileIDsClientFromFactory Test success: verifyGetFileIDsClientFromFactory 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: 5261ef05: GET_STATUS: IDENTIFY_REQUEST_SENT: , Identifying contributors for getting status Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetStatusRequest@609edb55[correlationID=5261ef05-687e-47c4-8c09-fab5d702bb07, 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: 5261ef05: GET_STATUS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 5261ef05: GET_STATUS: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: 5261ef05: GET_STATUS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2, Pillar1] Result: Received event: 5261ef05: GET_STATUS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending GetStatusRequest Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetStatusRequest@23e1f610[correlationID=5261ef05-687e-47c4-8c09-fab5d702bb07, 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@1a3a6216[correlationID=5261ef05-687e-47c4-8c09-fab5d702bb07, 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: 5261ef05: GET_STATUS: COMPONENT_COMPLETE: ContributorID Pillar1, resulting status: org.bitrepository.bitrepositoryelements.ResultingStatus@6c0bf8f4[statusInfo=org.bitrepository.bitrepositoryelements.StatusInfo@73476e2d[statusCode=OK, statusText=Everythings fine..], statusTimestamp=2015-12-04T02:19:00.040+01:00] Step: Send a final response from pillar 2 Result: Received event: 5261ef05: GET_STATUS: COMPONENT_COMPLETE: ContributorID Pillar2, resulting status: org.bitrepository.bitrepositoryelements.ResultingStatus@52b77d5e[statusInfo=org.bitrepository.bitrepositoryelements.StatusInfo@6ab6ec33[statusCode=OK, statusText=Everythings fine..], statusTimestamp=2015-12-04T02:19:00.041+01:00] Result: Received event: 5261ef05: 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: 8e97a377: GET_STATUS: IDENTIFY_REQUEST_SENT: , Identifying contributors for getting status Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetStatusRequest@6a9a6a0c[correlationID=8e97a377-0b7f-4769-9190-c29d7f29f73a, 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: 8e97a377: GET_STATUS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Step: Wait for timeout event Result: Received event: 8e97a377: GET_STATUS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors The following contributors didn't respond: [Pillar2] Result: Received event: 8e97a377: GET_STATUS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor Result: Received event: 8e97a377: GET_STATUS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 8e97a377: GET_STATUS: REQUEST_SENT: ContributorID [Pillar1], Sending GetStatusRequest Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetStatusRequest@8489c56[correlationID=8e97a377-0b7f-4769-9190-c29d7f29f73a, 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 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 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: Random1449191944171pillar 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 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@302ab67e[correlationID=f2f7fa9c-13d2-4738-a17b-8229dde4654f, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=getAllAuditTrailsTest, to=, version=28, minVersion=24, auditTrailInformation=] Result: Received event: f2f7fa9c: 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: f2f7fa9c: GET_AUDIT_TRAILS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: f2f7fa9c: GET_AUDIT_TRAILS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: f2f7fa9c: GET_AUDIT_TRAILS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2] Result: Received event: f2f7fa9c: 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@253c82ad[correlationID=f2f7fa9c-13d2-4738-a17b-8229dde4654f, 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@3af8f1ef[correlationID=f2f7fa9c-13d2-4738-a17b-8229dde4654f, 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: f2f7fa9c: 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: f2f7fa9c: GET_AUDIT_TRAILS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2, NumberOfAuditTrailEvents=2, PartialResult=false Result: Received event: f2f7fa9c: 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@62db3787[correlationID=87bab97a-8a6e-45d3-bb36-597eb0e9e191, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=getSomeAuditTrailsTest, to=Pillar1, version=28, minVersion=24, auditTrailInformation=] Result: Received event: 87bab97a: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails Step: Send a identifyResponse from pillar1 Result: Received event: 87bab97a: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 87bab97a: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 87bab97a: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1], Sending request for audit trails Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@68bbd5c2[correlationID=87bab97a-8a6e-45d3-bb36-597eb0e9e191, 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: 87bab97a: GET_AUDIT_TRAILS: COMPONENT_COMPLETE: ContributorID Pillar1, NumberOfAuditTrailEvents=2, PartialResult=false Result: Received event: 87bab97a: 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@37a522c8[correlationID=c6e42424-fcba-44e7-b461-3958302a80b9, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=incompleteSetOfFinalResponsesTest, to=, version=28, minVersion=24, auditTrailInformation=] Result: Received event: c6e42424: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails Step: Send a identifyResponse from each of the two pillars Result: Received event: c6e42424: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: c6e42424: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: c6e42424: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2] Result: Received event: c6e42424: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for audit trails Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@21ec723c[correlationID=c6e42424-fcba-44e7-b461-3958302a80b9, 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@3f41a7ab[correlationID=c6e42424-fcba-44e7-b461-3958302a80b9, 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@3f41a7ab[correlationID=c6e42424-fcba-44e7-b461-3958302a80b9, 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:05.759 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@3f41a7ab[correlationID=c6e42424-fcba-44e7-b461-3958302a80b9, 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@79462469[correlationID=0bf34ae7-e6dd-4dcc-aa89-afee4bf61658, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=negativeGetAuditTrailsResponseTest, to=, version=28, minVersion=24, auditTrailInformation=] Result: Received event: 0bf34ae7: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails Step: Send a identifyResponse from each of the two pillars Result: Received event: 0bf34ae7: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 0bf34ae7: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: 0bf34ae7: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2] Result: Received event: 0bf34ae7: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for audit trails Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@4295b0b8[correlationID=0bf34ae7-e6dd-4dcc-aa89-afee4bf61658, 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@ab8b1ef[correlationID=0bf34ae7-e6dd-4dcc-aa89-afee4bf61658, 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: 0bf34ae7: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE, GetAuditTrails failed Step: Send a final response from pillar 2 Result: Received event: 0bf34ae7: GET_AUDIT_TRAILS: COMPONENT_COMPLETE: ContributorID Pillar2, NumberOfAuditTrailEvents=2, PartialResult=false Result: Received event: 0bf34ae7: GET_AUDIT_TRAILS: FAILED: , Failed operation. Cause(s): [0bf34ae7: 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@24a26847[correlationID=d3150116-d024-4b92-8190-258249d79610, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noFinalResponsesTest, to=, version=28, minVersion=24, auditTrailInformation=] Result: Received event: d3150116: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails Step: Send a identifyResponse from each of the two pillars Result: Received event: d3150116: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: d3150116: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: d3150116: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2, Pillar1] Result: Received event: d3150116: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for audit trails Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@45bedfed[correlationID=d3150116-d024-4b92-8190-258249d79610, 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@7269674d[correlationID=d3150116-d024-4b92-8190-258249d79610, 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: c6e42424: GET_AUDIT_TRAILS: FAILED: , Failed to receive responses from all contributors before timeout(500ms). Missing contributors [Pillar1, Pillar2] Result: Received event: d3150116: 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@45bedfed[correlationID=d3150116-d024-4b92-8190-258249d79610, 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:06.342 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@45bedfed[correlationID=d3150116-d024-4b92-8190-258249d79610, 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@7269674d[correlationID=d3150116-d024-4b92-8190-258249d79610, 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:06.342 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@7269674d[correlationID=d3150116-d024-4b92-8190-258249d79610, 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@6d48f1c[correlationID=9a1c5455-600b-4a02-b7f3-53bfdf172a6f, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=progressEventsTest, to=, version=28, minVersion=24, auditTrailInformation=] Result: Received event: 9a1c5455: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails Step: Send a identifyResponse from each of the two pillars Result: Received event: 9a1c5455: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 9a1c5455: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: 9a1c5455: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2] Result: Received event: 9a1c5455: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for audit trails Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@5911d6e[correlationID=9a1c5455-600b-4a02-b7f3-53bfdf172a6f, 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@271fdeaf[correlationID=9a1c5455-600b-4a02-b7f3-53bfdf172a6f, 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: 9a1c5455: GET_AUDIT_TRAILS: PROGRESS: ContributorID Pillar1, GetAuditTrails request accepted Step: Send a general progress response from pillar 2 Result: Received event: 9a1c5455: GET_AUDIT_TRAILS: PROGRESS: ContributorID Pillar2, Still progressing Test success: progressEventsTest Test starting: verifyAuditTrailClientFromFactory Test success: verifyAuditTrailClientFromFactory 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 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@4ae730ca[correlationID=07e7fd69-2e07-4929-a9eb-7232a10cc804, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=collectionIDIncludedInEventsTest, to=, version=28, minVersion=24, auditTrailInformation=] Result: Received event: 07e7fd69: 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: 07e7fd69: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 07e7fd69: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE Result: Received event: 07e7fd69: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 07e7fd69: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1], Sending request for audit trails Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@33d6886b[correlationID=07e7fd69-2e07-4929-a9eb-7232a10cc804, 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: 07e7fd69: GET_AUDIT_TRAILS: FAILED: , Failed to receive responses from all contributors before timeout(500ms). Missing contributors [Pillar1] Test success: collectionIDIncludedInEventsTest 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@757e13b2, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@fe8344c[correlationID=a725d9d3-d4be-4833-ba17-3087ca1e2c9a, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=collectionIDIncludedInEventsTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@4b330722[fileID=, allFileIDs=true], checksumRequestForExistingFile=] Result: Received event: a725d9d3: 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: a725d9d3: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: a725d9d3: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE Result: Received event: a725d9d3: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: a725d9d3: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar1], Sending GetFileIDsRequest's Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@174bbe8e[correlationID=a725d9d3-d4be-4833-ba17-3087ca1e2c9a, 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@4412b152[fileID=, allFileIDs=true], minTimestamp=, maxTimestamp=, maxNumberOfResults=, checksumRequestForExistingFile=, resultAddress=] Step: Wait for 1 second Result: Received event: a725d9d3: GET_CHECKSUMS: 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@308034aa[correlationID=b58a085c-c73a-4cd1-929d-23fbbcb186a1, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=conversationTimeoutTest, to=, version=28, minVersion=24, auditTrailInformation=] Result: Received event: b58a085c: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails 02:19:08.956 WARN o.b.c.c.m.CollectionBasedConversationMediator - Failing timed out conversation b58a085c-c73a-4cd1-929d-23fbbcb186a1 (Age 1014ms) Result: Received event: b58a085c: GET_AUDIT_TRAILS: FAILED: , Failing timed out conversation b58a085c-c73a-4cd1-929d-23fbbcb186a1 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 getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@757e13b2, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@2300d2b4[correlationID=91cd2307-de74-405d-b720-826ffd2af97b, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=conversationTimeoutTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@b9286ad[fileID=, allFileIDs=true], checksumRequestForExistingFile=] Result: Received event: 91cd2307: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums 02:19:10.077 WARN o.b.c.c.m.CollectionBasedConversationMediator - Failing timed out conversation 91cd2307-de74-405d-b720-826ffd2af97b (Age 1014ms) Result: Received event: 91cd2307: GET_CHECKSUMS: FAILED: , Failing timed out conversation 91cd2307-de74-405d-b720-826ffd2af97b 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@792b4d95[correlationID=8e80b656-1293-4e3a-8e05-1ee030c5f5ff, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=identificationFailureTest, to=, version=28, minVersion=24, auditTrailInformation=] Result: Received event: 8e80b656: 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: 8e80b656: 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: 8e80b656: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: 8e80b656: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2] Result: Received event: 8e80b656: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar2], Sending request for audit trails Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@27779eaa[correlationID=8e80b656-1293-4e3a-8e05-1ee030c5f5ff, 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: 8e80b656: GET_AUDIT_TRAILS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false Result: Received event: 8e80b656: GET_AUDIT_TRAILS: FAILED: , Failed operation. Cause(s): [8e80b656: GET_AUDIT_TRAILS: 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 getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@757e13b2, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@daa6654[correlationID=99bf41cb-d290-4895-8464-17adabd6a725, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=identificationFailureTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@6fd33f5a[fileID=, allFileIDs=true], checksumRequestForExistingFile=] Result: Received event: 99bf41cb: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums Step: Send a identification response from contributor1 with a FAILURE response code. Result: Received event: 99bf41cb: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE Step: Send a identification response from contributor2 with a IDENTIFICATION_POSITIVE response code . Result: Received event: 99bf41cb: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: 99bf41cb: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2] Result: Received event: 99bf41cb: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar2], Sending GetFileIDsRequest's Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@6ec05499[correlationID=99bf41cb-d290-4895-8464-17adabd6a725, 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@308617d3[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: 99bf41cb: GET_CHECKSUMS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false Result: Received event: 99bf41cb: GET_CHECKSUMS: FAILED: , Failed operation. Cause(s): [99bf41cb: GET_CHECKSUMS: 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@bfa82bd[correlationID=25add7fd-98b9-4af3-a4cc-8e0ec4e0f8b2, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=identificationNegativeTest, to=, version=28, minVersion=24, auditTrailInformation=] Result: Received event: 25add7fd: 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: 25add7fd: 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: 25add7fd: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: 25add7fd: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2] Result: Received event: 25add7fd: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar2], Sending request for audit trails Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@384abf00[correlationID=25add7fd-98b9-4af3-a4cc-8e0ec4e0f8b2, 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: 25add7fd: GET_AUDIT_TRAILS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false Result: Received event: 25add7fd: GET_AUDIT_TRAILS: FAILED: , Failed operation. Cause(s): [25add7fd: GET_AUDIT_TRAILS: 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 getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@757e13b2, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@3ab8f900[correlationID=fbc62667-d264-4071-a47a-fbfdf1b2c60c, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=identificationNegativeTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@621508de[fileID=, allFileIDs=true], checksumRequestForExistingFile=] Result: Received event: fbc62667: 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: fbc62667: 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: fbc62667: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: fbc62667: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2] Result: Received event: fbc62667: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar2], Sending GetFileIDsRequest's Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@2cdd3638[correlationID=fbc62667-d264-4071-a47a-fbfdf1b2c60c, 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@5150ba5a[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: fbc62667: GET_CHECKSUMS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false Result: Received event: fbc62667: GET_CHECKSUMS: FAILED: , Failed operation. Cause(s): [fbc62667: GET_CHECKSUMS: 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@6f800942[correlationID=795646f9-7684-4884-9064-6c605a788814, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noContributorsRespondingTest, to=, version=28, minVersion=24, auditTrailInformation=] Result: Received event: 795646f9: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails Step: Wait for 1 second Result: Received event: 795646f9: GET_AUDIT_TRAILS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors The following contributors didn't respond: [Pillar1, Pillar2] Result: Received event: 795646f9: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor Result: Received event: 795646f9: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor Result: Received event: 795646f9: 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@6f800942[correlationID=795646f9-7684-4884-9064-6c605a788814, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noContributorsRespondingTest, to=, version=28, minVersion=24, auditTrailInformation=] 02:19:14.986 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@6f800942[correlationID=795646f9-7684-4884-9064-6c605a788814, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noContributorsRespondingTest, to=, version=28, minVersion=24, auditTrailInformation=] 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@757e13b2, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@7de752dd[correlationID=ae71aa64-c903-49ea-82fa-e9cc0743d2d5, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=noContributorsRespondingTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@729668d7[fileID=, allFileIDs=true], checksumRequestForExistingFile=] Result: Received event: ae71aa64: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums Step: Wait for 1 second Result: Received event: ae71aa64: GET_CHECKSUMS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors The following contributors didn't respond: [Pillar1, Pillar2] Result: Received event: ae71aa64: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor Result: Received event: ae71aa64: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor Result: Received event: ae71aa64: 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@7de752dd[correlationID=ae71aa64-c903-49ea-82fa-e9cc0743d2d5, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=noContributorsRespondingTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@729668d7[fileID=, allFileIDs=true], checksumRequestForExistingFile=] 02:19:15.217 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@7de752dd[correlationID=ae71aa64-c903-49ea-82fa-e9cc0743d2d5, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=noContributorsRespondingTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@729668d7[fileID=, allFileIDs=true], checksumRequestForExistingFile=] 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@29e3c7fe[correlationID=1c748662-1c9a-4f85-b5ea-c5af2e809ba2, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=oneContributorNotRespondingTest, to=, version=28, minVersion=24, auditTrailInformation=] Result: Received event: 1c748662: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails Step: Send a identification response from contributor1. Result: Received event: 1c748662: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Step: Wait 1 second. Result: Received event: 1c748662: GET_AUDIT_TRAILS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors The following contributors didn't respond: [Pillar2] Result: Received event: 1c748662: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor Result: Received event: 1c748662: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 1c748662: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1], Sending request for audit trails Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@5c29008c[correlationID=1c748662-1c9a-4f85-b5ea-c5af2e809ba2, 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: 1c748662: GET_AUDIT_TRAILS: COMPONENT_COMPLETE: ContributorID Pillar1, PartialResult=false Result: Received event: 1c748662: GET_AUDIT_TRAILS: FAILED: , Failed operation. Cause(s): [1c748662: GET_AUDIT_TRAILS: 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 getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@757e13b2, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@66fb1627[correlationID=6699b7e1-e6bf-4b63-adff-2145d70437ed, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=oneContributorNotRespondingTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@1cbd2c1a[fileID=, allFileIDs=true], checksumRequestForExistingFile=] Result: Received event: 6699b7e1: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums Step: Send a identification response from contributor1. Result: Received event: 6699b7e1: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Step: Wait 1 second. Result: Received event: 6699b7e1: GET_CHECKSUMS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors The following contributors didn't respond: [Pillar2] Result: Received event: 6699b7e1: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor Result: Received event: 6699b7e1: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 6699b7e1: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar1], Sending GetFileIDsRequest's Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@398a339a[correlationID=6699b7e1-e6bf-4b63-adff-2145d70437ed, 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@2401f1e3[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: 6699b7e1: GET_CHECKSUMS: COMPONENT_COMPLETE: ContributorID Pillar1, PartialResult=false Result: Received event: 6699b7e1: GET_CHECKSUMS: FAILED: , Failed operation. Cause(s): [6699b7e1: GET_CHECKSUMS: 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@52e7bed1[correlationID=51ef6e38-2414-41ab-9675-527cdafc76a7, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=operationTimeoutTest, to=, version=28, minVersion=24, auditTrailInformation=] Result: Received event: 51ef6e38: 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: 51ef6e38: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 51ef6e38: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE Result: Received event: 51ef6e38: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 51ef6e38: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1], Sending request for audit trails Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@2b686050[correlationID=51ef6e38-2414-41ab-9675-527cdafc76a7, 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: 51ef6e38: GET_AUDIT_TRAILS: 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 getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@757e13b2, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@38388db2[correlationID=bed13858-a8bf-4907-88e0-383265f24e8f, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=operationTimeoutTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@78ffe38[fileID=, allFileIDs=true], checksumRequestForExistingFile=] Result: Received event: bed13858: 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: bed13858: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: bed13858: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE Result: Received event: bed13858: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: bed13858: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar1], Sending GetFileIDsRequest's Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@4cbac3f[correlationID=bed13858-a8bf-4907-88e0-383265f24e8f, 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@7862e409[fileID=, allFileIDs=true], minTimestamp=, maxTimestamp=, maxNumberOfResults=, checksumRequestForExistingFile=, resultAddress=] Step: Wait for 1 second Result: Received event: bed13858: GET_CHECKSUMS: 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@225fe13f, TEST-AUDIT) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@2737fd1d[correlationID=3f023eb9-96e0-44c2-bc98-ec97598bd113, 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@2610cb55[fileID=default-test-file.txt, allFileIDs=], checksumRequestForExistingFile=] Result: Received event: 3f023eb9: 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: 3f023eb9: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 3f023eb9: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: 3f023eb9: GET_CHECKSUMS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2, Pillar1] Result: Received event: 3f023eb9: 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@62b0059[correlationID=3f023eb9-96e0-44c2-bc98-ec97598bd113, 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@264129aa[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@59af828a[correlationID=3f023eb9-96e0-44c2-bc98-ec97598bd113, 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@2177809a[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: 3f023eb9: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, NumberOfChecksums=0, PartialResult=false Result: Received event: 3f023eb9: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2, NumberOfChecksums=0, PartialResult=false Result: Received event: 3f023eb9: 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@59af828a[correlationID=3f023eb9-96e0-44c2-bc98-ec97598bd113, 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@2177809a[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:19:16.327 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: org.bitrepository.bitrepositorymessages.GetChecksumsRequest@59af828a[correlationID=3f023eb9-96e0-44c2-bc98-ec97598bd113, 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@2177809a[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@7b73b5c9, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@4a402ba3[correlationID=cbd7ce32-64d6-4eec-ae42-eae6208bc7d6, 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@65b2f815[fileID=, allFileIDs=true], checksumRequestForExistingFile=] Result: Received event: cbd7ce32: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums Step: Send an identification response from pillar2. Result: Received event: cbd7ce32: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: cbd7ce32: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2] Result: Received event: cbd7ce32: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar2], Sending GetFileIDsRequest's Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@7c3019d6[correlationID=cbd7ce32-64d6-4eec-ae42-eae6208bc7d6, 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@37e628c0[fileID=, allFileIDs=true], minTimestamp=, maxTimestamp=, maxNumberOfResults=, checksumRequestForExistingFile=, resultAddress=] Step: Send a complete event from the pillar Result: Received event: cbd7ce32: GET_CHECKSUMS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false Result: Received event: cbd7ce32: 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@55f4d7be[checksumType=MD5, checksumSalt=, otherChecksumType=], null, org.bitrepository.client.TestEventHandler@113b38ca, TEST-AUDIT) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@7f0dcfe6[correlationID=98eb732f-3d3f-4ccd-b1a7-207d08418207, 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@705ba09a[fileID=default-test-file.txt, allFileIDs=], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@55f4d7be[checksumType=MD5, checksumSalt=, otherChecksumType=]] Result: Received event: 98eb732f: 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: 98eb732f: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 98eb732f: GET_CHECKSUMS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 98eb732f: 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@4b5455c6[correlationID=98eb732f-3d3f-4ccd-b1a7-207d08418207, 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@5a37c1b5[fileID=default-test-file.txt, allFileIDs=], minTimestamp=, maxTimestamp=, maxNumberOfResults=, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@55f4d7be[checksumType=MD5, checksumSalt=, otherChecksumType=], resultAddress=] Step: Send a GetChecksumsFinalResponse to the client from pillar1 Result: Received event: 98eb732f: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, NumberOfChecksums=0, PartialResult=false Result: Received event: 98eb732f: 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@1558b8e7, TEST-AUDIT) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@2df44716[correlationID=d63c8aa0-6c61-416b-9e9a-47498242ecf8, 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@72fad01f[fileID=default-test-file.txt, allFileIDs=], checksumRequestForExistingFile=] Result: Received event: d63c8aa0: 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: d63c8aa0: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: d63c8aa0: GET_CHECKSUMS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: d63c8aa0: 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@2a7d12c8[correlationID=d63c8aa0-6c61-416b-9e9a-47498242ecf8, 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@25be3c66[fileID=default-test-file.txt, allFileIDs=], minTimestamp=, maxTimestamp=, maxNumberOfResults=, checksumRequestForExistingFile=, resultAddress=] Step: Send a error that the file cannot be found. Result: Received event: d63c8aa0: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FILE_NOT_FOUND_FAILURE, No such file. Result: Received event: d63c8aa0: GET_CHECKSUMS for file default-test-file.txt: FAILED: , Failed operation. Cause(s): [d63c8aa0: 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=Fri Dec 04 02:19:17 CET 2015, maxTimestamp=Fri Dec 04 02:19:17 CET 2015, maxNumberOfResults=1}, ContributorQuery{componentID='Pillar2, minTimestamp=Fri Dec 04 02:19:17 CET 2015, maxTimestamp=Fri Dec 04 02:19:18 CET 2015, maxNumberOfResults=2}], null, null, null, org.bitrepository.client.TestEventHandler@757e13b2, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@60d6d8d0[correlationID=b9367e95-e044-4206-9b60-e4f173ae2554, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=testPaging, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@e4e4643[fileID=, allFileIDs=true], checksumRequestForExistingFile=] Result: Received event: b9367e95: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums Step: Send a IdentifyPillarsForGetChecksumsResponse from both pillars. Result: Received event: b9367e95: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: b9367e95: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: b9367e95: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2, Pillar1] Result: Received event: b9367e95: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending GetFileIDsRequest's Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@4e9b4e98[correlationID=b9367e95-e044-4206-9b60-e4f173ae2554, 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@329b6556[fileID=, allFileIDs=true], minTimestamp=2015-12-04T02:19:17.058+01:00, maxTimestamp=2015-12-04T02:19:17.958+01:00, maxNumberOfResults=1, checksumRequestForExistingFile=, resultAddress=] Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@1eba2b8d[correlationID=b9367e95-e044-4206-9b60-e4f173ae2554, 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@6e3f108c[fileID=, allFileIDs=true], minTimestamp=2015-12-04T02:19:17.958+01:00, maxTimestamp=2015-12-04T02:19:18.058+01:00, maxNumberOfResults=2, checksumRequestForExistingFile=, resultAddress=] Test success: testPaging Test starting: verifyGetChecksumsClientFromFactory Test success: verifyGetChecksumsClientFromFactory 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: Random1449191959034pillar is not a valid pillar for collection TwoPillarCollection The collection contains the following pillars: [Pillar1, Pillar2] Test success: unknownPillarArgumentTest 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@5a6a336c[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1105a7e0[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@7b48f52e[checksumType=SHA1, checksumSalt=, otherChecksumType=], file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, 10, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@6c1a08f2[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1105a7e0[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@7b48f52e[checksumType=SHA1, checksumSalt=, otherChecksumType=], org.bitrepository.client.TestEventHandler@6760a74e, null Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileRequest@5b6626e5[correlationID=6aad251c-805e-43f6-803b-c0e73b5862f2, 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: 6aad251c: 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: 6aad251c: 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: 6aad251c: REPLACE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor Result: Received event: 6aad251c: 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@48b3a9ed[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6586480a[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@4962f58e[checksumType=SHA1, checksumSalt=, otherChecksumType=], file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, 10, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@30ecf828[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6586480a[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@4962f58e[checksumType=SHA1, checksumSalt=, otherChecksumType=], org.bitrepository.client.TestEventHandler@65c5c319, null Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileRequest@325401b3[correlationID=6314bd6e-4e47-475e-85d1-c470f2be8192, 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: 6314bd6e: 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: 6314bd6e: REPLACE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 6314bd6e: REPLACE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 6314bd6e: 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@3bbed4fa[correlationID=6314bd6e-4e47-475e-85d1-c470f2be8192, 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@48b3a9ed[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6586480a[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@4962f58e[checksumType=SHA1, checksumSalt=, otherChecksumType=], fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=10, checksumDataForNewFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@30ecf828[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6586480a[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@4962f58e[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: 6314bd6e: 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@5c7f8c9f[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2ce33999[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@677b5145[checksumType=SHA1, checksumSalt=, otherChecksumType=], file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, 0, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@5145dc7[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2ce33999[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@677b5145[checksumType=SHA1, checksumSalt=, otherChecksumType=], org.bitrepository.client.TestEventHandler@25af328e, null Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileRequest@10b5f853[correlationID=996dd983-b602-4c5a-8396-ac008592efeb, 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: 996dd983: 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: 996dd983: REPLACE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 996dd983: REPLACE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 996dd983: 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@a24e874[correlationID=996dd983-b602-4c5a-8396-ac008592efeb, 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@5c7f8c9f[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2ce33999[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@677b5145[checksumType=SHA1, checksumSalt=, otherChecksumType=], fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@5145dc7[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2ce33999[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@677b5145[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: 996dd983: REPLACE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE, Verifying that a failure can be understood! Result: Received event: 996dd983: REPLACE_FILE for file default-test-file.txt: FAILED: , Failed operation. Cause(s): [996dd983: 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@2a89db92[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@22ea05b6[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@235cbf67[checksumType=SHA1, checksumSalt=, otherChecksumType=], file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, 10, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@62414b20[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@22ea05b6[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@235cbf67[checksumType=SHA1, checksumSalt=, otherChecksumType=], org.bitrepository.client.TestEventHandler@6f049b1, null Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileRequest@74453b6c[correlationID=7d619a04-d2a9-478a-8525-826f3d54a158, 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: 7d619a04: 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: 7d619a04: REPLACE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 7d619a04: REPLACE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 7d619a04: 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@5ad4502b[correlationID=7d619a04-d2a9-478a-8525-826f3d54a158, 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@2a89db92[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@22ea05b6[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@235cbf67[checksumType=SHA1, checksumSalt=, otherChecksumType=], fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=10, checksumDataForNewFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@62414b20[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@22ea05b6[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@235cbf67[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: 7d619a04: 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: 7d619a04: REPLACE_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, checksum for new file: 'org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@62414b20[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@22ea05b6[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: 7d619a04: 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@1a9d5a73[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@3a05ba57[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@5773269[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@3a05ba57[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@2e9290bc[checksumType=MD5, checksumSalt={-86}, otherChecksumType=], org.bitrepository.client.TestEventHandler@5e2c19df, null Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileRequest@49ecd74f[correlationID=3c725d50-019c-4a45-be4e-ecd7d67337a0, 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: 3c725d50: 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: 3c725d50: REPLACE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 3c725d50: REPLACE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 3c725d50: 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@4f99290b[correlationID=3c725d50-019c-4a45-be4e-ecd7d67337a0, 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@1a9d5a73[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@3a05ba57[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@5773269[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@3a05ba57[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 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: Random1449191960376pillar 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@67cd916[checksumType=MD5, checksumSalt=, otherChecksumType=], org.bitrepository.client.TestEventHandler@153c5283, TEST-AUDIT-TRAIL) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@2f88c81a[correlationID=1555e229-7cd5-460d-b54a-3d100e634bf9, 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: 1555e229: 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: 1555e229: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Step: Send an normal identification response from pillar2. Result: Received event: 1555e229: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: 1555e229: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2] Result: Received event: 1555e229: 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@48c7f0d9[correlationID=1555e229-7cd5-460d-b54a-3d100e634bf9, 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@67cd916[checksumType=MD5, checksumSalt=, otherChecksumType=]] Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@e083961[correlationID=1555e229-7cd5-460d-b54a-3d100e634bf9, 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@67cd916[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@5fb03284, TEST-AUDIT-TRAIL) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@1dd241a0[correlationID=146d2542-463b-4167-bd87-d7f8892e67c0, 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: 146d2542: 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: 146d2542: 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@4de4c093[responseCode=DUPLICATE_FILE_FAILURE, responseText=Testing the handling of 'DUPLICATE FILE' identification.] (existing file checksum does not match) Result: Received event: 146d2542: 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@5faea3cb[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@169f4020[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={-70}, calculationTimestamp=2015-12-04T02:19:20.662+01:00], null, org.bitrepository.client.TestEventHandler@419e0ee5, TEST-AUDIT-TRAIL) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@6630e32d[correlationID=499d9dbd-b849-4049-81be-71d2b2f217c6, 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: 499d9dbd: 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: 499d9dbd: 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@1100a8f6[responseCode=DUPLICATE_FILE_FAILURE, responseText=Testing the handling of 'DUPLICATE FILE' identification.] (existing file checksum does not match) Result: Received event: 499d9dbd: 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@34fb622b, TEST-AUDIT-TRAIL) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@44259318[correlationID=b48f64ef-d14a-4bb8-91f0-5bbfd48c480b, 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: b48f64ef: 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: b48f64ef: 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@623efc15[responseCode=DUPLICATE_FILE_FAILURE, responseText=Testing the handling of 'DUPLICATE FILE' identification.] Result: Received event: b48f64ef: 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@45559fc8, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@6a2b1cdc[correlationID=1dbbaa09-9f0b-41fb-8daf-92b2c9e55f60, 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: 1dbbaa09: 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: 1dbbaa09: 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: 1dbbaa09: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor Result: Received event: 1dbbaa09: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor Result: Received event: 1dbbaa09: 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@790b51f1, TEST-AUDIT-TRAIL) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@27bdf7d[correlationID=0dd33d58-2d33-40c4-b39f-0fc10ab1fcf8, 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: 0dd33d58: 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: 0dd33d58: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Step: Send an normal identification response from pillar2. Result: Received event: 0dd33d58: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: 0dd33d58: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2] Result: Received event: 0dd33d58: 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@4536cfd3[correlationID=0dd33d58-2d33-40c4-b39f-0fc10ab1fcf8, 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@196a703f[correlationID=0dd33d58-2d33-40c4-b39f-0fc10ab1fcf8, 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@7485c18, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@25ff482a[correlationID=78f72ff2-2deb-46bc-909a-7284e084e07c, 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: 78f72ff2: 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: 78f72ff2: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 78f72ff2: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 78f72ff2: 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@13d2a198[correlationID=78f72ff2-2deb-46bc-909a-7284e084e07c, 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: 78f72ff2: 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: 78f72ff2: PUT_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, requestedChecksumResult=null Result: Received event: 78f72ff2: 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@7779243b, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@21f7bdf[correlationID=bdf88fec-a15c-4feb-b574-ead0d6806eea, 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: bdf88fec: 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: bdf88fec: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: bdf88fec: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: bdf88fec: 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@44c874fe[correlationID=bdf88fec-a15c-4feb-b574-ead0d6806eea, 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@7aaed8a0[correlationID=bdf88fec-a15c-4feb-b574-ead0d6806eea, 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: bdf88fec: 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@31695a9[correlationID=bdf88fec-a15c-4feb-b574-ead0d6806eea, 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: bdf88fec: 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: bdf88fec: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FILE_TRANSFER_FAILURE Result: Received event: bdf88fec: PUT_FILE for file default-test-file.txt: FAILED: , Failed operation. Cause(s): [bdf88fec: 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@7dd1b3c0, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@51386a2e[correlationID=d057acf9-e19b-4136-a96a-8ce9ae8f42ef, 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: d057acf9: 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: d057acf9: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: d057acf9: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: d057acf9: 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@7a3a7f99[correlationID=d057acf9-e19b-4136-a96a-8ce9ae8f42ef, 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@a859cad[correlationID=d057acf9-e19b-4136-a96a-8ce9ae8f42ef, 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: d057acf9: 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: d057acf9: PUT_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, requestedChecksumResult=null Result: Received event: d057acf9: 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@53f7a390, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@2c981784[correlationID=4103c03d-216b-404a-8d02-b1d67a99323e, 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: 4103c03d: 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: 4103c03d: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Step: Await the timeout. Result: Received event: 4103c03d: 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: 4103c03d: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor Result: Received event: 4103c03d: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 4103c03d: 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@68676319[correlationID=4103c03d-216b-404a-8d02-b1d67a99323e, 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: 4103c03d: PUT_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, requestedChecksumResult=null Result: Received event: 4103c03d: PUT_FILE for file default-test-file.txt: FAILED: , Failed operation. Cause(s): [4103c03d: 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@ba27c12, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@3c7a3f0d[correlationID=2f6afc3b-b2a3-417e-b120-f3670a569360, 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: 2f6afc3b: 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: 2f6afc3b: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Step: Await the timeout. Result: Received event: 2f6afc3b: 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: 2f6afc3b: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor Result: Received event: 2f6afc3b: 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@6bcb493e, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@225be644[correlationID=abe0c61b-a530-4498-837b-b0428d22cb2b, 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: abe0c61b: 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: abe0c61b: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: abe0c61b: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: abe0c61b: 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@527afebf[correlationID=abe0c61b-a530-4498-837b-b0428d22cb2b, 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: abe0c61b: 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@6a2c3fc2, TEST-AUDIT-TRAIL) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@37c595f4[correlationID=407efb62-e4b3-4a25-a463-619d34c81525, 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: 407efb62: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file Step: Send pillar response. Result: Received event: 407efb62: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 407efb62: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 407efb62: 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@b0ba49[correlationID=407efb62-e4b3-4a25-a463-619d34c81525, 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: 407efb62: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE, Verifying that a failure can be understood! Result: Received event: 407efb62: PUT_FILE for file default-test-file.txt: FAILED: , Failed operation. Cause(s): [407efb62: 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@380e8b10, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@de3cdeb[correlationID=b6fce54c-35c8-4733-a27b-27d5e85178e0, 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: b6fce54c: 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: b6fce54c: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: b6fce54c: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2] Result: Received event: b6fce54c: 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@1c1b9a9a[correlationID=b6fce54c-35c8-4733-a27b-27d5e85178e0, 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: b6fce54c: PUT_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2, requestedChecksumResult=null Result: Received event: b6fce54c: 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@267f6b32[checksumType=HMAC_MD5, checksumSalt={-86}, otherChecksumType=], org.bitrepository.client.TestEventHandler@3a084fc7, TEST-AUDIT-TRAIL) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@4e457635[correlationID=e974342d-70f6-43b7-88e3-0218686dba79, 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: e974342d: 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: e974342d: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Step: Send an normal identification response from pillar2. Result: Received event: e974342d: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: e974342d: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2] Result: Received event: e974342d: 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@64e4e885[correlationID=e974342d-70f6-43b7-88e3-0218686dba79, 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@175cef2[correlationID=e974342d-70f6-43b7-88e3-0218686dba79, 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@267f6b32[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@584c62b[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@4a43aaad[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-12-04T02:19:22.188+01:00], null, org.bitrepository.client.TestEventHandler@7a8c1916, TEST-AUDIT-TRAIL) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@66f44bef[correlationID=16c7c1b2-f908-4324-bfeb-1405484520de, 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: 16c7c1b2: 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: 16c7c1b2: PUT_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, requestedChecksumResult=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@8fd4fac[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@4c92c66f[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-12-04T02:19:22.191+01:00], File already existed on Pillar1 Step: Send an identification response from the second pillar. Result: Received event: 16c7c1b2: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: 16c7c1b2: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2] Result: Received event: 16c7c1b2: 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@156c2fa2[correlationID=16c7c1b2-f908-4324-bfeb-1405484520de, 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@584c62b[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@4a43aaad[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-12-04T02:19:22.188+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: 16c7c1b2: PUT_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2, requestedChecksumResult=null Result: Received event: 16c7c1b2: 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 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 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: Random1449191964723pillar is not a valid pillar for collection TwoPillarCollection The collection contains the following pillars: [Pillar1, Pillar2] Test success: unknownPillarArgumentTest 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@6c10a403[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@375ef82a[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@76b09f19[checksumType=SHA1, checksumSalt=, otherChecksumType=], eventHandler, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@171301f[correlationID=bf467ea4-3829-4e58-8552-c57810bf3d0b, 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: bf467ea4: 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: bf467ea4: 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: bf467ea4: DELETE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor Result: Received event: bf467ea4: 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@3e727eef[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2497e6d3[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@3930afed[checksumType=SHA1, checksumSalt=, otherChecksumType=], eventHandler, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@5899082a[correlationID=af0c6f81-47e1-45b5-80ec-7abde97bb58e, 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: af0c6f81: 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: af0c6f81: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: af0c6f81: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: af0c6f81: 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@6e0b41cb[correlationID=af0c6f81-47e1-45b5-80ec-7abde97bb58e, 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@3e727eef[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2497e6d3[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@3930afed[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: af0c6f81: 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@66c4fa48[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@11336197[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-12-04T02:19:26.170+01:00], null, eventHandler, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@15c46ce5[correlationID=8d960886-ca69-4fa8-a742-f3b3a4f15411, 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: 8d960886: 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: 8d960886: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 8d960886: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 8d960886: 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@a1ad17d[correlationID=8d960886-ca69-4fa8-a742-f3b3a4f15411, 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@66c4fa48[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@11336197[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-12-04T02:19:26.170+01:00], checksumRequestForExistingFile=] Step: Send a final response message from pillar 1 to the DeleteClient. Result: Received event: 8d960886: DELETE_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, DeleteFileResult=null Result: Received event: 8d960886: 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@3e2f3bc6[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@40a8a626[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@62a9d5e7[checksumType=SHA1, checksumSalt=, otherChecksumType=], eventHandler, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@7b7115c2[correlationID=a91deac9-5686-40c7-969e-9528f64b1d2b, 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: a91deac9: 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: a91deac9: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: a91deac9: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: a91deac9: 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@395be849[correlationID=a91deac9-5686-40c7-969e-9528f64b1d2b, 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@3e2f3bc6[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@40a8a626[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@62a9d5e7[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: a91deac9: DELETE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE, Verifying that a failure can be understood! Result: Received event: a91deac9: DELETE_FILE for file default-test-file.txt: FAILED: , Failed operation. Cause(s): [a91deac9: 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@120d6db2[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@38289dd8[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-12-04T02:19:27.388+01:00], null, eventHandler, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@11c0f55c[correlationID=a3374ac7-e0ad-4868-b532-2ac16a8adbbc, 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: a3374ac7: 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: a3374ac7: DELETE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: IDENTIFICATION_NEGATIVE Result: Received event: a3374ac7: 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@55acd2a8[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@195cca8f[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@7c0e7a[checksumType=SHA1, checksumSalt=, otherChecksumType=], eventHandler, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@2c128268[correlationID=43d5886c-a8db-4219-a03b-266be2406e80, 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: 43d5886c: 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: 43d5886c: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 43d5886c: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 43d5886c: 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@60ef851e[correlationID=43d5886c-a8db-4219-a03b-266be2406e80, 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@55acd2a8[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@195cca8f[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@7c0e7a[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: 43d5886c: 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: 43d5886c: DELETE_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, DeleteFileResult=null Result: Received event: 43d5886c: 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@5e1f3c74[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1e94fe1d[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-12-04T02:19:27.549+01:00], null, eventHandler, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@5e789bd6[correlationID=df044c2d-1888-4658-8a9d-4c74f9f576e5, 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: df044c2d: 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: df044c2d: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: df044c2d: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: df044c2d: 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@56b4e8c0[correlationID=df044c2d-1888-4658-8a9d-4c74f9f576e5, 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@5e1f3c74[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1e94fe1d[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-12-04T02:19:27.549+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@1de1dda1[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@46347cba[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-12-04T02:19:29.644+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6a18283e[checksumType=MD5, checksumSalt=, otherChecksumType=], eventHandler, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@4948d3ef[correlationID=a6fe6821-6b3b-4569-9bf2-cd65b3f9ff02, 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: a6fe6821: 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: a6fe6821: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: a6fe6821: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: a6fe6821: 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@3f6375ee[correlationID=a6fe6821-6b3b-4569-9bf2-cd65b3f9ff02, 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@1de1dda1[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@46347cba[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-12-04T02:19:29.644+01:00], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6a18283e[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@32505319[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7b47355b[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-12-04T02:19:29.724+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@735fc94f[checksumType=MD5, checksumSalt={-86}, otherChecksumType=], eventHandler, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@6de2d8f4[correlationID=1b2c8f0d-7ca7-40a4-94d5-cda7c6582da6, 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: 1b2c8f0d: 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: 1b2c8f0d: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 1b2c8f0d: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 1b2c8f0d: 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@1f358ddf[correlationID=1b2c8f0d-7ca7-40a4-94d5-cda7c6582da6, 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@32505319[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7b47355b[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-12-04T02:19:29.724+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@4014f892[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@5f131b6f[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-12-04T02:19:29.800+01:00], null, eventHandler, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@2c3077bf[correlationID=ec757af2-ed15-44ae-a2e2-ecd4f204ed25, 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: ec757af2: 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: ec757af2: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: ec757af2: DELETE_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, DeleteFileResult=null Result: Received event: ec757af2: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [] Result: Received event: ec757af2: 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 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: Random1449191972012pillar is not a valid pillar for collection TwoPillarCollection The collection contains the following pillars: [Pillar1, Pillar2] Test success: unknownPillarArgumentTest Finished testcase Finished suite Finished project Tests run: 156, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 56.502 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.6-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.6-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.6-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.6-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.6-SNAPSHOT.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-client/1.6-SNAPSHOT/bitrepository-client-1.6-SNAPSHOT.jar [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-client/1.6-SNAPSHOT/bitrepository-client-1.6-SNAPSHOT.pom [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/target/bitrepository-client-1.6-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-client/1.6-SNAPSHOT/bitrepository-client-1.6-SNAPSHOT-tests.jar [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/target/bitrepository-client-1.6-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-client/1.6-SNAPSHOT/bitrepository-client-1.6-SNAPSHOT-sources.jar [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/target/bitrepository-client-1.6-SNAPSHOT-distribution.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-client/1.6-SNAPSHOT/bitrepository-client-1.6-SNAPSHOT-distribution.tar.gz [JENKINS] Archiving disabled