SuccessConsole Output

Skipping 112 KB.. Full Log
dc17-4b4f-ab0d-b828c73686ea, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=defaultReturnChecksumsWithChecksumPillar, to=<null>, 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=<null>, checksumRequestForNewFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@69e58566[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>]]
      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@62b8dd6a, TEST-AUDIT-TRAIL)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@758e6acd[correlationID=296b2cc3-5092-44b0-b3ab-a4e6c4b02a76, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=fileExistsOnPillarChecksumFromPillarNoClientChecksum, to=<null>, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, fileID=default-test-file.txt, fileSize=0]
          Result: Received event: 296b2cc3: 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: 296b2cc3: 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@7df994ec[responseCode=DUPLICATE_FILE_FAILURE, responseText=Testing the handling of 'DUPLICATE FILE' identification.] (existing file checksum does not match)
          Result: Received event: 296b2cc3: 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@39d62e47[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1ced1fb9[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={-70}, calculationTimestamp=2015-11-21T02:19:32.299+01:00], null, org.bitrepository.client.TestEventHandler@5d28e108, TEST-AUDIT-TRAIL)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@4d2bcca8[correlationID=6712e94e-d1cd-41f3-9272-81d707c725a5, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=fileExistsOnPillarDifferentChecksumFromPillar, to=<null>, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, fileID=default-test-file.txt, fileSize=0]
          Result: Received event: 6712e94e: 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: 6712e94e: 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@2b592f17[responseCode=DUPLICATE_FILE_FAILURE, responseText=Testing the handling of 'DUPLICATE FILE' identification.] (existing file checksum does not match)
          Result: Received event: 6712e94e: 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@2fedae96, TEST-AUDIT-TRAIL)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@4945cd1f[correlationID=814a2e49-577e-4fbe-8761-2daa651d4dd6, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=fileExistsOnPillarNoChecksumFromPillar, to=<null>, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, fileID=default-test-file.txt, fileSize=0]
          Result: Received event: 814a2e49: 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: 814a2e49: 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@2dbfcbe4[responseCode=DUPLICATE_FILE_FAILURE, responseText=Testing the handling of 'DUPLICATE FILE' identification.]
          Result: Received event: 814a2e49: 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@3ff83cc8, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@6dd8ac29[correlationID=ab9a0fc9-a974-4011-895a-bc2d055c715b, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=noPillarsResponding, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt, fileSize=0]
          Result: Received event: ab9a0fc9: 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: ab9a0fc9: 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: ab9a0fc9: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor
          Result: Received event: ab9a0fc9: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
          Result: Received event: ab9a0fc9: 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@7225583d, TEST-AUDIT-TRAIL)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@5fe7454c[correlationID=bccd1b8f-da08-438e-8a87-c0d978978794, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=noReturnChecksumsWithChecksumPillar, to=<null>, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, fileID=default-test-file.txt, fileSize=0]
          Result: Received event: bccd1b8f: 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: bccd1b8f: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
        Step: Send an normal identification response from pillar2.
          Result: Received event: bccd1b8f: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
          Result: Received event: bccd1b8f: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2, Pillar1]
          Result: Received event: bccd1b8f: 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@71c1e70f[correlationID=bccd1b8f-da08-438e-8a87-c0d978978794, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=noReturnChecksumsWithChecksumPillar, to=<null>, 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=<null>, checksumRequestForNewFile=<null>]
          Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@1469015e[correlationID=bccd1b8f-da08-438e-8a87-c0d978978794, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=noReturnChecksumsWithChecksumPillar, to=<null>, 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=<null>, checksumRequestForNewFile=<null>]
      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@5d38758a, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@4acae4c7[correlationID=63178d73-d271-4fd9-9161-bc76ed4df008, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=normalPutFile, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt, fileSize=0]
          Result: Received event: 63178d73: 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: 63178d73: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 63178d73: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: 63178d73: 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@27bfa57f[correlationID=63178d73-d271-4fd9-9161-bc76ed4df008, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=normalPutFile, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>, checksumRequestForNewFile=<null>]
        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: 63178d73: 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: 63178d73: PUT_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, requestedChecksumResult=null
          Result: Received event: 63178d73: PUT_FILE for file default-test-file.txt: COMPLETE: 
      Test success: normalPutFile
      Test starting: onePillarPutRetryFailure
        Reference: <a href=https://sbforge.org/jira/browse/BITMAG-810>BITMAG-810 Reference client should be able to retry failed file transfers</a>
        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@310df168, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@3606c525[correlationID=e5192a73-5f04-4828-85c0-66ce51b2e70a, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarPutRetryFailure, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt, fileSize=0]
          Result: Received event: e5192a73: 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: e5192a73: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: e5192a73: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: e5192a73: 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@27959922[correlationID=e5192a73-5f04-4828-85c0-66ce51b2e70a, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarPutRetryFailure, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>, checksumRequestForNewFile=<null>]
        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@794daa09[correlationID=e5192a73-5f04-4828-85c0-66ce51b2e70a, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarPutRetryFailure, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>, checksumRequestForNewFile=<null>]
          Result: Received event: e5192a73: 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@796267e8[correlationID=e5192a73-5f04-4828-85c0-66ce51b2e70a, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarPutRetryFailure, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>, checksumRequestForNewFile=<null>]
          Result: Received event: e5192a73: 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: e5192a73: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FILE_TRANSFER_FAILURE
          Result: Received event: e5192a73: PUT_FILE for file default-test-file.txt: FAILED: , Failed operation. Cause(s):
[e5192a73: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FILE_TRANSFER_FAILURE]
      Test success: onePillarPutRetryFailure
      Test starting: onePillarPutRetrySuccess
        Reference: <a href=https://sbforge.org/jira/browse/BITMAG-810>BITMAG-810 Reference client should be able to retry failed file transfers</a>
        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@2c2c1790, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@645a9649[correlationID=c15655aa-ce0d-45d3-acbe-4a16afb35475, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarPutRetrySuccess, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt, fileSize=0]
          Result: Received event: c15655aa: 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: c15655aa: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: c15655aa: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: c15655aa: 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@7631fb3e[correlationID=c15655aa-ce0d-45d3-acbe-4a16afb35475, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarPutRetrySuccess, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>, checksumRequestForNewFile=<null>]
        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@3aede2ff[correlationID=c15655aa-ce0d-45d3-acbe-4a16afb35475, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarPutRetrySuccess, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>, checksumRequestForNewFile=<null>]
          Result: Received event: c15655aa: 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: c15655aa: PUT_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, requestedChecksumResult=null
          Result: Received event: c15655aa: PUT_FILE for file default-test-file.txt: COMPLETE: 
      Test success: onePillarPutRetrySuccess
      Test starting: onePillarRespondingWithPartialPutAllowed
        Reference: <a href=https://sbforge.org/jira/browse/BITMAG-598>BITMAG-598 It should be possible to putFiles, even though only a subset of the pillars are available</a>
        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@3b538e2a, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@7262532a[correlationID=fdd38dfb-4679-4053-b4d2-2766f32291d0, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarRespondingWithPartialPutAllowed, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt, fileSize=0]
          Result: Received event: fdd38dfb: 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: fdd38dfb: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
        Step: Await the timeout.
          Result: Received event: fdd38dfb: 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: fdd38dfb: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
          Result: Received event: fdd38dfb: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: fdd38dfb: 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@36a33ea8[correlationID=fdd38dfb-4679-4053-b4d2-2766f32291d0, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarRespondingWithPartialPutAllowed, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>, checksumRequestForNewFile=<null>]
        Step: The client should proceed to send a putFileOperation request to the responding pillar.
        Step: Send a pillar complete event
          Result: Received event: fdd38dfb: PUT_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, requestedChecksumResult=null
          Result: Received event: fdd38dfb: PUT_FILE for file default-test-file.txt: FAILED: , Failed operation. Cause(s):
[fdd38dfb: 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@1d7135c, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@2c2f4769[correlationID=07a4eb7d-4109-4ae2-9ecb-2ccd8204b52c, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarRespondingWithPartialPutDisallowed, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt, fileSize=0]
          Result: Received event: 07a4eb7d: 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: 07a4eb7d: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
        Step: Await the timeout.
          Result: Received event: 07a4eb7d: 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: 07a4eb7d: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
          Result: Received event: 07a4eb7d: 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@3057728e, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@5dbd7f00[correlationID=c6937414-314c-4f67-a713-25739d6ce369, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=putClientOperationTimeout, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt, fileSize=0]
          Result: Received event: c6937414: 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: c6937414: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: c6937414: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: c6937414: 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@138c2ba[correlationID=c6937414-314c-4f67-a713-25739d6ce369, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=putClientOperationTimeout, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>, checksumRequestForNewFile=<null>]
        Step: Validate the steps of the PutClient by going through the events.
        Step: Do not respond. Just await the timeout.
          Result: Received event: c6937414: 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@36dab184, TEST-AUDIT-TRAIL)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@71b9b035[correlationID=e047a5f7-5c29-4084-a16a-4a89891c596d, 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: e047a5f7: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file
        Step: Send pillar response.
          Result: Received event: e047a5f7: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: e047a5f7: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: e047a5f7: 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@724945[correlationID=e047a5f7-5c29-4084-a16a-4a89891c596d, 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=<null>, checksumRequestForNewFile=<null>]
        Step: Validate the steps of the PutClient by going through the events.
        Step: Send a failed response message to the PutClient.
          Result: Received event: e047a5f7: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE, Verifying that a failure can be understood!
          Result: Received event: e047a5f7: PUT_FILE for file default-test-file.txt: FAILED: , Failed operation. Cause(s):
[e047a5f7: 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: <a href=https://sbforge.org/jira/browse/BITMAG-925>BITMAG-925 Client will always try to put to the pillars defined in the first collection</a>
        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@5af7a7, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@685e8e17[correlationID=28e3e6a7-7e93-4147-ad33-d547a892897a, collectionID=SinglePillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=putToOtherCollection, to=Pillar2, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt, fileSize=0]
          Result: Received event: 28e3e6a7: 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: 28e3e6a7: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
          Result: Received event: 28e3e6a7: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
          Result: Received event: 28e3e6a7: 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@5f3705e7[correlationID=28e3e6a7-7e93-4147-ad33-d547a892897a, collectionID=SinglePillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=putToOtherCollection, to=Pillar2, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar2, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>, checksumRequestForNewFile=<null>]
        Step: Send a put complete event from the pillar
          Result: Received event: 28e3e6a7: PUT_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2, requestedChecksumResult=null
          Result: Received event: 28e3e6a7: 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: <a href="https://sbforge.org/jira/browse/BITMAG-677">BITMAG-677put, replace and delete clients fails if return checksums are requested and a checksumpillar is involved</a>
        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@28ea7f58[checksumType=HMAC_MD5, checksumSalt={-86}, otherChecksumType=<null>], org.bitrepository.client.TestEventHandler@2cf7ada5, TEST-AUDIT-TRAIL)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@14c6d1b7[correlationID=a5c0699e-c869-4744-abdf-42b2261583f4, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=saltedReturnChecksumsWithChecksumPillar, to=<null>, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, fileID=default-test-file.txt, fileSize=0]
          Result: Received event: a5c0699e: 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: a5c0699e: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
        Step: Send an normal identification response from pillar2.
          Result: Received event: a5c0699e: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
          Result: Received event: a5c0699e: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2, Pillar1]
          Result: Received event: a5c0699e: 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@664c6bbc[correlationID=a5c0699e-c869-4744-abdf-42b2261583f4, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=saltedReturnChecksumsWithChecksumPillar, to=<null>, 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=<null>, checksumRequestForNewFile=<null>]
          Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@442545ab[correlationID=a5c0699e-c869-4744-abdf-42b2261583f4, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=saltedReturnChecksumsWithChecksumPillar, to=<null>, 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=<null>, checksumRequestForNewFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@28ea7f58[checksumType=HMAC_MD5, checksumSalt={-86}, otherChecksumType=<null>]]
      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@26ae9861[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@5b1b5daf[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-11-21T02:19:34.695+01:00], null, org.bitrepository.client.TestEventHandler@66e74d3, TEST-AUDIT-TRAIL)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@1e1c1634[correlationID=64169c3f-b485-427e-acce-b7f3aa720cdc, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=sameFileExistsOnOnePillar, to=<null>, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, fileID=default-test-file.txt, fileSize=0]
          Result: Received event: 64169c3f: 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: 64169c3f: PUT_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, requestedChecksumResult=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@38691f8d[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@463a0302[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-11-21T02:19:34.695+01:00], File already existed on Pillar1
        Step: Send an identification response from the second pillar.
          Result: Received event: 64169c3f: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
          Result: Received event: 64169c3f: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
          Result: Received event: 64169c3f: 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@79228440[correlationID=64169c3f-b485-427e-acce-b7f3aa720cdc, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=sameFileExistsOnOnePillar, to=<null>, 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@26ae9861[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@5b1b5daf[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-11-21T02:19:34.695+01:00], checksumRequestForNewFile=<null>]
        Step: The client should proceed to send a putFileOperation request to the second pillar.
        Step: Send a pillar complete event
          Result: Received event: 64169c3f: PUT_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2, requestedChecksumResult=null
          Result: Received event: 64169c3f: 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 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@345f429[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@3464d24c[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], 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@341f2f4c[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, 10, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@68754439[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@3464d24c[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], 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@341f2f4c[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], org.bitrepository.client.TestEventHandler@44bd11a2, null
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileRequest@56595dcb[correlationID=bc9713e3-b279-4abf-9033-ab3339a78e73, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-ReplaceFileClientComponentTest-cibuild01, from=replaceClientIdentificationTimeout, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt, fileSize=<null>]
          Result: Received event: bc9713e3: 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: bc9713e3: 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: bc9713e3: REPLACE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor
          Result: Received event: bc9713e3: 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@51dcf51b[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6eb58fdd[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], 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@7a0619a8[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, 10, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@5df9d890[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6eb58fdd[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], 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@7a0619a8[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], org.bitrepository.client.TestEventHandler@6b3b9a19, null
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileRequest@29b23bc4[correlationID=fdd1b63a-f68b-44b7-bbb0-eaf4fe9d3575, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-ReplaceFileClientComponentTest-cibuild01, from=replaceClientOperationTimeout, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt, fileSize=<null>]
          Result: Received event: fdd1b63a: 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: fdd1b63a: REPLACE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: fdd1b63a: REPLACE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: fdd1b63a: 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@701dc5ad[correlationID=fdd1b63a-f68b-44b7-bbb0-eaf4fe9d3575, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-ReplaceFileClientComponentTest-cibuild01, from=replaceClientOperationTimeout, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@51dcf51b[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6eb58fdd[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], 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@7a0619a8[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=10, checksumDataForNewFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@5df9d890[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6eb58fdd[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], 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@7a0619a8[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>]]
        Step: Validate the steps of the ReplaceClient by going through the events.
        Step: Do not respond. Just await the timeout.
          Result: Received event: fdd1b63a: 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@5c8d22de[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@71ef3f0c[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], 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@471021f8[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, 0, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@3bbd9232[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@71ef3f0c[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], 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@471021f8[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], org.bitrepository.client.TestEventHandler@e13cc49, null
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileRequest@60c95d8[correlationID=395fdb5d-9e10-4e71-8e56-682d175ab503, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-ReplaceFileClientComponentTest-cibuild01, from=replaceClientPillarFailed, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt, fileSize=<null>]
          Result: Received event: 395fdb5d: 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: 395fdb5d: REPLACE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 395fdb5d: REPLACE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: 395fdb5d: 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@172e4d3a[correlationID=395fdb5d-9e10-4e71-8e56-682d175ab503, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-ReplaceFileClientComponentTest-cibuild01, from=replaceClientPillarFailed, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@5c8d22de[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@71ef3f0c[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], 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@471021f8[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@3bbd9232[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@71ef3f0c[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], 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@471021f8[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>]]
        Step: Validate the steps of the ReplaceClient by going through the events.
        Step: Send a failed response message to the ReplaceClient.
          Result: Received event: 395fdb5d: REPLACE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE, Verifying that a failure can be understood!
          Result: Received event: 395fdb5d: REPLACE_FILE for file default-test-file.txt: FAILED: , Failed operation. Cause(s):
[395fdb5d: 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@31dd8a0b[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@346e62d7[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], 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@59d64b60[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, 10, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@60e72ced[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@346e62d7[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], 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@59d64b60[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], org.bitrepository.client.TestEventHandler@3d376f28, null
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileRequest@7a08da83[correlationID=21c6c29e-516c-4d98-995c-8325f75f0ee0, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-ReplaceFileClientComponentTest-cibuild01, from=replaceClientTester, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt, fileSize=<null>]
          Result: Received event: 21c6c29e: 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: 21c6c29e: REPLACE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 21c6c29e: REPLACE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: 21c6c29e: 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@4837c56d[correlationID=21c6c29e-516c-4d98-995c-8325f75f0ee0, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-ReplaceFileClientComponentTest-cibuild01, from=replaceClientTester, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@31dd8a0b[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@346e62d7[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], 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@59d64b60[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=10, checksumDataForNewFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@60e72ced[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@346e62d7[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], 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@59d64b60[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>]]
        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: 21c6c29e: 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: 21c6c29e: REPLACE_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, checksum for new file: 'org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@60e72ced[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@346e62d7[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], 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: 21c6c29e: 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@b79953e[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6c743da[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], 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@722af653[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6c743da[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], 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@71fff0b[checksumType=MD5, checksumSalt={-86}, otherChecksumType=<null>], org.bitrepository.client.TestEventHandler@40085ab3, null
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileRequest@7c6d18fb[correlationID=129c39a6-f027-4e8c-8e43-4660e9ee2da7, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-ReplaceFileClientComponentTest-cibuild01, from=saltedReturnChecksumsForNewFileWithChecksumPillar, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt, fileSize=<null>]
          Result: Received event: 129c39a6: 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: 129c39a6: REPLACE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 129c39a6: REPLACE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: 129c39a6: 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@214faadd[correlationID=129c39a6-f027-4e8c-8e43-4660e9ee2da7, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-ReplaceFileClientComponentTest-cibuild01, from=saltedReturnChecksumsForNewFileWithChecksumPillar, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@b79953e[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6c743da[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], 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=<null>, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@722af653[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6c743da[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], 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=<null>]
      Test success: saltedReturnChecksumsForNewFileWithChecksumPillar
      Test starting: verifyReplaceFileClientFromFactory
        Description: Testing the initialization through the ModifyComponentFactory.
        Step: Use the ModifyComponentFactory to instantiate a ReplaceFileClient.
      Test success: verifyReplaceFileClientFromFactory
    Starting testcase 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 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: Random1448068777015pillar is not a valid pillar for collection TwoPillarCollection
The collection contains the following pillars: [Pillar1, Pillar2]
      Test success: unknownPillarArgumentTest
    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: Random1448068777865pillar 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 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@135a2a14[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1464019a[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], 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@4339a2e5[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], eventHandler, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@68645c77[correlationID=2f147acd-fe70-4636-9acd-d48e94441038, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientIdentificationTimeout, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt]
          Result: Received event: 2f147acd: 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: 2f147acd: 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: 2f147acd: DELETE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor
          Result: Received event: 2f147acd: 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@1456ada1[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@699f5e36[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], 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@1e09f286[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], eventHandler, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@55fc6954[correlationID=9d6f9591-27a2-4a0a-a88a-e3882c092c37, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientOperationTimeout, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt]
          Result: Received event: 9d6f9591: 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: 9d6f9591: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 9d6f9591: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: 9d6f9591: 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@679b73ab[correlationID=9d6f9591-27a2-4a0a-a88a-e3882c092c37, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientOperationTimeout, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@1456ada1[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@699f5e36[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], 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@1e09f286[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>]]
        Step: Validate the steps of the DeleteClient by going through the events.
        Step: Do not respond. Just await the timeout.
          Result: Received event: 9d6f9591: 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@6818550d[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@4d310fe6[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-11-21T02:19:39.877+01:00], null, eventHandler, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@34923f7f[correlationID=1a7d55e5-7607-452a-8b8c-d08a5fa6f508, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientOtherPillarFailedDuringIdentification, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt]
          Result: Received event: 1a7d55e5: 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: 1a7d55e5: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 1a7d55e5: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: 1a7d55e5: 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@28d38288[correlationID=1a7d55e5-7607-452a-8b8c-d08a5fa6f508, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientOtherPillarFailedDuringIdentification, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@6818550d[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@4d310fe6[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-11-21T02:19:39.877+01:00], checksumRequestForExistingFile=<null>]
        Step: Send a final response message from pillar 1 to the DeleteClient.
          Result: Received event: 1a7d55e5: DELETE_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, DeleteFileResult=null
          Result: Received event: 1a7d55e5: 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@6afa82fe[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7cb8b526[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], 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@797b2044[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], eventHandler, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@45cfbcc2[correlationID=3ca07d41-7faa-4519-bef6-9c76e9eedd73, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientPillarFailedDuringPerform, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt]
          Result: Received event: 3ca07d41: 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: 3ca07d41: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 3ca07d41: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: 3ca07d41: 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@42b4b037[correlationID=3ca07d41-7faa-4519-bef6-9c76e9eedd73, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientPillarFailedDuringPerform, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@6afa82fe[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7cb8b526[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], 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@797b2044[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>]]
        Step: Validate the steps of the DeleteClient by going through the events.
        Step: Send a failed response message to the DeleteClient.
          Result: Received event: 3ca07d41: DELETE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE, Verifying that a failure can be understood!
          Result: Received event: 3ca07d41: DELETE_FILE for file default-test-file.txt: FAILED: , Failed operation. Cause(s):
[3ca07d41: 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@6c8d6a2f[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@394c61cb[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-11-21T02:19:41.903+01:00], null, eventHandler, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@71713254[correlationID=234cb80c-e1a0-41d3-867e-1f2a7988b7ff, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientSpecifiedPillarFailedDuringIdentification, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt]
          Result: Received event: 234cb80c: 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: 234cb80c: DELETE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: IDENTIFICATION_NEGATIVE
          Result: Received event: 234cb80c: 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@32144b3c[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@3601fb92[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], 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@64434d5c[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], eventHandler, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@4a57771a[correlationID=126b9cc8-37ba-4de0-a5dd-8a9fbd0930cb, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientTester, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt]
          Result: Received event: 126b9cc8: 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: 126b9cc8: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 126b9cc8: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: 126b9cc8: 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@636e356f[correlationID=126b9cc8-37ba-4de0-a5dd-8a9fbd0930cb, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientTester, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@32144b3c[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@3601fb92[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], 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@64434d5c[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>]]
        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: 126b9cc8: 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: 126b9cc8: DELETE_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, DeleteFileResult=null
          Result: Received event: 126b9cc8: 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@20defbeb[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1eb738e5[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-11-21T02:19:42.807+01:00], null, eventHandler, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@456c2b84[correlationID=ae657321-a5a5-4cf2-b045-d7b62e695984, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteOnChecksumPillar, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt]
          Result: Received event: ae657321: 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: ae657321: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: ae657321: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: ae657321: 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@6f3679a7[correlationID=ae657321-a5a5-4cf2-b045-d7b62e695984, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteOnChecksumPillar, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@20defbeb[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1eb738e5[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-11-21T02:19:42.807+01:00], checksumRequestForExistingFile=<null>]
      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@6b2f16b9[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@67d15f2[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-11-21T02:19:45.000+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1fb25bca[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], eventHandler, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@2e1e02b8[correlationID=9fe12e16-513f-4387-bbce-c8d8b1d2d843, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteOnChecksumPillarWithDefaultReturnChecksumType, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt]
          Result: Received event: 9fe12e16: 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: 9fe12e16: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 9fe12e16: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: 9fe12e16: 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@53ab03c9[correlationID=9fe12e16-513f-4387-bbce-c8d8b1d2d843, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteOnChecksumPillarWithDefaultReturnChecksumType, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@6b2f16b9[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@67d15f2[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-11-21T02:19:45.000+01:00], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1fb25bca[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>]]
      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@360ea519[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2e643cad[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-11-21T02:19:45.207+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@14270971[checksumType=MD5, checksumSalt={-86}, otherChecksumType=<null>], eventHandler, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@21c64b8e[correlationID=5f75b2f0-59b2-49e2-bbfe-ee2d7b953065, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteOnChecksumPillarWithSaltedReturnChecksumType, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt]
          Result: Received event: 5f75b2f0: 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: 5f75b2f0: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 5f75b2f0: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: 5f75b2f0: 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@6d2dcd7f[correlationID=5f75b2f0-59b2-49e2-bbfe-ee2d7b953065, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteOnChecksumPillarWithSaltedReturnChecksumType, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@360ea519[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2e643cad[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-11-21T02:19:45.207+01:00], checksumRequestForExistingFile=<null>]
      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@117eac4a[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@cdb12a5[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-11-21T02:19:45.387+01:00], null, eventHandler, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@59732214[correlationID=7cbfed0f-7b03-4c18-a0e6-9fc237942390, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=fileAlreadyDeletedFromPillar, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt]
          Result: Received event: 7cbfed0f: 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: 7cbfed0f: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 7cbfed0f: DELETE_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, DeleteFileResult=null
          Result: Received event: 7cbfed0f: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: []
          Result: Received event: 7cbfed0f: 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 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@15db58c9[correlationID=9054fa87-2f98-4aa1-9b0c-6152e925d964, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=chooseFastestPillarGetFileClient, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt]
          Result: Received event: 9054fa87: 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: 9054fa87: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID THE-AVERAGE-PILLAR
          Result: Received event: 9054fa87: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID THE-FAST-PILLAR
          Result: Received event: 9054fa87: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID THE-SLOW-PILLAR
          Result: Received event: 9054fa87: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [THE-FAST-PILLAR]
          Result: Received event: 9054fa87: 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@3f88558d[correlationID=9054fa87-2f98-4aa1-9b0c-6152e925d964, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=chooseFastestPillarGetFileClient, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=THE-FAST-PILLAR, fileID=default-test-file.txt, filePart=<null>, 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@78f2bb1b[correlationID=90431d5a-2702-4e4f-949c-3f7f8b41c52f, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=conversationTimeout, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt]
          Result: Received event: 90431d5a: 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: 90431d5a: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 90431d5a: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: 90431d5a: 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@10323056[correlationID=90431d5a-2702-4e4f-949c-3f7f8b41c52f, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=conversationTimeout, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, filePart=<null>, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt]
        Step: Wait for 1 second
02:19:48.149 WARN  o.b.c.c.m.CollectionBasedConversationMediator - Failing timed out conversation 90431d5a-2702-4e4f-949c-3f7f8b41c52f (Age 999ms)
          Result: Received event: 90431d5a: GET_FILE for file default-test-file.txt: FAILED: , Failing timed out conversation 90431d5a-2702-4e4f-949c-3f7f8b41c52f
      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@5b9e7722[correlationID=7d6ed10e-1084-49e6-91ff-bc131f591a36, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=failureDuringPerform, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt]
          Result: Received event: 7d6ed10e: 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: 7d6ed10e: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 7d6ed10e: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
          Result: Received event: 7d6ed10e: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: 7d6ed10e: 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@48efa366[correlationID=7d6ed10e-1084-49e6-91ff-bc131f591a36, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=failureDuringPerform, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, filePart=<null>, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt]
        Step: Send a failure response from pillar1
          Result: Received event: 7d6ed10e: GET_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE
          Result: Received event: 7d6ed10e: GET_FILE for file default-test-file.txt: FAILED: , Failed to get file from Pillar1, org.bitrepository.bitrepositoryelements.ResponseInfo@1487c3b3[responseCode=FAILURE, responseText=<null>]
      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@79749108[correlationID=c60761d9-2d41-4030-9731-a7239c23a14a, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=getFileClientWithChecksumPillarInvolved, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt]
          Result: Received event: c60761d9: 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: c60761d9: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
          Result: Received event: c60761d9: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
          Result: Received event: c60761d9: 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@f284a7a[correlationID=c60761d9-2d41-4030-9731-a7239c23a14a, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=getFileClientWithChecksumPillarInvolved, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar2, fileID=default-test-file.txt, filePart=<null>, 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: c60761d9: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2
          Result: Received event: c60761d9: 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@4d3c0cce[correlationID=c02d48d0-462d-4d5a-a94a-f13a16b71a44, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=getFileClientWithIdentifyTimeout, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt]
          Result: Received event: c02d48d0: 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: c02d48d0: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
        Step: Wait 1 second.
          Result: Received event: c02d48d0: 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: c02d48d0: GET_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
          Result: Received event: c02d48d0: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: c02d48d0: 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@151e786c[correlationID=c02d48d0-462d-4d5a-a94a-f13a16b71a44, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=getFileClientWithIdentifyTimeout, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, filePart=<null>, 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: c02d48d0: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1
          Result: Received event: c02d48d0: 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@27a4a890[correlationID=f6ac1680-d1ad-4816-944e-08515c21bb10, collectionID=SinglePillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=getFileFromOtherCollection, to=Pillar2, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt]
          Result: Received event: f6ac1680: 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: f6ac1680: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
          Result: Received event: f6ac1680: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
          Result: Received event: f6ac1680: 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@19b5f793[correlationID=f6ac1680-d1ad-4816-944e-08515c21bb10, collectionID=SinglePillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=getFileFromOtherCollection, to=Pillar2, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar2, fileID=default-test-file.txt, filePart=<null>, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt]
        Step: Send a complete event from the pillar
          Result: Received event: f6ac1680: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2
          Result: Received event: f6ac1680: 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@19cc4b7d[correlationID=4ff592f4-834c-443d-bc3c-7ce8f0fbec57, 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: 4ff592f4: 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: 4ff592f4: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
          Result: Received event: 4ff592f4: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
          Result: Received event: 4ff592f4: 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@1d6d1a18[correlationID=4ff592f4-834c-443d-bc3c-7ce8f0fbec57, 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=<null>, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt]
        Step: Send a GetFileProgressResponse.
          Result: Received event: 4ff592f4: GET_FILE for file default-test-file.txt: PROGRESS: ContributorID Pillar2, First test progress response message
        Step: Send a GetFileFinalResponse.
          Result: Received event: 4ff592f4: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2
          Result: Received event: 4ff592f4: 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@55f2a26d[correlationID=759783a5-694d-4a6d-8e27-fb089623e4b7, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=getFileFromSpecificPillarWithFilePart, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt]
          Result: Received event: 759783a5: 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: 759783a5: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 759783a5: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: 759783a5: 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@16987824[correlationID=759783a5-694d-4a6d-8e27-fb089623e4b7, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=getFileFromSpecificPillarWithFilePart, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, filePart=org.bitrepository.bitrepositoryelements.FilePart@3f3cacde[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: 759783a5: 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: 759783a5: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1
          Result: Received event: 759783a5: 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@19bc42ea[correlationID=658f3e84-6629-4ec1-9bd0-f75b75edac2d, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=noIdentifyResponse, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt]
          Result: Received event: 658f3e84: GET_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetFile
        Step: Wait for 1 seconds
          Result: Received event: 658f3e84: 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: 658f3e84: GET_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor
          Result: Received event: 658f3e84: GET_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
          Result: Received event: 658f3e84: 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@1bb6b61c[correlationID=d5e4f410-568d-4b6d-9237-05a4064aaec3, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=singleComponentFailureDuringIdentify, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt]
          Result: Received event: d5e4f410: 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: d5e4f410: 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: d5e4f410: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
          Result: Received event: d5e4f410: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
          Result: Received event: d5e4f410: 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@4e2c656a[correlationID=d5e4f410-568d-4b6d-9237-05a4064aaec3, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=singleComponentFailureDuringIdentify, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar2, fileID=default-test-file.txt, filePart=<null>, 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: d5e4f410: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2
          Result: Received event: d5e4f410: 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@ca129b5[correlationID=c63ca31f-40fb-4419-bbfc-daf4591b8116, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=testNoSuchFileMultiplePillars, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileID=ERROR-NO-SUCH-FILE-ERROR]
          Result: Received event: c63ca31f: 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: c63ca31f: 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: c63ca31f: 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: c63ca31f: 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@5eb8dfd0[correlationID=a8f2c34c-5584-44bf-a5a4-50cc798f459d, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=testNoSuchFileSpecificPillar, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=ERROR-NO-SUCH-FILE-ERROR]
          Result: Received event: a8f2c34c: 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: a8f2c34c: 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: a8f2c34c: 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 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: Random1448068794364pillar 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 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: Random1448068797194pillar is not a valid pillar for collection TwoPillarCollection
The collection contains the following pillars: [Pillar1, Pillar2]
      Test success: unknownPillarArgumentTest
    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 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: ac3349b4: GET_STATUS: IDENTIFY_REQUEST_SENT: , Identifying contributors for getting status
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetStatusRequest@7751d800[correlationID=ac3349b4-d02d-451d-9190-c0236d1aaf2c, collectionID=<null>, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetStatusClientComponentTest-cibuild01, from=getAllStatuses, to=<null>, version=28, minVersion=24, auditTrailInformation=]
        Step: Send a identifyResponse from each pillar
          Result: Received event: ac3349b4: GET_STATUS: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: ac3349b4: GET_STATUS: COMPONENT_IDENTIFIED: ContributorID Pillar2
          Result: Received event: ac3349b4: GET_STATUS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2]
          Result: Received event: ac3349b4: GET_STATUS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending GetStatusRequest
          Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetStatusRequest@2dac8ef8[correlationID=ac3349b4-d02d-451d-9190-c0236d1aaf2c, collectionID=<null>, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetStatusClientComponentTest-cibuild01, from=getAllStatuses, to=<null>, version=28, minVersion=24, auditTrailInformation=, contributor=Pillar1]
          Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetStatusRequest@6fe0e4a9[correlationID=ac3349b4-d02d-451d-9190-c0236d1aaf2c, collectionID=<null>, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetStatusClientComponentTest-cibuild01, from=getAllStatuses, to=<null>, version=28, minVersion=24, auditTrailInformation=, contributor=Pillar2]
        Step: Send a final response from pillar 1
          Result: Received event: ac3349b4: GET_STATUS: COMPONENT_COMPLETE: ContributorID Pillar1, resulting status: org.bitrepository.bitrepositoryelements.ResultingStatus@41de65[statusInfo=org.bitrepository.bitrepositoryelements.StatusInfo@1aa96f4f[statusCode=OK, statusText=Everythings fine..], statusTimestamp=2015-11-21T02:19:57.320+01:00]
        Step: Send a final response from pillar 2
          Result: Received event: ac3349b4: GET_STATUS: COMPONENT_COMPLETE: ContributorID Pillar2, resulting status: org.bitrepository.bitrepositoryelements.ResultingStatus@689e5e35[statusInfo=org.bitrepository.bitrepositoryelements.StatusInfo@1960074f[statusCode=OK, statusText=Everythings fine..], statusTimestamp=2015-11-21T02:19:57.320+01:00]
          Result: Received event: ac3349b4: 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: a9e73ed9: GET_STATUS: IDENTIFY_REQUEST_SENT: , Identifying contributors for getting status
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetStatusRequest@524d3f70[correlationID=a9e73ed9-76c7-4fa5-a5c0-36d6a45a0728, collectionID=<null>, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetStatusClientComponentTest-cibuild01, from=incompleteSetOfIdendifyResponses, to=<null>, version=28, minVersion=24, auditTrailInformation=]
        Step: Send a identifyResponse from pillar 1
          Result: Received event: a9e73ed9: GET_STATUS: COMPONENT_IDENTIFIED: ContributorID Pillar1
        Step: Wait for timeout event
          Result: Received event: a9e73ed9: GET_STATUS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar2]
          Result: Received event: a9e73ed9: GET_STATUS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
          Result: Received event: a9e73ed9: GET_STATUS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: a9e73ed9: GET_STATUS: REQUEST_SENT: ContributorID [Pillar1], Sending GetStatusRequest
          Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetStatusRequest@67414728[correlationID=a9e73ed9-76c7-4fa5-a5c0-36d6a45a0728, collectionID=<null>, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetStatusClientComponentTest-cibuild01, from=incompleteSetOfIdendifyResponses, to=<null>, version=28, minVersion=24, auditTrailInformation=, contributor=Pillar1]
      Test success: incompleteSetOfIdendifyResponses
      Test starting: verifyGetStatusClientFromFactory
      Test success: verifyGetStatusClientFromFactory
    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 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: Random1448068801113pillar is not a valid pillar for collection TwoPillarCollection
The collection contains the following pillars: [Pillar1, Pillar2]
      Test success: unknownPillarArgumentTest
      Finished testcase
  Finished suite
Finished project
Tests run: 156, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 65.424 sec - in TestSuite

Results :

Tests run: 156, Failures: 0, Errors: 0, Skipped: 0

[JENKINS] Recording test results
[INFO] 
[INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ bitrepository-client ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/target/bitrepository-client-1.6-SNAPSHOT.jar
[INFO] 
[INFO] --- maven-jar-plugin:2.4:test-jar (default) @ bitrepository-client ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/target/bitrepository-client-1.6-SNAPSHOT-tests.jar
[INFO] 
[INFO] --- maven-source-plugin:2.2.1:jar-no-fork (attach-sources-no-fork) @ bitrepository-client ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/target/bitrepository-client-1.6-SNAPSHOT-sources.jar
[INFO] 
[INFO] --- maven-assembly-plugin:2.4:single (make-assembly) @ bitrepository-client ---
[INFO] Reading assembly descriptor: src/main/assembly/assembly.xml
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/target/bitrepository-client-1.6-SNAPSHOT-distribution.tar.gz
[INFO] 
[INFO] --- maven-install-plugin:2.5.1:install (default-install) @ bitrepository-client ---
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/target/bitrepository-client-1.6-SNAPSHOT.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-client/1.6-SNAPSHOT/bitrepository-client-1.6-SNAPSHOT.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-client/1.6-SNAPSHOT/bitrepository-client-1.6-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/target/bitrepository-client-1.6-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-client/1.6-SNAPSHOT/bitrepository-client-1.6-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/target/bitrepository-client-1.6-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-client/1.6-SNAPSHOT/bitrepository-client-1.6-SNAPSHOT-sources.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/target/bitrepository-client-1.6-SNAPSHOT-distribution.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-client/1.6-SNAPSHOT/bitrepository-client-1.6-SNAPSHOT-distribution.tar.gz
[JENKINS] Archiving disabled