[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Client 1.6-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-client ---
[INFO] Deleting /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/target
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ bitrepository-client ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 4 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ bitrepository-client ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 130 source files to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/target/classes
[WARNING] /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/src/main/java/org/bitrepository/commandline/utils/CommandLineArgumentsHandler.java: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/src/main/java/org/bitrepository/commandline/utils/CommandLineArgumentsHandler.java uses or overrides a deprecated API.
[WARNING] /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/src/main/java/org/bitrepository/commandline/utils/CommandLineArgumentsHandler.java: Recompile with -Xlint:deprecation for details.
[INFO]
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ bitrepository-client ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/src/test/resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ bitrepository-client ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 41 source files to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/target/test-classes
[INFO]
[INFO] --- maven-surefire-plugin:2.17:test (default-test) @ bitrepository-client ---
[INFO] Surefire report directory: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/target/surefire-reports
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running TestSuite
Configuring TestNG with: TestNG652Configurator
Starting test project Core module test
Suite: Surefire suite
Starting testcase AuditTrailClientComponentTest
Test starting: getAllAuditTrailsTest
Description: Tests the simplest case of getting all audit trail event for all contributers.
Step: Create a AuditTrailClient.
Step: Retrieve all audit trails from the collection by calling with a null componentQueries array
Stimuli: Calling getAuditTrails(null, default-test-file.txt, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@7de62196[correlationID=8f537eb1-6e68-4e83-b0ef-d09170e2d5a8, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=getAllAuditTrailsTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
Result: Received event: 8f537eb1: GET_AUDIT_TRAILS for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
Step: Send a identifyResponse from each pillar
Result: Received event: 8f537eb1: GET_AUDIT_TRAILS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 8f537eb1: GET_AUDIT_TRAILS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 8f537eb1: GET_AUDIT_TRAILS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2, Pillar1]
Result: Received event: 8f537eb1: GET_AUDIT_TRAILS for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for audit trails
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@51bd8b5c[correlationID=8f537eb1-6e68-4e83-b0ef-d09170e2d5a8, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=getAllAuditTrailsTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar1, fileID=default-test-file.txt, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@1b410b60[correlationID=8f537eb1-6e68-4e83-b0ef-d09170e2d5a8, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=getAllAuditTrailsTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar2, fileID=default-test-file.txt, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
Step: Send a final response from pillar 1
Result: Received event: 8f537eb1: GET_AUDIT_TRAILS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, NumberOfAuditTrailEvents=2, PartialResult=false
Step: Send a final response from pillar 2
Result: Received event: 8f537eb1: GET_AUDIT_TRAILS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2, NumberOfAuditTrailEvents=2, PartialResult=false
Result: Received event: 8f537eb1: GET_AUDIT_TRAILS for file default-test-file.txt: COMPLETE:
Test success: getAllAuditTrailsTest
Test starting: getSomeAuditTrailsTest
Description: Tests the client maps a AuditTrail query correctly to a GetAuditTrail request.
Step: Request audit trails from pillar 1 with both min and max sequence number set.
Stimuli: Calling getAuditTrails([AuditTrailQuery{componentID='Pillar1, minTimestamp=null, maxTimestamp=null, maxNumberOfResults=10000}minSequenceNumber=1, maxSequenceNumber=3}], null, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@5d066c7d[correlationID=cbc93cdd-3d4d-4008-9633-dca517817ee0, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=getSomeAuditTrailsTest, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>]
Result: Received event: cbc93cdd: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
Step: Send a identifyResponse from pillar1
Result: Received event: cbc93cdd: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: cbc93cdd: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: cbc93cdd: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1], Sending request for audit trails
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@5ba88be8[correlationID=cbc93cdd-3d4d-4008-9633-dca517817ee0, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=getSomeAuditTrailsTest, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar1, fileID=<null>, minSequenceNumber=1, maxSequenceNumber=3, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=10000, resultAddress=<null>]
Step: Verify no request is sent to pillar2
Step: Send a final response from pillar 1
Result: Received event: cbc93cdd: GET_AUDIT_TRAILS: COMPONENT_COMPLETE: ContributorID Pillar1, NumberOfAuditTrailEvents=2, PartialResult=false
Result: Received event: cbc93cdd: GET_AUDIT_TRAILS: COMPLETE:
Test success: getSomeAuditTrailsTest
Test starting: incompleteSetOfFinalResponsesTest
Description: Verify that the GetAuditTrail client works correct without receiving responses from all contributers.
Step: Configure 500 ms second timeout for the operation itself. The default 2 contributers collection is used
Stimuli: Calling getAuditTrails(null, null, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@4566d049[correlationID=81a5343b-c02f-4b1d-9e2c-9937bacb1483, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=incompleteSetOfFinalResponsesTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
Result: Received event: 81a5343b: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
Step: Send a identifyResponse from each of the two pillars
Result: Received event: 81a5343b: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 81a5343b: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 81a5343b: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2]
Result: Received event: 81a5343b: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for audit trails
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@1c3b9394[correlationID=81a5343b-c02f-4b1d-9e2c-9937bacb1483, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=incompleteSetOfFinalResponsesTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar1, fileID=<null>, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@6f2cfcc2[correlationID=81a5343b-c02f-4b1d-9e2c-9937bacb1483, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=incompleteSetOfFinalResponsesTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar2, fileID=<null>, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
Test success: incompleteSetOfFinalResponsesTest
Result: The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@6f2cfcc2[correlationID=81a5343b-c02f-4b1d-9e2c-9937bacb1483, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=incompleteSetOfFinalResponsesTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar2, fileID=<null>, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
02:18:53.811 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@6f2cfcc2[correlationID=81a5343b-c02f-4b1d-9e2c-9937bacb1483, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=incompleteSetOfFinalResponsesTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar2, fileID=<null>, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
Test starting: negativeGetAuditTrailsResponseTest
Description: Verify that the GetAuditTrail client works correct when receiving a negative GetAuditTrails response from one contributers.
Step: Create a AuditTrailClient.
Step: Retrieve all audit trails from the collection by calling with a null componentQueries array
Stimuli: Calling getAuditTrails(null, null, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@20b5f2ac[correlationID=a716742d-353b-41ee-9725-be5a57f78aab, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=negativeGetAuditTrailsResponseTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
Result: Received event: a716742d: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
Step: Send a identifyResponse from each of the two pillars
Result: Received event: a716742d: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: a716742d: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: a716742d: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2]
Result: Received event: a716742d: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for audit trails
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@293d0107[correlationID=a716742d-353b-41ee-9725-be5a57f78aab, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=negativeGetAuditTrailsResponseTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar1, fileID=<null>, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@2692b61e[correlationID=a716742d-353b-41ee-9725-be5a57f78aab, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=negativeGetAuditTrailsResponseTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar2, fileID=<null>, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
Step: Send a failed response from pillar 1
Result: Received event: a716742d: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE, GetAuditTrails failed
Step: Send a final response from pillar 2
Result: Received event: a716742d: GET_AUDIT_TRAILS: COMPONENT_COMPLETE: ContributorID Pillar2, NumberOfAuditTrailEvents=2, PartialResult=false
Result: Received event: a716742d: GET_AUDIT_TRAILS: FAILED: , Failed operation. Cause(s):
[a716742d: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE, GetAuditTrails failed]
Test success: negativeGetAuditTrailsResponseTest
Result: Received event: 81a5343b: GET_AUDIT_TRAILS: FAILED: , Failed to receive responses from all contributors before timeout(500ms). Missing contributors [Pillar1, Pillar2]
Test starting: noFinalResponsesTest
Description: Tests the the AuditTrailClient handles lack of Final Responses gracefully
Step: Set a 100 ms timeout for the operation.
Step: Make the client ask for all audit trails.
Stimuli: Calling getAuditTrails(null, null, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@18cc679e[correlationID=cd0ef75f-5de2-4e75-89cd-a53b03ceb0d2, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noFinalResponsesTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
Result: Received event: cd0ef75f: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
Step: Send a identifyResponse from each of the two pillars
Result: Received event: cd0ef75f: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: cd0ef75f: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: cd0ef75f: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2, Pillar1]
Result: Received event: cd0ef75f: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for audit trails
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@67ef029[correlationID=cd0ef75f-5de2-4e75-89cd-a53b03ceb0d2, 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@7df587ef[correlationID=cd0ef75f-5de2-4e75-89cd-a53b03ceb0d2, 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: cd0ef75f: 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@67ef029[correlationID=cd0ef75f-5de2-4e75-89cd-a53b03ceb0d2, 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:18:54.654 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@67ef029[correlationID=cd0ef75f-5de2-4e75-89cd-a53b03ceb0d2, 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@7df587ef[correlationID=cd0ef75f-5de2-4e75-89cd-a53b03ceb0d2, 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:18:54.656 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@7df587ef[correlationID=cd0ef75f-5de2-4e75-89cd-a53b03ceb0d2, 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@79ab3a71[correlationID=32fe5f80-a790-4526-9d9d-1feee6bcdf7a, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=progressEventsTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
Result: Received event: 32fe5f80: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
Step: Send a identifyResponse from each of the two pillars
Result: Received event: 32fe5f80: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 32fe5f80: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 32fe5f80: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2, Pillar1]
Result: Received event: 32fe5f80: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for audit trails
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@71652c98[correlationID=32fe5f80-a790-4526-9d9d-1feee6bcdf7a, 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@51bde877[correlationID=32fe5f80-a790-4526-9d9d-1feee6bcdf7a, 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: 32fe5f80: GET_AUDIT_TRAILS: PROGRESS: ContributorID Pillar1, GetAuditTrails request accepted
Step: Send a general progress response from pillar 2
Result: Received event: 32fe5f80: GET_AUDIT_TRAILS: PROGRESS: ContributorID Pillar2, Still progressing
Test success: progressEventsTest
Test starting: verifyAuditTrailClientFromFactory
Test success: verifyAuditTrailClientFromFactory
Starting testcase AuditTrailQueryTest
Test starting: testBothSequenceNumberFailure
Description: Test the creation of a AuditTrailQuery with both SequenceNumber, where max is smalle than min.
Test success: testBothSequenceNumberFailure
Test starting: testBothSequenceNumberSuccess
Description: Test the creation of a AuditTrailQuery with both SequenceNumber, where max is larger than min.
Test success: testBothSequenceNumberSuccess
Test starting: testNoSequenceNumbers
Description: Test that a AuditTrailQuery can be created without any sequence numbers.
Test success: testNoSequenceNumbers
Test starting: testOnlyMinSequenceNumber
Description: Test the creation of a AuditTrailQuery with only the minSequenceNumber
Test success: testOnlyMinSequenceNumber
Test starting: collectionIDIncludedInEventsTest
Description: Tests the the client provides collectionID in events.
Step: Set a 0.5 second operation timeout.
Step: Start the operation
Stimuli: Calling getAuditTrails(null, null, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@8c46918[correlationID=cc14589b-2c39-418c-baa2-f67a89110d2c, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=collectionIDIncludedInEventsTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
Result: Received event: cc14589b: 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: cc14589b: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: cc14589b: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE
Result: Received event: cc14589b: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: cc14589b: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1], Sending request for audit trails
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@682bd3c4[correlationID=cc14589b-2c39-418c-baa2-f67a89110d2c, 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: cc14589b: GET_AUDIT_TRAILS: FAILED: , Failed to receive responses from all contributors before timeout(500ms). Missing contributors [Pillar1]
Test success: collectionIDIncludedInEventsTest
Starting testcase GetChecksumsClientComponentTest
Test starting: collectionIDIncludedInEventsTest
Description: Tests the the client provides collectionID in events.
Step: Set a 0.5 second operation timeout.
Step: Start the operation
Stimuli: Calling getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@5cdf39b2, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@1cc9cfb2[correlationID=38d4c20e-7b5e-4445-bf7b-c5068da4aa91, 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@cfbc8e8[fileID=<null>, allFileIDs=true], checksumRequestForExistingFile=<null>]
Result: Received event: 38d4c20e: 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: 38d4c20e: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 38d4c20e: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE
Result: Received event: 38d4c20e: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 38d4c20e: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar1], Sending GetFileIDsRequest's
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@46d9aec8[correlationID=38d4c20e-7b5e-4445-bf7b-c5068da4aa91, 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@14379273[fileID=<null>, allFileIDs=true], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, checksumRequestForExistingFile=<null>, resultAddress=<null>]
Step: Wait for 1 second
Result: Received event: 38d4c20e: GET_CHECKSUMS: FAILED: , Failed to receive responses from all contributors before timeout(500ms). Missing contributors [Pillar1]
Test success: collectionIDIncludedInEventsTest
Test starting: conversationTimeoutTest
Description: Tests the the client handles lack of IdentifyPillarResponses gracefully
Step: Set a 100 ms ConversationTimeout.
Step: Start the operation
Stimuli: Calling getAuditTrails(null, null, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@367b22e5[correlationID=72a951d5-bb31-44b6-84bf-a6e23b310b61, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=conversationTimeoutTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
Result: Received event: 72a951d5: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
02:18:57.843 WARN o.b.c.c.m.CollectionBasedConversationMediator - Failing timed out conversation 72a951d5-bb31-44b6-84bf-a6e23b310b61 (Age 1003ms)
Result: Received event: 72a951d5: GET_AUDIT_TRAILS: FAILED: , Failing timed out conversation 72a951d5-bb31-44b6-84bf-a6e23b310b61
Test success: conversationTimeoutTest
Test starting: conversationTimeoutTest
Description: Tests the the client handles lack of IdentifyPillarResponses gracefully
Step: Set a 100 ms ConversationTimeout.
Step: Start the operation
Stimuli: Calling getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@5cdf39b2, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@2418ba04[correlationID=ec724787-fc4c-4ebd-9c5b-006be53f2dbc, 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@14229fa7[fileID=<null>, allFileIDs=true], checksumRequestForExistingFile=<null>]
Result: Received event: ec724787: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums
02:18:59.206 WARN o.b.c.c.m.CollectionBasedConversationMediator - Failing timed out conversation ec724787-fc4c-4ebd-9c5b-006be53f2dbc (Age 1010ms)
Result: Received event: ec724787: GET_CHECKSUMS: FAILED: , Failing timed out conversation ec724787-fc4c-4ebd-9c5b-006be53f2dbc
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@51c959a4[correlationID=643d4279-5335-4b0c-beb4-03599549c8a7, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=identificationFailureTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
Result: Received event: 643d4279: 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: 643d4279: 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: 643d4279: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 643d4279: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: 643d4279: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar2], Sending request for audit trails
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@10a0fe30[correlationID=643d4279-5335-4b0c-beb4-03599549c8a7, 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: 643d4279: GET_AUDIT_TRAILS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false
Result: Received event: 643d4279: GET_AUDIT_TRAILS: FAILED: , Failed operation. Cause(s):
[643d4279: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE]
Test success: identificationFailureTest
Test starting: identificationFailureTest
Description: Verify that the client works correctly when a contributor sends a failure response.
Step: Start the operation.
Stimuli: Calling getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@5cdf39b2, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@57562473[correlationID=5c713c18-c203-4e91-9713-fe1c4eed7329, 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@7a360554[fileID=<null>, allFileIDs=true], checksumRequestForExistingFile=<null>]
Result: Received event: 5c713c18: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums
Step: Send a identification response from contributor1 with a FAILURE response code.
Result: Received event: 5c713c18: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE
Step: Send a identification response from contributor2 with a IDENTIFICATION_POSITIVE response code .
Result: Received event: 5c713c18: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 5c713c18: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: 5c713c18: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar2], Sending GetFileIDsRequest's
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@4bc33720[correlationID=5c713c18-c203-4e91-9713-fe1c4eed7329, 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@2dd0f797[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: 5c713c18: GET_CHECKSUMS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false
Result: Received event: 5c713c18: GET_CHECKSUMS: FAILED: , Failed operation. Cause(s):
[5c713c18: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE]
Test success: identificationFailureTest
Test starting: identificationNegativeTest
Description: Verify that the client works correctly when a contributor sends a negative response.
Step: Start the operation.
Stimuli: Calling getAuditTrails(null, null, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@38830ea[correlationID=2ff43036-f530-4803-bd6f-050721605551, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=identificationNegativeTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
Result: Received event: 2ff43036: 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: 2ff43036: 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: 2ff43036: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 2ff43036: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: 2ff43036: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar2], Sending request for audit trails
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@3a790e40[correlationID=2ff43036-f530-4803-bd6f-050721605551, 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: 2ff43036: GET_AUDIT_TRAILS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false
Result: Received event: 2ff43036: GET_AUDIT_TRAILS: FAILED: , Failed operation. Cause(s):
[2ff43036: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: IDENTIFICATION_NEGATIVE]
Test success: identificationNegativeTest
Test starting: identificationNegativeTest
Description: Verify that the client works correctly when a contributor sends a negative response.
Step: Start the operation.
Stimuli: Calling getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@5cdf39b2, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@2d760326[correlationID=6aae2686-f0d1-41c8-ac15-21d09203fd8b, 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@9e54c59[fileID=<null>, allFileIDs=true], checksumRequestForExistingFile=<null>]
Result: Received event: 6aae2686: 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: 6aae2686: 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: 6aae2686: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 6aae2686: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: 6aae2686: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar2], Sending GetFileIDsRequest's
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@4a2e7bcb[correlationID=6aae2686-f0d1-41c8-ac15-21d09203fd8b, 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@575c3e9b[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: 6aae2686: GET_CHECKSUMS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false
Result: Received event: 6aae2686: GET_CHECKSUMS: FAILED: , Failed operation. Cause(s):
[6aae2686: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: IDENTIFICATION_NEGATIVE]
Test success: identificationNegativeTest
Test starting: noContributorsRespondingTest
Description: Tests the the client handles lack of a IdentifyResponse gracefully. More concrete this means that the occurrence of a identification timeout should be handled correctly
Step: Set a 100 ms timeout for identifying contributors.
Step: Start the operation.
Stimuli: Calling getAuditTrails(null, null, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@5f5827d0[correlationID=e4ba6547-1e02-4220-8dd9-15f4366ad7d4, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noContributorsRespondingTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
Result: Received event: e4ba6547: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
Step: Wait for 1 second
Result: Received event: e4ba6547: GET_AUDIT_TRAILS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar1, Pillar2]
Result: Received event: e4ba6547: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor
Result: Received event: e4ba6547: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
Result: Received event: e4ba6547: 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@5f5827d0[correlationID=e4ba6547-1e02-4220-8dd9-15f4366ad7d4, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noContributorsRespondingTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
02:19:05.791 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@5f5827d0[correlationID=e4ba6547-1e02-4220-8dd9-15f4366ad7d4, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noContributorsRespondingTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
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@5cdf39b2, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@6e829e50[correlationID=3183a7b2-6a73-4ddc-8bfb-482ee62a81d5, 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@4aa2877c[fileID=<null>, allFileIDs=true], checksumRequestForExistingFile=<null>]
Result: Received event: 3183a7b2: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums
Step: Wait for 1 second
Result: Received event: 3183a7b2: GET_CHECKSUMS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar1, Pillar2]
Result: Received event: 3183a7b2: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor
Result: Received event: 3183a7b2: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
Result: Received event: 3183a7b2: 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@6e829e50[correlationID=3183a7b2-6a73-4ddc-8bfb-482ee62a81d5, 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@4aa2877c[fileID=<null>, allFileIDs=true], checksumRequestForExistingFile=<null>]
02:19:06.315 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@6e829e50[correlationID=3183a7b2-6a73-4ddc-8bfb-482ee62a81d5, 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@4aa2877c[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 getAuditTrails(null, null, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@28babeca[correlationID=6050e6f2-aee8-48f6-b558-dee4badf6988, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=oneContributorNotRespondingTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
Result: Received event: 6050e6f2: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
Step: Send a identification response from contributor1.
Result: Received event: 6050e6f2: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Step: Wait 1 second.
Result: Received event: 6050e6f2: GET_AUDIT_TRAILS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar2]
Result: Received event: 6050e6f2: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
Result: Received event: 6050e6f2: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 6050e6f2: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1], Sending request for audit trails
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@7143dc9f[correlationID=6050e6f2-aee8-48f6-b558-dee4badf6988, 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: 6050e6f2: GET_AUDIT_TRAILS: COMPONENT_COMPLETE: ContributorID Pillar1, PartialResult=false
Result: Received event: 6050e6f2: GET_AUDIT_TRAILS: FAILED: , Failed operation. Cause(s):
[6050e6f2: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor]
Test success: oneContributorNotRespondingTest
Test starting: oneContributorNotRespondingTest
Description: Verify that the client works correct without receiving identification responses from all contributors.
Added fixture: Set the a identification timeout to 100 ms.
Step: Start the operation.
Stimuli: Calling getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@5cdf39b2, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@6ee88e21[correlationID=d1a61a2f-722f-4296-9c3b-e24ed5d48122, 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@78d23d6a[fileID=<null>, allFileIDs=true], checksumRequestForExistingFile=<null>]
Result: Received event: d1a61a2f: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums
Step: Send a identification response from contributor1.
Result: Received event: d1a61a2f: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Step: Wait 1 second.
Result: Received event: d1a61a2f: GET_CHECKSUMS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar2]
Result: Received event: d1a61a2f: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
Result: Received event: d1a61a2f: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: d1a61a2f: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar1], Sending GetFileIDsRequest's
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@7f843cc7[correlationID=d1a61a2f-722f-4296-9c3b-e24ed5d48122, 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@7bbbb7ef[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: d1a61a2f: GET_CHECKSUMS: COMPONENT_COMPLETE: ContributorID Pillar1, PartialResult=false
Result: Received event: d1a61a2f: GET_CHECKSUMS: FAILED: , Failed operation. Cause(s):
[d1a61a2f: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor]
Test success: oneContributorNotRespondingTest
Test starting: operationTimeoutTest
Description: Tests the the client handles lack of final responses gracefully.
Step: Set a 100 ms operation timeout.
Step: Start the operation
Stimuli: Calling getAuditTrails(null, null, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@6d5f4900[correlationID=6648a028-29e3-48cc-b456-92e661f49b05, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=operationTimeoutTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
Result: Received event: 6648a028: 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: 6648a028: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 6648a028: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE
Result: Received event: 6648a028: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 6648a028: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1], Sending request for audit trails
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@1b560eb0[correlationID=6648a028-29e3-48cc-b456-92e661f49b05, 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: 6648a028: GET_AUDIT_TRAILS: FAILED: , Failed to receive responses from all contributors before timeout(100ms). Missing contributors [Pillar1]
Test success: operationTimeoutTest
Test starting: operationTimeoutTest
Description: Tests the the client handles lack of final responses gracefully.
Step: Set a 100 ms operation timeout.
Step: Start the operation
Stimuli: Calling getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@5cdf39b2, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@5122e4bf[correlationID=d6af8a03-7c7d-430d-8c3d-9b7f9b3d8bfa, 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@23e61112[fileID=<null>, allFileIDs=true], checksumRequestForExistingFile=<null>]
Result: Received event: d6af8a03: 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: d6af8a03: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: d6af8a03: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE
Result: Received event: d6af8a03: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: d6af8a03: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar1], Sending GetFileIDsRequest's
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@61b60600[correlationID=d6af8a03-7c7d-430d-8c3d-9b7f9b3d8bfa, 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@27f71195[fileID=<null>, allFileIDs=true], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, checksumRequestForExistingFile=<null>, resultAddress=<null>]
Step: Wait for 1 second
Result: Received event: d6af8a03: GET_CHECKSUMS: FAILED: , Failed to receive responses from all contributors before timeout(100ms). Missing contributors [Pillar1]
Test success: operationTimeoutTest
Starting testcase DeleteFileClientComponentTest
Test starting: deleteClientIdentificationTimeout
Description: Tests the handling of a failed identification for the DeleteClient
Step: Initialise the number of pillars and the DeleteClient. Sets the identification timeout to 1 sec.
Step: Request a file to be deleted on the default pillar.
Stimuli: Calling deleteFile(default-test-file.txt, Pillar1, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@5514579e[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@58c42c8c[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@3af236d0[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], eventHandler, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@23564dd2[correlationID=04697557-ee95-4c62-99e6-3e2b16841975, 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: 04697557: 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: 04697557: 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: 04697557: DELETE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor
Result: Received event: 04697557: 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@1a785fd5[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@4a660b34[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@362a561e[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], eventHandler, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@2df3545d[correlationID=2c849618-6264-4c69-b053-50d7a9249025, 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: 2c849618: 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: 2c849618: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 2c849618: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 2c849618: 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@fe8aaeb[correlationID=2c849618-6264-4c69-b053-50d7a9249025, 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@1a785fd5[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@4a660b34[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@362a561e[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: 2c849618: 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@39ace1a7[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1930a804[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-12-08T02:19:09.623+01:00], null, eventHandler, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@bd4ee01[correlationID=542319fb-e377-4c37-8ba6-c541c707f8c7, 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: 542319fb: 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: 542319fb: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 542319fb: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 542319fb: 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@598657cd[correlationID=542319fb-e377-4c37-8ba6-c541c707f8c7, 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@39ace1a7[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1930a804[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-12-08T02:19:09.623+01:00], checksumRequestForExistingFile=<null>]
Step: Send a final response message from pillar 1 to the DeleteClient.
Result: Received event: 542319fb: DELETE_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, DeleteFileResult=null
Result: Received event: 542319fb: 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@7433ca19[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@5d221b20[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@79d4ff58[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], eventHandler, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@7ec13984[correlationID=5b2d7046-0400-4f42-9727-d15d1970af41, 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: 5b2d7046: 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: 5b2d7046: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 5b2d7046: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 5b2d7046: 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@59fea5f5[correlationID=5b2d7046-0400-4f42-9727-d15d1970af41, 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@7433ca19[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@5d221b20[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@79d4ff58[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: 5b2d7046: DELETE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE, Verifying that a failure can be understood!
Result: Received event: 5b2d7046: DELETE_FILE for file default-test-file.txt: FAILED: , Failed operation. Cause(s):
[5b2d7046: 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@222d9d4f[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@4269aad7[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-12-08T02:19:11.458+01:00], null, eventHandler, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@a4df251[correlationID=88806153-ab77-4b26-b085-a7b7b3c48494, 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: 88806153: 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: 88806153: DELETE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: IDENTIFICATION_NEGATIVE
Result: Received event: 88806153: 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@3b9c9b8b[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7769d9b6[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@248d3a[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], eventHandler, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@3c71cf3e[correlationID=057ee113-5ffa-4b8b-91d3-4cebcbbc7104, 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: 057ee113: 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: 057ee113: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 057ee113: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 057ee113: 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@5af38a4a[correlationID=057ee113-5ffa-4b8b-91d3-4cebcbbc7104, 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@3b9c9b8b[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7769d9b6[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@248d3a[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: 057ee113: 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: 057ee113: DELETE_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, DeleteFileResult=null
Result: Received event: 057ee113: 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@713e7d9a[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@681d704e[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-12-08T02:19:11.962+01:00], null, eventHandler, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@846b47[correlationID=861802e5-92e9-4f75-b9f5-b48d800a9517, 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: 861802e5: 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: 861802e5: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 861802e5: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 861802e5: 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@3e6acec2[correlationID=861802e5-92e9-4f75-b9f5-b48d800a9517, 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@713e7d9a[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@681d704e[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-12-08T02:19:11.962+01:00], checksumRequestForExistingFile=<null>]
Test success: deleteOnChecksumPillar
Test starting: deleteOnChecksumPillarWithDefaultReturnChecksumType
Description: Verify that the DeleteClient works correctly when a return checksum of the default typeis requested.
Step: Request a file to be deleted on the pillar1. The call should include a request for a check sum of the default type
Stimuli: Calling deleteFile(default-test-file.txt, Pillar1, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@48692405[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@151659dd[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-12-08T02:19:14.594+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@4a58e0e9[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], eventHandler, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@e8c84eb[correlationID=fa8ae9a9-9956-4196-86ca-03be5b7196a2, 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: fa8ae9a9: 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: fa8ae9a9: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: fa8ae9a9: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: fa8ae9a9: 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@25e95af1[correlationID=fa8ae9a9-9956-4196-86ca-03be5b7196a2, 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@48692405[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@151659dd[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-12-08T02:19:14.594+01:00], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@4a58e0e9[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@3be46d9c[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@41d877bb[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-12-08T02:19:15.117+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@39c5a105[checksumType=MD5, checksumSalt={-86}, otherChecksumType=<null>], eventHandler, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@492fa72a[correlationID=2564c8ad-f476-4290-bdd4-fe076036ef99, 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: 2564c8ad: 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: 2564c8ad: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 2564c8ad: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 2564c8ad: 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@53d87b2d[correlationID=2564c8ad-f476-4290-bdd4-fe076036ef99, 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@3be46d9c[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@41d877bb[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-12-08T02:19:15.117+01:00], checksumRequestForExistingFile=<null>]
Test success: deleteOnChecksumPillarWithSaltedReturnChecksumType
Test starting: fileAlreadyDeletedFromPillar
Description: Test that a delete on a pillar completes successfully when the file is missing (has already been deleted). This is a test of the Idempotent behaviour of the delete client
Step: Request a file to be deleted on pillar1.
Stimuli: Calling deleteFile(default-test-file.txt, Pillar1, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@575d48db[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1b36d248[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-12-08T02:19:15.967+01:00], null, eventHandler, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@7e94de5f[correlationID=7eb0aa81-0024-48c4-be17-03750887876e, 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: 7eb0aa81: 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: 7eb0aa81: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 7eb0aa81: DELETE_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, DeleteFileResult=null
Result: Received event: 7eb0aa81: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: []
Result: Received event: 7eb0aa81: 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
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@18b30951, TEST-AUDIT)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@48f4264e[correlationID=19487a61-60a7-43de-8999-dc3ea975b0ae, 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@2697c156[fileID=default-test-file.txt, allFileIDs=<null>], checksumRequestForExistingFile=<null>]
Result: Received event: 19487a61: 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: 19487a61: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 19487a61: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 19487a61: GET_CHECKSUMS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2, Pillar1]
Result: Received event: 19487a61: 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@3a6b94b6[correlationID=19487a61-60a7-43de-8999-dc3ea975b0ae, 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@22ee7fdc[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@1a88d194[correlationID=19487a61-60a7-43de-8999-dc3ea975b0ae, 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@6949cead[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: 19487a61: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, NumberOfChecksums=0, PartialResult=false
Result: Received event: 19487a61: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2, NumberOfChecksums=0, PartialResult=false
Result: Received event: 19487a61: 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@1a88d194[correlationID=19487a61-60a7-43de-8999-dc3ea975b0ae, 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@6949cead[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:17.793 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.GetChecksumsRequest@1a88d194[correlationID=19487a61-60a7-43de-8999-dc3ea975b0ae, 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@6949cead[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@14bf9fd0, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@391e5ffa[correlationID=fa038b0b-9cb7-44e2-b740-36b2202c74a7, 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@f4d391c[fileID=<null>, allFileIDs=true], checksumRequestForExistingFile=<null>]
Result: Received event: fa038b0b: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums
Step: Send an identification response from pillar2.
Result: Received event: fa038b0b: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: fa038b0b: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: fa038b0b: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar2], Sending GetFileIDsRequest's
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@2fa2143d[correlationID=fa038b0b-9cb7-44e2-b740-36b2202c74a7, 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@64887fbc[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: fa038b0b: GET_CHECKSUMS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false
Result: Received event: fa038b0b: 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@417751d3[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], null, org.bitrepository.client.TestEventHandler@5bf4dfb, TEST-AUDIT)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@8c3b634[correlationID=643f9cb5-d5b8-4995-913d-b6850f23c446, 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@65259737[fileID=default-test-file.txt, allFileIDs=<null>], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@417751d3[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>]]
Result: Received event: 643f9cb5: 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: 643f9cb5: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 643f9cb5: GET_CHECKSUMS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 643f9cb5: 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@6108fd23[correlationID=643f9cb5-d5b8-4995-913d-b6850f23c446, 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@746f8520[fileID=default-test-file.txt, allFileIDs=<null>], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@417751d3[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], resultAddress=<null>]
Step: Send a GetChecksumsFinalResponse to the client from pillar1
Result: Received event: 643f9cb5: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, NumberOfChecksums=0, PartialResult=false
Result: Received event: 643f9cb5: 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@4af44f2a, TEST-AUDIT)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@570127fa[correlationID=6f3b2c89-efae-45aa-bef0-b77dbc486ab3, 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@5b324447[fileID=default-test-file.txt, allFileIDs=<null>], checksumRequestForExistingFile=<null>]
Result: Received event: 6f3b2c89: 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: 6f3b2c89: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 6f3b2c89: GET_CHECKSUMS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 6f3b2c89: 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@47994b51[correlationID=6f3b2c89-efae-45aa-bef0-b77dbc486ab3, 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@19f99aaf[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: 6f3b2c89: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FILE_NOT_FOUND_FAILURE, No such file.
Result: Received event: 6f3b2c89: GET_CHECKSUMS for file default-test-file.txt: FAILED: , Failed operation. Cause(s):
[6f3b2c89: 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=Tue Dec 08 02:19:18 CET 2015, maxTimestamp=Tue Dec 08 02:19:19 CET 2015, maxNumberOfResults=1}, ContributorQuery{componentID='Pillar2, minTimestamp=Tue Dec 08 02:19:19 CET 2015, maxTimestamp=Tue Dec 08 02:19:19 CET 2015, maxNumberOfResults=2}], null, null, null, org.bitrepository.client.TestEventHandler@5cdf39b2, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@2d758472[correlationID=95256734-271f-4d14-a556-6653a296437f, 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@7615666e[fileID=<null>, allFileIDs=true], checksumRequestForExistingFile=<null>]
Result: Received event: 95256734: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums
Step: Send a IdentifyPillarsForGetChecksumsResponse from both pillars.
Result: Received event: 95256734: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 95256734: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 95256734: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2, Pillar1]
Result: Received event: 95256734: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending GetFileIDsRequest's
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@33e6bd36[correlationID=95256734-271f-4d14-a556-6653a296437f, 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@6e1d9b32[fileID=<null>, allFileIDs=true], minTimestamp=2015-12-08T02:19:18.875+01:00, maxTimestamp=2015-12-08T02:19:19.775+01:00, maxNumberOfResults=1, checksumRequestForExistingFile=<null>, resultAddress=<null>]
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@2db6ba81[correlationID=95256734-271f-4d14-a556-6653a296437f, 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@10728fe8[fileID=<null>, allFileIDs=true], minTimestamp=2015-12-08T02:19:19.775+01:00, maxTimestamp=2015-12-08T02:19:19.875+01:00, maxNumberOfResults=2, checksumRequestForExistingFile=<null>, resultAddress=<null>]
Test success: testPaging
Test starting: verifyGetChecksumsClientFromFactory
Test success: verifyGetChecksumsClientFromFactory
Starting testcase GetStatusClientComponentTest
Test starting: getAllStatuses
Description: Tests the simplest case of getting status for all contributers.
Step: Create a GetStatusClient.
Step: Retrieve from all contributors in the collection
Stimuli: Calling getAuditTrails()
Result: Received event: f7b389c2: GET_STATUS: IDENTIFY_REQUEST_SENT: , Identifying contributors for getting status
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetStatusRequest@7e741d6b[correlationID=f7b389c2-5ec8-4177-9bba-954e897bf7d5, collectionID=<null>, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetStatusClientComponentTest-cibuild01, from=getAllStatuses, to=<null>, version=28, minVersion=24, auditTrailInformation=]
Step: Send a identifyResponse from each pillar
Result: Received event: f7b389c2: GET_STATUS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: f7b389c2: GET_STATUS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: f7b389c2: GET_STATUS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2]
Result: Received event: f7b389c2: GET_STATUS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending GetStatusRequest
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetStatusRequest@662e5590[correlationID=f7b389c2-5ec8-4177-9bba-954e897bf7d5, collectionID=<null>, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetStatusClientComponentTest-cibuild01, from=getAllStatuses, to=<null>, version=28, minVersion=24, auditTrailInformation=, contributor=Pillar1]
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetStatusRequest@23e573e[correlationID=f7b389c2-5ec8-4177-9bba-954e897bf7d5, collectionID=<null>, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetStatusClientComponentTest-cibuild01, from=getAllStatuses, to=<null>, version=28, minVersion=24, auditTrailInformation=, contributor=Pillar2]
Step: Send a final response from pillar 1
Result: Received event: f7b389c2: GET_STATUS: COMPONENT_COMPLETE: ContributorID Pillar1, resulting status: org.bitrepository.bitrepositoryelements.ResultingStatus@53f94afe[statusInfo=org.bitrepository.bitrepositoryelements.StatusInfo@304e1e4e[statusCode=OK, statusText=Everythings fine..], statusTimestamp=2015-12-08T02:19:20.655+01:00]
Step: Send a final response from pillar 2
Result: Received event: f7b389c2: GET_STATUS: COMPONENT_COMPLETE: ContributorID Pillar2, resulting status: org.bitrepository.bitrepositoryelements.ResultingStatus@7d4e424e[statusInfo=org.bitrepository.bitrepositoryelements.StatusInfo@799206ad[statusCode=OK, statusText=Everythings fine..], statusTimestamp=2015-12-08T02:19:20.656+01:00]
Result: Received event: f7b389c2: GET_STATUS: COMPLETE:
Test success: getAllStatuses
Test starting: incompleteSetOfIdendifyResponses
Description: Verify that the GetStatus client works correct without receiving responses from all contributers.
Step: Configure 1 second timeout for identifying contributers. The default 2 contributers collection is used
Stimuli: Calling getAuditTrails()
Result: Received event: 5e50acd5: GET_STATUS: IDENTIFY_REQUEST_SENT: , Identifying contributors for getting status
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetStatusRequest@1e5e2e06[correlationID=5e50acd5-3774-4ff7-bd1e-3f73692e6d39, collectionID=<null>, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetStatusClientComponentTest-cibuild01, from=incompleteSetOfIdendifyResponses, to=<null>, version=28, minVersion=24, auditTrailInformation=]
Step: Send a identifyResponse from pillar 1
Result: Received event: 5e50acd5: GET_STATUS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Step: Wait for timeout event
Result: Received event: 5e50acd5: GET_STATUS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar2]
Result: Received event: 5e50acd5: GET_STATUS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
Result: Received event: 5e50acd5: GET_STATUS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 5e50acd5: GET_STATUS: REQUEST_SENT: ContributorID [Pillar1], Sending GetStatusRequest
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetStatusRequest@3eb936fc[correlationID=5e50acd5-3774-4ff7-bd1e-3f73692e6d39, collectionID=<null>, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetStatusClientComponentTest-cibuild01, from=incompleteSetOfIdendifyResponses, to=<null>, version=28, minVersion=24, auditTrailInformation=, contributor=Pillar1]
Test success: incompleteSetOfIdendifyResponses
Test starting: verifyGetStatusClientFromFactory
Test success: verifyGetStatusClientFromFactory
Starting testcase NegativeResponseExceptionTest
Test starting: testNegativeResponse
Description: Test the instantiation of the exception
Step: Setup
Step: Try to throw such an exception with the response code
Test success: testNegativeResponse
Starting testcase PutFileCmdTest
Test starting: checksumArgumentNonSaltAlgorithmWitoutSaltTest
Description: Test MD5 checksum without salt -> no failure
Test success: checksumArgumentNonSaltAlgorithmWitoutSaltTest
Test starting: checksumArgumentSaltAlgorithmWithSaltTest
Description: Test HMAC_SHA256 checksum with salt -> No failure
Test success: checksumArgumentSaltAlgorithmWithSaltTest
Test starting: defaultSuccessScenarioTest
Description: Tests simplest arguments for running the CmdLineClient
Test success: defaultSuccessScenarioTest
Test starting: missingChecksumWhenFileArgumentTest
Description: Tests the scenario, where no checksum argument is given, but a file is given.
Test success: missingChecksumWhenFileArgumentTest
Test starting: missingChecksumWhenURLArgumentTest
Description: Tests the scenario, where no checksum argument is given, but a URL is given.
Invalid argument: The URL argument requires also the checksum argument (-c).
Test success: missingChecksumWhenURLArgumentTest
Test starting: missingCollectionArgumentTest
Description: Tests the scenario, where the collection arguments is missing.
Takes the following arguments:
-s The path to the directory with the settings files for the client
-k The path to the file containing the private key.
-v Makes the client more verbose
-c The id for the collection to perform the operation on.
-i The id for the file to perform the operation on.
-p [OPTIONAL] The id of the pillar where the should be performed. If undefined the operations is performed on all pillars.
-f The path to the file, which is wanted to be put. Is required, unless a URL is given.
-u The URL for the file to be put. Is required, unless the actual file is given.
-C The checksum for the file to be retreived. Required if using an URL.
-R [OPTIONAL] The algorithm of checksum to request in the response from the pillars.
-S [OPTIONAL] The salt of checksum to request in the response. Requires the ChecksumType argument.
-d If this argument is present, then the file will be removed from the server, when the operation is complete.
Missing argument: Missing required option: c
Test success: missingCollectionArgumentTest
Test starting: missingFileIDWhenFileArgumentTest
Description: Tests the scenario, where no checksum argument is given, but a URL is given.
Test success: missingFileIDWhenFileArgumentTest
Test starting: missingFileIDWhenURLArgumentTest
Description: Tests the scenario, where no checksum argument is given, but a URL is given.
Invalid argument: The URL argument requires also the argument for the ID of the file (-i).
Test success: missingFileIDWhenURLArgumentTest
Test starting: missingFileOrURLArgumentTest
Description: Tests the scenario, where no arguments for file or url is given.
Invalid argument: Requires either the file argument (-f) or the URL argument (-u).
Test success: missingFileOrURLArgumentTest
Test starting: specificPillarArgumentTest
Description: Test argument for a specific pillar
Test success: specificPillarArgumentTest
Test starting: unknownPillarArgumentTest
Description: Testing against a non-existing pillar id -> Should fail
Invalid argument: Random1449537564848pillar is not a valid pillar for collection TwoPillarCollection
The collection contains the following pillars: [Pillar1, Pillar2]
Test success: unknownPillarArgumentTest
Test starting: urlSuccessScenarioTest
Description: Tests arguments for putting a file on a given URL
Test success: urlSuccessScenarioTest
Starting testcase ReplaceFileClientComponentTest
Test starting: replaceClientIdentificationTimeout
Description: Tests the handling of a failed identification for the ReplaceClient
Step: Initialise the number of pillars and the DeleteClient. Sets the identification timeout to 100 ms.
Step: Request a file to be replaced on the default pillar.
Stimuli: replaceFile(default-test-file.txt, Pillar1, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@1c586bb6[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@503eac4c[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@1eaf95d2[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, 10, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@2836374[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@503eac4c[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@1eaf95d2[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], org.bitrepository.client.TestEventHandler@5d59ad49, null
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileRequest@78a03662[correlationID=094e6f24-f8a3-427d-bfa6-daaf994aa751, 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: 094e6f24: 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: 094e6f24: 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: 094e6f24: REPLACE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor
Result: Received event: 094e6f24: 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@68fce3e5[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@d2eddc2[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@13967a64[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, 10, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@30d4d6fb[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@d2eddc2[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@13967a64[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], org.bitrepository.client.TestEventHandler@3fb8e8cf, null
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileRequest@4483e237[correlationID=6c6cb89f-f9d4-4f11-bbd6-8d6892273859, 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: 6c6cb89f: 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: 6c6cb89f: REPLACE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 6c6cb89f: REPLACE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 6c6cb89f: 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@721384e0[correlationID=6c6cb89f-f9d4-4f11-bbd6-8d6892273859, 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@68fce3e5[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@d2eddc2[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@13967a64[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@30d4d6fb[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@d2eddc2[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@13967a64[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: 6c6cb89f: 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@4f3d49e4[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7d26b390[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@6ff5eeed[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, 0, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@76b49d0[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7d26b390[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@6ff5eeed[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], org.bitrepository.client.TestEventHandler@223c42b0, null
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileRequest@6acedf54[correlationID=e8740a2e-3f5f-4704-b9e7-36ce3f384fe7, 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: e8740a2e: 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: e8740a2e: REPLACE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: e8740a2e: REPLACE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: e8740a2e: 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@77f43f3e[correlationID=e8740a2e-3f5f-4704-b9e7-36ce3f384fe7, 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@4f3d49e4[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7d26b390[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@6ff5eeed[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@76b49d0[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7d26b390[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@6ff5eeed[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: e8740a2e: REPLACE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE, Verifying that a failure can be understood!
Result: Received event: e8740a2e: REPLACE_FILE for file default-test-file.txt: FAILED: , Failed operation. Cause(s):
[e8740a2e: 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@1f9e42d2[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@4f1fb8fc[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@759c0c14[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, 10, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@61427cd3[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@4f1fb8fc[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@759c0c14[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], org.bitrepository.client.TestEventHandler@ca72afb, null
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileRequest@3e4dabcb[correlationID=784e6ec0-7a01-4286-be14-b53f9dd05c28, 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: 784e6ec0: 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: 784e6ec0: REPLACE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 784e6ec0: REPLACE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 784e6ec0: 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@59f2a9e9[correlationID=784e6ec0-7a01-4286-be14-b53f9dd05c28, 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@1f9e42d2[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@4f1fb8fc[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@759c0c14[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@61427cd3[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@4f1fb8fc[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@759c0c14[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: 784e6ec0: 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: 784e6ec0: REPLACE_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, checksum for new file: 'org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@61427cd3[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@4f1fb8fc[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: 784e6ec0: 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@7d0ae3d1[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2114955c[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@1362f4[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2114955c[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@6e5506c9[checksumType=MD5, checksumSalt={-86}, otherChecksumType=<null>], org.bitrepository.client.TestEventHandler@446b74b9, null
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileRequest@41d0b71d[correlationID=d0adb9c7-8358-4f48-871b-dac3d3c7c48e, 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: d0adb9c7: 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: d0adb9c7: REPLACE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: d0adb9c7: REPLACE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: d0adb9c7: 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@1cea4fdf[correlationID=d0adb9c7-8358-4f48-871b-dac3d3c7c48e, 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@7d0ae3d1[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2114955c[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@1362f4[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2114955c[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
Starting testcase CommandLineTest
Test starting: argumentsTesterUnknownArgument
Description: Test the handling of arguments by the CommandLineArgumentHandler.
Step: Validate arguments without any options.
Test success: argumentsTesterUnknownArgument
Test starting: argumentsTesterWrongArgument
Description: Test the handling of arguments by the CommandLineArgumentHandler.
Step: Validate the default options
Test success: argumentsTesterWrongArgument
Test starting: newArgumentTester
Description: Test the handling of a new argument.
Step: Test the option
Test success: newArgumentTester
Starting testcase DeleteFileCmdTest
Test starting: checksumArgumentNonSaltAlgorithmWitoutSaltTest
Description: Test MD5 checksum without salt -> no failure
Test success: checksumArgumentNonSaltAlgorithmWitoutSaltTest
Test starting: checksumArgumentSaltAlgorithmWithSaltTest
Description: Test HMAC_SHA256 checksum with salt -> No failure
Test success: checksumArgumentSaltAlgorithmWithSaltTest
Test starting: defaultSuccessScenarioTest
Description: Tests simplest arguments for running the CmdLineClient
Test success: defaultSuccessScenarioTest
Test starting: missingCollectionArgumentTest
Description: Tests the scenario, where the collection arguments is missing.
Takes the following arguments:
-s The path to the directory with the settings files for the client
-k The path to the file containing the private key.
-v Makes the client more verbose
-c The id for the collection to perform the operation on.
-i The id for the file to perform the operation on.
-p [OPTIONAL] The id of the pillar where the should be performed. If undefined the operations is performed on all pillars.
-C [OPTIONAL] The checksum of the file to be delete.
-R [OPTIONAL] The algorithm of checksum to request in the response from the pillars.
-S [OPTIONAL] The salt of checksum to request in the response. Requires the ChecksumType argument.
Missing argument: Missing required option: c
Test success: missingCollectionArgumentTest
Test starting: missingFileIDArgumentTest
Description: Tests the scenario, where no arguments for file id argument is given.
Takes the following arguments:
-s The path to the directory with the settings files for the client
-k The path to the file containing the private key.
-v Makes the client more verbose
-c The id for the collection to perform the operation on.
-i The id for the file to perform the operation on.
-p [OPTIONAL] The id of the pillar where the should be performed. If undefined the operations is performed on all pillars.
-C [OPTIONAL] The checksum of the file to be delete.
-R [OPTIONAL] The algorithm of checksum to request in the response from the pillars.
-S [OPTIONAL] The salt of checksum to request in the response. Requires the ChecksumType argument.
Missing argument: Missing required option: i
Test success: missingFileIDArgumentTest
Test starting: missingPillarArgumentTest
Description: Tests the different scenarios, with the pillar argument.
Invalid argument: The pillar argument -p must defined for the delete operation, only single pillar deletes are allowed
Test success: missingPillarArgumentTest
Test starting: unknownPillarArgumentTest
Step: Testing against a non-existing pillar id
Invalid argument: Random1449537567113pillar is not a valid pillar for collection TwoPillarCollection
The collection contains the following pillars: [Pillar1, Pillar2]
Test success: unknownPillarArgumentTest
Starting testcase GetFileClientComponentTest
Test starting: chooseFastestPillarGetFileClient
Description: Set the GetClient to retrieve a file as fast as possible, where it has to choose between to pillars with different times. The messages should be delivered at the same time.
Step: Create a GetFileClient configured to use a fast and a slow pillar.
Step: Defining the variables for the GetFileClient and defining them in the configuration
Step: Make the GetClient ask for fastest pillar.
Stimuli: Calling getFileFromFastestPillar(default-test-file.txt, file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileRequest@40c0937f[correlationID=18286f6a-439b-4239-94af-61a7bb328249, 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: 18286f6a: 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: 18286f6a: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID THE-AVERAGE-PILLAR
Result: Received event: 18286f6a: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID THE-FAST-PILLAR
Result: Received event: 18286f6a: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID THE-SLOW-PILLAR
Result: Received event: 18286f6a: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [THE-FAST-PILLAR]
Result: Received event: 18286f6a: 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@3e5a40e7[correlationID=18286f6a-439b-4239-94af-61a7bb328249, 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@766f5049[correlationID=4adaf9f8-5e64-4a50-b32e-8cde12598603, 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: 4adaf9f8: 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: 4adaf9f8: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 4adaf9f8: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 4adaf9f8: 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@207b440f[correlationID=4adaf9f8-5e64-4a50-b32e-8cde12598603, 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:28.395 WARN o.b.c.c.m.CollectionBasedConversationMediator - Failing timed out conversation 4adaf9f8-5e64-4a50-b32e-8cde12598603 (Age 999ms)
Result: Received event: 4adaf9f8: GET_FILE for file default-test-file.txt: FAILED: , Failing timed out conversation 4adaf9f8-5e64-4a50-b32e-8cde12598603
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@c030d36[correlationID=eaddebf7-572c-485d-a98e-50d451057e56, 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: eaddebf7: 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: eaddebf7: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: eaddebf7: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: eaddebf7: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: eaddebf7: 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@2ef116e8[correlationID=eaddebf7-572c-485d-a98e-50d451057e56, 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: eaddebf7: GET_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE
Result: Received event: eaddebf7: GET_FILE for file default-test-file.txt: FAILED: , Failed to get file from Pillar1, org.bitrepository.bitrepositoryelements.ResponseInfo@243d57d4[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@17abb298[correlationID=da9f7297-1ece-4043-8e64-70e16839fb93, 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: da9f7297: 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: da9f7297: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: da9f7297: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: da9f7297: 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@22d61fa7[correlationID=da9f7297-1ece-4043-8e64-70e16839fb93, 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: da9f7297: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2
Result: Received event: da9f7297: 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@5c3fb4e6[correlationID=fa432181-1031-4610-a12f-cf9a6746ad56, 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: fa432181: 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: fa432181: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Step: Wait 1 second.
Result: Received event: fa432181: 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: fa432181: GET_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
Result: Received event: fa432181: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: fa432181: 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@51f1b290[correlationID=fa432181-1031-4610-a12f-cf9a6746ad56, 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: fa432181: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1
Result: Received event: fa432181: 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@16554f2e[correlationID=8e649912-a1ad-460a-863b-2560cbc5d65b, 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: 8e649912: 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: 8e649912: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 8e649912: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: 8e649912: 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@10dad714[correlationID=8e649912-a1ad-460a-863b-2560cbc5d65b, 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: 8e649912: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2
Result: Received event: 8e649912: 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@29862f60[correlationID=b7f55e4d-a379-47a8-ba0d-b2505ebf7d0f, 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: b7f55e4d: 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: b7f55e4d: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: b7f55e4d: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: b7f55e4d: 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@35b1e5e5[correlationID=b7f55e4d-a379-47a8-ba0d-b2505ebf7d0f, 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: b7f55e4d: GET_FILE for file default-test-file.txt: PROGRESS: ContributorID Pillar2, First test progress response message
Step: Send a GetFileFinalResponse.
Result: Received event: b7f55e4d: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2
Result: Received event: b7f55e4d: 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@24f89b6b[correlationID=e7efd756-eeea-4de0-890e-16a3ee23f5d3, 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: e7efd756: 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: e7efd756: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: e7efd756: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: e7efd756: 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@3730fb2f[correlationID=e7efd756-eeea-4de0-890e-16a3ee23f5d3, 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@8d95ac8[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: e7efd756: 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: e7efd756: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1
Result: Received event: e7efd756: 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@236a7f65[correlationID=73d4cdcd-a35d-4668-b14d-e15821b67cc5, 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: 73d4cdcd: GET_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetFile
Step: Wait for 1 seconds
Result: Received event: 73d4cdcd: 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: 73d4cdcd: GET_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor
Result: Received event: 73d4cdcd: GET_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
Result: Received event: 73d4cdcd: 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@1a611ec7[correlationID=df047548-acda-4c47-8e16-42f17ec1d74f, 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: df047548: 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: df047548: 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: df047548: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: df047548: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: df047548: 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@11e1e137[correlationID=df047548-acda-4c47-8e16-42f17ec1d74f, 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: df047548: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2
Result: Received event: df047548: 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@6771c4d8[correlationID=1df78387-a2be-4e25-8ebc-f917e74e0025, 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: 1df78387: 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: 1df78387: 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: 1df78387: 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: 1df78387: 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@119636bf[correlationID=3225c174-8997-4973-b93a-e9bc2c09e0d4, 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: 3225c174: 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: 3225c174: 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: 3225c174: GET_FILE for file ERROR-NO-SUCH-FILE-ERROR: FAILED: , Unable to continue operation, contributors unavailable.
Test success: testNoSuchFileSpecificPillar
Test starting: verifyGetFileClientFromFactory
Test success: verifyGetFileClientFromFactory
Starting testcase GetFileCmdTest
Test starting: defaultSuccessScenarioTest
Description: Tests simplest arguments for running the CmdLineClient
Test success: defaultSuccessScenarioTest
Test starting: missingCollectionArgumentTest
Description: Tests the scenario, where the collection arguments is missing.
Takes the following arguments:
-s The path to the directory with the settings files for the client
-k The path to the file containing the private key.
-v Makes the client more verbose
-c The id for the collection to perform the operation on.
-i The id for the file to perform the operation on.
-p [OPTIONAL] The id of the pillar where the should be performed. If undefined the operations is performed on all pillars.
-l [OPTIONAL] The location where the file should be placed (either total path or directory). If no argument, then in the directory where the script is located.
Missing argument: Missing required option: c
Test success: missingCollectionArgumentTest
Test starting: missingFileIDArgumentTest
Description: Tests the scenario, where no arguments for file id argument is given.
Takes the following arguments:
-s The path to the directory with the settings files for the client
-k The path to the file containing the private key.
-v Makes the client more verbose
-c The id for the collection to perform the operation on.
-i The id for the file to perform the operation on.
-p [OPTIONAL] The id of the pillar where the should be performed. If undefined the operations is performed on all pillars.
-l [OPTIONAL] The location where the file should be placed (either total path or directory). If no argument, then in the directory where the script is located.
Missing argument: Missing required option: i
Test success: missingFileIDArgumentTest
Test starting: specificPillarArgumentTest
Description: Test argument for a specific pillar
Test success: specificPillarArgumentTest
Test starting: unknownPillarArgumentTest
Description: Testing against a non-existing pillar id -> Should fail
Invalid argument: Random1449537577004pillar is not a valid pillar for collection TwoPillarCollection
The collection contains the following pillars: [Pillar1, Pillar2]
Test success: unknownPillarArgumentTest
Starting testcase GetFileIDsCmdTest
Test starting: defaultSuccessScenarioTest
Description: Tests simplest arguments for running the CmdLineClient
Test success: defaultSuccessScenarioTest
Test starting: fileArgumentTest
Description: Tests the argument for a specific file.
Test success: fileArgumentTest
Test starting: missingCollectionArgumentTest
Description: Tests the scenario, where the collection arguments is missing.
Takes the following arguments:
-s The path to the directory with the settings files for the client
-k The path to the file containing the private key.
-v Makes the client more verbose
-c The id for the collection to perform the operation on.
-i The id for the file to perform the operation on.
-p [OPTIONAL] The id of the pillar where the should be performed. If undefined the operations is performed on all pillars.
Missing argument: Missing required option: c
Test success: missingCollectionArgumentTest
Test starting: specificPillarArgumentTest
Description: Test argument for a specific pillar
Test success: specificPillarArgumentTest
Test starting: unknownPillarArgumentTest
Description: Testing against a non-existing pillar id -> Should fail
Invalid argument: Random1449537578039pillar is not a valid pillar for collection TwoPillarCollection
The collection contains the following pillars: [Pillar1, Pillar2]
Test success: unknownPillarArgumentTest
Starting testcase ReplaceFileCmdTest
Test starting: URLSuccessScenarioTest
Description: Tests the scenario, where a URL instead of a file is used for the replacement file.
Test success: URLSuccessScenarioTest
Test starting: bothFileAndURLArgumentTest
Description: Tests the scenario, where both arguments for file or url is given.
Invalid argument: Cannot take both a file (-f) and an URL (-u) as argument.
Test success: bothFileAndURLArgumentTest
Test starting: checksumArgumentNonSaltAlgorithmWitoutSaltTest
Description: Test MD5 checksum without salt -> no failure
Test success: checksumArgumentNonSaltAlgorithmWitoutSaltTest
Test starting: checksumArgumentSaltAlgorithmWithSaltTest
Description: Test HMAC_SHA256 checksum with salt -> No failure
Test success: checksumArgumentSaltAlgorithmWithSaltTest
Test starting: defaultSuccessScenarioTest
Description: Tests simplest arguments for running the CmdLineClient
Test success: defaultSuccessScenarioTest
Test starting: missingChecksumForExistingFileWhenUsingFileArgumentTest
Description: Tests the scenario, where no checksum argument is given, but a File is given.
Invalid argument: Checksum argument (-C) are mandatory for Replace and replace operations as defined in RepositorySettings.
Test success: missingChecksumForExistingFileWhenUsingFileArgumentTest
Test starting: missingChecksumForExistingFileWhenUsingURLArgumentTest
Description: Tests the scenario, where no checksum argument is given, but a URL is given.
Invalid argument: Checksum argument (-C) are mandatory for Replace and replace operations as defined in RepositorySettings.
Test success: missingChecksumForExistingFileWhenUsingURLArgumentTest
Test starting: missingChecksumForNewFileWhenUsingFileArgumentTest
Description: Tests the scenario, where no checksum argument is given, but a File is given.
Test success: missingChecksumForNewFileWhenUsingFileArgumentTest
Test starting: missingChecksumForNewFileWhenUsingURLArgumentTest
Description: Tests the scenario, where no checksum argument is given, but a URL is given.
Invalid argument: The URL argument requires also the checksum argument for the file to replace with (-r).
Test success: missingChecksumForNewFileWhenUsingURLArgumentTest
Test starting: missingCollectionArgumentTest
Description: Tests the scenario, where the collection arguments is missing.
Takes the following arguments:
-s The path to the directory with the settings files for the client
-k The path to the file containing the private key.
-v Makes the client more verbose
-c The id for the collection to perform the operation on.
-i The id for the file to perform the operation on.
-p [OPTIONAL] The id of the pillar where the should be performed. If undefined the operations is performed on all pillars.
-C [OPTIONAL] The checksum of the file to be replaced.
-f The path to the new file for the replacement. Required unless using the URL argument.
-u The URL for the file to be retreived. Is required, unless the actual file is given.
-r The checksum for the file to replace with. Required when using the URL argument.
-R [OPTIONAL] The algorithm of checksum to request in the response from the pillars.
-S [OPTIONAL] The salt of checksum to request in the response. Requires the ChecksumType argument.
-d If this argument is present, then the file will be removed from the server, when the operation is complete.
Missing argument: Missing required option: c
Test success: missingCollectionArgumentTest
Test starting: missingFileIDWhenFileArgumentTest
Description: Tests the scenario, where no checksum argument is given, but a URL is given.
Test success: missingFileIDWhenFileArgumentTest
Test starting: missingFileIDWhenURLArgumentTest
Description: Tests the scenario, where no checksum argument is given, but a URL is given.
Invalid argument: The URL argument requires also the argument for the ID of the file (-i).
Test success: missingFileIDWhenURLArgumentTest
Test starting: missingFileOrURLArgumentTest
Description: Tests the scenario, where no arguments for file or url is given.
Invalid argument: Requires either the file argument (-f) or the URL argument (-u).
Test success: missingFileOrURLArgumentTest
Test starting: missingPillarArgumentTest
Description: Tests the different scenarios, with the pillar argument.
Invalid argument: The pillar argument (-p) must defined for the Replace operation, only single pillar Replaces are allowed
Test success: missingPillarArgumentTest
Test starting: unknownPillarArgumentTest
Step: Testing against a non-existing pillar id
Invalid argument: Random1449537584567pillar is not a valid pillar for collection TwoPillarCollection
The collection contains the following pillars: [Pillar1, Pillar2]
Test success: unknownPillarArgumentTest
Starting testcase ChecksumExtractionUtilsTest
Test starting: testDefaultChecksumSpec
Description: Test that the default checksum is retrieved when no arguments are given.
Test success: testDefaultChecksumSpec
Test starting: testDefaultChecksumSpecWithSaltArgument
Description: Test that the HMAC version of default checksum is retrieved when the salt arguments are given.
Test success: testDefaultChecksumSpecWithSaltArgument
Test starting: testNonSaltChecksumSpecWithSaltArgument
Description: Test that a salt checksum type is retrieved even though a non-salt checksum algorithm it is given as argument, but a salt argument also is given.
Test success: testNonSaltChecksumSpecWithSaltArgument
Test starting: testNonSaltChecksumSpecWithoutSaltArgument
Description: Test that a non-salt checksum type is retrieved when it is given as argument, and no salt arguments are given.
Test success: testNonSaltChecksumSpecWithoutSaltArgument
Test starting: testSaltChecksumSpecWithSaltArgument
Description: Test that a salt checksum type is retrieved when the salt checksum algorithm it is given as argument, and a salt argument also is given.
Test success: testSaltChecksumSpecWithSaltArgument
Test starting: testSaltChecksumSpecWithoutSaltArgument
Description: Test that a non-salt checksum type is retrieved even though a salt checksum algorithm it is given as argument, but no salt argument also is given.
Test success: testSaltChecksumSpecWithoutSaltArgument
Starting testcase GetFileIDsClientComponentTest
Test starting: collectionIDIncludedInEventsTest
Description: Tests the the client provides collectionID in events.
Step: Set a 0.5 second operation timeout.
Step: Start the operation
Stimuli: Calling getFileIDs(null, null, null, org.bitrepository.client.TestEventHandler@66e63575)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@590ac60e[correlationID=65c3e5c2-2fb8-49e7-854a-e21bb8e7ad9b, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=collectionIDIncludedInEventsTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@6a909132[fileID=<null>, allFileIDs=true]]
Result: Received event: 65c3e5c2: GET_FILE_IDS: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs
Step: Send positive responses from the pillar1 and a negative response from pillar2
Result: Received event: 65c3e5c2: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 65c3e5c2: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE
Result: Received event: 65c3e5c2: GET_FILE_IDS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 65c3e5c2: GET_FILE_IDS: REQUEST_SENT: ContributorID [Pillar1], Sending request for get fileIDs
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@7cbeeca7[correlationID=65c3e5c2-2fb8-49e7-854a-e21bb8e7ad9b, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=collectionIDIncludedInEventsTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@12c9fb03[fileID=<null>, allFileIDs=true], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
Step: Wait for 1 second
Result: Received event: 65c3e5c2: GET_FILE_IDS: FAILED: , Failed to receive responses from all contributors before timeout(500ms). Missing contributors [Pillar1]
Test success: collectionIDIncludedInEventsTest
Test starting: conversationTimeoutTest
Description: Tests the the client handles lack of IdentifyPillarResponses gracefully
Step: Set a 100 ms ConversationTimeout.
Step: Start the operation
Stimuli: Calling getFileIDs(null, null, null, org.bitrepository.client.TestEventHandler@66e63575)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@483c6cc[correlationID=466f08b2-6741-4d27-93fd-131208b9244d, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=conversationTimeoutTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@6faab2bd[fileID=<null>, allFileIDs=true]]
Result: Received event: 466f08b2: GET_FILE_IDS: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs
02:19:47.296 WARN o.b.c.c.m.CollectionBasedConversationMediator - Failing timed out conversation 466f08b2-6741-4d27-93fd-131208b9244d (Age 1000ms)
Result: Received event: 466f08b2: GET_FILE_IDS: FAILED: , Failing timed out conversation 466f08b2-6741-4d27-93fd-131208b9244d
Test success: conversationTimeoutTest
Test starting: identificationFailureTest
Description: Verify that the client works correctly when a contributor sends a failure response.
Step: Start the operation.
Stimuli: Calling getFileIDs(null, null, null, org.bitrepository.client.TestEventHandler@66e63575)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@985b9f6[correlationID=1b5402b4-9b4b-47cf-b045-4cf81f75a4a0, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=identificationFailureTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@407691d1[fileID=<null>, allFileIDs=true]]
Result: Received event: 1b5402b4: GET_FILE_IDS: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs
Step: Send a identification response from contributor1 with a FAILURE response code.
Result: Received event: 1b5402b4: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE
Step: Send a identification response from contributor2 with a IDENTIFICATION_POSITIVE response code .
Result: Received event: 1b5402b4: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 1b5402b4: GET_FILE_IDS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: 1b5402b4: GET_FILE_IDS: REQUEST_SENT: ContributorID [Pillar2], Sending request for get fileIDs
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@ca69671[correlationID=1b5402b4-9b4b-47cf-b045-4cf81f75a4a0, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=identificationFailureTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@28c8c41a[fileID=<null>, allFileIDs=true], 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: 1b5402b4: GET_FILE_IDS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false
Result: Received event: 1b5402b4: GET_FILE_IDS: FAILED: , Failed operation. Cause(s):
[1b5402b4: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE]
Test success: identificationFailureTest
Test starting: identificationNegativeTest
Description: Verify that the client works correctly when a contributor sends a negative response.
Step: Start the operation.
Stimuli: Calling getFileIDs(null, null, null, org.bitrepository.client.TestEventHandler@66e63575)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@6ab00916[correlationID=34ad2c65-62c4-4b04-95fe-eb60205bdc1e, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=identificationNegativeTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@2f739d9a[fileID=<null>, allFileIDs=true]]
Result: Received event: 34ad2c65: GET_FILE_IDS: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs
Step: Send a identification response from contributor1 with a IDENTIFICATION_NEGATIVE response code .
Result: Received event: 34ad2c65: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: IDENTIFICATION_NEGATIVE
Step: Send a identification response from contributor2 with a IDENTIFICATION_POSITIVE response code .
Result: Received event: 34ad2c65: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 34ad2c65: GET_FILE_IDS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: 34ad2c65: GET_FILE_IDS: REQUEST_SENT: ContributorID [Pillar2], Sending request for get fileIDs
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@253417d7[correlationID=34ad2c65-62c4-4b04-95fe-eb60205bdc1e, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=identificationNegativeTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@4f2642de[fileID=<null>, allFileIDs=true], 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: 34ad2c65: GET_FILE_IDS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false
Result: Received event: 34ad2c65: GET_FILE_IDS: FAILED: , Failed operation. Cause(s):
[34ad2c65: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: IDENTIFICATION_NEGATIVE]
Test success: identificationNegativeTest
Test starting: noContributorsRespondingTest
Description: Tests the the client handles lack of a IdentifyResponse gracefully. More concrete this means that the occurrence of a identification timeout should be handled correctly
Step: Set a 100 ms timeout for identifying contributors.
Step: Start the operation.
Stimuli: Calling getFileIDs(null, null, null, org.bitrepository.client.TestEventHandler@66e63575)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@223788ba[correlationID=12322453-39d4-4ed4-9145-367993eab027, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=noContributorsRespondingTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@3b80ca33[fileID=<null>, allFileIDs=true]]
Result: Received event: 12322453: GET_FILE_IDS: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs
Step: Wait for 1 second
Result: Received event: 12322453: GET_FILE_IDS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar1, Pillar2]
Result: Received event: 12322453: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor
Result: Received event: 12322453: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
Result: Received event: 12322453: GET_FILE_IDS: FAILED: , Unable to continue operation, contributors unavailable.
Test success: noContributorsRespondingTest
Result: The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@223788ba[correlationID=12322453-39d4-4ed4-9145-367993eab027, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=noContributorsRespondingTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@3b80ca33[fileID=<null>, allFileIDs=true]]
02:19:50.236 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@223788ba[correlationID=12322453-39d4-4ed4-9145-367993eab027, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=noContributorsRespondingTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@3b80ca33[fileID=<null>, allFileIDs=true]]
Test starting: oneContributorNotRespondingTest
Description: Verify that the client works correct without receiving identification responses from all contributors.
Added fixture: Set the a identification timeout to 100 ms.
Step: Start the operation.
Stimuli: Calling getFileIDs(null, null, null, org.bitrepository.client.TestEventHandler@66e63575)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@4eb7f0bb[correlationID=dffbd848-ff7a-484d-83f7-4b95c4087aa9, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=oneContributorNotRespondingTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@5b1b01e6[fileID=<null>, allFileIDs=true]]
Result: Received event: dffbd848: GET_FILE_IDS: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs
Step: Send a identification response from contributor1.
Result: Received event: dffbd848: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Step: Wait 1 second.
Result: Received event: dffbd848: GET_FILE_IDS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar2]
Result: Received event: dffbd848: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
Result: Received event: dffbd848: GET_FILE_IDS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: dffbd848: GET_FILE_IDS: REQUEST_SENT: ContributorID [Pillar1], Sending request for get fileIDs
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@fcdce6d[correlationID=dffbd848-ff7a-484d-83f7-4b95c4087aa9, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=oneContributorNotRespondingTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@296f14b4[fileID=<null>, allFileIDs=true], 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: dffbd848: GET_FILE_IDS: COMPONENT_COMPLETE: ContributorID Pillar1, PartialResult=false
Result: Received event: dffbd848: GET_FILE_IDS: FAILED: , Failed operation. Cause(s):
[dffbd848: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor]
Test success: oneContributorNotRespondingTest
Test starting: operationTimeoutTest
Description: Tests the the client handles lack of final responses gracefully.
Step: Set a 100 ms operation timeout.
Step: Start the operation
Stimuli: Calling getFileIDs(null, null, null, org.bitrepository.client.TestEventHandler@66e63575)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@59e1b2e4[correlationID=800cbb48-2c8f-48e0-a593-61c85ef19d33, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=operationTimeoutTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@67c784a6[fileID=<null>, allFileIDs=true]]
Result: Received event: 800cbb48: GET_FILE_IDS: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs
Step: Send positive responses from the pillar1 and a negative response from pillar2
Result: Received event: 800cbb48: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 800cbb48: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE
Result: Received event: 800cbb48: GET_FILE_IDS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 800cbb48: GET_FILE_IDS: REQUEST_SENT: ContributorID [Pillar1], Sending request for get fileIDs
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@4ca2e82d[correlationID=800cbb48-2c8f-48e0-a593-61c85ef19d33, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=operationTimeoutTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@188015cf[fileID=<null>, allFileIDs=true], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
Step: Wait for 1 second
Result: Received event: 800cbb48: GET_FILE_IDS: FAILED: , Failed to receive responses from all contributors before timeout(100ms). Missing contributors [Pillar1]
Test success: operationTimeoutTest
Test starting: getFileIDsDeliveredAtUrl
Description: Tests the delivery of fileIDs from a pillar at a given URL.
Step: Initialise the variables for this test.
Step: Request the delivery of the file ids of a file from the pillar(s). A callback listener should be supplied.
Stimuli: Calling getFileIDs(null, default-test-file.txt, file:../bitrepository-core/src/test/resources/test-files//TEST-FILE-IDS-DELIVERY.xml, org.bitrepository.client.TestEventHandler@66e63575)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@179a0d61[correlationID=57116cdd-6ee7-4580-9fb5-4485ac0ec48b, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=getFileIDsDeliveredAtUrl, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@56597d82[fileID=default-test-file.txt, allFileIDs=<null>]]
Result: Received event: 57116cdd: GET_FILE_IDS for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs
Step: The pillar sends a response to the identify message.
Result: Received event: 57116cdd: GET_FILE_IDS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 57116cdd: GET_FILE_IDS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 57116cdd: GET_FILE_IDS for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for get fileIDs
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@58bb4b69[correlationID=57116cdd-6ee7-4580-9fb5-4485ac0ec48b, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=getFileIDsDeliveredAtUrl, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@1f0db41a[fileID=default-test-file.txt, allFileIDs=<null>], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=file:../bitrepository-core/src/test/resources/test-files//TEST-FILE-IDS-DELIVERY.xml-Pillar1]
Step: The pillar sends a getFileIDsProgressResponse to the GetFileIDsClient.
Result: Received event: 57116cdd: GET_FILE_IDS for file default-test-file.txt: PROGRESS: ContributorID Pillar1, First test progress response message
Step: The resulting file is uploaded to the indicated url and the pillar sends a final response upload message
Result: Received event: 57116cdd: GET_FILE_IDS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, PartialResult=false
Result: Received event: 57116cdd: GET_FILE_IDS for file default-test-file.txt: COMPLETE:
Step: Receive and validate event results for the pillar.
Test success: getFileIDsDeliveredAtUrl
Test starting: getFileIDsDeliveredThroughMessage
Description: Tests the delivery of fileIDs from a pillar at a given URL.
Step: Initialise the variables for this test.
Step: Ensure the delivery file isn't already present on the http server
Step: Request the delivery of the file ids of a file from the pillar(s). A callback listener should be supplied.
Stimuli: Calling getFileIDs(null, default-test-file.txt, null, org.bitrepository.client.TestEventHandler@66e63575)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@4f24edf9[correlationID=0e83b7ac-ce8f-4329-b56b-98a56bb6882b, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=getFileIDsDeliveredThroughMessage, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@add929e[fileID=default-test-file.txt, allFileIDs=<null>]]
Result: Received event: 0e83b7ac: GET_FILE_IDS for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs
Step: The pillar sends a response to the identify message.
Result: Received event: 0e83b7ac: GET_FILE_IDS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 0e83b7ac: GET_FILE_IDS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 0e83b7ac: GET_FILE_IDS for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for get fileIDs
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@700cb93f[correlationID=0e83b7ac-ce8f-4329-b56b-98a56bb6882b, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=getFileIDsDeliveredThroughMessage, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@18afc9e2[fileID=default-test-file.txt, allFileIDs=<null>], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
Step: The pillar sends a getFileIDsProgressResponse to the GetFileIDsClient.
Result: Received event: 0e83b7ac: GET_FILE_IDS for file default-test-file.txt: PROGRESS: ContributorID Pillar1, First test progress response message
Step: The resulting file is uploaded to the indicated url and the pillar sends a final response upload message
Result: Received event: 0e83b7ac: GET_FILE_IDS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, NumberOfFileIDs=1, PartialResult=false
Result: Received event: 0e83b7ac: GET_FILE_IDS for file default-test-file.txt: COMPLETE:
Step: Receive and validate event results for the pillar.
Test success: getFileIDsDeliveredThroughMessage
Test starting: getFileIDsFromOtherCollection
Description: Tests the getFileIDs client will correctly try to get from a second collection if required
Added fixture: Configure collection1 to contain both pillars and collection 2 to only contain pillar2
Step: Request the putting of a file through the PutClient for collection2
Stimuli: Calling getFileIDs(null, default-test-file.txt, null, org.bitrepository.client.TestEventHandler@571cb7bc)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@23fe64a0[correlationID=a470ed07-0ea5-4670-a308-82ccb6fddc09, collectionID=SinglePillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=getFileIDsFromOtherCollection, to=Pillar2, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@66019544[fileID=default-test-file.txt, allFileIDs=<null>]]
Result: Received event: a470ed07: GET_FILE_IDS for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs
Step: Send an identification response from pillar2.
Result: Received event: a470ed07: GET_FILE_IDS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: a470ed07: GET_FILE_IDS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: a470ed07: GET_FILE_IDS for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar2], Sending request for get fileIDs
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@68ebe2e6[correlationID=a470ed07-0ea5-4670-a308-82ccb6fddc09, collectionID=SinglePillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=getFileIDsFromOtherCollection, to=Pillar2, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@38e0403f[fileID=default-test-file.txt, allFileIDs=<null>], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
Step: Send a complete event from the pillar
Result: Received event: a470ed07: GET_FILE_IDS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false
Result: Received event: a470ed07: GET_FILE_IDS for file default-test-file.txt: COMPLETE:
Test success: getFileIDsFromOtherCollection
Test starting: testNoSuchFile
Description: Testing how a request for a non-existing file is handled.
Step: Setting up variables and such.
Step: Request the delivery of the file id of a file from the pillar(s). A callback listener should be supplied.
Stimuli: Calling getFileIDs(null, default-test-file.txt, file:../bitrepository-core/src/test/resources/test-files//TEST-FILE-IDS-DELIVERY.xml, org.bitrepository.client.TestEventHandler@66e63575)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@429c9245[correlationID=8513ad8e-5b82-4443-aeb2-345c06d904ba, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=testNoSuchFile, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@785bb7e9[fileID=default-test-file.txt, allFileIDs=<null>]]
Result: Received event: 8513ad8e: GET_FILE_IDS for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs
Step: The pillar sends a response to the identify message.
Result: Received event: 8513ad8e: GET_FILE_IDS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 8513ad8e: GET_FILE_IDS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 8513ad8e: GET_FILE_IDS for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for get fileIDs
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@43d22b4[correlationID=8513ad8e-5b82-4443-aeb2-345c06d904ba, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=testNoSuchFile, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@221586cc[fileID=default-test-file.txt, allFileIDs=<null>], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=file:../bitrepository-core/src/test/resources/test-files//TEST-FILE-IDS-DELIVERY.xml-Pillar1]
Step: Send a error that the file cannot be found.
Result: Received event: 8513ad8e: GET_FILE_IDS for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FILE_NOT_FOUND_FAILURE, No such file.
Result: Received event: 8513ad8e: GET_FILE_IDS for file default-test-file.txt: FAILED: , Failed operation. Cause(s):
[8513ad8e: GET_FILE_IDS for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FILE_NOT_FOUND_FAILURE, No such file.]
Test success: testNoSuchFile
Test starting: testPaging
Description: Tests the GetFileIDs client correctly handles functionality for limiting results, either by timestamp or result count.
Step: Request fileIDs from with MinTimestamp, MaxTimestamp, MaxNumberOfResults set for both pillars .
Stimuli: Calling getFileIDs([ContributorQuery{componentID='Pillar1, minTimestamp=Tue Dec 08 02:19:50 CET 2015, maxTimestamp=Tue Dec 08 02:19:51 CET 2015, maxNumberOfResults=1}, ContributorQuery{componentID='Pillar2, minTimestamp=Tue Dec 08 02:19:51 CET 2015, maxTimestamp=Tue Dec 08 02:19:51 CET 2015, maxNumberOfResults=2}], null, null, org.bitrepository.client.TestEventHandler@66e63575)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@55d658d7[correlationID=033eb785-7b45-4921-9500-f0d4f2ad6cb9, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=testPaging, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@3b3f87ae[fileID=<null>, allFileIDs=true]]
Result: Received event: 033eb785: GET_FILE_IDS: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs
Step: Send a IdentifyPillarsForGetFileIDsResponse from both pillars.
Result: Received event: 033eb785: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 033eb785: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 033eb785: GET_FILE_IDS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2, Pillar1]
Result: Received event: 033eb785: GET_FILE_IDS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for get fileIDs
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@335be13c[correlationID=033eb785-7b45-4921-9500-f0d4f2ad6cb9, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=testPaging, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@749e120e[fileID=<null>, allFileIDs=true], minTimestamp=2015-12-08T02:19:50.754+01:00, maxTimestamp=2015-12-08T02:19:51.654+01:00, maxNumberOfResults=1, resultAddress=<null>]
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@5a253cca[correlationID=033eb785-7b45-4921-9500-f0d4f2ad6cb9, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=testPaging, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@6e613ceb[fileID=<null>, allFileIDs=true], minTimestamp=2015-12-08T02:19:51.654+01:00, maxTimestamp=2015-12-08T02:19:51.754+01:00, maxNumberOfResults=2, resultAddress=<null>]
Test success: testPaging
Test starting: verifyGetFileIDsClientFromFactory
Test success: verifyGetFileIDsClientFromFactory
Starting testcase PutFileClientComponentTest
Test starting: defaultReturnChecksumsWithChecksumPillar
Description: Tests that PutClient handles the presence of a ChecksumPillar correctly, when a return checksum of default type is requested (which a checksum pillar can provide).
Step: Call putFile while requesting a salted checksum to be returned.
Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@691eec36[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], org.bitrepository.client.TestEventHandler@7d2459aa, TEST-AUDIT-TRAIL)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@22f791db[correlationID=0543a31f-802b-4f6f-945b-7a58c2ffb316, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=defaultReturnChecksumsWithChecksumPillar, to=<null>, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, fileID=default-test-file.txt, fileSize=0]
Result: Received event: 0543a31f: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file
Step: Send an identification response with a PillarChecksumSpec element set, indicating that this is a checksum pillar.
Result: Received event: 0543a31f: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Step: Send an normal identification response from pillar2.
Result: Received event: 0543a31f: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 0543a31f: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2]
Result: Received event: 0543a31f: PUT_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for put file
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@76dac40e[correlationID=0543a31f-802b-4f6f-945b-7a58c2ffb316, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=defaultReturnChecksumsWithChecksumPillar, to=<null>, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>, checksumRequestForNewFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@691eec36[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>]]
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@619e86dc[correlationID=0543a31f-802b-4f6f-945b-7a58c2ffb316, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=defaultReturnChecksumsWithChecksumPillar, to=<null>, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, pillarID=Pillar2, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>, checksumRequestForNewFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@691eec36[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>]]
Test success: defaultReturnChecksumsWithChecksumPillar
Test starting: fileExistsOnPillarChecksumFromPillarNoClientChecksum
Description: Tests that PutClient handles the presence of a file correctly, when the pillar returns a checksum but the putFile was called without a checksum.
Step: Call putFile.
Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, null, org.bitrepository.client.TestEventHandler@5e1d77de, TEST-AUDIT-TRAIL)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@6549398[correlationID=d3865966-5ef9-4269-a41e-c53211b13cca, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=fileExistsOnPillarChecksumFromPillarNoClientChecksum, to=<null>, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, fileID=default-test-file.txt, fileSize=0]
Result: Received event: d3865966: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file
Step: Send a DUPLICATE_FILE_FAILURE response with a random checksum.
Result: Received event: d3865966: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: DUPLICATE_FILE_FAILURE, Received negative response from component Pillar1: org.bitrepository.bitrepositoryelements.ResponseInfo@1de66441[responseCode=DUPLICATE_FILE_FAILURE, responseText=Testing the handling of 'DUPLICATE FILE' identification.] (existing file checksum does not match)
Result: Received event: d3865966: PUT_FILE for file default-test-file.txt: FAILED: , Can not put file default-test-file.txt, as an different file already exists on pillar Pillar1
Test success: fileExistsOnPillarChecksumFromPillarNoClientChecksum
Test starting: fileExistsOnPillarDifferentChecksumFromPillar
Description: Tests that PutClient handles the presence of a file correctly, when the pillar returns a checksum different from the file being put.
Step: Call putFile.
Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@c87bf1e[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2118d522[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={-70}, calculationTimestamp=2015-12-08T02:19:52.150+01:00], null, org.bitrepository.client.TestEventHandler@2cbfc87f, TEST-AUDIT-TRAIL)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@6b600259[correlationID=9682f13a-9899-40dc-9b0e-7d6b69a0c7f5, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=fileExistsOnPillarDifferentChecksumFromPillar, to=<null>, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, fileID=default-test-file.txt, fileSize=0]
Result: Received event: 9682f13a: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file
Step: Send a DUPLICATE_FILE_FAILURE response with a random checksum.
Result: Received event: 9682f13a: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: DUPLICATE_FILE_FAILURE, Received negative response from component Pillar1: org.bitrepository.bitrepositoryelements.ResponseInfo@6f568b26[responseCode=DUPLICATE_FILE_FAILURE, responseText=Testing the handling of 'DUPLICATE FILE' identification.] (existing file checksum does not match)
Result: Received event: 9682f13a: PUT_FILE for file default-test-file.txt: FAILED: , Can not put file default-test-file.txt, as an different file already exists on pillar Pillar1
Test success: fileExistsOnPillarDifferentChecksumFromPillar
Test starting: fileExistsOnPillarNoChecksumFromPillar
Description: Tests that PutClient handles the presence of a file correctly, when the pillar doesn't return a checksum in the identification response.
Step: Call putFile.
Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, null, org.bitrepository.client.TestEventHandler@38babc22, TEST-AUDIT-TRAIL)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@46e9a4f6[correlationID=7836ffba-582e-4cae-87ff-0a384f9d9cf5, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=fileExistsOnPillarNoChecksumFromPillar, to=<null>, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, fileID=default-test-file.txt, fileSize=0]
Result: Received event: 7836ffba: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file
Step: Send a DUPLICATE_FILE_FAILURE response without a checksum.
Result: Received event: 7836ffba: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: DUPLICATE_FILE_FAILURE, Received negative response from component Pillar1: org.bitrepository.bitrepositoryelements.ResponseInfo@1457fcc7[responseCode=DUPLICATE_FILE_FAILURE, responseText=Testing the handling of 'DUPLICATE FILE' identification.]
Result: Received event: 7836ffba: PUT_FILE for file default-test-file.txt: FAILED: , Can not put file default-test-file.txt, as an file already exists on pillar Pillar1
Test success: fileExistsOnPillarNoChecksumFromPillar
Test starting: noPillarsResponding
Description: Tests the handling of missing identification responses from all pillar
Added fixture: Sets the identification timeout to 100 ms.
Step: Request the putting of a file through the PutClient
Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, null, org.bitrepository.client.TestEventHandler@e1d21f5, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@75e8d6b0[correlationID=f98a55f7-b53b-4492-b8ff-d5561718ed84, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=noPillarsResponding, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt, fileSize=0]
Result: Received event: f98a55f7: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file
Step: Do not respond. Just await the timeout.
Result: Received event: f98a55f7: PUT_FILE for file default-test-file.txt: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar1, Pillar2]
Result: Received event: f98a55f7: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor
Result: Received event: f98a55f7: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
Result: Received event: f98a55f7: PUT_FILE for file default-test-file.txt: FAILED: , Unable to continue operation, contributors unavailable.
Test success: noPillarsResponding
Test starting: noReturnChecksumsWithChecksumPillar
Description: Tests that PutClient handles the presence of a ChecksumPillar correctly, when no return checksum is requested.
Step: Call putFile while requesting a salted checksum to be returned.
Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, null, org.bitrepository.client.TestEventHandler@513028e3, TEST-AUDIT-TRAIL)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@595ed648[correlationID=2dd5ff6a-90b1-4c28-9cec-1a62b0deed53, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=noReturnChecksumsWithChecksumPillar, to=<null>, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, fileID=default-test-file.txt, fileSize=0]
Result: Received event: 2dd5ff6a: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file
Step: Send an identification response with a PillarChecksumSpec element set, indicating that this is a checksum pillar.
Result: Received event: 2dd5ff6a: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Step: Send an normal identification response from pillar2.
Result: Received event: 2dd5ff6a: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 2dd5ff6a: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2]
Result: Received event: 2dd5ff6a: PUT_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for put file
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@7a970713[correlationID=2dd5ff6a-90b1-4c28-9cec-1a62b0deed53, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=noReturnChecksumsWithChecksumPillar, to=<null>, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>, checksumRequestForNewFile=<null>]
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@55d4729f[correlationID=2dd5ff6a-90b1-4c28-9cec-1a62b0deed53, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=noReturnChecksumsWithChecksumPillar, to=<null>, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, pillarID=Pillar2, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>, checksumRequestForNewFile=<null>]
Test success: noReturnChecksumsWithChecksumPillar
Test starting: normalPutFile
Description: Tests the PutClient. Makes a whole conversation for the put client for a 'good' scenario.
Added fixture: Initialise the number of pillars to one
Step: Ensure that the test-file is placed on the HTTP server.
Step: Request the delivery of a file from a specific pillar. A callback listener should be supplied.
Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, null, org.bitrepository.client.TestEventHandler@2aaa0bf1, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@788bc15b[correlationID=d72bcb50-7ce0-4796-8ddf-879255c1ed18, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=normalPutFile, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt, fileSize=0]
Result: Received event: d72bcb50: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file
Step: Make response for the pillar.
Result: Received event: d72bcb50: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: d72bcb50: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: d72bcb50: PUT_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for put file
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@5587af1[correlationID=d72bcb50-7ce0-4796-8ddf-879255c1ed18, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=normalPutFile, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>, checksumRequestForNewFile=<null>]
Step: Validate the steps of the PutClient by going through the events.
Step: The pillar sends a progress response to the PutClient.
Result: Received event: d72bcb50: PUT_FILE for file default-test-file.txt: PROGRESS: ContributorID Pillar1, First test progress response message
Step: Send a final response message to the PutClient.
Result: Received event: d72bcb50: PUT_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, requestedChecksumResult=null
Result: Received event: d72bcb50: PUT_FILE for file default-test-file.txt: COMPLETE:
Test success: normalPutFile
Test starting: onePillarPutRetryFailure
Reference: <a href=https://sbforge.org/jira/browse/BITMAG-810>BITMAG-810 Reference client should be able to retry failed file transfers</a>
Description: Tests that a putfile attempt failing due to FILE_TRANSFER_FAILURE is only attempted the maximum allowed attempts
Added fixture: Sets the identification timeout to 3 sec, allow two retries and only register one pillar.
Step: Request the putting of a file through the PutClient
Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, null, org.bitrepository.client.TestEventHandler@1b02763b, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@5b021360[correlationID=069d4557-5b2e-4ab1-9497-f318afa1788c, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarPutRetryFailure, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt, fileSize=0]
Result: Received event: 069d4557: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file
Step: Send an identification response from the one pillar.
Result: Received event: 069d4557: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 069d4557: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 069d4557: PUT_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for put file
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@67d215a9[correlationID=069d4557-5b2e-4ab1-9497-f318afa1788c, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarPutRetryFailure, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>, checksumRequestForNewFile=<null>]
Step: The client should proceed to send a putFileOperation request to the responding pillar.
Step: Send a PutFileFinalResponse indicating a FILE_TRANSFER_FAILURE
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@6fe914c6[correlationID=069d4557-5b2e-4ab1-9497-f318afa1788c, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarPutRetryFailure, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>, checksumRequestForNewFile=<null>]
Result: Received event: 069d4557: PUT_FILE for file default-test-file.txt: WARNING: ContributorID Pillar1, Retrying putfile (attempt number 2)
Step: Send a PutFileFinalResponse indicating a FILE_TRANSFER_FAILURE for the second put attempt
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@24bb9348[correlationID=069d4557-5b2e-4ab1-9497-f318afa1788c, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarPutRetryFailure, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>, checksumRequestForNewFile=<null>]
Result: Received event: 069d4557: PUT_FILE for file default-test-file.txt: WARNING: ContributorID Pillar1, Retrying putfile (attempt number 3)
Step: Send a PutFileFinalResponse indicating a FILE_TRANSFER_FAILURE for the third put attempt
Result: Received event: 069d4557: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FILE_TRANSFER_FAILURE
Result: Received event: 069d4557: PUT_FILE for file default-test-file.txt: FAILED: , Failed operation. Cause(s):
[069d4557: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FILE_TRANSFER_FAILURE]
Test success: onePillarPutRetryFailure
Test starting: onePillarPutRetrySuccess
Reference: <a href=https://sbforge.org/jira/browse/BITMAG-810>BITMAG-810 Reference client should be able to retry failed file transfers</a>
Description: Tests the handling of a failed transmission when retry is allowed
Added fixture: Sets the identification timeout to 3 sec, allow two retries and only register one pillar.
Step: Request the putting of a file through the PutClient
Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, null, org.bitrepository.client.TestEventHandler@16f0f9b1, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@4a3d432b[correlationID=161b68be-7d81-4d59-9c18-565709f2226d, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarPutRetrySuccess, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt, fileSize=0]
Result: Received event: 161b68be: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file
Step: Send an identification response from the one pillar.
Result: Received event: 161b68be: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 161b68be: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 161b68be: PUT_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for put file
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@530ca3e4[correlationID=161b68be-7d81-4d59-9c18-565709f2226d, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarPutRetrySuccess, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>, checksumRequestForNewFile=<null>]
Step: The client should proceed to send a putFileOperation request to the responding pillar.
Step: Send a PutFileFinalResponse indicating a FILE_TRANSFER_FAILURE
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@4220e545[correlationID=161b68be-7d81-4d59-9c18-565709f2226d, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarPutRetrySuccess, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>, checksumRequestForNewFile=<null>]
Result: Received event: 161b68be: PUT_FILE for file default-test-file.txt: WARNING: ContributorID Pillar1, Retrying putfile (attempt number 2)
Step: A new PutFileRequest is send, pillar responds with success
Result: Received event: 161b68be: PUT_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, requestedChecksumResult=null
Result: Received event: 161b68be: PUT_FILE for file default-test-file.txt: COMPLETE:
Test success: onePillarPutRetrySuccess
Test starting: onePillarRespondingWithPartialPutAllowed
Reference: <a href=https://sbforge.org/jira/browse/BITMAG-598>BITMAG-598 It should be possible to putFiles, even though only a subset of the pillars are available</a>
Description: Tests the handling of missing identification responses from one pillar, when partial put are allowed
Added fixture: Sets the identification timeout to 100 ms and allow partial puts.
Step: Request the putting of a file through the PutClient
Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, null, org.bitrepository.client.TestEventHandler@665ddc01, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@659aec43[correlationID=0b31db46-c84c-4754-8b7b-f778a3c79fa0, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarRespondingWithPartialPutAllowed, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt, fileSize=0]
Result: Received event: 0b31db46: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file
Step: Only send an identification response from one pillar.
Result: Received event: 0b31db46: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Step: Await the timeout.
Result: Received event: 0b31db46: PUT_FILE for file default-test-file.txt: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar2]
Result: Received event: 0b31db46: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
Result: Received event: 0b31db46: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 0b31db46: PUT_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for put file
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@5e96c9b3[correlationID=0b31db46-c84c-4754-8b7b-f778a3c79fa0, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarRespondingWithPartialPutAllowed, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>, checksumRequestForNewFile=<null>]
Step: The client should proceed to send a putFileOperation request to the responding pillar.
Step: Send a pillar complete event
Result: Received event: 0b31db46: PUT_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, requestedChecksumResult=null
Result: Received event: 0b31db46: PUT_FILE for file default-test-file.txt: FAILED: , Failed operation. Cause(s):
[0b31db46: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor]
Test success: onePillarRespondingWithPartialPutAllowed
Test starting: onePillarRespondingWithPartialPutDisallowed
Description: Tests the handling of missing identification responses from one pillar, when partial put are allowed
Added fixture: Sets the identification timeout to 100 ms and disallow partial puts.
Step: Request the putting of a file through the PutClient
Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, null, org.bitrepository.client.TestEventHandler@11c0f55c, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@33b7016c[correlationID=09d05ae6-ef7d-45a2-ae1e-d34b5e80f7d9, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarRespondingWithPartialPutDisallowed, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt, fileSize=0]
Result: Received event: 09d05ae6: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file
Step: Only send an identification response from one pillar.
Result: Received event: 09d05ae6: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Step: Await the timeout.
Result: Received event: 09d05ae6: PUT_FILE for file default-test-file.txt: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar2]
Result: Received event: 09d05ae6: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
Result: Received event: 09d05ae6: PUT_FILE for file default-test-file.txt: FAILED: , Unable to continue operation, contributors unavailable.
Test success: onePillarRespondingWithPartialPutDisallowed
Test starting: putClientOperationTimeout
Description: Tests the handling of a failed operation for the PutClient
Step: Initialise the number of pillars and the PutClient. Sets the operation timeout to 100 ms.
Step: Request the putting of a file through the PutClient
Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, null, org.bitrepository.client.TestEventHandler@7c0e7a, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@2c128268[correlationID=5e7f6261-832b-44cc-95fa-1b5c3871bce2, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=putClientOperationTimeout, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt, fileSize=0]
Result: Received event: 5e7f6261: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file
Step: Make response for the pillar.
Result: Received event: 5e7f6261: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 5e7f6261: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 5e7f6261: PUT_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for put file
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@60ef851e[correlationID=5e7f6261-832b-44cc-95fa-1b5c3871bce2, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=putClientOperationTimeout, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>, checksumRequestForNewFile=<null>]
Step: Validate the steps of the PutClient by going through the events.
Step: Do not respond. Just await the timeout.
Result: Received event: 5e7f6261: PUT_FILE for file default-test-file.txt: FAILED: , Failed to receive responses from all contributors before timeout(100ms). Missing contributors [Pillar1]
Test success: putClientOperationTimeout
Test starting: putClientPillarOperationFailed
Description: Tests the handling of a operation failure for the PutClient.
Step: Initialise the number of pillars to one
Step: Ensure that the test-file is placed on the HTTP server.
Step: Request the delivery of a file from a specific pillar. A callback listener should be supplied.
Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, null, org.bitrepository.client.TestEventHandler@123a52d3, TEST-AUDIT-TRAIL)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@42cdaea2[correlationID=abd789dc-d89a-4b19-84d6-80db950dab9c, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=putClientPillarOperationFailed, to=Pillar1, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, fileID=default-test-file.txt, fileSize=0]
Result: Received event: abd789dc: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file
Step: Send pillar response.
Result: Received event: abd789dc: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: abd789dc: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: abd789dc: PUT_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for put file
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@1e94fe1d[correlationID=abd789dc-d89a-4b19-84d6-80db950dab9c, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=putClientPillarOperationFailed, to=Pillar1, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>, checksumRequestForNewFile=<null>]
Step: Validate the steps of the PutClient by going through the events.
Step: Send a failed response message to the PutClient.
Result: Received event: abd789dc: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE, Verifying that a failure can be understood!
Result: Received event: abd789dc: PUT_FILE for file default-test-file.txt: FAILED: , Failed operation. Cause(s):
[abd789dc: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE, Verifying that a failure can be understood!]
Test success: putClientPillarOperationFailed
Test starting: putToOtherCollection
Reference: <a href=https://sbforge.org/jira/browse/BITMAG-925>BITMAG-925 Client will always try to put to the pillars defined in the first collection</a>
Description: Tests the putFIle client will correctly try to put to a second collection if required
Added fixture: Sets the identification timeout to 3 sec, allow two retries and only register one pillar.
Added fixture: Configure collection1 to contain both pillars and collection 2 to only contain pillar2
Step: Request the putting of a file through the PutClient for collection2
Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, null, org.bitrepository.client.TestEventHandler@340c7419, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@24ec7ab7[correlationID=d25ad091-57b4-4b84-8b88-b1389c7e9b11, collectionID=SinglePillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=putToOtherCollection, to=Pillar2, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt, fileSize=0]
Result: Received event: d25ad091: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file
Step: Send an identification response from pillar2.
Result: Received event: d25ad091: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: d25ad091: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: d25ad091: PUT_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar2], Sending request for put file
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@de42c9e[correlationID=d25ad091-57b4-4b84-8b88-b1389c7e9b11, collectionID=SinglePillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=putToOtherCollection, to=Pillar2, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar2, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>, checksumRequestForNewFile=<null>]
Step: Send a put complete event from the pillar
Result: Received event: d25ad091: PUT_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2, requestedChecksumResult=null
Result: Received event: d25ad091: PUT_FILE for file default-test-file.txt: COMPLETE:
Test success: putToOtherCollection
Test starting: saltedReturnChecksumsWithChecksumPillar
Description: Tests that PutClient handles the presence of a ChecksumPillar correctly, when a salted return checksum (which a checksum pillar can't provide) is requested.
Reference: <a href="https://sbforge.org/jira/browse/BITMAG-677">BITMAG-677put, replace and delete clients fails if return checksums are requested and a checksumpillar is involved</a>
Step: Call putFile while requesting a salted checksum to be returned.
Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@5632152e[checksumType=HMAC_MD5, checksumSalt={-86}, otherChecksumType=<null>], org.bitrepository.client.TestEventHandler@64845cb6, TEST-AUDIT-TRAIL)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@7abe286[correlationID=5e266fbf-8d9f-4e08-9e47-ace2491169ef, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=saltedReturnChecksumsWithChecksumPillar, to=<null>, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, fileID=default-test-file.txt, fileSize=0]
Result: Received event: 5e266fbf: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file
Step: Send an identification response with a PillarChecksumSpec element set, indicating that this is a checksum pillar.
Result: Received event: 5e266fbf: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Step: Send an normal identification response from pillar2.
Result: Received event: 5e266fbf: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 5e266fbf: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2]
Result: Received event: 5e266fbf: PUT_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for put file
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@69c86e4b[correlationID=5e266fbf-8d9f-4e08-9e47-ace2491169ef, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=saltedReturnChecksumsWithChecksumPillar, to=<null>, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>, checksumRequestForNewFile=<null>]
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@31af1e26[correlationID=5e266fbf-8d9f-4e08-9e47-ace2491169ef, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=saltedReturnChecksumsWithChecksumPillar, to=<null>, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, pillarID=Pillar2, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>, checksumRequestForNewFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@5632152e[checksumType=HMAC_MD5, checksumSalt={-86}, otherChecksumType=<null>]]
Test success: saltedReturnChecksumsWithChecksumPillar
Test starting: sameFileExistsOnOnePillar
Description: Tests that PutClient handles the presence of a file correctly, when the pillar returns a checksum equal the file being put (idempotent).
Step: Call putFile.
Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@74c7e49a[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@557f3f76[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-12-08T02:19:54.615+01:00], null, org.bitrepository.client.TestEventHandler@5522861e, TEST-AUDIT-TRAIL)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@742ccaa7[correlationID=940e272e-b4f2-41fb-ae42-1b47811611e6, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=sameFileExistsOnOnePillar, to=<null>, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, fileID=default-test-file.txt, fileSize=0]
Result: Received event: 940e272e: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file
Step: Send a DUPLICATE_FILE_FAILURE response with a checksum equal to the one supplied to the client.
Result: Received event: 940e272e: PUT_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, requestedChecksumResult=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@527f7988[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@4014f892[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-12-08T02:19:54.616+01:00], File already existed on Pillar1
Step: Send an identification response from the second pillar.
Result: Received event: 940e272e: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 940e272e: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: 940e272e: PUT_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar2], Sending request for put file
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@2c3077bf[correlationID=940e272e-b4f2-41fb-ae42-1b47811611e6, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=sameFileExistsOnOnePillar, to=<null>, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, pillarID=Pillar2, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@74c7e49a[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@557f3f76[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-12-08T02:19:54.615+01:00], checksumRequestForNewFile=<null>]
Step: The client should proceed to send a putFileOperation request to the second pillar.
Step: Send a pillar complete event
Result: Received event: 940e272e: PUT_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2, requestedChecksumResult=null
Result: Received event: 940e272e: PUT_FILE for file default-test-file.txt: COMPLETE:
Test success: sameFileExistsOnOnePillar
Test starting: verifyPutClientFromFactory
Description: Testing the initialization through the ModifyComponentFactory.
Step: Use the ModifyComponentFactory to instantiate a PutFileClient.
Test success: verifyPutClientFromFactory
Starting testcase GetChecksumsCmdTest
Test starting: checksumArgumentNonSaltAlgorithmWitoutSaltTest
Description: Test MD5 checksum without salt -> no failure
Test success: checksumArgumentNonSaltAlgorithmWitoutSaltTest
Result: Received event: 32fe5f80: GET_AUDIT_TRAILS: FAILED: , Failed to receive responses from all contributors before timeout(60000ms). Missing contributors [Pillar1, Pillar2]
Test starting: checksumArgumentSaltAlgorithmWithSaltTest
Description: Test HMAC_SHA256 checksum with salt -> No failure
Test success: checksumArgumentSaltAlgorithmWithSaltTest
Test starting: defaultSuccessScenarioTest
Description: Tests simplest arguments for running the CmdLineClient
Test success: defaultSuccessScenarioTest
Test starting: fileArgumentTest
Description: Tests the argument for a specific file.
Test success: fileArgumentTest
Test starting: missingCollectionArgumentTest
Description: Tests the scenario, where the collection arguments is missing.
Takes the following arguments:
-s The path to the directory with the settings files for the client
-k The path to the file containing the private key.
-v Makes the client more verbose
-c The id for the collection to perform the operation on.
-i The id for the file to perform the operation on.
-p [OPTIONAL] The id of the pillar where the should be performed. If undefined the operations is performed on all pillars.
-R [OPTIONAL] The algorithm of checksum to request in the response from the pillars. If no such argument is given, then the default from settings is retrieved.
-S [OPTIONAL] The salt of checksum to request in the response. Requires the ChecksumType argument.
Missing argument: Missing required option: c
Test success: missingCollectionArgumentTest
Test starting: specificPillarArgumentTest
Description: Test argument for a specific pillar
Test success: specificPillarArgumentTest
Test starting: unknownPillarArgumentTest
Description: Testing against a non-existing pillar id -> Should fail
Invalid argument: Random1449537595624pillar is not a valid pillar for collection TwoPillarCollection
The collection contains the following pillars: [Pillar1, Pillar2]
Test success: unknownPillarArgumentTest
Finished testcase
Finished suite
Finished project
Result: Received event: 72a951d5: GET_AUDIT_TRAILS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar1, Pillar2]
Result: Received event: 72a951d5: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor
Result: Received event: 72a951d5: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
Result: Received event: 72a951d5: GET_AUDIT_TRAILS: FAILED: , Unable to continue operation, contributors unavailable.
Tests run: 156, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 69.33 sec - in TestSuite
Result: Received event: ec724787: GET_CHECKSUMS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar1, Pillar2]
Result: Received event: ec724787: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor
Result: Received event: ec724787: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
Result: Received event: ec724787: GET_CHECKSUMS: FAILED: , Unable to continue operation, contributors unavailable.
[JENKINS] Recording test results
Results :
Tests run: 156, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ bitrepository-client ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/target/bitrepository-client-1.6-SNAPSHOT.jar
[INFO]
[INFO] --- maven-jar-plugin:2.4:test-jar (default) @ bitrepository-client ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/target/bitrepository-client-1.6-SNAPSHOT-tests.jar
[INFO]
[INFO] --- maven-source-plugin:2.2.1:jar-no-fork (attach-sources-no-fork) @ bitrepository-client ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/target/bitrepository-client-1.6-SNAPSHOT-sources.jar
[INFO]
[INFO] --- maven-assembly-plugin:2.4:single (make-assembly) @ bitrepository-client ---
[INFO] Reading assembly descriptor: src/main/assembly/assembly.xml
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/target/bitrepository-client-1.6-SNAPSHOT-distribution.tar.gz
[INFO]
[INFO] --- maven-install-plugin:2.5.1:install (default-install) @ bitrepository-client ---
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/target/bitrepository-client-1.6-SNAPSHOT.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-client/1.6-SNAPSHOT/bitrepository-client-1.6-SNAPSHOT.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-client/1.6-SNAPSHOT/bitrepository-client-1.6-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/target/bitrepository-client-1.6-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-client/1.6-SNAPSHOT/bitrepository-client-1.6-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/target/bitrepository-client-1.6-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-client/1.6-SNAPSHOT/bitrepository-client-1.6-SNAPSHOT-sources.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/target/bitrepository-client-1.6-SNAPSHOT-distribution.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-client/1.6-SNAPSHOT/bitrepository-client-1.6-SNAPSHOT-distribution.tar.gz
[JENKINS] Archiving disabled
Console Output
Help us localize this page