Console Output

Skipping 112 KB.. Full Log

quenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
        Step: Send a failed response from pillar 1
          Result: Received event: dc9f25df: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE, GetAuditTrails failed
        Step: Send a final response from pillar 2
          Result: Received event: dc9f25df: GET_AUDIT_TRAILS: COMPONENT_COMPLETE: ContributorID Pillar2, NumberOfAuditTrailEvents=2, PartialResult=false
          Result: Received event: dc9f25df: GET_AUDIT_TRAILS: FAILED: , Failed operation. Cause(s):
[dc9f25df: 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@58b4f4a[correlationID=9f009cfd-0226-4e0d-9971-8e0657c81ff7, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noFinalResponsesTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
          Result: Received event: 9f009cfd: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
        Step: Send a identifyResponse from each of the two pillars
          Result: Received event: 9f009cfd: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 9f009cfd: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2
          Result: Received event: 9f009cfd: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2, Pillar1]
          Result: Received event: 9f009cfd: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for audit trails
          Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@4325de9e[correlationID=9f009cfd-0226-4e0d-9971-8e0657c81ff7, 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@1c0b38af[correlationID=9f009cfd-0226-4e0d-9971-8e0657c81ff7, 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: 353e3ab8: GET_AUDIT_TRAILS: FAILED: , Failed to receive responses from all contributors before timeout(500ms). Missing contributors [Pillar1, Pillar2]
          Result: Received event: 9f009cfd: 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@4325de9e[correlationID=9f009cfd-0226-4e0d-9971-8e0657c81ff7, 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:39.643 WARN  o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: 
org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@4325de9e[correlationID=9f009cfd-0226-4e0d-9971-8e0657c81ff7, 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@1c0b38af[correlationID=9f009cfd-0226-4e0d-9971-8e0657c81ff7, 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:39.644 WARN  o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: 
org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@1c0b38af[correlationID=9f009cfd-0226-4e0d-9971-8e0657c81ff7, 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>]
      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@28e04625[correlationID=122163c5-8c69-4b6e-a31b-3f28e8197790, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=progressEventsTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
          Result: Received event: 122163c5: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
        Step: Send a identifyResponse from each of the two pillars
          Result: Received event: 122163c5: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 122163c5: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2
          Result: Received event: 122163c5: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2, Pillar1]
          Result: Received event: 122163c5: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for audit trails
          Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@8bbd0c7[correlationID=122163c5-8c69-4b6e-a31b-3f28e8197790, 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@22406e9b[correlationID=122163c5-8c69-4b6e-a31b-3f28e8197790, 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: 122163c5: GET_AUDIT_TRAILS: PROGRESS: ContributorID Pillar1, GetAuditTrails request accepted
        Step: Send a general progress response from pillar 2
          Result: Received event: 122163c5: 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@41758fc9[correlationID=d9b41ff7-4c4d-43d4-9521-09963f443852, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=collectionIDIncludedInEventsTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
          Result: Received event: d9b41ff7: 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: d9b41ff7: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: d9b41ff7: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE
          Result: Received event: d9b41ff7: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: d9b41ff7: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1], Sending request for audit trails
          Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@1e2b7fa5[correlationID=d9b41ff7-4c4d-43d4-9521-09963f443852, 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: d9b41ff7: 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@3265e21a[correlationID=4d18fa21-5532-437a-9fa9-4459ac867989, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=conversationTimeoutTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
          Result: Received event: 4d18fa21: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
02:19:41.540 WARN  o.b.c.c.m.CollectionBasedConversationMediator - Failing timed out conversation 4d18fa21-5532-437a-9fa9-4459ac867989 (Age 1018ms)
          Result: Received event: 4d18fa21: GET_AUDIT_TRAILS: FAILED: , Failing timed out conversation 4d18fa21-5532-437a-9fa9-4459ac867989
      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@50ed196f[correlationID=1fdf6501-4e96-4be1-9387-51e602b50939, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=identificationFailureTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
          Result: Received event: 1fdf6501: 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: 1fdf6501: 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: 1fdf6501: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2
          Result: Received event: 1fdf6501: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
          Result: Received event: 1fdf6501: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar2], Sending request for audit trails
          Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@45330a89[correlationID=1fdf6501-4e96-4be1-9387-51e602b50939, 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: 1fdf6501: GET_AUDIT_TRAILS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false
          Result: Received event: 1fdf6501: GET_AUDIT_TRAILS: FAILED: , Failed operation. Cause(s):
[1fdf6501: 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@131fa25c[correlationID=0ee04405-26bc-4202-a44e-471ab1e24a39, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=identificationNegativeTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
          Result: Received event: 0ee04405: 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: 0ee04405: 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: 0ee04405: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2
          Result: Received event: 0ee04405: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
          Result: Received event: 0ee04405: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar2], Sending request for audit trails
          Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@724e9296[correlationID=0ee04405-26bc-4202-a44e-471ab1e24a39, 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: 0ee04405: GET_AUDIT_TRAILS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false
          Result: Received event: 0ee04405: GET_AUDIT_TRAILS: FAILED: , Failed operation. Cause(s):
[0ee04405: 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@403acbdb[correlationID=fdd30908-2c50-4114-ae97-fbdf56b08efc, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noContributorsRespondingTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
          Result: Received event: fdd30908: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
        Step: Wait for 1 second
          Result: Received event: fdd30908: GET_AUDIT_TRAILS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar1, Pillar2]
          Result: Received event: fdd30908: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor
          Result: Received event: fdd30908: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
          Result: Received event: fdd30908: 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@403acbdb[correlationID=fdd30908-2c50-4114-ae97-fbdf56b08efc, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noContributorsRespondingTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
02:19:44.368 WARN  o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: 
org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@403acbdb[correlationID=fdd30908-2c50-4114-ae97-fbdf56b08efc, 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@7c99e5dd[correlationID=7cdb224e-0718-45a5-8345-d878774ed1a8, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=oneContributorNotRespondingTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
          Result: Received event: 7cdb224e: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
        Step: Send a identification response from contributor1.
          Result: Received event: 7cdb224e: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1
        Step: Wait 1 second.
          Result: Received event: 7cdb224e: GET_AUDIT_TRAILS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar2]
          Result: Received event: 7cdb224e: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
          Result: Received event: 7cdb224e: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: 7cdb224e: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1], Sending request for audit trails
          Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@24232fcc[correlationID=7cdb224e-0718-45a5-8345-d878774ed1a8, 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: 7cdb224e: GET_AUDIT_TRAILS: COMPONENT_COMPLETE: ContributorID Pillar1, PartialResult=false
          Result: Received event: 7cdb224e: GET_AUDIT_TRAILS: FAILED: , Failed operation. Cause(s):
[7cdb224e: 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@2e643cad[correlationID=e2a6b48d-654a-4f27-ac16-c28d7ceba3a4, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=operationTimeoutTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
          Result: Received event: e2a6b48d: 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: e2a6b48d: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: e2a6b48d: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE
          Result: Received event: e2a6b48d: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: e2a6b48d: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1], Sending request for audit trails
          Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@21c64b8e[correlationID=e2a6b48d-654a-4f27-ac16-c28d7ceba3a4, 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: e2a6b48d: GET_AUDIT_TRAILS: FAILED: , Failed to receive responses from all contributors before timeout(100ms). Missing contributors [Pillar1]
      Test success: operationTimeoutTest
    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: Random1444868387255pillar is not a valid pillar for collection TwoPillarCollection
The collection contains the following pillars: [Pillar1, Pillar2]
      Test success: unknownPillarArgumentTest
      Test starting: urlSuccessScenarioTest
        Description: Tests arguments for putting a file on a given URL
      Test success: urlSuccessScenarioTest
    Starting testcase AuditTrailQueryTest
      Test starting: testBothSequenceNumberFailure
        Description: Test the creation of a AuditTrailQuery with both SequenceNumber, where max is smalle than min.
      Test success: testBothSequenceNumberFailure
      Test starting: testBothSequenceNumberSuccess
        Description: Test the creation of a AuditTrailQuery with both SequenceNumber, where max is larger than min.
      Test success: testBothSequenceNumberSuccess
      Test starting: testNoSequenceNumbers
        Description: Test that a AuditTrailQuery can be created without any sequence numbers.
      Test success: testNoSequenceNumbers
      Test starting: testOnlyMinSequenceNumber
        Description: Test the creation of a AuditTrailQuery with only the minSequenceNumber
      Test success: testOnlyMinSequenceNumber
    Starting testcase DeleteFileCmdTest
      Test starting: checksumArgumentNonSaltAlgorithmWitoutSaltTest
        Description: Test MD5 checksum without salt -> no failure
      Test success: checksumArgumentNonSaltAlgorithmWitoutSaltTest
      Test starting: checksumArgumentSaltAlgorithmWithSaltTest
        Description: Test HMAC_SHA256 checksum with salt -> No failure
      Test success: checksumArgumentSaltAlgorithmWithSaltTest
      Test starting: defaultSuccessScenarioTest
        Description: Tests simplest arguments for running the CmdLineClient
      Test success: defaultSuccessScenarioTest
      Test starting: missingCollectionArgumentTest
        Description: Tests the scenario, where the collection arguments is missing.
Takes the following arguments:
-p [OPTIONAL] The id of the pillar where the should be performed. If undefined the operations is performed on all pillars.
-R [OPTIONAL] The algorithm of checksum to request in the response from the pillars.
-s The path to the directory with the settings files for the client
-c The id for the collection to perform the operation on.
-C [OPTIONAL] The checksum of the file to be delete.
-S [OPTIONAL] The salt of checksum to request in the response. Requires the ChecksumType argument.
-v Makes the client more verbose
-i The id for the file to perform the operation on.
-k The path to the file containing the private key.
Missing argument: c
      Test success: missingCollectionArgumentTest
      Test starting: missingFileIDArgumentTest
        Description: Tests the scenario, where no arguments for file id argument is given.
Takes the following arguments:
-p [OPTIONAL] The id of the pillar where the should be performed. If undefined the operations is performed on all pillars.
-R [OPTIONAL] The algorithm of checksum to request in the response from the pillars.
-s The path to the directory with the settings files for the client
-c The id for the collection to perform the operation on.
-C [OPTIONAL] The checksum of the file to be delete.
-S [OPTIONAL] The salt of checksum to request in the response. Requires the ChecksumType argument.
-v Makes the client more verbose
-i The id for the file to perform the operation on.
-k The path to the file containing the private key.
Missing argument: i
      Test success: missingFileIDArgumentTest
      Test starting: missingPillarArgumentTest
        Description: Tests the different scenarios, with the pillar argument.
Invalid argument: The pillar argument -p must defined for the delete operation, only single pillar deletes are allowed
      Test success: missingPillarArgumentTest
      Test starting: unknownPillarArgumentTest
        Step: Testing against a non-existing pillar id
Invalid argument: Random1444868388820pillar is not a valid pillar for collection TwoPillarCollection
The collection contains the following pillars: [Pillar1, Pillar2]
      Test success: unknownPillarArgumentTest
    Starting testcase GetChecksumsClientComponentTest
      Test starting: collectionIDIncludedInEventsTest
        Description: Tests the the client provides collectionID in events.
        Step: Set a 0.5 second operation timeout.
        Step: Start the operation
          Stimuli: Calling getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@68661b94, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@7b1a2d0a[correlationID=9bb9548f-be1a-4429-92bb-b3b74eede990, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=collectionIDIncludedInEventsTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@510fb2d8[fileID=<null>, allFileIDs=true], checksumRequestForExistingFile=<null>]
          Result: Received event: 9bb9548f: 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: 9bb9548f: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 9bb9548f: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE
          Result: Received event: 9bb9548f: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: 9bb9548f: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar1], Sending GetFileIDsRequest's
          Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@31288ffc[correlationID=9bb9548f-be1a-4429-92bb-b3b74eede990, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=collectionIDIncludedInEventsTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@1d9d6273[fileID=<null>, allFileIDs=true], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, checksumRequestForExistingFile=<null>, resultAddress=<null>]
        Step: Wait for 1 second
          Result: Received event: 9bb9548f: GET_CHECKSUMS: FAILED: , Failed to receive responses from all contributors before timeout(500ms). Missing contributors [Pillar1]
      Test success: collectionIDIncludedInEventsTest
      Test starting: conversationTimeoutTest
        Description: Tests the the client handles lack of IdentifyPillarResponses gracefully  
        Step: Set a 100 ms ConversationTimeout.
        Step: Start the operation
          Stimuli: Calling getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@68661b94, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@65162814[correlationID=35ded163-b69e-47e9-8c66-0fa60aa98694, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=conversationTimeoutTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@ba0b690[fileID=<null>, allFileIDs=true], checksumRequestForExistingFile=<null>]
          Result: Received event: 35ded163: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums
02:19:50.737 WARN  o.b.c.c.m.CollectionBasedConversationMediator - Failing timed out conversation 35ded163-b69e-47e9-8c66-0fa60aa98694 (Age 1014ms)
          Result: Received event: 35ded163: GET_CHECKSUMS: FAILED: , Failing timed out conversation 35ded163-b69e-47e9-8c66-0fa60aa98694
      Test success: conversationTimeoutTest
      Test starting: identificationFailureTest
        Description: Verify that the client works correctly when a contributor sends a failure response.
        Step: Start the operation.
          Stimuli: Calling getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@68661b94, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@14c428e9[correlationID=447174a2-eaba-4b49-8d05-ab39f1bac85e, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=identificationFailureTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@2be51f04[fileID=<null>, allFileIDs=true], checksumRequestForExistingFile=<null>]
          Result: Received event: 447174a2: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums
        Step: Send a identification response from contributor1 with a FAILURE response code.
          Result: Received event: 447174a2: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE
        Step: Send a identification response from contributor2 with a IDENTIFICATION_POSITIVE response code .
          Result: Received event: 447174a2: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar2
          Result: Received event: 447174a2: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
          Result: Received event: 447174a2: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar2], Sending GetFileIDsRequest's
          Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@37f3e60c[correlationID=447174a2-eaba-4b49-8d05-ab39f1bac85e, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=identificationFailureTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@2c5037b[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 message from contributor2
          Result: Received event: 447174a2: GET_CHECKSUMS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false
          Result: Received event: 447174a2: GET_CHECKSUMS: FAILED: , Failed operation. Cause(s):
[447174a2: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE]
      Test success: identificationFailureTest
      Test starting: identificationNegativeTest
        Description: Verify that the client works correctly when a contributor sends a negative response.
        Step: Start the operation.
          Stimuli: Calling getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@68661b94, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@4fe01994[correlationID=02d1b897-e898-4fe3-ae4f-7f7498404a30, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=identificationNegativeTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@c77bcb0[fileID=<null>, allFileIDs=true], checksumRequestForExistingFile=<null>]
          Result: Received event: 02d1b897: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums
        Step: Send a identification response from contributor1 with a IDENTIFICATION_NEGATIVE response code .
          Result: Received event: 02d1b897: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: IDENTIFICATION_NEGATIVE
        Step: Send a identification response from contributor2 with a IDENTIFICATION_POSITIVE response code .
          Result: Received event: 02d1b897: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar2
          Result: Received event: 02d1b897: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
          Result: Received event: 02d1b897: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar2], Sending GetFileIDsRequest's
          Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@5eb82ec9[correlationID=02d1b897-e898-4fe3-ae4f-7f7498404a30, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=identificationNegativeTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@115bb033[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 message from contributor2
          Result: Received event: 02d1b897: GET_CHECKSUMS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false
          Result: Received event: 02d1b897: GET_CHECKSUMS: FAILED: , Failed operation. Cause(s):
[02d1b897: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: IDENTIFICATION_NEGATIVE]
      Test success: identificationNegativeTest
      Test starting: noContributorsRespondingTest
        Description: Tests the the client handles lack of a IdentifyResponse gracefully. More concrete this means that the occurrence of a identification timeout should be handled correctly
        Step: Set a 100 ms timeout for identifying contributors.
        Step: Start the operation.
          Stimuli: Calling getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@68661b94, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@1127ec2d[correlationID=07e5d18a-a9b8-438e-9f26-b03f9455a732, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=noContributorsRespondingTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@61fee0d7[fileID=<null>, allFileIDs=true], checksumRequestForExistingFile=<null>]
          Result: Received event: 07e5d18a: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums
        Step: Wait for 1 second
          Result: Received event: 07e5d18a: GET_CHECKSUMS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar1, Pillar2]
          Result: Received event: 07e5d18a: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor
          Result: Received event: 07e5d18a: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
          Result: Received event: 07e5d18a: GET_CHECKSUMS: FAILED: , Unable to continue operation, contributors unavailable.
      Test success: noContributorsRespondingTest
          Result: The following messages haven't been handled by the testcase: 
org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@1127ec2d[correlationID=07e5d18a-a9b8-438e-9f26-b03f9455a732, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=noContributorsRespondingTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@61fee0d7[fileID=<null>, allFileIDs=true], checksumRequestForExistingFile=<null>]
02:19:53.818 WARN  o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: 
org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@1127ec2d[correlationID=07e5d18a-a9b8-438e-9f26-b03f9455a732, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=noContributorsRespondingTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@61fee0d7[fileID=<null>, allFileIDs=true], checksumRequestForExistingFile=<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 getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@68661b94, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@426a15b4[correlationID=76070213-be7f-40c5-bfeb-9a9a821e2799, 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@5d0a60f1[fileID=<null>, allFileIDs=true], checksumRequestForExistingFile=<null>]
          Result: Received event: 76070213: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums
        Step: Send a identification response from contributor1.
          Result: Received event: 76070213: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar1
        Step: Wait 1 second.
          Result: Received event: 76070213: GET_CHECKSUMS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar2]
          Result: Received event: 76070213: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
          Result: Received event: 76070213: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: 76070213: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar1], Sending GetFileIDsRequest's
          Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@4b07b838[correlationID=76070213-be7f-40c5-bfeb-9a9a821e2799, 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@5c794b5a[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: 76070213: GET_CHECKSUMS: COMPONENT_COMPLETE: ContributorID Pillar1, PartialResult=false
          Result: Received event: 76070213: GET_CHECKSUMS: FAILED: , Failed operation. Cause(s):
[76070213: 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@68661b94, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@6de7643c[correlationID=030773ac-fb4f-4cf3-a80b-c67c4b51fb5e, 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@787eb31b[fileID=<null>, allFileIDs=true], checksumRequestForExistingFile=<null>]
          Result: Received event: 030773ac: 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: 030773ac: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 030773ac: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE
          Result: Received event: 030773ac: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: 030773ac: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar1], Sending GetFileIDsRequest's
          Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@70178324[correlationID=030773ac-fb4f-4cf3-a80b-c67c4b51fb5e, 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@2607cf9e[fileID=<null>, allFileIDs=true], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, checksumRequestForExistingFile=<null>, resultAddress=<null>]
        Step: Wait for 1 second
          Result: Received event: 030773ac: GET_CHECKSUMS: FAILED: , Failed to receive responses from all contributors before timeout(100ms). Missing contributors [Pillar1]
      Test success: operationTimeoutTest
      Test starting: getChecksumsDeliveredAtUrl
        Description: Tests the delivery of checksums from all pillars at a given URL.
        Step: Ensure the delivery file isn't already present on the http server
        Step: Request the delivery of the checksum of a file from all pillars.
          Stimuli: Calling getChecksums(null, default-test-file.txt, null, file:../bitrepository-core/src/test/resources/test-files//TEST-CHECKSUM-DELIVERY.xml, org.bitrepository.client.TestEventHandler@433b9807, TEST-AUDIT)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@d9a9c76[correlationID=d38e2965-e301-4907-b909-cfdccb3fdafa, 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@44414bd4[fileID=default-test-file.txt, allFileIDs=<null>], checksumRequestForExistingFile=<null>]
          Result: Received event: d38e2965: 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: d38e2965: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: d38e2965: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
          Result: Received event: d38e2965: GET_CHECKSUMS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2, Pillar1]
          Result: Received event: d38e2965: 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@293c1612[correlationID=d38e2965-e301-4907-b909-cfdccb3fdafa, 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@67edf70a[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@48e25867[correlationID=d38e2965-e301-4907-b909-cfdccb3fdafa, 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@5a06a235[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: d38e2965: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, NumberOfChecksums=0, PartialResult=false
          Result: Received event: d38e2965: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2, NumberOfChecksums=0, PartialResult=false
          Result: Received event: d38e2965: 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@48e25867[correlationID=d38e2965-e301-4907-b909-cfdccb3fdafa, 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@5a06a235[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:54.447 WARN  o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: 
org.bitrepository.bitrepositorymessages.GetChecksumsRequest@48e25867[correlationID=d38e2965-e301-4907-b909-cfdccb3fdafa, 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@5a06a235[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@20fc59c2, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@34a05f9[correlationID=8de6fc37-e23a-4f8d-ab49-948a2959018d, 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@4c4add5e[fileID=<null>, allFileIDs=true], checksumRequestForExistingFile=<null>]
          Result: Received event: 8de6fc37: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums
        Step: Send an identification response from pillar2.
          Result: Received event: 8de6fc37: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar2
          Result: Received event: 8de6fc37: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
          Result: Received event: 8de6fc37: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar2], Sending GetFileIDsRequest's
          Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@27e8a588[correlationID=8de6fc37-e23a-4f8d-ab49-948a2959018d, 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@74de0941[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: 8de6fc37: GET_CHECKSUMS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false
          Result: Received event: 8de6fc37: 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@72b06c51[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], null, org.bitrepository.client.TestEventHandler@11861ce0, TEST-AUDIT)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@3efae691[correlationID=2cbf36f0-d5c1-46ec-9182-5eab022b4413, 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@3d85a2a0[fileID=default-test-file.txt, allFileIDs=<null>], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@72b06c51[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>]]
          Result: Received event: 2cbf36f0: 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: 2cbf36f0: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 2cbf36f0: GET_CHECKSUMS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: 2cbf36f0: 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@6de6f7cd[correlationID=2cbf36f0-d5c1-46ec-9182-5eab022b4413, 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@4415a8e[fileID=default-test-file.txt, allFileIDs=<null>], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@72b06c51[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], resultAddress=<null>]
        Step: Send a GetChecksumsFinalResponse to the client from pillar1
          Result: Received event: 2cbf36f0: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, NumberOfChecksums=0, PartialResult=false
          Result: Received event: 2cbf36f0: 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@780eaf3f, TEST-AUDIT)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@377b582b[correlationID=b6557f72-38e6-4116-b5d9-a4cc69ad44d2, 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@1c2b9948[fileID=default-test-file.txt, allFileIDs=<null>], checksumRequestForExistingFile=<null>]
          Result: Received event: b6557f72: 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: b6557f72: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: b6557f72: GET_CHECKSUMS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: b6557f72: 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@dfb8c98[correlationID=b6557f72-38e6-4116-b5d9-a4cc69ad44d2, 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@60ac370c[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: b6557f72: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FILE_NOT_FOUND_FAILURE, No such file.
          Result: Received event: b6557f72: GET_CHECKSUMS for file default-test-file.txt: FAILED: , Failed operation. Cause(s):
[b6557f72: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FILE_NOT_FOUND_FAILURE, No such file.]
      Test success: testNoSuchFile
      Test starting: testPaging
        Description: Tests the GetChecksums client correctly handles functionality for limiting results, either by timestamp or result count.
        Step: Request checksums from with MinTimestamp, MaxTimestamp, MaxNumberOfResults set for both pillars .
          Stimuli: Calling getChecksums([ContributorQuery{componentID='Pillar1, minTimestamp=Thu Oct 15 02:19:55 CEST 2015, maxTimestamp=Thu Oct 15 02:19:56 CEST 2015, maxNumberOfResults=1}, ContributorQuery{componentID='Pillar2, minTimestamp=Thu Oct 15 02:19:56 CEST 2015, maxTimestamp=Thu Oct 15 02:19:56 CEST 2015, maxNumberOfResults=2}], null, null, null, org.bitrepository.client.TestEventHandler@68661b94, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@3f643af6[correlationID=cd15737d-b26f-4e9f-9197-bac22b73485b, 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@1db5a911[fileID=<null>, allFileIDs=true], checksumRequestForExistingFile=<null>]
          Result: Received event: cd15737d: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums
        Step: Send a IdentifyPillarsForGetChecksumsResponse from both pillars.
          Result: Received event: cd15737d: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: cd15737d: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar2
          Result: Received event: cd15737d: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2]
          Result: Received event: cd15737d: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending GetFileIDsRequest's
          Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@5e209dae[correlationID=cd15737d-b26f-4e9f-9197-bac22b73485b, 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@6e6d5a5a[fileID=<null>, allFileIDs=true], minTimestamp=2015-10-15T02:19:55.321+02:00, maxTimestamp=2015-10-15T02:19:56.221+02:00, maxNumberOfResults=1, checksumRequestForExistingFile=<null>, resultAddress=<null>]
          Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@6310e808[correlationID=cd15737d-b26f-4e9f-9197-bac22b73485b, 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@4e56ab8d[fileID=<null>, allFileIDs=true], minTimestamp=2015-10-15T02:19:56.221+02:00, maxTimestamp=2015-10-15T02:19:56.321+02: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@64d0f697[correlationID=7a3f6a93-d885-4dcf-85e4-1cc46334db56, 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: 7a3f6a93: 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: 7a3f6a93: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID THE-AVERAGE-PILLAR
          Result: Received event: 7a3f6a93: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID THE-FAST-PILLAR
          Result: Received event: 7a3f6a93: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID THE-SLOW-PILLAR
          Result: Received event: 7a3f6a93: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [THE-FAST-PILLAR]
          Result: Received event: 7a3f6a93: 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@191e18d7[correlationID=7a3f6a93-d885-4dcf-85e4-1cc46334db56, 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@2da3ae4c[correlationID=642f1696-dcd5-418d-a211-8dd2d848b32d, 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: 642f1696: 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: 642f1696: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 642f1696: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: 642f1696: 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@2f2bb096[correlationID=642f1696-dcd5-418d-a211-8dd2d848b32d, 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:57.946 WARN  o.b.c.c.m.CollectionBasedConversationMediator - Failing timed out conversation 642f1696-dcd5-418d-a211-8dd2d848b32d (Age 1012ms)
          Result: Received event: 642f1696: GET_FILE for file default-test-file.txt: FAILED: , Failing timed out conversation 642f1696-dcd5-418d-a211-8dd2d848b32d
      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@5bce1e69[correlationID=3f3f96ad-f502-4208-b6df-c6839a4eadce, 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: 3f3f96ad: 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: 3f3f96ad: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 3f3f96ad: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
          Result: Received event: 3f3f96ad: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: 3f3f96ad: 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@50e46059[correlationID=3f3f96ad-f502-4208-b6df-c6839a4eadce, 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: 3f3f96ad: GET_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE
          Result: Received event: 3f3f96ad: GET_FILE for file default-test-file.txt: FAILED: , Failed to get file from Pillar1, org.bitrepository.bitrepositoryelements.ResponseInfo@f915ab3[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@33a49aca[correlationID=1ea4fce0-8371-4c5d-a556-57038bbefc9b, 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: 1ea4fce0: 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: 1ea4fce0: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
          Result: Received event: 1ea4fce0: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
          Result: Received event: 1ea4fce0: 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@4d4f6efb[correlationID=1ea4fce0-8371-4c5d-a556-57038bbefc9b, 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: 1ea4fce0: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2
          Result: Received event: 1ea4fce0: 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@1bd09bbc[correlationID=20953e5a-95e3-4c8f-a5d4-68986673f1ba, 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: 20953e5a: 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: 20953e5a: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
        Step: Wait 1 second.
          Result: Received event: 20953e5a: 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: 20953e5a: GET_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
          Result: Received event: 20953e5a: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: 20953e5a: 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@1a987d4c[correlationID=20953e5a-95e3-4c8f-a5d4-68986673f1ba, 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: 20953e5a: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1
          Result: Received event: 20953e5a: 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@3d4da817[correlationID=4a973183-f53c-4bcc-87ef-9efd7121c641, 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: 4a973183: 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: 4a973183: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
          Result: Received event: 4a973183: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
          Result: Received event: 4a973183: 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@3d7f8110[correlationID=4a973183-f53c-4bcc-87ef-9efd7121c641, 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: 4a973183: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2
          Result: Received event: 4a973183: 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@5b294fe7[correlationID=e287ba3b-9234-4109-bd85-09d134dfc8cb, 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: e287ba3b: 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: e287ba3b: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
          Result: Received event: e287ba3b: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
          Result: Received event: e287ba3b: 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@46ca7c9[correlationID=e287ba3b-9234-4109-bd85-09d134dfc8cb, 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: e287ba3b: GET_FILE for file default-test-file.txt: PROGRESS: ContributorID Pillar2, First test progress response message
        Step: Send a GetFileFinalResponse.
          Result: Received event: e287ba3b: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2
          Result: Received event: e287ba3b: 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@777777f2[correlationID=27d301b1-29d8-42f5-8d99-02a10f8e7e9e, 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: 27d301b1: 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: 27d301b1: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 27d301b1: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: 27d301b1: 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@7bec1342[correlationID=27d301b1-29d8-42f5-8d99-02a10f8e7e9e, 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@27b4172d[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: 27d301b1: 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: 27d301b1: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1
          Result: Received event: 27d301b1: 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@50bbad5c[correlationID=6eaa7ce5-dd4c-45d3-82fe-c3dfffe48d54, 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: 6eaa7ce5: GET_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetFile
        Step: Wait for 1 seconds
          Result: Received event: 6eaa7ce5: 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: 6eaa7ce5: GET_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor
          Result: Received event: 6eaa7ce5: GET_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
          Result: Received event: 6eaa7ce5: 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@36a0cf2b[correlationID=9b0659ff-08e0-4714-9027-653687bb578b, 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: 9b0659ff: 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: 9b0659ff: 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: 9b0659ff: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
          Result: Received event: 9b0659ff: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
          Result: Received event: 9b0659ff: 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@156d8f7b[correlationID=9b0659ff-08e0-4714-9027-653687bb578b, 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: 9b0659ff: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2
          Result: Received event: 9b0659ff: 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@26e7b0bd[correlationID=3a70ced5-207e-4b2e-bfbc-377d4f660603, 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: 3a70ced5: 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: 3a70ced5: 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: 3a70ced5: 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: 3a70ced5: 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@cf9073a[correlationID=eb6abc3c-f86d-423e-b7f6-6758bc92bf83, 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: eb6abc3c: 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: eb6abc3c: 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: eb6abc3c: 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 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@4d07c08d[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1de5e942[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@1089512e[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], eventHandler, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@41e65db7[correlationID=be36a200-ac1d-465f-8be2-5ed3497d03fe, 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: be36a200: 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: be36a200: 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: be36a200: DELETE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor
          Result: Received event: be36a200: 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@5761748e[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@58f72035[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@1b67989d[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], eventHandler, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@6b532a5[correlationID=bc07a760-887f-4412-baa2-fe1e6cf1e0b3, 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: bc07a760: 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: bc07a760: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: bc07a760: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: bc07a760: 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@3bbb9611[correlationID=bc07a760-887f-4412-baa2-fe1e6cf1e0b3, 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@5761748e[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@58f72035[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@1b67989d[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: bc07a760: 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@4fb4bffa[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@181bb932[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-10-15T02:20:03.524+02:00], null, eventHandler, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@6279d5fe[correlationID=9abc4a7f-f7c9-442d-82df-fb67276b74bc, 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: 9abc4a7f: 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: 9abc4a7f: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 9abc4a7f: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: 9abc4a7f: 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@7fbe92c6[correlationID=9abc4a7f-f7c9-442d-82df-fb67276b74bc, 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@4fb4bffa[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@181bb932[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-10-15T02:20:03.524+02:00], checksumRequestForExistingFile=<null>]
        Step: Send a final response message from pillar 1 to the DeleteClient.
          Result: Received event: 9abc4a7f: DELETE_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, DeleteFileResult=null
          Result: Received event: 9abc4a7f: 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@7d6cb988[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@69e34852[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@36ef63b1[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], eventHandler, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@387a3d5d[correlationID=ba9434b8-f904-49bb-b5e0-7004530fd358, 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: ba9434b8: 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: ba9434b8: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: ba9434b8: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: ba9434b8: 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@53100ea1[correlationID=ba9434b8-f904-49bb-b5e0-7004530fd358, 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@7d6cb988[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@69e34852[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@36ef63b1[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: ba9434b8: DELETE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE, Verifying that a failure can be understood!
          Result: Received event: ba9434b8: DELETE_FILE for file default-test-file.txt: FAILED: , Failed operation. Cause(s):
[ba9434b8: 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@73e15f73[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@b966ce3[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-10-15T02:20:04.709+02:00], null, eventHandler, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@4e3ee766[correlationID=e7b5f0ec-6266-41c3-a76c-0b5c903263da, 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: e7b5f0ec: 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: e7b5f0ec: DELETE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: IDENTIFICATION_NEGATIVE
          Result: Received event: e7b5f0ec: 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@6855bae5[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6d3e7bd0[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@3d4fad6c[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], eventHandler, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@1d646e4c[correlationID=977bceb0-458a-44ec-9091-571ee3f14f6b, 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: 977bceb0: 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: 977bceb0: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 977bceb0: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: 977bceb0: 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@46dd6da8[correlationID=977bceb0-458a-44ec-9091-571ee3f14f6b, 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@6855bae5[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6d3e7bd0[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@3d4fad6c[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: 977bceb0: 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: 977bceb0: DELETE_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, DeleteFileResult=null
          Result: Received event: 977bceb0: 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@50dd3bd2[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@15dadf44[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-10-15T02:20:04.901+02:00], null, eventHandler, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@2dae11b4[correlationID=51886039-d6bd-4628-b904-d242d8b71c04, 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: 51886039: 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: 51886039: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 51886039: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: 51886039: 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@20b167a2[correlationID=51886039-d6bd-4628-b904-d242d8b71c04, 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@50dd3bd2[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@15dadf44[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-10-15T02:20:04.901+02: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@3d8cef0c[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2b7d8e96[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-10-15T02:20:07.038+02:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@42d7ffe5[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], eventHandler, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@ba380a5[correlationID=2262db33-304c-4b29-931d-2b2c41864f47, 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: 2262db33: 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: 2262db33: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 2262db33: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: 2262db33: 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@16c3c7db[correlationID=2262db33-304c-4b29-931d-2b2c41864f47, 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@3d8cef0c[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2b7d8e96[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-10-15T02:20:07.038+02:00], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@42d7ffe5[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@4624e79a[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7e1ee1a5[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-10-15T02:20:07.146+02:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@305a4a7d[checksumType=MD5, checksumSalt={-86}, otherChecksumType=<null>], eventHandler, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@6670ff38[correlationID=5e517c17-38c1-4622-93df-a074f2736037, 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: 5e517c17: 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: 5e517c17: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 5e517c17: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: 5e517c17: 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@e1306d6[correlationID=5e517c17-38c1-4622-93df-a074f2736037, 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@4624e79a[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7e1ee1a5[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-10-15T02:20:07.146+02: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@10bf7e8e[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@5a1927f6[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-10-15T02:20:07.328+02:00], null, eventHandler, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@3d4e5eb[correlationID=bc871db6-976b-48de-9e10-83848a6fb350, 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: bc871db6: 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: bc871db6: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: bc871db6: DELETE_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, DeleteFileResult=null
          Result: Received event: bc871db6: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: []
          Result: Received event: bc871db6: 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 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@653adef5[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@18d76f8d[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@8a51c4e[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, 10, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@487f767e[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@18d76f8d[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@8a51c4e[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], org.bitrepository.client.TestEventHandler@7b81d4f2, null
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileRequest@58096708[correlationID=83c1623c-28c4-4c3b-8c93-25a3ca626625, 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: 83c1623c: 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: 83c1623c: 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: 83c1623c: REPLACE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor
          Result: Received event: 83c1623c: 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@3078c800[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@3ea04bda[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@321e503[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, 10, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@5c72ea80[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@3ea04bda[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@321e503[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], org.bitrepository.client.TestEventHandler@2abc01c6, null
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileRequest@167e61d0[correlationID=a8884d12-0229-4968-9521-ef5c3221ed4c, 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: a8884d12: 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: a8884d12: REPLACE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: a8884d12: REPLACE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: a8884d12: 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@511658c4[correlationID=a8884d12-0229-4968-9521-ef5c3221ed4c, 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@3078c800[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@3ea04bda[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@321e503[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@5c72ea80[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@3ea04bda[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@321e503[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: a8884d12: 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@59546b04[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@17db0fad[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@705bd68c[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, 0, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@41d71bec[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@17db0fad[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@705bd68c[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], org.bitrepository.client.TestEventHandler@3ba15499, null
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileRequest@74c89227[correlationID=24d474b3-0c20-495e-8eb5-8550b4835c5e, 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: 24d474b3: 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: 24d474b3: REPLACE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 24d474b3: REPLACE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: 24d474b3: 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@2378ad42[correlationID=24d474b3-0c20-495e-8eb5-8550b4835c5e, 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@59546b04[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@17db0fad[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@705bd68c[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@41d71bec[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@17db0fad[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@705bd68c[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: 24d474b3: REPLACE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE, Verifying that a failure can be understood!
          Result: Received event: 24d474b3: REPLACE_FILE for file default-test-file.txt: FAILED: , Failed operation. Cause(s):
[24d474b3: 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@71721588[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2b4e8d08[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@398cf908[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, 10, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@6b378dea[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2b4e8d08[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@398cf908[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], org.bitrepository.client.TestEventHandler@a080b51, null
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileRequest@55f1f1d5[correlationID=f4c10f81-0f4b-4fb5-a3cc-23e6f37455d0, 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: f4c10f81: 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: f4c10f81: REPLACE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: f4c10f81: REPLACE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: f4c10f81: 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@5ce49280[correlationID=f4c10f81-0f4b-4fb5-a3cc-23e6f37455d0, 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@71721588[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2b4e8d08[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@398cf908[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@6b378dea[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2b4e8d08[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@398cf908[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: f4c10f81: 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: f4c10f81: REPLACE_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, checksum for new file: 'org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@6b378dea[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2b4e8d08[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: f4c10f81: 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@3d64b103[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@c23f6cd[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@6fd717ad[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@c23f6cd[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@1580163d[checksumType=MD5, checksumSalt={-86}, otherChecksumType=<null>], org.bitrepository.client.TestEventHandler@d744127, null
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileRequest@1ef25bda[correlationID=015e1ca8-d75b-40e0-81af-c89f4c0896d4, 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: 015e1ca8: 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: 015e1ca8: REPLACE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 015e1ca8: REPLACE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: 015e1ca8: 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@5c6b8b2c[correlationID=015e1ca8-d75b-40e0-81af-c89f4c0896d4, 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@3d64b103[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@c23f6cd[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@6fd717ad[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@c23f6cd[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 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
      Finished testcase
  Finished suite
Finished project
Tests run: 156, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 67.817 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
[JENKINS] Archiving disabled
[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