[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 [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 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@4e8e8621[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@4443ef6f[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@7e46d648[checksumType=SHA1, checksumSalt=, otherChecksumType=], eventHandler, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@56ba8773[correlationID=0b48aea2-0ae0-4cda-83d8-55ed08a633c0, 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: 0b48aea2: 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: 0b48aea2: 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: 0b48aea2: DELETE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor Result: Received event: 0b48aea2: 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@5c748168[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6441c486[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@834831b[checksumType=SHA1, checksumSalt=, otherChecksumType=], eventHandler, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@234a8f27[correlationID=61cf1ed5-21bb-411c-a3f0-ecdaa6658cbb, 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: 61cf1ed5: 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: 61cf1ed5: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 61cf1ed5: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 61cf1ed5: 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@6a0659ac[correlationID=61cf1ed5-21bb-411c-a3f0-ecdaa6658cbb, 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@5c748168[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6441c486[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@834831b[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: 61cf1ed5: 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@2b329bbd[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@34819867[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-11-26T02:18:57.800+01:00], null, eventHandler, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@118102ee[correlationID=ec00df07-f178-4845-9a70-fff2366b3d51, 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: ec00df07: 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: ec00df07: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: ec00df07: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: ec00df07: 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@771d1ffb[correlationID=ec00df07-f178-4845-9a70-fff2366b3d51, 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@2b329bbd[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@34819867[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-11-26T02:18:57.800+01:00], checksumRequestForExistingFile=] Step: Send a final response message from pillar 1 to the DeleteClient. Result: Received event: ec00df07: DELETE_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, DeleteFileResult=null Result: Received event: ec00df07: 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@54f4a7f0[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@61a1ea2c[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@149debbb[checksumType=SHA1, checksumSalt=, otherChecksumType=], eventHandler, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@25cd49a4[correlationID=5e55f94e-07ba-4354-81d4-ce3ee6995618, 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: 5e55f94e: 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: 5e55f94e: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 5e55f94e: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 5e55f94e: 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@3ae9d1e2[correlationID=5e55f94e-07ba-4354-81d4-ce3ee6995618, 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@54f4a7f0[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@61a1ea2c[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@149debbb[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: 5e55f94e: DELETE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE, Verifying that a failure can be understood! Result: Received event: 5e55f94e: DELETE_FILE for file default-test-file.txt: FAILED: , Failed operation. Cause(s): [5e55f94e: 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@1aabf50d[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@73c9e8e8[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-11-26T02:18:59.764+01:00], null, eventHandler, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@de8039f[correlationID=18cf0a00-2c05-4092-b1ad-e94343b4831e, 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: 18cf0a00: 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: 18cf0a00: DELETE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: IDENTIFICATION_NEGATIVE Result: Received event: 18cf0a00: 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@1a96d94c[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2a869a16[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@ae202c6[checksumType=SHA1, checksumSalt=, otherChecksumType=], eventHandler, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@46aa712c[correlationID=6d92cbe4-1d80-4e6f-94f8-29d249b9fafb, 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: 6d92cbe4: 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: 6d92cbe4: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 6d92cbe4: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 6d92cbe4: 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@7412ed6b[correlationID=6d92cbe4-1d80-4e6f-94f8-29d249b9fafb, 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@1a96d94c[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2a869a16[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@ae202c6[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: 6d92cbe4: 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: 6d92cbe4: DELETE_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, DeleteFileResult=null Result: Received event: 6d92cbe4: 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@29fd8e67[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@e146f93[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-11-26T02:19:00.362+01:00], null, eventHandler, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@4bd5849e[correlationID=92b39cd0-f195-4b9b-b0aa-701452149bbb, 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: 92b39cd0: 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: 92b39cd0: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 92b39cd0: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 92b39cd0: 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@39909d1a[correlationID=92b39cd0-f195-4b9b-b0aa-701452149bbb, 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@29fd8e67[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@e146f93[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-11-26T02:19:00.362+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@3e4e8fdf[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6a1d6ef2[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-11-26T02:19:02.763+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2721044[checksumType=MD5, checksumSalt=, otherChecksumType=], eventHandler, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@205df5dc[correlationID=8da531ae-a3de-4482-a5fe-119c7d81fe25, 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: 8da531ae: 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: 8da531ae: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 8da531ae: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 8da531ae: 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@6bee793f[correlationID=8da531ae-a3de-4482-a5fe-119c7d81fe25, 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@3e4e8fdf[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6a1d6ef2[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-11-26T02:19:02.763+01:00], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2721044[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@fe87ddd[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@4eea94a4[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-11-26T02:19:03.074+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7c281eb8[checksumType=MD5, checksumSalt={-86}, otherChecksumType=], eventHandler, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@65f40689[correlationID=fe244966-c124-479a-80c1-e5d8cdd6fd8d, 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: fe244966: 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: fe244966: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: fe244966: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: fe244966: 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@33eb6758[correlationID=fe244966-c124-479a-80c1-e5d8cdd6fd8d, 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@fe87ddd[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@4eea94a4[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-11-26T02:19:03.074+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@7061622[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@32d418a9[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-11-26T02:19:03.321+01:00], null, eventHandler, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@52ea0269[correlationID=45419472-abbf-43c2-9082-1cf92c17a0c2, 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: 45419472: 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: 45419472: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 45419472: DELETE_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, DeleteFileResult=null Result: Received event: 45419472: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [] Result: Received event: 45419472: 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: -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 The path to the directory with the settings files for the client -c The id for the collection to perform the operation on. -S [OPTIONAL] The salt of checksum to request in the response. Requires the ChecksumType argument. -v Makes the client more verbose -i The id for the file to perform the operation on. -k The path to the file containing the private key. Missing argument: 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: Random1448500747358pillar 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@23708f14[correlationID=7957fb06-6538-4186-879c-e0204b4dd80f, 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: 7957fb06: 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: 7957fb06: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID THE-AVERAGE-PILLAR Result: Received event: 7957fb06: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID THE-FAST-PILLAR Result: Received event: 7957fb06: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID THE-SLOW-PILLAR Result: Received event: 7957fb06: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [THE-FAST-PILLAR] Result: Received event: 7957fb06: 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@25df2014[correlationID=7957fb06-6538-4186-879c-e0204b4dd80f, 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@3d7b3b18[correlationID=e18f3b6e-65fe-481b-9e41-75663ef2a2c4, 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: e18f3b6e: 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: e18f3b6e: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: e18f3b6e: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: e18f3b6e: 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@1d0dad12[correlationID=e18f3b6e-65fe-481b-9e41-75663ef2a2c4, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=conversationTimeout, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileID=default-test-file.txt, filePart=, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt] Step: Wait for 1 second 02:19:08.769 WARN o.b.c.c.m.CollectionBasedConversationMediator - Failing timed out conversation e18f3b6e-65fe-481b-9e41-75663ef2a2c4 (Age 1009ms) Result: Received event: e18f3b6e: GET_FILE for file default-test-file.txt: FAILED: , Failing timed out conversation e18f3b6e-65fe-481b-9e41-75663ef2a2c4 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@24c84e65[correlationID=a6a58184-3970-4f92-a631-dee1e2e146c6, 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: a6a58184: 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: a6a58184: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: a6a58184: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: a6a58184: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: a6a58184: 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@4604e051[correlationID=a6a58184-3970-4f92-a631-dee1e2e146c6, 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: a6a58184: GET_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE Result: Received event: a6a58184: GET_FILE for file default-test-file.txt: FAILED: , Failed to get file from Pillar1, org.bitrepository.bitrepositoryelements.ResponseInfo@4535bdc6[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@67c2b55d[correlationID=2769c4b0-7290-4895-b7db-89ebe1e788b5, 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: 2769c4b0: 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: 2769c4b0: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: 2769c4b0: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2] Result: Received event: 2769c4b0: 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@6f921e32[correlationID=2769c4b0-7290-4895-b7db-89ebe1e788b5, 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: 2769c4b0: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2 Result: Received event: 2769c4b0: 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@3ddac0b6[correlationID=25f15c1b-1bc1-4a1d-9204-cde1f1dd7631, 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: 25f15c1b: 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: 25f15c1b: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Step: Wait 1 second. Result: Received event: 25f15c1b: 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: 25f15c1b: GET_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor Result: Received event: 25f15c1b: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 25f15c1b: 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@54f53b86[correlationID=25f15c1b-1bc1-4a1d-9204-cde1f1dd7631, 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: 25f15c1b: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1 Result: Received event: 25f15c1b: 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@76c587ce[correlationID=bb0dbf2a-3251-461a-9e57-d44a62b148ac, 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: bb0dbf2a: 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: bb0dbf2a: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: bb0dbf2a: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2] Result: Received event: bb0dbf2a: 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@5265a8dd[correlationID=bb0dbf2a-3251-461a-9e57-d44a62b148ac, 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: bb0dbf2a: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2 Result: Received event: bb0dbf2a: 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@736f8837[correlationID=af264ca3-6223-429b-b19d-1078fb27184b, 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: af264ca3: 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: af264ca3: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: af264ca3: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2] Result: Received event: af264ca3: 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@1b6e4761[correlationID=af264ca3-6223-429b-b19d-1078fb27184b, 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: af264ca3: GET_FILE for file default-test-file.txt: PROGRESS: ContributorID Pillar2, First test progress response message Step: Send a GetFileFinalResponse. Result: Received event: af264ca3: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2 Result: Received event: af264ca3: 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@35d3202b[correlationID=67015435-7a55-469e-b514-1ab465eb6b72, 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: 67015435: 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: 67015435: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 67015435: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 67015435: 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@64381526[correlationID=67015435-7a55-469e-b514-1ab465eb6b72, 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@46290193[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: 67015435: 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: 67015435: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1 Result: Received event: 67015435: 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@54a5799f[correlationID=0e807334-9fdf-4527-8fcb-da6768eedb44, 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: 0e807334: GET_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetFile Step: Wait for 1 seconds Result: Received event: 0e807334: 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: 0e807334: GET_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor Result: Received event: 0e807334: GET_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor Result: Received event: 0e807334: 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@6fe337a5[correlationID=c1c04686-4c17-4fd2-a9eb-d31801299d2f, 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: c1c04686: 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: c1c04686: 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: c1c04686: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: c1c04686: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2] Result: Received event: c1c04686: 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@43312512[correlationID=c1c04686-4c17-4fd2-a9eb-d31801299d2f, 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: c1c04686: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2 Result: Received event: c1c04686: 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@662061e3[correlationID=f6a9cf49-9786-4d40-81ce-ce50f2a404c7, 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: f6a9cf49: 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: f6a9cf49: 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: f6a9cf49: 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: f6a9cf49: 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@f245168[correlationID=c6e2a715-74da-4a57-a491-21393659e66c, 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: c6e2a715: 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: c6e2a715: 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: c6e2a715: 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 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: -p [OPTIONAL] The id of the pillar where the should be performed. If undefined the operations is performed on all pillars. -s The path to the directory with the settings files for the client -c The id for the collection to perform the operation on. -v Makes the client more verbose -i The id for the file to perform the operation on. -k The path to the file containing the private key. -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: c Test success: missingCollectionArgumentTest Test starting: missingFileIDArgumentTest Description: Tests the scenario, where no arguments for file id argument is given. Takes the following arguments: -p [OPTIONAL] The id of the pillar where the should be performed. If undefined the operations is performed on all pillars. -s The path to the directory with the settings files for the client -c The id for the collection to perform the operation on. -v Makes the client more verbose -i The id for the file to perform the operation on. -k The path to the file containing the private key. -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: 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: Random1448500755993pillar is not a valid pillar for collection TwoPillarCollection The collection contains the following pillars: [Pillar1, Pillar2] Test success: unknownPillarArgumentTest Starting testcase NegativeResponseExceptionTest Test starting: testNegativeResponse Description: Test the instantiation of the exception Step: Setup Step: Try to throw such an exception with the response code Test success: testNegativeResponse Starting testcase 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@125bc00d[checksumType=MD5, checksumSalt=, otherChecksumType=], org.bitrepository.client.TestEventHandler@77e4ffe5, TEST-AUDIT-TRAIL) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@59bf79f3[correlationID=8a322694-94ba-472f-99ad-adac0476b709, 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: 8a322694: 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: 8a322694: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Step: Send an normal identification response from pillar2. Result: Received event: 8a322694: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: 8a322694: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2] Result: Received event: 8a322694: 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@726882da[correlationID=8a322694-94ba-472f-99ad-adac0476b709, 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@125bc00d[checksumType=MD5, checksumSalt=, otherChecksumType=]] Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@1ddf9fd[correlationID=8a322694-94ba-472f-99ad-adac0476b709, 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@125bc00d[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@7be9582e, TEST-AUDIT-TRAIL) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@73ac7716[correlationID=2b079b66-37b1-46ab-8889-06e205224398, 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: 2b079b66: 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: 2b079b66: 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@4c25687b[responseCode=DUPLICATE_FILE_FAILURE, responseText=Testing the handling of 'DUPLICATE FILE' identification.] (existing file checksum does not match) Result: Received event: 2b079b66: 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@7cecd959[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7f514dfe[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={-70}, calculationTimestamp=2015-11-26T02:19:16.403+01:00], null, org.bitrepository.client.TestEventHandler@2150dc64, TEST-AUDIT-TRAIL) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@3f33c5e4[correlationID=ad2ed8d0-f8f8-43a1-aac7-27893d51f4cf, 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: ad2ed8d0: 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: ad2ed8d0: 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@77d03738[responseCode=DUPLICATE_FILE_FAILURE, responseText=Testing the handling of 'DUPLICATE FILE' identification.] (existing file checksum does not match) Result: Received event: ad2ed8d0: 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@7892635c, TEST-AUDIT-TRAIL) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@79c9a128[correlationID=60d2d20f-e9c1-404a-92a4-8ed0d1396a05, 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: 60d2d20f: 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: 60d2d20f: 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@729a98e9[responseCode=DUPLICATE_FILE_FAILURE, responseText=Testing the handling of 'DUPLICATE FILE' identification.] Result: Received event: 60d2d20f: 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@346d8002, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@1368ed98[correlationID=f9d3d334-f6d8-423b-b10f-b5913d25f29c, 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: f9d3d334: 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: f9d3d334: 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: f9d3d334: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor Result: Received event: f9d3d334: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor Result: Received event: f9d3d334: 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@3b75b7b4, TEST-AUDIT-TRAIL) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@7882379b[correlationID=23d11543-98e2-4ece-9992-2761801771bf, 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: 23d11543: 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: 23d11543: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Step: Send an normal identification response from pillar2. Result: Received event: 23d11543: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: 23d11543: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2, Pillar1] Result: Received event: 23d11543: 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@731a5a39[correlationID=23d11543-98e2-4ece-9992-2761801771bf, 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@1acd952e[correlationID=23d11543-98e2-4ece-9992-2761801771bf, 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@296b758, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@7f129873[correlationID=bdfdd27f-eb51-4bcf-b39b-e7308e25081e, 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: bdfdd27f: 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: bdfdd27f: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: bdfdd27f: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: bdfdd27f: 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@ceeb762[correlationID=bdfdd27f-eb51-4bcf-b39b-e7308e25081e, 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: bdfdd27f: 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: bdfdd27f: PUT_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, requestedChecksumResult=null Result: Received event: bdfdd27f: 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@16c9ec5b, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@4001a5a1[correlationID=77b9a04c-4a35-4556-9de2-1b8a8b1a1162, 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: 77b9a04c: 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: 77b9a04c: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 77b9a04c: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 77b9a04c: 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@4fae8455[correlationID=77b9a04c-4a35-4556-9de2-1b8a8b1a1162, 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@16dc12cf[correlationID=77b9a04c-4a35-4556-9de2-1b8a8b1a1162, 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: 77b9a04c: 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@5bbd8118[correlationID=77b9a04c-4a35-4556-9de2-1b8a8b1a1162, 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: 77b9a04c: 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: 77b9a04c: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FILE_TRANSFER_FAILURE Result: Received event: 77b9a04c: PUT_FILE for file default-test-file.txt: FAILED: , Failed operation. Cause(s): [77b9a04c: 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@4377b35b, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@20dc2df1[correlationID=d15ada99-396b-4d19-9a35-32813c9a9341, 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: d15ada99: 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: d15ada99: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: d15ada99: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: d15ada99: 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@3e6b08d4[correlationID=d15ada99-396b-4d19-9a35-32813c9a9341, 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@40f88929[correlationID=d15ada99-396b-4d19-9a35-32813c9a9341, 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: d15ada99: 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: d15ada99: PUT_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, requestedChecksumResult=null Result: Received event: d15ada99: 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@4daa53e0, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@6b989889[correlationID=5137139e-9fad-4d7b-928b-2611d03ed302, 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: 5137139e: 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: 5137139e: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Step: Await the timeout. Result: Received event: 5137139e: 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: 5137139e: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor Result: Received event: 5137139e: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 5137139e: 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@5a32cf68[correlationID=5137139e-9fad-4d7b-928b-2611d03ed302, 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: 5137139e: PUT_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, requestedChecksumResult=null Result: Received event: 5137139e: PUT_FILE for file default-test-file.txt: FAILED: , Failed operation. Cause(s): [5137139e: 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@2a59a8fe, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@43baf0b9[correlationID=4ab5272e-17ed-4765-a91c-238c3f21da9b, 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: 4ab5272e: 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: 4ab5272e: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Step: Await the timeout. Result: Received event: 4ab5272e: 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: 4ab5272e: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor Result: Received event: 4ab5272e: 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@1c6ab85, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@45b221c7[correlationID=2420f736-e0d8-4113-a1b5-623c9bdd17c5, 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: 2420f736: 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: 2420f736: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 2420f736: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 2420f736: 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@7e38f55[correlationID=2420f736-e0d8-4113-a1b5-623c9bdd17c5, 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: 2420f736: 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@1377b7bf, TEST-AUDIT-TRAIL) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@7bfc7533[correlationID=bb568b33-22d5-4579-ac11-9b96b2c37a56, 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: bb568b33: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file Step: Send pillar response. Result: Received event: bb568b33: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: bb568b33: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: bb568b33: 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@28245839[correlationID=bb568b33-22d5-4579-ac11-9b96b2c37a56, 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: bb568b33: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE, Verifying that a failure can be understood! Result: Received event: bb568b33: PUT_FILE for file default-test-file.txt: FAILED: , Failed operation. Cause(s): [bb568b33: 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@f2120d5, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@1afea182[correlationID=0f5694ae-1f4e-42fb-b311-739f9f99f14f, 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: 0f5694ae: 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: 0f5694ae: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: 0f5694ae: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2] Result: Received event: 0f5694ae: 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@52a1d6f[correlationID=0f5694ae-1f4e-42fb-b311-739f9f99f14f, 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: 0f5694ae: PUT_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2, requestedChecksumResult=null Result: Received event: 0f5694ae: 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@2a2d0cff[checksumType=HMAC_MD5, checksumSalt={-86}, otherChecksumType=], org.bitrepository.client.TestEventHandler@40eb85e9, TEST-AUDIT-TRAIL) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@5f58ac11[correlationID=1c1910f6-af58-4ed7-94b5-d5a3a343cd97, 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: 1c1910f6: 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: 1c1910f6: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Step: Send an normal identification response from pillar2. Result: Received event: 1c1910f6: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: 1c1910f6: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2, Pillar1] Result: Received event: 1c1910f6: 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@bb0dcb6[correlationID=1c1910f6-af58-4ed7-94b5-d5a3a343cd97, 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@1192d1f5[correlationID=1c1910f6-af58-4ed7-94b5-d5a3a343cd97, 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@2a2d0cff[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@8c6a7db[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@5d95c7c2[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-11-26T02:19:19.864+01:00], null, org.bitrepository.client.TestEventHandler@40afa4f1, TEST-AUDIT-TRAIL) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@233b5c71[correlationID=9557d738-abc4-4a82-ae97-7b6fc0b983c0, 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: 9557d738: 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: 9557d738: PUT_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, requestedChecksumResult=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@50931911[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@29b21fa6[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-11-26T02:19:19.869+01:00], File already existed on Pillar1 Step: Send an identification response from the second pillar. Result: Received event: 9557d738: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: 9557d738: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2] Result: Received event: 9557d738: 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@19a48bde[correlationID=9557d738-abc4-4a82-ae97-7b6fc0b983c0, 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@8c6a7db[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@5d95c7c2[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-11-26T02:19:19.864+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: 9557d738: PUT_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2, requestedChecksumResult=null Result: Received event: 9557d738: 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 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@3387d45e[correlationID=1b199a71-f704-49e2-8923-b1e9e910837a, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=getAllAuditTrailsTest, to=, version=28, minVersion=24, auditTrailInformation=] Result: Received event: 1b199a71: 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: 1b199a71: GET_AUDIT_TRAILS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 1b199a71: GET_AUDIT_TRAILS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: 1b199a71: GET_AUDIT_TRAILS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2] Result: Received event: 1b199a71: 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@3ace955c[correlationID=1b199a71-f704-49e2-8923-b1e9e910837a, 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@7474bc14[correlationID=1b199a71-f704-49e2-8923-b1e9e910837a, 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: 1b199a71: 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: 1b199a71: GET_AUDIT_TRAILS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2, NumberOfAuditTrailEvents=2, PartialResult=false Result: Received event: 1b199a71: 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@752daa1f[correlationID=0b8e3a00-c443-40d3-b0b9-f04c476f9aca, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=getSomeAuditTrailsTest, to=Pillar1, version=28, minVersion=24, auditTrailInformation=] Result: Received event: 0b8e3a00: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails Step: Send a identifyResponse from pillar1 Result: Received event: 0b8e3a00: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 0b8e3a00: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 0b8e3a00: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1], Sending request for audit trails Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@1bff70a6[correlationID=0b8e3a00-c443-40d3-b0b9-f04c476f9aca, 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: 0b8e3a00: GET_AUDIT_TRAILS: COMPONENT_COMPLETE: ContributorID Pillar1, NumberOfAuditTrailEvents=2, PartialResult=false Result: Received event: 0b8e3a00: 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@75f1c170[correlationID=85bf8264-81e5-40d6-9678-a82658b03747, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=incompleteSetOfFinalResponsesTest, to=, version=28, minVersion=24, auditTrailInformation=] Result: Received event: 85bf8264: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails Step: Send a identifyResponse from each of the two pillars Result: Received event: 85bf8264: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 85bf8264: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: 85bf8264: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2, Pillar1] Result: Received event: 85bf8264: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for audit trails Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@67620d80[correlationID=85bf8264-81e5-40d6-9678-a82658b03747, 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@1c63aa5d[correlationID=85bf8264-81e5-40d6-9678-a82658b03747, 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@1c63aa5d[correlationID=85bf8264-81e5-40d6-9678-a82658b03747, 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:21.780 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@1c63aa5d[correlationID=85bf8264-81e5-40d6-9678-a82658b03747, 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@1b272037[correlationID=d681de1d-fbe2-40f1-a8ca-b763607e6a22, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=negativeGetAuditTrailsResponseTest, to=, version=28, minVersion=24, auditTrailInformation=] Result: Received event: d681de1d: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails Step: Send a identifyResponse from each of the two pillars Result: Received event: d681de1d: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: d681de1d: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: d681de1d: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2] Result: Received event: d681de1d: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for audit trails Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@17236e87[correlationID=d681de1d-fbe2-40f1-a8ca-b763607e6a22, 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@35a7c2cc[correlationID=d681de1d-fbe2-40f1-a8ca-b763607e6a22, 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: d681de1d: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE, GetAuditTrails failed Step: Send a final response from pillar 2 Result: Received event: d681de1d: GET_AUDIT_TRAILS: COMPONENT_COMPLETE: ContributorID Pillar2, NumberOfAuditTrailEvents=2, PartialResult=false Result: Received event: d681de1d: GET_AUDIT_TRAILS: FAILED: , Failed operation. Cause(s): [d681de1d: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE, GetAuditTrails failed] Test success: negativeGetAuditTrailsResponseTest Result: Received event: 85bf8264: GET_AUDIT_TRAILS: FAILED: , Failed to receive responses from all contributors before timeout(500ms). Missing contributors [Pillar1, Pillar2] 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@876c4f0[correlationID=387a34b3-6818-49bd-9906-514883acdb8d, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noFinalResponsesTest, to=, version=28, minVersion=24, auditTrailInformation=] Result: Received event: 387a34b3: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails Step: Send a identifyResponse from each of the two pillars Result: Received event: 387a34b3: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 387a34b3: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: 387a34b3: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2] Result: Received event: 387a34b3: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for audit trails Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@38696886[correlationID=387a34b3-6818-49bd-9906-514883acdb8d, 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@6066a3f[correlationID=387a34b3-6818-49bd-9906-514883acdb8d, 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: 387a34b3: 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@38696886[correlationID=387a34b3-6818-49bd-9906-514883acdb8d, 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:22.562 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@38696886[correlationID=387a34b3-6818-49bd-9906-514883acdb8d, 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@6066a3f[correlationID=387a34b3-6818-49bd-9906-514883acdb8d, 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:22.562 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@6066a3f[correlationID=387a34b3-6818-49bd-9906-514883acdb8d, 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@5b9037b6[correlationID=19eb096b-0bfe-470b-9bbe-d0ca60b4a26a, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=progressEventsTest, to=, version=28, minVersion=24, auditTrailInformation=] Result: Received event: 19eb096b: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails Step: Send a identifyResponse from each of the two pillars Result: Received event: 19eb096b: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 19eb096b: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: 19eb096b: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2] Result: Received event: 19eb096b: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for audit trails Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@2ef2fa78[correlationID=19eb096b-0bfe-470b-9bbe-d0ca60b4a26a, 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@74055597[correlationID=19eb096b-0bfe-470b-9bbe-d0ca60b4a26a, 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: 19eb096b: GET_AUDIT_TRAILS: PROGRESS: ContributorID Pillar1, GetAuditTrails request accepted Step: Send a general progress response from pillar 2 Result: Received event: 19eb096b: GET_AUDIT_TRAILS: PROGRESS: ContributorID Pillar2, Still progressing Test success: progressEventsTest Test starting: verifyAuditTrailClientFromFactory Test success: verifyAuditTrailClientFromFactory 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@485e52c9[correlationID=1edb415d-130d-4053-b05a-aa175c847bf4, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=collectionIDIncludedInEventsTest, to=, version=28, minVersion=24, auditTrailInformation=] Result: Received event: 1edb415d: 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: 1edb415d: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 1edb415d: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE Result: Received event: 1edb415d: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 1edb415d: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1], Sending request for audit trails Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@775b908f[correlationID=1edb415d-130d-4053-b05a-aa175c847bf4, 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: 1edb415d: GET_AUDIT_TRAILS: FAILED: , Failed to receive responses from all contributors before timeout(500ms). Missing contributors [Pillar1] Test success: collectionIDIncludedInEventsTest Starting testcase GetFileIDsClientComponentTest Test starting: collectionIDIncludedInEventsTest Description: Tests the the client provides collectionID in events. Step: Set a 0.5 second operation timeout. Step: Start the operation Stimuli: Calling getFileIDs(null, null, null, org.bitrepository.client.TestEventHandler@42c82f73) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@1c3577ec[correlationID=f63f58da-5b42-42c6-a984-22c5a02366b7, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=collectionIDIncludedInEventsTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@53a15397[fileID=, allFileIDs=true]] Result: Received event: f63f58da: 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: f63f58da: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: f63f58da: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE Result: Received event: f63f58da: GET_FILE_IDS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: f63f58da: GET_FILE_IDS: REQUEST_SENT: ContributorID [Pillar1], Sending request for get fileIDs Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@67668cf7[correlationID=f63f58da-5b42-42c6-a984-22c5a02366b7, 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@3e024667[fileID=, allFileIDs=true], minTimestamp=, maxTimestamp=, maxNumberOfResults=, resultAddress=] Step: Wait for 1 second Result: Received event: f63f58da: 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 getAuditTrails(null, null, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@6b7945e1[correlationID=e0c78846-8fb6-4eb0-99ad-9319f0720f38, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=conversationTimeoutTest, to=, version=28, minVersion=24, auditTrailInformation=] Result: Received event: e0c78846: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails 02:19:26.307 WARN o.b.c.c.m.CollectionBasedConversationMediator - Failing timed out conversation e0c78846-8fb6-4eb0-99ad-9319f0720f38 (Age 1009ms) Result: Received event: e0c78846: GET_AUDIT_TRAILS: FAILED: , Failing timed out conversation e0c78846-8fb6-4eb0-99ad-9319f0720f38 Test success: conversationTimeoutTest Test starting: conversationTimeoutTest Description: Tests the the client handles lack of IdentifyPillarResponses gracefully Step: Set a 100 ms ConversationTimeout. Step: Start the operation Stimuli: Calling getFileIDs(null, null, null, org.bitrepository.client.TestEventHandler@42c82f73) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@387c5d79[correlationID=6cbd3d81-3f60-44c4-9b11-9f9a3896d922, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=conversationTimeoutTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@14c10311[fileID=, allFileIDs=true]] Result: Received event: 6cbd3d81: GET_FILE_IDS: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs 02:19:27.771 WARN o.b.c.c.m.CollectionBasedConversationMediator - Failing timed out conversation 6cbd3d81-3f60-44c4-9b11-9f9a3896d922 (Age 1014ms) Result: Received event: 6cbd3d81: GET_FILE_IDS: FAILED: , Failing timed out conversation 6cbd3d81-3f60-44c4-9b11-9f9a3896d922 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@ad038f8[correlationID=c635a55c-e1b3-42ec-9246-074fca988eea, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=identificationFailureTest, to=, version=28, minVersion=24, auditTrailInformation=] Result: Received event: c635a55c: 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: c635a55c: 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: c635a55c: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: c635a55c: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2] Result: Received event: c635a55c: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar2], Sending request for audit trails Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@51934be2[correlationID=c635a55c-e1b3-42ec-9246-074fca988eea, 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: c635a55c: GET_AUDIT_TRAILS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false Result: Received event: c635a55c: GET_AUDIT_TRAILS: FAILED: , Failed operation. Cause(s): [c635a55c: 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 getFileIDs(null, null, null, org.bitrepository.client.TestEventHandler@42c82f73) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@946b9d9[correlationID=4cfadf78-4822-480f-a51f-015dfc3c83dc, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=identificationFailureTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@68cacf8b[fileID=, allFileIDs=true]] Result: Received event: 4cfadf78: 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: 4cfadf78: 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: 4cfadf78: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: 4cfadf78: GET_FILE_IDS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2] Result: Received event: 4cfadf78: GET_FILE_IDS: REQUEST_SENT: ContributorID [Pillar2], Sending request for get fileIDs Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@3743d16b[correlationID=4cfadf78-4822-480f-a51f-015dfc3c83dc, 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@b772e2b[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: 4cfadf78: GET_FILE_IDS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false Result: Received event: 4cfadf78: GET_FILE_IDS: FAILED: , Failed operation. Cause(s): [4cfadf78: 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 getAuditTrails(null, null, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@4f38acf[correlationID=fc0ab437-4fc7-4717-94bd-601c006b1e6a, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=identificationNegativeTest, to=, version=28, minVersion=24, auditTrailInformation=] Result: Received event: fc0ab437: 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: fc0ab437: 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: fc0ab437: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: fc0ab437: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2] Result: Received event: fc0ab437: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar2], Sending request for audit trails Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@27ae4c06[correlationID=fc0ab437-4fc7-4717-94bd-601c006b1e6a, 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: fc0ab437: GET_AUDIT_TRAILS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false Result: Received event: fc0ab437: GET_AUDIT_TRAILS: FAILED: , Failed operation. Cause(s): [fc0ab437: 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 getFileIDs(null, null, null, org.bitrepository.client.TestEventHandler@42c82f73) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@1e5bc4e7[correlationID=e1d7bc7d-0bd1-4d74-af15-f9e8712f64a5, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=identificationNegativeTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@539c833d[fileID=, allFileIDs=true]] Result: Received event: e1d7bc7d: 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: e1d7bc7d: 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: e1d7bc7d: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: e1d7bc7d: GET_FILE_IDS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2] Result: Received event: e1d7bc7d: GET_FILE_IDS: REQUEST_SENT: ContributorID [Pillar2], Sending request for get fileIDs Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@4fbdd61f[correlationID=e1d7bc7d-0bd1-4d74-af15-f9e8712f64a5, 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@f014ff3[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: e1d7bc7d: GET_FILE_IDS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false Result: Received event: e1d7bc7d: GET_FILE_IDS: FAILED: , Failed operation. Cause(s): [e1d7bc7d: 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 getAuditTrails(null, null, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@18e5b50[correlationID=1e8474be-74ad-43cc-be4b-5a1330e39def, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noContributorsRespondingTest, to=, version=28, minVersion=24, auditTrailInformation=] Result: Received event: 1e8474be: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails Step: Wait for 1 second Result: Received event: 1e8474be: GET_AUDIT_TRAILS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors The following contributors didn't respond: [Pillar1, Pillar2] Result: Received event: 1e8474be: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor Result: Received event: 1e8474be: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor Result: Received event: 1e8474be: 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@18e5b50[correlationID=1e8474be-74ad-43cc-be4b-5a1330e39def, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noContributorsRespondingTest, to=, version=28, minVersion=24, auditTrailInformation=] 02:19:33.477 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@18e5b50[correlationID=1e8474be-74ad-43cc-be4b-5a1330e39def, 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 getFileIDs(null, null, null, org.bitrepository.client.TestEventHandler@42c82f73) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@437b2db1[correlationID=d4f16c3e-80b7-4590-b280-e0c96dc2eeda, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=noContributorsRespondingTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@2876584f[fileID=, allFileIDs=true]] Result: Received event: d4f16c3e: GET_FILE_IDS: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs Step: Wait for 1 second Result: Received event: d4f16c3e: GET_FILE_IDS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors The following contributors didn't respond: [Pillar1, Pillar2] Result: Received event: d4f16c3e: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor Result: Received event: d4f16c3e: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor Result: Received event: d4f16c3e: 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@437b2db1[correlationID=d4f16c3e-80b7-4590-b280-e0c96dc2eeda, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=noContributorsRespondingTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@2876584f[fileID=, allFileIDs=true]] 02:19:33.961 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@437b2db1[correlationID=d4f16c3e-80b7-4590-b280-e0c96dc2eeda, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=noContributorsRespondingTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@2876584f[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 getAuditTrails(null, null, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@32ebfde1[correlationID=b988159e-ab12-4788-a386-46c49d9f996f, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=oneContributorNotRespondingTest, to=, version=28, minVersion=24, auditTrailInformation=] Result: Received event: b988159e: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails Step: Send a identification response from contributor1. Result: Received event: b988159e: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Step: Wait 1 second. Result: Received event: b988159e: GET_AUDIT_TRAILS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors The following contributors didn't respond: [Pillar2] Result: Received event: b988159e: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor Result: Received event: b988159e: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: b988159e: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1], Sending request for audit trails Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@5e0d50f6[correlationID=b988159e-ab12-4788-a386-46c49d9f996f, 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: b988159e: GET_AUDIT_TRAILS: COMPONENT_COMPLETE: ContributorID Pillar1, PartialResult=false Result: Received event: b988159e: GET_AUDIT_TRAILS: FAILED: , Failed operation. Cause(s): [b988159e: 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 getFileIDs(null, null, null, org.bitrepository.client.TestEventHandler@42c82f73) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@7d3818ab[correlationID=a5a77c58-d12e-4bd2-bbcb-97058c7f00eb, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=oneContributorNotRespondingTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@9a6c67c[fileID=, allFileIDs=true]] Result: Received event: a5a77c58: GET_FILE_IDS: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs Step: Send a identification response from contributor1. Result: Received event: a5a77c58: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Step: Wait 1 second. Result: Received event: a5a77c58: GET_FILE_IDS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors The following contributors didn't respond: [Pillar2] Result: Received event: a5a77c58: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor Result: Received event: a5a77c58: GET_FILE_IDS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: a5a77c58: GET_FILE_IDS: REQUEST_SENT: ContributorID [Pillar1], Sending request for get fileIDs Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@1b0fc553[correlationID=a5a77c58-d12e-4bd2-bbcb-97058c7f00eb, 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@66dbf4bf[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: a5a77c58: GET_FILE_IDS: COMPONENT_COMPLETE: ContributorID Pillar1, PartialResult=false Result: Received event: a5a77c58: GET_FILE_IDS: FAILED: , Failed operation. Cause(s): [a5a77c58: 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 getAuditTrails(null, null, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@3ec4c84a[correlationID=21d6cae9-1c5e-4dca-80a1-d21c3382c1bd, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=operationTimeoutTest, to=, version=28, minVersion=24, auditTrailInformation=] Result: Received event: 21d6cae9: 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: 21d6cae9: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 21d6cae9: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE Result: Received event: 21d6cae9: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 21d6cae9: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1], Sending request for audit trails Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@76700647[correlationID=21d6cae9-1c5e-4dca-80a1-d21c3382c1bd, 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: 21d6cae9: 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 getFileIDs(null, null, null, org.bitrepository.client.TestEventHandler@42c82f73) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@59ccdde4[correlationID=30b5e9e4-d9e9-4323-a7d9-fe3794c3af04, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=operationTimeoutTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@33b29c99[fileID=, allFileIDs=true]] Result: Received event: 30b5e9e4: 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: 30b5e9e4: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 30b5e9e4: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE Result: Received event: 30b5e9e4: GET_FILE_IDS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 30b5e9e4: GET_FILE_IDS: REQUEST_SENT: ContributorID [Pillar1], Sending request for get fileIDs Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@792feb9f[correlationID=30b5e9e4-d9e9-4323-a7d9-fe3794c3af04, 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@46b32aa3[fileID=, allFileIDs=true], minTimestamp=, maxTimestamp=, maxNumberOfResults=, resultAddress=] Step: Wait for 1 second Result: Received event: 30b5e9e4: 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: -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. -s The path to the directory with the settings files for the client -c The id for the collection to perform the operation on. -C [OPTIONAL] The checksum of the file to be delete. -S [OPTIONAL] The salt of checksum to request in the response. Requires the ChecksumType argument. -v Makes the client more verbose -i The id for the file to perform the operation on. -k The path to the file containing the private key. Missing argument: c Test success: missingCollectionArgumentTest Test starting: missingFileIDArgumentTest Description: Tests the scenario, where no arguments for file id argument is given. Takes the following arguments: -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. -s The path to the directory with the settings files for the client -c The id for the collection to perform the operation on. -C [OPTIONAL] The checksum of the file to be delete. -S [OPTIONAL] The salt of checksum to request in the response. Requires the ChecksumType argument. -v Makes the client more verbose -i The id for the file to perform the operation on. -k The path to the file containing the private key. Missing argument: 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: Random1448500776888pillar is not a valid pillar for collection TwoPillarCollection The collection contains the following pillars: [Pillar1, Pillar2] Test success: unknownPillarArgumentTest 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@42c82f73) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@2d309058[correlationID=a540d36c-ce55-4138-9317-9a62c292fa95, 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@52742778[fileID=default-test-file.txt, allFileIDs=]] Result: Received event: a540d36c: 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: a540d36c: GET_FILE_IDS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: a540d36c: GET_FILE_IDS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: a540d36c: 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@18ce4e9d[correlationID=a540d36c-ce55-4138-9317-9a62c292fa95, 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@3155bf8c[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: a540d36c: 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: a540d36c: GET_FILE_IDS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, PartialResult=false Result: Received event: a540d36c: 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@42c82f73) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@668b9072[correlationID=a84a0c20-e93f-4bb7-b8d6-6343b361f936, 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@78db5702[fileID=default-test-file.txt, allFileIDs=]] Result: Received event: a84a0c20: 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: a84a0c20: GET_FILE_IDS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: a84a0c20: GET_FILE_IDS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: a84a0c20: 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@7a715766[correlationID=a84a0c20-e93f-4bb7-b8d6-6343b361f936, 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@4043405a[fileID=default-test-file.txt, allFileIDs=], minTimestamp=, maxTimestamp=, maxNumberOfResults=, resultAddress=] Step: The pillar sends a getFileIDsProgressResponse to the GetFileIDsClient. Result: Received event: a84a0c20: 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: a84a0c20: GET_FILE_IDS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, NumberOfFileIDs=1, PartialResult=false Result: Received event: a84a0c20: 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@6d0dd338) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@75defebe[correlationID=74ae12cd-a270-47dc-8c69-88ac84402359, 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@173e347f[fileID=default-test-file.txt, allFileIDs=]] Result: Received event: 74ae12cd: 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: 74ae12cd: GET_FILE_IDS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: 74ae12cd: GET_FILE_IDS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2] Result: Received event: 74ae12cd: 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@7780a93c[correlationID=74ae12cd-a270-47dc-8c69-88ac84402359, 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@7529827c[fileID=default-test-file.txt, allFileIDs=], minTimestamp=, maxTimestamp=, maxNumberOfResults=, resultAddress=] Step: Send a complete event from the pillar Result: Received event: 74ae12cd: GET_FILE_IDS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false Result: Received event: 74ae12cd: 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@42c82f73) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@9ed1f3f[correlationID=011baccd-5606-487c-afd0-c3830b93f0ed, 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@4a256169[fileID=default-test-file.txt, allFileIDs=]] Result: Received event: 011baccd: 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: 011baccd: GET_FILE_IDS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 011baccd: GET_FILE_IDS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 011baccd: 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@797f26ce[correlationID=011baccd-5606-487c-afd0-c3830b93f0ed, 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@180aca39[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: 011baccd: GET_FILE_IDS for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FILE_NOT_FOUND_FAILURE, No such file. Result: Received event: 011baccd: GET_FILE_IDS for file default-test-file.txt: FAILED: , Failed operation. Cause(s): [011baccd: 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=Thu Nov 26 02:19:36 CET 2015, maxTimestamp=Thu Nov 26 02:19:37 CET 2015, maxNumberOfResults=1}, ContributorQuery{componentID='Pillar2, minTimestamp=Thu Nov 26 02:19:37 CET 2015, maxTimestamp=Thu Nov 26 02:19:37 CET 2015, maxNumberOfResults=2}], null, null, org.bitrepository.client.TestEventHandler@42c82f73) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@34b312d8[correlationID=0e6b69c1-9c80-4005-814e-30a9426f31de, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=testPaging, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@1d50301[fileID=, allFileIDs=true]] Result: Received event: 0e6b69c1: GET_FILE_IDS: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs Step: Send a IdentifyPillarsForGetFileIDsResponse from both pillars. Result: Received event: 0e6b69c1: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 0e6b69c1: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: 0e6b69c1: GET_FILE_IDS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2] Result: Received event: 0e6b69c1: GET_FILE_IDS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for get fileIDs Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@10ed3435[correlationID=0e6b69c1-9c80-4005-814e-30a9426f31de, 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@3989e022[fileID=, allFileIDs=true], minTimestamp=2015-11-26T02:19:36.832+01:00, maxTimestamp=2015-11-26T02:19:37.732+01:00, maxNumberOfResults=1, resultAddress=] Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@6e0ae02d[correlationID=0e6b69c1-9c80-4005-814e-30a9426f31de, 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@74d16083[fileID=, allFileIDs=true], minTimestamp=2015-11-26T02:19:37.732+01:00, maxTimestamp=2015-11-26T02:19:37.832+01:00, maxNumberOfResults=2, resultAddress=] Test success: testPaging Test starting: verifyGetFileIDsClientFromFactory Test success: verifyGetFileIDsClientFromFactory 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: -c The id for the collection to perform the operation on. -C [OPTIONAL] The checksum of the file to be replaced. -d If this argument is present, then the file will be removed from the server, when the operation is complete. -f The path to the new file for the replacement. Required unless using the URL argument. -i The id for the file to perform the operation on. -k The path to the file containing the private key. -p [OPTIONAL] The id of the pillar where the should be performed. If undefined the operations is performed on all pillars. -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 The path to the directory with the settings files for the client -S [OPTIONAL] The salt of checksum to request in the response. Requires the ChecksumType argument. -u The URL for the file to be retreived. Is required, unless the actual file is given. -v Makes the client more verbose Missing argument: 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: Random1448500781358pillar is not a valid pillar for collection TwoPillarCollection The collection contains the following pillars: [Pillar1, Pillar2] Test success: unknownPillarArgumentTest 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@71ee6d22, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@17d96a31[correlationID=00d4e502-8c66-48d5-a2d2-21edd3a21a60, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=collectionIDIncludedInEventsTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@1d0442a2[fileID=, allFileIDs=true], checksumRequestForExistingFile=] Result: Received event: 00d4e502: 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: 00d4e502: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 00d4e502: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE Result: Received event: 00d4e502: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 00d4e502: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar1], Sending GetFileIDsRequest's Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@4bfed947[correlationID=00d4e502-8c66-48d5-a2d2-21edd3a21a60, 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@74d083c8[fileID=, allFileIDs=true], minTimestamp=, maxTimestamp=, maxNumberOfResults=, checksumRequestForExistingFile=, resultAddress=] Step: Wait for 1 second Result: Received event: 00d4e502: 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 getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@71ee6d22, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@34cfcec2[correlationID=24c26275-88f3-4dd1-8376-cb04c7858b33, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=conversationTimeoutTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@6f39000e[fileID=, allFileIDs=true], checksumRequestForExistingFile=] Result: Received event: 24c26275: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums 02:19:43.158 WARN o.b.c.c.m.CollectionBasedConversationMediator - Failing timed out conversation 24c26275-88f3-4dd1-8376-cb04c7858b33 (Age 1007ms) Result: Received event: 24c26275: GET_CHECKSUMS: FAILED: , Failing timed out conversation 24c26275-88f3-4dd1-8376-cb04c7858b33 Test success: conversationTimeoutTest Test starting: identificationFailureTest Description: Verify that the client works correctly when a contributor sends a failure response. Step: Start the operation. Stimuli: Calling getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@71ee6d22, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@2225a51b[correlationID=93b5b678-d1ad-4ba1-acd3-646f0d8208e3, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=identificationFailureTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@4156134d[fileID=, allFileIDs=true], checksumRequestForExistingFile=] Result: Received event: 93b5b678: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums Step: Send a identification response from contributor1 with a FAILURE response code. Result: Received event: 93b5b678: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE Step: Send a identification response from contributor2 with a IDENTIFICATION_POSITIVE response code . Result: Received event: 93b5b678: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: 93b5b678: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2] Result: Received event: 93b5b678: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar2], Sending GetFileIDsRequest's Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@6a5b87dc[correlationID=93b5b678-d1ad-4ba1-acd3-646f0d8208e3, 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@6559faf1[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: 93b5b678: GET_CHECKSUMS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false Result: Received event: 93b5b678: GET_CHECKSUMS: FAILED: , Failed operation. Cause(s): [93b5b678: 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 getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@71ee6d22, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@37b8aab2[correlationID=7e12e3e6-594a-4b5a-bd46-8bc58e7c7964, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=identificationNegativeTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@1f8585a5[fileID=, allFileIDs=true], checksumRequestForExistingFile=] Result: Received event: 7e12e3e6: 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: 7e12e3e6: 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: 7e12e3e6: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: 7e12e3e6: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2] Result: Received event: 7e12e3e6: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar2], Sending GetFileIDsRequest's Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@5b04d06a[correlationID=7e12e3e6-594a-4b5a-bd46-8bc58e7c7964, 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@299b1c82[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: 7e12e3e6: GET_CHECKSUMS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false Result: Received event: 7e12e3e6: GET_CHECKSUMS: FAILED: , Failed operation. Cause(s): [7e12e3e6: 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 getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@71ee6d22, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@600fbcf7[correlationID=f7289134-77f8-4dd9-bd19-36c176a360e6, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=noContributorsRespondingTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@48fceda2[fileID=, allFileIDs=true], checksumRequestForExistingFile=] Result: Received event: f7289134: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums Step: Wait for 1 second Result: Received event: f7289134: GET_CHECKSUMS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors The following contributors didn't respond: [Pillar1, Pillar2] Result: Received event: f7289134: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor Result: Received event: f7289134: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor Result: Received event: f7289134: 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@600fbcf7[correlationID=f7289134-77f8-4dd9-bd19-36c176a360e6, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=noContributorsRespondingTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@48fceda2[fileID=, allFileIDs=true], checksumRequestForExistingFile=] 02:19:46.199 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@600fbcf7[correlationID=f7289134-77f8-4dd9-bd19-36c176a360e6, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=noContributorsRespondingTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@48fceda2[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 getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@71ee6d22, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@6e484af9[correlationID=423d98e4-1d82-4019-bd07-148c09baea2e, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=oneContributorNotRespondingTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@7797b489[fileID=, allFileIDs=true], checksumRequestForExistingFile=] Result: Received event: 423d98e4: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums Step: Send a identification response from contributor1. Result: Received event: 423d98e4: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Step: Wait 1 second. Result: Received event: 423d98e4: GET_CHECKSUMS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors The following contributors didn't respond: [Pillar2] Result: Received event: 423d98e4: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor Result: Received event: 423d98e4: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 423d98e4: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar1], Sending GetFileIDsRequest's Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@2ade3e83[correlationID=423d98e4-1d82-4019-bd07-148c09baea2e, 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@1ee051ce[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: 423d98e4: GET_CHECKSUMS: COMPONENT_COMPLETE: ContributorID Pillar1, PartialResult=false Result: Received event: 423d98e4: GET_CHECKSUMS: FAILED: , Failed operation. Cause(s): [423d98e4: 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 getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@71ee6d22, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@595a3150[correlationID=6acc63c3-a2eb-4f90-b110-7f2c176171e3, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=operationTimeoutTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@56d1c219[fileID=, allFileIDs=true], checksumRequestForExistingFile=] Result: Received event: 6acc63c3: 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: 6acc63c3: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 6acc63c3: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE Result: Received event: 6acc63c3: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 6acc63c3: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar1], Sending GetFileIDsRequest's Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@5d3d8794[correlationID=6acc63c3-a2eb-4f90-b110-7f2c176171e3, 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@5565fdd2[fileID=, allFileIDs=true], minTimestamp=, maxTimestamp=, maxNumberOfResults=, checksumRequestForExistingFile=, resultAddress=] Step: Wait for 1 second Result: Received event: 6acc63c3: 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@fd681b3, TEST-AUDIT) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@2119e4d2[correlationID=37d0b801-d7ce-4b89-b18a-32ec2b99826d, 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@770632c5[fileID=default-test-file.txt, allFileIDs=], checksumRequestForExistingFile=] Result: Received event: 37d0b801: 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: 37d0b801: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 37d0b801: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: 37d0b801: GET_CHECKSUMS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2] Result: Received event: 37d0b801: 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@686dc8e2[correlationID=37d0b801-d7ce-4b89-b18a-32ec2b99826d, 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@2e3b4f30[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@718c7433[correlationID=37d0b801-d7ce-4b89-b18a-32ec2b99826d, 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@13ce519a[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: 37d0b801: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, NumberOfChecksums=0, PartialResult=false Result: Received event: 37d0b801: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2, NumberOfChecksums=0, PartialResult=false Result: Received event: 37d0b801: 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@718c7433[correlationID=37d0b801-d7ce-4b89-b18a-32ec2b99826d, 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@13ce519a[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:47.199 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: org.bitrepository.bitrepositorymessages.GetChecksumsRequest@718c7433[correlationID=37d0b801-d7ce-4b89-b18a-32ec2b99826d, 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@13ce519a[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@237d6031, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@37aaa8b1[correlationID=0a9b9a6c-01ee-47be-9235-19ef465ebf1f, 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@1f208930[fileID=, allFileIDs=true], checksumRequestForExistingFile=] Result: Received event: 0a9b9a6c: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums Step: Send an identification response from pillar2. Result: Received event: 0a9b9a6c: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: 0a9b9a6c: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2] Result: Received event: 0a9b9a6c: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar2], Sending GetFileIDsRequest's Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@114cbcc4[correlationID=0a9b9a6c-01ee-47be-9235-19ef465ebf1f, 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@7341617c[fileID=, allFileIDs=true], minTimestamp=, maxTimestamp=, maxNumberOfResults=, checksumRequestForExistingFile=, resultAddress=] Step: Send a complete event from the pillar Result: Received event: 0a9b9a6c: GET_CHECKSUMS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false Result: Received event: 0a9b9a6c: 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@68cbe4da[checksumType=MD5, checksumSalt=, otherChecksumType=], null, org.bitrepository.client.TestEventHandler@4352280e, TEST-AUDIT) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@2f1ea14f[correlationID=917409c1-849b-486b-bc33-4ca3ee33f62c, 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@5ac24c22[fileID=default-test-file.txt, allFileIDs=], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@68cbe4da[checksumType=MD5, checksumSalt=, otherChecksumType=]] Result: Received event: 917409c1: 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: 917409c1: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 917409c1: GET_CHECKSUMS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 917409c1: 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@3f58c971[correlationID=917409c1-849b-486b-bc33-4ca3ee33f62c, 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@6516130c[fileID=default-test-file.txt, allFileIDs=], minTimestamp=, maxTimestamp=, maxNumberOfResults=, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@68cbe4da[checksumType=MD5, checksumSalt=, otherChecksumType=], resultAddress=] Step: Send a GetChecksumsFinalResponse to the client from pillar1 Result: Received event: 917409c1: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, NumberOfChecksums=0, PartialResult=false Result: Received event: 917409c1: 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@741d4ff5, TEST-AUDIT) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@6ad73de1[correlationID=b1cfb2f9-0f57-45c2-99ea-0644b3d5942e, 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@408c030b[fileID=default-test-file.txt, allFileIDs=], checksumRequestForExistingFile=] Result: Received event: b1cfb2f9: 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: b1cfb2f9: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: b1cfb2f9: GET_CHECKSUMS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: b1cfb2f9: 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@3474184e[correlationID=b1cfb2f9-0f57-45c2-99ea-0644b3d5942e, 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@679f1314[fileID=default-test-file.txt, allFileIDs=], minTimestamp=, maxTimestamp=, maxNumberOfResults=, checksumRequestForExistingFile=, resultAddress=] Step: Send a error that the file cannot be found. Result: Received event: b1cfb2f9: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FILE_NOT_FOUND_FAILURE, No such file. Result: Received event: b1cfb2f9: GET_CHECKSUMS for file default-test-file.txt: FAILED: , Failed operation. Cause(s): [b1cfb2f9: 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=Thu Nov 26 02:19:47 CET 2015, maxTimestamp=Thu Nov 26 02:19:48 CET 2015, maxNumberOfResults=1}, ContributorQuery{componentID='Pillar2, minTimestamp=Thu Nov 26 02:19:48 CET 2015, maxTimestamp=Thu Nov 26 02:19:48 CET 2015, maxNumberOfResults=2}], null, null, null, org.bitrepository.client.TestEventHandler@71ee6d22, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@62386752[correlationID=f61e9f92-c3ae-4d48-a659-454a28d00f92, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=testPaging, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@67520476[fileID=, allFileIDs=true], checksumRequestForExistingFile=] Result: Received event: f61e9f92: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums Step: Send a IdentifyPillarsForGetChecksumsResponse from both pillars. Result: Received event: f61e9f92: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: f61e9f92: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: f61e9f92: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2, Pillar1] Result: Received event: f61e9f92: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending GetFileIDsRequest's Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@3931325f[correlationID=f61e9f92-c3ae-4d48-a659-454a28d00f92, 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@4eb7f0bb[fileID=, allFileIDs=true], minTimestamp=2015-11-26T02:19:47.927+01:00, maxTimestamp=2015-11-26T02:19:48.827+01:00, maxNumberOfResults=1, checksumRequestForExistingFile=, resultAddress=] Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@5b1b01e6[correlationID=f61e9f92-c3ae-4d48-a659-454a28d00f92, 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@55a02b79[fileID=, allFileIDs=true], minTimestamp=2015-11-26T02:19:48.827+01:00, maxTimestamp=2015-11-26T02:19:48.927+01:00, maxNumberOfResults=2, checksumRequestForExistingFile=, resultAddress=] Test success: testPaging Test starting: verifyGetChecksumsClientFromFactory Test success: verifyGetChecksumsClientFromFactory 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: 28890532: GET_STATUS: IDENTIFY_REQUEST_SENT: , Identifying contributors for getting status Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetStatusRequest@179a0d61[correlationID=28890532-2018-4a43-a158-017b648c1ed2, 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: 28890532: GET_STATUS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 28890532: GET_STATUS: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: 28890532: GET_STATUS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2, Pillar1] Result: Received event: 28890532: GET_STATUS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending GetStatusRequest Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetStatusRequest@1f0db41a[correlationID=28890532-2018-4a43-a158-017b648c1ed2, 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@45ef2dab[correlationID=28890532-2018-4a43-a158-017b648c1ed2, 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: 28890532: GET_STATUS: COMPONENT_COMPLETE: ContributorID Pillar1, resulting status: org.bitrepository.bitrepositoryelements.ResultingStatus@90ffb91[statusInfo=org.bitrepository.bitrepositoryelements.StatusInfo@2cc788cc[statusCode=OK, statusText=Everythings fine..], statusTimestamp=2015-11-26T02:19:49.274+01:00] Step: Send a final response from pillar 2 Result: Received event: 28890532: GET_STATUS: COMPONENT_COMPLETE: ContributorID Pillar2, resulting status: org.bitrepository.bitrepositoryelements.ResultingStatus@4d52455[statusInfo=org.bitrepository.bitrepositoryelements.StatusInfo@67103520[statusCode=OK, statusText=Everythings fine..], statusTimestamp=2015-11-26T02:19:49.274+01:00] Result: Received event: 28890532: 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: 17d92d8d: GET_STATUS: IDENTIFY_REQUEST_SENT: , Identifying contributors for getting status Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetStatusRequest@2e0fd059[correlationID=17d92d8d-9be0-404e-afb6-b08414188587, 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: 17d92d8d: GET_STATUS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Step: Wait for timeout event Result: Received event: 17d92d8d: GET_STATUS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors The following contributors didn't respond: [Pillar2] Result: Received event: 17d92d8d: GET_STATUS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor Result: Received event: 17d92d8d: GET_STATUS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 17d92d8d: GET_STATUS: REQUEST_SENT: ContributorID [Pillar1], Sending GetStatusRequest Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetStatusRequest@7b203a1c[correlationID=17d92d8d-9be0-404e-afb6-b08414188587, 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 AuditTrailQueryTest Test starting: testBothSequenceNumberFailure Description: Test the creation of a AuditTrailQuery with both SequenceNumber, where max is smalle than min. Test success: testBothSequenceNumberFailure Test starting: testBothSequenceNumberSuccess Description: Test the creation of a AuditTrailQuery with both SequenceNumber, where max is larger than min. Test success: testBothSequenceNumberSuccess Test starting: testNoSequenceNumbers Description: Test that a AuditTrailQuery can be created without any sequence numbers. Test success: testNoSequenceNumbers Test starting: testOnlyMinSequenceNumber Description: Test the creation of a AuditTrailQuery with only the minSequenceNumber Test success: testOnlyMinSequenceNumber Starting testcase 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: -p [OPTIONAL] The id of the pillar where the should be performed. If undefined the operations is performed on all pillars. -s The path to the directory with the settings files for the client -c The id for the collection to perform the operation on. -v Makes the client more verbose -i The id for the file to perform the operation on. -k The path to the file containing the private key. Missing argument: 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: Random1448500791953pillar is not a valid pillar for collection TwoPillarCollection The collection contains the following pillars: [Pillar1, Pillar2] Test success: unknownPillarArgumentTest 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: -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. -s The path to the directory with the settings files for the client -c The id for the collection to perform the operation on. -C The checksum for the file to be retreived. Required if using an URL. -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. -u The URL for the file to be put. Is required, unless the actual file is given. -v Makes the client more verbose -f The path to the file, which is wanted to be put. Is required, unless a URL is given. -i The id for the file to perform the operation on. -k The path to the file containing the private key. Missing argument: 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: Random1448500793392pillar 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 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@28b443b[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@30770b75[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@508e2c28[checksumType=SHA1, checksumSalt=, otherChecksumType=], file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, 10, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@361b7a69[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@30770b75[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@508e2c28[checksumType=SHA1, checksumSalt=, otherChecksumType=], org.bitrepository.client.TestEventHandler@6ee95a0d, null Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileRequest@66cdc806[correlationID=3cf09b87-a543-418e-9643-45fe927af764, 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: 3cf09b87: 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: 3cf09b87: 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: 3cf09b87: REPLACE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor Result: Received event: 3cf09b87: 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@4cb1dce6[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@29cc44d0[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@5e85fdec[checksumType=SHA1, checksumSalt=, otherChecksumType=], file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, 10, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@3afec723[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@29cc44d0[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@5e85fdec[checksumType=SHA1, checksumSalt=, otherChecksumType=], org.bitrepository.client.TestEventHandler@786a6a76, null Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileRequest@334b4b6f[correlationID=61573695-e34d-4f83-9ace-fcdfaaa96deb, 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: 61573695: 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: 61573695: REPLACE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 61573695: REPLACE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 61573695: 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@e5bbad1[correlationID=61573695-e34d-4f83-9ace-fcdfaaa96deb, 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@4cb1dce6[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@29cc44d0[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@5e85fdec[checksumType=SHA1, checksumSalt=, otherChecksumType=], fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=10, checksumDataForNewFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@3afec723[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@29cc44d0[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@5e85fdec[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: 61573695: 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@9b38b82[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@379957ec[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@13a51131[checksumType=SHA1, checksumSalt=, otherChecksumType=], file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, 0, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@43207ef8[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@379957ec[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@13a51131[checksumType=SHA1, checksumSalt=, otherChecksumType=], org.bitrepository.client.TestEventHandler@565a0285, null Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileRequest@2b810995[correlationID=fdd1ae0b-79ff-486c-9a0e-a8dbffff813b, 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: fdd1ae0b: 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: fdd1ae0b: REPLACE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: fdd1ae0b: REPLACE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: fdd1ae0b: 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@5001d219[correlationID=fdd1ae0b-79ff-486c-9a0e-a8dbffff813b, 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@9b38b82[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@379957ec[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@13a51131[checksumType=SHA1, checksumSalt=, otherChecksumType=], fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@43207ef8[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@379957ec[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@13a51131[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: fdd1ae0b: REPLACE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE, Verifying that a failure can be understood! Result: Received event: fdd1ae0b: REPLACE_FILE for file default-test-file.txt: FAILED: , Failed operation. Cause(s): [fdd1ae0b: 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@147894f0[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@4f0aa51e[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@3ab2eed2[checksumType=SHA1, checksumSalt=, otherChecksumType=], file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, 10, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@1db53124[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@4f0aa51e[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@3ab2eed2[checksumType=SHA1, checksumSalt=, otherChecksumType=], org.bitrepository.client.TestEventHandler@4dbaf976, null Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileRequest@5782978a[correlationID=0031e153-fb65-4a3b-93a2-1222ab5154d9, 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: 0031e153: 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: 0031e153: REPLACE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 0031e153: REPLACE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 0031e153: 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@4e6315be[correlationID=0031e153-fb65-4a3b-93a2-1222ab5154d9, 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@147894f0[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@4f0aa51e[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@3ab2eed2[checksumType=SHA1, checksumSalt=, otherChecksumType=], fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=10, checksumDataForNewFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@1db53124[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@4f0aa51e[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@3ab2eed2[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: 0031e153: 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: 0031e153: REPLACE_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, checksum for new file: 'org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@1db53124[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@4f0aa51e[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: 0031e153: 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@5c1e772[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2a29b243[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@19a429d6[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2a29b243[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@68dd3d5b[checksumType=MD5, checksumSalt={-86}, otherChecksumType=], org.bitrepository.client.TestEventHandler@62adbd45, null Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileRequest@5f1b0f9[correlationID=6206ae64-12ff-43da-acff-8ddf19fd4688, 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: 6206ae64: 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: 6206ae64: REPLACE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 6206ae64: REPLACE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 6206ae64: 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@3c150602[correlationID=6206ae64-12ff-43da-acff-8ddf19fd4688, 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@5c1e772[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2a29b243[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@19a429d6[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2a29b243[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 Finished testcase Finished suite Finished project Tests run: 156, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 65.087 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 --- [JENKINS] Archiving disabled [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