[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 ChecksumExtractionUtilsTest
Test starting: testDefaultChecksumSpec
Description: Test that the default checksum is retrieved when no arguments are given.
Test success: testDefaultChecksumSpec
Test starting: testDefaultChecksumSpecWithSaltArgument
Description: Test that the HMAC version of default checksum is retrieved when the salt arguments are given.
Test success: testDefaultChecksumSpecWithSaltArgument
Test starting: testNonSaltChecksumSpecWithSaltArgument
Description: Test that a salt checksum type is retrieved even though a non-salt checksum algorithm it is given as argument, but a salt argument also is given.
Test success: testNonSaltChecksumSpecWithSaltArgument
Test starting: testNonSaltChecksumSpecWithoutSaltArgument
Description: Test that a non-salt checksum type is retrieved when it is given as argument, and no salt arguments are given.
Test success: testNonSaltChecksumSpecWithoutSaltArgument
Test starting: testSaltChecksumSpecWithSaltArgument
Description: Test that a salt checksum type is retrieved when the salt checksum algorithm it is given as argument, and a salt argument also is given.
Test success: testSaltChecksumSpecWithSaltArgument
Test starting: testSaltChecksumSpecWithoutSaltArgument
Description: Test that a non-salt checksum type is retrieved even though a salt checksum algorithm it is given as argument, but no salt argument also is given.
Test success: testSaltChecksumSpecWithoutSaltArgument
Starting testcase CommandLineTest
Test starting: argumentsTesterUnknownArgument
Description: Test the handling of arguments by the CommandLineArgumentHandler.
Step: Validate arguments without any options.
Test success: argumentsTesterUnknownArgument
Test starting: argumentsTesterWrongArgument
Description: Test the handling of arguments by the CommandLineArgumentHandler.
Step: Validate the default options
Test success: argumentsTesterWrongArgument
Test starting: newArgumentTester
Description: Test the handling of a new argument.
Step: Test the option
Test success: newArgumentTester
Starting testcase 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@6050462a)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@426e505c[correlationID=514ec503-f30e-4a31-a039-77912333f070, 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@614aeccc[fileID=<null>, allFileIDs=true]]
Result: Received event: 514ec503: 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: 514ec503: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 514ec503: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE
Result: Received event: 514ec503: GET_FILE_IDS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 514ec503: GET_FILE_IDS: REQUEST_SENT: ContributorID [Pillar1], Sending request for get fileIDs
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@56ba8773[correlationID=514ec503-f30e-4a31-a039-77912333f070, 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@6ceb7b5e[fileID=<null>, allFileIDs=true], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
Step: Wait for 1 second
Result: Received event: 514ec503: 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@6050462a)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@834831b[correlationID=317c893a-e010-4a03-b909-6384591274e8, 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@234a8f27[fileID=<null>, allFileIDs=true]]
Result: Received event: 317c893a: GET_FILE_IDS: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs
02:19:10.971 WARN o.b.c.c.m.CollectionBasedConversationMediator - Failing timed out conversation 317c893a-e010-4a03-b909-6384591274e8 (Age 1014ms)
Result: Received event: 317c893a: GET_FILE_IDS: FAILED: , Failing timed out conversation 317c893a-e010-4a03-b909-6384591274e8
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@6050462a)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@3491e86e[correlationID=a2efc0c4-d047-4ea3-9685-107af112ea3d, 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@68f32020[fileID=<null>, allFileIDs=true]]
Result: Received event: a2efc0c4: 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: a2efc0c4: 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: a2efc0c4: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: a2efc0c4: GET_FILE_IDS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: a2efc0c4: GET_FILE_IDS: REQUEST_SENT: ContributorID [Pillar2], Sending request for get fileIDs
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@19b047fe[correlationID=a2efc0c4-d047-4ea3-9685-107af112ea3d, 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@22590e3e[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: a2efc0c4: GET_FILE_IDS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false
Result: Received event: a2efc0c4: GET_FILE_IDS: FAILED: , Failed operation. Cause(s):
[a2efc0c4: 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@6050462a)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@5e8cda75[correlationID=bb0be03f-d7af-4a56-9877-0a4916bba421, 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@3f049056[fileID=<null>, allFileIDs=true]]
Result: Received event: bb0be03f: 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: bb0be03f: 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: bb0be03f: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: bb0be03f: GET_FILE_IDS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: bb0be03f: GET_FILE_IDS: REQUEST_SENT: ContributorID [Pillar2], Sending request for get fileIDs
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@3e1a3801[correlationID=bb0be03f-d7af-4a56-9877-0a4916bba421, 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@6fd12c5[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: bb0be03f: GET_FILE_IDS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false
Result: Received event: bb0be03f: GET_FILE_IDS: FAILED: , Failed operation. Cause(s):
[bb0be03f: 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@6050462a)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@1ba359bd[correlationID=9d92c6f2-ceae-4fe2-a09d-ed979cd91106, 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@62e93c3a[fileID=<null>, allFileIDs=true]]
Result: Received event: 9d92c6f2: GET_FILE_IDS: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs
Step: Wait for 1 second
Result: Received event: 9d92c6f2: GET_FILE_IDS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar1, Pillar2]
Result: Received event: 9d92c6f2: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor
Result: Received event: 9d92c6f2: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
Result: Received event: 9d92c6f2: 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@1ba359bd[correlationID=9d92c6f2-ceae-4fe2-a09d-ed979cd91106, 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@62e93c3a[fileID=<null>, allFileIDs=true]]
02:19:14.285 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@1ba359bd[correlationID=9d92c6f2-ceae-4fe2-a09d-ed979cd91106, 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@62e93c3a[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@6050462a)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@5f254608[correlationID=74774bec-d4f4-4dff-9172-5c5d46e7cb7b, 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@2eeb0f9b[fileID=<null>, allFileIDs=true]]
Result: Received event: 74774bec: GET_FILE_IDS: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs
Step: Send a identification response from contributor1.
Result: Received event: 74774bec: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Step: Wait 1 second.
Result: Received event: 74774bec: GET_FILE_IDS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar2]
Result: Received event: 74774bec: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
Result: Received event: 74774bec: GET_FILE_IDS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 74774bec: GET_FILE_IDS: REQUEST_SENT: ContributorID [Pillar1], Sending request for get fileIDs
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@66bfd225[correlationID=74774bec-d4f4-4dff-9172-5c5d46e7cb7b, 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@68783082[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: 74774bec: GET_FILE_IDS: COMPONENT_COMPLETE: ContributorID Pillar1, PartialResult=false
Result: Received event: 74774bec: GET_FILE_IDS: FAILED: , Failed operation. Cause(s):
[74774bec: 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@6050462a)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@54d1608f[correlationID=270d6c76-9be4-46d5-a800-8719ca9fe761, 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@7e7fe6d[fileID=<null>, allFileIDs=true]]
Result: Received event: 270d6c76: 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: 270d6c76: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 270d6c76: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE
Result: Received event: 270d6c76: GET_FILE_IDS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 270d6c76: GET_FILE_IDS: REQUEST_SENT: ContributorID [Pillar1], Sending request for get fileIDs
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@24386839[correlationID=270d6c76-9be4-46d5-a800-8719ca9fe761, 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@7b32b129[fileID=<null>, allFileIDs=true], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
Step: Wait for 1 second
Result: Received event: 270d6c76: GET_FILE_IDS: 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@2740e316[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@5b5a4aed[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@2c991465[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], eventHandler, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@5fef2aac[correlationID=b0abed2b-5dcf-4126-8987-f97dd636e893, 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: b0abed2b: 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: b0abed2b: 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: b0abed2b: DELETE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor
Result: Received event: b0abed2b: 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@6025d790[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@af7e376[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@5dcd0cdf[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], eventHandler, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@4fb04a72[correlationID=4b641ef5-f03b-421f-90ef-705382c917d1, 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: 4b641ef5: 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: 4b641ef5: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 4b641ef5: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 4b641ef5: 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@343e225a[correlationID=4b641ef5-f03b-421f-90ef-705382c917d1, 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@6025d790[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@af7e376[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@5dcd0cdf[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: 4b641ef5: 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@25c2a9e3[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@9b23822[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-16T02:19:17.297+01:00], null, eventHandler, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@60f21960[correlationID=b97804a2-72a4-4a4f-bab3-911a8374cd75, 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: b97804a2: 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: b97804a2: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: b97804a2: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: b97804a2: 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@5a515e5d[correlationID=b97804a2-72a4-4a4f-bab3-911a8374cd75, 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@25c2a9e3[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@9b23822[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-16T02:19:17.297+01:00], checksumRequestForExistingFile=<null>]
Step: Send a final response message from pillar 1 to the DeleteClient.
Result: Received event: b97804a2: DELETE_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, DeleteFileResult=null
Result: Received event: b97804a2: 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@6b2dd3df[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@4db77402[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@73c48264[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], eventHandler, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@5ef85555[correlationID=79a7e7b0-179d-44a0-a476-6d560d6996fa, 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: 79a7e7b0: 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: 79a7e7b0: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 79a7e7b0: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 79a7e7b0: 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@2dafae61[correlationID=79a7e7b0-179d-44a0-a476-6d560d6996fa, 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@6b2dd3df[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@4db77402[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@73c48264[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: 79a7e7b0: DELETE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE, Verifying that a failure can be understood!
Result: Received event: 79a7e7b0: DELETE_FILE for file default-test-file.txt: FAILED: , Failed operation. Cause(s):
[79a7e7b0: 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@6b63abdc[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7b351446[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-16T02:19:18.816+01:00], null, eventHandler, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@5f08fe00[correlationID=2d1f6a56-24b6-4055-9615-de911dbfaf09, 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: 2d1f6a56: 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: 2d1f6a56: DELETE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: IDENTIFICATION_NEGATIVE
Result: Received event: 2d1f6a56: 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@6af65f29[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@370c9018[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@3c81cd82[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], eventHandler, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@111c229c[correlationID=6bb96660-ac9e-4916-8a3d-72680a4504e0, 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: 6bb96660: 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: 6bb96660: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 6bb96660: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 6bb96660: 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@1a14fdf0[correlationID=6bb96660-ac9e-4916-8a3d-72680a4504e0, 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@6af65f29[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@370c9018[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@3c81cd82[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: 6bb96660: 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: 6bb96660: DELETE_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, DeleteFileResult=null
Result: Received event: 6bb96660: 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@40bd0f8[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7eb27768[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-16T02:19:19.259+01:00], null, eventHandler, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@6169be09[correlationID=2777f124-4eca-4c75-bc51-628836ad51f0, 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: 2777f124: 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: 2777f124: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 2777f124: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 2777f124: 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@5fb54740[correlationID=2777f124-4eca-4c75-bc51-628836ad51f0, 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@40bd0f8[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7eb27768[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-16T02:19:19.259+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@693f2213[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@514377fc[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-16T02:19:21.549+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2e4eda17[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], eventHandler, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@7b5021d1[correlationID=00d258b0-1820-44f4-a74f-230a45090b99, 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: 00d258b0: 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: 00d258b0: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 00d258b0: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 00d258b0: 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@7ac48f05[correlationID=00d258b0-1820-44f4-a74f-230a45090b99, 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@693f2213[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@514377fc[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-16T02:19:21.549+01:00], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2e4eda17[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@4f26425b[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@f03ee8f[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-16T02:19:21.846+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@40dd552c[checksumType=MD5, checksumSalt={-86}, otherChecksumType=<null>], eventHandler, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@33f4c769[correlationID=0ac712d7-c8d8-4f60-bd6f-e794a085cc57, 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: 0ac712d7: 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: 0ac712d7: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 0ac712d7: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 0ac712d7: 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@5e5a8718[correlationID=0ac712d7-c8d8-4f60-bd6f-e794a085cc57, 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@4f26425b[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@f03ee8f[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-16T02:19:21.846+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@4b5ad306[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@54be6213[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-16T02:19:22.128+01:00], null, eventHandler, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@48a46b0f[correlationID=c7c715ce-fb15-41cd-822c-d8f27cc1f6ba, 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: c7c715ce: 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: c7c715ce: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: c7c715ce: DELETE_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, DeleteFileResult=null
Result: Received event: c7c715ce: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: []
Result: Received event: c7c715ce: DELETE_FILE for file default-test-file.txt: COMPLETE:
Step: The client should then continue to the performing phase and finish immediately as the pillar has already had the file removed apparently .
Step: Send a identify response from Pillar2
Test success: fileAlreadyDeletedFromPillar
Test starting: verifyDeleteClientFromFactory
Description: Testing the initialization through the ModifyComponentFactory.
Step: Use the ModifyComponentFactory to instantiate a PutFileClient.
Test success: verifyDeleteClientFromFactory
Starting testcase 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: Random1450228765829pillar is not a valid pillar for collection TwoPillarCollection
The collection contains the following pillars: [Pillar1, Pillar2]
Test success: unknownPillarArgumentTest
Test starting: getFileIDsDeliveredAtUrl
Description: Tests the delivery of fileIDs from a pillar at a given URL.
Step: Initialise the variables for this test.
Step: Request the delivery of the file ids of a file from the pillar(s). A callback listener should be supplied.
Stimuli: Calling getFileIDs(null, default-test-file.txt, file:../bitrepository-core/src/test/resources/test-files//TEST-FILE-IDS-DELIVERY.xml, org.bitrepository.client.TestEventHandler@6050462a)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@446dacf9[correlationID=e2c0273e-b477-4837-ad34-672df0eebef7, 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@13018f00[fileID=default-test-file.txt, allFileIDs=<null>]]
Result: Received event: e2c0273e: 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: e2c0273e: GET_FILE_IDS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: e2c0273e: GET_FILE_IDS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: e2c0273e: 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@2e1e7bc6[correlationID=e2c0273e-b477-4837-ad34-672df0eebef7, 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@7bd1098[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: e2c0273e: 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: e2c0273e: GET_FILE_IDS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, PartialResult=false
Result: Received event: e2c0273e: 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@6050462a)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@472dbaf5[correlationID=351880be-874c-49d9-8f26-e59f127f657e, 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@25c4f621[fileID=default-test-file.txt, allFileIDs=<null>]]
Result: Received event: 351880be: 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: 351880be: GET_FILE_IDS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 351880be: GET_FILE_IDS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 351880be: 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@46ff1aad[correlationID=351880be-874c-49d9-8f26-e59f127f657e, 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@6c2fea95[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: 351880be: 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: 351880be: GET_FILE_IDS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, NumberOfFileIDs=1, PartialResult=false
Result: Received event: 351880be: 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@7cadf3ca)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@34fcc5e3[correlationID=b45a10c6-aa89-47c3-8d92-b06ffeef1569, 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@737445ab[fileID=default-test-file.txt, allFileIDs=<null>]]
Result: Received event: b45a10c6: 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: b45a10c6: GET_FILE_IDS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: b45a10c6: GET_FILE_IDS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: b45a10c6: 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@2f3c7b24[correlationID=b45a10c6-aa89-47c3-8d92-b06ffeef1569, 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@7dbd70fd[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: b45a10c6: GET_FILE_IDS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false
Result: Received event: b45a10c6: 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@6050462a)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@6173863f[correlationID=f6dab87e-23d2-49de-a4e1-30834c250167, 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@a08e41b[fileID=default-test-file.txt, allFileIDs=<null>]]
Result: Received event: f6dab87e: 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: f6dab87e: GET_FILE_IDS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: f6dab87e: GET_FILE_IDS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: f6dab87e: 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@4ebb7bab[correlationID=f6dab87e-23d2-49de-a4e1-30834c250167, 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@33845e3d[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: f6dab87e: GET_FILE_IDS for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FILE_NOT_FOUND_FAILURE, No such file.
Result: Received event: f6dab87e: GET_FILE_IDS for file default-test-file.txt: FAILED: , Failed operation. Cause(s):
[f6dab87e: 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=Wed Dec 16 02:19:25 CET 2015, maxTimestamp=Wed Dec 16 02:19:26 CET 2015, maxNumberOfResults=1}, ContributorQuery{componentID='Pillar2, minTimestamp=Wed Dec 16 02:19:26 CET 2015, maxTimestamp=Wed Dec 16 02:19:26 CET 2015, maxNumberOfResults=2}], null, null, org.bitrepository.client.TestEventHandler@6050462a)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@5089a72b[correlationID=937e4df1-2691-4eaa-854d-e06d752aba78, 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@1164990a[fileID=<null>, allFileIDs=true]]
Result: Received event: 937e4df1: GET_FILE_IDS: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs
Step: Send a IdentifyPillarsForGetFileIDsResponse from both pillars.
Result: Received event: 937e4df1: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 937e4df1: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 937e4df1: GET_FILE_IDS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2, Pillar1]
Result: Received event: 937e4df1: GET_FILE_IDS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for get fileIDs
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@346a2799[correlationID=937e4df1-2691-4eaa-854d-e06d752aba78, 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@17344d7[fileID=<null>, allFileIDs=true], minTimestamp=2015-12-16T02:19:25.903+01:00, maxTimestamp=2015-12-16T02:19:26.803+01:00, maxNumberOfResults=1, resultAddress=<null>]
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@75b4db22[correlationID=937e4df1-2691-4eaa-854d-e06d752aba78, 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@670aac24[fileID=<null>, allFileIDs=true], minTimestamp=2015-12-16T02:19:26.803+01:00, maxTimestamp=2015-12-16T02:19:26.903+01:00, maxNumberOfResults=2, resultAddress=<null>]
Test success: testPaging
Test starting: verifyGetFileIDsClientFromFactory
Test success: verifyGetFileIDsClientFromFactory
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: 493dd8e8: GET_STATUS: IDENTIFY_REQUEST_SENT: , Identifying contributors for getting status
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetStatusRequest@7dc963be[correlationID=493dd8e8-c2ac-45ed-a4c2-e1bfdb445456, 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: 493dd8e8: GET_STATUS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 493dd8e8: GET_STATUS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 493dd8e8: GET_STATUS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2, Pillar1]
Result: Received event: 493dd8e8: GET_STATUS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending GetStatusRequest
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetStatusRequest@68ea1eb5[correlationID=493dd8e8-c2ac-45ed-a4c2-e1bfdb445456, 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@d7c00de[correlationID=493dd8e8-c2ac-45ed-a4c2-e1bfdb445456, 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: 493dd8e8: GET_STATUS: COMPONENT_COMPLETE: ContributorID Pillar1, resulting status: org.bitrepository.bitrepositoryelements.ResultingStatus@6046fba0[statusInfo=org.bitrepository.bitrepositoryelements.StatusInfo@248ba4fc[statusCode=OK, statusText=Everythings fine..], statusTimestamp=2015-12-16T02:19:27.434+01:00]
Step: Send a final response from pillar 2
Result: Received event: 493dd8e8: GET_STATUS: COMPONENT_COMPLETE: ContributorID Pillar2, resulting status: org.bitrepository.bitrepositoryelements.ResultingStatus@54cce500[statusInfo=org.bitrepository.bitrepositoryelements.StatusInfo@755033c5[statusCode=OK, statusText=Everythings fine..], statusTimestamp=2015-12-16T02:19:27.437+01:00]
Result: Received event: 493dd8e8: 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: fce07e48: GET_STATUS: IDENTIFY_REQUEST_SENT: , Identifying contributors for getting status
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetStatusRequest@27adb90f[correlationID=fce07e48-2a7a-489b-9f9e-e19ae74f0677, 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: fce07e48: GET_STATUS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Step: Wait for timeout event
Result: Received event: fce07e48: GET_STATUS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar2]
Result: Received event: fce07e48: GET_STATUS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
Result: Received event: fce07e48: GET_STATUS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: fce07e48: GET_STATUS: REQUEST_SENT: ContributorID [Pillar1], Sending GetStatusRequest
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetStatusRequest@6c47b955[correlationID=fce07e48-2a7a-489b-9f9e-e19ae74f0677, 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 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@3687b83c[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], org.bitrepository.client.TestEventHandler@4cbd17b3, TEST-AUDIT-TRAIL)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@3a5c6009[correlationID=baaaf5f3-6050-45a2-ab2c-23aebf46001c, 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: baaaf5f3: 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: baaaf5f3: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Step: Send an normal identification response from pillar2.
Result: Received event: baaaf5f3: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: baaaf5f3: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2, Pillar1]
Result: Received event: baaaf5f3: 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@5a2297d7[correlationID=baaaf5f3-6050-45a2-ab2c-23aebf46001c, 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@3687b83c[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>]]
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@39d37da8[correlationID=baaaf5f3-6050-45a2-ab2c-23aebf46001c, 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@3687b83c[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@4986b0ea, TEST-AUDIT-TRAIL)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@ce5a2ea[correlationID=48d2d3ce-1f50-495b-8034-79c0017aed19, 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: 48d2d3ce: 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: 48d2d3ce: 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@219ec4b6[responseCode=DUPLICATE_FILE_FAILURE, responseText=Testing the handling of 'DUPLICATE FILE' identification.] (existing file checksum does not match)
Result: Received event: 48d2d3ce: 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@6b23897a[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@40dd2cfe[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={-70}, calculationTimestamp=2015-12-16T02:19:29.313+01:00], null, org.bitrepository.client.TestEventHandler@21cb5648, TEST-AUDIT-TRAIL)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@69fa5536[correlationID=897bc406-b232-4773-983c-86ab6ce1b899, 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: 897bc406: 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: 897bc406: 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@4cf46574[responseCode=DUPLICATE_FILE_FAILURE, responseText=Testing the handling of 'DUPLICATE FILE' identification.] (existing file checksum does not match)
Result: Received event: 897bc406: 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@6d3c80bf, TEST-AUDIT-TRAIL)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@2f53e07d[correlationID=1f30e22b-c9ad-4158-8f04-8475738b159f, 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: 1f30e22b: 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: 1f30e22b: 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@5c3ad125[responseCode=DUPLICATE_FILE_FAILURE, responseText=Testing the handling of 'DUPLICATE FILE' identification.]
Result: Received event: 1f30e22b: 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@37596b44, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@29ec5005[correlationID=96154f86-697d-44d8-8a64-bc78dcc5cd81, 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: 96154f86: 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: 96154f86: 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: 96154f86: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor
Result: Received event: 96154f86: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
Result: Received event: 96154f86: 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@77a35b2f, TEST-AUDIT-TRAIL)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@755057c7[correlationID=b7b53cea-916c-45a2-8d84-eaa45c2b697a, 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: b7b53cea: 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: b7b53cea: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Step: Send an normal identification response from pillar2.
Result: Received event: b7b53cea: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: b7b53cea: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2, Pillar1]
Result: Received event: b7b53cea: 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@1d642682[correlationID=b7b53cea-916c-45a2-8d84-eaa45c2b697a, 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@6afdb486[correlationID=b7b53cea-916c-45a2-8d84-eaa45c2b697a, 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@7b9b244e, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@996126b[correlationID=4b97e694-47dc-4f0c-8746-b5661219c95d, 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: 4b97e694: 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: 4b97e694: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 4b97e694: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 4b97e694: 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@6d4b09c7[correlationID=4b97e694-47dc-4f0c-8746-b5661219c95d, 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: 4b97e694: 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: 4b97e694: PUT_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, requestedChecksumResult=null
Result: Received event: 4b97e694: 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@5f0c45ae, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@66d62c59[correlationID=0c18e357-b365-443d-ab35-34b9a1e98d7b, 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: 0c18e357: 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: 0c18e357: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 0c18e357: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 0c18e357: 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@2c2dfde3[correlationID=0c18e357-b365-443d-ab35-34b9a1e98d7b, 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@1131fcfd[correlationID=0c18e357-b365-443d-ab35-34b9a1e98d7b, 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: 0c18e357: 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@46d2be66[correlationID=0c18e357-b365-443d-ab35-34b9a1e98d7b, 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: 0c18e357: 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: 0c18e357: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FILE_TRANSFER_FAILURE
Result: Received event: 0c18e357: PUT_FILE for file default-test-file.txt: FAILED: , Failed operation. Cause(s):
[0c18e357: 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@4fb1bffd, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@427c9a13[correlationID=9ca60fad-fdff-40a1-b074-4141e9d4e5ad, 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: 9ca60fad: 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: 9ca60fad: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 9ca60fad: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 9ca60fad: 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@6e620fa9[correlationID=9ca60fad-fdff-40a1-b074-4141e9d4e5ad, 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@2cee1bcf[correlationID=9ca60fad-fdff-40a1-b074-4141e9d4e5ad, 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: 9ca60fad: 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: 9ca60fad: PUT_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, requestedChecksumResult=null
Result: Received event: 9ca60fad: 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@78854721, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@11759e4a[correlationID=cc182a84-ebf4-4d64-ad12-2d2f9979600e, 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: cc182a84: 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: cc182a84: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Step: Await the timeout.
Result: Received event: cc182a84: 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: cc182a84: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
Result: Received event: cc182a84: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: cc182a84: 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@29453ab9[correlationID=cc182a84-ebf4-4d64-ad12-2d2f9979600e, 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: cc182a84: PUT_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, requestedChecksumResult=null
Result: Received event: cc182a84: PUT_FILE for file default-test-file.txt: FAILED: , Failed operation. Cause(s):
[cc182a84: 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@20834c45, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@74061ced[correlationID=444df61a-a045-40fe-bf91-2e754bceb141, 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: 444df61a: 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: 444df61a: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Step: Await the timeout.
Result: Received event: 444df61a: 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: 444df61a: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
Result: Received event: 444df61a: 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@228c854f, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@47c019d7[correlationID=a4c94c36-286d-47f0-98d1-90e9cde607d0, 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: a4c94c36: 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: a4c94c36: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: a4c94c36: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: a4c94c36: 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@f2e28c7[correlationID=a4c94c36-286d-47f0-98d1-90e9cde607d0, 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: a4c94c36: 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@68c9cf93, TEST-AUDIT-TRAIL)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@2715b3ea[correlationID=6558843b-a538-4932-a2a5-cdc9be2c51f6, 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: 6558843b: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file
Step: Send pillar response.
Result: Received event: 6558843b: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 6558843b: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 6558843b: 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@5aa0d535[correlationID=6558843b-a538-4932-a2a5-cdc9be2c51f6, 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: 6558843b: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE, Verifying that a failure can be understood!
Result: Received event: 6558843b: PUT_FILE for file default-test-file.txt: FAILED: , Failed operation. Cause(s):
[6558843b: 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@d0971cd, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@53b42a0d[correlationID=c8a1811d-da8d-48c5-a2b5-02284029deec, 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: c8a1811d: 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: c8a1811d: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: c8a1811d: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: c8a1811d: 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@33c5d3e[correlationID=c8a1811d-da8d-48c5-a2b5-02284029deec, 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: c8a1811d: PUT_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2, requestedChecksumResult=null
Result: Received event: c8a1811d: 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@23c07745[checksumType=HMAC_MD5, checksumSalt={-86}, otherChecksumType=<null>], org.bitrepository.client.TestEventHandler@62a07c01, TEST-AUDIT-TRAIL)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@52dbd3d[correlationID=0c43d52c-ff8b-4dc1-8972-4d8921f5e52e, 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: 0c43d52c: 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: 0c43d52c: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Step: Send an normal identification response from pillar2.
Result: Received event: 0c43d52c: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 0c43d52c: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2]
Result: Received event: 0c43d52c: 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@704205ef[correlationID=0c43d52c-ff8b-4dc1-8972-4d8921f5e52e, 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@18ee9a8f[correlationID=0c43d52c-ff8b-4dc1-8972-4d8921f5e52e, 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@23c07745[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@6a7c0932[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@4e64e44c[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-16T02:19:32.029+01:00], null, org.bitrepository.client.TestEventHandler@51413d02, TEST-AUDIT-TRAIL)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@406ea770[correlationID=f0f5cf08-dd90-4ab1-b0a7-6e2c0ddf33d4, 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: f0f5cf08: 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: f0f5cf08: PUT_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, requestedChecksumResult=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@7b0f5814[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@4eef2522[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-16T02:19:32.033+01:00], File already existed on Pillar1
Step: Send an identification response from the second pillar.
Result: Received event: f0f5cf08: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: f0f5cf08: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: f0f5cf08: 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@598b15ba[correlationID=f0f5cf08-dd90-4ab1-b0a7-6e2c0ddf33d4, 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@6a7c0932[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@4e64e44c[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-16T02:19:32.029+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: f0f5cf08: PUT_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2, requestedChecksumResult=null
Result: Received event: f0f5cf08: 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
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: Random1450228773736pillar is not a valid pillar for collection TwoPillarCollection
The collection contains the following pillars: [Pillar1, Pillar2]
Test success: unknownPillarArgumentTest
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: Random1450228774724pillar 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: Random1450228779053pillar is not a valid pillar for collection TwoPillarCollection
The collection contains the following pillars: [Pillar1, Pillar2]
Test success: unknownPillarArgumentTest
Starting testcase UnexpectedResponseExceptionTest
Test starting: testUnexpectedResponse
Description: Test the instantiation of the exception
Step: Setup
Step: Try to throw such an exception
Step: Throw the exception with an embedded exception
Test success: testUnexpectedResponse
Starting testcase 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@7a234d98[correlationID=44c91953-7627-419f-a13c-af7997c095fd, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=getAllAuditTrailsTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
Result: Received event: 44c91953: 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: 44c91953: GET_AUDIT_TRAILS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 44c91953: GET_AUDIT_TRAILS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 44c91953: GET_AUDIT_TRAILS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2]
Result: Received event: 44c91953: 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@75d9aae4[correlationID=44c91953-7627-419f-a13c-af7997c095fd, 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@57321187[correlationID=44c91953-7627-419f-a13c-af7997c095fd, 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: 44c91953: 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: 44c91953: GET_AUDIT_TRAILS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2, NumberOfAuditTrailEvents=2, PartialResult=false
Result: Received event: 44c91953: 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@4cfe2c78[correlationID=ae1a3996-3456-4850-ab80-59716596413d, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=getSomeAuditTrailsTest, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>]
Result: Received event: ae1a3996: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
Step: Send a identifyResponse from pillar1
Result: Received event: ae1a3996: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: ae1a3996: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: ae1a3996: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1], Sending request for audit trails
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@292e8d0a[correlationID=ae1a3996-3456-4850-ab80-59716596413d, 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: ae1a3996: GET_AUDIT_TRAILS: COMPONENT_COMPLETE: ContributorID Pillar1, NumberOfAuditTrailEvents=2, PartialResult=false
Result: Received event: ae1a3996: 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@3c21f35b[correlationID=999d3794-4dbe-4342-bee7-354e3c5d92a4, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=incompleteSetOfFinalResponsesTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
Result: Received event: 999d3794: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
Step: Send a identifyResponse from each of the two pillars
Result: Received event: 999d3794: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 999d3794: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 999d3794: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2, Pillar1]
Result: Received event: 999d3794: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for audit trails
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@74db835a[correlationID=999d3794-4dbe-4342-bee7-354e3c5d92a4, 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@47531db1[correlationID=999d3794-4dbe-4342-bee7-354e3c5d92a4, 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@47531db1[correlationID=999d3794-4dbe-4342-bee7-354e3c5d92a4, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=incompleteSetOfFinalResponsesTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar2, fileID=<null>, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
02:19:40.586 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@47531db1[correlationID=999d3794-4dbe-4342-bee7-354e3c5d92a4, 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@585f319e[correlationID=1142dfa7-b143-410f-9306-f5507ce5dd47, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=negativeGetAuditTrailsResponseTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
Result: Received event: 1142dfa7: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
Step: Send a identifyResponse from each of the two pillars
Result: Received event: 1142dfa7: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 1142dfa7: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 1142dfa7: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2, Pillar1]
Result: Received event: 1142dfa7: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for audit trails
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@574dcc6a[correlationID=1142dfa7-b143-410f-9306-f5507ce5dd47, 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@763fc4dc[correlationID=1142dfa7-b143-410f-9306-f5507ce5dd47, 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: 1142dfa7: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE, GetAuditTrails failed
Step: Send a final response from pillar 2
Result: Received event: 1142dfa7: GET_AUDIT_TRAILS: COMPONENT_COMPLETE: ContributorID Pillar2, NumberOfAuditTrailEvents=2, PartialResult=false
Result: Received event: 1142dfa7: GET_AUDIT_TRAILS: FAILED: , Failed operation. Cause(s):
[1142dfa7: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE, GetAuditTrails failed]
Test success: negativeGetAuditTrailsResponseTest
Test starting: noFinalResponsesTest
Description: Tests the the AuditTrailClient handles lack of Final Responses gracefully
Step: Set a 100 ms timeout for the operation.
Step: Make the client ask for all audit trails.
Stimuli: Calling getAuditTrails(null, null, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@b18d1ff[correlationID=2c49791c-b64b-4edc-abbb-55672b7c95f0, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noFinalResponsesTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
Result: Received event: 2c49791c: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
Step: Send a identifyResponse from each of the two pillars
Result: Received event: 2c49791c: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 2c49791c: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 2c49791c: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2, Pillar1]
Result: Received event: 2c49791c: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for audit trails
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@5eb0f030[correlationID=2c49791c-b64b-4edc-abbb-55672b7c95f0, 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@13ea5530[correlationID=2c49791c-b64b-4edc-abbb-55672b7c95f0, 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: 2c49791c: 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@5eb0f030[correlationID=2c49791c-b64b-4edc-abbb-55672b7c95f0, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noFinalResponsesTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar1, fileID=<null>, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
02:19:40.879 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@5eb0f030[correlationID=2c49791c-b64b-4edc-abbb-55672b7c95f0, 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@13ea5530[correlationID=2c49791c-b64b-4edc-abbb-55672b7c95f0, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noFinalResponsesTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar2, fileID=<null>, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
02:19:40.879 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@13ea5530[correlationID=2c49791c-b64b-4edc-abbb-55672b7c95f0, 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@3c15ab2c[correlationID=d656c1aa-c1d6-4188-a2a9-80accc4fab77, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=progressEventsTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
Result: Received event: d656c1aa: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
Step: Send a identifyResponse from each of the two pillars
Result: Received event: d656c1aa: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: d656c1aa: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: d656c1aa: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2]
Result: Received event: d656c1aa: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for audit trails
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@57c3e84[correlationID=d656c1aa-c1d6-4188-a2a9-80accc4fab77, 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@1421a9cc[correlationID=d656c1aa-c1d6-4188-a2a9-80accc4fab77, 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: d656c1aa: GET_AUDIT_TRAILS: PROGRESS: ContributorID Pillar1, GetAuditTrails request accepted
Step: Send a general progress response from pillar 2
Result: Received event: d656c1aa: GET_AUDIT_TRAILS: PROGRESS: ContributorID Pillar2, Still progressing
Test success: progressEventsTest
Test starting: verifyAuditTrailClientFromFactory
Test success: verifyAuditTrailClientFromFactory
Result: Received event: 999d3794: GET_AUDIT_TRAILS: FAILED: , Failed to receive responses from all contributors before timeout(500ms). Missing contributors [Pillar1, Pillar2]
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@7c2f3fe[correlationID=fb7ae38d-d09f-4111-9d41-9d80a635abf8, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=collectionIDIncludedInEventsTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
Result: Received event: fb7ae38d: 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: fb7ae38d: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: fb7ae38d: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE
Result: Received event: fb7ae38d: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: fb7ae38d: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1], Sending request for audit trails
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@52d53a96[correlationID=fb7ae38d-d09f-4111-9d41-9d80a635abf8, 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: fb7ae38d: GET_AUDIT_TRAILS: FAILED: , Failed to receive responses from all contributors before timeout(500ms). Missing contributors [Pillar1]
Test success: collectionIDIncludedInEventsTest
Test starting: conversationTimeoutTest
Description: Tests the the client handles lack of IdentifyPillarResponses gracefully
Step: Set a 100 ms ConversationTimeout.
Step: Start the operation
Stimuli: Calling getAuditTrails(null, null, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@59d2198d[correlationID=470836b9-8159-4506-9ff4-feefe5d9d462, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=conversationTimeoutTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
Result: Received event: 470836b9: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
02:19:42.766 WARN o.b.c.c.m.CollectionBasedConversationMediator - Failing timed out conversation 470836b9-8159-4506-9ff4-feefe5d9d462 (Age 1004ms)
Result: Received event: 470836b9: GET_AUDIT_TRAILS: FAILED: , Failing timed out conversation 470836b9-8159-4506-9ff4-feefe5d9d462
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@17630f31[correlationID=930f13c2-f57c-419b-9c0c-14bd2ffda344, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=identificationFailureTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
Result: Received event: 930f13c2: 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: 930f13c2: 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: 930f13c2: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 930f13c2: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: 930f13c2: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar2], Sending request for audit trails
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@70b62924[correlationID=930f13c2-f57c-419b-9c0c-14bd2ffda344, 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: 930f13c2: GET_AUDIT_TRAILS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false
Result: Received event: 930f13c2: GET_AUDIT_TRAILS: FAILED: , Failed operation. Cause(s):
[930f13c2: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE]
Test success: identificationFailureTest
Test starting: identificationNegativeTest
Description: Verify that the client works correctly when a contributor sends a negative response.
Step: Start the operation.
Stimuli: Calling getAuditTrails(null, null, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@262f71ef[correlationID=886821d2-5739-4f0f-972d-cfa0de92922c, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=identificationNegativeTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
Result: Received event: 886821d2: 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: 886821d2: 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: 886821d2: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 886821d2: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: 886821d2: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar2], Sending request for audit trails
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@4faf1f1a[correlationID=886821d2-5739-4f0f-972d-cfa0de92922c, 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: 886821d2: GET_AUDIT_TRAILS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false
Result: Received event: 886821d2: GET_AUDIT_TRAILS: FAILED: , Failed operation. Cause(s):
[886821d2: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: IDENTIFICATION_NEGATIVE]
Test success: identificationNegativeTest
Test starting: noContributorsRespondingTest
Description: Tests the the client handles lack of a IdentifyResponse gracefully. More concrete this means that the occurrence of a identification timeout should be handled correctly
Step: Set a 100 ms timeout for identifying contributors.
Step: Start the operation.
Stimuli: Calling getAuditTrails(null, null, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@3ab3a232[correlationID=2273cca9-a09f-40d4-8036-235a90d78e50, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noContributorsRespondingTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
Result: Received event: 2273cca9: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
Step: Wait for 1 second
Result: Received event: 2273cca9: GET_AUDIT_TRAILS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar1, Pillar2]
Result: Received event: 2273cca9: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor
Result: Received event: 2273cca9: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
Result: Received event: 2273cca9: 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@3ab3a232[correlationID=2273cca9-a09f-40d4-8036-235a90d78e50, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noContributorsRespondingTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
02:19:45.159 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@3ab3a232[correlationID=2273cca9-a09f-40d4-8036-235a90d78e50, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noContributorsRespondingTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
Test starting: oneContributorNotRespondingTest
Description: Verify that the client works correct without receiving identification responses from all contributors.
Added fixture: Set the a identification timeout to 100 ms.
Step: Start the operation.
Stimuli: Calling getAuditTrails(null, null, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@4a3306c2[correlationID=21395f08-f956-4f46-9277-d52b9b56e966, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=oneContributorNotRespondingTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
Result: Received event: 21395f08: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
Step: Send a identification response from contributor1.
Result: Received event: 21395f08: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Step: Wait 1 second.
Result: Received event: 21395f08: GET_AUDIT_TRAILS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar2]
Result: Received event: 21395f08: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
Result: Received event: 21395f08: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 21395f08: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1], Sending request for audit trails
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@3173eb4e[correlationID=21395f08-f956-4f46-9277-d52b9b56e966, 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: 21395f08: GET_AUDIT_TRAILS: COMPONENT_COMPLETE: ContributorID Pillar1, PartialResult=false
Result: Received event: 21395f08: GET_AUDIT_TRAILS: FAILED: , Failed operation. Cause(s):
[21395f08: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor]
Test success: oneContributorNotRespondingTest
Test starting: operationTimeoutTest
Description: Tests the the client handles lack of final responses gracefully.
Step: Set a 100 ms operation timeout.
Step: Start the operation
Stimuli: Calling getAuditTrails(null, null, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@48fffb84[correlationID=4b9939be-d3a6-46d0-b5a0-1de1141001a2, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=operationTimeoutTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
Result: Received event: 4b9939be: 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: 4b9939be: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 4b9939be: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE
Result: Received event: 4b9939be: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 4b9939be: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1], Sending request for audit trails
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@71a7ce25[correlationID=4b9939be-d3a6-46d0-b5a0-1de1141001a2, 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: 4b9939be: GET_AUDIT_TRAILS: FAILED: , Failed to receive responses from all contributors before timeout(100ms). Missing contributors [Pillar1]
Test success: operationTimeoutTest
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@550b7a92[correlationID=66efbfe1-fb8c-402b-9d26-048ee66f6940, 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: 66efbfe1: 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: 66efbfe1: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID THE-AVERAGE-PILLAR
Result: Received event: 66efbfe1: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID THE-FAST-PILLAR
Result: Received event: 66efbfe1: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID THE-SLOW-PILLAR
Result: Received event: 66efbfe1: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [THE-FAST-PILLAR]
Result: Received event: 66efbfe1: 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@28353636[correlationID=66efbfe1-fb8c-402b-9d26-048ee66f6940, 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@3881f391[correlationID=d0dd4e16-2db5-483f-b9a1-5eb29b964abc, 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: d0dd4e16: 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: d0dd4e16: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: d0dd4e16: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: d0dd4e16: 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@2319092a[correlationID=d0dd4e16-2db5-483f-b9a1-5eb29b964abc, 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:46.814 WARN o.b.c.c.m.CollectionBasedConversationMediator - Failing timed out conversation d0dd4e16-2db5-483f-b9a1-5eb29b964abc (Age 1006ms)
Result: Received event: d0dd4e16: GET_FILE for file default-test-file.txt: FAILED: , Failing timed out conversation d0dd4e16-2db5-483f-b9a1-5eb29b964abc
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@3b591a07[correlationID=d0c86557-439b-496e-ad03-ea616b1b1fe0, 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: d0c86557: 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: d0c86557: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: d0c86557: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: d0c86557: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: d0c86557: 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@61e1e505[correlationID=d0c86557-439b-496e-ad03-ea616b1b1fe0, 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: d0c86557: GET_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE
Result: Received event: d0c86557: GET_FILE for file default-test-file.txt: FAILED: , Failed to get file from Pillar1, org.bitrepository.bitrepositoryelements.ResponseInfo@6d223cb2[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@13a984b0[correlationID=b6c828ca-59d2-4297-a78e-c018fed4ed95, 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: b6c828ca: 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: b6c828ca: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: b6c828ca: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: b6c828ca: 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@7c12e6e3[correlationID=b6c828ca-59d2-4297-a78e-c018fed4ed95, 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: b6c828ca: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2
Result: Received event: b6c828ca: 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@56ac955c[correlationID=b687d2ff-9d78-4141-8c5b-19782d106f6c, 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: b687d2ff: 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: b687d2ff: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Step: Wait 1 second.
Result: Received event: b687d2ff: 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: b687d2ff: GET_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
Result: Received event: b687d2ff: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: b687d2ff: 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@182631c2[correlationID=b687d2ff-9d78-4141-8c5b-19782d106f6c, 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: b687d2ff: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1
Result: Received event: b687d2ff: 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@59609d18[correlationID=cbe5d565-ff51-45c1-899e-5816293f1b2f, 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: cbe5d565: 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: cbe5d565: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: cbe5d565: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: cbe5d565: 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@591027b[correlationID=cbe5d565-ff51-45c1-899e-5816293f1b2f, 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: cbe5d565: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2
Result: Received event: cbe5d565: 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@5dfdb548[correlationID=4fb8c8d2-7093-4d15-9a8f-119f1a94bd78, 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: 4fb8c8d2: 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: 4fb8c8d2: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 4fb8c8d2: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: 4fb8c8d2: 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@5c37d3a8[correlationID=4fb8c8d2-7093-4d15-9a8f-119f1a94bd78, 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: 4fb8c8d2: GET_FILE for file default-test-file.txt: PROGRESS: ContributorID Pillar2, First test progress response message
Step: Send a GetFileFinalResponse.
Result: Received event: 4fb8c8d2: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2
Result: Received event: 4fb8c8d2: 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@28fe86da[correlationID=d1fa3abc-5836-43a9-b4c3-90e55e1e8fca, 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: d1fa3abc: 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: d1fa3abc: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: d1fa3abc: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: d1fa3abc: 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@936c949[correlationID=d1fa3abc-5836-43a9-b4c3-90e55e1e8fca, 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@30e6a3f5[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: d1fa3abc: 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: d1fa3abc: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1
Result: Received event: d1fa3abc: 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@a429406[correlationID=040f6096-591d-4fc0-a565-d6566d59900c, 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: 040f6096: GET_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetFile
Step: Wait for 1 seconds
Result: Received event: 040f6096: 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: 040f6096: GET_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor
Result: Received event: 040f6096: GET_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
Result: Received event: 040f6096: 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@3f8b8746[correlationID=b9e98efd-e6cc-4a48-bdb9-e66a77893645, 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: b9e98efd: 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: b9e98efd: 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: b9e98efd: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: b9e98efd: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: b9e98efd: 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@42c9b9f5[correlationID=b9e98efd-e6cc-4a48-bdb9-e66a77893645, 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: b9e98efd: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2
Result: Received event: b9e98efd: 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@4431e54b[correlationID=de8a8881-ad35-4f96-aa9a-087c4c177b30, 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: de8a8881: 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: de8a8881: 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: de8a8881: 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: de8a8881: 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@4b0465bd[correlationID=e0e1543f-4a5f-4e77-8b80-9ac756dc4f24, 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: e0e1543f: 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: e0e1543f: 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: e0e1543f: 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 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@5e59888e[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@3fb6d686[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@37f2f6b8[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, 10, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@58ff0c7b[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@3fb6d686[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@37f2f6b8[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], org.bitrepository.client.TestEventHandler@4a70e212, null
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileRequest@43fb1f3c[correlationID=bd7c4ab7-cf0b-4425-8e6a-7ac71947440e, 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: bd7c4ab7: 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: bd7c4ab7: 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: bd7c4ab7: REPLACE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor
Result: Received event: bd7c4ab7: 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@77e1f2a2[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@14f5137e[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@5fafcb97[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, 10, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@61d3ee02[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@14f5137e[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@5fafcb97[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], org.bitrepository.client.TestEventHandler@195f7478, null
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileRequest@250deace[correlationID=2b7b15e1-3442-4276-a257-70071c96e72b, 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: 2b7b15e1: 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: 2b7b15e1: REPLACE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 2b7b15e1: REPLACE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 2b7b15e1: 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@7a8233ec[correlationID=2b7b15e1-3442-4276-a257-70071c96e72b, 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@77e1f2a2[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@14f5137e[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@5fafcb97[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@61d3ee02[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@14f5137e[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@5fafcb97[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: 2b7b15e1: 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@3c2c5c75[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7ede2028[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@5f382a22[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, 0, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@2b96995d[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7ede2028[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@5f382a22[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], org.bitrepository.client.TestEventHandler@7507a7ae, null
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileRequest@7ad71646[correlationID=915e2a25-d8f3-4b58-95fb-2c1e2879ce5a, 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: 915e2a25: 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: 915e2a25: REPLACE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 915e2a25: REPLACE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 915e2a25: 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@7b636bbc[correlationID=915e2a25-d8f3-4b58-95fb-2c1e2879ce5a, 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@3c2c5c75[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7ede2028[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@5f382a22[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@2b96995d[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7ede2028[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@5f382a22[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: 915e2a25: REPLACE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE, Verifying that a failure can be understood!
Result: Received event: 915e2a25: REPLACE_FILE for file default-test-file.txt: FAILED: , Failed operation. Cause(s):
[915e2a25: 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@171b75ad[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6673ec27[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@31f78f06[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, 10, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@d024531[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6673ec27[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@31f78f06[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], org.bitrepository.client.TestEventHandler@4178ef21, null
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileRequest@381331fd[correlationID=a79c68f2-556c-43fe-8988-76b4ea45b0b7, 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: a79c68f2: 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: a79c68f2: REPLACE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: a79c68f2: REPLACE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: a79c68f2: 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@2aa5e608[correlationID=a79c68f2-556c-43fe-8988-76b4ea45b0b7, 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@171b75ad[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6673ec27[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@31f78f06[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@d024531[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6673ec27[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@31f78f06[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: a79c68f2: 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: a79c68f2: REPLACE_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, checksum for new file: 'org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@d024531[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6673ec27[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: a79c68f2: 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@14d212a5[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@8ba9a69[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@35cc869b[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@8ba9a69[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@26528259[checksumType=MD5, checksumSalt={-86}, otherChecksumType=<null>], org.bitrepository.client.TestEventHandler@2291fb0c, null
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileRequest@7e2454e5[correlationID=b0a6eeeb-2575-40dd-ac2f-060215ec0bb2, 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: b0a6eeeb: 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: b0a6eeeb: REPLACE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: b0a6eeeb: REPLACE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: b0a6eeeb: 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@1d7ff206[correlationID=b0a6eeeb-2575-40dd-ac2f-060215ec0bb2, 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@14d212a5[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@8ba9a69[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@35cc869b[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@8ba9a69[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 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: Random1450228791994pillar is not a valid pillar for collection TwoPillarCollection
The collection contains the following pillars: [Pillar1, Pillar2]
Test success: unknownPillarArgumentTest
Starting testcase PutFileCmdTest
Test starting: checksumArgumentNonSaltAlgorithmWitoutSaltTest
Description: Test MD5 checksum without salt -> no failure
Test success: checksumArgumentNonSaltAlgorithmWitoutSaltTest
Test starting: checksumArgumentSaltAlgorithmWithSaltTest
Description: Test HMAC_SHA256 checksum with salt -> No failure
Test success: checksumArgumentSaltAlgorithmWithSaltTest
Test starting: defaultSuccessScenarioTest
Description: Tests simplest arguments for running the CmdLineClient
Test success: defaultSuccessScenarioTest
Test starting: missingChecksumWhenFileArgumentTest
Description: Tests the scenario, where no checksum argument is given, but a file is given.
Test success: missingChecksumWhenFileArgumentTest
Test starting: missingChecksumWhenURLArgumentTest
Description: Tests the scenario, where no checksum argument is given, but a URL is given.
Invalid argument: The URL argument requires also the checksum argument (-c).
Test success: missingChecksumWhenURLArgumentTest
Test starting: missingCollectionArgumentTest
Description: Tests the scenario, where the collection arguments is missing.
Takes the following arguments:
-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: Random1450228793881pillar 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 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@113b3670, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@50d0956b[correlationID=171cdd89-2214-4870-a20d-8702f00150bb, 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@3cc70958[fileID=<null>, allFileIDs=true], checksumRequestForExistingFile=<null>]
Result: Received event: 171cdd89: 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: 171cdd89: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 171cdd89: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE
Result: Received event: 171cdd89: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 171cdd89: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar1], Sending GetFileIDsRequest's
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@7cbd373e[correlationID=171cdd89-2214-4870-a20d-8702f00150bb, 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@78346c38[fileID=<null>, allFileIDs=true], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, checksumRequestForExistingFile=<null>, resultAddress=<null>]
Step: Wait for 1 second
Result: Received event: 171cdd89: GET_CHECKSUMS: FAILED: , Failed to receive responses from all contributors before timeout(500ms). Missing contributors [Pillar1]
Test success: collectionIDIncludedInEventsTest
Test starting: conversationTimeoutTest
Description: Tests the the client handles lack of IdentifyPillarResponses gracefully
Step: Set a 100 ms ConversationTimeout.
Step: Start the operation
Stimuli: Calling getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@113b3670, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@2f7670b1[correlationID=c8fa9da5-47bf-49ce-90a7-ad358bb875ef, 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@198da7f[fileID=<null>, allFileIDs=true], checksumRequestForExistingFile=<null>]
Result: Received event: c8fa9da5: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums
02:19:55.780 WARN o.b.c.c.m.CollectionBasedConversationMediator - Failing timed out conversation c8fa9da5-47bf-49ce-90a7-ad358bb875ef (Age 1008ms)
Result: Received event: c8fa9da5: GET_CHECKSUMS: FAILED: , Failing timed out conversation c8fa9da5-47bf-49ce-90a7-ad358bb875ef
Test success: conversationTimeoutTest
Test starting: identificationFailureTest
Description: Verify that the client works correctly when a contributor sends a failure response.
Step: Start the operation.
Stimuli: Calling getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@113b3670, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@5d256ac5[correlationID=e5722ff1-b2a1-4145-ae2a-775e7443aa8a, 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@42428c94[fileID=<null>, allFileIDs=true], checksumRequestForExistingFile=<null>]
Result: Received event: e5722ff1: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums
Step: Send a identification response from contributor1 with a FAILURE response code.
Result: Received event: e5722ff1: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE
Step: Send a identification response from contributor2 with a IDENTIFICATION_POSITIVE response code .
Result: Received event: e5722ff1: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: e5722ff1: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: e5722ff1: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar2], Sending GetFileIDsRequest's
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@7d389fa7[correlationID=e5722ff1-b2a1-4145-ae2a-775e7443aa8a, 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@b3da187[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: e5722ff1: GET_CHECKSUMS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false
Result: Received event: e5722ff1: GET_CHECKSUMS: FAILED: , Failed operation. Cause(s):
[e5722ff1: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE]
Test success: identificationFailureTest
Test starting: identificationNegativeTest
Description: Verify that the client works correctly when a contributor sends a negative response.
Step: Start the operation.
Stimuli: Calling getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@113b3670, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@5a3f22c1[correlationID=7139ff53-f94f-4dbf-a1d0-787ea8ce01cb, 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@29b0c471[fileID=<null>, allFileIDs=true], checksumRequestForExistingFile=<null>]
Result: Received event: 7139ff53: 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: 7139ff53: 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: 7139ff53: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 7139ff53: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: 7139ff53: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar2], Sending GetFileIDsRequest's
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@1fbde260[correlationID=7139ff53-f94f-4dbf-a1d0-787ea8ce01cb, 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@3cb7e27c[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: 7139ff53: GET_CHECKSUMS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false
Result: Received event: 7139ff53: GET_CHECKSUMS: FAILED: , Failed operation. Cause(s):
[7139ff53: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: IDENTIFICATION_NEGATIVE]
Test success: identificationNegativeTest
Test starting: noContributorsRespondingTest
Description: Tests the the client handles lack of a IdentifyResponse gracefully. More concrete this means that the occurrence of a identification timeout should be handled correctly
Step: Set a 100 ms timeout for identifying contributors.
Step: Start the operation.
Stimuli: Calling getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@113b3670, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@65ea5213[correlationID=35ef45d1-bca6-43f1-96d4-18bfd2541634, 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@59d98859[fileID=<null>, allFileIDs=true], checksumRequestForExistingFile=<null>]
Result: Received event: 35ef45d1: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums
Step: Wait for 1 second
Result: Received event: 35ef45d1: GET_CHECKSUMS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar1, Pillar2]
Result: Received event: 35ef45d1: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor
Result: Received event: 35ef45d1: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
Result: Received event: 35ef45d1: 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@65ea5213[correlationID=35ef45d1-bca6-43f1-96d4-18bfd2541634, 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@59d98859[fileID=<null>, allFileIDs=true], checksumRequestForExistingFile=<null>]
02:19:58.285 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@65ea5213[correlationID=35ef45d1-bca6-43f1-96d4-18bfd2541634, 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@59d98859[fileID=<null>, allFileIDs=true], checksumRequestForExistingFile=<null>]
Test starting: oneContributorNotRespondingTest
Description: Verify that the client works correct without receiving identification responses from all contributors.
Added fixture: Set the a identification timeout to 100 ms.
Step: Start the operation.
Stimuli: Calling getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@113b3670, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@32b08e35[correlationID=cfbd3349-ce08-4919-a682-81fd6eb0c97e, 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@7796b952[fileID=<null>, allFileIDs=true], checksumRequestForExistingFile=<null>]
Result: Received event: cfbd3349: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums
Step: Send a identification response from contributor1.
Result: Received event: cfbd3349: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Step: Wait 1 second.
Result: Received event: cfbd3349: GET_CHECKSUMS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar2]
Result: Received event: cfbd3349: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
Result: Received event: cfbd3349: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: cfbd3349: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar1], Sending GetFileIDsRequest's
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@49fabe82[correlationID=cfbd3349-ce08-4919-a682-81fd6eb0c97e, 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@496ac5f6[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: cfbd3349: GET_CHECKSUMS: COMPONENT_COMPLETE: ContributorID Pillar1, PartialResult=false
Result: Received event: cfbd3349: GET_CHECKSUMS: FAILED: , Failed operation. Cause(s):
[cfbd3349: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor]
Test success: oneContributorNotRespondingTest
Test starting: operationTimeoutTest
Description: Tests the the client handles lack of final responses gracefully.
Step: Set a 100 ms operation timeout.
Step: Start the operation
Stimuli: Calling getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@113b3670, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@5d1416ce[correlationID=005af70b-e8c7-4436-9030-17fd03a10803, 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@749cad34[fileID=<null>, allFileIDs=true], checksumRequestForExistingFile=<null>]
Result: Received event: 005af70b: 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: 005af70b: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 005af70b: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE
Result: Received event: 005af70b: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 005af70b: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar1], Sending GetFileIDsRequest's
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@4c2bfb2b[correlationID=005af70b-e8c7-4436-9030-17fd03a10803, 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@31f42606[fileID=<null>, allFileIDs=true], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, checksumRequestForExistingFile=<null>, resultAddress=<null>]
Step: Wait for 1 second
Result: Received event: 005af70b: GET_CHECKSUMS: FAILED: , Failed to receive responses from all contributors before timeout(100ms). Missing contributors [Pillar1]
Test success: operationTimeoutTest
Test starting: getChecksumsDeliveredAtUrl
Description: Tests the delivery of checksums from all pillars at a given URL.
Step: Ensure the delivery file isn't already present on the http server
Step: Request the delivery of the checksum of a file from all pillars.
Stimuli: Calling getChecksums(null, default-test-file.txt, null, file:../bitrepository-core/src/test/resources/test-files//TEST-CHECKSUM-DELIVERY.xml, org.bitrepository.client.TestEventHandler@b030da9, TEST-AUDIT)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@4fc61fd4[correlationID=4aa36f5b-e5a9-4a83-8375-4511087b50e9, 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@4a06f0c7[fileID=default-test-file.txt, allFileIDs=<null>], checksumRequestForExistingFile=<null>]
Result: Received event: 4aa36f5b: 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: 4aa36f5b: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 4aa36f5b: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 4aa36f5b: GET_CHECKSUMS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2]
Result: Received event: 4aa36f5b: 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@7c0e06c7[correlationID=4aa36f5b-e5a9-4a83-8375-4511087b50e9, 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@1734149[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@3433e418[correlationID=4aa36f5b-e5a9-4a83-8375-4511087b50e9, 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@7bbb9c72[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: 4aa36f5b: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, NumberOfChecksums=0, PartialResult=false
Result: Received event: 4aa36f5b: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2, NumberOfChecksums=0, PartialResult=false
Result: Received event: 4aa36f5b: 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@3433e418[correlationID=4aa36f5b-e5a9-4a83-8375-4511087b50e9, 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@7bbb9c72[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:58.755 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.GetChecksumsRequest@3433e418[correlationID=4aa36f5b-e5a9-4a83-8375-4511087b50e9, 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@7bbb9c72[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@38e6ab22, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@1709ca1[correlationID=f96b7989-d300-4471-b3b4-6bbcb78de919, 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@35db021a[fileID=<null>, allFileIDs=true], checksumRequestForExistingFile=<null>]
Result: Received event: f96b7989: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums
Step: Send an identification response from pillar2.
Result: Received event: f96b7989: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: f96b7989: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: f96b7989: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar2], Sending GetFileIDsRequest's
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@5d9d0e67[correlationID=f96b7989-d300-4471-b3b4-6bbcb78de919, 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@580d14e1[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: f96b7989: GET_CHECKSUMS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false
Result: Received event: f96b7989: 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@8250eac[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], null, org.bitrepository.client.TestEventHandler@1f9c2844, TEST-AUDIT)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@367c0690[correlationID=a146031c-e118-4a76-a62d-8ccd096a2402, 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@3b51543[fileID=default-test-file.txt, allFileIDs=<null>], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@8250eac[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>]]
Result: Received event: a146031c: 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: a146031c: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: a146031c: GET_CHECKSUMS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: a146031c: 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@5d65e9d3[correlationID=a146031c-e118-4a76-a62d-8ccd096a2402, 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@b7b3c69[fileID=default-test-file.txt, allFileIDs=<null>], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@8250eac[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], resultAddress=<null>]
Step: Send a GetChecksumsFinalResponse to the client from pillar1
Result: Received event: a146031c: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, NumberOfChecksums=0, PartialResult=false
Result: Received event: a146031c: 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@2549c297, TEST-AUDIT)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@4f8edb57[correlationID=21a81c39-cb57-492c-bc8b-b4cca2ca1db9, 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@163d9ea1[fileID=default-test-file.txt, allFileIDs=<null>], checksumRequestForExistingFile=<null>]
Result: Received event: 21a81c39: 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: 21a81c39: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 21a81c39: GET_CHECKSUMS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 21a81c39: 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@53df16bf[correlationID=21a81c39-cb57-492c-bc8b-b4cca2ca1db9, 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@6ab23bf0[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: 21a81c39: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FILE_NOT_FOUND_FAILURE, No such file.
Result: Received event: 21a81c39: GET_CHECKSUMS for file default-test-file.txt: FAILED: , Failed operation. Cause(s):
[21a81c39: 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=Wed Dec 16 02:19:59 CET 2015, maxTimestamp=Wed Dec 16 02:20:00 CET 2015, maxNumberOfResults=1}, ContributorQuery{componentID='Pillar2, minTimestamp=Wed Dec 16 02:20:00 CET 2015, maxTimestamp=Wed Dec 16 02:20:00 CET 2015, maxNumberOfResults=2}], null, null, null, org.bitrepository.client.TestEventHandler@113b3670, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@339d8dc2[correlationID=7c4c5418-f6ab-4bf6-a2ff-3525bdadf67b, 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@3307d4f[fileID=<null>, allFileIDs=true], checksumRequestForExistingFile=<null>]
Result: Received event: 7c4c5418: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums
Step: Send a IdentifyPillarsForGetChecksumsResponse from both pillars.
Result: Received event: 7c4c5418: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 7c4c5418: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 7c4c5418: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2]
Result: Received event: 7c4c5418: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending GetFileIDsRequest's
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@4ce61b67[correlationID=7c4c5418-f6ab-4bf6-a2ff-3525bdadf67b, 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@4cbccdb1[fileID=<null>, allFileIDs=true], minTimestamp=2015-12-16T02:19:59.409+01:00, maxTimestamp=2015-12-16T02:20:00.309+01:00, maxNumberOfResults=1, checksumRequestForExistingFile=<null>, resultAddress=<null>]
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@1c896d2c[correlationID=7c4c5418-f6ab-4bf6-a2ff-3525bdadf67b, 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@5cb9f193[fileID=<null>, allFileIDs=true], minTimestamp=2015-12-16T02:20:00.309+01:00, maxTimestamp=2015-12-16T02:20:00.409+01:00, maxNumberOfResults=2, checksumRequestForExistingFile=<null>, resultAddress=<null>]
Test success: testPaging
Test starting: verifyGetChecksumsClientFromFactory
Test success: verifyGetChecksumsClientFromFactory
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
Finished testcase
Finished suite
Finished project
Tests run: 156, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 63.365 sec - in TestSuite
Results :
Tests run: 156, Failures: 0, Errors: 0, Skipped: 0
[JENKINS] Recording test results
[INFO]
[INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ bitrepository-client ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/target/bitrepository-client-1.6-SNAPSHOT.jar
[INFO]
[INFO] --- maven-jar-plugin:2.4:test-jar (default) @ bitrepository-client ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/target/bitrepository-client-1.6-SNAPSHOT-tests.jar
[INFO]
[INFO] --- maven-source-plugin:2.2.1:jar-no-fork (attach-sources-no-fork) @ bitrepository-client ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/target/bitrepository-client-1.6-SNAPSHOT-sources.jar
[INFO]
[INFO] --- maven-assembly-plugin:2.4:single (make-assembly) @ bitrepository-client ---
[INFO] Reading assembly descriptor: src/main/assembly/assembly.xml
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/target/bitrepository-client-1.6-SNAPSHOT-distribution.tar.gz
[INFO]
[INFO] --- maven-install-plugin:2.5.1:install (default-install) @ bitrepository-client ---
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/target/bitrepository-client-1.6-SNAPSHOT.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-client/1.6-SNAPSHOT/bitrepository-client-1.6-SNAPSHOT.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-client/1.6-SNAPSHOT/bitrepository-client-1.6-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/target/bitrepository-client-1.6-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-client/1.6-SNAPSHOT/bitrepository-client-1.6-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/target/bitrepository-client-1.6-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-client/1.6-SNAPSHOT/bitrepository-client-1.6-SNAPSHOT-sources.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/target/bitrepository-client-1.6-SNAPSHOT-distribution.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-client/1.6-SNAPSHOT/bitrepository-client-1.6-SNAPSHOT-distribution.tar.gz
[JENKINS] Archiving disabled
Console Output
Help us localize this page