Started by an SCM change Building remotely on Local activeMQ in workspace /home/cibuild01/workspace/Bitrepository-sonar > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url https://github.com/bitrepository/reference.git # timeout=10 Fetching upstream changes from https://github.com/bitrepository/reference.git > git --version # timeout=10 > git -c core.askpass=true fetch --tags --progress https://github.com/bitrepository/reference.git +refs/heads/master:refs/remotes/origin/master > git rev-parse refs/remotes/origin/master^{commit} # timeout=10 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10 Checking out Revision 80e546352271c45a5b14a7dd980a5dad62b1f935 (refs/remotes/origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 80e546352271c45a5b14a7dd980a5dad62b1f935 > git rev-list dfe9574a943d862e20af50db6ee09fda3e6d1603 # timeout=10 > git tag -a -f -m Jenkins Build #73 jenkins-Bitrepository-sonar-73 # timeout=10 Parsing POMs Modules changed, recalculating dependency graph Established TCP socket on 60315 maven32-agent.jar already up to date maven32-interceptor.jar already up to date maven3-interceptor-commons.jar already up to date [Bitrepository-sonar] $ /usr/java/java-1.8.0-oracle-1.8.0.11.x86_64/bin/java -Xmx512m -XX:MaxPermSize=128m -cp /home/cibuild01/maven32-agent.jar:/home/cibuild01/tools/hudson.tasks.Maven_MavenInstallation/Maven3.2/boot/plexus-classworlds-2.5.1.jar:/home/cibuild01/tools/hudson.tasks.Maven_MavenInstallation/Maven3.2/conf/logging jenkins.maven3.agent.Maven32Main /home/cibuild01/tools/hudson.tasks.Maven_MavenInstallation/Maven3.2 /home/cibuild01/slave.jar /home/cibuild01/maven32-interceptor.jar /home/cibuild01/maven3-interceptor-commons.jar 60315 Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=128m; support was removed in 8.0 <===[JENKINS REMOTING CAPACITY]===>channel started Executing Maven: -B -f /home/cibuild01/workspace/Bitrepository-sonar/pom.xml clean install [INFO] Scanning for projects... [INFO] ------------------------------------------------------------------------ [INFO] Reactor Build Order: [INFO] [INFO] Bitrepository [INFO] Bitrepository Reference Settings [INFO] Bitrepository Core [INFO] Bitrepository Client [INFO] Bitrepository Service [INFO] Bitrepository Integrity Service [INFO] Bitrepository Alarm Service [INFO] Bitrepository Audit Trail Service [INFO] Bitrepository Reference Pillar [INFO] Bitrepository Monitoring Service [INFO] Bitrepository Webclient [INFO] Bitrepository Integration [INFO] [INFO] Using the builder org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder with a thread count of 1 [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building Bitrepository 1.6-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-parent --- [INFO] Deleting /home/cibuild01/workspace/Bitrepository-sonar/target [INFO] [INFO] --- maven-jar-plugin:2.4:test-jar (default) @ bitrepository-parent --- [WARNING] JAR will be empty - no content was marked for inclusion! [INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/target/bitrepository-parent-1.6-SNAPSHOT-tests.jar [INFO] [INFO] --- maven-source-plugin:2.2.1:jar-no-fork (attach-sources-no-fork) @ bitrepository-parent --- [INFO] [INFO] --- maven-install-plugin:2.5.1:install (default-install) @ bitrepository-parent --- [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-parent/1.6-SNAPSHOT/bitrepository-parent-1.6-SNAPSHOT.pom [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/target/bitrepository-parent-1.6-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-parent/1.6-SNAPSHOT/bitrepository-parent-1.6-SNAPSHOT-tests.jar [JENKINS] Archiving disabled [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building Bitrepository Reference Settings 1.6-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-reference-settings --- [INFO] Deleting /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-settings/target [INFO] [INFO] --- maven-resources-plugin:2.6:copy-resources (copy-resources) @ bitrepository-reference-settings --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 2 resources [INFO] [INFO] --- maven-jaxb2-plugin:0.11.0:generate (generate-classes-from-xsds) @ bitrepository-reference-settings --- [INFO] Sources are not up-to-date, XJC will be executed. [INFO] [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ bitrepository-reference-settings --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 2 resources [INFO] Copying 1 resource [INFO] Copying 1 resource [INFO] [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ bitrepository-reference-settings --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 38 source files to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-settings/target/classes [INFO] [INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ bitrepository-reference-settings --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-settings/src/test/resources [INFO] [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ bitrepository-reference-settings --- [INFO] No sources to compile [INFO] [INFO] --- maven-surefire-plugin:2.17:test (default-test) @ bitrepository-reference-settings --- [INFO] No tests to run. [JENKINS] Recording test results [INFO] [INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ bitrepository-reference-settings --- [INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-settings/target/bitrepository-reference-settings-1.6-SNAPSHOT.jar [INFO] [INFO] --- maven-jar-plugin:2.4:test-jar (default) @ bitrepository-reference-settings --- [WARNING] JAR will be empty - no content was marked for inclusion! [INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-settings/target/bitrepository-reference-settings-1.6-SNAPSHOT-tests.jar [INFO] [INFO] --- maven-source-plugin:2.2.1:jar-no-fork (attach-sources-no-fork) @ bitrepository-reference-settings --- [INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-settings/target/bitrepository-reference-settings-1.6-SNAPSHOT-sources.jar [INFO] [INFO] --- maven-install-plugin:2.5.1:install (default-install) @ bitrepository-reference-settings --- [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-settings/target/bitrepository-reference-settings-1.6-SNAPSHOT.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-settings/1.6-SNAPSHOT/bitrepository-reference-settings-1.6-SNAPSHOT.jar [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-settings/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-settings/1.6-SNAPSHOT/bitrepository-reference-settings-1.6-SNAPSHOT.pom [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-settings/target/bitrepository-reference-settings-1.6-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-settings/1.6-SNAPSHOT/bitrepository-reference-settings-1.6-SNAPSHOT-tests.jar [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-settings/target/bitrepository-reference-settings-1.6-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-settings/1.6-SNAPSHOT/bitrepository-reference-settings-1.6-SNAPSHOT-sources.jar [JENKINS] Archiving disabled [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building Bitrepository Core 1.6-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-core --- [INFO] Deleting /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-core/target [INFO] [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ bitrepository-core --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 2 resources [INFO] [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ bitrepository-core --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 89 source files to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-core/target/classes [INFO] [INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ bitrepository-core --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 11 resources [INFO] [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ bitrepository-core --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 62 source files to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-core/target/test-classes [INFO] [INFO] --- maven-surefire-plugin:2.17:test (default-test) @ bitrepository-core --- [INFO] Surefire report directory: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-core/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 ArgumentValidatorTest Test starting: testArgumentValidatorArrays Description: Test the argument validator for arguments for arrays Step: Check against null or empty arrays Test success: testArgumentValidatorArrays Test starting: testArgumentValidatorBoolean Description: Test the argument validator for arguments for booleans Step: validate checkTrue Test success: testArgumentValidatorBoolean Test starting: testArgumentValidatorCollection Description: Test the argument validator for arguments for collections Step: Check against null or empty collection Test success: testArgumentValidatorCollection Test starting: testArgumentValidatorInteger Description: Test the argument validator for arguments for integers Step: Test not negative Step: Test positive Test success: testArgumentValidatorInteger Test starting: testArgumentValidatorLong Description: Test the argument validator for arguments for longs Step: Test not negative Step: Test positive Test success: testArgumentValidatorLong Test starting: testArgumentValidatorObject Description: Test the argument validator for arguments not null Step: Test not null Test success: testArgumentValidatorObject Test starting: testArgumentValidatorString Description: Test the argument validator for arguments for strings Step: Test empty string Test success: testArgumentValidatorString Test starting: utilityTester Description: Test that the utility class is a proper utility class. Test success: utilityTester Starting testcase CertificateIDTest Test starting: equalTest Description: Tests the equality of CertificateIDs Step: Setup Step: Validate the content of the certificateID Step: Test whether it equals it self Step: Test with a null as argument Step: Test with another class Step: Test with same issuer but no serial Step: Test with same serial but no issuer Step: Test the positive case, with both the issuer and serial Step: Setup an empty certificate Step: Test empty certificate against issuer but no serial Step: Test empty certificate against serial but no issuer Step: Test empty certificate against serial and issuer Step: Test the positive case, with neither issuer nor serial Step: Check the hash codes for the two certificate Test success: equalTest Test starting: negativeCertificateIdentificationTest Description: Tests that a certificate is not identified based on a incorrect signature. Step: Create CertificateID object based on a certificate not used for signing the data Step: Create CertificateID object based on signature Step: Assert that the two CertificateID objects are equal Test success: negativeCertificateIdentificationTest Test starting: positiveCertificateIdentificationTest Description: Tests that a certificate can be identified based on the correct signature. Step: Create CertificateID object based on the certificate used to sign the data Step: Create CertificateID object based on signature Step: Assert that the two CertificateID objects are equal Test success: positiveCertificateIdentificationTest Starting testcase ChecksumUtilsTest Test starting: calculateDigestChecksums Description: Tests whether the utility class for calculating checksums with MessageDigest is able to correctly calculate the checksums. Step: Setup variables. Step: Test with no text and no key for MD5, SHA1, and SHA256 Step: Test with text Step: add a salt to the checksum Test success: calculateDigestChecksums Test starting: calculateHmacChecksums Description: Tests whether the utility class for calculating checksums with HMAC is able to correctly calculate predefined examples from : http://en.wikipedia.org/wiki/HMAC#Examples_of_HMAC_.28MD5.2C_SHA1.2C_SHA256_.29 Step: Setup variables. Step: Test with no text and no key for HMAC_MD5, HMAC_SHA1, and HMAC_SHA256 Step: Test with the text 'The quick brown fox jumps over the lazy dog' and key 'key' for MD5, SHA1, and SHA256 Step: Try calculating HMAC with a null salt Test success: calculateHmacChecksums Test starting: testChecksumAlgorithmValidation Description: Test the algorithm validation for every single possible checksum algorithm. Step: Test 'MD5' Step: Test 'SHA1' Step: Test 'SHA256' Step: Test 'SHA384' Step: Test 'SHA512' Step: Test 'HMAC_MD5' Step: Test 'HMAC_SHA1' Step: Test 'HMAC_SHA256' Step: Test 'HMAC_SHA384' Step: Test 'HMAC_SHA512' Step: Test 'OTHER' Test success: testChecksumAlgorithmValidation Test starting: testChecksumOnFile Description: Test the checksum calculation on a file Step: Setup Step: Calculate the checksum of the file with the different ways of defining the MD5 without salt Test success: testChecksumOnFile Test starting: testDefaultChecksum Description: Test the extraction of the default checksum from settings. Step: Setup the settings Step: Use utils to extract default checksum spec Test success: testDefaultChecksum Test starting: utilityTester Description: Test that the utility class is a proper utility class. Test success: utilityTester Starting testcase FileUtilsTest Test starting: createDeleteDirectoryTester Description: Test the ability to delete directories. Step: Test deleting a directory with file and subdirectory Test success: createDeleteDirectoryTester Test starting: createDirectoryTester Description: Test the ability to create directories. Step: Test the ability to create a directory Step: Test error scenarios, when the directory path is a file Test success: createDirectoryTester Test starting: createSubDirectoryTester Description: Test the ability to create sub directories. Step: Test the ability to create sub-directories Step: Test that it fails if the 'directory' is actually a file Step: Test that it fails, if the parent directory does not allow writing Test success: createSubDirectoryTester Test starting: deprecateFileTester Description: Test the deprecation of a file. Step: Setup Step: Deprecate the file Test success: deprecateFileTester Test starting: moveFileTester Description: Test the moving of a file. Step: Setup Step: Move the file Test success: moveFileTester Test starting: unzipFileTester Description: Test unzipping a file. Step: Setup Step: Unzip the zipfile to the directory Test success: unzipFileTester Test starting: utilityTester Description: Test that the utility class is a proper utility class. Test success: utilityTester Test starting: writeInputstreamTester Description: Test writing an inputstream to a file. Step: Setup Step: Write the input stream to the file Test success: writeInputstreamTester Starting testcase GeneralMessageBusTest Test starting: busActivityTest Description: Tests whether it is possible to create a message listener, and then set it to listen to the topic. Then puts a messageon the topic for the message listener to find, andtests whether it finds the correct message. Step: Send a message to the topic Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@2a7686a7[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@758a34ce[origDateTime=2011-05-03T11:18:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=]] Step: Make sure both listeners received the message Test success: busActivityTest Test starting: twoListenersForTopicTest Description: Verifies that two listeners on the same topic both receive the message Step: Make a connection to the message bus and add two listeners Step: Send a message to the topic Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@4816c290[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@4940809c[origDateTime=2011-05-03T11:18:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=]] Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@4816c290[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@4940809c[origDateTime=2011-05-03T11:18:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=]] Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@4816c290[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@4940809c[origDateTime=2011-05-03T11:18:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=]] Step: Make sure both listeners received the message Test success: twoListenersForTopicTest Result: The following messages haven't been handled by the testcase: org.bitrepository.bitrepositorymessages.AlarmMessage@4816c290[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@4940809c[origDateTime=2011-05-03T11:18:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=]] 02:17:59.727 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: org.bitrepository.bitrepositorymessages.AlarmMessage@4816c290[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@4940809c[origDateTime=2011-05-03T11:18:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=]] Test starting: utilityTester Description: Test that the utility class is a proper utility class. Test success: utilityTester Starting testcase HttpFileExchangeTest Test starting: checkUrlEncodingOfFilenamesTest Description: Tests that the filename is url-encoded correctly for a configured webdav server Step: Check plain filename (a filename that does not see any changes due to urlencoding Step: Check that + is encoded as expected Test success: checkUrlEncodingOfFilenamesTest Starting testcase MessageAuthenticationExceptionTest Test starting: testMessageAuthenticationException 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: testMessageAuthenticationException Starting testcase OperationAuthorizationExceptionTest Test starting: testOperationAuthorizationException 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: testOperationAuthorizationException Starting testcase TimeUtilsTest Test starting: shortDateTest Test success: shortDateTest Test starting: timeTester Description: Tests the TimeUtils. Pi days = 271433605 milliseconds Step: Test that milliseconds can be converted into human readable seconds Step: Test that milliseconds can be converted into human readable minutes. Step: Test that milliseconds can be converted into human readable hours. Step: Test that milliseconds can be converted into human readable minutes. Step: Test the human readable output. Test success: timeTester Test starting: utilityTester Description: Test that the utility class is a proper utility class. Test success: utilityTester Test starting: zeroIntervalTest Description: Verifies that a 0 ms interval is represented correctly Step: Call the millisecondsToHuman with 0 ms Test success: zeroIntervalTest Starting testcase UnableToFinishExceptionTest Test starting: testUnableToFinish 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: testUnableToFinish Starting testcase ActiveMQMessageBusTest 02:18:01.408 WARN o.a.activemq.broker.BrokerService - Memory Usage for the Broker (1024 mb) is more than the maximum available for the JVM: 487 mb - resetting to 70% of maximum available: 341 mb 02:18:01.409 WARN o.a.activemq.broker.BrokerService - Temporary Store limit is 51200 mb (current temporary store usage is 0 mb). The temporary data directory: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-core/target only has 10973 mb of usable space - resetting to maximum available disk space: 10973 mb Test starting: collectionFilterTest Description: Test that message bus filters identify requests to other collection, eg. ignores these. Step: Send an identify request with a undefined 'Collection' header property, eg. this identify requests should be handled by everybody. Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@45fd6df9[correlationID=12345, collectionID=MyCollection, destination=topic://collectionTopic, replyTo=topic://clientTopic, from=ClientPillar, to=, version=28, minVersion=24, auditTrailInformation=User: Name, Institution: Place, fileID=MyDataID] Step: Send an identify request with the 'Collection' header property set to my collection Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@4b3a9b36[correlationID=12345, collectionID=MyCollection, destination=topic://collectionTopic, replyTo=topic://clientTopic, from=ClientPillar, to=, version=28, minVersion=24, auditTrailInformation=User: Name, Institution: Place, fileID=MyDataID] Step: Send an invalid message with the 'Receiver' header property set to another specific component Test success: collectionFilterTest Test starting: sendMessageToSpecificComponentTest Description: Test that message bus correct uses the 'to' header property to indicated that the message is meant for a specific component Step: Send a message with the 'Recipient' parameter set to at specific component Stimuli: Sending message: org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@7a0e7ecd[correlationID=12345, collectionID=MySla, destination=TEST-TOPIC-cibuild01, replyTo=topic://clientTopic, from=ClientPillar, to=specificReceiver, version=28, minVersion=24, auditTrailInformation=User: Name, Institution: Place, fileID=MyDataID] Test success: sendMessageToSpecificComponentTest Test starting: toFilterTest Description: Test that message bus filters identify requests to other components, eg. ignores these. Step: Send an identify request with a undefined 'To' header property, eg. this identify requests should be handled by all components. Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@4f050689[correlationID=12345, collectionID=MySla, destination=TEST-TOPIC-cibuild01, replyTo=topic://clientTopic, from=ClientPillar, to=, version=28, minVersion=24, auditTrailInformation=User: Name, Institution: Place, fileID=MyDataID] Step: Send an identify request with the 'To' header property set to this component Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@5e2a3560[correlationID=12345, collectionID=MySla, destination=TEST-TOPIC-cibuild01, replyTo=topic://clientTopic, from=ClientPillar, to=, version=28, minVersion=24, auditTrailInformation=User: Name, Institution: Place, fileID=MyDataID] Step: Send an invalid identify request with the 'To' header property set to another specific component Step: Send an identify response with the 'To' header property set to another component Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileResponse@50edc0d5[correlationID=12345, collectionID=MySla, destination=topic://collectionTopic, replyTo=topic://clientTopic, from=MyPillar, to=, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@54d25e10[responseCode=IDENTIFICATION_POSITIVE, responseText=Ready to delete file 'MyDataID'.], fileID=MyDataID, pillarID=MyPillar, pillarChecksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@11d0caee[checksumType=MD5, checksumSalt={-85,-51}, otherChecksumType=], timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@1e5e6c81[timeMeasureUnit=MILLISECONDS, timeMeasureValue=1000]] Step: Send an non-identify request with the 'To' header property set to another component Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.DeleteFileRequest@200bfcf7[correlationID=12345, collectionID=MySla, destination=TEST-TOPIC-cibuild01, replyTo=topic://clientTopic, from=ClientPillar, to=, version=28, minVersion=24, auditTrailInformation=User: Name, Institution: Place, pillarID=MyPillar, fileID=MyDataID, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@2c4c0270[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@5c77bf8d[checksumType=MD5, checksumSalt={-85,-85}, otherChecksumType=], checksumValue={19,95,33,86}, calculationTimestamp=2011-02-17T09:47:00], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@5f2544eb[checksumType=MD5, checksumSalt={-85,-51}, otherChecksumType=]] Test success: toFilterTest Starting testcase CertificateUseExceptionTest Test starting: testCertificateUseException 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: testCertificateUseException Starting testcase ConfigLoaderTest Test starting: testLoadingConfig Description: Test the loading of a configuration file for the config loader. Step: Setup variables Step: Test with a invalid file path Step: Test when the file is unreadable Step: success case Test success: testLoadingConfig Starting testcase FileIDUtilsTest Test starting: fileIDsTest Description: Test the utility class for generating FileIDs Step: Test 'all file ids' Step: Test a specific file id Test success: fileIDsTest Test starting: utilityTester Description: Test that the utility class is a proper utility class. Test success: utilityTester Test starting: busActivityTest Description: Tests whether it is possible to create a message listener, and then set it to listen to the topic. Then puts a messageon the topic for the message listener to find, andtests whether it finds the correct message. Step: Send a message to the topic Stimuli: Sending message: org.bitrepository.bitrepositorymessages.AlarmMessage@291a4791[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@5b1e88f[origDateTime=2011-05-03T11:18:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=]] Step: Make sure both listeners received the message Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@666f0438[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@4f367c45[origDateTime=2011-05-03T11:18:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=]] Test success: busActivityTest Test starting: twoListenersForTopicTest Description: Verifies that two listeners on the same topic both receive the message Step: Make a connection to the message bus and add two listeners Step: Send a message to the topic Stimuli: Sending message: org.bitrepository.bitrepositorymessages.AlarmMessage@267ff4df[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@7c4b5ceb[origDateTime=2011-05-03T11:18:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=]] Step: Make sure both listeners received the message Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@71ff35a1[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@6fff1c8b[origDateTime=2011-05-03T11:18:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=]] Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@1ca8657b[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@5c123e18[origDateTime=2011-05-03T11:18:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=]] Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@633bce5d[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@76000ffb[origDateTime=2011-05-03T11:18:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=]] Test success: twoListenersForTopicTest Result: The following messages haven't been handled by the testcase: org.bitrepository.bitrepositorymessages.AlarmMessage@71ff35a1[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@6fff1c8b[origDateTime=2011-05-03T11:18:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=]] 02:18:13.781 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: org.bitrepository.bitrepositorymessages.AlarmMessage@71ff35a1[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@6fff1c8b[origDateTime=2011-05-03T11:18:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=]] Test starting: utilityTester Description: Test that the utility class is a proper utility class. Test success: utilityTester Starting testcase ReceivedMessageHandlerTest Test starting: manyMessageDispatch Description: Tests that many (50) messages can be handled in parallel in the default pool configuration. Added fixture: Create a ReceivedMessageHandler with a null configuration. This should create a ReceivedMessageHandler with a single CachedThreadPool. Step: Dispatch messages to 49 listeners, where the first 49 are blocking. Step: Unblock the blocked listeners Test success: manyMessageDispatch Test starting: parallelMessageDispatch Description: Tests that two messages can be handled in parallel in the default pool configuration. Added fixture: Create a ReceivedMessageHandler with a null configuration. This should create a ReceivedMessageHandler with a single CachedThreadPool. Step: Dispatch messages to two listeners, the first blocking. Step: Unblock the first listener Test success: parallelMessageDispatch Test starting: singleMessageDispatch Description: Tests that a single message is dispatched correctly Test success: singleMessageDispatch Test starting: singleThreadMessageDispatch Description: Tests that two messages will be handled in sequence if a singleThreaded pool is configured. Added fixture: Create a ReceivedMessageHandler with a single pool of size 1. Step: Dispatch messages to two listeners, the first blocking. Step: Unblock the first listener Test success: singleThreadMessageDispatch Test starting: specificCollectionPoolAndDefaultPool Description: Tests it is possible to specify a pool for a specific collection, with a default pool for the remainder. Added fixture: Create a ReceivedMessageHandler with a one specific pool for Collection1. The Collection1 pool should be limited to 1 thread. Step: Dispatch two messages for collection1, blocking on the processing of the first message. Step: Dispatch a message for the other collection. Step: Dispatch a message with no collectionID. Step: Unblock the blocked collection1 listener Test success: specificCollectionPoolAndDefaultPool Test starting: specificCollectionPoolWithSpecificMessageTypePool Description: Tests it is possible to specify a pool for a specific collection for only a specificmessage type. Added fixture: Create a ReceivedMessageHandler with a one specific pool for Collection1 and PutFileRequests. The pool should be limited to 1 thread. Step: Dispatch two putFileRequests for collection1, blocking on the processing of the first message. Step: Dispatch a putFile request for the other collection. Step: Dispatch a status request for collection1. Step: Unblock the blocked collection1 listener Test success: specificCollectionPoolWithSpecificMessageTypePool Test starting: specificMessageCategoryPoolAndDefaultPool Description: Tests it is possible to specify a pool for a specific message category, with a default pool for the remainder. Added fixture: Create a ReceivedMessageHandler with a one specific pool for slow requests. The put file pool should be limited to 1 thread. Step: Dispatch two put messages, blocking on the processing of the first message. Step: Dispatch a status request message. Step: Unblock the blocked put listener Test success: specificMessageCategoryPoolAndDefaultPool Test starting: specificMessageNamePoolAndDefaultPool Description: Tests it is possible to specify a pool for a specific message type, with a default pool for the remainder. Added fixture: Create a ReceivedMessageHandler with a one specific pool for put requests. The put file pool should be limited to 1 thread. Step: Dispatch two put messages, blocking on the processing of the first message. Step: Dispatch a status request message. Step: Unblock the blocked put listener Test success: specificMessageNamePoolAndDefaultPool Test starting: specificMessagePools Description: Tests that different message types can be handled by different executors. Added fixture: Create a ReceivedMessageHandler with a two pools, one for status requests and one for put requests. The put file pool should be limited to 1 thread. Step: Dispatch two put messages, blocking on the processing of the first message. Step: Dispatch a status request message. Step: Unblock the blocked put listener Test success: specificMessagePools Starting testcase SettingsLoaderTest Test starting: testDevelopmentCollectionSettingsLoading Test success: testDevelopmentCollectionSettingsLoading Test starting: testExampleSettingsLoading Test success: testExampleSettingsLoading Test starting: componentIDTest Test success: componentIDTest Test starting: reloadTest Test success: reloadTest Starting testcase Base16UtilsTest Test starting: badArgumentTest Description: Test bad arguments Step: Test with a odd number of characters. Test success: badArgumentTest Test starting: decodeChecksum Description: Validating the decoding of the checksums. Step: Decode the checksum and validate. Test success: decodeChecksum Test starting: encodeChecksum Description: Validating the encoding of the checksums. Step: Encode the checksum and validate Test success: encodeChecksum Test starting: utilityTester Description: Test that the utility class is a proper utility class. Test success: utilityTester Starting testcase PermissionStoreTest Test starting: certificateFingerprintTest Description: Tests that a certificate fingerprint can correctly be retrived for a signer. Added fixture: Create signer to lookup fingerprint Step: Lookup fingerprint based on signerId Test success: certificateFingerprintTest Test starting: negativeCertificateRetrievalTest Description: Tests that a certificate cannot be retrieved based on the wrong signerId. Step: Create signer and modify its ID so lookup will fail Step: Lookup certificate based on signerId Test success: negativeCertificateRetrievalTest Test starting: positiveCertificateRetrievalTest Description: Tests that a certificate can be retrieved based on the correct signerId. Step: Create signer to lookup certificate Step: Lookup certificate based on signerId Test success: positiveCertificateRetrievalTest Starting testcase SecurityManagerTest Test starting: certificateAuthorizationBehaviourTest Description: Tests that a certificate is only allowed by registered users (component). Step: Check that the registered component is allowed. Step: Check that an unregistered component is not allowed. Test success: certificateAuthorizationBehaviourTest Test starting: negativeSigningAuthenticationRoundtripBadDataTest Description: Tests that a roundtrip of signing a request and afterwards authenticating it fails due to bad data Description: Tests that a roundtrip of signing a request and afterwards authenticating is succedes. Step: Sign a chunck of data. Step: Check signature matches the data Test success: negativeSigningAuthenticationRoundtripBadDataTest Test starting: negativeSigningAuthenticationRoundtripUnkonwnCertificateTest Description: Tests that a roundtrip of signing a request and afterwards authenticating it fails due to a unknown certificate. Step: Sign a chunck of data. Step: Check signature matches the data Test success: negativeSigningAuthenticationRoundtripUnkonwnCertificateTest Test starting: operationAuthorizationBehaviourTest Description: Tests that a signature only allows the correct requests. Step: Check that GET_FILE is allowed. Test success: operationAuthorizationBehaviourTest Test starting: positiveSigningAuthenticationRoundtripTest Description: Tests that a roundtrip of signing a request and afterwards authenticating is succedes. Step: Sign a chunck of data. Step: Check signature matches the data Test success: positiveSigningAuthenticationRoundtripTest Starting testcase UnregisteredPermissionTest Test starting: testUnregisteredPermissionException 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: testUnregisteredPermissionException Starting testcase MessageCreationTest Test starting: messageCreationTest Description: Tests if we are able to create message objects from xml. The input XML is the example code defined in the message-xml, thereby also testing whether this is valid. Step: Creating IdentifyPillarsForGetFileRequest message Step: Creating IdentifyPillarsForGetFileResponse message Step: Creating GetFileRequest message Step: Creating GetFileProgressResponse message Step: Creating GetFileFinalResponse message Step: Creating IdentifyPillarsForPutFileRequest message Step: Creating IdentifyPillarsForPutFileResponse message Step: Creating PutFileRequest message Step: Creating PutFileProgressResponse message Step: Creating PutFileFinalResponse message Step: Creating IdentifyPillarsForDeleteFileRequest message Step: Creating IdentifyPillarsForDeleteFileResponse message Step: Creating DeleteFileRequest message Step: Creating DeleteFileProgressResponse message Step: Creating DeleteFileFinalResponse message Step: Creating IdentifyPillarsForReplaceFileRequest message Step: Creating IdentifyPillarsForReplaceFileResponse message Step: Creating ReplaceFileRequest message Step: Creating ReplaceFileProgressResponse message Step: Creating ReplaceFileFinalResponse message Step: Creating IdentifyPillarsForGetChecksumsRequest message Step: Creating IdentifyPillarsForGetChecksumsResponse message Step: Creating GetChecksumsRequest message Step: Creating GetChecksumsProgressResponse message Step: Creating GetChecksumsFinalResponse message Step: Creating IdentifyPillarsForGetFileIDsRequest message Step: Creating IdentifyPillarsForGetFileIDsResponse message Step: Creating GetFileIDsRequest message Step: Creating GetFileIDsProgressResponse message Step: Creating GetFileIDsFinalResponse message Step: Creating IdentifyContributorsForGetStatusRequest message Step: Creating IdentifyContributorsForGetStatusResponse message Step: Creating GetStatusRequest message Step: Creating GetStatusProgressResponse message Step: Creating GetStatusFinalResponse message Step: Creating IdentifyContributorsForGetAuditTrailsRequest message Step: Creating IdentifyContributorsForGetAuditTrailsResponse message Step: Creating GetAuditTrailsRequest message Step: Creating GetAuditTrailsProgressResponse message Step: Creating GetAuditTrailsFinalResponse message Step: Creating AlarmMessage message Test success: messageCreationTest Starting testcase MultiThreadedMessageBusTest Test starting: manyTheadsBeforeFinish Description: Tests whether it is possible to start the handling of many threads simultaneously. Step: Send one message for each listener Stimuli: Sending message: org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileRequest@33f42420[correlationID=12345, collectionID=MySla, destination=BusActivityTest, replyTo=topic://clientTopic, from=ClientPillar, to=, version=28, minVersion=24, auditTrailInformation=User: Name, Institution: Place, fileID=MyDataID] Stimuli: Sending message: org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileRequest@33f42420[correlationID=12345, collectionID=MySla, destination=BusActivityTest, replyTo=topic://clientTopic, from=ClientPillar, to=, version=28, minVersion=24, auditTrailInformation=User: Name, Institution: Place, fileID=MyDataID] Stimuli: Sending message: org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileRequest@33f42420[correlationID=12345, collectionID=MySla, destination=BusActivityTest, replyTo=topic://clientTopic, from=ClientPillar, to=, version=28, minVersion=24, auditTrailInformation=User: Name, Institution: Place, fileID=MyDataID] Test success: manyTheadsBeforeFinish Starting testcase TimeMeasurementUtilsTest Test starting: testCompareMilliSeconds Description: Test the comparison between TimeMeasure units. Test success: testCompareMilliSeconds Test starting: testCompareMilliSecondsToHours Description: Test the comparison between milliseconds and hours. Test success: testCompareMilliSecondsToHours Test starting: testMaxValue Description: Test the Maximum value Test success: testMaxValue Test starting: utilityTester Description: Test that the utility class is a proper utility class. Test success: utilityTester Starting testcase CalendarUtilsTest Test starting: calendarTester Description: Test the calendar utility class Step: Test the convertion of a date Step: Test that a 'null' date is equivalent to epoch Step: Test epoch Step: Test that a given time in millis is extractable in millis Step: Test the 'getNow' function Step: Test the reverse conversion, from XMLCalendar to Date Test success: calendarTester Test starting: utilityTester Description: Test that the utility class is a proper utility class. Test success: utilityTester Starting testcase MessageSignerExceptionTest Test starting: testMessageSigningException 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: testMessageSigningException Starting testcase MessageUtilsTest Test starting: testIdentificationResponse Description: Tests isIdentifyResponse method in the message utility class. Step: validate that it can see a identify response Test success: testIdentificationResponse Test starting: testPositiveIdentification Description: Tests isPositiveIdentifyResponse method in the message utility class. Step: validate that it can see a positive identify response Test success: testPositiveIdentification Test starting: testProgressResponse Description: Tests isPositiveProgressResponse method in the message utility class. Step: validate progress response Test success: testProgressResponse Test starting: validateUtilityClass Description: Validating that the utility class is actually an utility class. Test success: validateUtilityClass Starting testcase PermissionStoreExceptionTest Test starting: testPermissionStoreException 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: testPermissionStoreException Starting testcase StreamUtilsTest Test starting: streamTester Description: Tests the SteamUtils class. Step: Setup variables Step: Test with null arguments Step: Test copying the input stream to the output stream. Test success: streamTester Test starting: utilityTester Description: Test that the utility class is a proper utility class. Test success: utilityTester Starting testcase FileIDValidatorTest Test starting: badRegexTest Description: Tests the FileIDValidator handling of bad file id pattern. Step: Give the validator a 'null' as allowed file id pattern Step: Give the validator an empty string as allowed file id pattern Test success: badRegexTest Test starting: validatorDefaultTest Description: Tests the FileIDValidator class default restrictions. Only the length should fail. Step: Setup the validator, where all file ids are allowed at default. Step: Test a null as argument Step: Test a valid fileID Step: Test odd characters Step: Test invalid length Step: Test too short Test success: validatorDefaultTest Test starting: validatorTest Description: Tests the FileIDValidator class for the input handling based on a given regex. Step: Setup the validator Step: Test a null as argument Step: Test a valid fileID Step: Test invalid characters Step: Test invalid length Step: Test too short Test success: validatorTest Starting testcase XMLFileSettingsLoaderTest Test starting: testCollectionSettingsLoading Test success: testCollectionSettingsLoading Starting testcase SecurityExceptionTest Test starting: testSecurityException 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: testSecurityException Starting testcase ResponseInfoUtilsTest Test starting: responseInfoTester Description: Test the response info. Step: Validate the positive identification response Step: Validate the Progress response Test success: responseInfoTester Test starting: utilityTester Description: Test that the utility class is a proper utility class. Test success: utilityTester Finished testcase 02:18:26.375 ERROR o.b.protocol.bus.RawMessagebus - JMSException caught: javax.jms.JMSException: java.io.EOFException at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:54) ~[activemq-client-5.12.1.jar:5.12.1] at org.apache.activemq.ActiveMQConnection.onAsyncException(ActiveMQConnection.java:1972) ~[activemq-client-5.12.1.jar:5.12.1] at org.apache.activemq.ActiveMQConnection.onException(ActiveMQConnection.java:1991) ~[activemq-client-5.12.1.jar:5.12.1] at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:101) ~[activemq-client-5.12.1.jar:5.12.1] at org.apache.activemq.transport.ResponseCorrelator.onException(ResponseCorrelator.java:126) ~[activemq-client-5.12.1.jar:5.12.1] at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:101) ~[activemq-client-5.12.1.jar:5.12.1] at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:101) ~[activemq-client-5.12.1.jar:5.12.1] at org.apache.activemq.transport.WireFormatNegotiator.onException(WireFormatNegotiator.java:160) ~[activemq-client-5.12.1.jar:5.12.1] at org.apache.activemq.transport.AbstractInactivityMonitor.onException(AbstractInactivityMonitor.java:344) ~[activemq-client-5.12.1.jar:5.12.1] at org.apache.activemq.transport.TransportSupport.onException(TransportSupport.java:96) ~[activemq-client-5.12.1.jar:5.12.1] at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:200) ~[activemq-client-5.12.1.jar:5.12.1] at java.lang.Thread.run(Thread.java:745) [na:1.8.0_11] Caused by: java.io.EOFException: null at java.io.DataInputStream.readInt(DataInputStream.java:392) ~[na:1.8.0_11] at org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:267) ~[activemq-client-5.12.1.jar:5.12.1] at org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:221) ~[activemq-client-5.12.1.jar:5.12.1] at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:213) ~[activemq-client-5.12.1.jar:5.12.1] at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:196) ~[activemq-client-5.12.1.jar:5.12.1] ... 1 common frames omitted 02:18:26.520 ERROR o.b.protocol.bus.RawMessagebus - JMSException caught: javax.jms.JMSException: java.io.EOFException at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:54) ~[activemq-client-5.12.1.jar:5.12.1] at org.apache.activemq.ActiveMQConnection.onAsyncException(ActiveMQConnection.java:1972) ~[activemq-client-5.12.1.jar:5.12.1] at org.apache.activemq.ActiveMQConnection.onException(ActiveMQConnection.java:1991) ~[activemq-client-5.12.1.jar:5.12.1] at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:101) ~[activemq-client-5.12.1.jar:5.12.1] at org.apache.activemq.transport.ResponseCorrelator.onException(ResponseCorrelator.java:126) ~[activemq-client-5.12.1.jar:5.12.1] at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:101) ~[activemq-client-5.12.1.jar:5.12.1] at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:101) ~[activemq-client-5.12.1.jar:5.12.1] at org.apache.activemq.transport.WireFormatNegotiator.onException(WireFormatNegotiator.java:160) ~[activemq-client-5.12.1.jar:5.12.1] at org.apache.activemq.transport.AbstractInactivityMonitor.onException(AbstractInactivityMonitor.java:344) ~[activemq-client-5.12.1.jar:5.12.1] at org.apache.activemq.transport.TransportSupport.onException(TransportSupport.java:96) ~[activemq-client-5.12.1.jar:5.12.1] at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:200) ~[activemq-client-5.12.1.jar:5.12.1] at java.lang.Thread.run(Thread.java:745) [na:1.8.0_11] Caused by: java.io.EOFException: null at java.io.DataInputStream.readInt(DataInputStream.java:392) ~[na:1.8.0_11] at org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:267) ~[activemq-client-5.12.1.jar:5.12.1] at org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:221) ~[activemq-client-5.12.1.jar:5.12.1] at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:213) ~[activemq-client-5.12.1.jar:5.12.1] at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:196) ~[activemq-client-5.12.1.jar:5.12.1] ... 1 common frames omitted 02:18:26.539 ERROR o.b.protocol.bus.RawMessagebus - JMSException caught: javax.jms.JMSException: java.io.EOFException at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:54) ~[activemq-client-5.12.1.jar:5.12.1] at org.apache.activemq.ActiveMQConnection.onAsyncException(ActiveMQConnection.java:1972) ~[activemq-client-5.12.1.jar:5.12.1] at org.apache.activemq.ActiveMQConnection.onException(ActiveMQConnection.java:1991) ~[activemq-client-5.12.1.jar:5.12.1] at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:101) ~[activemq-client-5.12.1.jar:5.12.1] at org.apache.activemq.transport.ResponseCorrelator.onException(ResponseCorrelator.java:126) ~[activemq-client-5.12.1.jar:5.12.1] at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:101) ~[activemq-client-5.12.1.jar:5.12.1] at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:101) ~[activemq-client-5.12.1.jar:5.12.1] at org.apache.activemq.transport.WireFormatNegotiator.onException(WireFormatNegotiator.java:160) ~[activemq-client-5.12.1.jar:5.12.1] at org.apache.activemq.transport.AbstractInactivityMonitor.onException(AbstractInactivityMonitor.java:344) ~[activemq-client-5.12.1.jar:5.12.1] at org.apache.activemq.transport.TransportSupport.onException(TransportSupport.java:96) ~[activemq-client-5.12.1.jar:5.12.1] at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:200) ~[activemq-client-5.12.1.jar:5.12.1] at java.lang.Thread.run(Thread.java:745) [na:1.8.0_11] Caused by: java.io.EOFException: null at java.io.DataInputStream.readInt(DataInputStream.java:392) ~[na:1.8.0_11] at org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:267) ~[activemq-client-5.12.1.jar:5.12.1] at org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:221) ~[activemq-client-5.12.1.jar:5.12.1] at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:213) ~[activemq-client-5.12.1.jar:5.12.1] at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:196) ~[activemq-client-5.12.1.jar:5.12.1] ... 1 common frames omitted Finished suite Finished project Tests run: 95, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 33.445 sec - in TestSuite Results : Tests run: 95, Failures: 0, Errors: 0, Skipped: 0 [JENKINS] Recording test results log4j:WARN No appenders could be found for logger (org.apache.commons.beanutils.converters.BooleanConverter). log4j:WARN Please initialize the log4j system properly. [JENKINS] Archiving disabled [INFO] [INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ bitrepository-core --- [INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-core/target/bitrepository-core-1.6-SNAPSHOT.jar [INFO] [INFO] --- maven-jar-plugin:2.4:test-jar (default) @ bitrepository-core --- [INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-core/target/bitrepository-core-1.6-SNAPSHOT-tests.jar [INFO] [INFO] --- maven-source-plugin:2.2.1:jar-no-fork (attach-sources-no-fork) @ bitrepository-core --- [INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-core/target/bitrepository-core-1.6-SNAPSHOT-sources.jar [INFO] [INFO] --- maven-install-plugin:2.5.1:install (default-install) @ bitrepository-core --- [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-core/target/bitrepository-core-1.6-SNAPSHOT.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-core/1.6-SNAPSHOT/bitrepository-core-1.6-SNAPSHOT.jar [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-core/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-core/1.6-SNAPSHOT/bitrepository-core-1.6-SNAPSHOT.pom [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-core/target/bitrepository-core-1.6-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-core/1.6-SNAPSHOT/bitrepository-core-1.6-SNAPSHOT-tests.jar [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-core/target/bitrepository-core-1.6-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-core/1.6-SNAPSHOT/bitrepository-core-1.6-SNAPSHOT-sources.jar [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=449eb7d2-775d-4968-b9f7-18bca3d250b2, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=collectionIDIncludedInEventsTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@614aeccc[fileID=, allFileIDs=true]] Result: Received event: 449eb7d2: 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: 449eb7d2: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 449eb7d2: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE Result: Received event: 449eb7d2: GET_FILE_IDS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 449eb7d2: 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=449eb7d2-775d-4968-b9f7-18bca3d250b2, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=collectionIDIncludedInEventsTest, to=, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@6ceb7b5e[fileID=, allFileIDs=true], minTimestamp=, maxTimestamp=, maxNumberOfResults=, resultAddress=] Step: Wait for 1 second Result: Received event: 449eb7d2: 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=4767afcf-0921-4a9b-a9c6-09733a3ad6e6, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=conversationTimeoutTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@234a8f27[fileID=, allFileIDs=true]] Result: Received event: 4767afcf: GET_FILE_IDS: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs 02:18:43.735 WARN o.b.c.c.m.CollectionBasedConversationMediator - Failing timed out conversation 4767afcf-0921-4a9b-a9c6-09733a3ad6e6 (Age 1009ms) Result: Received event: 4767afcf: GET_FILE_IDS: FAILED: , Failing timed out conversation 4767afcf-0921-4a9b-a9c6-09733a3ad6e6 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=a4664d5b-c909-49e7-98c3-dc8d9ece2f8c, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=identificationFailureTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@68f32020[fileID=, allFileIDs=true]] Result: Received event: a4664d5b: 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: a4664d5b: 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: a4664d5b: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: a4664d5b: GET_FILE_IDS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2] Result: Received event: a4664d5b: 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=a4664d5b-c909-49e7-98c3-dc8d9ece2f8c, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=identificationFailureTest, to=, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@22590e3e[fileID=, allFileIDs=true], minTimestamp=, maxTimestamp=, maxNumberOfResults=, resultAddress=] Step: Verify that the client continues to the performing phase. Step: Send a final response message from contributor2 Result: Received event: a4664d5b: GET_FILE_IDS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false Result: Received event: a4664d5b: GET_FILE_IDS: FAILED: , Failed operation. Cause(s): [a4664d5b: 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=80db65f1-3aa9-410b-a9ca-731a0a1072e6, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=identificationNegativeTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@3f049056[fileID=, allFileIDs=true]] Result: Received event: 80db65f1: 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: 80db65f1: 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: 80db65f1: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: 80db65f1: GET_FILE_IDS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2] Result: Received event: 80db65f1: 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=80db65f1-3aa9-410b-a9ca-731a0a1072e6, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=identificationNegativeTest, to=, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@6fd12c5[fileID=, allFileIDs=true], minTimestamp=, maxTimestamp=, maxNumberOfResults=, resultAddress=] Step: Verify that the client continues to the performing phase. Step: Send a final response message from contributor2 Result: Received event: 80db65f1: GET_FILE_IDS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false Result: Received event: 80db65f1: GET_FILE_IDS: FAILED: , Failed operation. Cause(s): [80db65f1: 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=2cc7f734-6333-42d3-bde4-be6641c8e756, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=noContributorsRespondingTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@62e93c3a[fileID=, allFileIDs=true]] Result: Received event: 2cc7f734: GET_FILE_IDS: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs Step: Wait for 1 second Result: Received event: 2cc7f734: GET_FILE_IDS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors The following contributors didn't respond: [Pillar1, Pillar2] Result: Received event: 2cc7f734: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor Result: Received event: 2cc7f734: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor Result: Received event: 2cc7f734: 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=2cc7f734-6333-42d3-bde4-be6641c8e756, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=noContributorsRespondingTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@62e93c3a[fileID=, allFileIDs=true]] 02:18:49.916 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@1ba359bd[correlationID=2cc7f734-6333-42d3-bde4-be6641c8e756, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=noContributorsRespondingTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@62e93c3a[fileID=, 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=5650804c-9b7f-4b1f-9280-57a44c466ab7, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=oneContributorNotRespondingTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@2eeb0f9b[fileID=, allFileIDs=true]] Result: Received event: 5650804c: GET_FILE_IDS: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs Step: Send a identification response from contributor1. Result: Received event: 5650804c: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Step: Wait 1 second. Result: Received event: 5650804c: GET_FILE_IDS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors The following contributors didn't respond: [Pillar2] Result: Received event: 5650804c: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor Result: Received event: 5650804c: GET_FILE_IDS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 5650804c: GET_FILE_IDS: REQUEST_SENT: ContributorID [Pillar1], Sending request for get fileIDs Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@47b260eb[correlationID=5650804c-9b7f-4b1f-9280-57a44c466ab7, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=oneContributorNotRespondingTest, to=, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@4975966d[fileID=, allFileIDs=true], minTimestamp=, maxTimestamp=, maxNumberOfResults=, resultAddress=] Step: Verify that the client continues to the performing phase. Step: Send a final response upload message Result: Received event: 5650804c: GET_FILE_IDS: COMPONENT_COMPLETE: ContributorID Pillar1, PartialResult=false Result: Received event: 5650804c: GET_FILE_IDS: FAILED: , Failed operation. Cause(s): [5650804c: 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=02607c04-0350-4d77-ba82-140e9496d6df, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=operationTimeoutTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@7e7fe6d[fileID=, allFileIDs=true]] Result: Received event: 02607c04: 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: 02607c04: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 02607c04: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE Result: Received event: 02607c04: GET_FILE_IDS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 02607c04: 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=02607c04-0350-4d77-ba82-140e9496d6df, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=operationTimeoutTest, to=, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@7b32b129[fileID=, allFileIDs=true], minTimestamp=, maxTimestamp=, maxNumberOfResults=, resultAddress=] Step: Wait for 1 second Result: Received event: 02607c04: GET_FILE_IDS: FAILED: , Failed to receive responses from all contributors before timeout(100ms). Missing contributors [Pillar1] Test success: operationTimeoutTest Starting testcase DeleteFileCmdTest Test starting: checksumArgumentNonSaltAlgorithmWitoutSaltTest Description: Test MD5 checksum without salt -> no failure Test success: checksumArgumentNonSaltAlgorithmWitoutSaltTest Test starting: checksumArgumentSaltAlgorithmWithSaltTest Description: Test HMAC_SHA256 checksum with salt -> No failure Test success: checksumArgumentSaltAlgorithmWithSaltTest Test starting: defaultSuccessScenarioTest Description: Tests simplest arguments for running the CmdLineClient Test success: defaultSuccessScenarioTest Test starting: missingCollectionArgumentTest Description: Tests the scenario, where the collection arguments is missing. Takes the following arguments: -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: Random1449191933008pillar is not a valid pillar for collection TwoPillarCollection The collection contains the following pillars: [Pillar1, Pillar2] Test success: unknownPillarArgumentTest Starting testcase GetFileClientComponentTest Test starting: chooseFastestPillarGetFileClient Description: Set the GetClient to retrieve a file as fast as possible, where it has to choose between to pillars with different times. The messages should be delivered at the same time. Step: Create a GetFileClient configured to use a fast and a slow pillar. Step: Defining the variables for the GetFileClient and defining them in the configuration Step: Make the GetClient ask for fastest pillar. Stimuli: Calling getFileFromFastestPillar(default-test-file.txt, file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileRequest@5cffec7[correlationID=29235e92-a570-49da-b993-f98604401e3c, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=chooseFastestPillarGetFileClient, to=, version=28, minVersion=24, auditTrailInformation=, fileID=default-test-file.txt] Result: Received event: 29235e92: 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: 29235e92: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID THE-AVERAGE-PILLAR Result: Received event: 29235e92: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID THE-FAST-PILLAR Result: Received event: 29235e92: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID THE-SLOW-PILLAR Result: Received event: 29235e92: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [THE-FAST-PILLAR] Result: Received event: 29235e92: 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@e07b4db[correlationID=29235e92-a570-49da-b993-f98604401e3c, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=chooseFastestPillarGetFileClient, to=, version=28, minVersion=24, auditTrailInformation=, pillarID=THE-FAST-PILLAR, fileID=default-test-file.txt, filePart=, 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@38e00b47[correlationID=12c7743d-a36f-4a49-b852-b11094c1cc01, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=conversationTimeout, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, fileID=default-test-file.txt] Result: Received event: 12c7743d: 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: 12c7743d: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 12c7743d: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 12c7743d: 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@425b5fe2[correlationID=12c7743d-a36f-4a49-b852-b11094c1cc01, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=conversationTimeout, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileID=default-test-file.txt, filePart=, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt] Step: Wait for 1 second 02:18:54.528 WARN o.b.c.c.m.CollectionBasedConversationMediator - Failing timed out conversation 12c7743d-a36f-4a49-b852-b11094c1cc01 (Age 1010ms) Result: Received event: 12c7743d: GET_FILE for file default-test-file.txt: FAILED: , Failing timed out conversation 12c7743d-a36f-4a49-b852-b11094c1cc01 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@16e907b6[correlationID=23ccb9b2-e86d-4da4-bf89-1bfe2e9e21e1, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=failureDuringPerform, to=, version=28, minVersion=24, auditTrailInformation=, fileID=default-test-file.txt] Result: Received event: 23ccb9b2: 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: 23ccb9b2: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 23ccb9b2: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: 23ccb9b2: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 23ccb9b2: 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@23ec2bdc[correlationID=23ccb9b2-e86d-4da4-bf89-1bfe2e9e21e1, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=failureDuringPerform, to=, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileID=default-test-file.txt, filePart=, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt] Step: Send a failure response from pillar1 Result: Received event: 23ccb9b2: GET_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE Result: Received event: 23ccb9b2: GET_FILE for file default-test-file.txt: FAILED: , Failed to get file from Pillar1, org.bitrepository.bitrepositoryelements.ResponseInfo@631944d4[responseCode=FAILURE, responseText=] 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@4cd5fc46[correlationID=2a857d79-86a8-4a45-b372-6e2bd145d8ca, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=getFileClientWithChecksumPillarInvolved, to=, version=28, minVersion=24, auditTrailInformation=, fileID=default-test-file.txt] Result: Received event: 2a857d79: 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: 2a857d79: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: 2a857d79: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2] Result: Received event: 2a857d79: 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@3221588e[correlationID=2a857d79-86a8-4a45-b372-6e2bd145d8ca, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=getFileClientWithChecksumPillarInvolved, to=, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar2, fileID=default-test-file.txt, filePart=, 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: 2a857d79: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2 Result: Received event: 2a857d79: 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@4a0c3aa8[correlationID=f986d617-75a5-4d1d-a01b-ecba7925bfe5, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=getFileClientWithIdentifyTimeout, to=, version=28, minVersion=24, auditTrailInformation=, fileID=default-test-file.txt] Result: Received event: f986d617: 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: f986d617: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Step: Wait 1 second. Result: Received event: f986d617: 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: f986d617: GET_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor Result: Received event: f986d617: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: f986d617: 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@4d4a0b9b[correlationID=f986d617-75a5-4d1d-a01b-ecba7925bfe5, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=getFileClientWithIdentifyTimeout, to=, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileID=default-test-file.txt, filePart=, 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: f986d617: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1 Result: Received event: f986d617: 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@181098bf[correlationID=8bd4be18-20e9-441c-a416-9ae97bbcd058, collectionID=SinglePillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=getFileFromOtherCollection, to=Pillar2, version=28, minVersion=24, auditTrailInformation=, fileID=default-test-file.txt] Result: Received event: 8bd4be18: 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: 8bd4be18: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: 8bd4be18: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2] Result: Received event: 8bd4be18: 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@6a552721[correlationID=8bd4be18-20e9-441c-a416-9ae97bbcd058, collectionID=SinglePillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=getFileFromOtherCollection, to=Pillar2, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar2, fileID=default-test-file.txt, filePart=, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt] Step: Send a complete event from the pillar Result: Received event: 8bd4be18: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2 Result: Received event: 8bd4be18: 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@360a3106[correlationID=c1bba5ad-c919-4f04-9bef-b1dbb1d563b6, 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: c1bba5ad: 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: c1bba5ad: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: c1bba5ad: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2] Result: Received event: c1bba5ad: 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@7e9a836[correlationID=c1bba5ad-c919-4f04-9bef-b1dbb1d563b6, 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=, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt] Step: Send a GetFileProgressResponse. Result: Received event: c1bba5ad: GET_FILE for file default-test-file.txt: PROGRESS: ContributorID Pillar2, First test progress response message Step: Send a GetFileFinalResponse. Result: Received event: c1bba5ad: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2 Result: Received event: c1bba5ad: 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@44864ebe[correlationID=b21214a1-d480-42ba-b8a9-d898278844f4, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=getFileFromSpecificPillarWithFilePart, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, fileID=default-test-file.txt] Result: Received event: b21214a1: 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: b21214a1: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: b21214a1: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: b21214a1: 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@408f70ab[correlationID=b21214a1-d480-42ba-b8a9-d898278844f4, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=getFileFromSpecificPillarWithFilePart, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileID=default-test-file.txt, filePart=org.bitrepository.bitrepositoryelements.FilePart@5383bf08[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: b21214a1: 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: b21214a1: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1 Result: Received event: b21214a1: 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@215a329c[correlationID=6a19d0bf-ce1e-4107-bc02-0ffa87d99ca2, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=noIdentifyResponse, to=, version=28, minVersion=24, auditTrailInformation=, fileID=default-test-file.txt] Result: Received event: 6a19d0bf: GET_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetFile Step: Wait for 1 seconds Result: Received event: 6a19d0bf: 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: 6a19d0bf: GET_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor Result: Received event: 6a19d0bf: GET_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor Result: Received event: 6a19d0bf: 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@71eafb64[correlationID=785e99b4-0a95-4f8c-bb4e-15bf607deefd, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=singleComponentFailureDuringIdentify, to=, version=28, minVersion=24, auditTrailInformation=, fileID=default-test-file.txt] Result: Received event: 785e99b4: 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: 785e99b4: 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: 785e99b4: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: 785e99b4: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2] Result: Received event: 785e99b4: 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@727f36dd[correlationID=785e99b4-0a95-4f8c-bb4e-15bf607deefd, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=singleComponentFailureDuringIdentify, to=, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar2, fileID=default-test-file.txt, filePart=, 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: 785e99b4: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2 Result: Received event: 785e99b4: 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@22cb8e5f[correlationID=e32c1449-4f05-4191-be30-1e784324b40b, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=testNoSuchFileMultiplePillars, to=, version=28, minVersion=24, auditTrailInformation=, fileID=ERROR-NO-SUCH-FILE-ERROR] Result: Received event: e32c1449: 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: e32c1449: 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: e32c1449: 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: e32c1449: 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@5e198c40[correlationID=b28cb24b-8485-4a5f-96f0-14f3e893c755, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=testNoSuchFileSpecificPillar, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, fileID=ERROR-NO-SUCH-FILE-ERROR] Result: Received event: b28cb24b: 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: b28cb24b: 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: b28cb24b: 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 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@542754be[correlationID=7d3c2e16-3a34-494a-8546-e25070c01b66, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=getFileIDsDeliveredAtUrl, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@af57949[fileID=default-test-file.txt, allFileIDs=]] Result: Received event: 7d3c2e16: 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: 7d3c2e16: GET_FILE_IDS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 7d3c2e16: GET_FILE_IDS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 7d3c2e16: 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@5186b78a[correlationID=7d3c2e16-3a34-494a-8546-e25070c01b66, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=getFileIDsDeliveredAtUrl, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@3f6a9ba0[fileID=default-test-file.txt, allFileIDs=], minTimestamp=, maxTimestamp=, maxNumberOfResults=, 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: 7d3c2e16: 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: 7d3c2e16: GET_FILE_IDS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, PartialResult=false Result: Received event: 7d3c2e16: 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@539bb233[correlationID=15f42b33-8705-4b7f-aeba-bbe96e7756e8, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=getFileIDsDeliveredThroughMessage, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@21b2579d[fileID=default-test-file.txt, allFileIDs=]] Result: Received event: 15f42b33: 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: 15f42b33: GET_FILE_IDS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 15f42b33: GET_FILE_IDS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 15f42b33: 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@796613b7[correlationID=15f42b33-8705-4b7f-aeba-bbe96e7756e8, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=getFileIDsDeliveredThroughMessage, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@77622c82[fileID=default-test-file.txt, allFileIDs=], minTimestamp=, maxTimestamp=, maxNumberOfResults=, resultAddress=] Step: The pillar sends a getFileIDsProgressResponse to the GetFileIDsClient. Result: Received event: 15f42b33: 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: 15f42b33: GET_FILE_IDS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, NumberOfFileIDs=1, PartialResult=false Result: Received event: 15f42b33: 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@6167a456) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@54eb2bf6[correlationID=9978b897-b3b6-42c6-9e76-3b17b6c07baf, collectionID=SinglePillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=getFileIDsFromOtherCollection, to=Pillar2, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@6d01f2e5[fileID=default-test-file.txt, allFileIDs=]] Result: Received event: 9978b897: 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: 9978b897: GET_FILE_IDS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: 9978b897: GET_FILE_IDS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2] Result: Received event: 9978b897: 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@3a7d6976[correlationID=9978b897-b3b6-42c6-9e76-3b17b6c07baf, collectionID=SinglePillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=getFileIDsFromOtherCollection, to=Pillar2, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@37c45154[fileID=default-test-file.txt, allFileIDs=], minTimestamp=, maxTimestamp=, maxNumberOfResults=, resultAddress=] Step: Send a complete event from the pillar Result: Received event: 9978b897: GET_FILE_IDS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false Result: Received event: 9978b897: 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@5a079446[correlationID=20c17963-3f22-46e7-ad46-d7e2f201c840, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=testNoSuchFile, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@694c0ed1[fileID=default-test-file.txt, allFileIDs=]] Result: Received event: 20c17963: 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: 20c17963: GET_FILE_IDS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 20c17963: GET_FILE_IDS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 20c17963: 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@4d071e4b[correlationID=20c17963-3f22-46e7-ad46-d7e2f201c840, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=testNoSuchFile, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@2b441609[fileID=default-test-file.txt, allFileIDs=], minTimestamp=, maxTimestamp=, maxNumberOfResults=, 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: 20c17963: GET_FILE_IDS for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FILE_NOT_FOUND_FAILURE, No such file. Result: Received event: 20c17963: GET_FILE_IDS for file default-test-file.txt: FAILED: , Failed operation. Cause(s): [20c17963: 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=Fri Dec 04 02:18:58 CET 2015, maxTimestamp=Fri Dec 04 02:18:59 CET 2015, maxNumberOfResults=1}, ContributorQuery{componentID='Pillar2, minTimestamp=Fri Dec 04 02:18:59 CET 2015, maxTimestamp=Fri Dec 04 02:18:59 CET 2015, maxNumberOfResults=2}], null, null, org.bitrepository.client.TestEventHandler@6050462a) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@1be3a294[correlationID=b8764796-4d57-41e9-986e-330e84950c56, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=testPaging, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@33502cfe[fileID=, allFileIDs=true]] Result: Received event: b8764796: GET_FILE_IDS: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs Step: Send a IdentifyPillarsForGetFileIDsResponse from both pillars. Result: Received event: b8764796: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: b8764796: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: b8764796: GET_FILE_IDS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2, Pillar1] Result: Received event: b8764796: GET_FILE_IDS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for get fileIDs Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@1728d307[correlationID=b8764796-4d57-41e9-986e-330e84950c56, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=testPaging, to=, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@252d2ac0[fileID=, allFileIDs=true], minTimestamp=2015-12-04T02:18:58.692+01:00, maxTimestamp=2015-12-04T02:18:59.592+01:00, maxNumberOfResults=1, resultAddress=] Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@3f0b5619[correlationID=b8764796-4d57-41e9-986e-330e84950c56, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=testPaging, to=, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@67afc9b6[fileID=, allFileIDs=true], minTimestamp=2015-12-04T02:18:59.592+01:00, maxTimestamp=2015-12-04T02:18:59.692+01:00, maxNumberOfResults=2, resultAddress=] 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: 5261ef05: GET_STATUS: IDENTIFY_REQUEST_SENT: , Identifying contributors for getting status Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetStatusRequest@609edb55[correlationID=5261ef05-687e-47c4-8c09-fab5d702bb07, collectionID=, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetStatusClientComponentTest-cibuild01, from=getAllStatuses, to=, version=28, minVersion=24, auditTrailInformation=] Step: Send a identifyResponse from each pillar Result: Received event: 5261ef05: GET_STATUS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 5261ef05: GET_STATUS: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: 5261ef05: GET_STATUS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2, Pillar1] Result: Received event: 5261ef05: GET_STATUS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending GetStatusRequest Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetStatusRequest@23e1f610[correlationID=5261ef05-687e-47c4-8c09-fab5d702bb07, collectionID=, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetStatusClientComponentTest-cibuild01, from=getAllStatuses, to=, version=28, minVersion=24, auditTrailInformation=, contributor=Pillar1] Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetStatusRequest@1a3a6216[correlationID=5261ef05-687e-47c4-8c09-fab5d702bb07, collectionID=, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetStatusClientComponentTest-cibuild01, from=getAllStatuses, to=, version=28, minVersion=24, auditTrailInformation=, contributor=Pillar2] Step: Send a final response from pillar 1 Result: Received event: 5261ef05: GET_STATUS: COMPONENT_COMPLETE: ContributorID Pillar1, resulting status: org.bitrepository.bitrepositoryelements.ResultingStatus@6c0bf8f4[statusInfo=org.bitrepository.bitrepositoryelements.StatusInfo@73476e2d[statusCode=OK, statusText=Everythings fine..], statusTimestamp=2015-12-04T02:19:00.040+01:00] Step: Send a final response from pillar 2 Result: Received event: 5261ef05: GET_STATUS: COMPONENT_COMPLETE: ContributorID Pillar2, resulting status: org.bitrepository.bitrepositoryelements.ResultingStatus@52b77d5e[statusInfo=org.bitrepository.bitrepositoryelements.StatusInfo@6ab6ec33[statusCode=OK, statusText=Everythings fine..], statusTimestamp=2015-12-04T02:19:00.041+01:00] Result: Received event: 5261ef05: 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: 8e97a377: GET_STATUS: IDENTIFY_REQUEST_SENT: , Identifying contributors for getting status Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetStatusRequest@6a9a6a0c[correlationID=8e97a377-0b7f-4769-9190-c29d7f29f73a, collectionID=, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetStatusClientComponentTest-cibuild01, from=incompleteSetOfIdendifyResponses, to=, version=28, minVersion=24, auditTrailInformation=] Step: Send a identifyResponse from pillar 1 Result: Received event: 8e97a377: GET_STATUS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Step: Wait for timeout event Result: Received event: 8e97a377: GET_STATUS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors The following contributors didn't respond: [Pillar2] Result: Received event: 8e97a377: GET_STATUS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor Result: Received event: 8e97a377: GET_STATUS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 8e97a377: GET_STATUS: REQUEST_SENT: ContributorID [Pillar1], Sending GetStatusRequest Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetStatusRequest@8489c56[correlationID=8e97a377-0b7f-4769-9190-c29d7f29f73a, collectionID=, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetStatusClientComponentTest-cibuild01, from=incompleteSetOfIdendifyResponses, to=, version=28, minVersion=24, auditTrailInformation=, contributor=Pillar1] Test success: incompleteSetOfIdendifyResponses Test starting: verifyGetStatusClientFromFactory Test success: verifyGetStatusClientFromFactory Starting testcase NegativeResponseExceptionTest Test starting: testNegativeResponse Description: Test the instantiation of the exception Step: Setup Step: Try to throw such an exception with the response code Test success: testNegativeResponse Starting testcase PutFileCmdTest Test starting: checksumArgumentNonSaltAlgorithmWitoutSaltTest Description: Test MD5 checksum without salt -> no failure Test success: checksumArgumentNonSaltAlgorithmWitoutSaltTest Test starting: checksumArgumentSaltAlgorithmWithSaltTest Description: Test HMAC_SHA256 checksum with salt -> No failure Test success: checksumArgumentSaltAlgorithmWithSaltTest Test starting: defaultSuccessScenarioTest Description: Tests simplest arguments for running the CmdLineClient Test success: defaultSuccessScenarioTest Test starting: missingChecksumWhenFileArgumentTest Description: Tests the scenario, where no checksum argument is given, but a file is given. Test success: missingChecksumWhenFileArgumentTest Test starting: missingChecksumWhenURLArgumentTest Description: Tests the scenario, where no checksum argument is given, but a URL is given. Invalid argument: The URL argument requires also the checksum argument (-c). Test success: missingChecksumWhenURLArgumentTest Test starting: missingCollectionArgumentTest Description: Tests the scenario, where the collection arguments is missing. Takes the following arguments: -s The path to the directory with the settings files for the client -k The path to the file containing the private key. -v Makes the client more verbose -c The id for the collection to perform the operation on. -i The id for the file to perform the operation on. -p [OPTIONAL] The id of the pillar where the should be performed. If undefined the operations is performed on all pillars. -f The path to the file, which is wanted to be put. Is required, unless a URL is given. -u The URL for the file to be put. Is required, unless the actual file is given. -C The checksum for the file to be retreived. Required if using an URL. -R [OPTIONAL] The algorithm of checksum to request in the response from the pillars. -S [OPTIONAL] The salt of checksum to request in the response. Requires the ChecksumType argument. -d If this argument is present, then the file will be removed from the server, when the operation is complete. Missing argument: Missing required option: c Test success: missingCollectionArgumentTest Test starting: missingFileIDWhenFileArgumentTest Description: Tests the scenario, where no checksum argument is given, but a URL is given. Test success: missingFileIDWhenFileArgumentTest Test starting: missingFileIDWhenURLArgumentTest Description: Tests the scenario, where no checksum argument is given, but a URL is given. Invalid argument: The URL argument requires also the argument for the ID of the file (-i). Test success: missingFileIDWhenURLArgumentTest Test starting: missingFileOrURLArgumentTest Description: Tests the scenario, where no arguments for file or url is given. Invalid argument: Requires either the file argument (-f) or the URL argument (-u). Test success: missingFileOrURLArgumentTest Test starting: specificPillarArgumentTest Description: Test argument for a specific pillar Test success: specificPillarArgumentTest Test starting: unknownPillarArgumentTest Description: Testing against a non-existing pillar id -> Should fail Invalid argument: Random1449191944171pillar 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 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@302ab67e[correlationID=f2f7fa9c-13d2-4738-a17b-8229dde4654f, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=getAllAuditTrailsTest, to=, version=28, minVersion=24, auditTrailInformation=] Result: Received event: f2f7fa9c: 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: f2f7fa9c: GET_AUDIT_TRAILS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: f2f7fa9c: GET_AUDIT_TRAILS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: f2f7fa9c: GET_AUDIT_TRAILS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2] Result: Received event: f2f7fa9c: 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@253c82ad[correlationID=f2f7fa9c-13d2-4738-a17b-8229dde4654f, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=getAllAuditTrailsTest, to=, version=28, minVersion=24, auditTrailInformation=, contributor=Pillar1, fileID=default-test-file.txt, minSequenceNumber=, maxSequenceNumber=, minTimestamp=, maxTimestamp=, maxNumberOfResults=, resultAddress=] Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@3af8f1ef[correlationID=f2f7fa9c-13d2-4738-a17b-8229dde4654f, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=getAllAuditTrailsTest, to=, version=28, minVersion=24, auditTrailInformation=, contributor=Pillar2, fileID=default-test-file.txt, minSequenceNumber=, maxSequenceNumber=, minTimestamp=, maxTimestamp=, maxNumberOfResults=, resultAddress=] Step: Send a final response from pillar 1 Result: Received event: f2f7fa9c: 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: f2f7fa9c: GET_AUDIT_TRAILS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2, NumberOfAuditTrailEvents=2, PartialResult=false Result: Received event: f2f7fa9c: 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@62db3787[correlationID=87bab97a-8a6e-45d3-bb36-597eb0e9e191, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=getSomeAuditTrailsTest, to=Pillar1, version=28, minVersion=24, auditTrailInformation=] Result: Received event: 87bab97a: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails Step: Send a identifyResponse from pillar1 Result: Received event: 87bab97a: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 87bab97a: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 87bab97a: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1], Sending request for audit trails Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@68bbd5c2[correlationID=87bab97a-8a6e-45d3-bb36-597eb0e9e191, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=getSomeAuditTrailsTest, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, contributor=Pillar1, fileID=, minSequenceNumber=1, maxSequenceNumber=3, minTimestamp=, maxTimestamp=, maxNumberOfResults=10000, resultAddress=] Step: Verify no request is sent to pillar2 Step: Send a final response from pillar 1 Result: Received event: 87bab97a: GET_AUDIT_TRAILS: COMPONENT_COMPLETE: ContributorID Pillar1, NumberOfAuditTrailEvents=2, PartialResult=false Result: Received event: 87bab97a: 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@37a522c8[correlationID=c6e42424-fcba-44e7-b461-3958302a80b9, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=incompleteSetOfFinalResponsesTest, to=, version=28, minVersion=24, auditTrailInformation=] Result: Received event: c6e42424: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails Step: Send a identifyResponse from each of the two pillars Result: Received event: c6e42424: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: c6e42424: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: c6e42424: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2] Result: Received event: c6e42424: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for audit trails Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@21ec723c[correlationID=c6e42424-fcba-44e7-b461-3958302a80b9, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=incompleteSetOfFinalResponsesTest, to=, version=28, minVersion=24, auditTrailInformation=, contributor=Pillar1, fileID=, minSequenceNumber=, maxSequenceNumber=, minTimestamp=, maxTimestamp=, maxNumberOfResults=, resultAddress=] Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@3f41a7ab[correlationID=c6e42424-fcba-44e7-b461-3958302a80b9, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=incompleteSetOfFinalResponsesTest, to=, version=28, minVersion=24, auditTrailInformation=, contributor=Pillar2, fileID=, minSequenceNumber=, maxSequenceNumber=, minTimestamp=, maxTimestamp=, maxNumberOfResults=, resultAddress=] Test success: incompleteSetOfFinalResponsesTest Result: The following messages haven't been handled by the testcase: org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@3f41a7ab[correlationID=c6e42424-fcba-44e7-b461-3958302a80b9, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=incompleteSetOfFinalResponsesTest, to=, version=28, minVersion=24, auditTrailInformation=, contributor=Pillar2, fileID=, minSequenceNumber=, maxSequenceNumber=, minTimestamp=, maxTimestamp=, maxNumberOfResults=, resultAddress=] 02:19:05.759 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@3f41a7ab[correlationID=c6e42424-fcba-44e7-b461-3958302a80b9, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=incompleteSetOfFinalResponsesTest, to=, version=28, minVersion=24, auditTrailInformation=, contributor=Pillar2, fileID=, minSequenceNumber=, maxSequenceNumber=, minTimestamp=, maxTimestamp=, maxNumberOfResults=, resultAddress=] 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@79462469[correlationID=0bf34ae7-e6dd-4dcc-aa89-afee4bf61658, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=negativeGetAuditTrailsResponseTest, to=, version=28, minVersion=24, auditTrailInformation=] Result: Received event: 0bf34ae7: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails Step: Send a identifyResponse from each of the two pillars Result: Received event: 0bf34ae7: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 0bf34ae7: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: 0bf34ae7: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2] Result: Received event: 0bf34ae7: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for audit trails Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@4295b0b8[correlationID=0bf34ae7-e6dd-4dcc-aa89-afee4bf61658, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=negativeGetAuditTrailsResponseTest, to=, version=28, minVersion=24, auditTrailInformation=, contributor=Pillar1, fileID=, minSequenceNumber=, maxSequenceNumber=, minTimestamp=, maxTimestamp=, maxNumberOfResults=, resultAddress=] Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@ab8b1ef[correlationID=0bf34ae7-e6dd-4dcc-aa89-afee4bf61658, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=negativeGetAuditTrailsResponseTest, to=, version=28, minVersion=24, auditTrailInformation=, contributor=Pillar2, fileID=, minSequenceNumber=, maxSequenceNumber=, minTimestamp=, maxTimestamp=, maxNumberOfResults=, resultAddress=] Step: Send a failed response from pillar 1 Result: Received event: 0bf34ae7: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE, GetAuditTrails failed Step: Send a final response from pillar 2 Result: Received event: 0bf34ae7: GET_AUDIT_TRAILS: COMPONENT_COMPLETE: ContributorID Pillar2, NumberOfAuditTrailEvents=2, PartialResult=false Result: Received event: 0bf34ae7: GET_AUDIT_TRAILS: FAILED: , Failed operation. Cause(s): [0bf34ae7: 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@24a26847[correlationID=d3150116-d024-4b92-8190-258249d79610, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noFinalResponsesTest, to=, version=28, minVersion=24, auditTrailInformation=] Result: Received event: d3150116: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails Step: Send a identifyResponse from each of the two pillars Result: Received event: d3150116: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: d3150116: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: d3150116: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2, Pillar1] Result: Received event: d3150116: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for audit trails Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@45bedfed[correlationID=d3150116-d024-4b92-8190-258249d79610, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noFinalResponsesTest, to=, version=28, minVersion=24, auditTrailInformation=, contributor=Pillar1, fileID=, minSequenceNumber=, maxSequenceNumber=, minTimestamp=, maxTimestamp=, maxNumberOfResults=, resultAddress=] Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@7269674d[correlationID=d3150116-d024-4b92-8190-258249d79610, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noFinalResponsesTest, to=, version=28, minVersion=24, auditTrailInformation=, contributor=Pillar2, fileID=, minSequenceNumber=, maxSequenceNumber=, minTimestamp=, maxTimestamp=, maxNumberOfResults=, resultAddress=] Step: Wait for 1 second Result: Received event: c6e42424: GET_AUDIT_TRAILS: FAILED: , Failed to receive responses from all contributors before timeout(500ms). Missing contributors [Pillar1, Pillar2] Result: Received event: d3150116: 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@45bedfed[correlationID=d3150116-d024-4b92-8190-258249d79610, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noFinalResponsesTest, to=, version=28, minVersion=24, auditTrailInformation=, contributor=Pillar1, fileID=, minSequenceNumber=, maxSequenceNumber=, minTimestamp=, maxTimestamp=, maxNumberOfResults=, resultAddress=] 02:19:06.342 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@45bedfed[correlationID=d3150116-d024-4b92-8190-258249d79610, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noFinalResponsesTest, to=, version=28, minVersion=24, auditTrailInformation=, contributor=Pillar1, fileID=, minSequenceNumber=, maxSequenceNumber=, minTimestamp=, maxTimestamp=, maxNumberOfResults=, resultAddress=] Result: The following messages haven't been handled by the testcase: org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@7269674d[correlationID=d3150116-d024-4b92-8190-258249d79610, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noFinalResponsesTest, to=, version=28, minVersion=24, auditTrailInformation=, contributor=Pillar2, fileID=, minSequenceNumber=, maxSequenceNumber=, minTimestamp=, maxTimestamp=, maxNumberOfResults=, resultAddress=] 02:19:06.342 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@7269674d[correlationID=d3150116-d024-4b92-8190-258249d79610, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noFinalResponsesTest, to=, version=28, minVersion=24, auditTrailInformation=, contributor=Pillar2, fileID=, minSequenceNumber=, maxSequenceNumber=, minTimestamp=, maxTimestamp=, maxNumberOfResults=, resultAddress=] 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@6d48f1c[correlationID=9a1c5455-600b-4a02-b7f3-53bfdf172a6f, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=progressEventsTest, to=, version=28, minVersion=24, auditTrailInformation=] Result: Received event: 9a1c5455: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails Step: Send a identifyResponse from each of the two pillars Result: Received event: 9a1c5455: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 9a1c5455: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: 9a1c5455: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2] Result: Received event: 9a1c5455: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for audit trails Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@5911d6e[correlationID=9a1c5455-600b-4a02-b7f3-53bfdf172a6f, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=progressEventsTest, to=, version=28, minVersion=24, auditTrailInformation=, contributor=Pillar1, fileID=, minSequenceNumber=, maxSequenceNumber=, minTimestamp=, maxTimestamp=, maxNumberOfResults=, resultAddress=] Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@271fdeaf[correlationID=9a1c5455-600b-4a02-b7f3-53bfdf172a6f, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=progressEventsTest, to=, version=28, minVersion=24, auditTrailInformation=, contributor=Pillar2, fileID=, minSequenceNumber=, maxSequenceNumber=, minTimestamp=, maxTimestamp=, maxNumberOfResults=, resultAddress=] Step: Send a progress accepted response from pillar 1 Result: Received event: 9a1c5455: GET_AUDIT_TRAILS: PROGRESS: ContributorID Pillar1, GetAuditTrails request accepted Step: Send a general progress response from pillar 2 Result: Received event: 9a1c5455: GET_AUDIT_TRAILS: PROGRESS: ContributorID Pillar2, Still progressing Test success: progressEventsTest Test starting: verifyAuditTrailClientFromFactory Test success: verifyAuditTrailClientFromFactory Starting testcase AuditTrailQueryTest Test starting: testBothSequenceNumberFailure Description: Test the creation of a AuditTrailQuery with both SequenceNumber, where max is smalle than min. Test success: testBothSequenceNumberFailure Test starting: testBothSequenceNumberSuccess Description: Test the creation of a AuditTrailQuery with both SequenceNumber, where max is larger than min. Test success: testBothSequenceNumberSuccess Test starting: testNoSequenceNumbers Description: Test that a AuditTrailQuery can be created without any sequence numbers. Test success: testNoSequenceNumbers Test starting: testOnlyMinSequenceNumber Description: Test the creation of a AuditTrailQuery with only the minSequenceNumber Test success: testOnlyMinSequenceNumber Test starting: collectionIDIncludedInEventsTest Description: Tests the the client provides collectionID in events. Step: Set a 0.5 second operation timeout. Step: Start the operation Stimuli: Calling getAuditTrails(null, null, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@4ae730ca[correlationID=07e7fd69-2e07-4929-a9eb-7232a10cc804, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=collectionIDIncludedInEventsTest, to=, version=28, minVersion=24, auditTrailInformation=] Result: Received event: 07e7fd69: 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: 07e7fd69: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 07e7fd69: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE Result: Received event: 07e7fd69: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 07e7fd69: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1], Sending request for audit trails Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@33d6886b[correlationID=07e7fd69-2e07-4929-a9eb-7232a10cc804, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=collectionIDIncludedInEventsTest, to=, version=28, minVersion=24, auditTrailInformation=, contributor=Pillar1, fileID=, minSequenceNumber=, maxSequenceNumber=, minTimestamp=, maxTimestamp=, maxNumberOfResults=, resultAddress=] Step: Wait for 1 second Result: Received event: 07e7fd69: GET_AUDIT_TRAILS: FAILED: , Failed to receive responses from all contributors before timeout(500ms). Missing contributors [Pillar1] Test success: collectionIDIncludedInEventsTest Starting testcase GetChecksumsClientComponentTest Test starting: collectionIDIncludedInEventsTest Description: Tests the the client provides collectionID in events. Step: Set a 0.5 second operation timeout. Step: Start the operation Stimuli: Calling getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@757e13b2, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@fe8344c[correlationID=a725d9d3-d4be-4833-ba17-3087ca1e2c9a, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=collectionIDIncludedInEventsTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@4b330722[fileID=, allFileIDs=true], checksumRequestForExistingFile=] Result: Received event: a725d9d3: 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: a725d9d3: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: a725d9d3: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE Result: Received event: a725d9d3: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: a725d9d3: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar1], Sending GetFileIDsRequest's Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@174bbe8e[correlationID=a725d9d3-d4be-4833-ba17-3087ca1e2c9a, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=collectionIDIncludedInEventsTest, to=, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@4412b152[fileID=, allFileIDs=true], minTimestamp=, maxTimestamp=, maxNumberOfResults=, checksumRequestForExistingFile=, resultAddress=] Step: Wait for 1 second Result: Received event: a725d9d3: GET_CHECKSUMS: FAILED: , Failed to receive responses from all contributors before timeout(500ms). Missing contributors [Pillar1] Test success: collectionIDIncludedInEventsTest Test starting: conversationTimeoutTest Description: Tests the the client handles lack of IdentifyPillarResponses gracefully Step: Set a 100 ms ConversationTimeout. Step: Start the operation Stimuli: Calling getAuditTrails(null, null, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@308034aa[correlationID=b58a085c-c73a-4cd1-929d-23fbbcb186a1, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=conversationTimeoutTest, to=, version=28, minVersion=24, auditTrailInformation=] Result: Received event: b58a085c: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails 02:19:08.956 WARN o.b.c.c.m.CollectionBasedConversationMediator - Failing timed out conversation b58a085c-c73a-4cd1-929d-23fbbcb186a1 (Age 1014ms) Result: Received event: b58a085c: GET_AUDIT_TRAILS: FAILED: , Failing timed out conversation b58a085c-c73a-4cd1-929d-23fbbcb186a1 Test success: conversationTimeoutTest Test starting: conversationTimeoutTest Description: Tests the the client handles lack of IdentifyPillarResponses gracefully Step: Set a 100 ms ConversationTimeout. Step: Start the operation Stimuli: Calling getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@757e13b2, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@2300d2b4[correlationID=91cd2307-de74-405d-b720-826ffd2af97b, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=conversationTimeoutTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@b9286ad[fileID=, allFileIDs=true], checksumRequestForExistingFile=] Result: Received event: 91cd2307: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums 02:19:10.077 WARN o.b.c.c.m.CollectionBasedConversationMediator - Failing timed out conversation 91cd2307-de74-405d-b720-826ffd2af97b (Age 1014ms) Result: Received event: 91cd2307: GET_CHECKSUMS: FAILED: , Failing timed out conversation 91cd2307-de74-405d-b720-826ffd2af97b 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@792b4d95[correlationID=8e80b656-1293-4e3a-8e05-1ee030c5f5ff, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=identificationFailureTest, to=, version=28, minVersion=24, auditTrailInformation=] Result: Received event: 8e80b656: 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: 8e80b656: 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: 8e80b656: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: 8e80b656: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2] Result: Received event: 8e80b656: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar2], Sending request for audit trails Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@27779eaa[correlationID=8e80b656-1293-4e3a-8e05-1ee030c5f5ff, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=identificationFailureTest, to=, version=28, minVersion=24, auditTrailInformation=, contributor=Pillar2, fileID=, minSequenceNumber=, maxSequenceNumber=, minTimestamp=, maxTimestamp=, maxNumberOfResults=, resultAddress=] Step: Verify that the client continues to the performing phase. Step: Send a final response message from contributor2 Result: Received event: 8e80b656: GET_AUDIT_TRAILS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false Result: Received event: 8e80b656: GET_AUDIT_TRAILS: FAILED: , Failed operation. Cause(s): [8e80b656: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE] Test success: identificationFailureTest Test starting: identificationFailureTest Description: Verify that the client works correctly when a contributor sends a failure response. Step: Start the operation. Stimuli: Calling getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@757e13b2, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@daa6654[correlationID=99bf41cb-d290-4895-8464-17adabd6a725, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=identificationFailureTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@6fd33f5a[fileID=, allFileIDs=true], checksumRequestForExistingFile=] Result: Received event: 99bf41cb: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums Step: Send a identification response from contributor1 with a FAILURE response code. Result: Received event: 99bf41cb: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE Step: Send a identification response from contributor2 with a IDENTIFICATION_POSITIVE response code . Result: Received event: 99bf41cb: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: 99bf41cb: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2] Result: Received event: 99bf41cb: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar2], Sending GetFileIDsRequest's Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@6ec05499[correlationID=99bf41cb-d290-4895-8464-17adabd6a725, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=identificationFailureTest, to=, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@308617d3[fileID=, allFileIDs=true], minTimestamp=, maxTimestamp=, maxNumberOfResults=, checksumRequestForExistingFile=, resultAddress=] Step: Verify that the client continues to the performing phase. Step: Send a final response message from contributor2 Result: Received event: 99bf41cb: GET_CHECKSUMS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false Result: Received event: 99bf41cb: GET_CHECKSUMS: FAILED: , Failed operation. Cause(s): [99bf41cb: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE] Test success: identificationFailureTest Test starting: identificationNegativeTest Description: Verify that the client works correctly when a contributor sends a negative response. Step: Start the operation. Stimuli: Calling getAuditTrails(null, null, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@bfa82bd[correlationID=25add7fd-98b9-4af3-a4cc-8e0ec4e0f8b2, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=identificationNegativeTest, to=, version=28, minVersion=24, auditTrailInformation=] Result: Received event: 25add7fd: 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: 25add7fd: 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: 25add7fd: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: 25add7fd: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2] Result: Received event: 25add7fd: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar2], Sending request for audit trails Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@384abf00[correlationID=25add7fd-98b9-4af3-a4cc-8e0ec4e0f8b2, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=identificationNegativeTest, to=, version=28, minVersion=24, auditTrailInformation=, contributor=Pillar2, fileID=, minSequenceNumber=, maxSequenceNumber=, minTimestamp=, maxTimestamp=, maxNumberOfResults=, resultAddress=] Step: Verify that the client continues to the performing phase. Step: Send a final response message from contributor2 Result: Received event: 25add7fd: GET_AUDIT_TRAILS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false Result: Received event: 25add7fd: GET_AUDIT_TRAILS: FAILED: , Failed operation. Cause(s): [25add7fd: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: IDENTIFICATION_NEGATIVE] Test success: identificationNegativeTest Test starting: identificationNegativeTest Description: Verify that the client works correctly when a contributor sends a negative response. Step: Start the operation. Stimuli: Calling getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@757e13b2, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@3ab8f900[correlationID=fbc62667-d264-4071-a47a-fbfdf1b2c60c, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=identificationNegativeTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@621508de[fileID=, allFileIDs=true], checksumRequestForExistingFile=] Result: Received event: fbc62667: 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: fbc62667: 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: fbc62667: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: fbc62667: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2] Result: Received event: fbc62667: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar2], Sending GetFileIDsRequest's Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@2cdd3638[correlationID=fbc62667-d264-4071-a47a-fbfdf1b2c60c, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=identificationNegativeTest, to=, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@5150ba5a[fileID=, allFileIDs=true], minTimestamp=, maxTimestamp=, maxNumberOfResults=, checksumRequestForExistingFile=, resultAddress=] Step: Verify that the client continues to the performing phase. Step: Send a final response message from contributor2 Result: Received event: fbc62667: GET_CHECKSUMS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false Result: Received event: fbc62667: GET_CHECKSUMS: FAILED: , Failed operation. Cause(s): [fbc62667: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: IDENTIFICATION_NEGATIVE] Test success: identificationNegativeTest Test starting: noContributorsRespondingTest Description: Tests the the client handles lack of a IdentifyResponse gracefully. More concrete this means that the occurrence of a identification timeout should be handled correctly Step: Set a 100 ms timeout for identifying contributors. Step: Start the operation. Stimuli: Calling getAuditTrails(null, null, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@6f800942[correlationID=795646f9-7684-4884-9064-6c605a788814, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noContributorsRespondingTest, to=, version=28, minVersion=24, auditTrailInformation=] Result: Received event: 795646f9: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails Step: Wait for 1 second Result: Received event: 795646f9: GET_AUDIT_TRAILS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors The following contributors didn't respond: [Pillar1, Pillar2] Result: Received event: 795646f9: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor Result: Received event: 795646f9: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor Result: Received event: 795646f9: 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@6f800942[correlationID=795646f9-7684-4884-9064-6c605a788814, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noContributorsRespondingTest, to=, version=28, minVersion=24, auditTrailInformation=] 02:19:14.986 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@6f800942[correlationID=795646f9-7684-4884-9064-6c605a788814, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noContributorsRespondingTest, to=, version=28, minVersion=24, auditTrailInformation=] 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@757e13b2, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@7de752dd[correlationID=ae71aa64-c903-49ea-82fa-e9cc0743d2d5, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=noContributorsRespondingTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@729668d7[fileID=, allFileIDs=true], checksumRequestForExistingFile=] Result: Received event: ae71aa64: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums Step: Wait for 1 second Result: Received event: ae71aa64: GET_CHECKSUMS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors The following contributors didn't respond: [Pillar1, Pillar2] Result: Received event: ae71aa64: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor Result: Received event: ae71aa64: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor Result: Received event: ae71aa64: 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@7de752dd[correlationID=ae71aa64-c903-49ea-82fa-e9cc0743d2d5, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=noContributorsRespondingTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@729668d7[fileID=, allFileIDs=true], checksumRequestForExistingFile=] 02:19:15.217 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@7de752dd[correlationID=ae71aa64-c903-49ea-82fa-e9cc0743d2d5, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=noContributorsRespondingTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@729668d7[fileID=, allFileIDs=true], checksumRequestForExistingFile=] 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@29e3c7fe[correlationID=1c748662-1c9a-4f85-b5ea-c5af2e809ba2, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=oneContributorNotRespondingTest, to=, version=28, minVersion=24, auditTrailInformation=] Result: Received event: 1c748662: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails Step: Send a identification response from contributor1. Result: Received event: 1c748662: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Step: Wait 1 second. Result: Received event: 1c748662: GET_AUDIT_TRAILS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors The following contributors didn't respond: [Pillar2] Result: Received event: 1c748662: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor Result: Received event: 1c748662: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 1c748662: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1], Sending request for audit trails Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@5c29008c[correlationID=1c748662-1c9a-4f85-b5ea-c5af2e809ba2, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=oneContributorNotRespondingTest, to=, version=28, minVersion=24, auditTrailInformation=, contributor=Pillar1, fileID=, minSequenceNumber=, maxSequenceNumber=, minTimestamp=, maxTimestamp=, maxNumberOfResults=, resultAddress=] Step: Verify that the client continues to the performing phase. Step: Send a final response upload message Result: Received event: 1c748662: GET_AUDIT_TRAILS: COMPONENT_COMPLETE: ContributorID Pillar1, PartialResult=false Result: Received event: 1c748662: GET_AUDIT_TRAILS: FAILED: , Failed operation. Cause(s): [1c748662: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor] Test success: oneContributorNotRespondingTest Test starting: oneContributorNotRespondingTest Description: Verify that the client works correct without receiving identification responses from all contributors. Added fixture: Set the a identification timeout to 100 ms. Step: Start the operation. Stimuli: Calling getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@757e13b2, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@66fb1627[correlationID=6699b7e1-e6bf-4b63-adff-2145d70437ed, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=oneContributorNotRespondingTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@1cbd2c1a[fileID=, allFileIDs=true], checksumRequestForExistingFile=] Result: Received event: 6699b7e1: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums Step: Send a identification response from contributor1. Result: Received event: 6699b7e1: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Step: Wait 1 second. Result: Received event: 6699b7e1: GET_CHECKSUMS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors The following contributors didn't respond: [Pillar2] Result: Received event: 6699b7e1: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor Result: Received event: 6699b7e1: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 6699b7e1: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar1], Sending GetFileIDsRequest's Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@398a339a[correlationID=6699b7e1-e6bf-4b63-adff-2145d70437ed, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=oneContributorNotRespondingTest, to=, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@2401f1e3[fileID=, allFileIDs=true], minTimestamp=, maxTimestamp=, maxNumberOfResults=, checksumRequestForExistingFile=, resultAddress=] Step: Verify that the client continues to the performing phase. Step: Send a final response upload message Result: Received event: 6699b7e1: GET_CHECKSUMS: COMPONENT_COMPLETE: ContributorID Pillar1, PartialResult=false Result: Received event: 6699b7e1: GET_CHECKSUMS: FAILED: , Failed operation. Cause(s): [6699b7e1: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor] Test success: oneContributorNotRespondingTest Test starting: operationTimeoutTest Description: Tests the the client handles lack of final responses gracefully. Step: Set a 100 ms operation timeout. Step: Start the operation Stimuli: Calling getAuditTrails(null, null, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@52e7bed1[correlationID=51ef6e38-2414-41ab-9675-527cdafc76a7, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=operationTimeoutTest, to=, version=28, minVersion=24, auditTrailInformation=] Result: Received event: 51ef6e38: 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: 51ef6e38: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 51ef6e38: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE Result: Received event: 51ef6e38: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 51ef6e38: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1], Sending request for audit trails Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@2b686050[correlationID=51ef6e38-2414-41ab-9675-527cdafc76a7, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=operationTimeoutTest, to=, version=28, minVersion=24, auditTrailInformation=, contributor=Pillar1, fileID=, minSequenceNumber=, maxSequenceNumber=, minTimestamp=, maxTimestamp=, maxNumberOfResults=, resultAddress=] Step: Wait for 1 second Result: Received event: 51ef6e38: GET_AUDIT_TRAILS: FAILED: , Failed to receive responses from all contributors before timeout(100ms). Missing contributors [Pillar1] Test success: operationTimeoutTest Test starting: operationTimeoutTest Description: Tests the the client handles lack of final responses gracefully. Step: Set a 100 ms operation timeout. Step: Start the operation Stimuli: Calling getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@757e13b2, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@38388db2[correlationID=bed13858-a8bf-4907-88e0-383265f24e8f, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=operationTimeoutTest, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@78ffe38[fileID=, allFileIDs=true], checksumRequestForExistingFile=] Result: Received event: bed13858: 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: bed13858: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: bed13858: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE Result: Received event: bed13858: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: bed13858: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar1], Sending GetFileIDsRequest's Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@4cbac3f[correlationID=bed13858-a8bf-4907-88e0-383265f24e8f, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=operationTimeoutTest, to=, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@7862e409[fileID=, allFileIDs=true], minTimestamp=, maxTimestamp=, maxNumberOfResults=, checksumRequestForExistingFile=, resultAddress=] Step: Wait for 1 second Result: Received event: bed13858: 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@225fe13f, TEST-AUDIT) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@2737fd1d[correlationID=3f023eb9-96e0-44c2-bc98-ec97598bd113, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=getChecksumsDeliveredAtUrl, to=, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@2610cb55[fileID=default-test-file.txt, allFileIDs=], checksumRequestForExistingFile=] Result: Received event: 3f023eb9: 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: 3f023eb9: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 3f023eb9: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: 3f023eb9: GET_CHECKSUMS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2, Pillar1] Result: Received event: 3f023eb9: 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@62b0059[correlationID=3f023eb9-96e0-44c2-bc98-ec97598bd113, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=getChecksumsDeliveredAtUrl, to=, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@264129aa[fileID=default-test-file.txt, allFileIDs=], minTimestamp=, maxTimestamp=, maxNumberOfResults=, checksumRequestForExistingFile=, 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@59af828a[correlationID=3f023eb9-96e0-44c2-bc98-ec97598bd113, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=getChecksumsDeliveredAtUrl, to=, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT, pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@2177809a[fileID=default-test-file.txt, allFileIDs=], minTimestamp=, maxTimestamp=, maxNumberOfResults=, checksumRequestForExistingFile=, 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: 3f023eb9: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, NumberOfChecksums=0, PartialResult=false Result: Received event: 3f023eb9: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2, NumberOfChecksums=0, PartialResult=false Result: Received event: 3f023eb9: 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@59af828a[correlationID=3f023eb9-96e0-44c2-bc98-ec97598bd113, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=getChecksumsDeliveredAtUrl, to=, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT, pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@2177809a[fileID=default-test-file.txt, allFileIDs=], minTimestamp=, maxTimestamp=, maxNumberOfResults=, checksumRequestForExistingFile=, resultAddress=file:../bitrepository-core/src/test/resources/test-files//TEST-CHECKSUM-DELIVERY.xml-Pillar2] 02:19:16.327 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: org.bitrepository.bitrepositorymessages.GetChecksumsRequest@59af828a[correlationID=3f023eb9-96e0-44c2-bc98-ec97598bd113, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=getChecksumsDeliveredAtUrl, to=, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT, pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@2177809a[fileID=default-test-file.txt, allFileIDs=], minTimestamp=, maxTimestamp=, maxNumberOfResults=, checksumRequestForExistingFile=, 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@7b73b5c9, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@4a402ba3[correlationID=cbd7ce32-64d6-4eec-ae42-eae6208bc7d6, collectionID=SinglePillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=getChecksumsFromOtherCollection, to=Pillar2, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@65b2f815[fileID=, allFileIDs=true], checksumRequestForExistingFile=] Result: Received event: cbd7ce32: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums Step: Send an identification response from pillar2. Result: Received event: cbd7ce32: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: cbd7ce32: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2] Result: Received event: cbd7ce32: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar2], Sending GetFileIDsRequest's Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@7c3019d6[correlationID=cbd7ce32-64d6-4eec-ae42-eae6208bc7d6, collectionID=SinglePillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=getChecksumsFromOtherCollection, to=Pillar2, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@37e628c0[fileID=, allFileIDs=true], minTimestamp=, maxTimestamp=, maxNumberOfResults=, checksumRequestForExistingFile=, resultAddress=] Step: Send a complete event from the pillar Result: Received event: cbd7ce32: GET_CHECKSUMS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false Result: Received event: cbd7ce32: 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@55f4d7be[checksumType=MD5, checksumSalt=, otherChecksumType=], null, org.bitrepository.client.TestEventHandler@113b38ca, TEST-AUDIT) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@7f0dcfe6[correlationID=98eb732f-3d3f-4ccd-b1a7-207d08418207, 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@705ba09a[fileID=default-test-file.txt, allFileIDs=], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@55f4d7be[checksumType=MD5, checksumSalt=, otherChecksumType=]] Result: Received event: 98eb732f: 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: 98eb732f: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 98eb732f: GET_CHECKSUMS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 98eb732f: 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@4b5455c6[correlationID=98eb732f-3d3f-4ccd-b1a7-207d08418207, 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@5a37c1b5[fileID=default-test-file.txt, allFileIDs=], minTimestamp=, maxTimestamp=, maxNumberOfResults=, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@55f4d7be[checksumType=MD5, checksumSalt=, otherChecksumType=], resultAddress=] Step: Send a GetChecksumsFinalResponse to the client from pillar1 Result: Received event: 98eb732f: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, NumberOfChecksums=0, PartialResult=false Result: Received event: 98eb732f: 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@1558b8e7, TEST-AUDIT) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@2df44716[correlationID=d63c8aa0-6c61-416b-9e9a-47498242ecf8, 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@72fad01f[fileID=default-test-file.txt, allFileIDs=], checksumRequestForExistingFile=] Result: Received event: d63c8aa0: 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: d63c8aa0: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: d63c8aa0: GET_CHECKSUMS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: d63c8aa0: 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@2a7d12c8[correlationID=d63c8aa0-6c61-416b-9e9a-47498242ecf8, 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@25be3c66[fileID=default-test-file.txt, allFileIDs=], minTimestamp=, maxTimestamp=, maxNumberOfResults=, checksumRequestForExistingFile=, resultAddress=] Step: Send a error that the file cannot be found. Result: Received event: d63c8aa0: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FILE_NOT_FOUND_FAILURE, No such file. Result: Received event: d63c8aa0: GET_CHECKSUMS for file default-test-file.txt: FAILED: , Failed operation. Cause(s): [d63c8aa0: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FILE_NOT_FOUND_FAILURE, No such file.] Test success: testNoSuchFile Test starting: testPaging Description: Tests the GetChecksums client correctly handles functionality for limiting results, either by timestamp or result count. Step: Request checksums from with MinTimestamp, MaxTimestamp, MaxNumberOfResults set for both pillars . Stimuli: Calling getChecksums([ContributorQuery{componentID='Pillar1, minTimestamp=Fri Dec 04 02:19:17 CET 2015, maxTimestamp=Fri Dec 04 02:19:17 CET 2015, maxNumberOfResults=1}, ContributorQuery{componentID='Pillar2, minTimestamp=Fri Dec 04 02:19:17 CET 2015, maxTimestamp=Fri Dec 04 02:19:18 CET 2015, maxNumberOfResults=2}], null, null, null, org.bitrepository.client.TestEventHandler@757e13b2, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@60d6d8d0[correlationID=b9367e95-e044-4206-9b60-e4f173ae2554, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=testPaging, to=, version=28, minVersion=24, auditTrailInformation=, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@e4e4643[fileID=, allFileIDs=true], checksumRequestForExistingFile=] Result: Received event: b9367e95: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums Step: Send a IdentifyPillarsForGetChecksumsResponse from both pillars. Result: Received event: b9367e95: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: b9367e95: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: b9367e95: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2, Pillar1] Result: Received event: b9367e95: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending GetFileIDsRequest's Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@4e9b4e98[correlationID=b9367e95-e044-4206-9b60-e4f173ae2554, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=testPaging, to=, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@329b6556[fileID=, allFileIDs=true], minTimestamp=2015-12-04T02:19:17.058+01:00, maxTimestamp=2015-12-04T02:19:17.958+01:00, maxNumberOfResults=1, checksumRequestForExistingFile=, resultAddress=] Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@1eba2b8d[correlationID=b9367e95-e044-4206-9b60-e4f173ae2554, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=testPaging, to=, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@6e3f108c[fileID=, allFileIDs=true], minTimestamp=2015-12-04T02:19:17.958+01:00, maxTimestamp=2015-12-04T02:19:18.058+01:00, maxNumberOfResults=2, checksumRequestForExistingFile=, resultAddress=] Test success: testPaging Test starting: verifyGetChecksumsClientFromFactory Test success: verifyGetChecksumsClientFromFactory 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: Random1449191959034pillar is not a valid pillar for collection TwoPillarCollection The collection contains the following pillars: [Pillar1, Pillar2] Test success: unknownPillarArgumentTest Starting testcase ReplaceFileClientComponentTest Test starting: replaceClientIdentificationTimeout Description: Tests the handling of a failed identification for the ReplaceClient Step: Initialise the number of pillars and the DeleteClient. Sets the identification timeout to 100 ms. Step: Request a file to be replaced on the default pillar. Stimuli: replaceFile(default-test-file.txt, Pillar1, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@5a6a336c[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1105a7e0[checksumType=MD5, checksumSalt=, otherChecksumType=], 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@7b48f52e[checksumType=SHA1, checksumSalt=, otherChecksumType=], file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, 10, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@6c1a08f2[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1105a7e0[checksumType=MD5, checksumSalt=, otherChecksumType=], 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@7b48f52e[checksumType=SHA1, checksumSalt=, otherChecksumType=], org.bitrepository.client.TestEventHandler@6760a74e, null Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileRequest@5b6626e5[correlationID=6aad251c-805e-43f6-803b-c0e73b5862f2, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-ReplaceFileClientComponentTest-cibuild01, from=replaceClientIdentificationTimeout, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, fileID=default-test-file.txt, fileSize=] Result: Received event: 6aad251c: 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: 6aad251c: 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: 6aad251c: REPLACE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor Result: Received event: 6aad251c: 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@48b3a9ed[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6586480a[checksumType=MD5, checksumSalt=, otherChecksumType=], 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@4962f58e[checksumType=SHA1, checksumSalt=, otherChecksumType=], file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, 10, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@30ecf828[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6586480a[checksumType=MD5, checksumSalt=, otherChecksumType=], 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@4962f58e[checksumType=SHA1, checksumSalt=, otherChecksumType=], org.bitrepository.client.TestEventHandler@65c5c319, null Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileRequest@325401b3[correlationID=6314bd6e-4e47-475e-85d1-c470f2be8192, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-ReplaceFileClientComponentTest-cibuild01, from=replaceClientOperationTimeout, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, fileID=default-test-file.txt, fileSize=] Result: Received event: 6314bd6e: 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: 6314bd6e: REPLACE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 6314bd6e: REPLACE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 6314bd6e: 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@3bbed4fa[correlationID=6314bd6e-4e47-475e-85d1-c470f2be8192, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-ReplaceFileClientComponentTest-cibuild01, from=replaceClientOperationTimeout, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@48b3a9ed[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6586480a[checksumType=MD5, checksumSalt=, otherChecksumType=], 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@4962f58e[checksumType=SHA1, checksumSalt=, otherChecksumType=], fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=10, checksumDataForNewFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@30ecf828[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6586480a[checksumType=MD5, checksumSalt=, otherChecksumType=], 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@4962f58e[checksumType=SHA1, checksumSalt=, otherChecksumType=]] Step: Validate the steps of the ReplaceClient by going through the events. Step: Do not respond. Just await the timeout. Result: Received event: 6314bd6e: 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@5c7f8c9f[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2ce33999[checksumType=MD5, checksumSalt=, otherChecksumType=], 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@677b5145[checksumType=SHA1, checksumSalt=, otherChecksumType=], file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, 0, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@5145dc7[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2ce33999[checksumType=MD5, checksumSalt=, otherChecksumType=], 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@677b5145[checksumType=SHA1, checksumSalt=, otherChecksumType=], org.bitrepository.client.TestEventHandler@25af328e, null Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileRequest@10b5f853[correlationID=996dd983-b602-4c5a-8396-ac008592efeb, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-ReplaceFileClientComponentTest-cibuild01, from=replaceClientPillarFailed, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, fileID=default-test-file.txt, fileSize=] Result: Received event: 996dd983: 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: 996dd983: REPLACE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 996dd983: REPLACE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 996dd983: 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@a24e874[correlationID=996dd983-b602-4c5a-8396-ac008592efeb, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-ReplaceFileClientComponentTest-cibuild01, from=replaceClientPillarFailed, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@5c7f8c9f[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2ce33999[checksumType=MD5, checksumSalt=, otherChecksumType=], 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@677b5145[checksumType=SHA1, checksumSalt=, otherChecksumType=], fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@5145dc7[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2ce33999[checksumType=MD5, checksumSalt=, otherChecksumType=], 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@677b5145[checksumType=SHA1, checksumSalt=, otherChecksumType=]] Step: Validate the steps of the ReplaceClient by going through the events. Step: Send a failed response message to the ReplaceClient. Result: Received event: 996dd983: REPLACE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE, Verifying that a failure can be understood! Result: Received event: 996dd983: REPLACE_FILE for file default-test-file.txt: FAILED: , Failed operation. Cause(s): [996dd983: 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@2a89db92[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@22ea05b6[checksumType=MD5, checksumSalt=, otherChecksumType=], 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@235cbf67[checksumType=SHA1, checksumSalt=, otherChecksumType=], file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, 10, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@62414b20[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@22ea05b6[checksumType=MD5, checksumSalt=, otherChecksumType=], 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@235cbf67[checksumType=SHA1, checksumSalt=, otherChecksumType=], org.bitrepository.client.TestEventHandler@6f049b1, null Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileRequest@74453b6c[correlationID=7d619a04-d2a9-478a-8525-826f3d54a158, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-ReplaceFileClientComponentTest-cibuild01, from=replaceClientTester, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, fileID=default-test-file.txt, fileSize=] Result: Received event: 7d619a04: 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: 7d619a04: REPLACE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 7d619a04: REPLACE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 7d619a04: 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@5ad4502b[correlationID=7d619a04-d2a9-478a-8525-826f3d54a158, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-ReplaceFileClientComponentTest-cibuild01, from=replaceClientTester, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@2a89db92[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@22ea05b6[checksumType=MD5, checksumSalt=, otherChecksumType=], 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@235cbf67[checksumType=SHA1, checksumSalt=, otherChecksumType=], fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=10, checksumDataForNewFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@62414b20[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@22ea05b6[checksumType=MD5, checksumSalt=, otherChecksumType=], 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@235cbf67[checksumType=SHA1, checksumSalt=, otherChecksumType=]] 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: 7d619a04: 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: 7d619a04: REPLACE_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, checksum for new file: 'org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@62414b20[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@22ea05b6[checksumType=MD5, checksumSalt=, otherChecksumType=], 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: 7d619a04: 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@1a9d5a73[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@3a05ba57[checksumType=MD5, checksumSalt=, otherChecksumType=], 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@5773269[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@3a05ba57[checksumType=MD5, checksumSalt=, otherChecksumType=], 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@2e9290bc[checksumType=MD5, checksumSalt={-86}, otherChecksumType=], org.bitrepository.client.TestEventHandler@5e2c19df, null Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileRequest@49ecd74f[correlationID=3c725d50-019c-4a45-be4e-ecd7d67337a0, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-ReplaceFileClientComponentTest-cibuild01, from=saltedReturnChecksumsForNewFileWithChecksumPillar, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, fileID=default-test-file.txt, fileSize=] Result: Received event: 3c725d50: 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: 3c725d50: REPLACE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 3c725d50: REPLACE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 3c725d50: 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@4f99290b[correlationID=3c725d50-019c-4a45-be4e-ecd7d67337a0, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-ReplaceFileClientComponentTest-cibuild01, from=saltedReturnChecksumsForNewFileWithChecksumPillar, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@1a9d5a73[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@3a05ba57[checksumType=MD5, checksumSalt=, otherChecksumType=], 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=, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@5773269[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@3a05ba57[checksumType=MD5, checksumSalt=, otherChecksumType=], 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=] 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: Random1449191960376pillar is not a valid pillar for collection TwoPillarCollection The collection contains the following pillars: [Pillar1, Pillar2] Test success: unknownPillarArgumentTest 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@67cd916[checksumType=MD5, checksumSalt=, otherChecksumType=], org.bitrepository.client.TestEventHandler@153c5283, TEST-AUDIT-TRAIL) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@2f88c81a[correlationID=1555e229-7cd5-460d-b54a-3d100e634bf9, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=defaultReturnChecksumsWithChecksumPillar, to=, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, fileID=default-test-file.txt, fileSize=0] Result: Received event: 1555e229: 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: 1555e229: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Step: Send an normal identification response from pillar2. Result: Received event: 1555e229: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: 1555e229: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2] Result: Received event: 1555e229: 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@48c7f0d9[correlationID=1555e229-7cd5-460d-b54a-3d100e634bf9, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=defaultReturnChecksumsWithChecksumPillar, to=, 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=, checksumRequestForNewFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@67cd916[checksumType=MD5, checksumSalt=, otherChecksumType=]] Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@e083961[correlationID=1555e229-7cd5-460d-b54a-3d100e634bf9, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=defaultReturnChecksumsWithChecksumPillar, to=, 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=, checksumRequestForNewFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@67cd916[checksumType=MD5, checksumSalt=, otherChecksumType=]] 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@5fb03284, TEST-AUDIT-TRAIL) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@1dd241a0[correlationID=146d2542-463b-4167-bd87-d7f8892e67c0, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=fileExistsOnPillarChecksumFromPillarNoClientChecksum, to=, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, fileID=default-test-file.txt, fileSize=0] Result: Received event: 146d2542: 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: 146d2542: 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@4de4c093[responseCode=DUPLICATE_FILE_FAILURE, responseText=Testing the handling of 'DUPLICATE FILE' identification.] (existing file checksum does not match) Result: Received event: 146d2542: 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@5faea3cb[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@169f4020[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={-70}, calculationTimestamp=2015-12-04T02:19:20.662+01:00], null, org.bitrepository.client.TestEventHandler@419e0ee5, TEST-AUDIT-TRAIL) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@6630e32d[correlationID=499d9dbd-b849-4049-81be-71d2b2f217c6, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=fileExistsOnPillarDifferentChecksumFromPillar, to=, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, fileID=default-test-file.txt, fileSize=0] Result: Received event: 499d9dbd: 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: 499d9dbd: 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@1100a8f6[responseCode=DUPLICATE_FILE_FAILURE, responseText=Testing the handling of 'DUPLICATE FILE' identification.] (existing file checksum does not match) Result: Received event: 499d9dbd: 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@34fb622b, TEST-AUDIT-TRAIL) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@44259318[correlationID=b48f64ef-d14a-4bb8-91f0-5bbfd48c480b, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=fileExistsOnPillarNoChecksumFromPillar, to=, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, fileID=default-test-file.txt, fileSize=0] Result: Received event: b48f64ef: 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: b48f64ef: 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@623efc15[responseCode=DUPLICATE_FILE_FAILURE, responseText=Testing the handling of 'DUPLICATE FILE' identification.] Result: Received event: b48f64ef: 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@45559fc8, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@6a2b1cdc[correlationID=1dbbaa09-9f0b-41fb-8daf-92b2c9e55f60, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=noPillarsResponding, to=, version=28, minVersion=24, auditTrailInformation=, fileID=default-test-file.txt, fileSize=0] Result: Received event: 1dbbaa09: 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: 1dbbaa09: 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: 1dbbaa09: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor Result: Received event: 1dbbaa09: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor Result: Received event: 1dbbaa09: 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@790b51f1, TEST-AUDIT-TRAIL) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@27bdf7d[correlationID=0dd33d58-2d33-40c4-b39f-0fc10ab1fcf8, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=noReturnChecksumsWithChecksumPillar, to=, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, fileID=default-test-file.txt, fileSize=0] Result: Received event: 0dd33d58: 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: 0dd33d58: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Step: Send an normal identification response from pillar2. Result: Received event: 0dd33d58: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: 0dd33d58: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2] Result: Received event: 0dd33d58: 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@4536cfd3[correlationID=0dd33d58-2d33-40c4-b39f-0fc10ab1fcf8, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=noReturnChecksumsWithChecksumPillar, to=, 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=, checksumRequestForNewFile=] Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@196a703f[correlationID=0dd33d58-2d33-40c4-b39f-0fc10ab1fcf8, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=noReturnChecksumsWithChecksumPillar, to=, 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=, checksumRequestForNewFile=] 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@7485c18, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@25ff482a[correlationID=78f72ff2-2deb-46bc-909a-7284e084e07c, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=normalPutFile, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, fileID=default-test-file.txt, fileSize=0] Result: Received event: 78f72ff2: 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: 78f72ff2: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 78f72ff2: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 78f72ff2: 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@13d2a198[correlationID=78f72ff2-2deb-46bc-909a-7284e084e07c, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=normalPutFile, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=, checksumRequestForNewFile=] 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: 78f72ff2: 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: 78f72ff2: PUT_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, requestedChecksumResult=null Result: Received event: 78f72ff2: PUT_FILE for file default-test-file.txt: COMPLETE: Test success: normalPutFile Test starting: onePillarPutRetryFailure Reference: BITMAG-810 Reference client should be able to retry failed file transfers 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@7779243b, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@21f7bdf[correlationID=bdf88fec-a15c-4feb-b574-ead0d6806eea, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarPutRetryFailure, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, fileID=default-test-file.txt, fileSize=0] Result: Received event: bdf88fec: 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: bdf88fec: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: bdf88fec: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: bdf88fec: 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@44c874fe[correlationID=bdf88fec-a15c-4feb-b574-ead0d6806eea, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarPutRetryFailure, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=, checksumRequestForNewFile=] 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@7aaed8a0[correlationID=bdf88fec-a15c-4feb-b574-ead0d6806eea, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarPutRetryFailure, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=, checksumRequestForNewFile=] Result: Received event: bdf88fec: 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@31695a9[correlationID=bdf88fec-a15c-4feb-b574-ead0d6806eea, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarPutRetryFailure, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=, checksumRequestForNewFile=] Result: Received event: bdf88fec: 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: bdf88fec: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FILE_TRANSFER_FAILURE Result: Received event: bdf88fec: PUT_FILE for file default-test-file.txt: FAILED: , Failed operation. Cause(s): [bdf88fec: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FILE_TRANSFER_FAILURE] Test success: onePillarPutRetryFailure Test starting: onePillarPutRetrySuccess Reference: BITMAG-810 Reference client should be able to retry failed file transfers 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@7dd1b3c0, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@51386a2e[correlationID=d057acf9-e19b-4136-a96a-8ce9ae8f42ef, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarPutRetrySuccess, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, fileID=default-test-file.txt, fileSize=0] Result: Received event: d057acf9: 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: d057acf9: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: d057acf9: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: d057acf9: 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@7a3a7f99[correlationID=d057acf9-e19b-4136-a96a-8ce9ae8f42ef, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarPutRetrySuccess, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=, checksumRequestForNewFile=] 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@a859cad[correlationID=d057acf9-e19b-4136-a96a-8ce9ae8f42ef, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarPutRetrySuccess, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=, checksumRequestForNewFile=] Result: Received event: d057acf9: 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: d057acf9: PUT_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, requestedChecksumResult=null Result: Received event: d057acf9: PUT_FILE for file default-test-file.txt: COMPLETE: Test success: onePillarPutRetrySuccess Test starting: onePillarRespondingWithPartialPutAllowed Reference: BITMAG-598 It should be possible to putFiles, even though only a subset of the pillars are available 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@53f7a390, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@2c981784[correlationID=4103c03d-216b-404a-8d02-b1d67a99323e, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarRespondingWithPartialPutAllowed, to=, version=28, minVersion=24, auditTrailInformation=, fileID=default-test-file.txt, fileSize=0] Result: Received event: 4103c03d: 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: 4103c03d: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Step: Await the timeout. Result: Received event: 4103c03d: 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: 4103c03d: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor Result: Received event: 4103c03d: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 4103c03d: 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@68676319[correlationID=4103c03d-216b-404a-8d02-b1d67a99323e, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarRespondingWithPartialPutAllowed, to=, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=, checksumRequestForNewFile=] Step: The client should proceed to send a putFileOperation request to the responding pillar. Step: Send a pillar complete event Result: Received event: 4103c03d: PUT_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, requestedChecksumResult=null Result: Received event: 4103c03d: PUT_FILE for file default-test-file.txt: FAILED: , Failed operation. Cause(s): [4103c03d: 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@ba27c12, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@3c7a3f0d[correlationID=2f6afc3b-b2a3-417e-b120-f3670a569360, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarRespondingWithPartialPutDisallowed, to=, version=28, minVersion=24, auditTrailInformation=, fileID=default-test-file.txt, fileSize=0] Result: Received event: 2f6afc3b: 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: 2f6afc3b: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Step: Await the timeout. Result: Received event: 2f6afc3b: 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: 2f6afc3b: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor Result: Received event: 2f6afc3b: 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@6bcb493e, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@225be644[correlationID=abe0c61b-a530-4498-837b-b0428d22cb2b, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=putClientOperationTimeout, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, fileID=default-test-file.txt, fileSize=0] Result: Received event: abe0c61b: 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: abe0c61b: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: abe0c61b: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: abe0c61b: 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@527afebf[correlationID=abe0c61b-a530-4498-837b-b0428d22cb2b, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=putClientOperationTimeout, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=, checksumRequestForNewFile=] Step: Validate the steps of the PutClient by going through the events. Step: Do not respond. Just await the timeout. Result: Received event: abe0c61b: 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@6a2c3fc2, TEST-AUDIT-TRAIL) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@37c595f4[correlationID=407efb62-e4b3-4a25-a463-619d34c81525, 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: 407efb62: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file Step: Send pillar response. Result: Received event: 407efb62: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 407efb62: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 407efb62: 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@b0ba49[correlationID=407efb62-e4b3-4a25-a463-619d34c81525, 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=, checksumRequestForNewFile=] Step: Validate the steps of the PutClient by going through the events. Step: Send a failed response message to the PutClient. Result: Received event: 407efb62: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE, Verifying that a failure can be understood! Result: Received event: 407efb62: PUT_FILE for file default-test-file.txt: FAILED: , Failed operation. Cause(s): [407efb62: 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: BITMAG-925 Client will always try to put to the pillars defined in the first collection 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@380e8b10, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@de3cdeb[correlationID=b6fce54c-35c8-4733-a27b-27d5e85178e0, collectionID=SinglePillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=putToOtherCollection, to=Pillar2, version=28, minVersion=24, auditTrailInformation=, fileID=default-test-file.txt, fileSize=0] Result: Received event: b6fce54c: 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: b6fce54c: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: b6fce54c: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2] Result: Received event: b6fce54c: 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@1c1b9a9a[correlationID=b6fce54c-35c8-4733-a27b-27d5e85178e0, collectionID=SinglePillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=putToOtherCollection, to=Pillar2, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar2, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=, checksumRequestForNewFile=] Step: Send a put complete event from the pillar Result: Received event: b6fce54c: PUT_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2, requestedChecksumResult=null Result: Received event: b6fce54c: 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: BITMAG-677put, replace and delete clients fails if return checksums are requested and a checksumpillar is involved 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@267f6b32[checksumType=HMAC_MD5, checksumSalt={-86}, otherChecksumType=], org.bitrepository.client.TestEventHandler@3a084fc7, TEST-AUDIT-TRAIL) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@4e457635[correlationID=e974342d-70f6-43b7-88e3-0218686dba79, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=saltedReturnChecksumsWithChecksumPillar, to=, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, fileID=default-test-file.txt, fileSize=0] Result: Received event: e974342d: 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: e974342d: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Step: Send an normal identification response from pillar2. Result: Received event: e974342d: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: e974342d: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2] Result: Received event: e974342d: 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@64e4e885[correlationID=e974342d-70f6-43b7-88e3-0218686dba79, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=saltedReturnChecksumsWithChecksumPillar, to=, 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=, checksumRequestForNewFile=] Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@175cef2[correlationID=e974342d-70f6-43b7-88e3-0218686dba79, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=saltedReturnChecksumsWithChecksumPillar, to=, 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=, checksumRequestForNewFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@267f6b32[checksumType=HMAC_MD5, checksumSalt={-86}, otherChecksumType=]] 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@584c62b[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@4a43aaad[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-12-04T02:19:22.188+01:00], null, org.bitrepository.client.TestEventHandler@7a8c1916, TEST-AUDIT-TRAIL) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@66f44bef[correlationID=16c7c1b2-f908-4324-bfeb-1405484520de, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=sameFileExistsOnOnePillar, to=, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, fileID=default-test-file.txt, fileSize=0] Result: Received event: 16c7c1b2: 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: 16c7c1b2: PUT_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, requestedChecksumResult=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@8fd4fac[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@4c92c66f[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-12-04T02:19:22.191+01:00], File already existed on Pillar1 Step: Send an identification response from the second pillar. Result: Received event: 16c7c1b2: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2 Result: Received event: 16c7c1b2: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2] Result: Received event: 16c7c1b2: 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@156c2fa2[correlationID=16c7c1b2-f908-4324-bfeb-1405484520de, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=sameFileExistsOnOnePillar, to=, 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@584c62b[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@4a43aaad[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-12-04T02:19:22.188+01:00], checksumRequestForNewFile=] Step: The client should proceed to send a putFileOperation request to the second pillar. Step: Send a pillar complete event Result: Received event: 16c7c1b2: PUT_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2, requestedChecksumResult=null Result: Received event: 16c7c1b2: 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 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 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: Random1449191964723pillar is not a valid pillar for collection TwoPillarCollection The collection contains the following pillars: [Pillar1, Pillar2] Test success: unknownPillarArgumentTest 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@6c10a403[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@375ef82a[checksumType=MD5, checksumSalt=, otherChecksumType=], 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@76b09f19[checksumType=SHA1, checksumSalt=, otherChecksumType=], eventHandler, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@171301f[correlationID=bf467ea4-3829-4e58-8552-c57810bf3d0b, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientIdentificationTimeout, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, fileID=default-test-file.txt] Result: Received event: bf467ea4: 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: bf467ea4: 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: bf467ea4: DELETE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor Result: Received event: bf467ea4: 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@3e727eef[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2497e6d3[checksumType=MD5, checksumSalt=, otherChecksumType=], 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@3930afed[checksumType=SHA1, checksumSalt=, otherChecksumType=], eventHandler, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@5899082a[correlationID=af0c6f81-47e1-45b5-80ec-7abde97bb58e, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientOperationTimeout, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, fileID=default-test-file.txt] Result: Received event: af0c6f81: 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: af0c6f81: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: af0c6f81: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: af0c6f81: 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@6e0b41cb[correlationID=af0c6f81-47e1-45b5-80ec-7abde97bb58e, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientOperationTimeout, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@3e727eef[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2497e6d3[checksumType=MD5, checksumSalt=, otherChecksumType=], 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@3930afed[checksumType=SHA1, checksumSalt=, otherChecksumType=]] Step: Validate the steps of the DeleteClient by going through the events. Step: Do not respond. Just await the timeout. Result: Received event: af0c6f81: 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@66c4fa48[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@11336197[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-12-04T02:19:26.170+01:00], null, eventHandler, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@15c46ce5[correlationID=8d960886-ca69-4fa8-a742-f3b3a4f15411, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientOtherPillarFailedDuringIdentification, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, fileID=default-test-file.txt] Result: Received event: 8d960886: 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: 8d960886: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 8d960886: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 8d960886: 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@a1ad17d[correlationID=8d960886-ca69-4fa8-a742-f3b3a4f15411, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientOtherPillarFailedDuringIdentification, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@66c4fa48[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@11336197[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-12-04T02:19:26.170+01:00], checksumRequestForExistingFile=] Step: Send a final response message from pillar 1 to the DeleteClient. Result: Received event: 8d960886: DELETE_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, DeleteFileResult=null Result: Received event: 8d960886: 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@3e2f3bc6[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@40a8a626[checksumType=MD5, checksumSalt=, otherChecksumType=], 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@62a9d5e7[checksumType=SHA1, checksumSalt=, otherChecksumType=], eventHandler, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@7b7115c2[correlationID=a91deac9-5686-40c7-969e-9528f64b1d2b, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientPillarFailedDuringPerform, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, fileID=default-test-file.txt] Result: Received event: a91deac9: 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: a91deac9: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: a91deac9: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: a91deac9: 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@395be849[correlationID=a91deac9-5686-40c7-969e-9528f64b1d2b, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientPillarFailedDuringPerform, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@3e2f3bc6[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@40a8a626[checksumType=MD5, checksumSalt=, otherChecksumType=], 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@62a9d5e7[checksumType=SHA1, checksumSalt=, otherChecksumType=]] Step: Validate the steps of the DeleteClient by going through the events. Step: Send a failed response message to the DeleteClient. Result: Received event: a91deac9: DELETE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE, Verifying that a failure can be understood! Result: Received event: a91deac9: DELETE_FILE for file default-test-file.txt: FAILED: , Failed operation. Cause(s): [a91deac9: 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@120d6db2[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@38289dd8[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-12-04T02:19:27.388+01:00], null, eventHandler, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@11c0f55c[correlationID=a3374ac7-e0ad-4868-b532-2ac16a8adbbc, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientSpecifiedPillarFailedDuringIdentification, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, fileID=default-test-file.txt] Result: Received event: a3374ac7: 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: a3374ac7: DELETE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: IDENTIFICATION_NEGATIVE Result: Received event: a3374ac7: 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@55acd2a8[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@195cca8f[checksumType=MD5, checksumSalt=, otherChecksumType=], 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@7c0e7a[checksumType=SHA1, checksumSalt=, otherChecksumType=], eventHandler, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@2c128268[correlationID=43d5886c-a8db-4219-a03b-266be2406e80, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientTester, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, fileID=default-test-file.txt] Result: Received event: 43d5886c: 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: 43d5886c: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 43d5886c: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 43d5886c: 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@60ef851e[correlationID=43d5886c-a8db-4219-a03b-266be2406e80, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientTester, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@55acd2a8[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@195cca8f[checksumType=MD5, checksumSalt=, otherChecksumType=], 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@7c0e7a[checksumType=SHA1, checksumSalt=, otherChecksumType=]] 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: 43d5886c: 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: 43d5886c: DELETE_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, DeleteFileResult=null Result: Received event: 43d5886c: 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@5e1f3c74[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1e94fe1d[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-12-04T02:19:27.549+01:00], null, eventHandler, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@5e789bd6[correlationID=df044c2d-1888-4658-8a9d-4c74f9f576e5, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteOnChecksumPillar, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, fileID=default-test-file.txt] Result: Received event: df044c2d: 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: df044c2d: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: df044c2d: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: df044c2d: 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@56b4e8c0[correlationID=df044c2d-1888-4658-8a9d-4c74f9f576e5, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteOnChecksumPillar, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@5e1f3c74[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1e94fe1d[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-12-04T02:19:27.549+01:00], checksumRequestForExistingFile=] 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@1de1dda1[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@46347cba[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-12-04T02:19:29.644+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6a18283e[checksumType=MD5, checksumSalt=, otherChecksumType=], eventHandler, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@4948d3ef[correlationID=a6fe6821-6b3b-4569-9bf2-cd65b3f9ff02, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteOnChecksumPillarWithDefaultReturnChecksumType, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, fileID=default-test-file.txt] Result: Received event: a6fe6821: 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: a6fe6821: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: a6fe6821: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: a6fe6821: 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@3f6375ee[correlationID=a6fe6821-6b3b-4569-9bf2-cd65b3f9ff02, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteOnChecksumPillarWithDefaultReturnChecksumType, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@1de1dda1[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@46347cba[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-12-04T02:19:29.644+01:00], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6a18283e[checksumType=MD5, checksumSalt=, otherChecksumType=]] 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@32505319[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7b47355b[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-12-04T02:19:29.724+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@735fc94f[checksumType=MD5, checksumSalt={-86}, otherChecksumType=], eventHandler, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@6de2d8f4[correlationID=1b2c8f0d-7ca7-40a4-94d5-cda7c6582da6, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteOnChecksumPillarWithSaltedReturnChecksumType, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, fileID=default-test-file.txt] Result: Received event: 1b2c8f0d: 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: 1b2c8f0d: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: 1b2c8f0d: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1] Result: Received event: 1b2c8f0d: 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@1f358ddf[correlationID=1b2c8f0d-7ca7-40a4-94d5-cda7c6582da6, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteOnChecksumPillarWithSaltedReturnChecksumType, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@32505319[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7b47355b[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-12-04T02:19:29.724+01:00], checksumRequestForExistingFile=] 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@4014f892[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@5f131b6f[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-12-04T02:19:29.800+01:00], null, eventHandler, null) Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@2c3077bf[correlationID=ec757af2-ed15-44ae-a2e2-ecd4f204ed25, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=fileAlreadyDeletedFromPillar, to=Pillar1, version=28, minVersion=24, auditTrailInformation=, fileID=default-test-file.txt] Result: Received event: ec757af2: 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: ec757af2: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1 Result: Received event: ec757af2: DELETE_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, DeleteFileResult=null Result: Received event: ec757af2: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [] Result: Received event: ec757af2: 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 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: Random1449191972012pillar is not a valid pillar for collection TwoPillarCollection The collection contains the following pillars: [Pillar1, Pillar2] Test success: unknownPillarArgumentTest Finished testcase Finished suite Finished project Tests run: 156, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 56.502 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 [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building Bitrepository Service 1.6-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-service --- [INFO] Deleting /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-service/target [INFO] [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ bitrepository-service --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 7 resources [INFO] [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ bitrepository-service --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 53 source files to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-service/target/classes [INFO] [INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ bitrepository-service --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ bitrepository-service --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 9 source files to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-service/target/test-classes [INFO] [INFO] --- maven-surefire-plugin:2.17:test (default-test) @ bitrepository-service --- [INFO] Surefire report directory: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-service/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 InvalidMessageExceptionTest Test starting: testIdentifyContributor 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: testIdentifyContributor Test starting: componentIDTest Test success: componentIDTest Starting testcase IdentifyContributorExceptionTest Test starting: testIdentifyContributor 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: testIdentifyContributor Starting testcase AuditTrailContributorDatabaseTest Test starting: testAuditTrailDatabaseFunctions Description: Testing the basic functions of the audit trail database interface. Step: Setup varibles and the database connection. Step: Populate the database. Step: Test extracting all the events Step: Test extracting the events for fileID1 Step: Test extracting the events for fileID2 Step: Test extracting the events with the sequence number at least equal to the largest sequence number. Step: Test extracting the events for fileID1 with sequence number 2 or more Step: Test extracting the events for fileID1 with at most sequence number 2 Step: Test extracting at most 3 events Step: Test extracting at most 1000 events Step: Test extracting from another collection Test success: testAuditTrailDatabaseFunctions Test starting: testAuditTrailDatabaseIngest Description: Testing the ingest of data. Step: Setup varibles and the database connection. Step: Test with all data. Step: Test with no collection Step: Test with with no file id. Step: Test with with no actor. Step: Test with with no info. Step: Test with with no audittrail. Step: Test with with no operationID. Step: Test with with no certificateID. Step: Test with with no action. Step: Test with with very large file id. Step: Test with with very large actor name. Step: Test with with very large info. Step: Test with with very large audittrail. Test success: testAuditTrailDatabaseIngest Starting testcase IllegalOperationExceptionTest Test starting: testIdentifyContributor 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: testIdentifyContributor Starting testcase AuditTrailContributorDatabaseMigrationTest Test starting: testMigratingAuditContributorDatabase Description: Tests that the database can be migrated to latest version with the provided scripts. Step: Validate setup Step: Ingest a entry to the database without the collection id Step: Perform migration 02:19:49.432 WARN o.b.service.database.DatabaseUtils - Migrating AuditContributorDB from version 1 to 2. 02:19:49.562 WARN o.b.service.database.DatabaseUtils - Migrating AuditContributorDB from version 2 to 3. 02:19:49.875 WARN o.b.service.database.DatabaseUtils - Migrating AuditContributorDB from version 3 to 4. Test success: testMigratingAuditContributorDatabase Finished testcase Finished suite Finished project Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 9.396 sec - in TestSuite Results : Tests run: 7, Failures: 0, Errors: 0, Skipped: 0 [JENKINS] Recording test results [INFO] [INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ bitrepository-service --- [INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-service/target/bitrepository-service-1.6-SNAPSHOT.jar [INFO] [INFO] --- maven-jar-plugin:2.4:test-jar (default) @ bitrepository-service --- [INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-service/target/bitrepository-service-1.6-SNAPSHOT-tests.jar [INFO] [INFO] --- maven-source-plugin:2.2.1:jar-no-fork (attach-sources-no-fork) @ bitrepository-service --- [INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-service/target/bitrepository-service-1.6-SNAPSHOT-sources.jar [INFO] [INFO] --- maven-install-plugin:2.5.1:install (default-install) @ bitrepository-service --- [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-service/target/bitrepository-service-1.6-SNAPSHOT.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-service/1.6-SNAPSHOT/bitrepository-service-1.6-SNAPSHOT.jar [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-service/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-service/1.6-SNAPSHOT/bitrepository-service-1.6-SNAPSHOT.pom [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-service/target/bitrepository-service-1.6-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-service/1.6-SNAPSHOT/bitrepository-service-1.6-SNAPSHOT-tests.jar [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-service/target/bitrepository-service-1.6-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-service/1.6-SNAPSHOT/bitrepository-service-1.6-SNAPSHOT-sources.jar [JENKINS] Archiving disabled [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building Bitrepository Integrity Service 1.6-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-integrity-service --- [INFO] Deleting /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integrity-service/target [INFO] [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ bitrepository-integrity-service --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 12 resources [INFO] [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ bitrepository-integrity-service --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 67 source files to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integrity-service/target/classes [INFO] [INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ bitrepository-integrity-service --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ bitrepository-integrity-service --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 24 source files to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integrity-service/target/test-classes [INFO] [INFO] --- maven-surefire-plugin:2.17:test (default-test) @ bitrepository-integrity-service --- [INFO] Surefire report directory: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integrity-service/target/surefire-reports ------------------------------------------------------- T E S T S ------------------------------------------------------- Running TestSuite Configuring TestNG with: TestNG652Configurator Starting test project Integration Service Test Suite: Surefire suite Test starting: testConstructor Test success: testConstructor Test starting: testFailContributor Test success: testFailContributor Test starting: testFinishContributor Test success: testFinishContributor Test starting: testReloadContributors Test success: testReloadContributors Test starting: testRetry Test success: testRetry Test starting: testSucceed Test success: testSucceed Starting testcase MaxChecksumAgeProviderTest Test starting: testNoPillarSpecificSetting Description: Test the MaxChecksumAge when no settings are defined for the specific pillar Step: Create a MaxChecksumAgeProvider with settings containing a default MaxAge of 10 and no pillar specific settings Test success: testNoPillarSpecificSetting Test starting: testNoSettings Description: Test the MaxChecksumAge when no settings are defined Step: Create a MaxChecksumAgeProvider with null settings and a default MaxAge of 100 Test success: testNoSettings Test starting: testPillarSpecificSetting Description: Test the MaxChecksumAge when a value has been defined for specific pillars Step: Create a MaxChecksumAgeProvider with settings containing a default MaxAge of 10, pillar1MaxChecksumAge of 1001 and pillar2 MaxChecksumAge of 1002 Test success: testPillarSpecificSetting Starting testcase PutFileStepTest Test starting: testNegativeReply Description: Test the step for getting the file can handle FAILURE operation event. Test success: testNegativeReply Test starting: testPositiveReply Description: Test the step for getting the file can handle COMPLETE operation event. Test success: testPositiveReply Starting testcase RepairMissingFilesWorkflowTest Test starting: testFailedGetFile Description: Test that the workflow does not try to put a file, if it fails to get it. Step: Prepare for calls to mocks to fail when performing get-file Step: Run missing checksum step. 02:20:02.412 ERROR o.b.i.w.RepairMissingFilesWorkflow - Failure in step: 'Performing GetFile for 'test-file-1'.'. java.lang.IllegalStateException: Aborting workflow due to failure getting the file 'test-file-1'. Cause: null: null: FAILED: , failure at org.bitrepository.integrityservice.workflow.step.GetFileStep.performStep(GetFileStep.java:74) ~[classes/:na] at org.bitrepository.service.workflow.Workflow.performStep(Workflow.java:63) ~[bitrepository-service-1.6-SNAPSHOT.jar:1.6-SNAPSHOT] at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflow.getFileStep(RepairMissingFilesWorkflow.java:177) [classes/:na] at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflow.repairMissingFilesForPillar(RepairMissingFilesWorkflow.java:117) [classes/:na] at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflow.start(RepairMissingFilesWorkflow.java:89) [classes/:na] at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflowTest.testFailedGetFile(RepairMissingFilesWorkflowTest.java:194) [test-classes/:na] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_11] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_11] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_11] at java.lang.reflect.Method.invoke(Method.java:483) ~[na:1.8.0_11] at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84) [testng-6.8.8.jar:na] at org.testng.internal.Invoker.invokeMethod(Invoker.java:714) [testng-6.8.8.jar:na] at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901) [testng-6.8.8.jar:na] at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231) [testng-6.8.8.jar:na] at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127) [testng-6.8.8.jar:na] at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111) [testng-6.8.8.jar:na] at org.testng.TestRunner.privateRun(TestRunner.java:767) [testng-6.8.8.jar:na] at org.testng.TestRunner.run(TestRunner.java:617) [testng-6.8.8.jar:na] at org.testng.SuiteRunner.runTest(SuiteRunner.java:348) [testng-6.8.8.jar:na] at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:343) [testng-6.8.8.jar:na] at org.testng.SuiteRunner.privateRun(SuiteRunner.java:305) [testng-6.8.8.jar:na] at org.testng.SuiteRunner.run(SuiteRunner.java:254) [testng-6.8.8.jar:na] at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) [testng-6.8.8.jar:na] at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) [testng-6.8.8.jar:na] at org.testng.TestNG.runSuitesSequentially(TestNG.java:1224) [testng-6.8.8.jar:na] at org.testng.TestNG.runSuitesLocally(TestNG.java:1149) [testng-6.8.8.jar:na] at org.testng.TestNG.run(TestNG.java:1057) [testng-6.8.8.jar:na] at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:115) [surefire-testng-2.17.jar:2.17] at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:204) [surefire-testng-2.17.jar:2.17] at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:107) [surefire-testng-2.17.jar:2.17] at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:112) [surefire-testng-2.17.jar:2.17] at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) [surefire-booter-2.17.jar:2.17] at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) [surefire-booter-2.17.jar:2.17] at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) [surefire-booter-2.17.jar:2.17] 02:20:02.418 WARN o.b.i.w.RepairMissingFilesWorkflow - Error occured during repair of missing file, 'test-file-1'. Tries to continue. java.lang.RuntimeException: Failed to run step Performing GetFile for 'test-file-1'. at org.bitrepository.service.workflow.Workflow.performStep(Workflow.java:69) ~[bitrepository-service-1.6-SNAPSHOT.jar:1.6-SNAPSHOT] at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflow.getFileStep(RepairMissingFilesWorkflow.java:177) [classes/:na] at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflow.repairMissingFilesForPillar(RepairMissingFilesWorkflow.java:117) [classes/:na] at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflow.start(RepairMissingFilesWorkflow.java:89) [classes/:na] at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflowTest.testFailedGetFile(RepairMissingFilesWorkflowTest.java:194) [test-classes/:na] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_11] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_11] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_11] at java.lang.reflect.Method.invoke(Method.java:483) ~[na:1.8.0_11] at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84) [testng-6.8.8.jar:na] at org.testng.internal.Invoker.invokeMethod(Invoker.java:714) [testng-6.8.8.jar:na] at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901) [testng-6.8.8.jar:na] at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231) [testng-6.8.8.jar:na] at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127) [testng-6.8.8.jar:na] at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111) [testng-6.8.8.jar:na] at org.testng.TestRunner.privateRun(TestRunner.java:767) [testng-6.8.8.jar:na] at org.testng.TestRunner.run(TestRunner.java:617) [testng-6.8.8.jar:na] at org.testng.SuiteRunner.runTest(SuiteRunner.java:348) [testng-6.8.8.jar:na] at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:343) [testng-6.8.8.jar:na] at org.testng.SuiteRunner.privateRun(SuiteRunner.java:305) [testng-6.8.8.jar:na] at org.testng.SuiteRunner.run(SuiteRunner.java:254) [testng-6.8.8.jar:na] at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) [testng-6.8.8.jar:na] at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) [testng-6.8.8.jar:na] at org.testng.TestNG.runSuitesSequentially(TestNG.java:1224) [testng-6.8.8.jar:na] at org.testng.TestNG.runSuitesLocally(TestNG.java:1149) [testng-6.8.8.jar:na] at org.testng.TestNG.run(TestNG.java:1057) [testng-6.8.8.jar:na] at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:115) [surefire-testng-2.17.jar:2.17] at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:204) [surefire-testng-2.17.jar:2.17] at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:107) [surefire-testng-2.17.jar:2.17] at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:112) [surefire-testng-2.17.jar:2.17] at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) [surefire-booter-2.17.jar:2.17] at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) [surefire-booter-2.17.jar:2.17] at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) [surefire-booter-2.17.jar:2.17] Caused by: java.lang.IllegalStateException: Aborting workflow due to failure getting the file 'test-file-1'. Cause: null: null: FAILED: , failure at org.bitrepository.integrityservice.workflow.step.GetFileStep.performStep(GetFileStep.java:74) ~[classes/:na] at org.bitrepository.service.workflow.Workflow.performStep(Workflow.java:63) ~[bitrepository-service-1.6-SNAPSHOT.jar:1.6-SNAPSHOT] ... 32 common frames omitted Test success: testFailedGetFile Test starting: testFailedPutFile Description: Test that the workflow makes calls to the collector for get and put file, even when put file fails. Step: Prepare for calls to mocks Step: Run workflow to repair missing files. 02:20:03.136 ERROR o.b.i.w.RepairMissingFilesWorkflow - Failure in step: 'Performing PutFile for 'test-file-1'.'. java.lang.IllegalStateException: Aborting workflow due to failure putting the file 'test-file-1'. Cause: null: null: FAILED: , failure at org.bitrepository.integrityservice.workflow.step.PutFileStep.performStep(PutFileStep.java:88) ~[classes/:na] at org.bitrepository.service.workflow.Workflow.performStep(Workflow.java:63) ~[bitrepository-service-1.6-SNAPSHOT.jar:1.6-SNAPSHOT] at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflow.putFileStep(RepairMissingFilesWorkflow.java:192) [classes/:na] at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflow.repairMissingFilesForPillar(RepairMissingFilesWorkflow.java:118) [classes/:na] at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflow.start(RepairMissingFilesWorkflow.java:89) [classes/:na] at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflowTest.testFailedPutFile(RepairMissingFilesWorkflowTest.java:242) [test-classes/:na] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_11] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_11] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_11] at java.lang.reflect.Method.invoke(Method.java:483) ~[na:1.8.0_11] at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84) [testng-6.8.8.jar:na] at org.testng.internal.Invoker.invokeMethod(Invoker.java:714) [testng-6.8.8.jar:na] at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901) [testng-6.8.8.jar:na] at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231) [testng-6.8.8.jar:na] at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127) [testng-6.8.8.jar:na] at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111) [testng-6.8.8.jar:na] at org.testng.TestRunner.privateRun(TestRunner.java:767) [testng-6.8.8.jar:na] at org.testng.TestRunner.run(TestRunner.java:617) [testng-6.8.8.jar:na] at org.testng.SuiteRunner.runTest(SuiteRunner.java:348) [testng-6.8.8.jar:na] at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:343) [testng-6.8.8.jar:na] at org.testng.SuiteRunner.privateRun(SuiteRunner.java:305) [testng-6.8.8.jar:na] at org.testng.SuiteRunner.run(SuiteRunner.java:254) [testng-6.8.8.jar:na] at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) [testng-6.8.8.jar:na] at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) [testng-6.8.8.jar:na] at org.testng.TestNG.runSuitesSequentially(TestNG.java:1224) [testng-6.8.8.jar:na] at org.testng.TestNG.runSuitesLocally(TestNG.java:1149) [testng-6.8.8.jar:na] at org.testng.TestNG.run(TestNG.java:1057) [testng-6.8.8.jar:na] at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:115) [surefire-testng-2.17.jar:2.17] at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:204) [surefire-testng-2.17.jar:2.17] at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:107) [surefire-testng-2.17.jar:2.17] at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:112) [surefire-testng-2.17.jar:2.17] at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) [surefire-booter-2.17.jar:2.17] at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) [surefire-booter-2.17.jar:2.17] at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) [surefire-booter-2.17.jar:2.17] 02:20:03.140 WARN o.b.i.w.RepairMissingFilesWorkflow - Error occured during repair of missing file, 'test-file-1'. Tries to continue. java.lang.RuntimeException: Failed to run step Performing PutFile for 'test-file-1'. at org.bitrepository.service.workflow.Workflow.performStep(Workflow.java:69) ~[bitrepository-service-1.6-SNAPSHOT.jar:1.6-SNAPSHOT] at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflow.putFileStep(RepairMissingFilesWorkflow.java:192) [classes/:na] at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflow.repairMissingFilesForPillar(RepairMissingFilesWorkflow.java:118) [classes/:na] at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflow.start(RepairMissingFilesWorkflow.java:89) [classes/:na] at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflowTest.testFailedPutFile(RepairMissingFilesWorkflowTest.java:242) [test-classes/:na] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_11] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_11] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_11] at java.lang.reflect.Method.invoke(Method.java:483) ~[na:1.8.0_11] at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84) [testng-6.8.8.jar:na] at org.testng.internal.Invoker.invokeMethod(Invoker.java:714) [testng-6.8.8.jar:na] at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901) [testng-6.8.8.jar:na] at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231) [testng-6.8.8.jar:na] at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127) [testng-6.8.8.jar:na] at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111) [testng-6.8.8.jar:na] at org.testng.TestRunner.privateRun(TestRunner.java:767) [testng-6.8.8.jar:na] at org.testng.TestRunner.run(TestRunner.java:617) [testng-6.8.8.jar:na] at org.testng.SuiteRunner.runTest(SuiteRunner.java:348) [testng-6.8.8.jar:na] at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:343) [testng-6.8.8.jar:na] at org.testng.SuiteRunner.privateRun(SuiteRunner.java:305) [testng-6.8.8.jar:na] at org.testng.SuiteRunner.run(SuiteRunner.java:254) [testng-6.8.8.jar:na] at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) [testng-6.8.8.jar:na] at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) [testng-6.8.8.jar:na] at org.testng.TestNG.runSuitesSequentially(TestNG.java:1224) [testng-6.8.8.jar:na] at org.testng.TestNG.runSuitesLocally(TestNG.java:1149) [testng-6.8.8.jar:na] at org.testng.TestNG.run(TestNG.java:1057) [testng-6.8.8.jar:na] at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:115) [surefire-testng-2.17.jar:2.17] at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:204) [surefire-testng-2.17.jar:2.17] at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:107) [surefire-testng-2.17.jar:2.17] at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:112) [surefire-testng-2.17.jar:2.17] at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) [surefire-booter-2.17.jar:2.17] at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) [surefire-booter-2.17.jar:2.17] at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) [surefire-booter-2.17.jar:2.17] Caused by: java.lang.IllegalStateException: Aborting workflow due to failure putting the file 'test-file-1'. Cause: null: null: FAILED: , failure at org.bitrepository.integrityservice.workflow.step.PutFileStep.performStep(PutFileStep.java:88) ~[classes/:na] at org.bitrepository.service.workflow.Workflow.performStep(Workflow.java:63) ~[bitrepository-service-1.6-SNAPSHOT.jar:1.6-SNAPSHOT] ... 32 common frames omitted Test success: testFailedPutFile Test starting: testNoMissingFiles Description: Test that the workflow does nothing, when it has no missing files. Step: Prepare for calls to mocks Step: Run workflow for repairing missing files. Test success: testNoMissingFiles Test starting: testSuccesRepair Description: Test that the workflow makes calls to the collector, when a file is missing Step: Prepare for calls to mocks to handle a repair Step: Run workflow for repairing missing files. 02:20:05.362 WARN o.b.i.w.RepairMissingFilesWorkflow - Issue deleting file from FileExchange org.apache.http.conn.HttpHostConnectException: Connect to localhost:80 [localhost/127.0.0.1] failed: Connection refused at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:151) ~[httpclient-4.5.1.jar:4.5.1] at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:353) ~[httpclient-4.5.1.jar:4.5.1] at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:380) ~[httpclient-4.5.1.jar:4.5.1] at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236) ~[httpclient-4.5.1.jar:4.5.1] at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:184) ~[httpclient-4.5.1.jar:4.5.1] at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:88) ~[httpclient-4.5.1.jar:4.5.1] at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110) ~[httpclient-4.5.1.jar:4.5.1] at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184) ~[httpclient-4.5.1.jar:4.5.1] at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82) ~[httpclient-4.5.1.jar:4.5.1] at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:107) ~[httpclient-4.5.1.jar:4.5.1] at org.bitrepository.protocol.http.HttpFileExchange.deleteFile(HttpFileExchange.java:261) ~[bitrepository-core-1.6-SNAPSHOT.jar:1.6-SNAPSHOT] at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflow.deleteUrl(RepairMissingFilesWorkflow.java:207) [classes/:na] at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflow.repairMissingFilesForPillar(RepairMissingFilesWorkflow.java:119) [classes/:na] at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflow.start(RepairMissingFilesWorkflow.java:89) [classes/:na] at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflowTest.testSuccesRepair(RepairMissingFilesWorkflowTest.java:157) [test-classes/:na] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_11] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_11] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_11] at java.lang.reflect.Method.invoke(Method.java:483) ~[na:1.8.0_11] at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84) [testng-6.8.8.jar:na] at org.testng.internal.Invoker.invokeMethod(Invoker.java:714) [testng-6.8.8.jar:na] at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901) [testng-6.8.8.jar:na] at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231) [testng-6.8.8.jar:na] at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127) [testng-6.8.8.jar:na] at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111) [testng-6.8.8.jar:na] at org.testng.TestRunner.privateRun(TestRunner.java:767) [testng-6.8.8.jar:na] at org.testng.TestRunner.run(TestRunner.java:617) [testng-6.8.8.jar:na] at org.testng.SuiteRunner.runTest(SuiteRunner.java:348) [testng-6.8.8.jar:na] at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:343) [testng-6.8.8.jar:na] at org.testng.SuiteRunner.privateRun(SuiteRunner.java:305) [testng-6.8.8.jar:na] at org.testng.SuiteRunner.run(SuiteRunner.java:254) [testng-6.8.8.jar:na] at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) [testng-6.8.8.jar:na] at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) [testng-6.8.8.jar:na] at org.testng.TestNG.runSuitesSequentially(TestNG.java:1224) [testng-6.8.8.jar:na] at org.testng.TestNG.runSuitesLocally(TestNG.java:1149) [testng-6.8.8.jar:na] at org.testng.TestNG.run(TestNG.java:1057) [testng-6.8.8.jar:na] at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:115) [surefire-testng-2.17.jar:2.17] at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:204) [surefire-testng-2.17.jar:2.17] at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:107) [surefire-testng-2.17.jar:2.17] at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:112) [surefire-testng-2.17.jar:2.17] at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) [surefire-booter-2.17.jar:2.17] at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) [surefire-booter-2.17.jar:2.17] at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) [surefire-booter-2.17.jar:2.17] Caused by: java.net.ConnectException: Connection refused at java.net.PlainSocketImpl.socketConnect(Native Method) ~[na:1.8.0_11] at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:345) ~[na:1.8.0_11] at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) ~[na:1.8.0_11] at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) ~[na:1.8.0_11] at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) ~[na:1.8.0_11] at java.net.Socket.connect(Socket.java:589) ~[na:1.8.0_11] at org.apache.http.conn.socket.PlainConnectionSocketFactory.connectSocket(PlainConnectionSocketFactory.java:74) ~[httpclient-4.5.1.jar:4.5.1] at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:134) ~[httpclient-4.5.1.jar:4.5.1] ... 42 common frames omitted Test success: testSuccesRepair Starting testcase HandleChecksumValidationStepTest Test starting: testAuditTrailsForChecksumErrors Description: Test audit trails for checksum errors. Verify that a pillar with a single checksum will be pointed out as the possible cause. 02:20:16.225 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate. 02:20:16.227 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6 Step: Test step on data without checksum error Step: Test step on data where only two pillars have the file and they disagree about the checksum. number of files in the collection2 number of fileinfos: 3 Step: remove the last auditinfo Step: Test step on data where two pillars have one checksum and the last pillar has a different one Test success: testAuditTrailsForChecksumErrors Test starting: testChecksumMajority Description: Test the checksum integrity validator when two pillars have one checksum and the last pillar has another checksum. 02:20:21.351 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate. 02:20:21.356 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6 Step: Add data to the cache Step: Perform the checksum validation step Step: Validate the file ids Test success: testChecksumMajority Test starting: testMissingAtOnePillar Description: Test the checksum integrity validator when one pillar is missing the data. 02:20:24.361 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate. 02:20:24.364 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6 Step: Update the cache with identitical data for both pillars. Step: Perform the step Step: Validate the file ids Test success: testMissingAtOnePillar Test starting: testNoData Description: Test the checksum integrity validator without any data in the cache. 02:20:26.958 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate. 02:20:26.963 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6 Step: Validate the file ids Test success: testNoData Test starting: testSimilarData Description: Test the checksum integrity validator when all pillars have similar data. 02:20:28.841 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate. 02:20:28.843 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6 Step: Add data to the cache Step: Perform the step Step: Validate the file ids Test success: testSimilarData Test starting: testThreeDisagreeingChecksums Description: Test the checksum integrity validator when all pillars have different checksums. 02:20:31.407 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate. 02:20:31.410 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6 Step: Add data to the cache Step: Perform the step Step: Validate the file ids Test success: testThreeDisagreeingChecksums Test starting: testTwoDisagreeingChecksums Description: Test the checksum integrity validator when only two pillar has data, but it it different. 02:20:32.937 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate. 02:20:32.958 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6 Step: Add data to the cache Step: Perform the step Step: Validate the file ids Test success: testTwoDisagreeingChecksums Starting testcase IntegrityAlerterTest Test starting: testIntegrityFailed Description: Test the IntegrityFailed method for the IntegrityAlerter Step: Call the function for integrity failure. 02:20:33.528 WARN o.b.i.a.IntegrityAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@1d6f77d7[origDateTime=2015-12-04T02:20:33.528+01:00, alarmCode=INTEGRITY_ISSUE, alarmRaiser=IntegrityAlerterTest, alarmText=Testaintegrity alarm, fileID=, collectionID=TwoPillarCollection] Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@17c53dfb[correlationID=7ffed827-c6ba-4e4a-b9af-7f9274f2450e, collectionID=TwoPillarCollection, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-IntegrityAlerterTest-cibuild01-contributor, from=IntegrityAlerterTest, to=, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@1d6f77d7[origDateTime=2015-12-04T02:20:33.528+01:00, alarmCode=INTEGRITY_ISSUE, alarmRaiser=IntegrityAlerterTest, alarmText=Testaintegrity alarm, fileID=, collectionID=TwoPillarCollection]] Test success: testIntegrityFailed Test starting: testOperationFailed Description: Test the OperationFailed method for the IntegrityAlerter Step: Call the function for integrity failure. 02:20:35.263 WARN o.b.i.a.IntegrityAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@2c815fdc[origDateTime=2015-12-04T02:20:35.263+01:00, alarmCode=FAILED_OPERATION, alarmRaiser=IntegrityAlerterTest, alarmText=Testing the ability to fail., fileID=, collectionID=TwoPillarCollection] Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@769b0752[correlationID=cd32dde4-7f78-4d4d-849c-c550ff636b5f, collectionID=TwoPillarCollection, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-IntegrityAlerterTest-cibuild01-contributor, from=IntegrityAlerterTest, to=, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@2c815fdc[origDateTime=2015-12-04T02:20:35.263+01:00, alarmCode=FAILED_OPERATION, alarmRaiser=IntegrityAlerterTest, alarmText=Testing the ability to fail., fileID=, collectionID=TwoPillarCollection]] Test success: testOperationFailed Starting testcase IntegrityInformationCollectorTest Test starting: testCollectorGetChecksums Description: Tests that the collector calls the GetChecksumsClient Step: Define variables Step: Setup a GetChecksumsClient for test purpose. Step: Call the getChecksumsClient on the collector. Step: Call the getChecksumsClient on the collector four times more. Test success: testCollectorGetChecksums Test starting: testCollectorGetFile Description: Tests that the collector calls the GetFileClient Step: Define variables Step: Setup a GetFileClient for test purpose. Step: Call the GetFileClient on the collector. Step: Call the GetFileClient on the collector four times more. Test success: testCollectorGetFile Test starting: testCollectorGetFileIDs Description: Tests that the collector calls the GetFileClient Step: Define variables Step: Setup a GetFileIDsClient for test purpose. Step: Call the getFileIDs on the collector. Step: Call the getFileIDs on the collector four times more. Test success: testCollectorGetFileIDs Test starting: testCollectorHandleChecksumClientFailures Description: Test that the IntegrityInformationCollector works as a fault-barrier. Step: Setup variables for the test Step: Setup a failing GetChecksumClient for test purpose. Step: Verify that the collector does not fail, just because the GetChecksumClient does so 02:20:35.343 ERROR o.b.i.c.DelegatingIntegrityInformationCollector - Unexpected failure! java.lang.RuntimeException: null at org.bitrepository.integrityservice.collector.DelegatingIntegrityInformationCollector.getChecksums(DelegatingIntegrityInformationCollector.java:89) ~[classes/:na] at org.bitrepository.integrityservice.collector.IntegrityInformationCollectorTest.testCollectorHandleChecksumClientFailures(IntegrityInformationCollectorTest.java:200) [test-classes/:na] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_11] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_11] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_11] at java.lang.reflect.Method.invoke(Method.java:483) ~[na:1.8.0_11] at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84) [testng-6.8.8.jar:na] at org.testng.internal.Invoker.invokeMethod(Invoker.java:714) [testng-6.8.8.jar:na] at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901) [testng-6.8.8.jar:na] at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231) [testng-6.8.8.jar:na] at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127) [testng-6.8.8.jar:na] at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111) [testng-6.8.8.jar:na] at org.testng.TestRunner.privateRun(TestRunner.java:767) [testng-6.8.8.jar:na] at org.testng.TestRunner.run(TestRunner.java:617) [testng-6.8.8.jar:na] at org.testng.SuiteRunner.runTest(SuiteRunner.java:348) [testng-6.8.8.jar:na] at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:343) [testng-6.8.8.jar:na] at org.testng.SuiteRunner.privateRun(SuiteRunner.java:305) [testng-6.8.8.jar:na] at org.testng.SuiteRunner.run(SuiteRunner.java:254) [testng-6.8.8.jar:na] at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) [testng-6.8.8.jar:na] at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) [testng-6.8.8.jar:na] at org.testng.TestNG.runSuitesSequentially(TestNG.java:1224) [testng-6.8.8.jar:na] at org.testng.TestNG.runSuitesLocally(TestNG.java:1149) [testng-6.8.8.jar:na] at org.testng.TestNG.run(TestNG.java:1057) [testng-6.8.8.jar:na] at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:115) [surefire-testng-2.17.jar:2.17] at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:204) [surefire-testng-2.17.jar:2.17] at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:107) [surefire-testng-2.17.jar:2.17] at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:112) [surefire-testng-2.17.jar:2.17] at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) [surefire-booter-2.17.jar:2.17] at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) [surefire-booter-2.17.jar:2.17] at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) [surefire-booter-2.17.jar:2.17] Test success: testCollectorHandleChecksumClientFailures Test starting: testCollectorHandleGetFileClientFailures Description: Test that the IntegrityInformationCollector works as a fault-barrier. Step: Define variables Step: Setup a GetFileClient for test purpose, and ensure that it throws an error when called. Step: Verify that the collector does not fail, just because the GetFileClient does so 02:20:35.348 ERROR o.b.i.c.DelegatingIntegrityInformationCollector - Unexpected failure! java.lang.RuntimeException: null at org.bitrepository.integrityservice.collector.DelegatingIntegrityInformationCollector.getFile(DelegatingIntegrityInformationCollector.java:100) ~[classes/:na] at org.bitrepository.integrityservice.collector.IntegrityInformationCollectorTest.testCollectorHandleGetFileClientFailures(IntegrityInformationCollectorTest.java:239) [test-classes/:na] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_11] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_11] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_11] at java.lang.reflect.Method.invoke(Method.java:483) ~[na:1.8.0_11] at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84) [testng-6.8.8.jar:na] at org.testng.internal.Invoker.invokeMethod(Invoker.java:714) [testng-6.8.8.jar:na] at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901) [testng-6.8.8.jar:na] at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231) [testng-6.8.8.jar:na] at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127) [testng-6.8.8.jar:na] at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111) [testng-6.8.8.jar:na] at org.testng.TestRunner.privateRun(TestRunner.java:767) [testng-6.8.8.jar:na] at org.testng.TestRunner.run(TestRunner.java:617) [testng-6.8.8.jar:na] at org.testng.SuiteRunner.runTest(SuiteRunner.java:348) [testng-6.8.8.jar:na] at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:343) [testng-6.8.8.jar:na] at org.testng.SuiteRunner.privateRun(SuiteRunner.java:305) [testng-6.8.8.jar:na] at org.testng.SuiteRunner.run(SuiteRunner.java:254) [testng-6.8.8.jar:na] at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) [testng-6.8.8.jar:na] at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) [testng-6.8.8.jar:na] at org.testng.TestNG.runSuitesSequentially(TestNG.java:1224) [testng-6.8.8.jar:na] at org.testng.TestNG.runSuitesLocally(TestNG.java:1149) [testng-6.8.8.jar:na] at org.testng.TestNG.run(TestNG.java:1057) [testng-6.8.8.jar:na] at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:115) [surefire-testng-2.17.jar:2.17] at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:204) [surefire-testng-2.17.jar:2.17] at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:107) [surefire-testng-2.17.jar:2.17] at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:112) [surefire-testng-2.17.jar:2.17] at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) [surefire-booter-2.17.jar:2.17] at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) [surefire-booter-2.17.jar:2.17] at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) [surefire-booter-2.17.jar:2.17] Test success: testCollectorHandleGetFileClientFailures Test starting: testCollectorHandleGetFileIDsClientFailures Description: Test that the IntegrityInformationCollector works as a fault-barrier. Step: Setup variables for the test Step: Setup a DyingGetFileIDsClient for test purpose. Step: Verify that the collector does not fail, just because the GetChecksumClient does so 02:20:35.351 ERROR o.b.i.c.DelegatingIntegrityInformationCollector - Unexpected failure! java.lang.RuntimeException: null at org.bitrepository.integrityservice.collector.DelegatingIntegrityInformationCollector.getFileIDs(DelegatingIntegrityInformationCollector.java:78) ~[classes/:na] at org.bitrepository.integrityservice.collector.IntegrityInformationCollectorTest.testCollectorHandleGetFileIDsClientFailures(IntegrityInformationCollectorTest.java:219) [test-classes/:na] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_11] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_11] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_11] at java.lang.reflect.Method.invoke(Method.java:483) ~[na:1.8.0_11] at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84) [testng-6.8.8.jar:na] at org.testng.internal.Invoker.invokeMethod(Invoker.java:714) [testng-6.8.8.jar:na] at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901) [testng-6.8.8.jar:na] at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231) [testng-6.8.8.jar:na] at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127) [testng-6.8.8.jar:na] at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111) [testng-6.8.8.jar:na] at org.testng.TestRunner.privateRun(TestRunner.java:767) [testng-6.8.8.jar:na] at org.testng.TestRunner.run(TestRunner.java:617) [testng-6.8.8.jar:na] at org.testng.SuiteRunner.runTest(SuiteRunner.java:348) [testng-6.8.8.jar:na] at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:343) [testng-6.8.8.jar:na] at org.testng.SuiteRunner.privateRun(SuiteRunner.java:305) [testng-6.8.8.jar:na] at org.testng.SuiteRunner.run(SuiteRunner.java:254) [testng-6.8.8.jar:na] at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) [testng-6.8.8.jar:na] at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) [testng-6.8.8.jar:na] at org.testng.TestNG.runSuitesSequentially(TestNG.java:1224) [testng-6.8.8.jar:na] at org.testng.TestNG.runSuitesLocally(TestNG.java:1149) [testng-6.8.8.jar:na] at org.testng.TestNG.run(TestNG.java:1057) [testng-6.8.8.jar:na] at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:115) [surefire-testng-2.17.jar:2.17] at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:204) [surefire-testng-2.17.jar:2.17] at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:107) [surefire-testng-2.17.jar:2.17] at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:112) [surefire-testng-2.17.jar:2.17] at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) [surefire-booter-2.17.jar:2.17] at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) [surefire-booter-2.17.jar:2.17] at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) [surefire-booter-2.17.jar:2.17] Test success: testCollectorHandleGetFileIDsClientFailures Test starting: testCollectorHandlePutFileClientFailures Description: Test that the IntegrityInformationCollector works as a fault-barrier. Step: Define variables Step: Setup a PutFileClient for test purpose, and ensure that it throws an error when called. Step: Verify that the collector does not fail, just because the PutFileClient does so 02:20:35.361 ERROR o.b.i.c.DelegatingIntegrityInformationCollector - Unexpected failure! java.lang.RuntimeException: null at org.bitrepository.integrityservice.collector.DelegatingIntegrityInformationCollector.putFile(DelegatingIntegrityInformationCollector.java:111) ~[classes/:na] at org.bitrepository.integrityservice.collector.IntegrityInformationCollectorTest.testCollectorHandlePutFileClientFailures(IntegrityInformationCollectorTest.java:260) [test-classes/:na] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_11] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_11] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_11] at java.lang.reflect.Method.invoke(Method.java:483) ~[na:1.8.0_11] at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84) [testng-6.8.8.jar:na] at org.testng.internal.Invoker.invokeMethod(Invoker.java:714) [testng-6.8.8.jar:na] at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901) [testng-6.8.8.jar:na] at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231) [testng-6.8.8.jar:na] at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127) [testng-6.8.8.jar:na] at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111) [testng-6.8.8.jar:na] at org.testng.TestRunner.privateRun(TestRunner.java:767) [testng-6.8.8.jar:na] at org.testng.TestRunner.run(TestRunner.java:617) [testng-6.8.8.jar:na] at org.testng.SuiteRunner.runTest(SuiteRunner.java:348) [testng-6.8.8.jar:na] at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:343) [testng-6.8.8.jar:na] at org.testng.SuiteRunner.privateRun(SuiteRunner.java:305) [testng-6.8.8.jar:na] at org.testng.SuiteRunner.run(SuiteRunner.java:254) [testng-6.8.8.jar:na] at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) [testng-6.8.8.jar:na] at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) [testng-6.8.8.jar:na] at org.testng.TestNG.runSuitesSequentially(TestNG.java:1224) [testng-6.8.8.jar:na] at org.testng.TestNG.runSuitesLocally(TestNG.java:1149) [testng-6.8.8.jar:na] at org.testng.TestNG.run(TestNG.java:1057) [testng-6.8.8.jar:na] at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:115) [surefire-testng-2.17.jar:2.17] at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:204) [surefire-testng-2.17.jar:2.17] at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:107) [surefire-testng-2.17.jar:2.17] at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:112) [surefire-testng-2.17.jar:2.17] at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) [surefire-booter-2.17.jar:2.17] at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) [surefire-booter-2.17.jar:2.17] at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) [surefire-booter-2.17.jar:2.17] Test success: testCollectorHandlePutFileClientFailures Test starting: testCollectorPutFile Description: Tests that the collector calls the PutFileClient Step: Define variables Step: Setup a PutFileClient for test purpose. Step: Call the PutFileClient on the collector. Step: Call the PutFileClient on the collector four times more. Test success: testCollectorPutFile Starting testcase IntegrityWorkflowManagerTest Test starting: collectionSpecificWorkflows Description: Verifies that the IntegrityWorkflowManager loads correctly for workflows configured for specific collection. Step: Create a IntegrityWorkflowManager based on a workflow with different schedules for collection 1 and 2 (daily and hourly) Test success: collectionSpecificWorkflows Test starting: noWorkflowPackage Description: Verifies that the IntegrityWorkflowManager loads correctly for at workflow configuration with a workflow class name without a package scope (located in the deafult workflow package). Step: Create a IntegrityWorkflowManager based on a single Testworkflow with a daily schedule in a to collection system, where the className is just the simplename Test success: noWorkflowPackage Test starting: noWorkflowSettings Description: Verifies that the IntegrityWorkflowManager loads correctly for missing reference settings a workflow settings element. Step: Create a IntegrityWorkflowManager based on a workflowsettingsless configuration Test success: noWorkflowSettings Test starting: normalWorkflowSettings Description: Verifies that the IntegrityWorkflowManager loads correctly for at normally defined workflow. Step: Create a IntegrityWorkflowManager based on a single Testworkflow with a daily schedule in a to collection system Test success: normalWorkflowSettings Test starting: startWorkflow Description: Verifies that the that it is possible to manually start a workflow. Step: Call the startWorkflow with a workflow defined in the configuration Test success: startWorkflow Test starting: unscheduledWorkflow Description: Verifies that the IntegrityWorkflowManager loads workflow correctly for workflows without a defined schedule meaning they are never run automatically. Step: Create a IntegrityWorkflowManager based on a single Testworkflow without a schedule Test success: unscheduledWorkflow Starting testcase IntegrityDBToolsTest Test starting: testAddCollectionSuccess Description: Tests that a new collection can be added to the integrity database 02:20:37.632 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate. 02:20:37.636 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6 Step: Extract initial list of collections Step: Add the new collection Test success: testAddCollectionSuccess Test starting: testAddExistingCollection Description: Tests that an existing collectionID cannot be added to the integrity database. 02:20:39.639 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate. 02:20:39.640 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6 Step: Extract initial list of collections. Step: Attempt to add the new collection. Test success: testAddExistingCollection Test starting: testRemoveNonExistingCollection Description: Tests that a non existing collection can't be removed from the integrity database. 02:20:41.353 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate. 02:20:41.355 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6 Step: Extract initial list of collections. Step: Attempt to remove the non-existing collection. Test success: testRemoveNonExistingCollection Starting testcase IntegrityDatabaseTest Test starting: initialStateExtractionTest Description: Tests the initial state of the IntegrityModel. Should not contain any data. 02:20:42.488 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate. 02:20:42.490 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6 Step: Test the 'findChecksumsOlderThan' Step: Test the 'findMissingChecksums' Step: Test the 'findMissingFiles' Step: Test the 'getAllFileIDs' Step: Test the 'getFileInfos' Step: Test the 'getNumberOfFiles' Test success: initialStateExtractionTest Test starting: instantiationTest Description: Tests that the connection can be instantaited. 02:20:43.912 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate. 02:20:43.914 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6 Test success: instantiationTest Test starting: testDeletingEntry Description: Tests the deletion of an FileID entry. 02:20:45.213 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate. 02:20:45.220 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6 Step: Create data Step: Delete the entry Test success: testDeletingEntry Test starting: testIngestOfChecksumsData Description: Tests the ingesting of checksums data 02:20:46.996 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate. 02:20:46.999 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6 Step: Create data Step: Extract the data Test success: testIngestOfChecksumsData Test starting: testIngestOfFileIDsData Description: Tests the ingesting of file ids data 02:20:48.380 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate. 02:20:48.381 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6 Step: Create data Step: Extract the data Test success: testIngestOfFileIDsData Starting testcase UpdateFileIDsStepTest Test starting: testAbortWorkflowWhenNegativeReply Description: Test the step for updating the file ids will throw an WorkflowAbortedExceptionwhen AbortOnFailedContributor is set to true and a FAILED event is received. 02:20:48.628 WARN o.b.i.c.IntegrityCollectorEventHandler - Component failure for 'test-pillar-1'. 02:20:48.629 WARN o.b.i.c.IntegrityCollectorEventHandler - Failure: null: null: FAILED: , Operation failed Test success: testAbortWorkflowWhenNegativeReply Test starting: testContinueWorkflowWhenNegativeReply Description: Test the step for updating the file ids will continue when getting an FAILED operation event when AbortOnFailedContributor is set to false 02:20:48.684 WARN o.b.i.c.IntegrityCollectorEventHandler - Component failure for 'test-pillar-1'. 02:20:48.684 WARN o.b.i.c.IntegrityCollectorEventHandler - Failure: null: null: FAILED: , Operation failed Test success: testContinueWorkflowWhenNegativeReply Test starting: testIngestOfResults Description: Test the step for updating the file ids can ingest the data correctly into the store. Test success: testIngestOfResults Test starting: testPartialResults Description: Test that the number of partial is used for generating more than one request. Step: Setup the collector mock to generate a isPartialResult=true event the first time and a isPartialResult=false the second time Test success: testPartialResults Test starting: testPositiveReply Description: Test the step for updating the file ids can handle COMPLETE operation event. Test success: testPositiveReply Test starting: testRetryCollectionWhenNegativeReply Description: Test the step for updating the file ids will retry on a FAILED event 02:20:50.476 WARN o.b.i.c.IntegrityCollectorEventHandler - Component failure for 'test-pillar-1'. 02:20:50.480 WARN o.b.i.c.IntegrityCollectorEventHandler - Failure: null: null: FAILED: , Operation failed Test success: testRetryCollectionWhenNegativeReply Starting testcase BasicIntegrityReporterTest Test starting: checksumIssuesTest Description: Verifies that missing files are reported correctly Step: Report a checksum issue Step: Report another checksum issue on the same pillar Step: Report a checksum issue on another pillar Test success: checksumIssuesTest Test starting: deletedFilesTest Description: Verifies that the hasIntegrityIssues() reports deleted files correctly Step: Report a delete file for a new Reporter Test success: deletedFilesTest Test starting: missingChecksumTest Description: Verifies that missing checksums are reported correctly Step: Report a missing checksum Step: Report another missing checksum on the same pillar Step: Report a missing checksum on another pillar Test success: missingChecksumTest Test starting: missingFilesTest Description: Verifies that missing files are reported correctly Step: Report a missing file Step: Report another missing file on the same pillar Step: Report a missing file on another pillar Test success: missingFilesTest Test starting: noIntegrityIssuesTest Description: Verifies that missing files are reported correctly Step: Create a clean reporter Test success: noIntegrityIssuesTest Test starting: obsoleteChecksumTest Description: Verifies that obsolete checksums are reported correctly Step: Report a obsolete checksum Step: Report another obsolete checksum on the same pillar Step: Report a obsolete checksum on another pillar Test success: obsoleteChecksumTest Starting testcase FileInfoTest Test starting: testFileInfo Description: Tests the FileInfo element. Adds all data and extracts it again. Step: Setup the file info. Step: Change the checksum Step: Change the date for last file id check Step: Change the date for last checksum check Test success: testFileInfo Starting testcase IntegrityDAOTest Test starting: initialStateExtractionTest Description: Tests the initial state of the IntegrityModel. Should not contain any data. 02:20:51.496 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate. 02:20:51.499 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6 Test success: initialStateExtractionTest Test starting: instantiationTest Description: Testing the connection to the integrity database. 02:20:52.960 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate. 02:20:52.963 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6 Test success: instantiationTest Test starting: reinitialiseDatabaseTest Description: Testing the connection to the integrity database. Step: Setup manually. 02:20:54.225 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate. 02:20:54.226 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6 Step: Close the connection and create another one. Test success: reinitialiseDatabaseTest Test starting: testDeletingEntry Description: Tests the deletion of an FileID entry from a collection. Checks that it does not effect another collection with a fileID equal to the deleted 02:20:57.006 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate. 02:20:57.008 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6 Step: Create data Step: Ensure that the data is present Step: Delete the entry for the first pillar Step: Delete the entry for the second pillar Step: Check that the data in the extra collection is still present Test success: testDeletingEntry Test starting: testDeletingNonExistingEntry Description: Tests the deletion of an nonexisting FileID entry. 02:20:58.227 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate. 02:20:58.229 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6 Step: Create data Step: Delete a nonexisting entry Test success: testDeletingNonExistingEntry Test starting: testExtractCollectionFileSize Description: Tests that the accumulated size of the collection can be extracted 02:20:59.585 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate. 02:20:59.586 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6 Step: Insert test data into database Step: Check the reported size of the first pillar in the collection Step: Check the reported size of the second pillar in the collection Step: Check the reported size of the whole collection Test success: testExtractCollectionFileSize Test starting: testExtractingAllKnownFilesForPillars Description: Tests that known files can be extracted for specific pillars. 02:21:01.124 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate. 02:21:01.124 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6 Step: Insert two files into database for a pillar Step: Insert a file to the extra collection for the common pillar Step: Extract all the existing file ids for the pillar for collection 'TwoPillarCollection' Step: Extract the single fileID for the extra collection Step: Extract all the existing file ids for another pillar Test success: testExtractingAllKnownFilesForPillars Test starting: testExtractingAllKnownFilesForPillarsLimits Description: Tests the limits for extracting files for specific pillars. 02:21:02.422 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate. 02:21:02.422 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6 Step: Insert two files into database for a pillar Step: Extract with a maximum of 1 Step: Extract with a minimum of 1 and maximum of infinite Test success: testExtractingAllKnownFilesForPillarsLimits Test starting: testExtractingAllMissingFilesForPillars Description: Tests that missing files can be extracted for specific pillars. 02:21:03.924 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate. 02:21:03.925 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6 Step: Insert two files into database for a pillar and mark them as missing Step: Check the number of files in collection and on pillars Step: Extract missing files from the first pillar Step: Extract missing files from the second pillar Test success: testExtractingAllMissingFilesForPillars Test starting: testExtractingAllMissingFilesForPillarsLimits Description: Tests the limits for extracting missing files for specific pillars. 02:21:05.241 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate. 02:21:05.241 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6 Step: Insert two files into database for a pillar and set them to missing Step: Extract with a maximum of 1 Step: Extract with a minimum of 1 and maximum of infinite Test success: testExtractingAllMissingFilesForPillarsLimits Test starting: testFindInconsistentChecksum Description: Testing the localization of inconsistent checksums 02:21:06.394 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate. 02:21:06.395 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6 Step: Update the database with 2 inconsistent files and one consistent file. Step: Find the files with inconsistent checksums Test success: testFindInconsistentChecksum Test starting: testFindOrphanFiles Description: Tests the ability to find orphan files. 02:21:07.707 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate. 02:21:07.708 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6 Step: Create data Test success: testFindOrphanFiles Test starting: testGetLatestChecksumDateEntryForCollection Description: Tests that checksum date entries can be retrieved and manipulated. 02:21:09.363 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate. 02:21:09.365 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6 Step: Create data Test success: testGetLatestChecksumDateEntryForCollection Test starting: testGetLatestFileDateEntryForCollection Description: Tests that checksum date entries can be retrieved and manipulated. 02:21:10.574 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate. 02:21:10.575 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6 Step: Create data Test success: testGetLatestFileDateEntryForCollection Test starting: testIngestOfChecksumsData Description: Tests the ingesting of checksums data 02:21:11.470 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate. 02:21:11.472 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6 Step: Create data Step: Extract the data Step: Check that the extra collection is untouched by the ingest Test success: testIngestOfChecksumsData Test starting: testIngestOfFileIDsData Description: Tests the ingesting of file ids data 02:21:12.543 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate. 02:21:12.546 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6 Step: Create data Step: Extract the data Step: Check that the extra collection is untouched by the ingest Test success: testIngestOfFileIDsData Test starting: testMissingChecksums Description: Testing the checksum validation, when only one pillar has a checksum for a file. 02:21:13.720 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate. 02:21:13.721 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6 Step: Update the database with 1 file, missing its checksum on one pillar. Step: Finding the files with inconsistent checksums Test success: testMissingChecksums Test starting: testMissingChecksumsChecksumNotUpdated Description: Testing the checksum validation, when only one pillar has a checksum for a file. 02:21:16.279 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate. 02:21:16.280 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6 Step: Update the database with 1 file, no missing checksums. Step: Finding the files with inconsistent checksums Step: Updating the checksum for one pillar, and checking that the other pillars checksum is now missing Step: Finding the files with inconsistent checksums Test success: testMissingChecksumsChecksumNotUpdated Test starting: testNoChecksums Description: Testing the checksum validation, when no checksums exists. 02:21:18.378 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate. 02:21:18.380 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6 Step: Update the database with 2 inconsistent files and one consistent file. Step: Finding the files with inconsistent checksums Test success: testNoChecksums Test starting: testOutdatedChecksums Description: Testing the checksum validation, when only one pillar has a checksum for a file. 02:21:19.445 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate. 02:21:19.447 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6 Step: Update the database with one file, one pillar having an outdated checksum. Step: Finding the files with inconsistent checksums Test success: testOutdatedChecksums Starting testcase UpdateChecksumsStepTest Test starting: testAbortWorkflowWhenNegativeReply Description: Test the step for updating the checksums will abort the workflow in case of FAILURE operation event and AbortOnFailedContributor = true . 02:21:19.792 WARN o.b.i.c.IntegrityCollectorEventHandler - Component failure for 'test-pillar-1'. 02:21:19.792 WARN o.b.i.c.IntegrityCollectorEventHandler - Failure: null: null: FAILED: , Problem encountered Test success: testAbortWorkflowWhenNegativeReply Test starting: testCallForChangingChecksumStates Description: Test the step for updating the checksums delivers the results to the integrity model. Test success: testCallForChangingChecksumStates Test starting: testContinueWorkflowNegativeReply Description: Test the step for updating the checksums will continue the workflow in case of FAILURE operation event and AbortOnFailedContributor = false . 02:21:19.941 WARN o.b.i.c.IntegrityCollectorEventHandler - Component failure for 'test-pillar-1'. 02:21:19.941 WARN o.b.i.c.IntegrityCollectorEventHandler - Failure: null: null: FAILED: , Problem encountered Test success: testContinueWorkflowNegativeReply Test starting: testFullChecksumCollection Description: Test that the full list of checksums is requested. Test success: testFullChecksumCollection Test starting: testIncrementalChecksumCollection Description: Test that only the list of new checksums is requested. Test success: testIncrementalChecksumCollection Test starting: testIngestOfResults Description: Test the step for updating the checksums delivers the results to the integrity model. Test success: testIngestOfResults Test starting: testPartialResults Description: Test that the number of partial is used for generating more than one request. Step: Setup the collector mock to generate a isPartialResult=true event the first time and a isPartialResult=false the second time Test success: testPartialResults Test starting: testPositiveReply Description: Test the step for updating the checksums can handle COMPLETE operation event. Test success: testPositiveReply Test starting: testRetryCollectionWhenNegativeReply Description: Test the step for updating the file ids will retry on a FAILED event 02:21:20.381 WARN o.b.i.c.IntegrityCollectorEventHandler - Component failure for 'test-pillar-1'. 02:21:20.381 WARN o.b.i.c.IntegrityCollectorEventHandler - Failure: null: null: FAILED: , Problem encountered Test success: testRetryCollectionWhenNegativeReply Starting testcase GetFileStepTest Test starting: testNegativeReply Description: Test the step for getting the file can handle FAILURE operation event. Test success: testNegativeReply Test starting: testPositiveReply Description: Test the step for getting the file can handle COMPLETE operation event. Test success: testPositiveReply Finished testcase Finished suite Finished project Tests run: 90, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 84.42 sec - in TestSuite Results : Tests run: 90, Failures: 0, Errors: 0, Skipped: 0 [JENKINS] Recording test results [INFO] [INFO] --- maven-war-plugin:2.4:war (default-war) @ bitrepository-integrity-service --- [INFO] Packaging webapp [INFO] Assembling webapp [bitrepository-integrity-service] in [/home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integrity-service/target/bitrepository-integrity-service-1.6-SNAPSHOT] [INFO] Processing war project [INFO] Copying webapp resources [/home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integrity-service/src/main/webapp] [INFO] Webapp assembled in [404 msecs] [INFO] Building war: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integrity-service/target/bitrepository-integrity-service-1.6-SNAPSHOT.war [INFO] [INFO] --- maven-jar-plugin:2.4:test-jar (default) @ bitrepository-integrity-service --- [INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integrity-service/target/bitrepository-integrity-service-1.6-SNAPSHOT-tests.jar [INFO] [INFO] --- maven-source-plugin:2.2.1:jar-no-fork (attach-sources-no-fork) @ bitrepository-integrity-service --- [INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integrity-service/target/bitrepository-integrity-service-1.6-SNAPSHOT-sources.jar [INFO] [INFO] --- maven-assembly-plugin:2.4:single (distribution) @ bitrepository-integrity-service --- [INFO] Reading assembly descriptor: src/main/assembly/assembly.xml [INFO] Building tar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integrity-service/target/bitrepository-integrity-service-1.6-SNAPSHOT-distribution.tar.gz [INFO] [INFO] --- maven-install-plugin:2.5.1:install (default-install) @ bitrepository-integrity-service --- [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integrity-service/target/bitrepository-integrity-service-1.6-SNAPSHOT.war to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integrity-service/1.6-SNAPSHOT/bitrepository-integrity-service-1.6-SNAPSHOT.war [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integrity-service/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integrity-service/1.6-SNAPSHOT/bitrepository-integrity-service-1.6-SNAPSHOT.pom [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integrity-service/target/bitrepository-integrity-service-1.6-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integrity-service/1.6-SNAPSHOT/bitrepository-integrity-service-1.6-SNAPSHOT-tests.jar [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integrity-service/target/bitrepository-integrity-service-1.6-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integrity-service/1.6-SNAPSHOT/bitrepository-integrity-service-1.6-SNAPSHOT-sources.jar [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integrity-service/target/bitrepository-integrity-service-1.6-SNAPSHOT-distribution.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integrity-service/1.6-SNAPSHOT/bitrepository-integrity-service-1.6-SNAPSHOT-distribution.tar.gz [JENKINS] Archiving disabled [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building Bitrepository Alarm Service 1.6-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-alarm-service --- [INFO] Deleting /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-alarm-service/target [INFO] [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ bitrepository-alarm-service --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 5 resources [INFO] [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ bitrepository-alarm-service --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 26 source files to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-alarm-service/target/classes [INFO] [INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ bitrepository-alarm-service --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 2 resources [INFO] [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ bitrepository-alarm-service --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 6 source files to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-alarm-service/target/test-classes [INFO] [INFO] --- maven-surefire-plugin:2.17:test (default-test) @ bitrepository-alarm-service --- [INFO] Surefire report directory: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-alarm-service/target/surefire-reports ------------------------------------------------------- T E S T S ------------------------------------------------------- Running TestSuite Configuring TestNG with: TestNG652Configurator Starting test project Alarm Service Test Suite: Surefire suite Starting testcase AlarmDatabaseTest Test starting: AlarmDatabaseExtractionTest Description: Testing the connection to the alarm service database especially with regards to extracting the data from it. Step: Setup the variables and constants. Step: Adds the variables to the settings and instantaites the database cache Step: Populate the database with two alarms. Step: Try to extract all the data from the database. Step: Try to extract the alarms for component 1. Step: Try to extract the alarms for component 2. Step: Try to extract the alarms for the alarm code 'COMPONENT_FAILURE'. Step: Try to extract the alarms for the alarm code 'CHECKSUM_ALARM'. Step: Try to extract the new alarm. Step: Try to extract the old alarm. Step: Try to extract the alarms for the file id. Step: Try to extract the alarms for the collection id. Step: Try to extract the oldest alarm from the database. Step: Try to extract the newest alarm from the database. Test success: AlarmDatabaseExtractionTest Test starting: AlarmDatabaseLargeIngestionTest Description: Testing the ingestion of a large texts into the database Step: Setup and create alarm Step: Insert the data into the database Test success: AlarmDatabaseLargeIngestionTest Step: Cleanup after test. Starting testcase AlarmHandlerTest Test starting: alarmMediatorTest Description: Test the mediator handling of alarm messages. Step: Setup mediator and create alarm handler. Step: Try giving it a non-alarm message 02:21:36.603 WARN o.b.alarm.handling.AlarmMediator - Recieved unexpected message: 'org.bitrepository.bitrepositorymessages.Message@78d50a3c[correlationID=, collectionID=, destination=, replyTo=, from=, to=, version=, minVersion=]' Step: Giv the mediator an AlarmMessage Step: Close the mediator. Test success: alarmMediatorTest Starting testcase AlarmDatabaseExtractionModelTest Test starting: alarmExceptionTest Description: Test the AlarmDatabaseExtractionModel class Step: Define constants etc. Step: Create an empty model Step: Test the AlarmCode Step: Test the ascending Step: Test the ComponentID Step: Test the EndDate Step: Test the FileID Step: Test the MaxCount Step: Test the StartDate Step: Test the CollectionID Test success: alarmExceptionTest Starting testcase AlarmExceptionTest Test starting: alarmExceptionTest Description: Tests that AlarmExceptions can be thrown. Test success: alarmExceptionTest Finished testcase Finished suite Finished project Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 7.915 sec - in TestSuite Results : Tests run: 5, Failures: 0, Errors: 0, Skipped: 0 [JENKINS] Recording test results [INFO] [INFO] --- maven-war-plugin:2.4:war (default-war) @ bitrepository-alarm-service --- [INFO] Packaging webapp [INFO] Assembling webapp [bitrepository-alarm-service] in [/home/cibuild01/workspace/Bitrepository-sonar/bitrepository-alarm-service/target/bitrepository-alarm-service-1.6-SNAPSHOT] [INFO] Processing war project [INFO] Copying webapp resources [/home/cibuild01/workspace/Bitrepository-sonar/bitrepository-alarm-service/src/main/webapp] [INFO] Webapp assembled in [66 msecs] [INFO] Building war: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-alarm-service/target/bitrepository-alarm-service-1.6-SNAPSHOT.war [INFO] [INFO] --- maven-jar-plugin:2.4:test-jar (default) @ bitrepository-alarm-service --- [INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-alarm-service/target/bitrepository-alarm-service-1.6-SNAPSHOT-tests.jar [INFO] [INFO] --- maven-source-plugin:2.2.1:jar-no-fork (attach-sources-no-fork) @ bitrepository-alarm-service --- [INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-alarm-service/target/bitrepository-alarm-service-1.6-SNAPSHOT-sources.jar [INFO] [INFO] --- maven-assembly-plugin:2.4:single (distribution) @ bitrepository-alarm-service --- [INFO] Reading assembly descriptor: src/main/assembly/assembly.xml [INFO] Building tar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-alarm-service/target/bitrepository-alarm-service-1.6-SNAPSHOT-distribution.tar.gz [INFO] [INFO] --- maven-install-plugin:2.5.1:install (default-install) @ bitrepository-alarm-service --- [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-alarm-service/target/bitrepository-alarm-service-1.6-SNAPSHOT.war to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-alarm-service/1.6-SNAPSHOT/bitrepository-alarm-service-1.6-SNAPSHOT.war [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-alarm-service/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-alarm-service/1.6-SNAPSHOT/bitrepository-alarm-service-1.6-SNAPSHOT.pom [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-alarm-service/target/bitrepository-alarm-service-1.6-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-alarm-service/1.6-SNAPSHOT/bitrepository-alarm-service-1.6-SNAPSHOT-tests.jar [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-alarm-service/target/bitrepository-alarm-service-1.6-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-alarm-service/1.6-SNAPSHOT/bitrepository-alarm-service-1.6-SNAPSHOT-sources.jar [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-alarm-service/target/bitrepository-alarm-service-1.6-SNAPSHOT-distribution.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-alarm-service/1.6-SNAPSHOT/bitrepository-alarm-service-1.6-SNAPSHOT-distribution.tar.gz [JENKINS] Archiving disabled [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building Bitrepository Audit Trail Service 1.6-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-audit-trail-service --- [INFO] Deleting /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-audit-trail-service/target [INFO] [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ bitrepository-audit-trail-service --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 9 resources [INFO] [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ bitrepository-audit-trail-service --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 23 source files to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-audit-trail-service/target/classes [INFO] [INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ bitrepository-audit-trail-service --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ bitrepository-audit-trail-service --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 11 source files to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-audit-trail-service/target/test-classes [INFO] [INFO] --- maven-surefire-plugin:2.17:test (default-test) @ bitrepository-audit-trail-service --- [INFO] Surefire report directory: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-audit-trail-service/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 AuditDatabaseTest Test starting: AuditDatabaseExtractionTest Description: Testing the connection to the audit trail service database especially with regards to extracting the data from it. Step: Setup the variables and constants. Step: Adds the variables to the settings and instantaites the database cache Step: Validate that the database is empty and then populate it. Step: Extract the audit trails Step: Test the extraction of FileID Step: Test the extraction of CollectionID Step: Perform extraction based on the component id. Step: Perform extraction based on the sequence number restriction Step: Perform extraction based on actor id restriction. Step: Perform extraction based on operation restriction. Step: Perform extraction based on date restriction. Step: Perform extraction based on fingerprint restriction. Step: Perform extraction based on operationID restriction. Test success: AuditDatabaseExtractionTest Test starting: AuditDatabaseGoodIngestTest Description: Testing good case ingest of audittrails into the database Step: Adds the variables to the settings and instantaites the database cache Step: Build test data Test success: AuditDatabaseGoodIngestTest Test starting: AuditDatabaseIngestTest Description: Testing ingest of audittrails into the database Step: Adds the variables to the settings and instantaites the database cache Step: Test ingesting with all data Step: Test ingesting with no timestamp Step: Test ingesting with no file action Step: Test ingesting with no actor Step: Test ingesting with no audit info Step: Test ingesting with no file id Step: Test ingesting with no info Step: Test ingesting with no component id Step: Test ingesting with no sequence number Step: Test ingest with very long auditInfo (255+) Step: Test ingest with very long info (255+) Test success: AuditDatabaseIngestTest Test starting: AuditDatabasePreservationTest Description: Tests the functions related to the preservation of the database. Step: Adds the variables to the settings and instantaites the database cache Step: Validate the preservation sequence number Step: Validate the insertion of the preservation sequence number Test success: AuditDatabasePreservationTest Starting testcase AuditCollectorTest Test starting: auditCollectorIntervalTest Description: Test that the collector calls the AuditClient at the correct intervals. 02:21:59.552 WARN o.b.a.collector.IncrementalCollector - Received bad collection id! Expected 'TwoPillarCollection', but got 'dummy-collection'. 02:22:00.567 WARN o.b.a.collector.IncrementalCollector - Received bad collection id! Expected 'TwoPillarCollection', but got 'dummy-collection'. Test success: auditCollectorIntervalTest Starting testcase LocalAuditPreservationTest Test starting: auditPreservationIngestTest Description: Tests the ingest of the audit trail preservation. Step: Setup variables and settings for the test Step: Create the preserver and populate the store Step: Call the preservation of audit trails now. Test success: auditPreservationIngestTest Starting testcase IncrementalCollectorTest Test starting: collectionIdFailureTest Description: Tests what happens when a wrong collection id is received. Step: Step: Start a collection with two contributors Step: Send an auditTrail result from contributor 1 with a wrong collection id. 02:22:01.243 WARN o.b.a.collector.IncrementalCollector - Received bad collection id! Expected 'dummy-collection', but got 'FalseCollection1449192121129'. Test success: collectionIdFailureTest Test starting: contributorFailureTest Description: Tests that the collector is able to collect from the remaining contributors if a contributor fails. Step: Step: Start a collection with two contributors Step: Send a audit trail result from contributor 2 with the PartialResults boolean set to true and a failed event from contributor 1 02:22:01.356 WARN o.b.a.collector.IncrementalCollector - Event: null: null: COMPONENT_FAILED: ContributorID Contributor1 ResponseCode: REQUEST_NOT_SUPPORTED 02:22:01.360 WARN o.b.a.collector.IncrementalCollector - Event: null: null: FAILED: , 02:22:01.364 ERROR o.b.a.collector.IncrementalCollector - Problem in collecting audittrails, collection will not be complete for collection 'dummy-collection' org.bitrepository.client.exceptions.NegativeResponseException: at org.bitrepository.access.getaudittrails.BlockingAuditTrailClient.getAuditTrails(BlockingAuditTrailClient.java:61) ~[bitrepository-client-1.6-SNAPSHOT.jar:1.6-SNAPSHOT] at org.bitrepository.audittrails.collector.IncrementalCollector.collect(IncrementalCollector.java:135) [classes/:na] at org.bitrepository.audittrails.collector.IncrementalCollector.performCollection(IncrementalCollector.java:112) [classes/:na] at org.bitrepository.audittrails.collector.IncrementalCollectorTest$CollectionRunner.run(IncrementalCollectorTest.java:288) [test-classes/:na] at java.lang.Thread.run(Thread.java:745) [na:1.8.0_11] Step: Send another audit trail result from contributor 2 with PartialResults set to false Test success: contributorFailureTest Test starting: multipleIncrementTest Description: Verifies the behaviour in the case where the adit trails needs to be reteived in multiple requests because of MaxNumberOfResults limits. Step: Start a collection with two contributors Step: Send a audit trail result from contributor 1 and 2 with the PartialResults boolean set to true Step: Send another audit trail result from the contributors, now with PartialResults set to false Test success: multipleIncrementTest Test starting: singleIncrementTest Description: Verifies the behaviour in the simplest case with just one result set Step: Start a collection with two contributors Step: Send a audit trail result from contributor 1 Step: Send a audit trail result from contributor 2 Test success: singleIncrementTest Starting testcase AuditPreservationEventHandlerTest Test starting: auditPreservationEventHandlerTest Description: Test the handling of the audit trail event handler. Step: Setup Step: Test the handling of another complete event. Test success: auditPreservationEventHandlerTest Starting testcase AuditServiceDatabaseMigrationTest Test starting: testMigratingAuditServiceDatabase Description: Tests that the database can be migrated to latest version with the provided scripts. Step: Validate setup Step: Perform migration 02:22:03.648 WARN o.b.service.database.DatabaseUtils - Migrating AuditServiceDB from version 2 to 3. 02:22:04.208 WARN o.b.service.database.DatabaseUtils - Migrating AuditServiceDB from version 3 to 4. 02:22:04.248 WARN o.b.service.database.DatabaseUtils - Migrating AuditServiceDB from version 4 to 5. Test success: testMigratingAuditServiceDatabase Finished testcase Finished suite Finished project Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 21.193 sec - in TestSuite Results : Tests run: 12, Failures: 0, Errors: 0, Skipped: 0 [JENKINS] Recording test results [INFO] [INFO] --- maven-war-plugin:2.4:war (default-war) @ bitrepository-audit-trail-service --- [INFO] Packaging webapp [INFO] Assembling webapp [bitrepository-audit-trail-service] in [/home/cibuild01/workspace/Bitrepository-sonar/bitrepository-audit-trail-service/target/bitrepository-audit-trail-service-1.6-SNAPSHOT] [INFO] Processing war project [INFO] Copying webapp resources [/home/cibuild01/workspace/Bitrepository-sonar/bitrepository-audit-trail-service/src/main/webapp] [INFO] Webapp assembled in [162 msecs] [INFO] Building war: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-audit-trail-service/target/bitrepository-audit-trail-service-1.6-SNAPSHOT.war [INFO] [INFO] --- maven-jar-plugin:2.4:test-jar (default) @ bitrepository-audit-trail-service --- [INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-audit-trail-service/target/bitrepository-audit-trail-service-1.6-SNAPSHOT-tests.jar [INFO] [INFO] --- maven-source-plugin:2.2.1:jar-no-fork (attach-sources-no-fork) @ bitrepository-audit-trail-service --- [INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-audit-trail-service/target/bitrepository-audit-trail-service-1.6-SNAPSHOT-sources.jar [INFO] [INFO] --- maven-assembly-plugin:2.4:single (distribution) @ bitrepository-audit-trail-service --- [INFO] Reading assembly descriptor: src/main/assembly/assembly.xml [INFO] Building tar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-audit-trail-service/target/bitrepository-audit-trail-service-1.6-SNAPSHOT-distribution.tar.gz [INFO] [INFO] --- maven-install-plugin:2.5.1:install (default-install) @ bitrepository-audit-trail-service --- [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-audit-trail-service/target/bitrepository-audit-trail-service-1.6-SNAPSHOT.war to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-audit-trail-service/1.6-SNAPSHOT/bitrepository-audit-trail-service-1.6-SNAPSHOT.war [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-audit-trail-service/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-audit-trail-service/1.6-SNAPSHOT/bitrepository-audit-trail-service-1.6-SNAPSHOT.pom [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-audit-trail-service/target/bitrepository-audit-trail-service-1.6-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-audit-trail-service/1.6-SNAPSHOT/bitrepository-audit-trail-service-1.6-SNAPSHOT-tests.jar [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-audit-trail-service/target/bitrepository-audit-trail-service-1.6-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-audit-trail-service/1.6-SNAPSHOT/bitrepository-audit-trail-service-1.6-SNAPSHOT-sources.jar [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-audit-trail-service/target/bitrepository-audit-trail-service-1.6-SNAPSHOT-distribution.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-audit-trail-service/1.6-SNAPSHOT/bitrepository-audit-trail-service-1.6-SNAPSHOT-distribution.tar.gz [JENKINS] Archiving disabled [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building Bitrepository Reference Pillar 1.6-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-reference-pillar --- [INFO] Deleting /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target [INFO] [INFO] --- maven-dependency-plugin:2.8:unpack-dependencies (unpack-shared-sqlscripts) @ bitrepository-reference-pillar --- [INFO] Unpacking /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-service/target/bitrepository-service-1.6-SNAPSHOT.jar to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/classes with includes "**/*.sql" and excludes "" [INFO] [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ bitrepository-reference-pillar --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 10 resources [INFO] [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ bitrepository-reference-pillar --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 44 source files to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/classes [INFO] [INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ bitrepository-reference-pillar --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 12 resources [INFO] [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ bitrepository-reference-pillar --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 70 source files to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/test-classes [INFO] [INFO] --- maven-surefire-plugin:2.17:test (default-test) @ bitrepository-reference-pillar --- [INFO] Surefire report directory: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/surefire-reports ------------------------------------------------------- T E S T S ------------------------------------------------------- Running TestSuite Configuring TestNG with: TestNG652Configurator Starting test project Reference Pillar Test Suite: Surefire suite Starting testcase ChecksumDatabaseTest Test starting: testChecksumDatabaseExtraction Description: Test the extraction of data from the checksum database. Step: Check whether the default entry exists. Step: Extract calculation date Step: Extract the checksum Step: Extract the whole entry Step: Extract all entries Test success: testChecksumDatabaseExtraction Test starting: testDeletion Description: Test that data can be deleted from the database. Step: Check whether the default entry exists. Step: Remove the default entry Test success: testDeletion Test starting: testExtractionOfMissingData Description: Test the handling of bad arguments. Step: Try to get the date of a wrong file id. Step: Try to get the date of a wrong file id. Step: Try to remove a bad file id Test success: testExtractionOfMissingData Test starting: testGetFileIDsRestrictions Description: Tests the restrictions on the GetFileIDs call to the database. Step: Instantiate database with appropriate data. Step: Test with no time restrictions and 10000 max_results Step: Test with minimum-date earlier than first file Step: Test with maximum-date earlier than first file Step: Test with minimum-date set to later than second file. Step: Test with maximum-date set to later than second file. Step: Test with minimum-date set to middle date. Step: Test with maximum-date set to middle date. Step: Test with both minimum-date and maximum-date set to middle date. Step: Test the first file-id, with no other restrictions Step: Test the second file-id, with no other restrictions Step: Test the date for the first file-id, while requesting the second file-id Test success: testGetFileIDsRestrictions Test starting: testReplacingExistingEntry Description: Test that an entry can be replaced by another in the database. Step: Check whether the default entry exists. Step: Replace the checksum and date Test success: testReplacingExistingEntry Test starting: testSpecifiedEntryExtraction Description: Test that specific entries can be extracted. Has two entries in the database: one for the current timestamp and one for the epoch. Step: Instantiate database with appropriate data. Step: Extract with out restrictions Step: Extract with a maximum of 1 entry Step: Extract all dates older than this tests instantiation Step: Extract all dates newer than this tests instantiation Step: Extract all dates older than the newest instance Step: Extract all dates newer than the oldest instantiation Test success: testSpecifiedEntryExtraction Starting testcase ChecksumEntryTest Test starting: testExtendedTestCase Description: Test the ChecksumEntry Step: Create a ChecksumEntry Step: Change the value of the checksum Step: Change the value of the calculation date Test success: testExtendedTestCase Starting testcase FullPillarModelTest Test starting: testPillarModelBasicFunctionality Description: Test the basic functions of the full reference pillar model. Step: Check the pillar id in the pillar model Step: Ask whether it can handle a file of size 0 Step: Ask whether it can handle a file of maximum size Step: Check the ChecksumPillarSpec Test success: testPillarModelBasicFunctionality Test starting: testPillarModelHasFile Description: Test that the file exists, when placed in the archive and cache Step: Setup Step: Check whether file exists and retrieve it. Step: Verify that no exceptions are thrown when verifying file existance. Step: Check retrieval of non-default checksum Test success: testPillarModelHasFile Test starting: testPillarModelNoFile Description: Test that the file exists, when placed in the archive and cache Step: Setup Step: Check whether file exists and try to retrieve it. Step: Verify that anexceptions are thrown when verifying file existance. 02:22:31.952 WARN o.b.pillar.store.FileStorageModel - The file 'DefaultFile' has been requested, but we do not have that file in collection 'TwoPillarCollection'! Test success: testPillarModelNoFile Starting testcase GetChecksumsTest Added fixture: Initialize a new Pillar. Test starting: badCaseIdentification Description: Tests the identification for a GetChecksums operation on the pillar for the failure scenario, when the file is missing. Step: Set up constants and variables. Step: Setup for delivering pillar id and not having the file Step: Create and send the identify request message. Result: Received message on TEST-TOPIC-badCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsResponse@63a9c661[correlationID=54ddbefd-fbe5-46cd-8696-9ab3205e5a22, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseIdentification-cibuild01-contributor, from=Pillar-badCaseIdentification, to=badCaseIdentification, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@4b425577[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@5934153e[fileID=DefaultFilebadCaseIdentification, allFileIDs=], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@3bb9ca38[checksumType=MD5, checksumSalt=, otherChecksumType=], pillarID=Pillar-badCaseIdentification, pillarChecksumSpec=, timeToDeliver=] Step: Retrieve and validate the response getPillarID() the pillar. Test success: badCaseIdentification Added fixture: Initialize a new Pillar. Test starting: badCaseOperationNoFile Description: Tests the GetChecksums functionality of the pillar for the failure scenario, where it does not have the file. Step: Set up constants and variables. Step: Setup for not having the file Step: Create and send the actual GetChecksums message to the pillar. 02:22:33.998 WARN o.b.p.m.GetChecksumsRequestHandler - The following file is missing 'DefaultFilebadCaseOperationNoFile' at collection 'TwoPillarCollection'. Result: Received message on TEST-TOPIC-badCaseOperationNoFile-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@31f77791[correlationID=f1436025-8cdb-47b5-8781-33d89cc0b32e, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@552fee7a[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@548e43b1[checksumType=MD5, checksumSalt=, otherChecksumType=], resultingChecksums=, partialResult=] Step: Retrieve the FinalResponse for the GetChecksums request Test success: badCaseOperationNoFile Added fixture: Initialize a new Pillar. Test starting: goodCaseIdentification Description: Tests the identification for a GetChecksums operation on the pillar for the successful scenario. Step: Set up constants and variables. Step: Setup for having the file and delivering pillar id Step: Create and send the identify request message. Result: Received message on TEST-TOPIC-goodCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsResponse@62cbc478[correlationID=2b322f52-f5c4-4839-b761-ad7bfe4de6b6, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseIdentification-cibuild01-contributor, from=Pillar-goodCaseIdentification, to=goodCaseIdentification, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@5438fa43[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@512abf25[fileID=DefaultFilegoodCaseIdentification, allFileIDs=], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@515ab3f2[checksumType=MD5, checksumSalt=, otherChecksumType=], pillarID=Pillar-goodCaseIdentification, pillarChecksumSpec=, timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@6d0e45a5[timeMeasureUnit=MILLISECONDS, timeMeasureValue=1000]] Step: Retrieve and validate the response getPillarID() the pillar. Test success: goodCaseIdentification Added fixture: Initialize a new Pillar. Test starting: goodCaseOperationAllFiles Description: Tests the GetChecksums operation on the pillar for the successful scenario, when requesting all files. Step: Set up constants and variables. Step: Setup for having the file and delivering result-set Step: Create and send the actual GetChecksums message to the pillar. Result: Received message on TEST-TOPIC-goodCaseOperationAllFiles-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsProgressResponse@656c5c3[correlationID=bd56cf11-2f8a-4e14-a1c0-ced742456e19, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationAllFiles-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationAllFiles-cibuild01-contributor, from=Pillar-goodCaseOperationAllFiles, to=goodCaseOperationAllFiles, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@7911cc15[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to calculate checksums.], pillarID=Pillar-goodCaseOperationAllFiles, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@4409cae6[fileID=, allFileIDs=true], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@14e750c5[checksumType=MD5, checksumSalt=, otherChecksumType=], resultAddress=] Result: Received message on TEST-TOPIC-goodCaseOperationAllFiles-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@77324a58[correlationID=bd56cf11-2f8a-4e14-a1c0-ced742456e19, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationAllFiles-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationAllFiles-cibuild01-contributor, from=Pillar-goodCaseOperationAllFiles, to=goodCaseOperationAllFiles, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@2c7c0e36[responseCode=OPERATION_COMPLETED, responseText=], pillarID=Pillar-goodCaseOperationAllFiles, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@14e750c5[checksumType=MD5, checksumSalt=, otherChecksumType=], resultingChecksums=org.bitrepository.bitrepositoryelements.ResultingChecksums@307cf964[resultAddress=, checksumDataItems={org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@374ccb9[fileID=DefaultFile, checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2015-12-04T02:22:36.586+01:00],org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@66713605[fileID=goodCaseOperationAllFiles-cibuild01--Test-File-1449192156583, checksumValue={18,52,-52,-52,-52,-52,67,34}, calculationTimestamp=1970-01-01T01:00:00.000+01:00]}], partialResult=false] Step: Retrieve the ProgressResponse for the GetChecksums request Step: Retrieve the FinalResponse for the GetChecksums request Test success: goodCaseOperationAllFiles Added fixture: Initialize a new Pillar. Test starting: goodCaseOperationSingleFile Description: Tests the GetChecksums operation on the pillar for the successful scenario when requesting one specific file. Step: Set up constants and variables. Step: Setup for having the file and delivering result-set Step: Create and send the actual GetChecksums message to the pillar. Result: Received message on TEST-TOPIC-goodCaseOperationSingleFile-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsProgressResponse@401317a0[correlationID=1a284731-fbc7-4d90-8207-cd151a469058, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationSingleFile-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationSingleFile-cibuild01-contributor, from=Pillar-goodCaseOperationSingleFile, to=goodCaseOperationSingleFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@3f866f50[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to calculate checksums.], pillarID=Pillar-goodCaseOperationSingleFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@5844a2d1[fileID=DefaultFilegoodCaseOperationSingleFile, allFileIDs=], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1201769d[checksumType=MD5, checksumSalt=, otherChecksumType=], resultAddress=] Result: Received message on TEST-TOPIC-goodCaseOperationSingleFile-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@4af7dd6a[correlationID=1a284731-fbc7-4d90-8207-cd151a469058, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationSingleFile-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationSingleFile-cibuild01-contributor, from=Pillar-goodCaseOperationSingleFile, to=goodCaseOperationSingleFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@4607d78b[responseCode=OPERATION_COMPLETED, responseText=], pillarID=Pillar-goodCaseOperationSingleFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1201769d[checksumType=MD5, checksumSalt=, otherChecksumType=], resultingChecksums=org.bitrepository.bitrepositoryelements.ResultingChecksums@3b28b7b0[resultAddress=, checksumDataItems={org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@22048bd6[fileID=DefaultFilegoodCaseOperationSingleFile, checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2015-12-04T02:22:36.914+01:00]}], partialResult=false] Step: Retrieve the ProgressResponse for the GetChecksums request Step: Retrieve the FinalResponse for the GetChecksums request Test success: goodCaseOperationSingleFile Added fixture: Initialize a new Pillar. Test starting: testRestrictions Description: Tests that the restrictions are correctly passed on to the cache. Step: Set up constants and variables. Step: Setup for only delivering result-set when the correct restrictions are given. Step: Create and send the actual GetChecksums message to the pillar. Result: Received message on TEST-TOPIC-testRestrictions-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsProgressResponse@26bb92e2[correlationID=e60a394b-8a5d-4ba4-ab05-256f0c852103, collectionID=TwoPillarCollection, destination=TEST-TOPIC-testRestrictions-cibuild01, replyTo=TEST-TOPIC-Pillar-testRestrictions-cibuild01-contributor, from=Pillar-testRestrictions, to=testRestrictions, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@18907af2[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to calculate checksums.], pillarID=Pillar-testRestrictions, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@658e7ead[fileID=, allFileIDs=true], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@cfd5cd2[checksumType=MD5, checksumSalt=, otherChecksumType=], resultAddress=] Result: Received message on TEST-TOPIC-testRestrictions-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@762bf32d[correlationID=e60a394b-8a5d-4ba4-ab05-256f0c852103, collectionID=TwoPillarCollection, destination=TEST-TOPIC-testRestrictions-cibuild01, replyTo=TEST-TOPIC-Pillar-testRestrictions-cibuild01-contributor, from=Pillar-testRestrictions, to=testRestrictions, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@6d7740f0[responseCode=OPERATION_COMPLETED, responseText=], pillarID=Pillar-testRestrictions, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@cfd5cd2[checksumType=MD5, checksumSalt=, otherChecksumType=], resultingChecksums=org.bitrepository.bitrepositoryelements.ResultingChecksums@7b1a30e5[resultAddress=, checksumDataItems={org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@1de7f898[fileID=DefaultFile, checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2015-12-04T02:22:37.365+01:00]}], partialResult=false] Step: Retrieve the ProgressResponse for the GetChecksums request Step: Retrieve the FinalResponse for the GetChecksums request Test success: testRestrictions Starting testcase GetFileIDsTest Added fixture: Initialize a new Pillar. Test starting: badCaseIdentification Description: Tests the identification for a GetFileIDs operation on the pillar for the failure scenario, when the file is missing. Step: Set up constants and variables. Step: Setup for delivering pillar id and not having the file Step: Create and send the identify request message. 02:22:37.619 WARN o.b.p.m.IdentifyPillarsForGetFileIDsRequestHandler - The following file is missing 'DefaultFilebadCaseIdentification' at collection 'TwoPillarCollection'. Result: Received message on TEST-TOPIC-badCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsResponse@43deba42[correlationID=a8426cb6-06b4-4611-af6f-9c8ea83829c7, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseIdentification-cibuild01-contributor, from=Pillar-badCaseIdentification, to=badCaseIdentification, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@e795a1d[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseIdentification, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@38c10190[fileID=DefaultFilebadCaseIdentification, allFileIDs=], timeToDeliver=] Step: Retrieve and validate the response getPillarID() the pillar. Test success: badCaseIdentification Added fixture: Initialize a new Pillar. Test starting: badCaseOperationNoFile Description: Tests the GetFileIDs functionality of the pillar for the failure scenario, where it does not have the file. Step: Set up constants and variables. Step: Setup for not having the file Step: Create and send the actual GetFileIDs message to the pillar. 02:22:38.849 WARN o.b.p.m.GetFileIDsRequestHandler - The following file is missing 'DefaultFilebadCaseOperationNoFile' at collection 'TwoPillarCollection'. Result: Received message on TEST-TOPIC-badCaseOperationNoFile-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsFinalResponse@60652518[correlationID=446bcf11-af20-44e0-a936-3349414d8906, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@438aaa9f[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@3f06ebe0[fileID=DefaultFilebadCaseOperationNoFile, allFileIDs=], resultingFileIDs=, partialResult=] 02:22:38.852 WARN o.b.p.m.GetFileIDsRequestHandler - The following file is missing 'DefaultFilebadCaseOperationNoFile' at collection 'TwoPillarCollection'. Result: Received message on TEST-TOPIC-badCaseOperationNoFile-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsFinalResponse@481ed95c[correlationID=446bcf11-af20-44e0-a936-3349414d8906, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@40cf6254[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@3f06ebe0[fileID=DefaultFilebadCaseOperationNoFile, allFileIDs=], resultingFileIDs=, partialResult=] Step: Retrieve the FinalResponse for the GetFileIDs request Test success: badCaseOperationNoFile Result: The following messages haven't been handled by the testcase: org.bitrepository.bitrepositorymessages.GetFileIDsFinalResponse@481ed95c[correlationID=446bcf11-af20-44e0-a936-3349414d8906, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@40cf6254[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@3f06ebe0[fileID=DefaultFilebadCaseOperationNoFile, allFileIDs=], resultingFileIDs=, partialResult=] 02:22:39.864 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: org.bitrepository.bitrepositorymessages.GetFileIDsFinalResponse@481ed95c[correlationID=446bcf11-af20-44e0-a936-3349414d8906, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@40cf6254[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@3f06ebe0[fileID=DefaultFilebadCaseOperationNoFile, allFileIDs=], resultingFileIDs=, partialResult=] Added fixture: Initialize a new Pillar. Test starting: goodCaseIdentification Description: Tests the identification for a GetFileIDs operation on the pillar for the successful scenario. Step: Set up constants and variables. Step: Setup for having the file and delivering pillar id Step: Create and send the identify request message. Result: Received message on TEST-TOPIC-goodCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsResponse@2211b44f[correlationID=9d71662d-e5b1-459b-9214-2ff12bd22626, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseIdentification-cibuild01-contributor, from=Pillar-goodCaseIdentification, to=goodCaseIdentification, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@6c830ebd[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], pillarID=Pillar-goodCaseIdentification, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@15f519f7[fileID=DefaultFilegoodCaseIdentification, allFileIDs=], timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@4a336377[timeMeasureUnit=MILLISECONDS, timeMeasureValue=1000]] Step: Retrieve and validate the response getPillarID() the pillar. Test success: goodCaseIdentification Test starting: componentIDTest Test success: componentIDTest Starting testcase PutFileTest Added fixture: Initialize a new Pillar. Test starting: badCaseIdentification Description: Tests the identification for a PutFile operation on the pillar for the failure scenario, when the file already exists. Step: Set up constants and variables. Step: Setup for already having the file and delivering pillar id Step: Create and send the identify request message. Result: Received message on TEST-TOPIC-badCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileResponse@7fcc3745[correlationID=49a84850-928a-4e76-bec0-aeadb5f00cd7, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseIdentification-cibuild01-contributor, from=Pillar-badCaseIdentification, to=badCaseIdentification, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@6d35ff7b[responseCode=DUPLICATE_FILE_FAILURE, responseText=], pillarID=Pillar-badCaseIdentification, fileID=DefaultFilebadCaseIdentification, pillarChecksumSpec=, checksumDataForExistingFile=, timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@4ef31221[timeMeasureUnit=MILLISECONDS, timeMeasureValue=1000]] Step: Retrieve and validate the response getPillarID() the pillar. Test success: badCaseIdentification Added fixture: Initialize a new Pillar. Test starting: badCaseOperationFileAlreadyExists Description: Tests the PutFile operation on the pillar for the failure scenario, when the file already exists. Step: Set up constants and variables. Step: Setup for already having the file and delivering pillar id Step: Create and send the identify request message. Result: Received message on TEST-TOPIC-badCaseOperationFileAlreadyExists-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileFinalResponse@197d5a87[correlationID=7c5be360-56c9-4a67-9ced-5a805e595a3d, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationFileAlreadyExists-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationFileAlreadyExists-cibuild01-contributor, from=Pillar-badCaseOperationFileAlreadyExists, to=badCaseOperationFileAlreadyExists, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@131d977f[responseCode=DUPLICATE_FILE_FAILURE, responseText=We already have the file], pillarID=Pillar-badCaseOperationFileAlreadyExists, pillarChecksumSpec=, fileID=DefaultFilebadCaseOperationFileAlreadyExists, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForNewFile=, checksumDataForExistingFile=] Step: Retrieve the FinalResponse for the PutFile request Test success: badCaseOperationFileAlreadyExists Added fixture: Initialize a new Pillar. Test starting: badCasePutOperationNoValidationChecksum Description: Tests the PutFile operation on the pillar for the failure scenario, when no validation checksum is given but required. Step: Set up constants and variables. Step: Setup for not already having the file and delivering pillar id Step: Create and send the identify request message. Result: Received message on TEST-TOPIC-badCasePutOperationNoValidationChecksum-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileFinalResponse@4be460e5[correlationID=997518ad-cc48-48fc-871e-c18d18a5580c, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCasePutOperationNoValidationChecksum-cibuild01, replyTo=TEST-TOPIC-Pillar-badCasePutOperationNoValidationChecksum-cibuild01-contributor, from=Pillar-badCasePutOperationNoValidationChecksum, to=badCasePutOperationNoValidationChecksum, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@454e9d65[responseCode=NEW_FILE_CHECKSUM_FAILURE, responseText=A checksum is required for the PutFile operation to be performed.], pillarID=Pillar-badCasePutOperationNoValidationChecksum, pillarChecksumSpec=, fileID=DefaultFilebadCasePutOperationNoValidationChecksum, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForNewFile=, checksumDataForExistingFile=] 02:22:45.866 WARN o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@7805478c[origDateTime=2015-12-04T02:22:45.865+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCasePutOperationNoValidationChecksum, alarmText=A checksum is required for the PutFile operation to be performed., fileID=DefaultFilebadCasePutOperationNoValidationChecksum, collectionID=TwoPillarCollection] Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@6807989e[correlationID=c76ffa94-9488-4ee7-93db-77a7b38ab8a5, collectionID=TwoPillarCollection, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-Pillar-badCasePutOperationNoValidationChecksum-cibuild01-contributor, from=Pillar-badCasePutOperationNoValidationChecksum, to=, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@7805478c[origDateTime=2015-12-04T02:22:45.865+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCasePutOperationNoValidationChecksum, alarmText=A checksum is required for the PutFile operation to be performed., fileID=DefaultFilebadCasePutOperationNoValidationChecksum, collectionID=TwoPillarCollection]] Step: Retrieve the FinalResponse for the PutFile request Step: Pillar should have sent an alarm Test success: badCasePutOperationNoValidationChecksum Added fixture: Initialize a new Pillar. Test starting: goodCaseIdentification Description: Tests the identification for a PutFile operation on the pillar for the successful scenario. Step: Set up constants and variables. Step: Setup for not already having the file and delivering pillar id Step: Create and send the identify request message. Result: Received message on TEST-TOPIC-goodCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileResponse@2125535d[correlationID=1e228f6b-fd0f-4ed8-861c-188dc0674bad, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseIdentification-cibuild01-contributor, from=Pillar-goodCaseIdentification, to=goodCaseIdentification, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@d190639[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], pillarID=Pillar-goodCaseIdentification, fileID=DefaultFilegoodCaseIdentification, pillarChecksumSpec=, checksumDataForExistingFile=, timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@5f82209e[timeMeasureUnit=MILLISECONDS, timeMeasureValue=1000]] Step: Retrieve and validate the response getPillarID() the pillar. Test success: goodCaseIdentification Added fixture: Initialize a new Pillar. Test starting: goodCaseOperationWithChecksumReturn Description: Tests the PutFile operation on the pillar for the success scenario, when requesting the cheksum of the file returned. Step: Set up constants and variables. Step: Setup for not already having the file and delivering pillar id, and delivering an answer for the checksum request Step: Create and send the identify request message. Result: Received message on TEST-TOPIC-goodCaseOperationWithChecksumReturn-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileProgressResponse@1987807b[correlationID=935d8fbd-09f9-4be6-927c-ffbc45915747, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationWithChecksumReturn-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationWithChecksumReturn-cibuild01-contributor, from=Pillar-goodCaseOperationWithChecksumReturn, to=goodCaseOperationWithChecksumReturn, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@71469e01[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Started to receive data.], pillarID=Pillar-goodCaseOperationWithChecksumReturn, pillarChecksumSpec=, fileID=DefaultFilegoodCaseOperationWithChecksumReturn, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt] Result: Received message on TEST-TOPIC-goodCaseOperationWithChecksumReturn-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileFinalResponse@2b464384[correlationID=935d8fbd-09f9-4be6-927c-ffbc45915747, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationWithChecksumReturn-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationWithChecksumReturn-cibuild01-contributor, from=Pillar-goodCaseOperationWithChecksumReturn, to=goodCaseOperationWithChecksumReturn, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@681b42d3[responseCode=OPERATION_COMPLETED, responseText=], pillarID=Pillar-goodCaseOperationWithChecksumReturn, pillarChecksumSpec=, fileID=DefaultFilegoodCaseOperationWithChecksumReturn, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForNewFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@77f7352a[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@4ede8888[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2015-12-04T02:22:48.212+01:00], checksumDataForExistingFile=] Step: Retrieve the ProgressResponse for the GetFileIDs request Step: Retrieve the FinalResponse for the PutFile request Test success: goodCaseOperationWithChecksumReturn Starting testcase ReplaceFileTest Added fixture: Initialize a new Pillar. Test starting: badCaseIdentification Description: Tests the identification for a ReplaceFile operation on the pillar for the failure scenario, when the file does not exist. Step: Set up constants and variables. Step: Setup for not having the file and delivering pillar id Step: Create and send the identify request message. Result: Received message on TEST-TOPIC-badCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileResponse@3180aee[correlationID=740b5982-81e2-4657-964b-7ef06ae0fa5f, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseIdentification-cibuild01-contributor, from=Pillar-badCaseIdentification, to=badCaseIdentification, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@5d94ac8a[responseCode=FILE_NOT_FOUND_FAILURE, responseText=Could not find the requested file to delete.], fileID=DefaultFile, pillarID=Pillar-badCaseIdentification, pillarChecksumSpec=, timeToDeliver=] Step: Retrieve and validate the response getPillarID() the pillar. Test success: badCaseIdentification Added fixture: Initialize a new Pillar. Test starting: badCaseOperationMissingFile Description: Tests the ReplaceFile operation on the pillar for the failure scenario, when the file is missing. Step: Set up constants and variables. Step: Setup for not having the file and delivering pillar id Step: Create and send the identify request message. Result: Received message on TEST-TOPIC-badCaseOperationMissingFile-cibuild01 : org.bitrepository.bitrepositorymessages.ReplaceFileFinalResponse@6ee1ddcf[correlationID=df724542-09c5-4382-94df-a40f300199e6, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationMissingFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationMissingFile-cibuild01-contributor, from=Pillar-badCaseOperationMissingFile, to=badCaseOperationMissingFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@6b630d4b[responseCode=FILE_NOT_FOUND_FAILURE, responseText=The file 'DefaultFile' has been requested, but we do not have that file!], pillarID=Pillar-badCaseOperationMissingFile, pillarChecksumSpec=, fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForExistingFile=, checksumDataForNewFile=] Step: Retrieve the FinalResponse for the ReplaceFile request Test success: badCaseOperationMissingFile Added fixture: Initialize a new Pillar. Test starting: badCaseOperationNoDestructiveChecksum Description: Tests the ReplaceFile operation on the pillar for the failure scenario, when no validation checksum is given for the destructive action, but though is required. Step: Set up constants and variables. Step: Setup for having the file and delivering pillar id Step: Create and send the identify request message. Result: Received message on TEST-TOPIC-badCaseOperationNoDestructiveChecksum-cibuild01 : org.bitrepository.bitrepositorymessages.ReplaceFileFinalResponse@3cc817bd[correlationID=43392389-9a54-4b8b-9636-6a6b9ce63ff6, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoDestructiveChecksum-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoDestructiveChecksum-cibuild01-contributor, from=Pillar-badCaseOperationNoDestructiveChecksum, to=badCaseOperationNoDestructiveChecksum, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@64b8eb96[responseCode=EXISTING_FILE_CHECKSUM_FAILURE, responseText=According to the contract a checksum for file to be deleted during the replacing operation is required.], pillarID=Pillar-badCaseOperationNoDestructiveChecksum, pillarChecksumSpec=, fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForExistingFile=, checksumDataForNewFile=] 02:22:52.750 WARN o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@776a7ec6[origDateTime=2015-12-04T02:22:52.750+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCaseOperationNoDestructiveChecksum, alarmText=According to the contract a checksum for file to be deleted during the replacing operation is required., fileID=DefaultFile, collectionID=TwoPillarCollection] Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@2d23a5be[correlationID=e201b26a-08a3-4ef5-9559-e61b021b34c4, collectionID=TwoPillarCollection, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoDestructiveChecksum-cibuild01-contributor, from=Pillar-badCaseOperationNoDestructiveChecksum, to=, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@776a7ec6[origDateTime=2015-12-04T02:22:52.750+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCaseOperationNoDestructiveChecksum, alarmText=According to the contract a checksum for file to be deleted during the replacing operation is required., fileID=DefaultFile, collectionID=TwoPillarCollection]] Step: Retrieve the FinalResponse for the ReplaceFile request Step: Pillar should have sent an alarm Test success: badCaseOperationNoDestructiveChecksum Added fixture: Initialize a new Pillar. Test starting: badCaseOperationNoValidationChecksum Description: Tests the ReplaceFile operation on the pillar for the failure scenario, when no validation checksum is given for the new file, but though is required. Step: Set up constants and variables. Step: Setup for having the file and delivering pillar id Step: Create and send the identify request message. Result: Received message on TEST-TOPIC-badCaseOperationNoValidationChecksum-cibuild01 : org.bitrepository.bitrepositorymessages.ReplaceFileFinalResponse@1e2b37cd[correlationID=abd21c9a-5ca3-4db6-bdbe-7e0d01be9f9e, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoValidationChecksum-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoValidationChecksum-cibuild01-contributor, from=Pillar-badCaseOperationNoValidationChecksum, to=badCaseOperationNoValidationChecksum, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@2ba08f26[responseCode=NEW_FILE_CHECKSUM_FAILURE, responseText=According to the contract a checksum for new file in the replacing operation is required.], pillarID=Pillar-badCaseOperationNoValidationChecksum, pillarChecksumSpec=, fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForExistingFile=, checksumDataForNewFile=] 02:22:53.595 WARN o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@6033f36c[origDateTime=2015-12-04T02:22:53.595+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCaseOperationNoValidationChecksum, alarmText=According to the contract a checksum for new file in the replacing operation is required., fileID=DefaultFile, collectionID=TwoPillarCollection] Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@50b624da[correlationID=de08b288-e65c-4c12-b118-16dc1bbfb38d, collectionID=TwoPillarCollection, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoValidationChecksum-cibuild01-contributor, from=Pillar-badCaseOperationNoValidationChecksum, to=, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@6033f36c[origDateTime=2015-12-04T02:22:53.595+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCaseOperationNoValidationChecksum, alarmText=According to the contract a checksum for new file in the replacing operation is required., fileID=DefaultFile, collectionID=TwoPillarCollection]] Step: Retrieve the FinalResponse for the ReplaceFile request Step: Pillar should have sent an alarm Test success: badCaseOperationNoValidationChecksum Added fixture: Initialize a new Pillar. Test starting: badCaseOperationWrongDestructiveChecksum Description: Tests the ReplaceFile operation on the pillar for the failure scenario, when the checksum for the destructive action is different from the one in the cache. Step: Set up constants and variables. Step: Setup for having the file and delivering pillar id Step: Create and send the identify request message. 02:22:53.728 WARN o.b.p.m.ReplaceFileRequestHandler - Failed to handle replace operation on file 'DefaultFile' since the request had the checksum '1234cccccccc4321' where our local file has the value '1234cccccccc4322'. Sending alarm and respond failure. Result: Received message on TEST-TOPIC-badCaseOperationWrongDestructiveChecksum-cibuild01 : org.bitrepository.bitrepositorymessages.ReplaceFileFinalResponse@1af6974c[correlationID=f41c33fd-9545-454a-b593-394b58aab88f, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationWrongDestructiveChecksum-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationWrongDestructiveChecksum-cibuild01-contributor, from=Pillar-badCaseOperationWrongDestructiveChecksum, to=badCaseOperationWrongDestructiveChecksum, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@61d61b0e[responseCode=EXISTING_FILE_CHECKSUM_FAILURE, responseText=Requested to replace the file 'DefaultFile' with checksum '1234cccccccc4321', but our file had a different checksum.], pillarID=Pillar-badCaseOperationWrongDestructiveChecksum, pillarChecksumSpec=, fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForExistingFile=, checksumDataForNewFile=] 02:22:53.730 WARN o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@3c2188f[origDateTime=2015-12-04T02:22:53.730+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCaseOperationWrongDestructiveChecksum, alarmText=Requested to replace the file 'DefaultFile' with checksum '1234cccccccc4321', but our file had a different checksum., fileID=DefaultFile, collectionID=TwoPillarCollection] Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@646bf8a6[correlationID=0dccd128-13d0-4987-baa2-d5a0e0024d0c, collectionID=TwoPillarCollection, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationWrongDestructiveChecksum-cibuild01-contributor, from=Pillar-badCaseOperationWrongDestructiveChecksum, to=, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@3c2188f[origDateTime=2015-12-04T02:22:53.730+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCaseOperationWrongDestructiveChecksum, alarmText=Requested to replace the file 'DefaultFile' with checksum '1234cccccccc4321', but our file had a different checksum., fileID=DefaultFile, collectionID=TwoPillarCollection]] Step: Retrieve the FinalResponse for the ReplaceFile request Step: Pillar should have sent an alarm Test success: badCaseOperationWrongDestructiveChecksum Added fixture: Initialize a new Pillar. Test starting: goodCaseIdentification Description: Tests the identification for a ReplaceFile operation on the pillar for the successful scenario. Step: Set up constants and variables. Step: Setup for having the file and delivering pillar id Step: Create and send the identify request message. Result: Received message on TEST-TOPIC-goodCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileResponse@644f6e89[correlationID=dc7774b9-e379-43ed-9051-999d55c5eb1d, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseIdentification-cibuild01-contributor, from=Pillar-goodCaseIdentification, to=goodCaseIdentification, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@9ae0794[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], fileID=DefaultFile, pillarID=Pillar-goodCaseIdentification, pillarChecksumSpec=, timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@60e5eed0[timeMeasureUnit=MILLISECONDS, timeMeasureValue=1000]] Step: Retrieve and validate the response getPillarID() the pillar. Test success: goodCaseIdentification Added fixture: Initialize a new Pillar. Test starting: goodCaseOperation Description: Tests the ReplaceFile operation on the pillar for the success scenario. Step: Set up constants and variables. Step: Setup for already having the file and delivering pillar id Step: Create and send the identify request message. Result: Received message on TEST-TOPIC-goodCaseOperation-cibuild01 : org.bitrepository.bitrepositorymessages.ReplaceFileProgressResponse@2d2afc39[correlationID=b7a6ddfa-2f35-4df6-9ed8-233fd9ca34b4, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperation-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperation-cibuild01-contributor, from=Pillar-goodCaseOperation, to=goodCaseOperation, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@e2498a3[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Performing the ReplaceFileRequest for file 'DefaultFile' at 'TwoPillarCollection'.], pillarID=Pillar-goodCaseOperation, pillarChecksumSpec=, fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt] Result: Received message on TEST-TOPIC-goodCaseOperation-cibuild01 : org.bitrepository.bitrepositorymessages.ReplaceFileFinalResponse@6a7ab205[correlationID=b7a6ddfa-2f35-4df6-9ed8-233fd9ca34b4, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperation-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperation-cibuild01-contributor, from=Pillar-goodCaseOperation, to=goodCaseOperation, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@10cb5047[responseCode=OPERATION_COMPLETED, responseText=], pillarID=Pillar-goodCaseOperation, pillarChecksumSpec=, fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForExistingFile=, checksumDataForNewFile=] Step: Retrieve the ProgressResponse for the GetFileIDs request Step: Retrieve the FinalResponse for the ReplaceFile request Test success: goodCaseOperation Added fixture: Initialize a new Pillar. Test starting: goodCaseOperationWithChecksumsReturn Description: Tests the ReplaceFile operation on the pillar for the success scenario, when requesting both the cheksums of the file returned. Step: Set up constants and variables. Step: Setup for already having the file and delivering pillar id Step: Create and send the identify request message. Result: Received message on TEST-TOPIC-goodCaseOperationWithChecksumsReturn-cibuild01 : org.bitrepository.bitrepositorymessages.ReplaceFileProgressResponse@183a84f4[correlationID=2cd1b4ee-7279-4ddf-a2cb-abea91d9e744, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationWithChecksumsReturn-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationWithChecksumsReturn-cibuild01-contributor, from=Pillar-goodCaseOperationWithChecksumsReturn, to=goodCaseOperationWithChecksumsReturn, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@2b9bbaa8[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Performing the ReplaceFileRequest for file 'DefaultFile' at 'TwoPillarCollection'.], pillarID=Pillar-goodCaseOperationWithChecksumsReturn, pillarChecksumSpec=, fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt] Result: Received message on TEST-TOPIC-goodCaseOperationWithChecksumsReturn-cibuild01 : org.bitrepository.bitrepositorymessages.ReplaceFileFinalResponse@11771fd6[correlationID=2cd1b4ee-7279-4ddf-a2cb-abea91d9e744, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationWithChecksumsReturn-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationWithChecksumsReturn-cibuild01-contributor, from=Pillar-goodCaseOperationWithChecksumsReturn, to=goodCaseOperationWithChecksumsReturn, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@1c512bb[responseCode=OPERATION_COMPLETED, responseText=], pillarID=Pillar-goodCaseOperationWithChecksumsReturn, pillarChecksumSpec=, fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@4d142b53[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@3bac86a3[checksumType=HMAC_SHA512, checksumSalt={97,98}, otherChecksumType=], checksumValue={18,52,-52,-52,-52,-52,67,34}, calculationTimestamp=2015-12-04T02:22:57.063+01:00], checksumDataForNewFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@128ca7af[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@3bf52f8f[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2015-12-04T02:22:57.064+01:00]] Step: Retrieve the ProgressResponse for the GetFileIDs request Step: Retrieve the FinalResponse for the ReplaceFile request Test success: goodCaseOperationWithChecksumsReturn Starting testcase ArchiveDirectoryTest Test starting: testArchiveDirectoryExistingFile Description: Test the ArchiveDirectory when the file exists Step: Setup Step: Validate the existence of the file Step: Delete the file. Test success: testArchiveDirectoryExistingFile Test starting: testArchiveDirectoryMissingFile Description: Test the ArchiveDirectory when the file is missing. Step: Setup Step: Validate the existence of the file Step: Delete the file. Test success: testArchiveDirectoryMissingFile Test starting: testArchiveDirectoryMoveFileToArchive Description: Testing the error scenarios when moving a file from tmp to archive for the ArchiveDirectory. Step: Setup Step: Moving file from tmp to archive Step: Create file in both tmp and archive. Step: Moving file from tmp to archive Step: Remove the file from archive and try again Test success: testArchiveDirectoryMoveFileToArchive Test starting: testArchiveDirectoryNewFile Description: Testing the ArchiveDirectory handling of a new file. Step: Setup Step: Retrieve tmp file Step: Request a new file for the tmp dir Step: Retrieve tmp file Step: Request another new file with the same name Step: Move the file from tmp to archive Test success: testArchiveDirectoryNewFile Test starting: testArchiveDirectoryRemoveFile Description: Testing the error scenarios when removing files from the archive. Step: Setup Step: Remove nonexisting file from archive Step: Remove nonexisting file from tmp Step: Create file in both tmp, archive and retain directories. Step: Remove the file from archive and tmp Test success: testArchiveDirectoryRemoveFile Starting testcase ChecksumDatabaseMigrationTest Test starting: testMigratingDatabaseChecksumsTable Description: Tests that the checksums table can be migrated from version 1 to 2, e.g. getting the column collectionid, which should be set to the default in settings. Step: Validate setup Step: Ingest a entry to the database without the collection id Step: Perform migration 02:22:59.008 WARN o.b.service.database.DatabaseUtils - Migrating the checksums table from version 1 to 2 in the ChecksumDatabase. 02:22:59.107 WARN o.b.service.database.DatabaseUtils - Migrating ChecksumDB from version 2 to 3. Step: Validate the entry Test success: testMigratingDatabaseChecksumsTable Starting testcase ChecksumPillarModelTest Test starting: testPillarModelBasicFunctionality Description: Test the basic functions of the full reference pillar model. Step: Check the pillar id in the pillar model Step: Ask whether it can handle a file of size 0 Step: Ask whether it can handle a file of maximum size Step: Check the ChecksumPillarSpec Step: Checkum whether the checksum pillar should download Test success: testPillarModelBasicFunctionality Test starting: testPillarModelHasFile Description: Test that the file exists, when placed in the archive and cache Step: Setup Step: Check whether file exists and retrieve it. Step: Check whether file exists. Step: Ask for the checksum data for the file with different checksum specs Step: Ask for the checksum entry for the file with different checksum specs Step: Ask for the checksum for the file with different checksum specs Step: Check extraction of checksum result set Step: Check retrieval of non-default checksum Step: Check retrieval of non-default checksum result set Step: Test retrieval of single checksum result set Test success: testPillarModelHasFile Test starting: testPillarModelNoFile Description: Test that the file exists, when placed in the archive and cache Step: Setup Step: Check whether file exists and try to retrieve it. Step: Verify that anexceptions are thrown when verifying file existance. Test success: testPillarModelNoFile Starting testcase GeneralMessageHandlingTest Added fixture: Initialize a new Pillar. Test starting: testPillarMessageHandler Description: Test the handling of the PillarMessageHandler super-class. Step: Setup Step: Test the pillar ID Test success: testPillarMessageHandler Starting testcase GetAuditTrailsTest Added fixture: Initialize a new Pillar. Test starting: checksumPillarGetAuditTrailsMaximumNumberOfResults Description: Tests the GetAuditTrails functionality of the pillar for the successful scenario, where a limited number of audit trails are requested. Step: Set up constants and variables. Step: Send the request for the limited amount of audit trails to the pillar. Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsMaximumNumberOfResults-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsProgressResponse@5e781b4f[correlationID=5a9b0cef-058f-4d10-84ba-c6cb56853638, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsMaximumNumberOfResults-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults, to=Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@1b89debc[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to extract the requested audit trails.], contributor=Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults, resultAddress=] Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsMaximumNumberOfResults-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsFinalResponse@17810908[correlationID=5a9b0cef-058f-4d10-84ba-c6cb56853638, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsMaximumNumberOfResults-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults, to=Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@174d5cf7[responseCode=OPERATION_COMPLETED, responseText=], contributor=Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@597eb9ac[resultAddress=, auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@65c66fc4[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@7a90f33d[sequenceNumber=1, fileID=fileId1449192179754, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=CHECKSUM_CALCULATED, actionDateTime=2015-12-04T02:22:59.754+01:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@7c7b27c[sequenceNumber=2, fileID=fileId1449192179754, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=DELETE_FILE, actionDateTime=2015-12-04T02:22:59.754+01:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@2bd8c8f1[sequenceNumber=3, fileID=fileId1449192179754, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=FAILURE, actionDateTime=2015-12-04T02:22:59.754+01:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@7db63a01[sequenceNumber=4, fileID=fileId1449192179754, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=FILE_MOVED, actionDateTime=2015-12-04T02:22:59.754+01:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@423791[sequenceNumber=5, fileID=fileId1449192179754, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=GET_CHECKSUMS, actionDateTime=2015-12-04T02:22:59.754+01:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails]}]], partialResult=true] Step: Validate the final response Test success: checksumPillarGetAuditTrailsMaximumNumberOfResults Added fixture: Initialize a new Pillar. Test starting: checksumPillarGetAuditTrailsSpecificRequests Description: Tests the GetAuditTrails functionality of the pillar for the successful scenario, where a specific audit trail are requested. Step: Set up constants and variables. Step: Send the identification request Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsResponse@500beb9f[correlationID=65f06741-1ea4-4bd3-8c72-0d90c17e97bc, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSpecificRequests-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSpecificRequests, to=Pillar-checksumPillarGetAuditTrailsSpecificRequests, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@67e37d25[responseCode=IDENTIFICATION_POSITIVE, responseText=]] Step: Retrieve and validate the response. Step: Make and send the request for the actual GetAuditTrails operation Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsProgressResponse@21f27bb5[correlationID=65f06741-1ea4-4bd3-8c72-0d90c17e97bc, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSpecificRequests-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSpecificRequests, to=Pillar-checksumPillarGetAuditTrailsSpecificRequests, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@2e2a2b07[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to extract the requested audit trails.], contributor=Pillar-checksumPillarGetAuditTrailsSpecificRequests, resultAddress=] Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsFinalResponse@52dc71b2[correlationID=65f06741-1ea4-4bd3-8c72-0d90c17e97bc, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSpecificRequests-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSpecificRequests, to=Pillar-checksumPillarGetAuditTrailsSpecificRequests, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@e1d2781[responseCode=OPERATION_COMPLETED, responseText=], contributor=Pillar-checksumPillarGetAuditTrailsSpecificRequests, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@3c00da24[resultAddress=, auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@430dbcb0[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@726d0482[sequenceNumber=1, fileID=fileId1449192179899, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=OTHER, actionDateTime=2015-12-04T02:22:59.899+01:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails]}]], partialResult=false] Step: Receive and validate the progress response. Step: Receive and validate the final response Step: Make another request, where both ingested audit trails is requested Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsProgressResponse@15ab0461[correlationID=65f06741-1ea4-4bd3-8c72-0d90c17e97bc, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSpecificRequests-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSpecificRequests, to=Pillar-checksumPillarGetAuditTrailsSpecificRequests, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@2f403d0a[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to extract the requested audit trails.], contributor=Pillar-checksumPillarGetAuditTrailsSpecificRequests, resultAddress=] Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsFinalResponse@186fc6e[correlationID=65f06741-1ea4-4bd3-8c72-0d90c17e97bc, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSpecificRequests-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSpecificRequests, to=Pillar-checksumPillarGetAuditTrailsSpecificRequests, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@1bd5b1c8[responseCode=OPERATION_COMPLETED, responseText=], contributor=Pillar-checksumPillarGetAuditTrailsSpecificRequests, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@569026df[resultAddress=, auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@7896e96a[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@726d0482[sequenceNumber=1, fileID=fileId1449192179899, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=OTHER, actionDateTime=2015-12-04T02:22:59.899+01:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@4e451f9a[sequenceNumber=2, fileID=notThisFile, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=UnknownActor, actionOnFile=FAILURE, actionDateTime=2015-12-04T02:22:59.899+01:00, info=badInfo, operationID=operationID, certificateID=certificateid, auditTrailInformation=WrongAuditTrail]}]], partialResult=false] Step: Receive and validate the progress response. Step: Receive and validate the final response Test success: checksumPillarGetAuditTrailsSpecificRequests Added fixture: Initialize a new Pillar. Test starting: checksumPillarGetAuditTrailsSuccessful Description: Tests the GetAuditTrails functionality of the pillar for the successful scenario, where all audit trails are requested. Step: Set up constants and variables. Step: Send the identification request Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSuccessful-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsResponse@7375ebe7[correlationID=82c920ee-9a0f-4104-b6f9-d3bc64c604a1, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSuccessful-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSuccessful-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSuccessful, to=Pillar-checksumPillarGetAuditTrailsSuccessful, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@16a7af5d[responseCode=IDENTIFICATION_POSITIVE, responseText=]] Step: Make and send the request for the actual GetAuditTrails operation Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSuccessful-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsProgressResponse@207358ad[correlationID=82c920ee-9a0f-4104-b6f9-d3bc64c604a1, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSuccessful-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSuccessful-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSuccessful, to=Pillar-checksumPillarGetAuditTrailsSuccessful, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@3e2ee637[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to extract the requested audit trails.], contributor=Pillar-checksumPillarGetAuditTrailsSuccessful, resultAddress=] Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSuccessful-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsFinalResponse@62d818c6[correlationID=82c920ee-9a0f-4104-b6f9-d3bc64c604a1, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSuccessful-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSuccessful-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSuccessful, to=Pillar-checksumPillarGetAuditTrailsSuccessful, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@492e9e87[responseCode=OPERATION_COMPLETED, responseText=], contributor=Pillar-checksumPillarGetAuditTrailsSuccessful, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@7322013f[resultAddress=, auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@3a744e32[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@18487f92[sequenceNumber=1, fileID=fileid, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=actor, actionOnFile=OTHER, actionDateTime=2015-12-04T02:23:00.050+01:00, info=info, operationID=operationID, certificateID=certificateID, auditTrailInformation=auditTrail]}]], partialResult=false] Step: Receive and validate the progress response. Step: Receive and validate the final response Test success: checksumPillarGetAuditTrailsSuccessful Starting testcase RecalculateChecksumWorkflowTest Added fixture: Initialize the Reference pillar cache with an empty file in default collection TwoPillarCollection Test starting: testWorkflowDoesNotRecalculateWhenNotNeeded Description: Test that the workflow does not recalculates the workflows, when the maximum age has not yet been met. Step: Create and run workflow Test success: testWorkflowDoesNotRecalculateWhenNotNeeded Added fixture: Initialize the Reference pillar cache with an empty file in default collection TwoPillarCollection Test starting: testWorkflowRecalculatesChecksum Description: Test that the workflow recalculates the workflows, when the maximum age has been met. Step: Create and run workflow Test success: testWorkflowRecalculatesChecksum Test starting: getPillarCollectionsTest Test success: getPillarCollectionsTest Starting testcase DeleteFileTest Added fixture: Initialize a new Pillar. Test starting: badCaseIdentification Description: Tests the identification for a DeleteFile operation on the checksum pillar for the failure scenario, when the file is missing. Step: Set up constants and variables. Step: Setup for delivering pillar id and not having the file Step: Create and send the identify request message. Result: Received message on TEST-TOPIC-badCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileResponse@1872a7fe[correlationID=0fc947ef-b348-41e1-9332-6cf3a28fd655, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseIdentification-cibuild01-contributor, from=Pillar-badCaseIdentification, to=badCaseIdentification, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@70720b78[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], fileID=DefaultFilebadCaseIdentification, pillarID=Pillar-badCaseIdentification, pillarChecksumSpec=, timeToDeliver=] Step: Retrieve and validate the response getPillarID() the pillar. Test success: badCaseIdentification Added fixture: Initialize a new Pillar. Test starting: badCaseOperationMissingVerification Description: Tests the DeleteFile functionality of the pillar for the failure scenario, where it does not have the file. Step: Set up constants and variables. Step: Setup for delivering pillar id and having the file Step: Create and send the actual DeleteFile message to the pillar. Result: Received message on TEST-TOPIC-badCaseOperationMissingVerification-cibuild01 : org.bitrepository.bitrepositorymessages.DeleteFileFinalResponse@ac71bd7[correlationID=607d6f21-3981-47bc-9a99-44db5d8a87d8, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationMissingVerification-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationMissingVerification-cibuild01-contributor, from=Pillar-badCaseOperationMissingVerification, to=badCaseOperationMissingVerification, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@64e6cdad[responseCode=EXISTING_FILE_CHECKSUM_FAILURE, responseText=No mandatory checksum for destructive operation was supplied.], pillarID=Pillar-badCaseOperationMissingVerification, fileID=DefaultFilebadCaseOperationMissingVerification, checksumDataForExistingFile=] 02:23:01.834 WARN o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@2c5e2a44[origDateTime=2015-12-04T02:23:01.834+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCaseOperationMissingVerification, alarmText=No mandatory checksum for destructive operation was supplied., fileID=DefaultFilebadCaseOperationMissingVerification, collectionID=TwoPillarCollection] Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@1ef585bb[correlationID=6289fbe8-6a91-4ec5-acb8-ee547527cd95, collectionID=TwoPillarCollection, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationMissingVerification-cibuild01-contributor, from=Pillar-badCaseOperationMissingVerification, to=, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@2c5e2a44[origDateTime=2015-12-04T02:23:01.834+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCaseOperationMissingVerification, alarmText=No mandatory checksum for destructive operation was supplied., fileID=DefaultFilebadCaseOperationMissingVerification, collectionID=TwoPillarCollection]] Step: Retrieve the FinalResponse for the DeleteFile request Step: Pillar should have sent an alarm Test success: badCaseOperationMissingVerification Added fixture: Initialize a new Pillar. Test starting: badCaseOperationNoFile Description: Tests the DeleteFile functionality of the pillar for the failure scenario, where it does not have the file. Step: Set up constants and variables. Step: Setup for delivering pillar id and not having the file Step: Create and send the actual DeleteFile message to the pillar. Result: Received message on TEST-TOPIC-badCaseOperationNoFile-cibuild01 : org.bitrepository.bitrepositorymessages.DeleteFileFinalResponse@4f7a2262[correlationID=5d61f2f4-0ba9-406b-b43c-3b5c2b098ab3, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@4a577b99[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileID=DefaultFilebadCaseOperationNoFile, checksumDataForExistingFile=] Result: Received message on TEST-TOPIC-badCaseOperationNoFile-cibuild01 : org.bitrepository.bitrepositorymessages.DeleteFileFinalResponse@4eb313ed[correlationID=5d61f2f4-0ba9-406b-b43c-3b5c2b098ab3, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@3fc92211[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileID=DefaultFilebadCaseOperationNoFile, checksumDataForExistingFile=] Result: Received message on TEST-TOPIC-badCaseOperationNoFile-cibuild01 : org.bitrepository.bitrepositorymessages.DeleteFileFinalResponse@117bfeb8[correlationID=5d61f2f4-0ba9-406b-b43c-3b5c2b098ab3, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@4781bb01[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileID=DefaultFilebadCaseOperationNoFile, checksumDataForExistingFile=] Step: Retrieve the FinalResponse for the DeleteFile request Test success: badCaseOperationNoFile Result: The following messages haven't been handled by the testcase: org.bitrepository.bitrepositorymessages.DeleteFileFinalResponse@4eb313ed[correlationID=5d61f2f4-0ba9-406b-b43c-3b5c2b098ab3, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@3fc92211[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileID=DefaultFilebadCaseOperationNoFile, checksumDataForExistingFile=] org.bitrepository.bitrepositorymessages.DeleteFileFinalResponse@117bfeb8[correlationID=5d61f2f4-0ba9-406b-b43c-3b5c2b098ab3, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@4781bb01[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileID=DefaultFilebadCaseOperationNoFile, checksumDataForExistingFile=] 02:23:02.944 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: org.bitrepository.bitrepositorymessages.DeleteFileFinalResponse@4eb313ed[correlationID=5d61f2f4-0ba9-406b-b43c-3b5c2b098ab3, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@3fc92211[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileID=DefaultFilebadCaseOperationNoFile, checksumDataForExistingFile=] org.bitrepository.bitrepositorymessages.DeleteFileFinalResponse@117bfeb8[correlationID=5d61f2f4-0ba9-406b-b43c-3b5c2b098ab3, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@4781bb01[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileID=DefaultFilebadCaseOperationNoFile, checksumDataForExistingFile=] Added fixture: Initialize a new Pillar. Test starting: goodCaseIdentification Description: Tests the identification for a DeleteFile operation on the pillar for the successful scenario. Step: Set up constants and variables. Step: Setup for having the file and delivering pillar id Step: Create and send the identify request message. Result: Received message on TEST-TOPIC-goodCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileResponse@41fbe8c0[correlationID=3b789624-f0cd-4d3d-9aa8-103f2821f338, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseIdentification-cibuild01-contributor, from=Pillar-goodCaseIdentification, to=goodCaseIdentification, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@1e8fd198[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], fileID=DefaultFilegoodCaseIdentification, pillarID=Pillar-goodCaseIdentification, pillarChecksumSpec=, timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@4f75c627[timeMeasureUnit=MILLISECONDS, timeMeasureValue=1000]] Step: Retrieve and validate the response getPillarID() the pillar. Test success: goodCaseIdentification Starting testcase ReferenceArchiveTest Added fixture: Initialize the Reference pillar cache with an empty file in default collection TwoPillarCollection Test starting: testReferenceArchive Description: Test the ReferenceArchive. Step: Setup Step: test 'hasFile' Step: Test 'getFile' Step: Test getAllFileIDs Step: Test 'getFileAsInputstream' Step: Delete, recreate and delete again Step: Try to delete missing file. Step: Replace a file, which does not exist in the filedir. Step: Copy a file into the tmpDir and then use replace. Step: Try performing the replace, when the file in the tempdir has been removed. Test success: testReferenceArchive Starting testcase GetFileTest Added fixture: Initialize a new Pillar. Test starting: badCaseIdentification Description: Tests the identification for a GetFile operation on the checksum pillar for the failure scenario, when the file is missing. Step: Set up constants and variables. Step: Setup for throwing an exception when asked to verify file existence Step: Create and send the identify request message. Result: Received message on TEST-TOPIC-badCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileResponse@7d2d7a85[correlationID=ee4b7cd7-ca72-4926-8529-3bc5f73521f2, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseIdentification-cibuild01-contributor, from=Pillar-badCaseIdentification, to=badCaseIdentification, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@5cb3c9e6[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], fileID=DefaultFilebadCaseIdentification, pillarID=Pillar-badCaseIdentification, timeToDeliver=] Step: Retrieve and validate the response getPillarID() the pillar. Test success: badCaseIdentification Added fixture: Initialize a new Pillar. Test starting: goodCaseIdentification Description: Tests the identification for a GetFile operation on the pillar for the successful scenario. Step: Set up constants and variables. Step: Setup for having the file and delivering pillar id Step: Create and send the identify request message. Result: Received message on TEST-TOPIC-goodCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileResponse@7f8586f9[correlationID=b078c79f-fec7-49a3-a9e5-b41f63bc768b, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseIdentification-cibuild01-contributor, from=Pillar-goodCaseIdentification, to=goodCaseIdentification, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@248227db[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], fileID=DefaultFilegoodCaseIdentification, pillarID=Pillar-goodCaseIdentification, timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@fb69ab1[timeMeasureUnit=MILLISECONDS, timeMeasureValue=1000]] Step: Retrieve and validate the response getPillarID() the pillar. Test success: goodCaseIdentification Starting testcase MediatorTest Test starting: testMediatorRuntimeExceptionHandling Description: Tests the handling of a runtime exception Step: Setup create and start the mediator. Step: Send a request to the mediator. 02:23:07.740 WARN o.b.pillar.MediatorTest$TestMediator - Unexpected exception caught. java.lang.RuntimeException: I am supposed to throw a RuntimeException at org.bitrepository.pillar.MediatorTest$ErroneousRequestHandler.processRequest(MediatorTest.java:122) ~[test-classes/:na] at org.bitrepository.pillar.MediatorTest$ErroneousRequestHandler.processRequest(MediatorTest.java:113) ~[test-classes/:na] at org.bitrepository.pillar.messagehandler.PillarMediator.handleRequest(PillarMediator.java:76) ~[classes/:na] at org.bitrepository.service.contributor.AbstractContributorMediator$GeneralRequestHandler.onMessage(AbstractContributorMediator.java:101) [bitrepository-service-1.6-SNAPSHOT.jar:1.6-SNAPSHOT] at org.bitrepository.protocol.messagebus.SimpleMessageBus.lambda$sendMessage$0(SimpleMessageBus.java:73) [bitrepository-core-1.6-SNAPSHOT.jar:1.6-SNAPSHOT] at org.bitrepository.protocol.messagebus.SimpleMessageBus$$Lambda$1/2037199851.accept(Unknown Source) [bitrepository-core-1.6-SNAPSHOT.jar:1.6-SNAPSHOT] at java.lang.Iterable.forEach(Iterable.java:75) [na:1.8.0_11] at org.bitrepository.protocol.messagebus.SimpleMessageBus.sendMessage(SimpleMessageBus.java:73) [bitrepository-core-1.6-SNAPSHOT.jar:1.6-SNAPSHOT] at org.bitrepository.pillar.MediatorTest.testMediatorRuntimeExceptionHandling(MediatorTest.java:84) [test-classes/:na] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_11] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_11] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_11] at java.lang.reflect.Method.invoke(Method.java:483) ~[na:1.8.0_11] at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84) [testng-6.8.8.jar:na] at org.testng.internal.Invoker.invokeMethod(Invoker.java:714) [testng-6.8.8.jar:na] at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901) [testng-6.8.8.jar:na] at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231) [testng-6.8.8.jar:na] at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127) [testng-6.8.8.jar:na] at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111) [testng-6.8.8.jar:na] at org.testng.TestRunner.privateRun(TestRunner.java:767) [testng-6.8.8.jar:na] at org.testng.TestRunner.run(TestRunner.java:617) [testng-6.8.8.jar:na] at org.testng.SuiteRunner.runTest(SuiteRunner.java:348) [testng-6.8.8.jar:na] at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:343) [testng-6.8.8.jar:na] at org.testng.SuiteRunner.privateRun(SuiteRunner.java:305) [testng-6.8.8.jar:na] at org.testng.SuiteRunner.run(SuiteRunner.java:254) [testng-6.8.8.jar:na] at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) [testng-6.8.8.jar:na] at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) [testng-6.8.8.jar:na] at org.testng.TestNG.runSuitesSequentially(TestNG.java:1224) [testng-6.8.8.jar:na] at org.testng.TestNG.runSuitesLocally(TestNG.java:1149) [testng-6.8.8.jar:na] at org.testng.TestNG.run(TestNG.java:1057) [testng-6.8.8.jar:na] at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:115) [surefire-testng-2.17.jar:2.17] at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:204) [surefire-testng-2.17.jar:2.17] at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:107) [surefire-testng-2.17.jar:2.17] at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:112) [surefire-testng-2.17.jar:2.17] at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) [surefire-booter-2.17.jar:2.17] at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) [surefire-booter-2.17.jar:2.17] at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) [surefire-booter-2.17.jar:2.17] Result: Received message on TEST-TOPIC-testMediatorRuntimeExceptionHandling-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetStatusResponse@6e1bd2b[correlationID=257cf70b-3b76-415d-9936-b6337e1f7e16, collectionID=TwoPillarCollection, destination=TEST-TOPIC-testMediatorRuntimeExceptionHandling-cibuild01, replyTo=TEST-TOPIC-MediatorUnderTest-cibuild01-contributor, from=MediatorUnderTest, to=MediatorUnderTest, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@18a66406[responseCode=FAILURE, responseText=java.lang.RuntimeException: I am supposed to throw a RuntimeException], contributor=TEST-TOPIC-cibuild01, timeToDeliver=] 02:23:07.742 WARN o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@52364a6e[origDateTime=2015-12-04T02:23:07.742+01:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MediatorUnderTest, alarmText=java.lang.RuntimeException: I am supposed to throw a RuntimeException, fileID=, collectionID=] Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@5935ade6[correlationID=87953666-fe83-47cb-be31-f930c51768f4, collectionID=, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-MediatorUnderTest-cibuild01-contributor, from=MediatorUnderTest, to=, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@52364a6e[origDateTime=2015-12-04T02:23:07.742+01:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MediatorUnderTest, alarmText=java.lang.RuntimeException: I am supposed to throw a RuntimeException, fileID=, collectionID=]] Test success: testMediatorRuntimeExceptionHandling Finished testcase Finished suite Finished project Tests run: 57, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 55.428 sec - in TestSuite Results : Tests run: 57, Failures: 0, Errors: 0, Skipped: 0 [JENKINS] Recording test results [INFO] [INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ bitrepository-reference-pillar --- [INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.6-SNAPSHOT.jar [INFO] [INFO] --- maven-jar-plugin:2.4:test-jar (default) @ bitrepository-reference-pillar --- [INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.6-SNAPSHOT-tests.jar [INFO] [INFO] --- maven-source-plugin:2.2.1:jar-no-fork (attach-sources-no-fork) @ bitrepository-reference-pillar --- [INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.6-SNAPSHOT-sources.jar [INFO] [INFO] --- maven-assembly-plugin:2.4:single (distribution) @ bitrepository-reference-pillar --- [INFO] Reading assembly descriptor: src/main/assembly/assembly.xml [INFO] Reading assembly descriptor: src/test/assembly/assembly.xml [INFO] Reading assembly descriptor: src/main/assembly/deploy-assembly.xml [INFO] Reading assembly descriptor: src/test/assembly/test-deploy-assembly.xml [INFO] Building tar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.6-SNAPSHOT-distribution.tar.gz [INFO] Building tar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.6-SNAPSHOT-acceptance-test.tar.gz [WARNING] Entry: bitrepository-reference-pillar-1.6-SNAPSHOT/lib/bitrepository-reference-pillar-1.6-SNAPSHOT-tests.jar longer than 100 characters. [WARNING] Resulting tar file can only be processed successfully by GNU compatible tar commands [INFO] Building tar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.6-SNAPSHOT-deploy.tar.gz [INFO] Building tar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.6-SNAPSHOT-acceptance-test-deploy.tar.gz [INFO] [INFO] --- maven-install-plugin:2.5.1:install (default-install) @ bitrepository-reference-pillar --- [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.6-SNAPSHOT.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.6-SNAPSHOT/bitrepository-reference-pillar-1.6-SNAPSHOT.jar [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.6-SNAPSHOT/bitrepository-reference-pillar-1.6-SNAPSHOT.pom [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.6-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.6-SNAPSHOT/bitrepository-reference-pillar-1.6-SNAPSHOT-tests.jar [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.6-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.6-SNAPSHOT/bitrepository-reference-pillar-1.6-SNAPSHOT-sources.jar [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.6-SNAPSHOT-distribution.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.6-SNAPSHOT/bitrepository-reference-pillar-1.6-SNAPSHOT-distribution.tar.gz [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.6-SNAPSHOT-acceptance-test.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.6-SNAPSHOT/bitrepository-reference-pillar-1.6-SNAPSHOT-acceptance-test.tar.gz [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.6-SNAPSHOT-deploy.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.6-SNAPSHOT/bitrepository-reference-pillar-1.6-SNAPSHOT-deploy.tar.gz [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.6-SNAPSHOT-acceptance-test-deploy.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.6-SNAPSHOT/bitrepository-reference-pillar-1.6-SNAPSHOT-acceptance-test-deploy.tar.gz [JENKINS] Archiving disabled [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building Bitrepository Monitoring Service 1.6-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-monitoring-service --- [INFO] Deleting /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-monitoring-service/target [INFO] [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ bitrepository-monitoring-service --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-monitoring-service/src/main/resources [INFO] [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ bitrepository-monitoring-service --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 14 source files to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-monitoring-service/target/classes [INFO] [INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ bitrepository-monitoring-service --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-monitoring-service/src/test/resources [INFO] [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ bitrepository-monitoring-service --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 7 source files to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-monitoring-service/target/test-classes [INFO] [INFO] --- maven-surefire-plugin:2.17:test (default-test) @ bitrepository-monitoring-service --- [INFO] Surefire report directory: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-monitoring-service/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 ComponentStatusStoreTest Test starting: testComponentStatus Description: Tests the compontent status Step: Setup Step: Validate the initial content Step: Update the replay counts and validate Step: Test what happens when an invalid component id attempted to be updated. 02:23:16.052 WARN o.b.m.status.ComponentStatusStore - Got status from an unexpected component: BAD-COMPONENT-ID Step: Try giving it a positive status Test success: testComponentStatus Starting testcase StatusEventHandlerTest Test starting: testStatusEventHandler Description: Test the GetStatusEventHandler handling of events Step: Setup Step: Validate initial calls to the mocks Step: Test an unhandled event. Step: Test the Complete event Step: Test the Failed event Step: Test the component complete status Test success: testStatusEventHandler Starting testcase MonitorAlerterTest Test starting: testMonitorAlerter Description: Tests the org.bitrepository.monitoringservice.alarm.BasicMonitoringServiceAlerter Step: Setup Step: Create the alerter, but ignore the part of actually sending the alarms. Just log it. Step: Check statuses with an empty map. Step: Check the status when a positive entry exists. Step: Check the status when a negative entry exists. 02:23:18.669 WARN o.b.m.a.BasicMonitoringServiceAlerter - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@5d908d47[origDateTime=2015-12-04T02:23:18.666+01:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MonitorAlerterUnderTest, alarmText=The following components have become unresponsive: [TestMonitorService], fileID=, collectionID=] Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@79defdc[correlationID=e0ab29ae-3925-4cae-891d-3938b68cd8b8, collectionID=, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-MonitorAlerterUnderTest-cibuild01-contributor, from=MonitorAlerterUnderTest, to=, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@5d908d47[origDateTime=2015-12-04T02:23:18.666+01:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MonitorAlerterUnderTest, alarmText=The following components have become unresponsive: [TestMonitorService], fileID=, collectionID=]] Test success: testMonitorAlerter Starting testcase StatusCollectorTest Test starting: testStatusCollector Description: Tests the status collector. Step: Setup Step: Create the collector Step: Start the collector Step: wait 2 * the interval Step: wait the interval + delay again Test success: testStatusCollector Finished testcase Finished suite Finished project Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 8.058 sec - in TestSuite Results : Tests run: 4, Failures: 0, Errors: 0, Skipped: 0 [JENKINS] Recording test results [INFO] [INFO] --- maven-war-plugin:2.4:war (default-war) @ bitrepository-monitoring-service --- [INFO] Packaging webapp [INFO] Assembling webapp [bitrepository-monitoring-service] in [/home/cibuild01/workspace/Bitrepository-sonar/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.6-SNAPSHOT] [INFO] Processing war project [INFO] Copying webapp resources [/home/cibuild01/workspace/Bitrepository-sonar/bitrepository-monitoring-service/src/main/webapp] [INFO] Webapp assembled in [143 msecs] [INFO] Building war: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.6-SNAPSHOT.war [INFO] [INFO] --- maven-jar-plugin:2.4:test-jar (default) @ bitrepository-monitoring-service --- [INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.6-SNAPSHOT-tests.jar [INFO] [INFO] --- maven-source-plugin:2.2.1:jar-no-fork (attach-sources-no-fork) @ bitrepository-monitoring-service --- [INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.6-SNAPSHOT-sources.jar [INFO] [INFO] --- maven-assembly-plugin:2.4:single (distribution) @ bitrepository-monitoring-service --- [INFO] Reading assembly descriptor: src/main/assembly/assembly.xml [INFO] Building tar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.6-SNAPSHOT-distribution.tar.gz [INFO] [INFO] --- maven-install-plugin:2.5.1:install (default-install) @ bitrepository-monitoring-service --- [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.6-SNAPSHOT.war to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-monitoring-service/1.6-SNAPSHOT/bitrepository-monitoring-service-1.6-SNAPSHOT.war [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-monitoring-service/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-monitoring-service/1.6-SNAPSHOT/bitrepository-monitoring-service-1.6-SNAPSHOT.pom [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.6-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-monitoring-service/1.6-SNAPSHOT/bitrepository-monitoring-service-1.6-SNAPSHOT-tests.jar [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.6-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-monitoring-service/1.6-SNAPSHOT/bitrepository-monitoring-service-1.6-SNAPSHOT-sources.jar [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.6-SNAPSHOT-distribution.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-monitoring-service/1.6-SNAPSHOT/bitrepository-monitoring-service-1.6-SNAPSHOT-distribution.tar.gz [JENKINS] Archiving disabled [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building Bitrepository Webclient 1.6-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-webclient --- [INFO] Deleting /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-webclient/target [INFO] [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ bitrepository-webclient --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 2 resources [INFO] [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ bitrepository-webclient --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 12 source files to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-webclient/target/classes [INFO] [INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ bitrepository-webclient --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-webclient/src/test/resources [INFO] [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ bitrepository-webclient --- [INFO] No sources to compile [INFO] [INFO] --- maven-surefire-plugin:2.17:test (default-test) @ bitrepository-webclient --- [INFO] No tests to run. [JENKINS] Recording test results [INFO] [INFO] --- maven-war-plugin:2.4:war (default-war) @ bitrepository-webclient --- [INFO] Packaging webapp [INFO] Assembling webapp [bitrepository-webclient] in [/home/cibuild01/workspace/Bitrepository-sonar/bitrepository-webclient/target/bitrepository-webclient-1.6-SNAPSHOT] [INFO] Processing war project [INFO] Copying webapp webResources [/home/cibuild01/workspace/Bitrepository-sonar/bitrepository-webclient/src/main/webapp] to [/home/cibuild01/workspace/Bitrepository-sonar/bitrepository-webclient/target/bitrepository-webclient-1.6-SNAPSHOT] [INFO] Copying webapp resources [/home/cibuild01/workspace/Bitrepository-sonar/bitrepository-webclient/src/main/webapp] [INFO] Webapp assembled in [1112 msecs] [INFO] Building war: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-webclient/target/bitrepository-webclient-1.6-SNAPSHOT.war [INFO] [INFO] --- maven-jar-plugin:2.4:test-jar (default) @ bitrepository-webclient --- [WARNING] JAR will be empty - no content was marked for inclusion! [INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-webclient/target/bitrepository-webclient-1.6-SNAPSHOT-tests.jar [INFO] [INFO] --- maven-source-plugin:2.2.1:jar-no-fork (attach-sources-no-fork) @ bitrepository-webclient --- [INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-webclient/target/bitrepository-webclient-1.6-SNAPSHOT-sources.jar [INFO] [INFO] --- maven-assembly-plugin:2.4:single (distribution) @ bitrepository-webclient --- [INFO] Reading assembly descriptor: src/main/assembly/assembly.xml [INFO] Building tar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-webclient/target/bitrepository-webclient-1.6-SNAPSHOT-distribution.tar.gz [INFO] [INFO] --- maven-install-plugin:2.5.1:install (default-install) @ bitrepository-webclient --- [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-webclient/target/bitrepository-webclient-1.6-SNAPSHOT.war to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-webclient/1.6-SNAPSHOT/bitrepository-webclient-1.6-SNAPSHOT.war [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-webclient/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-webclient/1.6-SNAPSHOT/bitrepository-webclient-1.6-SNAPSHOT.pom [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-webclient/target/bitrepository-webclient-1.6-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-webclient/1.6-SNAPSHOT/bitrepository-webclient-1.6-SNAPSHOT-tests.jar [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-webclient/target/bitrepository-webclient-1.6-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-webclient/1.6-SNAPSHOT/bitrepository-webclient-1.6-SNAPSHOT-sources.jar [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-webclient/target/bitrepository-webclient-1.6-SNAPSHOT-distribution.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-webclient/1.6-SNAPSHOT/bitrepository-webclient-1.6-SNAPSHOT-distribution.tar.gz [JENKINS] Archiving disabled [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building Bitrepository Integration 1.6-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-integration --- [INFO] Deleting /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integration/target [INFO] [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ bitrepository-integration --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 33 resources [INFO] [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ bitrepository-integration --- [INFO] No sources to compile [INFO] [INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ bitrepository-integration --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 1 resource [INFO] [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ bitrepository-integration --- [INFO] No sources to compile [INFO] [INFO] --- maven-surefire-plugin:2.17:test (default-test) @ bitrepository-integration --- [JENKINS] Recording test results [INFO] [INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ bitrepository-integration --- [INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integration/target/bitrepository-integration-1.6-SNAPSHOT.jar [INFO] [INFO] --- maven-jar-plugin:2.4:test-jar (default) @ bitrepository-integration --- [INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integration/target/bitrepository-integration-1.6-SNAPSHOT-tests.jar [INFO] [INFO] --- maven-source-plugin:2.2.1:jar-no-fork (attach-sources-no-fork) @ bitrepository-integration --- [INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integration/target/bitrepository-integration-1.6-SNAPSHOT-sources.jar [INFO] [INFO] --- maven-assembly-plugin:2.4:single (make-assembly) @ bitrepository-integration --- [INFO] Reading assembly descriptor: src/main/assembly/assembly.xml [INFO] Reading assembly descriptor: src/main/assembly/tools-assembly.xml [INFO] Building tar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integration/target/bitrepository-integration-1.6-SNAPSHOT-quickstart.tar.gz [INFO] Building tar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integration/target/bitrepository-integration-1.6-SNAPSHOT-tools.tar.gz [WARNING] Entry: bitrepository-integration-1.6-SNAPSHOT/lib/bitrepository-reference-pillar-1.6-SNAPSHOT-distribution.tar.gz longer than 100 characters. [WARNING] Resulting tar file can only be processed successfully by GNU compatible tar commands [INFO] [INFO] --- maven-install-plugin:2.5.1:install (default-install) @ bitrepository-integration --- [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integration/target/bitrepository-integration-1.6-SNAPSHOT.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integration/1.6-SNAPSHOT/bitrepository-integration-1.6-SNAPSHOT.jar [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integration/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integration/1.6-SNAPSHOT/bitrepository-integration-1.6-SNAPSHOT.pom [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integration/target/bitrepository-integration-1.6-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integration/1.6-SNAPSHOT/bitrepository-integration-1.6-SNAPSHOT-tests.jar [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integration/target/bitrepository-integration-1.6-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integration/1.6-SNAPSHOT/bitrepository-integration-1.6-SNAPSHOT-sources.jar [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integration/target/bitrepository-integration-1.6-SNAPSHOT-quickstart.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integration/1.6-SNAPSHOT/bitrepository-integration-1.6-SNAPSHOT-quickstart.tar.gz [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integration/target/bitrepository-integration-1.6-SNAPSHOT-tools.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integration/1.6-SNAPSHOT/bitrepository-integration-1.6-SNAPSHOT-tools.tar.gz [JENKINS] Archiving disabled [JENKINS] Archiving disabled [JENKINS] Archiving disabled [JENKINS] Archiving disabled [JENKINS] Archiving disabled [JENKINS] Archiving disabled [JENKINS] Archiving disabled [JENKINS] Archiving disabled [JENKINS] Archiving disabled [JENKINS] Archiving disabled [JENKINS] Archiving disabled [JENKINS] Archiving disabled [JENKINS] Archiving disabled [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] Bitrepository ..................................... SUCCESS [ 6.547 s] [INFO] Bitrepository Reference Settings .................. SUCCESS [ 12.376 s] [INFO] Bitrepository Core ................................ SUCCESS [ 45.301 s] [INFO] Bitrepository Client .............................. SUCCESS [01:03 min] [INFO] Bitrepository Service ............................. SUCCESS [ 13.047 s] [INFO] Bitrepository Integrity Service ................... SUCCESS [01:35 min] [INFO] Bitrepository Alarm Service ....................... SUCCESS [ 12.830 s] [INFO] Bitrepository Audit Trail Service ................. SUCCESS [ 27.743 s] [INFO] Bitrepository Reference Pillar .................... SUCCESS [01:03 min] [INFO] Bitrepository Monitoring Service .................. SUCCESS [ 12.664 s] [INFO] Bitrepository Webclient ........................... SUCCESS [ 4.663 s] [INFO] Bitrepository Integration ......................... SUCCESS [ 14.795 s] [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 06:21 min [INFO] Finished at: 2015-12-04T02:23:48+01:00 [INFO] Final Memory: 52M/133M [INFO] ------------------------------------------------------------------------ channel stopped [Bitrepository-sonar] $ /home/cibuild01/tools/hudson.tasks.Maven_MavenInstallation/Maven3.2/bin/mvn -f /home/cibuild01/workspace/Bitrepository-sonar/pom.xml -e -B sonar:sonar -Dsonar.jdbc.url=jdbc:postgresql://leda/sonar ******** ******** -Dsonar.host.url=https://sbforge.org/sonar Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=128m; support was removed in 8.0 [INFO] Error stacktraces are turned on. [INFO] Scanning for projects... [INFO] ------------------------------------------------------------------------ [INFO] Reactor Build Order: [INFO] [INFO] Bitrepository [INFO] Bitrepository Reference Settings [INFO] Bitrepository Core [INFO] Bitrepository Client [INFO] Bitrepository Service [INFO] Bitrepository Integrity Service [INFO] Bitrepository Alarm Service [INFO] Bitrepository Audit Trail Service [INFO] Bitrepository Reference Pillar [INFO] Bitrepository Monitoring Service [INFO] Bitrepository Webclient [INFO] Bitrepository Integration [INFO] Downloading: https://sbforge.org/nexus/content/groups/public/org/codehaus/mojo/maven-metadata.xml [INFO] Downloading: https://sbforge.org/nexus/content/groups/public/org/apache/maven/plugins/maven-metadata.xml [INFO] Downloaded: https://sbforge.org/nexus/content/groups/public/org/apache/maven/plugins/maven-metadata.xml (14 KB at 8.1 KB/sec) [INFO] Downloaded: https://sbforge.org/nexus/content/groups/public/org/codehaus/mojo/maven-metadata.xml (24 KB at 10.6 KB/sec) [INFO] Downloading: https://sbforge.org/nexus/content/groups/public/org/codehaus/mojo/sonar-maven-plugin/maven-metadata.xml [INFO] Downloaded: https://sbforge.org/nexus/content/groups/public/org/codehaus/mojo/sonar-maven-plugin/maven-metadata.xml (892 B at 0.9 KB/sec) [INFO] [INFO] Using the builder org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder with a thread count of 1 [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building Bitrepository 1.6-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- sonar-maven-plugin:2.7.1:sonar (default-cli) @ bitrepository-parent --- [INFO] User cache: /home/cibuild01/.sonar/cache [INFO] SonarQube version: 4.4 [INFO] Default locale: "en_US", source code encoding: "UTF-8" [INFO] [02:24:10.187] Load global settings [INFO] [02:24:10.380] User cache: /home/cibuild01/.sonar/cache [INFO] [02:24:10.407] Install plugins [INFO] [02:24:11.361] Install JDBC driver [INFO] [02:24:11.381] Create JDBC datasource for jdbc:postgresql://leda/sonar [INFO] [02:24:11.624] Initializing Hibernate [ERROR] [02:24:18.341] Invalid value of sonar.sources for org.bitrepository.reference:bitrepository-reference-settings [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] Bitrepository ..................................... FAILURE [ 18.786 s] [INFO] Bitrepository Reference Settings .................. SKIPPED [INFO] Bitrepository Core ................................ SKIPPED [INFO] Bitrepository Client .............................. SKIPPED [INFO] Bitrepository Service ............................. SKIPPED [INFO] Bitrepository Integrity Service ................... SKIPPED [INFO] Bitrepository Alarm Service ....................... SKIPPED [INFO] Bitrepository Audit Trail Service ................. SKIPPED [INFO] Bitrepository Reference Pillar .................... SKIPPED [INFO] Bitrepository Monitoring Service .................. SKIPPED [INFO] Bitrepository Webclient ........................... SKIPPED [INFO] Bitrepository Integration ......................... SKIPPED [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 26.831 s [INFO] Finished at: 2015-12-04T02:24:18+01:00 [INFO] Final Memory: 25M/68M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.codehaus.mojo:sonar-maven-plugin:2.7.1:sonar (default-cli) on project bitrepository-parent: The folder '/home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-settings/pom.xml' does not exist for 'org.bitrepository.reference:bitrepository-reference-settings' (base directory = /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-settings) -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.codehaus.mojo:sonar-maven-plugin:2.7.1:sonar (default-cli) on project bitrepository-parent: The folder '/home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-settings/pom.xml' does not exist for 'org.bitrepository.reference:bitrepository-reference-settings' (base directory = /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-settings) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:108) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:76) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:116) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:361) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:213) at org.apache.maven.cli.MavenCli.main(MavenCli.java:157) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) Caused by: org.apache.maven.plugin.MojoExecutionException: The folder '/home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-settings/pom.xml' does not exist for 'org.bitrepository.reference:bitrepository-reference-settings' (base directory = /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-settings) at org.codehaus.mojo.sonar.bootstrap.ExceptionHandling.handle(ExceptionHandling.java:41) at org.codehaus.mojo.sonar.bootstrap.RunnerBootstrapper.execute(RunnerBootstrapper.java:104) at org.codehaus.mojo.sonar.SonarMojo.execute(SonarMojo.java:135) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:133) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) ... 19 more Caused by: java.lang.IllegalStateException: The folder '/home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-settings/pom.xml' does not exist for 'org.bitrepository.reference:bitrepository-reference-settings' (base directory = /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-settings) at org.sonar.batch.scan.ProjectReactorBuilder.checkExistenceOfDirectories(ProjectReactorBuilder.java:423) at org.sonar.batch.scan.ProjectReactorBuilder.cleanAndCheckModuleProperties(ProjectReactorBuilder.java:336) at org.sonar.batch.scan.ProjectReactorBuilder.cleanAndCheckProjectDefinitions(ProjectReactorBuilder.java:319) at org.sonar.batch.scan.ProjectReactorBuilder.cleanAndCheckProjectDefinitions(ProjectReactorBuilder.java:325) at org.sonar.batch.scan.ProjectReactorBuilder.execute(ProjectReactorBuilder.java:117) at org.sonar.batch.scan.ProjectScanContainer.projectBootstrap(ProjectScanContainer.java:114) at org.sonar.batch.scan.ProjectScanContainer.doBeforeStart(ProjectScanContainer.java:92) at org.sonar.api.platform.ComponentContainer.startComponents(ComponentContainer.java:90) at org.sonar.api.platform.ComponentContainer.execute(ComponentContainer.java:77) at org.sonar.batch.scan.ScanTask.scan(ScanTask.java:64) at org.sonar.batch.scan.ScanTask.execute(ScanTask.java:51) at org.sonar.batch.bootstrap.TaskContainer.doAfterStart(TaskContainer.java:110) at org.sonar.api.platform.ComponentContainer.startComponents(ComponentContainer.java:92) at org.sonar.api.platform.ComponentContainer.execute(ComponentContainer.java:77) at org.sonar.batch.bootstrap.BootstrapContainer.executeTask(BootstrapContainer.java:185) at org.sonar.batch.bootstrapper.Batch.executeTask(Batch.java:95) at org.sonar.batch.bootstrapper.Batch.execute(Batch.java:67) at org.sonar.runner.batch.BatchIsolatedLauncher.executeOldVersion(BatchIsolatedLauncher.java:92) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.sonar.runner.impl.IsolatedLauncherProxy.invoke(IsolatedLauncherProxy.java:61) at com.sun.proxy.$Proxy21.executeOldVersion(Unknown Source) at org.sonar.runner.api.EmbeddedRunner.doExecute(EmbeddedRunner.java:284) at org.sonar.runner.api.EmbeddedRunner.runAnalysis(EmbeddedRunner.java:166) at org.sonar.runner.api.EmbeddedRunner.runAnalysis(EmbeddedRunner.java:153) at org.codehaus.mojo.sonar.bootstrap.RunnerBootstrapper.execute(RunnerBootstrapper.java:99) ... 22 more [ERROR] [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException SonarQube analysis completed: FAILURE Build step 'SonarQube' changed build result to FAILURE Build step 'SonarQube' marked build as failure Sending e-mails to: ktc@statsbiblioteket.dk abr@statsbiblioteket.dk jolf@kb.dk Finished: FAILURE