SuccessConsole Output

Skipping 112 KB.. Full Log
, null, org.bitrepository.client.TestEventHandler@37f37699, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@36fd028d[correlationID=a673b6ff-69f0-455c-8cce-1e756feb68fb, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=oneContributorNotRespondingTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@16c574c4[fileID=<null>, allFileIDs=true], checksumRequestForExistingFile=<null>]
          Result: Received event: a673b6ff: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums
        Step: Send a identification response from contributor1.
          Result: Received event: a673b6ff: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar1
        Step: Wait 1 second.
          Result: Received event: a673b6ff: GET_CHECKSUMS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar2]
          Result: Received event: a673b6ff: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
          Result: Received event: a673b6ff: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: a673b6ff: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar1], Sending GetFileIDsRequest's
          Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@6875a97a[correlationID=a673b6ff-69f0-455c-8cce-1e756feb68fb, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=oneContributorNotRespondingTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@263307a9[fileID=<null>, allFileIDs=true], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, checksumRequestForExistingFile=<null>, resultAddress=<null>]
        Step: Verify that the client continues to the performing phase.
        Step: Send a final response upload message
          Result: Received event: a673b6ff: GET_CHECKSUMS: COMPONENT_COMPLETE: ContributorID Pillar1, PartialResult=false
          Result: Received event: a673b6ff: GET_CHECKSUMS: FAILED: , Failed operation. Cause(s):
[a673b6ff: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor]
      Test success: oneContributorNotRespondingTest
      Test starting: operationTimeoutTest
        Description: Tests the the client handles lack of final responses gracefully.
        Step: Set a 100 ms operation timeout.
        Step: Start the operation
          Stimuli: Calling getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@37f37699, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@5bd5ace9[correlationID=940826a3-1950-4b31-861e-511add01b170, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=operationTimeoutTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@b439e50[fileID=<null>, allFileIDs=true], checksumRequestForExistingFile=<null>]
          Result: Received event: 940826a3: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums
        Step: Send positive responses from the pillar1 and a negative response from pillar2
          Result: Received event: 940826a3: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 940826a3: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE
          Result: Received event: 940826a3: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: 940826a3: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar1], Sending GetFileIDsRequest's
          Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@3cc1990[correlationID=940826a3-1950-4b31-861e-511add01b170, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=operationTimeoutTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@75084fe4[fileID=<null>, allFileIDs=true], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, checksumRequestForExistingFile=<null>, resultAddress=<null>]
        Step: Wait for 1 second
          Result: Received event: 940826a3: GET_CHECKSUMS: FAILED: , Failed to receive responses from all contributors before timeout(100ms). Missing contributors [Pillar1]
      Test success: operationTimeoutTest
    Starting testcase DeleteFileCmdTest
      Test starting: checksumArgumentNonSaltAlgorithmWitoutSaltTest
        Description: Test MD5 checksum without salt -> no failure
      Test success: checksumArgumentNonSaltAlgorithmWitoutSaltTest
      Test starting: checksumArgumentSaltAlgorithmWithSaltTest
        Description: Test HMAC_SHA256 checksum with salt -> No failure
      Test success: checksumArgumentSaltAlgorithmWithSaltTest
      Test starting: defaultSuccessScenarioTest
        Description: Tests simplest arguments for running the CmdLineClient
      Test success: defaultSuccessScenarioTest
      Test starting: missingCollectionArgumentTest
        Description: Tests the scenario, where the collection arguments is missing.
Takes the following arguments:
-p [OPTIONAL] The id of the pillar where the should be performed. If undefined the operations is performed on all pillars.
-R [OPTIONAL] The algorithm of checksum to request in the response from the pillars.
-s The path to the directory with the settings files for the client
-c The id for the collection to perform the operation on.
-C [OPTIONAL] The checksum of the file to be delete.
-S [OPTIONAL] The salt of checksum to request in the response. Requires the ChecksumType argument.
-v Makes the client more verbose
-i The id for the file to perform the operation on.
-k The path to the file containing the private key.
Missing argument: c
      Test success: missingCollectionArgumentTest
      Test starting: missingFileIDArgumentTest
        Description: Tests the scenario, where no arguments for file id argument is given.
Takes the following arguments:
-p [OPTIONAL] The id of the pillar where the should be performed. If undefined the operations is performed on all pillars.
-R [OPTIONAL] The algorithm of checksum to request in the response from the pillars.
-s The path to the directory with the settings files for the client
-c The id for the collection to perform the operation on.
-C [OPTIONAL] The checksum of the file to be delete.
-S [OPTIONAL] The salt of checksum to request in the response. Requires the ChecksumType argument.
-v Makes the client more verbose
-i The id for the file to perform the operation on.
-k The path to the file containing the private key.
Missing argument: i
      Test success: missingFileIDArgumentTest
      Test starting: missingPillarArgumentTest
        Description: Tests the different scenarios, with the pillar argument.
Invalid argument: The pillar argument -p must defined for the delete operation, only single pillar deletes are allowed
      Test success: missingPillarArgumentTest
      Test starting: unknownPillarArgumentTest
        Step: Testing against a non-existing pillar id
Invalid argument: Random1447982344795pillar is not a valid pillar for collection TwoPillarCollection
The collection contains the following pillars: [Pillar1, Pillar2]
      Test success: unknownPillarArgumentTest
      Test starting: getChecksumsDeliveredAtUrl
        Description: Tests the delivery of checksums from all pillars at a given URL.
        Step: Ensure the delivery file isn't already present on the http server
        Step: Request the delivery of the checksum of a file from all pillars.
          Stimuli: Calling getChecksums(null, default-test-file.txt, null, file:../bitrepository-core/src/test/resources/test-files//TEST-CHECKSUM-DELIVERY.xml, org.bitrepository.client.TestEventHandler@74d5c83, TEST-AUDIT)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@671d7871[correlationID=1d105044-ee94-4a42-9b7d-2f9137ef6a87, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=getChecksumsDeliveredAtUrl, to=<null>, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@3399d3b0[fileID=default-test-file.txt, allFileIDs=<null>], checksumRequestForExistingFile=<null>]
          Result: Received event: 1d105044: GET_CHECKSUMS for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums
        Step: The pillar sends a response to the identify message.
          Result: Received event: 1d105044: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 1d105044: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
          Result: Received event: 1d105044: GET_CHECKSUMS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2]
          Result: Received event: 1d105044: GET_CHECKSUMS for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending GetFileIDsRequest's
          Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@2d39c3fa[correlationID=1d105044-ee94-4a42-9b7d-2f9137ef6a87, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=getChecksumsDeliveredAtUrl, to=<null>, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@504081be[fileID=default-test-file.txt, allFileIDs=<null>], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, checksumRequestForExistingFile=<null>, resultAddress=file:../bitrepository-core/src/test/resources/test-files//TEST-CHECKSUM-DELIVERY.xml-Pillar1]
          Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@6433611f[correlationID=1d105044-ee94-4a42-9b7d-2f9137ef6a87, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=getChecksumsDeliveredAtUrl, to=<null>, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT, pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@1aec9516[fileID=default-test-file.txt, allFileIDs=<null>], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, checksumRequestForExistingFile=<null>, resultAddress=file:../bitrepository-core/src/test/resources/test-files//TEST-CHECKSUM-DELIVERY.xml-Pillar2]
        Step: Sends a final response from each pillar
          Result: Received event: 1d105044: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, NumberOfChecksums=0, PartialResult=false
          Result: Received event: 1d105044: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2, NumberOfChecksums=0, PartialResult=false
          Result: Received event: 1d105044: GET_CHECKSUMS for file default-test-file.txt: COMPLETE: 
      Test success: getChecksumsDeliveredAtUrl
          Result: The following messages haven't been handled by the testcase: 
org.bitrepository.bitrepositorymessages.GetChecksumsRequest@6433611f[correlationID=1d105044-ee94-4a42-9b7d-2f9137ef6a87, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=getChecksumsDeliveredAtUrl, to=<null>, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT, pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@1aec9516[fileID=default-test-file.txt, allFileIDs=<null>], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, checksumRequestForExistingFile=<null>, resultAddress=file:../bitrepository-core/src/test/resources/test-files//TEST-CHECKSUM-DELIVERY.xml-Pillar2]
02:19:05.067 WARN  o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: 
org.bitrepository.bitrepositorymessages.GetChecksumsRequest@6433611f[correlationID=1d105044-ee94-4a42-9b7d-2f9137ef6a87, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=getChecksumsDeliveredAtUrl, to=<null>, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT, pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@1aec9516[fileID=default-test-file.txt, allFileIDs=<null>], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, checksumRequestForExistingFile=<null>, resultAddress=file:../bitrepository-core/src/test/resources/test-files//TEST-CHECKSUM-DELIVERY.xml-Pillar2]
      Test starting: getChecksumsFromOtherCollection
        Description: Tests the getChecksums client will correctly try to get from a second collection if required
        Added fixture: Configure collection1 to contain both pillars and collection 2 to only contain pillar2
        Step: Request the putting of a file through the PutClient for collection2
          Stimuli: Calling getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@38fdbc9, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@31adc338[correlationID=1662c196-57f5-4656-a6d3-20d73fbbf247, collectionID=SinglePillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=getChecksumsFromOtherCollection, to=Pillar2, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@6694bf01[fileID=<null>, allFileIDs=true], checksumRequestForExistingFile=<null>]
          Result: Received event: 1662c196: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums
        Step: Send an identification response from pillar2.
          Result: Received event: 1662c196: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar2
          Result: Received event: 1662c196: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
          Result: Received event: 1662c196: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar2], Sending GetFileIDsRequest's
          Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@7acff702[correlationID=1662c196-57f5-4656-a6d3-20d73fbbf247, collectionID=SinglePillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=getChecksumsFromOtherCollection, to=Pillar2, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@25245f60[fileID=<null>, allFileIDs=true], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, checksumRequestForExistingFile=<null>, resultAddress=<null>]
        Step: Send a complete event from the pillar
          Result: Received event: 1662c196: GET_CHECKSUMS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false
          Result: Received event: 1662c196: GET_CHECKSUMS: COMPLETE: 
      Test success: getChecksumsFromOtherCollection
      Test starting: getChecksumsFromSinglePillar
        Description: Tests that the client can retrieve checksums from a single pillar.
        Step: Request the delivery of the checksum of a file from pillar1.
          Stimuli: Calling getChecksums([ContributorQuery{componentID='Pillar1, minTimestamp=null, maxTimestamp=null, maxNumberOfResults=null}], default-test-file.txt, org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1da450f3[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], null, org.bitrepository.client.TestEventHandler@409e8809, TEST-AUDIT)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@6691e468[correlationID=ab654847-a0b8-44c9-a808-3c6e33b3874e, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=getChecksumsFromSinglePillar, to=Pillar1, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@2e0f3405[fileID=default-test-file.txt, allFileIDs=<null>], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1da450f3[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>]]
          Result: Received event: ab654847: GET_CHECKSUMS for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums
        Step: Sends a response from pillar2.
        Step: Sends a response from pillar1.
          Result: Received event: ab654847: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: ab654847: GET_CHECKSUMS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: ab654847: GET_CHECKSUMS for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending GetFileIDsRequest's
          Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@2579d604[correlationID=ab654847-a0b8-44c9-a808-3c6e33b3874e, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=getChecksumsFromSinglePillar, to=Pillar1, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@4ca2c467[fileID=default-test-file.txt, allFileIDs=<null>], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1da450f3[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], resultAddress=<null>]
        Step: Send a GetChecksumsFinalResponse to the client from pillar1
          Result: Received event: ab654847: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, NumberOfChecksums=0, PartialResult=false
          Result: Received event: ab654847: GET_CHECKSUMS for file default-test-file.txt: COMPLETE: 
      Test success: getChecksumsFromSinglePillar
      Test starting: testNoSuchFile
        Description: Testing how a request for a non-existing file is handled.
        Step: Setting up variables and such.
        Step: Request the delivery of the checksum of a file from the pillar(s). A callback listener should be supplied.
          Stimuli: Calling getChecksums(null, default-test-file.txt, null, null, org.bitrepository.client.TestEventHandler@466eddc6, TEST-AUDIT)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@6ee60495[correlationID=71a0bf56-0882-4acd-a966-40a08129f3b3, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=testNoSuchFile, to=Pillar1, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@650c9a94[fileID=default-test-file.txt, allFileIDs=<null>], checksumRequestForExistingFile=<null>]
          Result: Received event: 71a0bf56: GET_CHECKSUMS for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums
        Step: The pillar sends a response to the identify message.
          Result: Received event: 71a0bf56: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 71a0bf56: GET_CHECKSUMS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: 71a0bf56: GET_CHECKSUMS for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending GetFileIDsRequest's
          Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@2bae60e8[correlationID=71a0bf56-0882-4acd-a966-40a08129f3b3, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=testNoSuchFile, to=Pillar1, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@75321ba4[fileID=default-test-file.txt, allFileIDs=<null>], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, checksumRequestForExistingFile=<null>, resultAddress=<null>]
        Step: Send a error that the file cannot be found.
          Result: Received event: 71a0bf56: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FILE_NOT_FOUND_FAILURE, No such file.
          Result: Received event: 71a0bf56: GET_CHECKSUMS for file default-test-file.txt: FAILED: , Failed operation. Cause(s):
[71a0bf56: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FILE_NOT_FOUND_FAILURE, No such file.]
      Test success: testNoSuchFile
      Test starting: testPaging
        Description: Tests the GetChecksums client correctly handles functionality for limiting results, either by timestamp or result count.
        Step: Request checksums from with MinTimestamp, MaxTimestamp, MaxNumberOfResults set for both pillars .
          Stimuli: Calling getChecksums([ContributorQuery{componentID='Pillar1, minTimestamp=Fri Nov 20 02:19:05 CET 2015, maxTimestamp=Fri Nov 20 02:19:06 CET 2015, maxNumberOfResults=1}, ContributorQuery{componentID='Pillar2, minTimestamp=Fri Nov 20 02:19:06 CET 2015, maxTimestamp=Fri Nov 20 02:19:06 CET 2015, maxNumberOfResults=2}], null, null, null, org.bitrepository.client.TestEventHandler@37f37699, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@352f9163[correlationID=bdd2cfca-c42e-42bf-a391-9963d4b0e9dd, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=testPaging, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@22be4867[fileID=<null>, allFileIDs=true], checksumRequestForExistingFile=<null>]
          Result: Received event: bdd2cfca: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums
        Step: Send a IdentifyPillarsForGetChecksumsResponse from both pillars.
          Result: Received event: bdd2cfca: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: bdd2cfca: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar2
          Result: Received event: bdd2cfca: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2, Pillar1]
          Result: Received event: bdd2cfca: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending GetFileIDsRequest's
          Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@2e2da422[correlationID=bdd2cfca-c42e-42bf-a391-9963d4b0e9dd, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=testPaging, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@7e003cf0[fileID=<null>, allFileIDs=true], minTimestamp=2015-11-20T02:19:05.836+01:00, maxTimestamp=2015-11-20T02:19:06.736+01:00, maxNumberOfResults=1, checksumRequestForExistingFile=<null>, resultAddress=<null>]
          Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@6e3d6d79[correlationID=bdd2cfca-c42e-42bf-a391-9963d4b0e9dd, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=testPaging, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@db70c9b[fileID=<null>, allFileIDs=true], minTimestamp=2015-11-20T02:19:06.736+01:00, maxTimestamp=2015-11-20T02:19:06.836+01:00, maxNumberOfResults=2, checksumRequestForExistingFile=<null>, resultAddress=<null>]
      Test success: testPaging
      Test starting: verifyGetChecksumsClientFromFactory
      Test success: verifyGetChecksumsClientFromFactory
    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@7c6f306b[correlationID=5ed995e7-9cdb-4e0d-bf4a-a16e44933939, 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: 5ed995e7: 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: 5ed995e7: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID THE-AVERAGE-PILLAR
          Result: Received event: 5ed995e7: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID THE-FAST-PILLAR
          Result: Received event: 5ed995e7: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID THE-SLOW-PILLAR
          Result: Received event: 5ed995e7: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [THE-FAST-PILLAR]
          Result: Received event: 5ed995e7: 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@4eb7ff99[correlationID=5ed995e7-9cdb-4e0d-bf4a-a16e44933939, 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@38dab7df[correlationID=9c1ce227-83dd-4023-a782-3ef0cecb1e95, 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: 9c1ce227: 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: 9c1ce227: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 9c1ce227: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: 9c1ce227: 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@1722bd4e[correlationID=9c1ce227-83dd-4023-a782-3ef0cecb1e95, 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:08.410 WARN  o.b.c.c.m.CollectionBasedConversationMediator - Failing timed out conversation 9c1ce227-83dd-4023-a782-3ef0cecb1e95 (Age 1001ms)
          Result: Received event: 9c1ce227: GET_FILE for file default-test-file.txt: FAILED: , Failing timed out conversation 9c1ce227-83dd-4023-a782-3ef0cecb1e95
      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@13e4b8da[correlationID=e67c698c-8ffb-4340-8c15-45c6065094d9, 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: e67c698c: 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: e67c698c: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: e67c698c: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
          Result: Received event: e67c698c: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: e67c698c: 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@3217fef1[correlationID=e67c698c-8ffb-4340-8c15-45c6065094d9, 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: e67c698c: GET_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE
          Result: Received event: e67c698c: GET_FILE for file default-test-file.txt: FAILED: , Failed to get file from Pillar1, org.bitrepository.bitrepositoryelements.ResponseInfo@28aedf6e[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@687328fc[correlationID=5a664854-dfdd-469c-9052-7a8ca18a418e, 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: 5a664854: 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: 5a664854: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
          Result: Received event: 5a664854: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
          Result: Received event: 5a664854: 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@490f1d58[correlationID=5a664854-dfdd-469c-9052-7a8ca18a418e, 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: 5a664854: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2
          Result: Received event: 5a664854: 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@626f0377[correlationID=b445892d-bf9e-4664-8838-19e858f9839b, 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: b445892d: 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: b445892d: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
        Step: Wait 1 second.
          Result: Received event: b445892d: 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: b445892d: GET_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
          Result: Received event: b445892d: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: b445892d: 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@1042e13e[correlationID=b445892d-bf9e-4664-8838-19e858f9839b, 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: b445892d: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1
          Result: Received event: b445892d: 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@4fbd42bb[correlationID=b9f68da7-dc0a-4e8e-ae7b-e58cbefaa554, 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: b9f68da7: 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: b9f68da7: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
          Result: Received event: b9f68da7: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
          Result: Received event: b9f68da7: 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@5d1f9d8b[correlationID=b9f68da7-dc0a-4e8e-ae7b-e58cbefaa554, 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: b9f68da7: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2
          Result: Received event: b9f68da7: 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@6bc0b35c[correlationID=57467059-0b96-4c30-b11a-0bba901a7d17, 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: 57467059: 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: 57467059: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
          Result: Received event: 57467059: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
          Result: Received event: 57467059: 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@61bd6c16[correlationID=57467059-0b96-4c30-b11a-0bba901a7d17, 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: 57467059: GET_FILE for file default-test-file.txt: PROGRESS: ContributorID Pillar2, First test progress response message
        Step: Send a GetFileFinalResponse.
          Result: Received event: 57467059: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2
          Result: Received event: 57467059: 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@179f2542[correlationID=a46dbeeb-db6c-4507-a614-2aae533d4fc4, 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: a46dbeeb: 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: a46dbeeb: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: a46dbeeb: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: a46dbeeb: 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@c63a15f[correlationID=a46dbeeb-db6c-4507-a614-2aae533d4fc4, 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@1f49b38a[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: a46dbeeb: 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: a46dbeeb: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1
          Result: Received event: a46dbeeb: 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@10130823[correlationID=1e647a7e-e373-4cac-bf3a-5905f4803804, 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: 1e647a7e: GET_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetFile
        Step: Wait for 1 seconds
          Result: Received event: 1e647a7e: 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: 1e647a7e: GET_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor
          Result: Received event: 1e647a7e: GET_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
          Result: Received event: 1e647a7e: 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@798c002f[correlationID=ee48a5ab-d492-4f85-96f4-1e78404afe2c, 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: ee48a5ab: 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: ee48a5ab: 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: ee48a5ab: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
          Result: Received event: ee48a5ab: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
          Result: Received event: ee48a5ab: 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@62c6f4c6[correlationID=ee48a5ab-d492-4f85-96f4-1e78404afe2c, 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: ee48a5ab: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2
          Result: Received event: ee48a5ab: 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@2ea3ed9f[correlationID=81888456-9837-402c-9914-d0014a6e7910, 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: 81888456: 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: 81888456: 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: 81888456: 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: 81888456: 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@3ea9fd6c[correlationID=a89110df-63f6-4522-ad96-27bfc2746307, 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: a89110df: 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: a89110df: 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: a89110df: 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 UnexpectedResponseExceptionTest
      Test starting: testUnexpectedResponse
        Description: Test the instantiation of the exception
        Step: Setup
        Step: Try to throw such an exception
        Step: Throw the exception with an embedded exception
      Test success: testUnexpectedResponse
    Starting testcase AuditTrailClientComponentTest
      Test starting: getAllAuditTrailsTest
        Description: Tests the simplest case of getting all audit trail event for all contributers.
        Step: Create a AuditTrailClient.
        Step: Retrieve all audit trails from the collection by calling with a null componentQueries array
          Stimuli: Calling getAuditTrails(null, default-test-file.txt, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@e5b24e9[correlationID=e7564aed-4501-481d-a0d7-207b19dbe4b6, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=getAllAuditTrailsTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
          Result: Received event: e7564aed: GET_AUDIT_TRAILS for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
        Step: Send a identifyResponse from each pillar
          Result: Received event: e7564aed: GET_AUDIT_TRAILS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: e7564aed: GET_AUDIT_TRAILS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
          Result: Received event: e7564aed: GET_AUDIT_TRAILS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2]
          Result: Received event: e7564aed: GET_AUDIT_TRAILS for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for audit trails
          Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@44c3a4c2[correlationID=e7564aed-4501-481d-a0d7-207b19dbe4b6, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=getAllAuditTrailsTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar1, fileID=default-test-file.txt, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
          Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@54904fe2[correlationID=e7564aed-4501-481d-a0d7-207b19dbe4b6, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=getAllAuditTrailsTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar2, fileID=default-test-file.txt, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
        Step: Send a final response from pillar 1
          Result: Received event: e7564aed: GET_AUDIT_TRAILS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, NumberOfAuditTrailEvents=2, PartialResult=false
        Step: Send a final response from pillar 2
          Result: Received event: e7564aed: GET_AUDIT_TRAILS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2, NumberOfAuditTrailEvents=2, PartialResult=false
          Result: Received event: e7564aed: GET_AUDIT_TRAILS for file default-test-file.txt: COMPLETE: 
      Test success: getAllAuditTrailsTest
      Test starting: getSomeAuditTrailsTest
        Description: Tests the client maps a AuditTrail query correctly to a GetAuditTrail request.
        Step: Request audit trails from pillar 1 with both min and max sequence number set.
          Stimuli: Calling getAuditTrails([AuditTrailQuery{componentID='Pillar1, minTimestamp=null, maxTimestamp=null, maxNumberOfResults=10000}minSequenceNumber=1, maxSequenceNumber=3}], null, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@5a19393[correlationID=d65b6769-08b2-4e0e-a774-5487e1d04b93, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=getSomeAuditTrailsTest, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>]
          Result: Received event: d65b6769: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
        Step: Send a identifyResponse from pillar1
          Result: Received event: d65b6769: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: d65b6769: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: d65b6769: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1], Sending request for audit trails
          Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@54139c70[correlationID=d65b6769-08b2-4e0e-a774-5487e1d04b93, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=getSomeAuditTrailsTest, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar1, fileID=<null>, minSequenceNumber=1, maxSequenceNumber=3, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=10000, resultAddress=<null>]
        Step: Verify no request is sent to pillar2
        Step: Send a final response from pillar 1
          Result: Received event: d65b6769: GET_AUDIT_TRAILS: COMPONENT_COMPLETE: ContributorID Pillar1, NumberOfAuditTrailEvents=2, PartialResult=false
          Result: Received event: d65b6769: GET_AUDIT_TRAILS: COMPLETE: 
      Test success: getSomeAuditTrailsTest
      Test starting: incompleteSetOfFinalResponsesTest
        Description: Verify that the GetAuditTrail client works correct without receiving responses from all contributers.
        Step: Configure 500 ms second timeout for the operation itself. The default 2 contributers collection is used
          Stimuli: Calling getAuditTrails(null, null, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@54435e36[correlationID=2b28bf05-9afa-44f6-a524-f9e8abbe5fc2, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=incompleteSetOfFinalResponsesTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
          Result: Received event: 2b28bf05: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
        Step: Send a identifyResponse from each of the two pillars
          Result: Received event: 2b28bf05: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 2b28bf05: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2
          Result: Received event: 2b28bf05: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2]
          Result: Received event: 2b28bf05: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for audit trails
          Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@22939384[correlationID=2b28bf05-9afa-44f6-a524-f9e8abbe5fc2, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=incompleteSetOfFinalResponsesTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar1, fileID=<null>, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
          Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@6c6fdb0e[correlationID=2b28bf05-9afa-44f6-a524-f9e8abbe5fc2, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=incompleteSetOfFinalResponsesTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar2, fileID=<null>, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
      Test success: incompleteSetOfFinalResponsesTest
          Result: The following messages haven't been handled by the testcase: 
org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@6c6fdb0e[correlationID=2b28bf05-9afa-44f6-a524-f9e8abbe5fc2, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=incompleteSetOfFinalResponsesTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar2, fileID=<null>, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
02:19:13.597 WARN  o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: 
org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@6c6fdb0e[correlationID=2b28bf05-9afa-44f6-a524-f9e8abbe5fc2, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=incompleteSetOfFinalResponsesTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar2, fileID=<null>, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
      Test starting: negativeGetAuditTrailsResponseTest
        Description: Verify that the GetAuditTrail client works correct when receiving a negative GetAuditTrails response from one contributers.
        Step: Create a AuditTrailClient.
        Step: Retrieve all audit trails from the collection by calling with a null componentQueries array
          Stimuli: Calling getAuditTrails(null, null, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@776d13af[correlationID=37812058-5db4-4ce1-9033-5f7603125fa4, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=negativeGetAuditTrailsResponseTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
          Result: Received event: 37812058: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
        Step: Send a identifyResponse from each of the two pillars
          Result: Received event: 37812058: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 37812058: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2
          Result: Received event: 37812058: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2]
          Result: Received event: 37812058: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for audit trails
          Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@d7f170c[correlationID=37812058-5db4-4ce1-9033-5f7603125fa4, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=negativeGetAuditTrailsResponseTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar1, fileID=<null>, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
          Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@12909d67[correlationID=37812058-5db4-4ce1-9033-5f7603125fa4, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=negativeGetAuditTrailsResponseTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar2, fileID=<null>, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
        Step: Send a failed response from pillar 1
          Result: Received event: 37812058: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE, GetAuditTrails failed
        Step: Send a final response from pillar 2
          Result: Received event: 37812058: GET_AUDIT_TRAILS: COMPONENT_COMPLETE: ContributorID Pillar2, NumberOfAuditTrailEvents=2, PartialResult=false
          Result: Received event: 37812058: GET_AUDIT_TRAILS: FAILED: , Failed operation. Cause(s):
[37812058: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE, GetAuditTrails failed]
      Test success: negativeGetAuditTrailsResponseTest
      Test starting: noFinalResponsesTest
        Description: Tests the the AuditTrailClient handles lack of Final Responses gracefully  
        Step: Set a 100 ms timeout for the operation.
        Step: Make the client ask for all audit trails.
          Stimuli: Calling getAuditTrails(null, null, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@6fe4223b[correlationID=3b344595-8fdc-47a3-896f-c1bf495cd436, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noFinalResponsesTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
          Result: Received event: 3b344595: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
        Step: Send a identifyResponse from each of the two pillars
          Result: Received event: 3b344595: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 3b344595: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2
          Result: Received event: 3b344595: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2]
          Result: Received event: 3b344595: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for audit trails
          Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@42985696[correlationID=3b344595-8fdc-47a3-896f-c1bf495cd436, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noFinalResponsesTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar1, fileID=<null>, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
          Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@ca35104[correlationID=3b344595-8fdc-47a3-896f-c1bf495cd436, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noFinalResponsesTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar2, fileID=<null>, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
        Step: Wait for 1 second
          Result: Received event: 3b344595: GET_AUDIT_TRAILS: FAILED: , Failed to receive responses from all contributors before timeout(100ms). Missing contributors [Pillar1, Pillar2]
      Test success: noFinalResponsesTest
          Result: The following messages haven't been handled by the testcase: 
org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@42985696[correlationID=3b344595-8fdc-47a3-896f-c1bf495cd436, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noFinalResponsesTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar1, fileID=<null>, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
02:19:14.034 WARN  o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: 
org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@42985696[correlationID=3b344595-8fdc-47a3-896f-c1bf495cd436, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noFinalResponsesTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar1, fileID=<null>, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
          Result: The following messages haven't been handled by the testcase: 
org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@ca35104[correlationID=3b344595-8fdc-47a3-896f-c1bf495cd436, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noFinalResponsesTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar2, fileID=<null>, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
02:19:14.035 WARN  o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: 
org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@ca35104[correlationID=3b344595-8fdc-47a3-896f-c1bf495cd436, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noFinalResponsesTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar2, fileID=<null>, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
          Result: Received event: 2b28bf05: GET_AUDIT_TRAILS: FAILED: , Failed to receive responses from all contributors before timeout(500ms). Missing contributors [Pillar1, Pillar2]
      Test starting: progressEventsTest
        Description: Tests that progress events are handled correctly.
        Step: Create a AuditTrailClient.
        Step: Retrieve all audit trails from the collection by calling with a null componentQueries array
          Stimuli: Calling getAuditTrails(null, null, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@5a44b349[correlationID=35553f19-ecab-4b18-87ba-299d111ba811, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=progressEventsTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
          Result: Received event: 35553f19: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
        Step: Send a identifyResponse from each of the two pillars
          Result: Received event: 35553f19: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 35553f19: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2
          Result: Received event: 35553f19: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2]
          Result: Received event: 35553f19: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for audit trails
          Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@4220fef7[correlationID=35553f19-ecab-4b18-87ba-299d111ba811, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=progressEventsTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar1, fileID=<null>, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
          Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@3d01c301[correlationID=35553f19-ecab-4b18-87ba-299d111ba811, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=progressEventsTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar2, fileID=<null>, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
        Step: Send a progress accepted response from pillar 1
          Result: Received event: 35553f19: GET_AUDIT_TRAILS: PROGRESS: ContributorID Pillar1, GetAuditTrails request accepted
        Step: Send a general progress response from pillar 2
          Result: Received event: 35553f19: GET_AUDIT_TRAILS: PROGRESS: ContributorID Pillar2, Still progressing
      Test success: progressEventsTest
      Test starting: verifyAuditTrailClientFromFactory
      Test success: verifyAuditTrailClientFromFactory
      Test starting: collectionIDIncludedInEventsTest
        Description: Tests the the client provides collectionID in events.
        Step: Set a 0.5 second operation timeout.
        Step: Start the operation
          Stimuli: Calling getAuditTrails(null, null, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@2b5509e2[correlationID=fdcd57a2-1ceb-48a8-9f0d-fa8775d2e46f, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=collectionIDIncludedInEventsTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
          Result: Received event: fdcd57a2: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
        Step: Send positive responses from the pillar1 and a negative response from pillar2
          Result: Received event: fdcd57a2: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: fdcd57a2: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE
          Result: Received event: fdcd57a2: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: fdcd57a2: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1], Sending request for audit trails
          Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@4910f85c[correlationID=fdcd57a2-1ceb-48a8-9f0d-fa8775d2e46f, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=collectionIDIncludedInEventsTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar1, fileID=<null>, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
        Step: Wait for 1 second
          Result: Received event: fdcd57a2: GET_AUDIT_TRAILS: FAILED: , Failed to receive responses from all contributors before timeout(500ms). Missing contributors [Pillar1]
      Test success: collectionIDIncludedInEventsTest
      Test starting: conversationTimeoutTest
        Description: Tests the the client handles lack of IdentifyPillarResponses gracefully  
        Step: Set a 100 ms ConversationTimeout.
        Step: Start the operation
          Stimuli: Calling getAuditTrails(null, null, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@5bf3e120[correlationID=5684f914-ddea-4c26-9a7f-0664b8703bc6, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=conversationTimeoutTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
          Result: Received event: 5684f914: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
02:19:16.083 WARN  o.b.c.c.m.CollectionBasedConversationMediator - Failing timed out conversation 5684f914-ddea-4c26-9a7f-0664b8703bc6 (Age 1007ms)
          Result: Received event: 5684f914: GET_AUDIT_TRAILS: FAILED: , Failing timed out conversation 5684f914-ddea-4c26-9a7f-0664b8703bc6
      Test success: conversationTimeoutTest
      Test starting: identificationFailureTest
        Description: Verify that the client works correctly when a contributor sends a failure response.
        Step: Start the operation.
          Stimuli: Calling getAuditTrails(null, null, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@46a2760a[correlationID=f63523c3-21b3-406b-ae43-be15e1a3472d, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=identificationFailureTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
          Result: Received event: f63523c3: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
        Step: Send a identification response from contributor1 with a FAILURE response code.
          Result: Received event: f63523c3: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE
        Step: Send a identification response from contributor2 with a IDENTIFICATION_POSITIVE response code .
          Result: Received event: f63523c3: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2
          Result: Received event: f63523c3: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
          Result: Received event: f63523c3: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar2], Sending request for audit trails
          Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@65b1321f[correlationID=f63523c3-21b3-406b-ae43-be15e1a3472d, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=identificationFailureTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar2, fileID=<null>, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
        Step: Verify that the client continues to the performing phase.
        Step: Send a final response message from contributor2
          Result: Received event: f63523c3: GET_AUDIT_TRAILS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false
          Result: Received event: f63523c3: GET_AUDIT_TRAILS: FAILED: , Failed operation. Cause(s):
[f63523c3: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE]
      Test success: identificationFailureTest
      Test starting: identificationNegativeTest
        Description: Verify that the client works correctly when a contributor sends a negative response.
        Step: Start the operation.
          Stimuli: Calling getAuditTrails(null, null, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@5d98a66e[correlationID=74663dac-1aee-4150-b120-c849b5cba7f3, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=identificationNegativeTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
          Result: Received event: 74663dac: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
        Step: Send a identification response from contributor1 with a IDENTIFICATION_NEGATIVE response code .
          Result: Received event: 74663dac: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: IDENTIFICATION_NEGATIVE
        Step: Send a identification response from contributor2 with a IDENTIFICATION_POSITIVE response code .
          Result: Received event: 74663dac: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2
          Result: Received event: 74663dac: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
          Result: Received event: 74663dac: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar2], Sending request for audit trails
          Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@d304447[correlationID=74663dac-1aee-4150-b120-c849b5cba7f3, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=identificationNegativeTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar2, fileID=<null>, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
        Step: Verify that the client continues to the performing phase.
        Step: Send a final response message from contributor2
          Result: Received event: 74663dac: GET_AUDIT_TRAILS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false
          Result: Received event: 74663dac: GET_AUDIT_TRAILS: FAILED: , Failed operation. Cause(s):
[74663dac: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: IDENTIFICATION_NEGATIVE]
      Test success: identificationNegativeTest
      Test starting: noContributorsRespondingTest
        Description: Tests the the client handles lack of a IdentifyResponse gracefully. More concrete this means that the occurrence of a identification timeout should be handled correctly
        Step: Set a 100 ms timeout for identifying contributors.
        Step: Start the operation.
          Stimuli: Calling getAuditTrails(null, null, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@4d237ca5[correlationID=a842d8b0-e2e7-4ff1-aa0c-ebc0dfe0c4a2, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noContributorsRespondingTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
          Result: Received event: a842d8b0: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
        Step: Wait for 1 second
          Result: Received event: a842d8b0: GET_AUDIT_TRAILS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar1, Pillar2]
          Result: Received event: a842d8b0: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor
          Result: Received event: a842d8b0: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
          Result: Received event: a842d8b0: GET_AUDIT_TRAILS: FAILED: , Unable to continue operation, contributors unavailable.
      Test success: noContributorsRespondingTest
          Result: The following messages haven't been handled by the testcase: 
org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@4d237ca5[correlationID=a842d8b0-e2e7-4ff1-aa0c-ebc0dfe0c4a2, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noContributorsRespondingTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
02:19:18.548 WARN  o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: 
org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@4d237ca5[correlationID=a842d8b0-e2e7-4ff1-aa0c-ebc0dfe0c4a2, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noContributorsRespondingTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
      Test starting: oneContributorNotRespondingTest
        Description: Verify that the client works correct without receiving identification responses from all contributors.
        Added fixture: Set the a identification timeout to 100 ms.
        Step: Start the operation.
          Stimuli: Calling getAuditTrails(null, null, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@21a77782[correlationID=aee36168-3949-438e-bf18-179518d19e07, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=oneContributorNotRespondingTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
          Result: Received event: aee36168: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
        Step: Send a identification response from contributor1.
          Result: Received event: aee36168: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1
        Step: Wait 1 second.
          Result: Received event: aee36168: GET_AUDIT_TRAILS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar2]
          Result: Received event: aee36168: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
          Result: Received event: aee36168: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: aee36168: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1], Sending request for audit trails
          Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@77c1ee02[correlationID=aee36168-3949-438e-bf18-179518d19e07, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=oneContributorNotRespondingTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar1, fileID=<null>, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
        Step: Verify that the client continues to the performing phase.
        Step: Send a final response upload message
          Result: Received event: aee36168: GET_AUDIT_TRAILS: COMPONENT_COMPLETE: ContributorID Pillar1, PartialResult=false
          Result: Received event: aee36168: GET_AUDIT_TRAILS: FAILED: , Failed operation. Cause(s):
[aee36168: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor]
      Test success: oneContributorNotRespondingTest
      Test starting: operationTimeoutTest
        Description: Tests the the client handles lack of final responses gracefully.
        Step: Set a 100 ms operation timeout.
        Step: Start the operation
          Stimuli: Calling getAuditTrails(null, null, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@657e0d21[correlationID=1fd339d6-17c3-4206-bc13-cba5375113c1, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=operationTimeoutTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
          Result: Received event: 1fd339d6: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
        Step: Send positive responses from the pillar1 and a negative response from pillar2
          Result: Received event: 1fd339d6: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 1fd339d6: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE
          Result: Received event: 1fd339d6: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: 1fd339d6: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1], Sending request for audit trails
          Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@56b4cb4d[correlationID=1fd339d6-17c3-4206-bc13-cba5375113c1, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=operationTimeoutTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar1, fileID=<null>, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
        Step: Wait for 1 second
          Result: Received event: 1fd339d6: GET_AUDIT_TRAILS: FAILED: , Failed to receive responses from all contributors before timeout(100ms). Missing contributors [Pillar1]
      Test success: operationTimeoutTest
    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@27db378a[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@5c6d3fbd[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@546b4d6c[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], eventHandler, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@71c74406[correlationID=5f8e0721-97bd-4780-93e0-e6375ea25418, 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: 5f8e0721: 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: 5f8e0721: 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: 5f8e0721: DELETE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor
          Result: Received event: 5f8e0721: 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@3c1d9114[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7e29471f[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@f7e49b[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], eventHandler, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@28625f8[correlationID=6cfbaf76-8943-4130-b4c9-d8c92476fa9c, 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: 6cfbaf76: 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: 6cfbaf76: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 6cfbaf76: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: 6cfbaf76: 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@66e63575[correlationID=6cfbaf76-8943-4130-b4c9-d8c92476fa9c, 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@3c1d9114[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7e29471f[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@f7e49b[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: 6cfbaf76: 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@2d7345d0[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1a2f12a7[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-20T02:19:20.444+01:00], null, eventHandler, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@6f309e47[correlationID=98fdc2d3-dc01-40c2-97aa-e34cfc30e6bc, 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: 98fdc2d3: 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: 98fdc2d3: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 98fdc2d3: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: 98fdc2d3: 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@66db5a9a[correlationID=98fdc2d3-dc01-40c2-97aa-e34cfc30e6bc, 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@2d7345d0[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1a2f12a7[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-20T02:19:20.444+01:00], checksumRequestForExistingFile=<null>]
        Step: Send a final response message from pillar 1 to the DeleteClient.
          Result: Received event: 98fdc2d3: DELETE_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, DeleteFileResult=null
          Result: Received event: 98fdc2d3: 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@c9c114a[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2ef1df73[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@985b9f6[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], eventHandler, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@407691d1[correlationID=2ed99202-24bb-4f66-af2b-1aaab042595d, 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: 2ed99202: 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: 2ed99202: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 2ed99202: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: 2ed99202: 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@ca69671[correlationID=2ed99202-24bb-4f66-af2b-1aaab042595d, 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@c9c114a[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2ef1df73[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@985b9f6[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: 2ed99202: DELETE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE, Verifying that a failure can be understood!
          Result: Received event: 2ed99202: DELETE_FILE for file default-test-file.txt: FAILED: , Failed operation. Cause(s):
[2ed99202: 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@2f739d9a[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@41e484e3[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-20T02:19:21.705+01:00], null, eventHandler, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@253417d7[correlationID=97b57b35-f5c7-41e1-b65a-3af4961e1cb9, 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: 97b57b35: 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: 97b57b35: DELETE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: IDENTIFICATION_NEGATIVE
          Result: Received event: 97b57b35: 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@3d2f2bb8[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@223788ba[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@3b80ca33[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], eventHandler, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@7d4e4df4[correlationID=bed3ef54-2307-41cb-bb49-d1c4ce778d90, 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: bed3ef54: 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: bed3ef54: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: bed3ef54: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: bed3ef54: 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@2794e6d3[correlationID=bed3ef54-2307-41cb-bb49-d1c4ce778d90, 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@3d2f2bb8[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@223788ba[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@3b80ca33[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: bed3ef54: 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: bed3ef54: DELETE_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, DeleteFileResult=null
          Result: Received event: bed3ef54: 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@17e77934[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@43487352[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-20T02:19:21.967+01:00], null, eventHandler, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@3cc612eb[correlationID=bd9a5c0a-c93a-48d9-a78c-50bcd347102c, 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: bd9a5c0a: 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: bd9a5c0a: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: bd9a5c0a: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: bd9a5c0a: 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@6d1c20f[correlationID=bd9a5c0a-c93a-48d9-a78c-50bcd347102c, 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@17e77934[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@43487352[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-20T02:19:21.967+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@23c54fbb[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@250db31d[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-20T02:19:24.082+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@3b91ed0e[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], eventHandler, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@f3e3cb1[correlationID=174b79f9-f62c-4a33-9dc5-e1f79e378381, 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: 174b79f9: 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: 174b79f9: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 174b79f9: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: 174b79f9: 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@4ed2dced[correlationID=174b79f9-f62c-4a33-9dc5-e1f79e378381, 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@23c54fbb[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@250db31d[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-20T02:19:24.082+01:00], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@3b91ed0e[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@2cc788cc[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@4d52455[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-20T02:19:24.154+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@67103520[checksumType=MD5, checksumSalt={-86}, otherChecksumType=<null>], eventHandler, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@11359920[correlationID=6ac2b7c9-558e-4687-b3ca-2f7877830242, 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: 6ac2b7c9: 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: 6ac2b7c9: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 6ac2b7c9: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: 6ac2b7c9: 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@2cfe99df[correlationID=6ac2b7c9-558e-4687-b3ca-2f7877830242, 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@2cc788cc[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@4d52455[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-20T02:19:24.154+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@32671bda[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@172309cf[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-20T02:19:24.286+01:00], null, eventHandler, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@5ed7b9aa[correlationID=92ef922c-51ff-41f1-9bdf-e5815c9ca1a4, 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: 92ef922c: 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: 92ef922c: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 92ef922c: DELETE_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, DeleteFileResult=null
          Result: Received event: 92ef922c: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: []
          Result: Received event: 92ef922c: DELETE_FILE for file default-test-file.txt: COMPLETE: 
        Step: The client should then continue to the performing phase and finish immediately as the pillar has already had the file removed apparently .
        Step: Send a identify response from Pillar2
      Test success: fileAlreadyDeletedFromPillar
      Test starting: verifyDeleteClientFromFactory
        Description: Testing the initialization through the ModifyComponentFactory.
        Step: Use the ModifyComponentFactory to instantiate a PutFileClient.
      Test success: verifyDeleteClientFromFactory
    Starting testcase GetFileIDsCmdTest
      Test starting: defaultSuccessScenarioTest
        Description: Tests simplest arguments for running the CmdLineClient
      Test success: defaultSuccessScenarioTest
      Test starting: fileArgumentTest
        Description: Tests the argument for a specific file.
      Test success: fileArgumentTest
      Test starting: missingCollectionArgumentTest
        Description: Tests the scenario, where the collection arguments is missing.
Takes the following arguments:
-p [OPTIONAL] The id of the pillar where the should be performed. If undefined the operations is performed on all pillars.
-s The path to the directory with the settings files for the client
-c The id for the collection to perform the operation on.
-v Makes the client more verbose
-i The id for the file to perform the operation on.
-k The path to the file containing the private key.
Missing argument: c
      Test success: missingCollectionArgumentTest
      Test starting: specificPillarArgumentTest
        Description: Test argument for a specific pillar
      Test success: specificPillarArgumentTest
      Test starting: unknownPillarArgumentTest
        Description: Testing against a non-existing pillar id -> Should fail
Invalid argument: Random1447982366328pillar is not a valid pillar for collection TwoPillarCollection
The collection contains the following pillars: [Pillar1, Pillar2]
      Test success: unknownPillarArgumentTest
    Starting testcase ReplaceFileClientComponentTest
      Test starting: replaceClientIdentificationTimeout
        Description: Tests the handling of a failed identification for the ReplaceClient
        Step: Initialise the number of pillars and the DeleteClient. Sets the identification timeout to 100 ms.
        Step: Request a file to be replaced on the default pillar.
          Stimuli: replaceFile(default-test-file.txt, Pillar1, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@757a537a[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@234d74c4[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@61078f35[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, 10, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@73d6261d[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@234d74c4[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@61078f35[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], org.bitrepository.client.TestEventHandler@54905a9e, null
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileRequest@1cb3ef9c[correlationID=cd2ee3b0-ec8e-41e8-907d-642f2695cc87, 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: cd2ee3b0: 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: cd2ee3b0: 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: cd2ee3b0: REPLACE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor
          Result: Received event: cd2ee3b0: 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@31cbe718[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@71671b6b[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@689eaa6a[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, 10, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@183fb032[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@71671b6b[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@689eaa6a[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], org.bitrepository.client.TestEventHandler@7622670a, null
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileRequest@3f5786e6[correlationID=67a5bd8c-5497-4b83-8e2f-8ce87319cce9, 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: 67a5bd8c: 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: 67a5bd8c: REPLACE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 67a5bd8c: REPLACE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: 67a5bd8c: 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@475c3cce[correlationID=67a5bd8c-5497-4b83-8e2f-8ce87319cce9, 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@31cbe718[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@71671b6b[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@689eaa6a[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@183fb032[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@71671b6b[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@689eaa6a[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: 67a5bd8c: 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@10cd0338[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@17b779f9[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@737c5ebb[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, 0, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@21b7f7f[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@17b779f9[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@737c5ebb[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], org.bitrepository.client.TestEventHandler@7ab768c7, null
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileRequest@56e3aed9[correlationID=6893d4dc-ec8c-441f-857c-399683a53a21, 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: 6893d4dc: 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: 6893d4dc: REPLACE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 6893d4dc: REPLACE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: 6893d4dc: 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@1e42c42f[correlationID=6893d4dc-ec8c-441f-857c-399683a53a21, 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@10cd0338[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@17b779f9[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@737c5ebb[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@21b7f7f[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@17b779f9[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@737c5ebb[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: 6893d4dc: REPLACE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE, Verifying that a failure can be understood!
          Result: Received event: 6893d4dc: REPLACE_FILE for file default-test-file.txt: FAILED: , Failed operation. Cause(s):
[6893d4dc: 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@72f689bc[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@26af38f1[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@2a4e3b6a[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, 10, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@7a084d61[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@26af38f1[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@2a4e3b6a[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], org.bitrepository.client.TestEventHandler@3c7580f5, null
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileRequest@63c25f3a[correlationID=e381a75f-ed1a-4e8d-941c-49c7de53f0fd, 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: e381a75f: 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: e381a75f: REPLACE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: e381a75f: REPLACE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: e381a75f: 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@d78c66[correlationID=e381a75f-ed1a-4e8d-941c-49c7de53f0fd, 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@72f689bc[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@26af38f1[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@2a4e3b6a[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@7a084d61[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@26af38f1[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@2a4e3b6a[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: e381a75f: 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: e381a75f: REPLACE_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, checksum for new file: 'org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@7a084d61[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@26af38f1[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: e381a75f: 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@3ea07b0a[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7c2b4366[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@5fc7ae34[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7c2b4366[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@1a3d1ae7[checksumType=MD5, checksumSalt={-86}, otherChecksumType=<null>], org.bitrepository.client.TestEventHandler@27784a81, null
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileRequest@16e0d7b[correlationID=873ab814-c285-4913-98b5-bca79bb96cd5, 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: 873ab814: 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: 873ab814: REPLACE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 873ab814: REPLACE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: 873ab814: 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@112261ce[correlationID=873ab814-c285-4913-98b5-bca79bb96cd5, 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@3ea07b0a[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7c2b4366[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@5fc7ae34[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7c2b4366[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 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: Random1447982368597pillar 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
      Finished testcase
  Finished suite
Finished project
Tests run: 156, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 59.517 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