SuccessConsole Output

Started by GitHub push by sbktc
Building remotely on Local activeMQ in workspace /home/cibuild01/workspace/Bitrepository-reference-test
 > 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 d677217d1bf023ebd601d17b8b7b77389cb1f69c (refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f d677217d1bf023ebd601d17b8b7b77389cb1f69c
 > git rev-list 2140ecc9f7d1bc3da0e61fbb33772461f7089dbd # timeout=10
 > git tag -a -f -m Jenkins Build #5880 jenkins-Bitrepository-reference-test-5880 # timeout=10
Parsing POMs
Established TCP socket on 37102
maven32-agent.jar already up to date
maven32-interceptor.jar already up to date
maven3-interceptor-commons.jar already up to date
[Bitrepository-reference-test] $ /home/cibuild01/tools/hudson.model.JDK/Java8/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.2.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 37102
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-reference-test/pom.xml clean deploy
[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] ------------------------------------------------------------------------
[INFO] Building Bitrepository 1.10-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-parent ---
[INFO] Deleting /home/cibuild01/workspace/Bitrepository-reference-test/target
[INFO] 
[INFO] --- jacoco-maven-plugin:0.7.5.201505241946:prepare-agent (default) @ bitrepository-parent ---
[INFO] argLine set to -javaagent:/home/cibuild01/.m2/repository/org/jacoco/org.jacoco.agent/0.7.5.201505241946/org.jacoco.agent-0.7.5.201505241946-runtime.jar=destfile=/home/cibuild01/workspace/Bitrepository-reference-test/target/jacoco.exec
[INFO] 
[INFO] --- jacoco-maven-plugin:0.7.5.201505241946:report (report) @ bitrepository-parent ---
[INFO] Skipping JaCoCo execution due to missing execution data file:/home/cibuild01/workspace/Bitrepository-reference-test/target/jacoco.exec
[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-reference-test/target/bitrepository-parent-1.10-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-reference-test/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-parent/1.10-SNAPSHOT/bitrepository-parent-1.10-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/target/bitrepository-parent-1.10-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-parent/1.10-SNAPSHOT/bitrepository-parent-1.10-SNAPSHOT-tests.jar
[INFO] 
[INFO] --- maven-deploy-plugin:2.8.1:deploy (default-deploy) @ bitrepository-parent ---
[INFO] Downloading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-parent/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-parent/1.10-SNAPSHOT/maven-metadata.xml (833 B at 1.0 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-parent/1.10-SNAPSHOT/bitrepository-parent-1.10-20170608.132535-5.pom
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-parent/1.10-SNAPSHOT/bitrepository-parent-1.10-20170608.132535-5.pom (18 KB at 69.2 KB/sec)
[INFO] Downloading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-parent/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-parent/maven-metadata.xml (489 B at 10.2 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-parent/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-parent/1.10-SNAPSHOT/maven-metadata.xml (833 B at 5.2 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-parent/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-parent/maven-metadata.xml (489 B at 7.8 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-parent/1.10-SNAPSHOT/bitrepository-parent-1.10-20170608.132535-5-tests.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-parent/1.10-SNAPSHOT/bitrepository-parent-1.10-20170608.132535-5-tests.jar (5 KB at 77.7 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-parent/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-parent/1.10-SNAPSHOT/maven-metadata.xml (833 B at 16.0 KB/sec)
[JENKINS] Archiving disabled
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Reference Settings 1.10-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-reference-settings ---
[INFO] Deleting /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-settings/target
[INFO] 
[INFO] --- jacoco-maven-plugin:0.7.5.201505241946:prepare-agent (default) @ bitrepository-reference-settings ---
[INFO] argLine set to -javaagent:/home/cibuild01/.m2/repository/org/jacoco/org.jacoco.agent/0.7.5.201505241946/org.jacoco.agent-0.7.5.201505241946-runtime.jar=destfile=/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-settings/target/jacoco.exec
[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-reference-test/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-reference-test/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] --- jacoco-maven-plugin:0.7.5.201505241946:report (report) @ bitrepository-reference-settings ---
[INFO] Skipping JaCoCo execution due to missing execution data file:/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-settings/target/jacoco.exec
[INFO] 
[INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ bitrepository-reference-settings ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-settings/target/bitrepository-reference-settings-1.10-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-reference-test/bitrepository-reference-settings/target/bitrepository-reference-settings-1.10-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-reference-test/bitrepository-reference-settings/target/bitrepository-reference-settings-1.10-SNAPSHOT-sources.jar
[INFO] 
[INFO] --- maven-install-plugin:2.5.1:install (default-install) @ bitrepository-reference-settings ---
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-settings/target/bitrepository-reference-settings-1.10-SNAPSHOT.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-settings/1.10-SNAPSHOT/bitrepository-reference-settings-1.10-SNAPSHOT.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-settings/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-settings/1.10-SNAPSHOT/bitrepository-reference-settings-1.10-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-settings/target/bitrepository-reference-settings-1.10-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-settings/1.10-SNAPSHOT/bitrepository-reference-settings-1.10-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-settings/target/bitrepository-reference-settings-1.10-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-settings/1.10-SNAPSHOT/bitrepository-reference-settings-1.10-SNAPSHOT-sources.jar
[INFO] 
[INFO] --- maven-deploy-plugin:2.8.1:deploy (default-deploy) @ bitrepository-reference-settings ---
[INFO] Downloading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-settings/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-settings/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 7.6 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-settings/1.10-SNAPSHOT/bitrepository-reference-settings-1.10-20170608.132548-5.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-settings/1.10-SNAPSHOT/bitrepository-reference-settings-1.10-20170608.132548-5.jar (97 KB at 1015.0 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-settings/1.10-SNAPSHOT/bitrepository-reference-settings-1.10-20170608.132548-5.pom
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-settings/1.10-SNAPSHOT/bitrepository-reference-settings-1.10-20170608.132548-5.pom (5 KB at 70.2 KB/sec)
[INFO] Downloading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-settings/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-settings/maven-metadata.xml (419 B at 13.2 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-settings/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-settings/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 22.7 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-settings/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-settings/maven-metadata.xml (419 B at 9.1 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-settings/1.10-SNAPSHOT/bitrepository-reference-settings-1.10-20170608.132548-5-tests.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-settings/1.10-SNAPSHOT/bitrepository-reference-settings-1.10-20170608.132548-5-tests.jar (3 KB at 33.8 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-settings/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-settings/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 20.4 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-settings/1.10-SNAPSHOT/bitrepository-reference-settings-1.10-20170608.132548-5-sources.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-settings/1.10-SNAPSHOT/bitrepository-reference-settings-1.10-20170608.132548-5-sources.jar (84 KB at 1422.9 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-settings/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-settings/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 19.1 KB/sec)
[JENKINS] Archiving disabled
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Core 1.10-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-core ---
[INFO] Deleting /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-core/target
[INFO] 
[INFO] --- jacoco-maven-plugin:0.7.5.201505241946:prepare-agent (default) @ bitrepository-core ---
[INFO] argLine set to -javaagent:/home/cibuild01/.m2/repository/org/jacoco/org.jacoco.agent/0.7.5.201505241946/org.jacoco.agent-0.7.5.201505241946-runtime.jar=destfile=/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-core/target/jacoco.exec
[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 91 source files to /home/cibuild01/workspace/Bitrepository-reference-test/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 66 source files to /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-core/target/test-classes
[WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-core/src/test/java/org/bitrepository/common/DefaultThreadFactoryTest.java: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-core/src/test/java/org/bitrepository/common/DefaultThreadFactoryTest.java uses unchecked or unsafe operations.
[WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-core/src/test/java/org/bitrepository/common/DefaultThreadFactoryTest.java: Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-surefire-plugin:2.17:test (default-test) @ bitrepository-core ---
[INFO] Surefire report directory: /home/cibuild01/workspace/Bitrepository-reference-test/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 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
      Test starting: testUncaughtExceptionHandler
15:26:05.865 ERROR o.b.common.DefaultThreadFactoryTest - UncaughtExceptionHandler caught Exception:
java.lang.RuntimeException: Hey this is the message I want to see
	at org.bitrepository.common.DefaultThreadFactoryTest.lambda$testUncaughtExceptionHandler$0(DefaultThreadFactoryTest.java:50)
	at java.lang.Thread.run(Thread.java:745)
      Test success: testUncaughtExceptionHandler
    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
    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 FileUtilsTest
      Test starting: cleanupEmptyDirectoriesTester
        Description: Test the cleanup of empty directories.
        Step: Cleanup non-empty folder
        Step: Cleanup when dir and root are the same
        Step: Test succes case, when the directory is empty
        Step: Test with a file.
      Test success: cleanupEmptyDirectoriesTester
      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 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 MultiThreadedMessageBusTest
15:26:07.513 WARN  o.a.activemq.broker.BrokerService - Memory Usage for the Broker (1024mb) is more than the maximum available for the JVM: 444 mb - resetting to 70% of maximum available: 311 mb
15:26:08.737 WARN  o.a.activemq.broker.BrokerService - Temporary Store limit is 51200 mb (current store usage is 0 mb). The data directory: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-core/target only has 6787 mb of usable space. - resetting to maximum available disk space: 6787 mb
      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@7a0619a8[correlationID=12345, collectionID=MySla, destination=BusActivityTest, replyTo=topic://clientTopic, from=ClientPillar, to=<null>(default), version=29, minVersion=24, auditTrailInformation=User: Name, Institution: Place, fileID=MyDataID]
          Stimuli: Sending message: org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileRequest@7a0619a8[correlationID=12345, collectionID=MySla, destination=BusActivityTest, replyTo=topic://clientTopic, from=ClientPillar, to=<null>(default), version=29, minVersion=24, auditTrailInformation=User: Name, Institution: Place, fileID=MyDataID]
          Stimuli: Sending message: org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileRequest@7a0619a8[correlationID=12345, collectionID=MySla, destination=BusActivityTest, replyTo=topic://clientTopic, from=ClientPillar, to=<null>(default), version=29, minVersion=24, auditTrailInformation=User: Name, Institution: Place, fileID=MyDataID]
      Test success: manyTheadsBeforeFinish
    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 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 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 PUT_FILE is allowed for both collections.
        Step: Check that GET_FILE is only allowed for the first collection.
      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 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 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 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 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 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: endDateRolloverTest
        Description: Test that the end date is correctly rolls over a year and month change.
      Test success: endDateRolloverTest
      Test starting: endDateTest
        Description: Test that the end date is considered as localtime and converted into UTC.
      Test success: endDateTest
      Test starting: startDateTest
        Description: Test that the start date is considered as localtime and converted into UTC.
      Test success: startDateTest
      Test starting: testBeginningOfDay
        Description: Tests that the time is converted to the beginning of the day localtime, not UTC
expectedSTartofDayInUTC parsed: 1454281200000
      Test success: testBeginningOfDay
      Test starting: testEndOfDay
        Description: Tests that the time is converted to the beginning of the day localtime, not UTC
      Test success: testEndOfDay
      Test starting: testSummerWinterTimeChange
        Description: Test that the interval between start and end date on a summertime to wintertime change is 25 hours (-1 millisecond).
      Test success: testSummerWinterTimeChange
      Test starting: testWinterSummerTimeChange
        Description: Test that the interval between start and end date on a wintertime to summertime change is 23 hours (-1 millisecond).
      Test success: testWinterSummerTimeChange
    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 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 MessageCreationTest
      Test starting: badDateMessageTest
        Description: Test to ensure that messages carrying dates must provide offset.
      Test success: badDateMessageTest
      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 SettingsLoaderTest
      Test starting: testDevelopmentCollectionSettingsLoading
      Test success: testDevelopmentCollectionSettingsLoading
      Test starting: testExampleSettingsLoading
      Test success: testExampleSettingsLoading
    Starting testcase ActiveMQMessageBusTest
      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@58c64ca5[correlationID=12345, collectionID=MyCollection, destination=topic://collectionTopic, replyTo=topic://clientTopic, from=ClientPillar, to=<null>(default), version=29, 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@5601a9cd[correlationID=12345, collectionID=MyCollection, destination=topic://collectionTopic, replyTo=topic://clientTopic, from=ClientPillar, to=<null>(default), version=29, 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@2adc508f[correlationID=12345, collectionID=MySla, destination=TEST-TOPIC-cibuild01, replyTo=topic://clientTopic, from=ClientPillar, to=specificReceiver, version=29, minVersion=24, auditTrailInformation=User: Name, Institution: Place, fileID=MyDataID]
      Test success: sendMessageToSpecificComponentTest
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@523e27d5[correlationID=12345, collectionID=MySla, destination=TEST-TOPIC-cibuild01, replyTo=topic://clientTopic, from=ClientPillar, to=specificReceiver, version=29, minVersion=24, auditTrailInformation=User: Name, Institution: Place, fileID=MyDataID]
          Result: The following messages haven't been handled by the testcase: 
org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@523e27d5[correlationID=12345, collectionID=MySla, destination=TEST-TOPIC-cibuild01, replyTo=topic://clientTopic, from=ClientPillar, to=specificReceiver, version=29, minVersion=24, auditTrailInformation=User: Name, Institution: Place, fileID=MyDataID]
15:26:30.341 WARN  o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: 
org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@523e27d5[correlationID=12345, collectionID=MySla, destination=TEST-TOPIC-cibuild01, replyTo=topic://clientTopic, from=ClientPillar, to=specificReceiver, version=29, minVersion=24, auditTrailInformation=User: Name, Institution: Place, fileID=MyDataID]
      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@173ca3f6[correlationID=12345, collectionID=MySla, destination=TEST-TOPIC-cibuild01, replyTo=topic://clientTopic, from=ClientPillar, to=<null>(default), version=29, 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@7d7566d0[correlationID=12345, collectionID=MySla, destination=TEST-TOPIC-cibuild01, replyTo=topic://clientTopic, from=ClientPillar, to=<null>(default), version=29, 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@2661f772[correlationID=12345, collectionID=MySla, destination=topic://collectionTopic, replyTo=topic://clientTopic, from=MyPillar, to=<null>(default), version=29, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@5c26ce4[responseCode=IDENTIFICATION_POSITIVE, responseText=Ready to delete file 'MyDataID'.], fileID=MyDataID, pillarID=MyPillar, pillarChecksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@77135cb9[checksumType=MD5, checksumSalt={-85,-51}, otherChecksumType=<null>(default)], timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@2106e76d[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@8754e58[correlationID=12345, collectionID=MySla, destination=TEST-TOPIC-cibuild01, replyTo=topic://clientTopic, from=ClientPillar, to=<null>(default), version=29, minVersion=24, auditTrailInformation=User: Name, Institution: Place, pillarID=MyPillar, fileID=MyDataID, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@10860c6e[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2ee79355[checksumType=MD5, checksumSalt={-85,-85}, otherChecksumType=<null>(default)], checksumValue={19,95,33,86}, calculationTimestamp=2011-02-17T09:47:00.000+01:00], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6412efe2[checksumType=MD5, checksumSalt={-85,-51}, otherChecksumType=<null>(default)]]
      Test success: toFilterTest
    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
      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@ac35c4d[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>(default), version=29, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@4ce6fb9a[origDateTime=2011-05-03T11:18:00Z, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>(default)]]
        Step: Make sure both listeners received the message
          Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@1ec6a6fe[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>(default), version=29, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@1d7db472[origDateTime=2011-05-03T11:18:00Z, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>(default)]]
      Test success: busActivityTest
    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
          Stimuli: Sending message: org.bitrepository.bitrepositorymessages.AlarmMessage@233f4b3a[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>(default), version=29, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@7a4e9801[origDateTime=2011-05-03T11:18:00Z, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>(default)]]
        Step: Make sure both listeners received the message
          Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@735dc70b[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>(default), version=29, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@525f6a8[origDateTime=2011-05-03T11:18:00Z, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>(default)]]
      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@5d3d0e88[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>(default), version=29, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@510a6317[origDateTime=2011-05-03T11:18:00Z, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>(default)]]
        Step: Make sure both listeners received the message
          Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@65f67b82[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>(default), version=29, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@39a8f364[origDateTime=2011-05-03T11:18:00Z, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>(default)]]
          Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@4753eeea[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>(default), version=29, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@609ef1d1[origDateTime=2011-05-03T11:18:00Z, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>(default)]]
          Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@6c8941a8[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>(default), version=29, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@3cc1e597[origDateTime=2011-05-03T11:18:00Z, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>(default)]]
      Test success: twoListenersForTopicTest
          Result: The following messages haven't been handled by the testcase: 
org.bitrepository.bitrepositorymessages.AlarmMessage@65f67b82[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>(default), version=29, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@39a8f364[origDateTime=2011-05-03T11:18:00Z, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>(default)]]
15:26:35.479 WARN  o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: 
org.bitrepository.bitrepositorymessages.AlarmMessage@65f67b82[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>(default), version=29, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@39a8f364[origDateTime=2011-05-03T11:18:00Z, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>(default)]]
      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@3ec57b57[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>(default), version=29, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@527ba75a[origDateTime=2011-05-03T11:18:00Z, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>(default)]]
        Step: Make sure both listeners received the message
          Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@7171b6ad[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>(default), version=29, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@41531aab[origDateTime=2011-05-03T11:18:00Z, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>(default)]]
          Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@270de96a[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>(default), version=29, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@27269535[origDateTime=2011-05-03T11:18:00Z, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>(default)]]
          Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@7ff167df[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>(default), version=29, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@e17f8d8[origDateTime=2011-05-03T11:18:00Z, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>(default)]]
      Test success: twoListenersForTopicTest
          Result: The following messages haven't been handled by the testcase: 
org.bitrepository.bitrepositorymessages.AlarmMessage@7171b6ad[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>(default), version=29, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@41531aab[origDateTime=2011-05-03T11:18:00Z, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>(default)]]
15:26:36.430 WARN  o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: 
org.bitrepository.bitrepositorymessages.AlarmMessage@7171b6ad[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>(default), version=29, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@41531aab[origDateTime=2011-05-03T11:18:00Z, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>(default)]]
      Test starting: utilityTester
        Description: Test that the utility class is a proper utility class.
      Test success: utilityTester
      Test starting: utilityTester
        Description: Test that the utility class is a proper utility class.
      Test success: utilityTester
    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 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 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 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
    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 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 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 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 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 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 XMLFileSettingsLoaderTest
      Test starting: testCollectionSettingsLoading
      Test success: testCollectionSettingsLoading
      Test starting: componentIDTest
      Test success: componentIDTest
      Test starting: reloadTest
      Test success: reloadTest
      Finished testcase
15:26:37.713 ERROR o.b.protocol.bus.RawMessagebus - JMSException caught: 
javax.jms.JMSException: java.io.EOFException
	at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:54)
	at org.apache.activemq.ActiveMQConnection.onAsyncException(ActiveMQConnection.java:1967)
	at org.apache.activemq.ActiveMQConnection.onException(ActiveMQConnection.java:1986)
	at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:101)
	at org.apache.activemq.transport.ResponseCorrelator.onException(ResponseCorrelator.java:126)
	at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:101)
	at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:101)
	at org.apache.activemq.transport.WireFormatNegotiator.onException(WireFormatNegotiator.java:173)
	at org.apache.activemq.transport.AbstractInactivityMonitor.onException(AbstractInactivityMonitor.java:344)
	at org.apache.activemq.transport.TransportSupport.onException(TransportSupport.java:96)
	at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:219)
	at java.lang.Thread.run(Thread.java:745)
Caused by: java.io.EOFException: null
	at java.io.DataInputStream.readInt(DataInputStream.java:392)
	at org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:267)
	at org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:240)
	at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:232)
	at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:215)
	... 1 common frames omitted
15:26:37.726 ERROR o.b.protocol.bus.RawMessagebus - JMSException caught: 
javax.jms.JMSException: java.io.EOFException
	at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:54)
	at org.apache.activemq.ActiveMQConnection.onAsyncException(ActiveMQConnection.java:1967)
	at org.apache.activemq.ActiveMQConnection.onException(ActiveMQConnection.java:1986)
	at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:101)
	at org.apache.activemq.transport.ResponseCorrelator.onException(ResponseCorrelator.java:126)
	at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:101)
	at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:101)
	at org.apache.activemq.transport.WireFormatNegotiator.onException(WireFormatNegotiator.java:173)
	at org.apache.activemq.transport.AbstractInactivityMonitor.onException(AbstractInactivityMonitor.java:344)
	at org.apache.activemq.transport.TransportSupport.onException(TransportSupport.java:96)
	at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:219)
	at java.lang.Thread.run(Thread.java:745)
Caused by: java.io.EOFException: null
	at java.io.DataInputStream.readInt(DataInputStream.java:392)
	at org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:267)
	at org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:240)
	at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:232)
	at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:215)
	... 1 common frames omitted
15:26:37.744 ERROR o.b.protocol.bus.RawMessagebus - JMSException caught: 
javax.jms.JMSException: java.io.EOFException
	at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:54)
	at org.apache.activemq.ActiveMQConnection.onAsyncException(ActiveMQConnection.java:1967)
	at org.apache.activemq.ActiveMQConnection.onException(ActiveMQConnection.java:1986)
	at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:101)
	at org.apache.activemq.transport.ResponseCorrelator.onException(ResponseCorrelator.java:126)
	at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:101)
	at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:101)
	at org.apache.activemq.transport.WireFormatNegotiator.onException(WireFormatNegotiator.java:173)
	at org.apache.activemq.transport.AbstractInactivityMonitor.onException(AbstractInactivityMonitor.java:344)
	at org.apache.activemq.transport.TransportSupport.onException(TransportSupport.java:96)
	at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:219)
	at java.lang.Thread.run(Thread.java:745)
Caused by: java.io.EOFException: null
	at java.io.DataInputStream.readInt(DataInputStream.java:392)
	at org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:267)
	at org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:240)
	at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:232)
	at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:215)
	... 1 common frames omitted
  Finished suite
Finished project
Tests run: 104, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 38.431 sec - in TestSuite

Results :

Tests run: 104, 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.
[INFO] 
[INFO] --- jacoco-maven-plugin:0.7.5.201505241946:report (report) @ bitrepository-core ---
[INFO] Analyzed bundle 'Bitrepository Core' with 87 classes
[INFO] 
[INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ bitrepository-core ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-core/target/bitrepository-core-1.10-SNAPSHOT.jar
[INFO] 
[INFO] --- maven-jar-plugin:2.4:test-jar (default) @ bitrepository-core ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-core/target/bitrepository-core-1.10-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-reference-test/bitrepository-core/target/bitrepository-core-1.10-SNAPSHOT-sources.jar
[INFO] 
[INFO] --- maven-install-plugin:2.5.1:install (default-install) @ bitrepository-core ---
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-core/target/bitrepository-core-1.10-SNAPSHOT.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-core/1.10-SNAPSHOT/bitrepository-core-1.10-SNAPSHOT.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-core/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-core/1.10-SNAPSHOT/bitrepository-core-1.10-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-core/target/bitrepository-core-1.10-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-core/1.10-SNAPSHOT/bitrepository-core-1.10-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-core/target/bitrepository-core-1.10-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-core/1.10-SNAPSHOT/bitrepository-core-1.10-SNAPSHOT-sources.jar
[INFO] 
[INFO] --- maven-deploy-plugin:2.8.1:deploy (default-deploy) @ bitrepository-core ---
[INFO] Downloading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-core/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-core/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 8.9 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-core/1.10-SNAPSHOT/bitrepository-core-1.10-20170608.132644-5.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-core/1.10-SNAPSHOT/bitrepository-core-1.10-20170608.132644-5.jar (146 KB at 2548.7 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-core/1.10-SNAPSHOT/bitrepository-core-1.10-20170608.132644-5.pom
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-core/1.10-SNAPSHOT/bitrepository-core-1.10-20170608.132644-5.pom (4 KB at 71.8 KB/sec)
[INFO] Downloading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-core/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-core/maven-metadata.xml (445 B at 14.5 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-core/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-core/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 27.0 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-core/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-core/maven-metadata.xml (445 B at 9.2 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-core/1.10-SNAPSHOT/bitrepository-core-1.10-20170608.132644-5-tests.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-core/1.10-SNAPSHOT/bitrepository-core-1.10-20170608.132644-5-tests.jar (168 KB at 2612.6 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-core/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-core/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 39.6 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-core/1.10-SNAPSHOT/bitrepository-core-1.10-20170608.132644-5-sources.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-core/1.10-SNAPSHOT/bitrepository-core-1.10-20170608.132644-5-sources.jar (141 KB at 2456.4 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-core/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-core/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 42.4 KB/sec)
[JENKINS] Archiving disabled
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Client 1.10-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] Downloading: https://sbforge.org/nexus/content/groups/public/org/bitrepository/reference/bitrepository-core/1.10-SNAPSHOT/bitrepository-core-1.10-20170608.132644-5-tests.jar
[INFO] Downloaded: https://sbforge.org/nexus/content/groups/public/org/bitrepository/reference/bitrepository-core/1.10-SNAPSHOT/bitrepository-core-1.10-20170608.132644-5-tests.jar (168 KB at 1741.7 KB/sec)
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-client ---
[INFO] Deleting /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-client/target
[INFO] 
[INFO] --- jacoco-maven-plugin:0.7.5.201505241946:prepare-agent (default) @ bitrepository-client ---
[INFO] argLine set to -javaagent:/home/cibuild01/.m2/repository/org/jacoco/org.jacoco.agent/0.7.5.201505241946/org.jacoco.agent-0.7.5.201505241946-runtime.jar=destfile=/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-client/target/jacoco.exec
[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-reference-test/bitrepository-client/target/classes
[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-reference-test/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-reference-test/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-reference-test/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 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@3a69014e, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@5b4d9bda[correlationID=dcd30a56-5283-4f40-8648-f81536607fcd, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=collectionIDIncludedInEventsTest, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@5f803481[fileID=<null>(default), allFileIDs=true], checksumRequestForExistingFile=<null>(default)]
          Result: Received event: dcd30a56: 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: dcd30a56: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: dcd30a56: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE
          Result: Received event: dcd30a56: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: dcd30a56: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar1], Sending GetFileIDsRequest's
          Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@15bb8ed5[correlationID=dcd30a56-5283-4f40-8648-f81536607fcd, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=collectionIDIncludedInEventsTest, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@18f8ebd4[fileID=<null>(default), allFileIDs=true], minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), checksumRequestForExistingFile=<null>(default), resultAddress=<null>(default)]
        Step: Wait for 1 second
          Result: Received event: dcd30a56: GET_CHECKSUMS: FAILED: , Failed to receive responses from all contributors before timeout(500ms). Missing contributors [Pillar1]
      Test success: collectionIDIncludedInEventsTest
15:26:54.928 ERROR o.b.a.g.c.GettingChecksums - Failing conversation 'GetChecksumsConversationContext{collectionID='TwoPillarCollection', conversationID='dcd30a56-5283-4f40-8648-f81536607fcd', clientID='collectionIDIncludedInEventsTest', fileID='null', contributors=[Pillar1, Pillar2], monitor=ConversationEventMonitor{, collectionID='TwoPillarCollection', conversationID='dcd30a56', operationType=GET_CHECKSUMS, fileID='null', eventHandler=org.bitrepository.client.TestEventHandler@3a69014e, contributorCompleteEvents=[], contributorFailedEvents=[dcd30a56: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE], failOnComponentFailure=true}, auditTrailInformation='null', state=org.bitrepository.client.conversation.FinishedState@7b4694d, checksumPillars=[]}' with exception
org.bitrepository.common.exceptions.UnableToFinishException: Failed to receive responses from all contributors before timeout(500ms). Missing contributors [Pillar1]
	at org.bitrepository.client.conversation.PerformingOperationState.logStateTimeout(PerformingOperationState.java:82)
	at org.bitrepository.client.conversation.GeneralConversationState$TimeoutHandler.run(GeneralConversationState.java:133)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
      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@3a69014e, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@2bd7f686[correlationID=b5f23ffb-c781-42ba-ab6e-972f524e5489, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=conversationTimeoutTest, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@3601549f[fileID=<null>(default), allFileIDs=true], checksumRequestForExistingFile=<null>(default)]
          Result: Received event: b5f23ffb: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums
15:26:56.302 WARN  o.b.c.c.m.CollectionBasedConversationMediator - Failing timed out conversation b5f23ffb-c781-42ba-ab6e-972f524e5489 (Age 997ms)
          Result: Received event: b5f23ffb: GET_CHECKSUMS: FAILED: , Failing timed out conversation b5f23ffb-c781-42ba-ab6e-972f524e5489
      Test success: conversationTimeoutTest
      Test starting: identificationFailureTest
        Description: Verify that the client works correctly when a contributor sends a failure response.
        Step: Start the operation.
          Stimuli: Calling getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@3a69014e, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@602aeb87[correlationID=7052beca-466a-4453-8c26-ac4cdd4ff432, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=identificationFailureTest, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@423762ae[fileID=<null>(default), allFileIDs=true], checksumRequestForExistingFile=<null>(default)]
          Result: Received event: 7052beca: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums
        Step: Send a identification response from contributor1 with a FAILURE response code.
          Result: Received event: 7052beca: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE
        Step: Send a identification response from contributor2 with a IDENTIFICATION_POSITIVE response code .
          Result: Received event: 7052beca: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar2
          Result: Received event: 7052beca: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
          Result: Received event: 7052beca: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar2], Sending GetFileIDsRequest's
          Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@535a6697[correlationID=7052beca-466a-4453-8c26-ac4cdd4ff432, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=identificationFailureTest, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@641bc9a8[fileID=<null>(default), allFileIDs=true], minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), checksumRequestForExistingFile=<null>(default), resultAddress=<null>(default)]
        Step: Verify that the client continues to the performing phase.
        Step: Send a final response message from contributor2
          Result: Received event: 7052beca: GET_CHECKSUMS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false
          Result: Received event: 7052beca: GET_CHECKSUMS: FAILED: , Failed operation. Cause(s):
[7052beca: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE]
      Test success: identificationFailureTest
      Test starting: identificationNegativeTest
        Description: Verify that the client works correctly when a contributor sends a negative response.
        Step: Start the operation.
          Stimuli: Calling getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@3a69014e, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@1adfb5b8[correlationID=91a9cd6f-e49a-488f-a613-20b937b9463c, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=identificationNegativeTest, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@254cc548[fileID=<null>(default), allFileIDs=true], checksumRequestForExistingFile=<null>(default)]
          Result: Received event: 91a9cd6f: 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: 91a9cd6f: 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: 91a9cd6f: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar2
          Result: Received event: 91a9cd6f: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
          Result: Received event: 91a9cd6f: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar2], Sending GetFileIDsRequest's
          Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@531299d3[correlationID=91a9cd6f-e49a-488f-a613-20b937b9463c, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=identificationNegativeTest, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@3487947c[fileID=<null>(default), allFileIDs=true], minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), checksumRequestForExistingFile=<null>(default), resultAddress=<null>(default)]
        Step: Verify that the client continues to the performing phase.
        Step: Send a final response message from contributor2
          Result: Received event: 91a9cd6f: GET_CHECKSUMS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false
          Result: Received event: 91a9cd6f: GET_CHECKSUMS: FAILED: , Failed operation. Cause(s):
[91a9cd6f: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: IDENTIFICATION_NEGATIVE]
      Test success: identificationNegativeTest
      Test starting: noContributorsRespondingTest
        Description: Tests the the client handles lack of a IdentifyResponse gracefully. More concrete this means that the occurrence of a identification timeout should be handled correctly
        Step: Set a 100 ms timeout for identifying contributors.
        Step: Start the operation.
          Stimuli: Calling getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@3a69014e, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@1fa44f66[correlationID=6820cec5-c5d9-4224-9e98-c8337619b5a9, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=noContributorsRespondingTest, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@4229b92c[fileID=<null>(default), allFileIDs=true], checksumRequestForExistingFile=<null>(default)]
          Result: Received event: 6820cec5: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums
        Step: Wait for 1 second
          Result: Received event: 6820cec5: GET_CHECKSUMS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar1, Pillar2]
          Result: Received event: 6820cec5: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor
          Result: Received event: 6820cec5: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
          Result: Received event: 6820cec5: 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@1fa44f66[correlationID=6820cec5-c5d9-4224-9e98-c8337619b5a9, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=noContributorsRespondingTest, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@4229b92c[fileID=<null>(default), allFileIDs=true], checksumRequestForExistingFile=<null>(default)]
15:26:59.655 WARN  o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: 
org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@1fa44f66[correlationID=6820cec5-c5d9-4224-9e98-c8337619b5a9, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=noContributorsRespondingTest, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@4229b92c[fileID=<null>(default), allFileIDs=true], checksumRequestForExistingFile=<null>(default)]
15:26:59.654 ERROR o.b.a.g.c.IdentifyPillarsForGetChecksums - Failing conversation 'GetChecksumsConversationContext{collectionID='TwoPillarCollection', conversationID='6820cec5-c5d9-4224-9e98-c8337619b5a9', clientID='noContributorsRespondingTest', fileID='null', contributors=[Pillar1, Pillar2], monitor=ConversationEventMonitor{, collectionID='TwoPillarCollection', conversationID='6820cec5', operationType=GET_CHECKSUMS, fileID='null', eventHandler=org.bitrepository.client.TestEventHandler@3a69014e, contributorCompleteEvents=[], contributorFailedEvents=[6820cec5: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor, 6820cec5: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor], failOnComponentFailure=true}, auditTrailInformation='null', state=org.bitrepository.client.conversation.FinishedState@44d3b58e, checksumPillars=[]}' with exception
org.bitrepository.common.exceptions.UnableToFinishException: Unable to continue operation, contributors unavailable.
	at org.bitrepository.client.conversation.IdentifyingState.completeState(IdentifyingState.java:76)
	at org.bitrepository.client.conversation.GeneralConversationState.changeState(GeneralConversationState.java:147)
	at org.bitrepository.client.conversation.GeneralConversationState.access$100(GeneralConversationState.java:48)
	at org.bitrepository.client.conversation.GeneralConversationState$TimeoutHandler.run(GeneralConversationState.java:134)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
      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@3a69014e, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@5b7b0ada[correlationID=8004608d-09ec-43d3-8831-51ebd381aaa6, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=oneContributorNotRespondingTest, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@705d72f0[fileID=<null>(default), allFileIDs=true], checksumRequestForExistingFile=<null>(default)]
          Result: Received event: 8004608d: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums
        Step: Send a identification response from contributor1.
          Result: Received event: 8004608d: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar1
        Step: Wait 1 second.
          Result: Received event: 8004608d: GET_CHECKSUMS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar2]
          Result: Received event: 8004608d: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
          Result: Received event: 8004608d: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: 8004608d: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar1], Sending GetFileIDsRequest's
          Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@72acc90f[correlationID=8004608d-09ec-43d3-8831-51ebd381aaa6, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=oneContributorNotRespondingTest, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@636407e4[fileID=<null>(default), allFileIDs=true], minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), checksumRequestForExistingFile=<null>(default), resultAddress=<null>(default)]
        Step: Verify that the client continues to the performing phase.
        Step: Send a final response upload message
          Result: Received event: 8004608d: GET_CHECKSUMS: COMPONENT_COMPLETE: ContributorID Pillar1, PartialResult=false
          Result: Received event: 8004608d: GET_CHECKSUMS: FAILED: , Failed operation. Cause(s):
[8004608d: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor]
      Test success: oneContributorNotRespondingTest
      Test starting: operationTimeoutTest
        Description: Tests the the client handles lack of final responses gracefully.
        Step: Set a 100 ms operation timeout.
        Step: Start the operation
          Stimuli: Calling getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@3a69014e, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@5543d800[correlationID=d3ab085a-7b50-4bc9-bc3b-e27b2b9e1c49, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=operationTimeoutTest, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@1e033801[fileID=<null>(default), allFileIDs=true], checksumRequestForExistingFile=<null>(default)]
          Result: Received event: d3ab085a: 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: d3ab085a: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: d3ab085a: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE
          Result: Received event: d3ab085a: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: d3ab085a: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar1], Sending GetFileIDsRequest's
          Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@57ed8f95[correlationID=d3ab085a-7b50-4bc9-bc3b-e27b2b9e1c49, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=operationTimeoutTest, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@1c25deb0[fileID=<null>(default), allFileIDs=true], minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), checksumRequestForExistingFile=<null>(default), resultAddress=<null>(default)]
        Step: Wait for 1 second
          Result: Received event: d3ab085a: GET_CHECKSUMS: FAILED: , Failed to receive responses from all contributors before timeout(100ms). Missing contributors [Pillar1]
15:27:00.597 ERROR o.b.a.g.c.GettingChecksums - Failing conversation 'GetChecksumsConversationContext{collectionID='TwoPillarCollection', conversationID='d3ab085a-7b50-4bc9-bc3b-e27b2b9e1c49', clientID='operationTimeoutTest', fileID='null', contributors=[Pillar1, Pillar2], monitor=ConversationEventMonitor{, collectionID='TwoPillarCollection', conversationID='d3ab085a', operationType=GET_CHECKSUMS, fileID='null', eventHandler=org.bitrepository.client.TestEventHandler@3a69014e, contributorCompleteEvents=[], contributorFailedEvents=[d3ab085a: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE], failOnComponentFailure=true}, auditTrailInformation='null', state=org.bitrepository.client.conversation.FinishedState@49716a15, checksumPillars=[]}' with exception
org.bitrepository.common.exceptions.UnableToFinishException: Failed to receive responses from all contributors before timeout(100ms). Missing contributors [Pillar1]
	at org.bitrepository.client.conversation.PerformingOperationState.logStateTimeout(PerformingOperationState.java:82)
	at org.bitrepository.client.conversation.GeneralConversationState$TimeoutHandler.run(GeneralConversationState.java:133)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
      Test success: operationTimeoutTest
    Starting testcase DeleteFileClientComponentTest
      Test starting: deleteClientIdentificationTimeout
        Description: Tests the handling of a failed identification for the DeleteClient
        Step: Initialise the number of pillars and the DeleteClient. Sets the identification timeout to 1 sec.
        Step: Request a file to be deleted on the default pillar.
          Stimuli: Calling deleteFile(default-test-file.txt, Pillar1, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@5c0f508b[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7a2ffb0b[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], 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@13cae908[checksumType=SHA1, checksumSalt=<null>(default), otherChecksumType=<null>(default)], eventHandler, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@53335328[correlationID=ab245724-2d3c-443d-a8cf-a2ac90826ea6, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientIdentificationTimeout, to=Pillar1, version=30, minVersion=24, auditTrailInformation=<null>(default), fileID=default-test-file.txt]
          Result: Received event: ab245724: 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: ab245724: 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: ab245724: DELETE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor
          Result: Received event: ab245724: DELETE_FILE for file default-test-file.txt: FAILED: , Unable to continue operation, contributors unavailable.
15:27:01.966 ERROR o.b.m.d.c.IdentifyPillarsForDeleteFile - Failing conversation 'DeleteFileConversationContext{collectionID='TwoPillarCollection', conversationID='ab245724-2d3c-443d-a8cf-a2ac90826ea6', clientID='deleteClientIdentificationTimeout', fileID='default-test-file.txt', contributors=[Pillar1], monitor=ConversationEventMonitor{, collectionID='TwoPillarCollection', conversationID='ab245724', operationType=DELETE_FILE, fileID='default-test-file.txt', eventHandler=org.bitrepository.client.TestEventHandler@10d7d970, contributorCompleteEvents=[], contributorFailedEvents=[ab245724: DELETE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor], failOnComponentFailure=true}, auditTrailInformation='null', state=org.bitrepository.client.conversation.FinishedState@4279ed4, checksumPillars=[]}' with exception
org.bitrepository.common.exceptions.UnableToFinishException: Unable to continue operation, contributors unavailable.
	at org.bitrepository.client.conversation.IdentifyingState.completeState(IdentifyingState.java:76)
	at org.bitrepository.client.conversation.GeneralConversationState.changeState(GeneralConversationState.java:147)
	at org.bitrepository.client.conversation.GeneralConversationState.access$100(GeneralConversationState.java:48)
	at org.bitrepository.client.conversation.GeneralConversationState$TimeoutHandler.run(GeneralConversationState.java:134)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
      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@682d8dad[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1aebe759[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], 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@6fd37997[checksumType=SHA1, checksumSalt=<null>(default), otherChecksumType=<null>(default)], eventHandler, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@5dc7881d[correlationID=81d83e5d-5819-4f3e-9321-85ac428dae57, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientOperationTimeout, to=Pillar1, version=30, minVersion=24, auditTrailInformation=<null>(default), fileID=default-test-file.txt]
          Result: Received event: 81d83e5d: 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: 81d83e5d: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 81d83e5d: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: 81d83e5d: 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@1c97c3bb[correlationID=81d83e5d-5819-4f3e-9321-85ac428dae57, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientOperationTimeout, to=Pillar1, version=30, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@682d8dad[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1aebe759[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], 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@6fd37997[checksumType=SHA1, checksumSalt=<null>(default), otherChecksumType=<null>(default)]]
        Step: Validate the steps of the DeleteClient by going through the events.
        Step: Do not respond. Just await the timeout.
          Result: Received event: 81d83e5d: DELETE_FILE for file default-test-file.txt: FAILED: , Failed to receive responses from all contributors before timeout(100ms). Missing contributors [Pillar1]
15:27:02.370 ERROR o.b.m.d.conversation.DeletingFile - Failing conversation 'DeleteFileConversationContext{collectionID='TwoPillarCollection', conversationID='81d83e5d-5819-4f3e-9321-85ac428dae57', clientID='deleteClientOperationTimeout', fileID='default-test-file.txt', contributors=[Pillar1], monitor=ConversationEventMonitor{, collectionID='TwoPillarCollection', conversationID='81d83e5d', operationType=DELETE_FILE, fileID='default-test-file.txt', eventHandler=org.bitrepository.client.TestEventHandler@473ff293, contributorCompleteEvents=[], contributorFailedEvents=[], failOnComponentFailure=true}, auditTrailInformation='null', state=org.bitrepository.client.conversation.FinishedState@5dc09a3, checksumPillars=[]}' with exception
org.bitrepository.common.exceptions.UnableToFinishException: Failed to receive responses from all contributors before timeout(100ms). Missing contributors [Pillar1]
	at org.bitrepository.client.conversation.PerformingOperationState.logStateTimeout(PerformingOperationState.java:82)
	at org.bitrepository.client.conversation.GeneralConversationState$TimeoutHandler.run(GeneralConversationState.java:133)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
      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@62cb977a[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7db70494[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2017-06-08T15:27:02.649+02:00], null, eventHandler, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@3f030217[correlationID=5e828ce2-4d27-4c8e-b5b6-d8c6d0685cee, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientOtherPillarFailedDuringIdentification, to=Pillar1, version=30, minVersion=24, auditTrailInformation=<null>(default), fileID=default-test-file.txt]
          Result: Received event: 5e828ce2: 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: 5e828ce2: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 5e828ce2: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: 5e828ce2: 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@1104ad6a[correlationID=5e828ce2-4d27-4c8e-b5b6-d8c6d0685cee, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientOtherPillarFailedDuringIdentification, to=Pillar1, version=30, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@62cb977a[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7db70494[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2017-06-08T15:27:02.649+02:00], checksumRequestForExistingFile=<null>(default)]
        Step: Send a final response message from pillar 1 to the DeleteClient.
          Result: Received event: 5e828ce2: DELETE_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, DeleteFileResult=null
          Result: Received event: 5e828ce2: 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@613ba54e[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@27422187[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], 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@7205a8b7[checksumType=SHA1, checksumSalt=<null>(default), otherChecksumType=<null>(default)], eventHandler, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@1ee126de[correlationID=e7ccf75e-2580-4a2f-a872-10e863f58242, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientPillarFailedDuringPerform, to=Pillar1, version=30, minVersion=24, auditTrailInformation=<null>(default), fileID=default-test-file.txt]
          Result: Received event: e7ccf75e: 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: e7ccf75e: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: e7ccf75e: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: e7ccf75e: 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@14b4b25e[correlationID=e7ccf75e-2580-4a2f-a872-10e863f58242, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientPillarFailedDuringPerform, to=Pillar1, version=30, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@613ba54e[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@27422187[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], 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@7205a8b7[checksumType=SHA1, checksumSalt=<null>(default), otherChecksumType=<null>(default)]]
        Step: Validate the steps of the DeleteClient by going through the events.
        Step: Send a failed response message to the DeleteClient.
          Result: Received event: e7ccf75e: DELETE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE, Verifying that a failure can be understood!
          Result: Received event: e7ccf75e: DELETE_FILE for file default-test-file.txt: FAILED: , Failed operation. Cause(s):
[e7ccf75e: 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@76ffd052[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1ebb36df[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2017-06-08T15:27:04.269+02:00], null, eventHandler, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@1f4de96e[correlationID=fa767f80-e612-4834-8584-8100a584e1da, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientSpecifiedPillarFailedDuringIdentification, to=Pillar1, version=30, minVersion=24, auditTrailInformation=<null>(default), fileID=default-test-file.txt]
          Result: Received event: fa767f80: 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: fa767f80: DELETE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: IDENTIFICATION_NEGATIVE
          Result: Received event: fa767f80: DELETE_FILE for file default-test-file.txt: FAILED: , Can not continue with delete operation, as Pillar1 is unable to perform the deletion.
15:27:04.279 ERROR o.b.m.d.c.IdentifyPillarsForDeleteFile - Failing conversation 'DeleteFileConversationContext{collectionID='TwoPillarCollection', conversationID='fa767f80-e612-4834-8584-8100a584e1da', clientID='deleteClientSpecifiedPillarFailedDuringIdentification', fileID='default-test-file.txt', contributors=[Pillar1], monitor=ConversationEventMonitor{, collectionID='TwoPillarCollection', conversationID='fa767f80', operationType=DELETE_FILE, fileID='default-test-file.txt', eventHandler=org.bitrepository.client.TestEventHandler@46c61d1, contributorCompleteEvents=[], contributorFailedEvents=[fa767f80: DELETE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: IDENTIFICATION_NEGATIVE], failOnComponentFailure=true}, auditTrailInformation='null', state=org.bitrepository.client.conversation.FinishedState@c194c4e, checksumPillars=[]}' with exception
org.bitrepository.common.exceptions.UnableToFinishException: Can not continue with delete operation, as Pillar1 is unable to perform the deletion.
	at org.bitrepository.modify.deletefile.conversation.IdentifyPillarsForDeleteFile.handleFailureResponse(IdentifyPillarsForDeleteFile.java:71)
	at org.bitrepository.client.conversation.IdentifyingState.processMessage(IdentifyingState.java:60)
	at org.bitrepository.client.conversation.GeneralConversationState.handleMessage(GeneralConversationState.java:110)
	at org.bitrepository.client.conversation.StateBasedConversation.onMessage(StateBasedConversation.java:53)
	at org.bitrepository.client.conversation.mediator.CollectionBasedConversationMediator.onMessage(CollectionBasedConversationMediator.java:136)
	at org.bitrepository.protocol.messagebus.SimpleMessageBus.lambda$sendMessage$0(SimpleMessageBus.java:73)
	at java.lang.Iterable.forEach(Iterable.java:75)
	at org.bitrepository.protocol.messagebus.SimpleMessageBus.sendMessage(SimpleMessageBus.java:73)
	at org.bitrepository.modify.deletefile.DeleteFileClientComponentTest.deleteClientSpecifiedPillarFailedDuringIdentification(DeleteFileClientComponentTest.java:356)
	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:498)
	at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:86)
	at org.testng.internal.Invoker.invokeMethod(Invoker.java:643)
	at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:820)
	at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1128)
	at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:129)
	at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:112)
	at org.testng.TestRunner.privateRun(TestRunner.java:782)
	at org.testng.TestRunner.run(TestRunner.java:632)
	at org.testng.SuiteRunner.runTest(SuiteRunner.java:366)
	at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:361)
	at org.testng.SuiteRunner.privateRun(SuiteRunner.java:319)
	at org.testng.SuiteRunner.run(SuiteRunner.java:268)
	at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
	at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
	at org.testng.TestNG.runSuitesSequentially(TestNG.java:1244)
	at org.testng.TestNG.runSuitesLocally(TestNG.java:1169)
	at org.testng.TestNG.run(TestNG.java:1064)
	at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:115)
	at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:204)
	at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:107)
	at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:112)
	at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
      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@5af47414[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@43e9a8a2[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], 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@178617da[checksumType=SHA1, checksumSalt=<null>(default), otherChecksumType=<null>(default)], eventHandler, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@d408c5d[correlationID=7a6d8166-e56a-403a-9788-3a924b19bb48, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientTester, to=Pillar1, version=30, minVersion=24, auditTrailInformation=<null>(default), fileID=default-test-file.txt]
          Result: Received event: 7a6d8166: 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: 7a6d8166: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 7a6d8166: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: 7a6d8166: 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@7acf07b2[correlationID=7a6d8166-e56a-403a-9788-3a924b19bb48, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientTester, to=Pillar1, version=30, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@5af47414[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@43e9a8a2[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], 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@178617da[checksumType=SHA1, checksumSalt=<null>(default), otherChecksumType=<null>(default)]]
        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: 7a6d8166: 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: 7a6d8166: DELETE_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, DeleteFileResult=null
          Result: Received event: 7a6d8166: 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@3811464b[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@5f0a5848[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2017-06-08T15:27:04.849+02:00], null, eventHandler, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@c6db00d[correlationID=fc177410-cb9d-46ec-99be-21f82a6a9375, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteOnChecksumPillar, to=Pillar1, version=30, minVersion=24, auditTrailInformation=<null>(default), fileID=default-test-file.txt]
          Result: Received event: fc177410: 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: fc177410: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: fc177410: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: fc177410: 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@413e8246[correlationID=fc177410-cb9d-46ec-99be-21f82a6a9375, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteOnChecksumPillar, to=Pillar1, version=30, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@3811464b[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@5f0a5848[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2017-06-08T15:27:04.849+02:00], checksumRequestForExistingFile=<null>(default)]
      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@685e5967[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@106387cf[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2017-06-08T15:27:07.143+02:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@3d3c14c3[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], eventHandler, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@599fab92[correlationID=0ea4f53f-cfa2-4a92-9b1a-5aeb7b3172dc, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteOnChecksumPillarWithDefaultReturnChecksumType, to=Pillar1, version=30, minVersion=24, auditTrailInformation=<null>(default), fileID=default-test-file.txt]
          Result: Received event: 0ea4f53f: 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: 0ea4f53f: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 0ea4f53f: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: 0ea4f53f: 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@3ed3e66d[correlationID=0ea4f53f-cfa2-4a92-9b1a-5aeb7b3172dc, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteOnChecksumPillarWithDefaultReturnChecksumType, to=Pillar1, version=30, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@685e5967[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@106387cf[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2017-06-08T15:27:07.143+02:00], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@3d3c14c3[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)]]
      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@7fe40b9f[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1f41f259[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2017-06-08T15:27:07.428+02:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@648c80cb[checksumType=MD5, checksumSalt={-86}, otherChecksumType=<null>(default)], eventHandler, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@4a9d6eb9[correlationID=f8c1e180-af5d-4ce9-be1b-622dffd88105, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteOnChecksumPillarWithSaltedReturnChecksumType, to=Pillar1, version=30, minVersion=24, auditTrailInformation=<null>(default), fileID=default-test-file.txt]
          Result: Received event: f8c1e180: 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: f8c1e180: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: f8c1e180: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: f8c1e180: 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@5b9c74a[correlationID=f8c1e180-af5d-4ce9-be1b-622dffd88105, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteOnChecksumPillarWithSaltedReturnChecksumType, to=Pillar1, version=30, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@7fe40b9f[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1f41f259[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2017-06-08T15:27:07.428+02:00], checksumRequestForExistingFile=<null>(default)]
      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@7672dd7a[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1aee0f49[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2017-06-08T15:27:07.952+02:00], null, eventHandler, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@7a80ebcd[correlationID=468a6534-95ea-4388-bd79-4e61371b5a62, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=fileAlreadyDeletedFromPillar, to=Pillar1, version=30, minVersion=24, auditTrailInformation=<null>(default), fileID=default-test-file.txt]
          Result: Received event: 468a6534: 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: 468a6534: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 468a6534: DELETE_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, DeleteFileResult=null
          Result: Received event: 468a6534: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: []
          Result: Received event: 468a6534: DELETE_FILE for file default-test-file.txt: COMPLETE: 
        Step: The client should then continue to the performing phase and finish immediately as the pillar has already had the file removed apparently .
        Step: Send a identify response from Pillar2
      Test success: fileAlreadyDeletedFromPillar
      Test starting: verifyDeleteClientFromFactory
        Description: Testing the initialization through the ModifyComponentFactory.
        Step: Use the ModifyComponentFactory to instantiate a PutFileClient.
      Test success: verifyDeleteClientFromFactory
      Test starting: getChecksumsDeliveredAtUrl
        Description: Tests the delivery of checksums from all pillars at a given URL.
        Step: Ensure the delivery file isn't already present on the http server
        Step: Request the delivery of the checksum of a file from all pillars.
          Stimuli: Calling getChecksums(null, default-test-file.txt, null, file:../bitrepository-core/src/test/resources/test-files//TEST-CHECKSUM-DELIVERY.xml, org.bitrepository.client.TestEventHandler@3f563397, TEST-AUDIT)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@268ee31d[correlationID=e95211f2-afec-4bc6-a51a-d5dcbaeb059e, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=getChecksumsDeliveredAtUrl, to=<null>(default), version=30, minVersion=24, auditTrailInformation=TEST-AUDIT, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@7bb50747[fileID=default-test-file.txt, allFileIDs=<null>(default)], checksumRequestForExistingFile=<null>(default)]
          Result: Received event: e95211f2: 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: e95211f2: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: e95211f2: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
          Result: Received event: e95211f2: GET_CHECKSUMS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2]
          Result: Received event: e95211f2: 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@17db90a7[correlationID=e95211f2-afec-4bc6-a51a-d5dcbaeb059e, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=getChecksumsDeliveredAtUrl, to=<null>(default), version=30, minVersion=24, auditTrailInformation=TEST-AUDIT, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@44872224[fileID=default-test-file.txt, allFileIDs=<null>(default)], minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), checksumRequestForExistingFile=<null>(default), 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@4ebe6c24[correlationID=e95211f2-afec-4bc6-a51a-d5dcbaeb059e, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=getChecksumsDeliveredAtUrl, to=<null>(default), version=30, minVersion=24, auditTrailInformation=TEST-AUDIT, pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@682fc714[fileID=default-test-file.txt, allFileIDs=<null>(default)], minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), checksumRequestForExistingFile=<null>(default), 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: e95211f2: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, NumberOfChecksums=0, PartialResult=false
          Result: Received event: e95211f2: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2, NumberOfChecksums=0, PartialResult=false
          Result: Received event: e95211f2: 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@4ebe6c24[correlationID=e95211f2-afec-4bc6-a51a-d5dcbaeb059e, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=getChecksumsDeliveredAtUrl, to=<null>(default), version=30, minVersion=24, auditTrailInformation=TEST-AUDIT, pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@682fc714[fileID=default-test-file.txt, allFileIDs=<null>(default)], minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), checksumRequestForExistingFile=<null>(default), resultAddress=file:../bitrepository-core/src/test/resources/test-files//TEST-CHECKSUM-DELIVERY.xml-Pillar2]
15:27:09.512 WARN  o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: 
org.bitrepository.bitrepositorymessages.GetChecksumsRequest@4ebe6c24[correlationID=e95211f2-afec-4bc6-a51a-d5dcbaeb059e, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=getChecksumsDeliveredAtUrl, to=<null>(default), version=30, minVersion=24, auditTrailInformation=TEST-AUDIT, pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@682fc714[fileID=default-test-file.txt, allFileIDs=<null>(default)], minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), checksumRequestForExistingFile=<null>(default), 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@53c39950, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@3d056418[correlationID=1abe5ed6-0e12-498a-9454-ff68ea40f68a, collectionID=SinglePillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=getChecksumsFromOtherCollection, to=Pillar2, version=30, minVersion=24, auditTrailInformation=<null>(default), fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@769d0ef2[fileID=<null>(default), allFileIDs=true], checksumRequestForExistingFile=<null>(default)]
          Result: Received event: 1abe5ed6: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums
        Step: Send an identification response from pillar2.
          Result: Received event: 1abe5ed6: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar2
          Result: Received event: 1abe5ed6: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
          Result: Received event: 1abe5ed6: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar2], Sending GetFileIDsRequest's
          Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@221ef0f0[correlationID=1abe5ed6-0e12-498a-9454-ff68ea40f68a, collectionID=SinglePillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=getChecksumsFromOtherCollection, to=Pillar2, version=30, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@34ad750f[fileID=<null>(default), allFileIDs=true], minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), checksumRequestForExistingFile=<null>(default), resultAddress=<null>(default)]
        Step: Send a complete event from the pillar
          Result: Received event: 1abe5ed6: GET_CHECKSUMS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false
          Result: Received event: 1abe5ed6: 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@19070326[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], null, org.bitrepository.client.TestEventHandler@52dfd7f5, TEST-AUDIT)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@5b5f48d5[correlationID=db91e4be-bc09-418a-99d1-56cb37532f7d, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=getChecksumsFromSinglePillar, to=Pillar1, version=30, minVersion=24, auditTrailInformation=TEST-AUDIT, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@421c4c3e[fileID=default-test-file.txt, allFileIDs=<null>(default)], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@19070326[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)]]
          Result: Received event: db91e4be: 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: db91e4be: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: db91e4be: GET_CHECKSUMS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: db91e4be: 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@4f6f7a86[correlationID=db91e4be-bc09-418a-99d1-56cb37532f7d, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=getChecksumsFromSinglePillar, to=Pillar1, version=30, minVersion=24, auditTrailInformation=TEST-AUDIT, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@6ed78a5e[fileID=default-test-file.txt, allFileIDs=<null>(default)], minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@19070326[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultAddress=<null>(default)]
        Step: Send a GetChecksumsFinalResponse to the client from pillar1
          Result: Received event: db91e4be: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, NumberOfChecksums=0, PartialResult=false
          Result: Received event: db91e4be: 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@3c88db1, TEST-AUDIT)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@241861bc[correlationID=03fda32d-961d-4b94-88ae-ee8ae28af771, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=testNoSuchFile, to=Pillar1, version=30, minVersion=24, auditTrailInformation=TEST-AUDIT, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@5078e308[fileID=default-test-file.txt, allFileIDs=<null>(default)], checksumRequestForExistingFile=<null>(default)]
          Result: Received event: 03fda32d: 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: 03fda32d: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 03fda32d: GET_CHECKSUMS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: 03fda32d: 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@672710d5[correlationID=03fda32d-961d-4b94-88ae-ee8ae28af771, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=testNoSuchFile, to=Pillar1, version=30, minVersion=24, auditTrailInformation=TEST-AUDIT, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@55880c[fileID=default-test-file.txt, allFileIDs=<null>(default)], minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), checksumRequestForExistingFile=<null>(default), resultAddress=<null>(default)]
        Step: Send a error that the file cannot be found.
          Result: Received event: 03fda32d: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FILE_NOT_FOUND_FAILURE, No such file.
          Result: Received event: 03fda32d: GET_CHECKSUMS for file default-test-file.txt: FAILED: , Failed operation. Cause(s):
[03fda32d: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FILE_NOT_FOUND_FAILURE, No such file.]
      Test success: testNoSuchFile
      Test starting: testPaging
        Description: Tests the GetChecksums client correctly handles functionality for limiting results, either by timestamp or result count.
        Step: Request checksums from with MinTimestamp, MaxTimestamp, MaxNumberOfResults set for both pillars .
          Stimuli: Calling getChecksums([ContributorQuery{componentID='Pillar1, minTimestamp=Thu Jun 08 15:27:10 CEST 2017, maxTimestamp=Thu Jun 08 15:27:11 CEST 2017, maxNumberOfResults=1}, ContributorQuery{componentID='Pillar2, minTimestamp=Thu Jun 08 15:27:11 CEST 2017, maxTimestamp=Thu Jun 08 15:27:11 CEST 2017, maxNumberOfResults=2}], null, null, null, org.bitrepository.client.TestEventHandler@3a69014e, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@3577fd9b[correlationID=da723c9c-e805-44fd-b2b7-dbb5a43ec1b3, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=testPaging, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@76140ca5[fileID=<null>(default), allFileIDs=true], checksumRequestForExistingFile=<null>(default)]
          Result: Received event: da723c9c: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums
        Step: Send a IdentifyPillarsForGetChecksumsResponse from both pillars.
          Result: Received event: da723c9c: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: da723c9c: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar2
          Result: Received event: da723c9c: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2, Pillar1]
          Result: Received event: da723c9c: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending GetFileIDsRequest's
          Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@4ac64dc2[correlationID=da723c9c-e805-44fd-b2b7-dbb5a43ec1b3, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=testPaging, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@1c61011b[fileID=<null>(default), allFileIDs=true], minTimestamp=2017-06-08T15:27:10.683+02:00, maxTimestamp=2017-06-08T15:27:11.583+02:00, maxNumberOfResults=1, checksumRequestForExistingFile=<null>(default), resultAddress=<null>(default)]
          Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@75af5f2a[correlationID=da723c9c-e805-44fd-b2b7-dbb5a43ec1b3, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=testPaging, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@adc06b2[fileID=<null>(default), allFileIDs=true], minTimestamp=2017-06-08T15:27:11.583+02:00, maxTimestamp=2017-06-08T15:27:11.683+02:00, maxNumberOfResults=2, checksumRequestForExistingFile=<null>(default), resultAddress=<null>(default)]
      Test success: testPaging
      Test starting: verifyGetChecksumsClientFromFactory
      Test success: verifyGetChecksumsClientFromFactory
    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 operation should be performed. If undefined the operation 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: Random1496928435591pillar is not a valid pillar for collection TwoPillarCollection
The collection contains the following pillars: [Pillar1, Pillar2]
      Test success: unknownPillarArgumentTest
    Starting testcase GetFileIDsCmdTest
      Test starting: defaultSuccessScenarioTest
        Description: Tests simplest arguments for running the CmdLineClient
      Test success: defaultSuccessScenarioTest
      Test starting: fileArgumentTest
        Description: Tests the argument for a specific file.
      Test success: fileArgumentTest
      Test starting: missingCollectionArgumentTest
        Description: Tests the scenario, where the collection arguments is missing.
Takes the following arguments:
-s The path to the directory with the settings files for the client
-k The path to the file containing the private key.
-v Makes the client more verbose
-c The id for the collection to perform the operation on.
-i The id for the file to perform the operation on.
-p [OPTIONAL] The id of the pillar where the operation should be performed. If undefined the operation 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: Random1496928437403pillar is not a valid pillar for collection TwoPillarCollection
The collection contains the following pillars: [Pillar1, Pillar2]
      Test success: unknownPillarArgumentTest
    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 operation should be performed. If undefined the operation is performed on all pillars.
-f The path to the file, which needs to be  uploaded. 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 retrieved. 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: Random1496928441240pillar 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 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 operation should be performed. If undefined the operation 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: Random1496928445974pillar is not a valid pillar for collection TwoPillarCollection
The collection contains the following pillars: [Pillar1, Pillar2]
      Test success: unknownPillarArgumentTest
    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@253e291e[correlationID=d18bf807-bb18-4ea6-abcb-a3123db5e8c1, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=getAllAuditTrailsTest, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default)]
          Result: Received event: d18bf807: 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: d18bf807: GET_AUDIT_TRAILS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: d18bf807: GET_AUDIT_TRAILS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
          Result: Received event: d18bf807: GET_AUDIT_TRAILS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2]
          Result: Received event: d18bf807: 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@2c35cdd1[correlationID=d18bf807-bb18-4ea6-abcb-a3123db5e8c1, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=getAllAuditTrailsTest, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), contributor=Pillar1, fileID=default-test-file.txt, minSequenceNumber=<null>(default), maxSequenceNumber=<null>(default), minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), resultAddress=<null>(default)]
          Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@5775a262[correlationID=d18bf807-bb18-4ea6-abcb-a3123db5e8c1, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=getAllAuditTrailsTest, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), contributor=Pillar2, fileID=default-test-file.txt, minSequenceNumber=<null>(default), maxSequenceNumber=<null>(default), minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), resultAddress=<null>(default)]
        Step: Send a final response from pillar 1
          Result: Received event: d18bf807: 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: d18bf807: GET_AUDIT_TRAILS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2, NumberOfAuditTrailEvents=2, PartialResult=false
          Result: Received event: d18bf807: 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@1fe37814[correlationID=d86d7c6f-529d-4e6a-b90e-e17c4d71ea19, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=getSomeAuditTrailsTest, to=Pillar1, version=30, minVersion=24, auditTrailInformation=<null>(default)]
          Result: Received event: d86d7c6f: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
        Step: Send a identifyResponse from pillar1
          Result: Received event: d86d7c6f: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: d86d7c6f: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: d86d7c6f: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1], Sending request for audit trails
          Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@39af729d[correlationID=d86d7c6f-529d-4e6a-b90e-e17c4d71ea19, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=getSomeAuditTrailsTest, to=Pillar1, version=30, minVersion=24, auditTrailInformation=<null>(default), contributor=Pillar1, fileID=<null>(default), minSequenceNumber=1, maxSequenceNumber=3, minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=10000, resultAddress=<null>(default)]
        Step: Verify no request is sent to pillar2
        Step: Send a final response from pillar 1
          Result: Received event: d86d7c6f: GET_AUDIT_TRAILS: COMPONENT_COMPLETE: ContributorID Pillar1, NumberOfAuditTrailEvents=2, PartialResult=false
          Result: Received event: d86d7c6f: 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@31f3a0d3[correlationID=70fbea53-0aeb-4cab-bb03-00b63df60dc1, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=incompleteSetOfFinalResponsesTest, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default)]
          Result: Received event: 70fbea53: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
        Step: Send a identifyResponse from each of the two pillars
          Result: Received event: 70fbea53: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 70fbea53: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2
          Result: Received event: 70fbea53: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2]
          Result: Received event: 70fbea53: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for audit trails
          Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@18c8c5ff[correlationID=70fbea53-0aeb-4cab-bb03-00b63df60dc1, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=incompleteSetOfFinalResponsesTest, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), contributor=Pillar1, fileID=<null>(default), minSequenceNumber=<null>(default), maxSequenceNumber=<null>(default), minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), resultAddress=<null>(default)]
          Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@34910b0d[correlationID=70fbea53-0aeb-4cab-bb03-00b63df60dc1, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=incompleteSetOfFinalResponsesTest, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), contributor=Pillar2, fileID=<null>(default), minSequenceNumber=<null>(default), maxSequenceNumber=<null>(default), minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), resultAddress=<null>(default)]
      Test success: incompleteSetOfFinalResponsesTest
          Result: The following messages haven't been handled by the testcase: 
org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@34910b0d[correlationID=70fbea53-0aeb-4cab-bb03-00b63df60dc1, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=incompleteSetOfFinalResponsesTest, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), contributor=Pillar2, fileID=<null>(default), minSequenceNumber=<null>(default), maxSequenceNumber=<null>(default), minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), resultAddress=<null>(default)]
15:27:27.652 WARN  o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: 
org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@34910b0d[correlationID=70fbea53-0aeb-4cab-bb03-00b63df60dc1, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=incompleteSetOfFinalResponsesTest, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), contributor=Pillar2, fileID=<null>(default), minSequenceNumber=<null>(default), maxSequenceNumber=<null>(default), minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), resultAddress=<null>(default)]
      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@4fcbf387[correlationID=89e78eb1-e066-4a56-8fa5-4d257fc7bb50, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=negativeGetAuditTrailsResponseTest, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default)]
          Result: Received event: 89e78eb1: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
        Step: Send a identifyResponse from each of the two pillars
          Result: Received event: 89e78eb1: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 89e78eb1: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2
          Result: Received event: 89e78eb1: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2, Pillar1]
          Result: Received event: 89e78eb1: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for audit trails
          Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@4c28b19f[correlationID=89e78eb1-e066-4a56-8fa5-4d257fc7bb50, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=negativeGetAuditTrailsResponseTest, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), contributor=Pillar1, fileID=<null>(default), minSequenceNumber=<null>(default), maxSequenceNumber=<null>(default), minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), resultAddress=<null>(default)]
          Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@5cef3456[correlationID=89e78eb1-e066-4a56-8fa5-4d257fc7bb50, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=negativeGetAuditTrailsResponseTest, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), contributor=Pillar2, fileID=<null>(default), minSequenceNumber=<null>(default), maxSequenceNumber=<null>(default), minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), resultAddress=<null>(default)]
        Step: Send a failed response from pillar 1
          Result: Received event: 89e78eb1: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE, GetAuditTrails failed
        Step: Send a final response from pillar 2
          Result: Received event: 89e78eb1: GET_AUDIT_TRAILS: COMPONENT_COMPLETE: ContributorID Pillar2, NumberOfAuditTrailEvents=2, PartialResult=false
          Result: Received event: 89e78eb1: GET_AUDIT_TRAILS: FAILED: , Failed operation. Cause(s):
[89e78eb1: 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@1a17ac99[correlationID=35312bba-b806-4063-9354-f7925b715089, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noFinalResponsesTest, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default)]
          Result: Received event: 35312bba: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
        Step: Send a identifyResponse from each of the two pillars
          Result: Received event: 35312bba: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 35312bba: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2
          Result: Received event: 35312bba: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2, Pillar1]
          Result: Received event: 35312bba: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for audit trails
          Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@5ecfa2a4[correlationID=35312bba-b806-4063-9354-f7925b715089, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noFinalResponsesTest, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), contributor=Pillar1, fileID=<null>(default), minSequenceNumber=<null>(default), maxSequenceNumber=<null>(default), minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), resultAddress=<null>(default)]
          Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@791bbe80[correlationID=35312bba-b806-4063-9354-f7925b715089, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noFinalResponsesTest, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), contributor=Pillar2, fileID=<null>(default), minSequenceNumber=<null>(default), maxSequenceNumber=<null>(default), minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), resultAddress=<null>(default)]
        Step: Wait for 1 second
          Result: Received event: 35312bba: GET_AUDIT_TRAILS: FAILED: , Failed to receive responses from all contributors before timeout(100ms). Missing contributors [Pillar1, Pillar2]
15:27:28.120 ERROR o.b.a.g.client.GettingAuditTrails - Failing conversation 'AuditTrailConversationContext{collectionID='TwoPillarCollection', conversationID='35312bba-b806-4063-9354-f7925b715089', clientID='noFinalResponsesTest', fileID='null', contributors=[Pillar1, Pillar2], monitor=ConversationEventMonitor{, collectionID='TwoPillarCollection', conversationID='35312bba', operationType=GET_AUDIT_TRAILS, fileID='null', eventHandler=org.bitrepository.client.TestEventHandler@2bee4c31, contributorCompleteEvents=[], contributorFailedEvents=[], failOnComponentFailure=true}, auditTrailInformation='null', state=org.bitrepository.client.conversation.FinishedState@1387a6a6, checksumPillars=[]}' with exception
org.bitrepository.common.exceptions.UnableToFinishException: Failed to receive responses from all contributors before timeout(100ms). Missing contributors [Pillar1, Pillar2]
	at org.bitrepository.client.conversation.PerformingOperationState.logStateTimeout(PerformingOperationState.java:82)
	at org.bitrepository.client.conversation.GeneralConversationState$TimeoutHandler.run(GeneralConversationState.java:133)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
      Test success: noFinalResponsesTest
          Result: The following messages haven't been handled by the testcase: 
org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@5ecfa2a4[correlationID=35312bba-b806-4063-9354-f7925b715089, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noFinalResponsesTest, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), contributor=Pillar1, fileID=<null>(default), minSequenceNumber=<null>(default), maxSequenceNumber=<null>(default), minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), resultAddress=<null>(default)]
15:27:28.122 WARN  o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: 
org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@5ecfa2a4[correlationID=35312bba-b806-4063-9354-f7925b715089, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noFinalResponsesTest, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), contributor=Pillar1, fileID=<null>(default), minSequenceNumber=<null>(default), maxSequenceNumber=<null>(default), minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), resultAddress=<null>(default)]
          Result: The following messages haven't been handled by the testcase: 
org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@791bbe80[correlationID=35312bba-b806-4063-9354-f7925b715089, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noFinalResponsesTest, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), contributor=Pillar2, fileID=<null>(default), minSequenceNumber=<null>(default), maxSequenceNumber=<null>(default), minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), resultAddress=<null>(default)]
15:27:28.122 WARN  o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: 
org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@791bbe80[correlationID=35312bba-b806-4063-9354-f7925b715089, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noFinalResponsesTest, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), contributor=Pillar2, fileID=<null>(default), minSequenceNumber=<null>(default), maxSequenceNumber=<null>(default), minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), resultAddress=<null>(default)]
          Result: Received event: 70fbea53: GET_AUDIT_TRAILS: FAILED: , Failed to receive responses from all contributors before timeout(500ms). Missing contributors [Pillar1, Pillar2]
15:27:28.146 ERROR o.b.a.g.client.GettingAuditTrails - Failing conversation 'AuditTrailConversationContext{collectionID='TwoPillarCollection', conversationID='70fbea53-0aeb-4cab-bb03-00b63df60dc1', clientID='incompleteSetOfFinalResponsesTest', fileID='null', contributors=[Pillar1, Pillar2], monitor=ConversationEventMonitor{, collectionID='TwoPillarCollection', conversationID='70fbea53', operationType=GET_AUDIT_TRAILS, fileID='null', eventHandler=org.bitrepository.client.TestEventHandler@2b14752f, contributorCompleteEvents=[], contributorFailedEvents=[], failOnComponentFailure=true}, auditTrailInformation='null', state=org.bitrepository.client.conversation.FinishedState@4e60e0ff, checksumPillars=[]}' with exception
org.bitrepository.common.exceptions.UnableToFinishException: Failed to receive responses from all contributors before timeout(500ms). Missing contributors [Pillar1, Pillar2]
	at org.bitrepository.client.conversation.PerformingOperationState.logStateTimeout(PerformingOperationState.java:82)
	at org.bitrepository.client.conversation.GeneralConversationState$TimeoutHandler.run(GeneralConversationState.java:133)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
      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@6844b62f[correlationID=0a76f45c-7e43-4d28-966b-bc8d54f26e4c, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=progressEventsTest, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default)]
          Result: Received event: 0a76f45c: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
        Step: Send a identifyResponse from each of the two pillars
          Result: Received event: 0a76f45c: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 0a76f45c: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2
          Result: Received event: 0a76f45c: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2, Pillar1]
          Result: Received event: 0a76f45c: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for audit trails
          Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@61bfcf43[correlationID=0a76f45c-7e43-4d28-966b-bc8d54f26e4c, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=progressEventsTest, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), contributor=Pillar1, fileID=<null>(default), minSequenceNumber=<null>(default), maxSequenceNumber=<null>(default), minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), resultAddress=<null>(default)]
          Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@2c87e895[correlationID=0a76f45c-7e43-4d28-966b-bc8d54f26e4c, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=progressEventsTest, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), contributor=Pillar2, fileID=<null>(default), minSequenceNumber=<null>(default), maxSequenceNumber=<null>(default), minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), resultAddress=<null>(default)]
        Step: Send a progress accepted response from pillar 1
          Result: Received event: 0a76f45c: GET_AUDIT_TRAILS: PROGRESS: ContributorID Pillar1, GetAuditTrails request accepted
        Step: Send a general progress response from pillar 2
          Result: Received event: 0a76f45c: GET_AUDIT_TRAILS: PROGRESS: ContributorID Pillar2, Still progressing
      Test success: progressEventsTest
      Test starting: verifyAuditTrailClientFromFactory
      Test success: verifyAuditTrailClientFromFactory
    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
      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@37f2dfd6[correlationID=cd8270c2-7764-480a-8d0c-b1712728f6f6, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=collectionIDIncludedInEventsTest, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default)]
          Result: Received event: cd8270c2: 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: cd8270c2: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: cd8270c2: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE
          Result: Received event: cd8270c2: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: cd8270c2: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1], Sending request for audit trails
          Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@55c316d9[correlationID=cd8270c2-7764-480a-8d0c-b1712728f6f6, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=collectionIDIncludedInEventsTest, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), contributor=Pillar1, fileID=<null>(default), minSequenceNumber=<null>(default), maxSequenceNumber=<null>(default), minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), resultAddress=<null>(default)]
        Step: Wait for 1 second
          Result: Received event: cd8270c2: GET_AUDIT_TRAILS: FAILED: , Failed to receive responses from all contributors before timeout(500ms). Missing contributors [Pillar1]
15:27:30.724 ERROR o.b.a.g.client.GettingAuditTrails - Failing conversation 'AuditTrailConversationContext{collectionID='TwoPillarCollection', conversationID='cd8270c2-7764-480a-8d0c-b1712728f6f6', clientID='collectionIDIncludedInEventsTest', fileID='null', contributors=[Pillar1, Pillar2], monitor=ConversationEventMonitor{, collectionID='TwoPillarCollection', conversationID='cd8270c2', operationType=GET_AUDIT_TRAILS, fileID='null', eventHandler=org.bitrepository.client.TestEventHandler@17b6a2c6, contributorCompleteEvents=[], contributorFailedEvents=[cd8270c2: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE], failOnComponentFailure=true}, auditTrailInformation='null', state=org.bitrepository.client.conversation.FinishedState@39aa8400, checksumPillars=[]}' with exception
org.bitrepository.common.exceptions.UnableToFinishException: Failed to receive responses from all contributors before timeout(500ms). Missing contributors [Pillar1]
	at org.bitrepository.client.conversation.PerformingOperationState.logStateTimeout(PerformingOperationState.java:82)
	at org.bitrepository.client.conversation.GeneralConversationState$TimeoutHandler.run(GeneralConversationState.java:133)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
      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@7f72f7cb[correlationID=4bdb40a2-0754-4aa2-9ad6-ecdd2289e3b0, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=conversationTimeoutTest, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default)]
          Result: Received event: 4bdb40a2: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
15:27:31.903 WARN  o.b.c.c.m.CollectionBasedConversationMediator - Failing timed out conversation 4bdb40a2-0754-4aa2-9ad6-ecdd2289e3b0 (Age 998ms)
          Result: Received event: 4bdb40a2: GET_AUDIT_TRAILS: FAILED: , Failing timed out conversation 4bdb40a2-0754-4aa2-9ad6-ecdd2289e3b0
      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@147fc609[correlationID=844a9cbc-529e-4969-997c-e0b6bfbbe0cb, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=identificationFailureTest, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default)]
          Result: Received event: 844a9cbc: 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: 844a9cbc: 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: 844a9cbc: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2
          Result: Received event: 844a9cbc: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
          Result: Received event: 844a9cbc: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar2], Sending request for audit trails
          Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@2c189612[correlationID=844a9cbc-529e-4969-997c-e0b6bfbbe0cb, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=identificationFailureTest, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), contributor=Pillar2, fileID=<null>(default), minSequenceNumber=<null>(default), maxSequenceNumber=<null>(default), minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), resultAddress=<null>(default)]
        Step: Verify that the client continues to the performing phase.
        Step: Send a final response message from contributor2
          Result: Received event: 844a9cbc: GET_AUDIT_TRAILS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false
          Result: Received event: 844a9cbc: GET_AUDIT_TRAILS: FAILED: , Failed operation. Cause(s):
[844a9cbc: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE]
      Test success: identificationFailureTest
      Test starting: identificationNegativeTest
        Description: Verify that the client works correctly when a contributor sends a negative response.
        Step: Start the operation.
          Stimuli: Calling getAuditTrails(null, null, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@629808fc[correlationID=4ebb02ea-0e43-4251-b2b6-ff7f821d9452, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=identificationNegativeTest, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default)]
          Result: Received event: 4ebb02ea: 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: 4ebb02ea: 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: 4ebb02ea: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2
          Result: Received event: 4ebb02ea: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
          Result: Received event: 4ebb02ea: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar2], Sending request for audit trails
          Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@1e306f66[correlationID=4ebb02ea-0e43-4251-b2b6-ff7f821d9452, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=identificationNegativeTest, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), contributor=Pillar2, fileID=<null>(default), minSequenceNumber=<null>(default), maxSequenceNumber=<null>(default), minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), resultAddress=<null>(default)]
        Step: Verify that the client continues to the performing phase.
        Step: Send a final response message from contributor2
          Result: Received event: 4ebb02ea: GET_AUDIT_TRAILS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false
          Result: Received event: 4ebb02ea: GET_AUDIT_TRAILS: FAILED: , Failed operation. Cause(s):
[4ebb02ea: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: IDENTIFICATION_NEGATIVE]
      Test success: identificationNegativeTest
      Test starting: noContributorsRespondingTest
        Description: Tests the the client handles lack of a IdentifyResponse gracefully. More concrete this means that the occurrence of a identification timeout should be handled correctly
        Step: Set a 100 ms timeout for identifying contributors.
        Step: Start the operation.
          Stimuli: Calling getAuditTrails(null, null, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@2afb3317[correlationID=24c96467-1381-405b-b01d-be8d863d97a8, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noContributorsRespondingTest, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default)]
          Result: Received event: 24c96467: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
        Step: Wait for 1 second
          Result: Received event: 24c96467: GET_AUDIT_TRAILS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar1, Pillar2]
          Result: Received event: 24c96467: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor
          Result: Received event: 24c96467: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
          Result: Received event: 24c96467: GET_AUDIT_TRAILS: FAILED: , Unable to continue operation, contributors unavailable.
15:27:34.532 ERROR o.b.a.g.c.IdentifyingAuditTrailContributors - Failing conversation 'AuditTrailConversationContext{collectionID='TwoPillarCollection', conversationID='24c96467-1381-405b-b01d-be8d863d97a8', clientID='noContributorsRespondingTest', fileID='null', contributors=[Pillar1, Pillar2], monitor=ConversationEventMonitor{, collectionID='TwoPillarCollection', conversationID='24c96467', operationType=GET_AUDIT_TRAILS, fileID='null', eventHandler=org.bitrepository.client.TestEventHandler@17b6a2c6, contributorCompleteEvents=[], contributorFailedEvents=[24c96467: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor, 24c96467: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor], failOnComponentFailure=true}, auditTrailInformation='null', state=org.bitrepository.client.conversation.FinishedState@311f2317, checksumPillars=[]}' with exception
org.bitrepository.common.exceptions.UnableToFinishException: Unable to continue operation, contributors unavailable.
	at org.bitrepository.client.conversation.IdentifyingState.completeState(IdentifyingState.java:76)
	at org.bitrepository.client.conversation.GeneralConversationState.changeState(GeneralConversationState.java:147)
	at org.bitrepository.client.conversation.GeneralConversationState.access$100(GeneralConversationState.java:48)
	at org.bitrepository.client.conversation.GeneralConversationState$TimeoutHandler.run(GeneralConversationState.java:134)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
      Test success: noContributorsRespondingTest
          Result: The following messages haven't been handled by the testcase: 
org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@2afb3317[correlationID=24c96467-1381-405b-b01d-be8d863d97a8, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noContributorsRespondingTest, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default)]
15:27:34.535 WARN  o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: 
org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@2afb3317[correlationID=24c96467-1381-405b-b01d-be8d863d97a8, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noContributorsRespondingTest, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default)]
      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@498fd768[correlationID=7d9056a8-639e-41c2-b750-ff1ce590b2bc, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=oneContributorNotRespondingTest, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default)]
          Result: Received event: 7d9056a8: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
        Step: Send a identification response from contributor1.
          Result: Received event: 7d9056a8: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1
        Step: Wait 1 second.
          Result: Received event: 7d9056a8: GET_AUDIT_TRAILS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar2]
          Result: Received event: 7d9056a8: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
          Result: Received event: 7d9056a8: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: 7d9056a8: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1], Sending request for audit trails
          Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@78314ad3[correlationID=7d9056a8-639e-41c2-b750-ff1ce590b2bc, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=oneContributorNotRespondingTest, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), contributor=Pillar1, fileID=<null>(default), minSequenceNumber=<null>(default), maxSequenceNumber=<null>(default), minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), resultAddress=<null>(default)]
        Step: Verify that the client continues to the performing phase.
        Step: Send a final response upload message
          Result: Received event: 7d9056a8: GET_AUDIT_TRAILS: COMPONENT_COMPLETE: ContributorID Pillar1, PartialResult=false
          Result: Received event: 7d9056a8: GET_AUDIT_TRAILS: FAILED: , Failed operation. Cause(s):
[7d9056a8: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor]
      Test success: oneContributorNotRespondingTest
      Test starting: operationTimeoutTest
        Description: Tests the the client handles lack of final responses gracefully.
        Step: Set a 100 ms operation timeout.
        Step: Start the operation
          Stimuli: Calling getAuditTrails(null, null, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@4df0dc7f[correlationID=fa3a3ac1-c349-4ad4-a2cb-ae536769af1e, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=operationTimeoutTest, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default)]
          Result: Received event: fa3a3ac1: 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: fa3a3ac1: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: fa3a3ac1: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE
          Result: Received event: fa3a3ac1: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: fa3a3ac1: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1], Sending request for audit trails
          Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@4bbe1bd1[correlationID=fa3a3ac1-c349-4ad4-a2cb-ae536769af1e, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=operationTimeoutTest, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), contributor=Pillar1, fileID=<null>(default), minSequenceNumber=<null>(default), maxSequenceNumber=<null>(default), minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), resultAddress=<null>(default)]
        Step: Wait for 1 second
          Result: Received event: fa3a3ac1: GET_AUDIT_TRAILS: FAILED: , Failed to receive responses from all contributors before timeout(100ms). Missing contributors [Pillar1]
15:27:35.055 ERROR o.b.a.g.client.GettingAuditTrails - Failing conversation 'AuditTrailConversationContext{collectionID='TwoPillarCollection', conversationID='fa3a3ac1-c349-4ad4-a2cb-ae536769af1e', clientID='operationTimeoutTest', fileID='null', contributors=[Pillar1, Pillar2], monitor=ConversationEventMonitor{, collectionID='TwoPillarCollection', conversationID='fa3a3ac1', operationType=GET_AUDIT_TRAILS, fileID='null', eventHandler=org.bitrepository.client.TestEventHandler@17b6a2c6, contributorCompleteEvents=[], contributorFailedEvents=[fa3a3ac1: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE], failOnComponentFailure=true}, auditTrailInformation='null', state=org.bitrepository.client.conversation.FinishedState@5a336781, checksumPillars=[]}' with exception
org.bitrepository.common.exceptions.UnableToFinishException: Failed to receive responses from all contributors before timeout(100ms). Missing contributors [Pillar1]
	at org.bitrepository.client.conversation.PerformingOperationState.logStateTimeout(PerformingOperationState.java:82)
	at org.bitrepository.client.conversation.GeneralConversationState$TimeoutHandler.run(GeneralConversationState.java:133)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
      Test success: operationTimeoutTest
    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: 56275f94: GET_STATUS: IDENTIFY_REQUEST_SENT: , Identifying contributors for getting status
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetStatusRequest@46ca7c9[correlationID=56275f94-5bbd-40d9-98c0-3d3a02660fe6, collectionID=<null>(default), destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetStatusClientComponentTest-cibuild01, from=getAllStatuses, to=<null>(default), version=30, minVersion=24, auditTrailInformation=]
        Step: Send a identifyResponse from each pillar
          Result: Received event: 56275f94: GET_STATUS: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 56275f94: GET_STATUS: COMPONENT_IDENTIFIED: ContributorID Pillar2
          Result: Received event: 56275f94: GET_STATUS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2]
          Result: Received event: 56275f94: GET_STATUS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending GetStatusRequest
          Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetStatusRequest@41bde31[correlationID=56275f94-5bbd-40d9-98c0-3d3a02660fe6, collectionID=<null>(default), destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetStatusClientComponentTest-cibuild01, from=getAllStatuses, to=<null>(default), version=30, minVersion=24, auditTrailInformation=, contributor=Pillar1]
          Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetStatusRequest@60af81c4[correlationID=56275f94-5bbd-40d9-98c0-3d3a02660fe6, collectionID=<null>(default), destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetStatusClientComponentTest-cibuild01, from=getAllStatuses, to=<null>(default), version=30, minVersion=24, auditTrailInformation=, contributor=Pillar2]
        Step: Send a final response from pillar 1
          Result: Received event: 56275f94: GET_STATUS: COMPONENT_COMPLETE: ContributorID Pillar1, resulting status: org.bitrepository.bitrepositoryelements.ResultingStatus@21fa667a[statusInfo=org.bitrepository.bitrepositoryelements.StatusInfo@58bdc6dc[statusCode=OK, statusText=Everythings fine..], statusTimestamp=2017-06-08T15:27:35.248+02:00]
        Step: Send a final response from pillar 2
          Result: Received event: 56275f94: GET_STATUS: COMPONENT_COMPLETE: ContributorID Pillar2, resulting status: org.bitrepository.bitrepositoryelements.ResultingStatus@2361f828[statusInfo=org.bitrepository.bitrepositoryelements.StatusInfo@3ebaa33c[statusCode=OK, statusText=Everythings fine..], statusTimestamp=2017-06-08T15:27:35.253+02:00]
          Result: Received event: 56275f94: 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: 2ab3512e: GET_STATUS: IDENTIFY_REQUEST_SENT: , Identifying contributors for getting status
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetStatusRequest@b2240cf[correlationID=2ab3512e-94ba-4bb4-8345-c8e05cf549d1, collectionID=<null>(default), destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetStatusClientComponentTest-cibuild01, from=incompleteSetOfIdendifyResponses, to=<null>(default), version=30, minVersion=24, auditTrailInformation=]
        Step: Send a identifyResponse from pillar 1
          Result: Received event: 2ab3512e: GET_STATUS: COMPONENT_IDENTIFIED: ContributorID Pillar1
        Step: Wait for timeout event
          Result: Received event: 2ab3512e: GET_STATUS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar2]
          Result: Received event: 2ab3512e: GET_STATUS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
          Result: Received event: 2ab3512e: GET_STATUS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: 2ab3512e: GET_STATUS: REQUEST_SENT: ContributorID [Pillar1], Sending GetStatusRequest
          Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetStatusRequest@37546243[correlationID=2ab3512e-94ba-4bb4-8345-c8e05cf549d1, collectionID=<null>(default), destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetStatusClientComponentTest-cibuild01, from=incompleteSetOfIdendifyResponses, to=<null>(default), version=30, minVersion=24, auditTrailInformation=, contributor=Pillar1]
      Test success: incompleteSetOfIdendifyResponses
      Test starting: verifyGetStatusClientFromFactory
      Test success: verifyGetStatusClientFromFactory
    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@4d810b08[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@c1089bb[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], 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@2286a421[checksumType=SHA1, checksumSalt=<null>(default), otherChecksumType=<null>(default)], file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, 10, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@2005dc6b[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@c1089bb[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], 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@2286a421[checksumType=SHA1, checksumSalt=<null>(default), otherChecksumType=<null>(default)], org.bitrepository.client.TestEventHandler@65994a28, null
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileRequest@71f15824[correlationID=51e961c4-33d1-4db0-8569-fdd125213039, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-ReplaceFileClientComponentTest-cibuild01, from=replaceClientIdentificationTimeout, to=Pillar1, version=30, minVersion=24, auditTrailInformation=<null>(default), fileID=default-test-file.txt, fileSize=<null>(default)]
          Result: Received event: 51e961c4: 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: 51e961c4: 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: 51e961c4: REPLACE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor
          Result: Received event: 51e961c4: REPLACE_FILE for file default-test-file.txt: FAILED: , Unable to continue operation, contributors unavailable.
15:27:36.839 ERROR o.b.m.r.c.IdentifyPillarsForReplaceFile - Failing conversation 'ReplaceFileConversationContext{collectionID='TwoPillarCollection', conversationID='51e961c4-33d1-4db0-8569-fdd125213039', clientID='replaceClientIdentificationTimeout', fileID='default-test-file.txt', contributors=[Pillar1], monitor=ConversationEventMonitor{, collectionID='TwoPillarCollection', conversationID='51e961c4', operationType=REPLACE_FILE, fileID='default-test-file.txt', eventHandler=org.bitrepository.client.TestEventHandler@65994a28, contributorCompleteEvents=[], contributorFailedEvents=[51e961c4: REPLACE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor], failOnComponentFailure=true}, auditTrailInformation='null', state=org.bitrepository.client.conversation.FinishedState@7f1be825, checksumPillars=[]}' with exception
org.bitrepository.common.exceptions.UnableToFinishException: Unable to continue operation, contributors unavailable.
	at org.bitrepository.client.conversation.IdentifyingState.completeState(IdentifyingState.java:76)
	at org.bitrepository.client.conversation.GeneralConversationState.changeState(GeneralConversationState.java:147)
	at org.bitrepository.client.conversation.GeneralConversationState.access$100(GeneralConversationState.java:48)
	at org.bitrepository.client.conversation.GeneralConversationState$TimeoutHandler.run(GeneralConversationState.java:134)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
      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@616092b2[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1241d57a[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], 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@453d6b04[checksumType=SHA1, checksumSalt=<null>(default), otherChecksumType=<null>(default)], file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, 10, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@10e0cfed[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1241d57a[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], 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@453d6b04[checksumType=SHA1, checksumSalt=<null>(default), otherChecksumType=<null>(default)], org.bitrepository.client.TestEventHandler@75f02a41, null
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileRequest@6986cb80[correlationID=7e3cdc76-38b0-4244-8342-ef6543ce8155, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-ReplaceFileClientComponentTest-cibuild01, from=replaceClientOperationTimeout, to=Pillar1, version=30, minVersion=24, auditTrailInformation=<null>(default), fileID=default-test-file.txt, fileSize=<null>(default)]
          Result: Received event: 7e3cdc76: 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: 7e3cdc76: REPLACE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 7e3cdc76: REPLACE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: 7e3cdc76: 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@25925217[correlationID=7e3cdc76-38b0-4244-8342-ef6543ce8155, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-ReplaceFileClientComponentTest-cibuild01, from=replaceClientOperationTimeout, to=Pillar1, version=30, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@616092b2[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1241d57a[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], 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@453d6b04[checksumType=SHA1, checksumSalt=<null>(default), otherChecksumType=<null>(default)], fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=10, checksumDataForNewFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@10e0cfed[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1241d57a[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], 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@453d6b04[checksumType=SHA1, checksumSalt=<null>(default), otherChecksumType=<null>(default)]]
        Step: Validate the steps of the ReplaceClient by going through the events.
        Step: Do not respond. Just await the timeout.
          Result: Received event: 7e3cdc76: REPLACE_FILE for file default-test-file.txt: FAILED: , Failed to receive responses from all contributors before timeout(100ms). Missing contributors [Pillar1]
15:27:37.053 ERROR o.b.m.r.conversation.ReplacingFile - Failing conversation 'ReplaceFileConversationContext{collectionID='TwoPillarCollection', conversationID='7e3cdc76-38b0-4244-8342-ef6543ce8155', clientID='replaceClientOperationTimeout', fileID='default-test-file.txt', contributors=[Pillar1], monitor=ConversationEventMonitor{, collectionID='TwoPillarCollection', conversationID='7e3cdc76', operationType=REPLACE_FILE, fileID='default-test-file.txt', eventHandler=org.bitrepository.client.TestEventHandler@75f02a41, contributorCompleteEvents=[], contributorFailedEvents=[], failOnComponentFailure=true}, auditTrailInformation='null', state=org.bitrepository.client.conversation.FinishedState@d0e42c7, checksumPillars=[]}' with exception
org.bitrepository.common.exceptions.UnableToFinishException: Failed to receive responses from all contributors before timeout(100ms). Missing contributors [Pillar1]
	at org.bitrepository.client.conversation.PerformingOperationState.logStateTimeout(PerformingOperationState.java:82)
	at org.bitrepository.client.conversation.GeneralConversationState$TimeoutHandler.run(GeneralConversationState.java:133)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
      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@4bec43d4[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@43786fd8[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], 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@3b666e5f[checksumType=SHA1, checksumSalt=<null>(default), otherChecksumType=<null>(default)], file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, 0, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@6448989[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@43786fd8[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], 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@3b666e5f[checksumType=SHA1, checksumSalt=<null>(default), otherChecksumType=<null>(default)], org.bitrepository.client.TestEventHandler@2f9f9876, null
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileRequest@2f9934f2[correlationID=64ff99cd-be82-44e4-bacd-a6528d58a8e0, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-ReplaceFileClientComponentTest-cibuild01, from=replaceClientPillarFailed, to=Pillar1, version=30, minVersion=24, auditTrailInformation=<null>(default), fileID=default-test-file.txt, fileSize=<null>(default)]
          Result: Received event: 64ff99cd: 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: 64ff99cd: REPLACE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 64ff99cd: REPLACE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: 64ff99cd: 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@5af7e70[correlationID=64ff99cd-be82-44e4-bacd-a6528d58a8e0, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-ReplaceFileClientComponentTest-cibuild01, from=replaceClientPillarFailed, to=Pillar1, version=30, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@4bec43d4[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@43786fd8[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], 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@3b666e5f[checksumType=SHA1, checksumSalt=<null>(default), otherChecksumType=<null>(default)], fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@6448989[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@43786fd8[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], 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@3b666e5f[checksumType=SHA1, checksumSalt=<null>(default), otherChecksumType=<null>(default)]]
        Step: Validate the steps of the ReplaceClient by going through the events.
        Step: Send a failed response message to the ReplaceClient.
          Result: Received event: 64ff99cd: REPLACE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE, Verifying that a failure can be understood!
          Result: Received event: 64ff99cd: REPLACE_FILE for file default-test-file.txt: FAILED: , Failed operation. Cause(s):
[64ff99cd: 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@357ea46e[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@62a01f1b[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], 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@11e97dff[checksumType=SHA1, checksumSalt=<null>(default), otherChecksumType=<null>(default)], file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, 10, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@3a5537e6[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@62a01f1b[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], 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@11e97dff[checksumType=SHA1, checksumSalt=<null>(default), otherChecksumType=<null>(default)], org.bitrepository.client.TestEventHandler@7a48b916, null
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileRequest@18722983[correlationID=64317802-b508-4b5d-b9b8-266ec1d72ed8, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-ReplaceFileClientComponentTest-cibuild01, from=replaceClientTester, to=Pillar1, version=30, minVersion=24, auditTrailInformation=<null>(default), fileID=default-test-file.txt, fileSize=<null>(default)]
          Result: Received event: 64317802: 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: 64317802: REPLACE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 64317802: REPLACE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: 64317802: 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@51574c53[correlationID=64317802-b508-4b5d-b9b8-266ec1d72ed8, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-ReplaceFileClientComponentTest-cibuild01, from=replaceClientTester, to=Pillar1, version=30, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@357ea46e[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@62a01f1b[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], 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@11e97dff[checksumType=SHA1, checksumSalt=<null>(default), otherChecksumType=<null>(default)], fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=10, checksumDataForNewFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@3a5537e6[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@62a01f1b[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], 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@11e97dff[checksumType=SHA1, checksumSalt=<null>(default), otherChecksumType=<null>(default)]]
        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: 64317802: 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: 64317802: REPLACE_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, checksum for new file: 'org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@3a5537e6[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@62a01f1b[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], 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: 64317802: 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@61d01566[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@568d439b[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], 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@1ef4aafe[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@568d439b[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], 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@6ac6d421[checksumType=MD5, checksumSalt={-86}, otherChecksumType=<null>(default)], org.bitrepository.client.TestEventHandler@bdc973a, null
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileRequest@37718c41[correlationID=d7a7f359-b5f7-479d-b565-934b8125e9c3, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-ReplaceFileClientComponentTest-cibuild01, from=saltedReturnChecksumsForNewFileWithChecksumPillar, to=Pillar1, version=30, minVersion=24, auditTrailInformation=<null>(default), fileID=default-test-file.txt, fileSize=<null>(default)]
          Result: Received event: d7a7f359: 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: d7a7f359: REPLACE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: d7a7f359: REPLACE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: d7a7f359: 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@50d2d97b[correlationID=d7a7f359-b5f7-479d-b565-934b8125e9c3, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-ReplaceFileClientComponentTest-cibuild01, from=saltedReturnChecksumsForNewFileWithChecksumPillar, to=Pillar1, version=30, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@61d01566[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@568d439b[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], checksumRequestForExistingFile=<null>(default), fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@1ef4aafe[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@568d439b[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], checksumRequestForNewFile=<null>(default)]
      Test success: saltedReturnChecksumsForNewFileWithChecksumPillar
      Test starting: verifyReplaceFileClientFromFactory
        Description: Testing the initialization through the ModifyComponentFactory.
        Step: Use the ModifyComponentFactory to instantiate a ReplaceFileClient.
      Test success: verifyReplaceFileClientFromFactory
    Starting testcase UnexpectedResponseExceptionTest
      Test starting: testUnexpectedResponse
        Description: Test the instantiation of the exception
        Step: Setup
        Step: Try to throw such an exception
        Step: Throw the exception with an embedded exception
      Test success: testUnexpectedResponse
    Starting testcase CommandLineTest
      Test starting: argumentsTesterUnknownArgument
        Description: Test the handling of arguments by the CommandLineArgumentHandler.
        Step: Validate arguments without any options.
      Test success: argumentsTesterUnknownArgument
      Test starting: argumentsTesterWrongArgument
        Description: Test the handling of arguments by the CommandLineArgumentHandler.
        Step: Validate the default options
      Test success: argumentsTesterWrongArgument
      Test starting: newArgumentTester
        Description: Test the handling of a new argument.
        Step: Test the option
      Test success: newArgumentTester
    Starting testcase 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 operation should be performed. If undefined the operation is performed on all pillars.
-l [OPTIONAL] The location where the file should be placed (either total path or directory). If no argument, then the file is placed 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 operation should be performed. If undefined the operation is performed on all pillars.
-l [OPTIONAL] The location where the file should be placed (either total path or directory). If no argument, then the file is placed 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: Random1496928458779pillar 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@1a00979c[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], org.bitrepository.client.TestEventHandler@3f84455d, TEST-AUDIT-TRAIL)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@3a59f5fd[correlationID=fca9070c-086b-498e-a89e-4f51cc4fd0c0, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=defaultReturnChecksumsWithChecksumPillar, to=<null>(default), version=30, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, fileID=default-test-file.txt, fileSize=0]
          Result: Received event: fca9070c: 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: fca9070c: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
        Step: Send an normal identification response from pillar2.
          Result: Received event: fca9070c: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
          Result: Received event: fca9070c: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2]
          Result: Received event: fca9070c: 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@bf2c325[correlationID=fca9070c-086b-498e-a89e-4f51cc4fd0c0, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=defaultReturnChecksumsWithChecksumPillar, to=<null>(default), version=30, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>(default), checksumRequestForNewFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1a00979c[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)]]
          Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@70f96d97[correlationID=fca9070c-086b-498e-a89e-4f51cc4fd0c0, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=defaultReturnChecksumsWithChecksumPillar, to=<null>(default), version=30, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, pillarID=Pillar2, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>(default), checksumRequestForNewFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1a00979c[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)]]
      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@33f997fe, TEST-AUDIT-TRAIL)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@1faca978[correlationID=03e9ff21-a07a-42a5-9731-570f6e57b9c5, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=fileExistsOnPillarChecksumFromPillarNoClientChecksum, to=<null>(default), version=30, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, fileID=default-test-file.txt, fileSize=0]
          Result: Received event: 03e9ff21: 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: 03e9ff21: 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@2d28a33[responseCode=DUPLICATE_FILE_FAILURE, responseText=Testing the handling of 'DUPLICATE FILE' identification.] (existing file checksum does not match)
          Result: Received event: 03e9ff21: 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
15:27:39.218 ERROR o.b.m.p.c.IdentifyPillarsForPutFile - Failing conversation 'PutFileConversationContext{collectionID='TwoPillarCollection', conversationID='03e9ff21-a07a-42a5-9731-570f6e57b9c5', clientID='fileExistsOnPillarChecksumFromPillarNoClientChecksum', fileID='default-test-file.txt', contributors=[Pillar1, Pillar2], monitor=ConversationEventMonitor{, collectionID='TwoPillarCollection', conversationID='03e9ff21', operationType=PUT_FILE, fileID='default-test-file.txt', eventHandler=org.bitrepository.client.TestEventHandler@33f997fe, contributorCompleteEvents=[], contributorFailedEvents=[03e9ff21: 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@2d28a33[responseCode=DUPLICATE_FILE_FAILURE, responseText=Testing the handling of 'DUPLICATE FILE' identification.] (existing file checksum does not match)], failOnComponentFailure=true}, auditTrailInformation='TEST-AUDIT-TRAIL', state=org.bitrepository.client.conversation.FinishedState@1d167768, checksumPillars=[]}' with exception
org.bitrepository.common.exceptions.UnableToFinishException: Can not put file default-test-file.txt, as an different file already exists on pillar Pillar1
	at org.bitrepository.modify.putfile.conversation.IdentifyPillarsForPutFile.handleFailureResponse(IdentifyPillarsForPutFile.java:76)
	at org.bitrepository.client.conversation.IdentifyingState.processMessage(IdentifyingState.java:60)
	at org.bitrepository.client.conversation.GeneralConversationState.handleMessage(GeneralConversationState.java:110)
	at org.bitrepository.client.conversation.StateBasedConversation.onMessage(StateBasedConversation.java:53)
	at org.bitrepository.client.conversation.mediator.CollectionBasedConversationMediator.onMessage(CollectionBasedConversationMediator.java:136)
	at org.bitrepository.protocol.messagebus.SimpleMessageBus.lambda$sendMessage$0(SimpleMessageBus.java:73)
	at java.lang.Iterable.forEach(Iterable.java:75)
	at org.bitrepository.protocol.messagebus.SimpleMessageBus.sendMessage(SimpleMessageBus.java:73)
	at org.bitrepository.modify.putfile.PutFileClientComponentTest.fileExistsOnPillarChecksumFromPillarNoClientChecksum(PutFileClientComponentTest.java:492)
	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:498)
	at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:86)
	at org.testng.internal.Invoker.invokeMethod(Invoker.java:643)
	at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:820)
	at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1128)
	at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:129)
	at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:112)
	at org.testng.TestRunner.privateRun(TestRunner.java:782)
	at org.testng.TestRunner.run(TestRunner.java:632)
	at org.testng.SuiteRunner.runTest(SuiteRunner.java:366)
	at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:361)
	at org.testng.SuiteRunner.privateRun(SuiteRunner.java:319)
	at org.testng.SuiteRunner.run(SuiteRunner.java:268)
	at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
	at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
	at org.testng.TestNG.runSuitesSequentially(TestNG.java:1244)
	at org.testng.TestNG.runSuitesLocally(TestNG.java:1169)
	at org.testng.TestNG.run(TestNG.java:1064)
	at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:115)
	at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:204)
	at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:107)
	at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:112)
	at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
      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@60528633[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@5d5599e2[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={-70}, calculationTimestamp=2017-06-08T15:27:39.381+02:00], null, org.bitrepository.client.TestEventHandler@64680729, TEST-AUDIT-TRAIL)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@785c354a[correlationID=baa7763a-ed44-4749-b799-32ddcef0cf19, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=fileExistsOnPillarDifferentChecksumFromPillar, to=<null>(default), version=30, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, fileID=default-test-file.txt, fileSize=0]
          Result: Received event: baa7763a: 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: baa7763a: 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@5955544c[responseCode=DUPLICATE_FILE_FAILURE, responseText=Testing the handling of 'DUPLICATE FILE' identification.] (existing file checksum does not match)
          Result: Received event: baa7763a: 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
15:27:39.386 ERROR o.b.m.p.c.IdentifyPillarsForPutFile - Failing conversation 'PutFileConversationContext{collectionID='TwoPillarCollection', conversationID='baa7763a-ed44-4749-b799-32ddcef0cf19', clientID='fileExistsOnPillarDifferentChecksumFromPillar', fileID='default-test-file.txt', contributors=[Pillar1, Pillar2], monitor=ConversationEventMonitor{, collectionID='TwoPillarCollection', conversationID='baa7763a', operationType=PUT_FILE, fileID='default-test-file.txt', eventHandler=org.bitrepository.client.TestEventHandler@64680729, contributorCompleteEvents=[], contributorFailedEvents=[baa7763a: 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@5955544c[responseCode=DUPLICATE_FILE_FAILURE, responseText=Testing the handling of 'DUPLICATE FILE' identification.] (existing file checksum does not match)], failOnComponentFailure=true}, auditTrailInformation='TEST-AUDIT-TRAIL', state=org.bitrepository.client.conversation.FinishedState@403adc49, checksumPillars=[]}' with exception
org.bitrepository.common.exceptions.UnableToFinishException: Can not put file default-test-file.txt, as an different file already exists on pillar Pillar1
	at org.bitrepository.modify.putfile.conversation.IdentifyPillarsForPutFile.handleFailureResponse(IdentifyPillarsForPutFile.java:76)
	at org.bitrepository.client.conversation.IdentifyingState.processMessage(IdentifyingState.java:60)
	at org.bitrepository.client.conversation.GeneralConversationState.handleMessage(GeneralConversationState.java:110)
	at org.bitrepository.client.conversation.StateBasedConversation.onMessage(StateBasedConversation.java:53)
	at org.bitrepository.client.conversation.mediator.CollectionBasedConversationMediator.onMessage(CollectionBasedConversationMediator.java:136)
	at org.bitrepository.protocol.messagebus.SimpleMessageBus.lambda$sendMessage$0(SimpleMessageBus.java:73)
	at java.lang.Iterable.forEach(Iterable.java:75)
	at org.bitrepository.protocol.messagebus.SimpleMessageBus.sendMessage(SimpleMessageBus.java:73)
	at org.bitrepository.modify.putfile.PutFileClientComponentTest.fileExistsOnPillarDifferentChecksumFromPillar(PutFileClientComponentTest.java:401)
	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:498)
	at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:86)
	at org.testng.internal.Invoker.invokeMethod(Invoker.java:643)
	at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:820)
	at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1128)
	at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:129)
	at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:112)
	at org.testng.TestRunner.privateRun(TestRunner.java:782)
	at org.testng.TestRunner.run(TestRunner.java:632)
	at org.testng.SuiteRunner.runTest(SuiteRunner.java:366)
	at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:361)
	at org.testng.SuiteRunner.privateRun(SuiteRunner.java:319)
	at org.testng.SuiteRunner.run(SuiteRunner.java:268)
	at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
	at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
	at org.testng.TestNG.runSuitesSequentially(TestNG.java:1244)
	at org.testng.TestNG.runSuitesLocally(TestNG.java:1169)
	at org.testng.TestNG.run(TestNG.java:1064)
	at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:115)
	at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:204)
	at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:107)
	at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:112)
	at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
      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@50383f03, TEST-AUDIT-TRAIL)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@4b37b02a[correlationID=0110fecf-1341-4c6e-a998-a7db85968f2b, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=fileExistsOnPillarNoChecksumFromPillar, to=<null>(default), version=30, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, fileID=default-test-file.txt, fileSize=0]
          Result: Received event: 0110fecf: 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: 0110fecf: 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@17171d41[responseCode=DUPLICATE_FILE_FAILURE, responseText=Testing the handling of 'DUPLICATE FILE' identification.]
          Result: Received event: 0110fecf: 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
15:27:39.533 ERROR o.b.m.p.c.IdentifyPillarsForPutFile - Failing conversation 'PutFileConversationContext{collectionID='TwoPillarCollection', conversationID='0110fecf-1341-4c6e-a998-a7db85968f2b', clientID='fileExistsOnPillarNoChecksumFromPillar', fileID='default-test-file.txt', contributors=[Pillar1, Pillar2], monitor=ConversationEventMonitor{, collectionID='TwoPillarCollection', conversationID='0110fecf', operationType=PUT_FILE, fileID='default-test-file.txt', eventHandler=org.bitrepository.client.TestEventHandler@50383f03, contributorCompleteEvents=[], contributorFailedEvents=[0110fecf: 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@17171d41[responseCode=DUPLICATE_FILE_FAILURE, responseText=Testing the handling of 'DUPLICATE FILE' identification.]], failOnComponentFailure=true}, auditTrailInformation='TEST-AUDIT-TRAIL', state=org.bitrepository.client.conversation.FinishedState@1df5926b, checksumPillars=[]}' with exception
org.bitrepository.common.exceptions.UnableToFinishException: Can not put file default-test-file.txt, as an file already exists on pillar Pillar1
	at org.bitrepository.modify.putfile.conversation.IdentifyPillarsForPutFile.handleFailureResponse(IdentifyPillarsForPutFile.java:84)
	at org.bitrepository.client.conversation.IdentifyingState.processMessage(IdentifyingState.java:60)
	at org.bitrepository.client.conversation.GeneralConversationState.handleMessage(GeneralConversationState.java:110)
	at org.bitrepository.client.conversation.StateBasedConversation.onMessage(StateBasedConversation.java:53)
	at org.bitrepository.client.conversation.mediator.CollectionBasedConversationMediator.onMessage(CollectionBasedConversationMediator.java:136)
	at org.bitrepository.protocol.messagebus.SimpleMessageBus.lambda$sendMessage$0(SimpleMessageBus.java:73)
	at java.lang.Iterable.forEach(Iterable.java:75)
	at org.bitrepository.protocol.messagebus.SimpleMessageBus.sendMessage(SimpleMessageBus.java:73)
	at org.bitrepository.modify.putfile.PutFileClientComponentTest.fileExistsOnPillarNoChecksumFromPillar(PutFileClientComponentTest.java:363)
	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:498)
	at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:86)
	at org.testng.internal.Invoker.invokeMethod(Invoker.java:643)
	at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:820)
	at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1128)
	at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:129)
	at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:112)
	at org.testng.TestRunner.privateRun(TestRunner.java:782)
	at org.testng.TestRunner.run(TestRunner.java:632)
	at org.testng.SuiteRunner.runTest(SuiteRunner.java:366)
	at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:361)
	at org.testng.SuiteRunner.privateRun(SuiteRunner.java:319)
	at org.testng.SuiteRunner.run(SuiteRunner.java:268)
	at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
	at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
	at org.testng.TestNG.runSuitesSequentially(TestNG.java:1244)
	at org.testng.TestNG.runSuitesLocally(TestNG.java:1169)
	at org.testng.TestNG.run(TestNG.java:1064)
	at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:115)
	at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:204)
	at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:107)
	at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:112)
	at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
      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@9726eda, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@153cffb8[correlationID=258d261b-9613-40ef-9c61-7922031f3067, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=noPillarsResponding, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), fileID=default-test-file.txt, fileSize=0]
          Result: Received event: 258d261b: 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: 258d261b: 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: 258d261b: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor
          Result: Received event: 258d261b: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
          Result: Received event: 258d261b: PUT_FILE for file default-test-file.txt: FAILED: , Unable to continue operation, contributors unavailable.
15:27:39.781 ERROR o.b.m.p.c.IdentifyPillarsForPutFile - Failing conversation 'PutFileConversationContext{collectionID='TwoPillarCollection', conversationID='258d261b-9613-40ef-9c61-7922031f3067', clientID='noPillarsResponding', fileID='default-test-file.txt', contributors=[Pillar1, Pillar2], monitor=ConversationEventMonitor{, collectionID='TwoPillarCollection', conversationID='258d261b', operationType=PUT_FILE, fileID='default-test-file.txt', eventHandler=org.bitrepository.client.TestEventHandler@9726eda, contributorCompleteEvents=[], contributorFailedEvents=[258d261b: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor, 258d261b: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor], failOnComponentFailure=true}, auditTrailInformation='null', state=org.bitrepository.client.conversation.FinishedState@4cc03388, checksumPillars=[]}' with exception
org.bitrepository.common.exceptions.UnableToFinishException: Unable to continue operation, contributors unavailable.
	at org.bitrepository.client.conversation.IdentifyingState.completeState(IdentifyingState.java:76)
	at org.bitrepository.client.conversation.GeneralConversationState.changeState(GeneralConversationState.java:147)
	at org.bitrepository.client.conversation.GeneralConversationState.access$100(GeneralConversationState.java:48)
	at org.bitrepository.client.conversation.GeneralConversationState$TimeoutHandler.run(GeneralConversationState.java:134)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
      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@7da2f81, TEST-AUDIT-TRAIL)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@146e6f97[correlationID=b012fc5a-da04-4c42-9653-8573e7a0a1b2, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=noReturnChecksumsWithChecksumPillar, to=<null>(default), version=30, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, fileID=default-test-file.txt, fileSize=0]
          Result: Received event: b012fc5a: 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: b012fc5a: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
        Step: Send an normal identification response from pillar2.
          Result: Received event: b012fc5a: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
          Result: Received event: b012fc5a: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2]
          Result: Received event: b012fc5a: 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@52e68f4a[correlationID=b012fc5a-da04-4c42-9653-8573e7a0a1b2, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=noReturnChecksumsWithChecksumPillar, to=<null>(default), version=30, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>(default), checksumRequestForNewFile=<null>(default)]
          Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@35935056[correlationID=b012fc5a-da04-4c42-9653-8573e7a0a1b2, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=noReturnChecksumsWithChecksumPillar, to=<null>(default), version=30, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, pillarID=Pillar2, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>(default), checksumRequestForNewFile=<null>(default)]
      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@65fe5b12, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@1138988e[correlationID=0cfe9c8d-255b-4e40-be3f-cf51ad3ce487, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=normalPutFile, to=Pillar1, version=30, minVersion=24, auditTrailInformation=<null>(default), fileID=default-test-file.txt, fileSize=0]
          Result: Received event: 0cfe9c8d: 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: 0cfe9c8d: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 0cfe9c8d: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: 0cfe9c8d: 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@5f447a57[correlationID=0cfe9c8d-255b-4e40-be3f-cf51ad3ce487, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=normalPutFile, to=Pillar1, version=30, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>(default), checksumRequestForNewFile=<null>(default)]
        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: 0cfe9c8d: 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: 0cfe9c8d: PUT_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, requestedChecksumResult=null
          Result: Received event: 0cfe9c8d: PUT_FILE for file default-test-file.txt: COMPLETE: 
      Test success: normalPutFile
      Test starting: onePillarPutRetryFailure
        Reference: <a href=https://sbforge.org/jira/browse/BITMAG-810>BITMAG-810 Reference client should be able to retry failed file transfers</a>
        Description: Tests that a putfile attempt failing due to FILE_TRANSFER_FAILURE is only attempted the maximum allowed attempts
        Added fixture: Sets the identification timeout to 3 sec, allow two retries and only register one pillar.
        Step: Request the putting of a file through the PutClient
          Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, null, org.bitrepository.client.TestEventHandler@1ffdb733, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@98a8418[correlationID=0ed86418-3ed2-4847-b167-0f642867fbc0, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarPutRetryFailure, to=Pillar1, version=30, minVersion=24, auditTrailInformation=<null>(default), fileID=default-test-file.txt, fileSize=0]
          Result: Received event: 0ed86418: 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: 0ed86418: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 0ed86418: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: 0ed86418: 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@1987ba29[correlationID=0ed86418-3ed2-4847-b167-0f642867fbc0, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarPutRetryFailure, to=Pillar1, version=30, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>(default), checksumRequestForNewFile=<null>(default)]
        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@2c7d64c1[correlationID=0ed86418-3ed2-4847-b167-0f642867fbc0, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarPutRetryFailure, to=Pillar1, version=30, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>(default), checksumRequestForNewFile=<null>(default)]
          Result: Received event: 0ed86418: 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@49b9aab1[correlationID=0ed86418-3ed2-4847-b167-0f642867fbc0, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarPutRetryFailure, to=Pillar1, version=30, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>(default), checksumRequestForNewFile=<null>(default)]
          Result: Received event: 0ed86418: 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: 0ed86418: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FILE_TRANSFER_FAILURE
          Result: Received event: 0ed86418: PUT_FILE for file default-test-file.txt: FAILED: , Failed operation. Cause(s):
[0ed86418: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FILE_TRANSFER_FAILURE]
      Test success: onePillarPutRetryFailure
      Test starting: onePillarPutRetrySuccess
        Reference: <a href=https://sbforge.org/jira/browse/BITMAG-810>BITMAG-810 Reference client should be able to retry failed file transfers</a>
        Description: Tests the handling of a failed transmission when retry is allowed
        Added fixture: Sets the identification timeout to 3 sec, allow two retries and only register one pillar.
        Step: Request the putting of a file through the PutClient
          Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, null, org.bitrepository.client.TestEventHandler@269e0783, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@47e4aa8d[correlationID=8b0d6fe8-b467-4bfb-8f46-a0ae464ba2c9, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarPutRetrySuccess, to=Pillar1, version=30, minVersion=24, auditTrailInformation=<null>(default), fileID=default-test-file.txt, fileSize=0]
          Result: Received event: 8b0d6fe8: 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: 8b0d6fe8: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 8b0d6fe8: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: 8b0d6fe8: 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@434268fd[correlationID=8b0d6fe8-b467-4bfb-8f46-a0ae464ba2c9, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarPutRetrySuccess, to=Pillar1, version=30, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>(default), checksumRequestForNewFile=<null>(default)]
        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@1536cd09[correlationID=8b0d6fe8-b467-4bfb-8f46-a0ae464ba2c9, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarPutRetrySuccess, to=Pillar1, version=30, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>(default), checksumRequestForNewFile=<null>(default)]
          Result: Received event: 8b0d6fe8: 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: 8b0d6fe8: PUT_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, requestedChecksumResult=null
          Result: Received event: 8b0d6fe8: PUT_FILE for file default-test-file.txt: COMPLETE: 
      Test success: onePillarPutRetrySuccess
      Test starting: onePillarRespondingWithPartialPutAllowed
        Reference: <a href=https://sbforge.org/jira/browse/BITMAG-598>BITMAG-598 It should be possible to putFiles, even though only a subset of the pillars are available</a>
        Description: Tests the handling of missing identification responses from one pillar, when partial put are allowed
        Added fixture: Sets the identification timeout to 100 ms and allow partial puts.
        Step: Request the putting of a file through the PutClient
          Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, null, org.bitrepository.client.TestEventHandler@12d26a7, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@4477e6d3[correlationID=fe34a870-965f-43ec-a9ea-4e80c8bafaae, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarRespondingWithPartialPutAllowed, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), fileID=default-test-file.txt, fileSize=0]
          Result: Received event: fe34a870: 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: fe34a870: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
        Step: Await the timeout.
          Result: Received event: fe34a870: 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: fe34a870: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
          Result: Received event: fe34a870: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: fe34a870: 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@58920629[correlationID=fe34a870-965f-43ec-a9ea-4e80c8bafaae, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarRespondingWithPartialPutAllowed, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>(default), checksumRequestForNewFile=<null>(default)]
        Step: The client should proceed to send a putFileOperation request to the responding pillar.
        Step: Send a pillar complete event
          Result: Received event: fe34a870: PUT_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, requestedChecksumResult=null
          Result: Received event: fe34a870: PUT_FILE for file default-test-file.txt: FAILED: , Failed operation. Cause(s):
[fe34a870: 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@5e9d7b78, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@520021aa[correlationID=7a514710-8aa5-4a83-9d21-9224a364d85c, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarRespondingWithPartialPutDisallowed, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), fileID=default-test-file.txt, fileSize=0]
          Result: Received event: 7a514710: 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: 7a514710: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
        Step: Await the timeout.
          Result: Received event: 7a514710: 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: 7a514710: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
          Result: Received event: 7a514710: PUT_FILE for file default-test-file.txt: FAILED: , Unable to continue operation, contributors unavailable.
15:27:40.812 ERROR o.b.m.p.c.IdentifyPillarsForPutFile - Failing conversation 'PutFileConversationContext{collectionID='TwoPillarCollection', conversationID='7a514710-8aa5-4a83-9d21-9224a364d85c', clientID='onePillarRespondingWithPartialPutDisallowed', fileID='default-test-file.txt', contributors=[Pillar1, Pillar2], monitor=ConversationEventMonitor{, collectionID='TwoPillarCollection', conversationID='7a514710', operationType=PUT_FILE, fileID='default-test-file.txt', eventHandler=org.bitrepository.client.TestEventHandler@5e9d7b78, contributorCompleteEvents=[], contributorFailedEvents=[7a514710: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor], failOnComponentFailure=true}, auditTrailInformation='null', state=org.bitrepository.client.conversation.FinishedState@78e897de, checksumPillars=[]}' with exception
org.bitrepository.common.exceptions.UnableToFinishException: Unable to continue operation, contributors unavailable.
	at org.bitrepository.client.conversation.IdentifyingState.completeState(IdentifyingState.java:76)
	at org.bitrepository.client.conversation.GeneralConversationState.changeState(GeneralConversationState.java:147)
	at org.bitrepository.client.conversation.GeneralConversationState.access$100(GeneralConversationState.java:48)
	at org.bitrepository.client.conversation.GeneralConversationState$TimeoutHandler.run(GeneralConversationState.java:134)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
      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@51dd465a, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@2c7131af[correlationID=ce0f61c1-9d1f-4b76-a746-23f7f4c0a836, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=putClientOperationTimeout, to=Pillar1, version=30, minVersion=24, auditTrailInformation=<null>(default), fileID=default-test-file.txt, fileSize=0]
          Result: Received event: ce0f61c1: 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: ce0f61c1: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: ce0f61c1: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: ce0f61c1: 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@97c920b[correlationID=ce0f61c1-9d1f-4b76-a746-23f7f4c0a836, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=putClientOperationTimeout, to=Pillar1, version=30, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>(default), checksumRequestForNewFile=<null>(default)]
        Step: Validate the steps of the PutClient by going through the events.
        Step: Do not respond. Just await the timeout.
          Result: Received event: ce0f61c1: PUT_FILE for file default-test-file.txt: FAILED: , Failed to receive responses from all contributors before timeout(100ms). Missing contributors [Pillar1]
15:27:41.017 ERROR o.b.m.p.conversation.PuttingFile - Failing conversation 'PutFileConversationContext{collectionID='TwoPillarCollection', conversationID='ce0f61c1-9d1f-4b76-a746-23f7f4c0a836', clientID='putClientOperationTimeout', fileID='default-test-file.txt', contributors=[Pillar1], monitor=ConversationEventMonitor{, collectionID='TwoPillarCollection', conversationID='ce0f61c1', operationType=PUT_FILE, fileID='default-test-file.txt', eventHandler=org.bitrepository.client.TestEventHandler@51dd465a, contributorCompleteEvents=[], contributorFailedEvents=[], failOnComponentFailure=true}, auditTrailInformation='null', state=org.bitrepository.client.conversation.FinishedState@70ffa7e, checksumPillars=[]}' with exception
org.bitrepository.common.exceptions.UnableToFinishException: Failed to receive responses from all contributors before timeout(100ms). Missing contributors [Pillar1]
	at org.bitrepository.client.conversation.PerformingOperationState.logStateTimeout(PerformingOperationState.java:82)
	at org.bitrepository.client.conversation.GeneralConversationState$TimeoutHandler.run(GeneralConversationState.java:133)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
      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@1e53e341, TEST-AUDIT-TRAIL)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@d57c80d[correlationID=d42ee0b3-9830-45f3-8436-8e9ae80e6fec, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=putClientPillarOperationFailed, to=Pillar1, version=30, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, fileID=default-test-file.txt, fileSize=0]
          Result: Received event: d42ee0b3: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file
        Step: Send pillar response.
          Result: Received event: d42ee0b3: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: d42ee0b3: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: d42ee0b3: 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@87c9b75[correlationID=d42ee0b3-9830-45f3-8436-8e9ae80e6fec, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=putClientPillarOperationFailed, to=Pillar1, version=30, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>(default), checksumRequestForNewFile=<null>(default)]
        Step: Validate the steps of the PutClient by going through the events.
        Step: Send a failed response message to the PutClient.
          Result: Received event: d42ee0b3: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE, Verifying that a failure can be understood!
          Result: Received event: d42ee0b3: PUT_FILE for file default-test-file.txt: FAILED: , Failed operation. Cause(s):
[d42ee0b3: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE, Verifying that a failure can be understood!]
      Test success: putClientPillarOperationFailed
      Test starting: putToOtherCollection
        Reference: <a href=https://sbforge.org/jira/browse/BITMAG-925>BITMAG-925 Client will always try to put to the pillars defined in the first collection</a>
        Description: Tests the putFIle client will correctly try to put to a second collection if required
        Added fixture: Sets the identification timeout to 3 sec, allow two retries and only register one pillar.
        Added fixture: Configure collection1 to contain both pillars and collection 2 to only contain pillar2
        Step: Request the putting of a file through the PutClient for collection2
          Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, null, org.bitrepository.client.TestEventHandler@3fc12b15, null)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@354a8947[correlationID=c05bc7fd-5cf3-4541-8fa7-dee7b85393d7, collectionID=SinglePillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=putToOtherCollection, to=Pillar2, version=30, minVersion=24, auditTrailInformation=<null>(default), fileID=default-test-file.txt, fileSize=0]
          Result: Received event: c05bc7fd: 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: c05bc7fd: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
          Result: Received event: c05bc7fd: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
          Result: Received event: c05bc7fd: 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@5b6b7813[correlationID=c05bc7fd-5cf3-4541-8fa7-dee7b85393d7, collectionID=SinglePillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=putToOtherCollection, to=Pillar2, version=30, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar2, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>(default), checksumRequestForNewFile=<null>(default)]
        Step: Send a put complete event from the pillar
          Result: Received event: c05bc7fd: PUT_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2, requestedChecksumResult=null
          Result: Received event: c05bc7fd: PUT_FILE for file default-test-file.txt: COMPLETE: 
      Test success: putToOtherCollection
      Test starting: saltedReturnChecksumsWithChecksumPillar
        Description: Tests that PutClient handles the presence of a ChecksumPillar correctly, when a salted return checksum (which a checksum pillar can't provide) is requested. 
        Reference: <a href="https://sbforge.org/jira/browse/BITMAG-677">BITMAG-677put, replace and delete clients fails if return checksums are requested and a checksumpillar is involved</a>
        Step: Call putFile while requesting a salted checksum to be returned.
          Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@25e8f113[checksumType=HMAC_MD5, checksumSalt={-86}, otherChecksumType=<null>(default)], org.bitrepository.client.TestEventHandler@3d89d3d9, TEST-AUDIT-TRAIL)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@12215244[correlationID=3f61f5c8-62bb-4419-83ef-d3688bd02eb7, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=saltedReturnChecksumsWithChecksumPillar, to=<null>(default), version=30, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, fileID=default-test-file.txt, fileSize=0]
          Result: Received event: 3f61f5c8: 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: 3f61f5c8: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
        Step: Send an normal identification response from pillar2.
          Result: Received event: 3f61f5c8: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
          Result: Received event: 3f61f5c8: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2, Pillar1]
          Result: Received event: 3f61f5c8: 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@38cc8abd[correlationID=3f61f5c8-62bb-4419-83ef-d3688bd02eb7, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=saltedReturnChecksumsWithChecksumPillar, to=<null>(default), version=30, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>(default), checksumRequestForNewFile=<null>(default)]
          Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@7c47cd4f[correlationID=3f61f5c8-62bb-4419-83ef-d3688bd02eb7, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=saltedReturnChecksumsWithChecksumPillar, to=<null>(default), version=30, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, pillarID=Pillar2, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>(default), checksumRequestForNewFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@25e8f113[checksumType=HMAC_MD5, checksumSalt={-86}, otherChecksumType=<null>(default)]]
      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@4df6d39c[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@4ec14e4c[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2017-06-08T15:27:41.573+02:00], null, org.bitrepository.client.TestEventHandler@1e4a0cdf, TEST-AUDIT-TRAIL)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@4eaa7133[correlationID=3fcc35af-0573-4fe5-ae9c-ae904c31662b, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=sameFileExistsOnOnePillar, to=<null>(default), version=30, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, fileID=default-test-file.txt, fileSize=0]
          Result: Received event: 3fcc35af: 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: 3fcc35af: PUT_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, requestedChecksumResult=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@3f2e6c8e[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2290b1b1[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2017-06-08T15:27:41.575+02:00], File already existed on Pillar1
        Step: Send an identification response from the second pillar.
          Result: Received event: 3fcc35af: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
          Result: Received event: 3fcc35af: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
          Result: Received event: 3fcc35af: 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@5ac1b6cc[correlationID=3fcc35af-0573-4fe5-ae9c-ae904c31662b, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=sameFileExistsOnOnePillar, to=<null>(default), version=30, 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@4df6d39c[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@4ec14e4c[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2017-06-08T15:27:41.573+02:00], checksumRequestForNewFile=<null>(default)]
        Step: The client should proceed to send a putFileOperation request to the second pillar.
        Step: Send a pillar complete event
          Result: Received event: 3fcc35af: PUT_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2, requestedChecksumResult=null
          Result: Received event: 3fcc35af: 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 AuditTrailQueryTest
      Test starting: testBothSequenceNumberFailure
        Description: Test the creation of a AuditTrailQuery with both SequenceNumber, where max is smalle than min.
      Test success: testBothSequenceNumberFailure
      Test starting: testBothSequenceNumberSuccess
        Description: Test the creation of a AuditTrailQuery with both SequenceNumber, where max is larger than min.
      Test success: testBothSequenceNumberSuccess
      Test starting: testNoSequenceNumbers
        Description: Test that a AuditTrailQuery can be created without any sequence numbers.
      Test success: testNoSequenceNumbers
      Test starting: testOnlyMinSequenceNumber
        Description: Test the creation of a AuditTrailQuery with only the minSequenceNumber
      Test success: testOnlyMinSequenceNumber
    Starting testcase 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@57d953ba)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@2326236d[correlationID=d111fda9-4675-4dda-90d7-7b4cf544b0e7, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=collectionIDIncludedInEventsTest, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@25a2e354[fileID=<null>(default), allFileIDs=true]]
          Result: Received event: d111fda9: 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: d111fda9: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: d111fda9: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE
          Result: Received event: d111fda9: GET_FILE_IDS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: d111fda9: GET_FILE_IDS: REQUEST_SENT: ContributorID [Pillar1], Sending request for get fileIDs
          Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@941076[correlationID=d111fda9-4675-4dda-90d7-7b4cf544b0e7, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=collectionIDIncludedInEventsTest, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@752a6b5a[fileID=<null>(default), allFileIDs=true], minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), resultAddress=<null>(default)]
        Step: Wait for 1 second
          Result: Received event: d111fda9: GET_FILE_IDS: FAILED: , Failed to receive responses from all contributors before timeout(500ms). Missing contributors [Pillar1]
15:27:42.372 ERROR o.b.a.g.conversation.GettingFileIDs - Failing conversation 'GetFileIDsConversationContext{collectionID='TwoPillarCollection', conversationID='d111fda9-4675-4dda-90d7-7b4cf544b0e7', clientID='collectionIDIncludedInEventsTest', fileID='null', contributors=[Pillar1, Pillar2], monitor=ConversationEventMonitor{, collectionID='TwoPillarCollection', conversationID='d111fda9', operationType=GET_FILE_IDS, fileID='null', eventHandler=org.bitrepository.client.TestEventHandler@57d953ba, contributorCompleteEvents=[], contributorFailedEvents=[d111fda9: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE], failOnComponentFailure=true}, auditTrailInformation='null', state=org.bitrepository.client.conversation.FinishedState@4a1ec564, checksumPillars=[]}' with exception
org.bitrepository.common.exceptions.UnableToFinishException: Failed to receive responses from all contributors before timeout(500ms). Missing contributors [Pillar1]
	at org.bitrepository.client.conversation.PerformingOperationState.logStateTimeout(PerformingOperationState.java:82)
	at org.bitrepository.client.conversation.GeneralConversationState$TimeoutHandler.run(GeneralConversationState.java:133)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
      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@57d953ba)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@730e60b[correlationID=cb8e77b7-5a48-4426-a21b-15768cbf99d8, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=conversationTimeoutTest, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@39930a6c[fileID=<null>(default), allFileIDs=true]]
          Result: Received event: cb8e77b7: GET_FILE_IDS: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs
15:27:43.539 WARN  o.b.c.c.m.CollectionBasedConversationMediator - Failing timed out conversation cb8e77b7-5a48-4426-a21b-15768cbf99d8 (Age 1000ms)
          Result: Received event: cb8e77b7: GET_FILE_IDS: FAILED: , Failing timed out conversation cb8e77b7-5a48-4426-a21b-15768cbf99d8
      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@57d953ba)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@22475317[correlationID=33f88769-9412-4990-afac-94124baada44, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=identificationFailureTest, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@2b17454[fileID=<null>(default), allFileIDs=true]]
          Result: Received event: 33f88769: 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: 33f88769: 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: 33f88769: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar2
          Result: Received event: 33f88769: GET_FILE_IDS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
          Result: Received event: 33f88769: GET_FILE_IDS: REQUEST_SENT: ContributorID [Pillar2], Sending request for get fileIDs
          Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@3cc2fe2e[correlationID=33f88769-9412-4990-afac-94124baada44, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=identificationFailureTest, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@2485cd4a[fileID=<null>(default), allFileIDs=true], minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), resultAddress=<null>(default)]
        Step: Verify that the client continues to the performing phase.
        Step: Send a final response message from contributor2
          Result: Received event: 33f88769: GET_FILE_IDS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false
          Result: Received event: 33f88769: GET_FILE_IDS: FAILED: , Failed operation. Cause(s):
[33f88769: 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@57d953ba)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@bd0311d[correlationID=fe9c8d42-b43c-4cee-ac0f-45000d47e8f6, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=identificationNegativeTest, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@50cf046e[fileID=<null>(default), allFileIDs=true]]
          Result: Received event: fe9c8d42: 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: fe9c8d42: 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: fe9c8d42: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar2
          Result: Received event: fe9c8d42: GET_FILE_IDS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
          Result: Received event: fe9c8d42: GET_FILE_IDS: REQUEST_SENT: ContributorID [Pillar2], Sending request for get fileIDs
          Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@5a621451[correlationID=fe9c8d42-b43c-4cee-ac0f-45000d47e8f6, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=identificationNegativeTest, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@50309ed9[fileID=<null>(default), allFileIDs=true], minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), resultAddress=<null>(default)]
        Step: Verify that the client continues to the performing phase.
        Step: Send a final response message from contributor2
          Result: Received event: fe9c8d42: GET_FILE_IDS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false
          Result: Received event: fe9c8d42: GET_FILE_IDS: FAILED: , Failed operation. Cause(s):
[fe9c8d42: 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@57d953ba)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@4d8f7b21[correlationID=42f6c5ce-a576-409e-8a0e-63b626b8d078, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=noContributorsRespondingTest, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@1e0a629b[fileID=<null>(default), allFileIDs=true]]
          Result: Received event: 42f6c5ce: GET_FILE_IDS: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs
        Step: Wait for 1 second
          Result: Received event: 42f6c5ce: GET_FILE_IDS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar1, Pillar2]
          Result: Received event: 42f6c5ce: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor
          Result: Received event: 42f6c5ce: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
          Result: Received event: 42f6c5ce: GET_FILE_IDS: FAILED: , Unable to continue operation, contributors unavailable.
15:27:46.105 ERROR o.b.a.g.c.IdentifyPillarsForGetFileIDs - Failing conversation 'GetFileIDsConversationContext{collectionID='TwoPillarCollection', conversationID='42f6c5ce-a576-409e-8a0e-63b626b8d078', clientID='noContributorsRespondingTest', fileID='null', contributors=[Pillar1, Pillar2], monitor=ConversationEventMonitor{, collectionID='TwoPillarCollection', conversationID='42f6c5ce', operationType=GET_FILE_IDS, fileID='null', eventHandler=org.bitrepository.client.TestEventHandler@57d953ba, contributorCompleteEvents=[], contributorFailedEvents=[42f6c5ce: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor, 42f6c5ce: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor], failOnComponentFailure=true}, auditTrailInformation='null', state=org.bitrepository.client.conversation.FinishedState@2753140, checksumPillars=[]}' with exception
org.bitrepository.common.exceptions.UnableToFinishException: Unable to continue operation, contributors unavailable.
	at org.bitrepository.client.conversation.IdentifyingState.completeState(IdentifyingState.java:76)
	at org.bitrepository.client.conversation.GeneralConversationState.changeState(GeneralConversationState.java:147)
	at org.bitrepository.client.conversation.GeneralConversationState.access$100(GeneralConversationState.java:48)
	at org.bitrepository.client.conversation.GeneralConversationState$TimeoutHandler.run(GeneralConversationState.java:134)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
      Test success: noContributorsRespondingTest
          Result: The following messages haven't been handled by the testcase: 
org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@4d8f7b21[correlationID=42f6c5ce-a576-409e-8a0e-63b626b8d078, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=noContributorsRespondingTest, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@1e0a629b[fileID=<null>(default), allFileIDs=true]]
15:27:46.109 WARN  o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: 
org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@4d8f7b21[correlationID=42f6c5ce-a576-409e-8a0e-63b626b8d078, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=noContributorsRespondingTest, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@1e0a629b[fileID=<null>(default), 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@57d953ba)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@4b8e4d3d[correlationID=43a9dc17-9753-4103-b9d1-4aa120c8f5d6, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=oneContributorNotRespondingTest, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@3e8ef038[fileID=<null>(default), allFileIDs=true]]
          Result: Received event: 43a9dc17: GET_FILE_IDS: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs
        Step: Send a identification response from contributor1.
          Result: Received event: 43a9dc17: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar1
        Step: Wait 1 second.
          Result: Received event: 43a9dc17: GET_FILE_IDS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar2]
          Result: Received event: 43a9dc17: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
          Result: Received event: 43a9dc17: GET_FILE_IDS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: 43a9dc17: GET_FILE_IDS: REQUEST_SENT: ContributorID [Pillar1], Sending request for get fileIDs
          Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@3e1f00b7[correlationID=43a9dc17-9753-4103-b9d1-4aa120c8f5d6, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=oneContributorNotRespondingTest, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@463bd100[fileID=<null>(default), allFileIDs=true], minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), resultAddress=<null>(default)]
        Step: Verify that the client continues to the performing phase.
        Step: Send a final response upload message
          Result: Received event: 43a9dc17: GET_FILE_IDS: COMPONENT_COMPLETE: ContributorID Pillar1, PartialResult=false
          Result: Received event: 43a9dc17: GET_FILE_IDS: FAILED: , Failed operation. Cause(s):
[43a9dc17: 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@57d953ba)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@7167ee0c[correlationID=fec77b1a-5a58-4a80-8089-4cfd0b3350df, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=operationTimeoutTest, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@2039d7b5[fileID=<null>(default), allFileIDs=true]]
          Result: Received event: fec77b1a: 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: fec77b1a: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: fec77b1a: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE
          Result: Received event: fec77b1a: GET_FILE_IDS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: fec77b1a: GET_FILE_IDS: REQUEST_SENT: ContributorID [Pillar1], Sending request for get fileIDs
          Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@d390ed7[correlationID=fec77b1a-5a58-4a80-8089-4cfd0b3350df, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=operationTimeoutTest, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@43e086f2[fileID=<null>(default), allFileIDs=true], minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), resultAddress=<null>(default)]
        Step: Wait for 1 second
          Result: Received event: fec77b1a: GET_FILE_IDS: FAILED: , Failed to receive responses from all contributors before timeout(100ms). Missing contributors [Pillar1]
15:27:46.641 ERROR o.b.a.g.conversation.GettingFileIDs - Failing conversation 'GetFileIDsConversationContext{collectionID='TwoPillarCollection', conversationID='fec77b1a-5a58-4a80-8089-4cfd0b3350df', clientID='operationTimeoutTest', fileID='null', contributors=[Pillar1, Pillar2], monitor=ConversationEventMonitor{, collectionID='TwoPillarCollection', conversationID='fec77b1a', operationType=GET_FILE_IDS, fileID='null', eventHandler=org.bitrepository.client.TestEventHandler@57d953ba, contributorCompleteEvents=[], contributorFailedEvents=[fec77b1a: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE], failOnComponentFailure=true}, auditTrailInformation='null', state=org.bitrepository.client.conversation.FinishedState@7a321946, checksumPillars=[]}' with exception
org.bitrepository.common.exceptions.UnableToFinishException: Failed to receive responses from all contributors before timeout(100ms). Missing contributors [Pillar1]
	at org.bitrepository.client.conversation.PerformingOperationState.logStateTimeout(PerformingOperationState.java:82)
	at org.bitrepository.client.conversation.GeneralConversationState$TimeoutHandler.run(GeneralConversationState.java:133)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
      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 operation should be performed. If undefined the operation is performed on all pillars.
-C [OPTIONAL] The checksum of the file to be deleted.
-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 operation should be performed. If undefined the operation is performed on all pillars.
-C [OPTIONAL] The checksum of the file to be deleted.
-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: Random1496928467865pillar is not a valid pillar for collection TwoPillarCollection
The collection contains the following pillars: [Pillar1, Pillar2]
      Test success: unknownPillarArgumentTest
      Test starting: getFileIDsDeliveredAtUrl
        Description: Tests the delivery of fileIDs from a pillar at a given URL.
        Step: Initialise the variables for this test.
        Step: Request the delivery of the file ids of a file from the pillar(s). A callback listener should be supplied.
          Stimuli: Calling getFileIDs(null, default-test-file.txt, file:../bitrepository-core/src/test/resources/test-files//TEST-FILE-IDS-DELIVERY.xml, org.bitrepository.client.TestEventHandler@57d953ba)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@34dc8c4f[correlationID=846d54bf-94ce-4c2b-9969-966f908a9d36, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=getFileIDsDeliveredAtUrl, to=Pillar1, version=30, minVersion=24, auditTrailInformation=<null>(default), fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@3dad3e98[fileID=default-test-file.txt, allFileIDs=<null>(default)]]
          Result: Received event: 846d54bf: 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: 846d54bf: GET_FILE_IDS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 846d54bf: GET_FILE_IDS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: 846d54bf: 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@141fe0f8[correlationID=846d54bf-94ce-4c2b-9969-966f908a9d36, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=getFileIDsDeliveredAtUrl, to=Pillar1, version=30, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@44f1a8c0[fileID=default-test-file.txt, allFileIDs=<null>(default)], minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), 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: 846d54bf: 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: 846d54bf: GET_FILE_IDS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, PartialResult=false
          Result: Received event: 846d54bf: 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@57d953ba)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@75016c1e[correlationID=d327e1d0-74f1-4774-be98-dcca02266e1c, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=getFileIDsDeliveredThroughMessage, to=Pillar1, version=30, minVersion=24, auditTrailInformation=<null>(default), fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@350c396c[fileID=default-test-file.txt, allFileIDs=<null>(default)]]
          Result: Received event: d327e1d0: 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: d327e1d0: GET_FILE_IDS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: d327e1d0: GET_FILE_IDS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: d327e1d0: 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@438e5c9[correlationID=d327e1d0-74f1-4774-be98-dcca02266e1c, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=getFileIDsDeliveredThroughMessage, to=Pillar1, version=30, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@7aa708cc[fileID=default-test-file.txt, allFileIDs=<null>(default)], minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), resultAddress=<null>(default)]
        Step: The pillar sends a getFileIDsProgressResponse to the GetFileIDsClient.
          Result: Received event: d327e1d0: 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: d327e1d0: GET_FILE_IDS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, NumberOfFileIDs=1, PartialResult=false
          Result: Received event: d327e1d0: 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@5c1ce862)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@4e8eaf23[correlationID=07606008-4693-4bd3-b2ec-8cf0866d1e4d, collectionID=SinglePillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=getFileIDsFromOtherCollection, to=Pillar2, version=30, minVersion=24, auditTrailInformation=<null>(default), fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@307579a6[fileID=default-test-file.txt, allFileIDs=<null>(default)]]
          Result: Received event: 07606008: 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: 07606008: GET_FILE_IDS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
          Result: Received event: 07606008: GET_FILE_IDS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
          Result: Received event: 07606008: 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@1a8e50e3[correlationID=07606008-4693-4bd3-b2ec-8cf0866d1e4d, collectionID=SinglePillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=getFileIDsFromOtherCollection, to=Pillar2, version=30, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@21420326[fileID=default-test-file.txt, allFileIDs=<null>(default)], minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), resultAddress=<null>(default)]
        Step: Send a complete event from the pillar
          Result: Received event: 07606008: GET_FILE_IDS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false
          Result: Received event: 07606008: 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@57d953ba)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@425c5531[correlationID=53a9b63b-89a7-4757-8ddf-7185787dfb77, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=testNoSuchFile, to=Pillar1, version=30, minVersion=24, auditTrailInformation=<null>(default), fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@797e5012[fileID=default-test-file.txt, allFileIDs=<null>(default)]]
          Result: Received event: 53a9b63b: 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: 53a9b63b: GET_FILE_IDS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 53a9b63b: GET_FILE_IDS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: 53a9b63b: 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@210b5793[correlationID=53a9b63b-89a7-4757-8ddf-7185787dfb77, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=testNoSuchFile, to=Pillar1, version=30, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@1de7b5e[fileID=default-test-file.txt, allFileIDs=<null>(default)], minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), 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: 53a9b63b: GET_FILE_IDS for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FILE_NOT_FOUND_FAILURE, No such file.
          Result: Received event: 53a9b63b: GET_FILE_IDS for file default-test-file.txt: FAILED: , Failed operation. Cause(s):
[53a9b63b: 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=Thu Jun 08 15:27:47 CEST 2017, maxTimestamp=Thu Jun 08 15:27:48 CEST 2017, maxNumberOfResults=1}, ContributorQuery{componentID='Pillar2, minTimestamp=Thu Jun 08 15:27:48 CEST 2017, maxTimestamp=Thu Jun 08 15:27:48 CEST 2017, maxNumberOfResults=2}], null, null, org.bitrepository.client.TestEventHandler@57d953ba)
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@25b72943[correlationID=eb5813a6-f93a-4407-a52a-92e0e0a860dc, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=testPaging, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@216249f4[fileID=<null>(default), allFileIDs=true]]
          Result: Received event: eb5813a6: GET_FILE_IDS: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs
        Step: Send a IdentifyPillarsForGetFileIDsResponse from both pillars.
          Result: Received event: eb5813a6: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: eb5813a6: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar2
          Result: Received event: eb5813a6: GET_FILE_IDS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2]
          Result: Received event: eb5813a6: GET_FILE_IDS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for get fileIDs
          Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@35d0b36d[correlationID=eb5813a6-f93a-4407-a52a-92e0e0a860dc, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=testPaging, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@6ce61ca[fileID=<null>(default), allFileIDs=true], minTimestamp=2017-06-08T15:27:47.631+02:00, maxTimestamp=2017-06-08T15:27:48.531+02:00, maxNumberOfResults=1, resultAddress=<null>(default)]
          Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@38557319[correlationID=eb5813a6-f93a-4407-a52a-92e0e0a860dc, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=testPaging, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@1a17b688[fileID=<null>(default), allFileIDs=true], minTimestamp=2017-06-08T15:27:48.531+02:00, maxTimestamp=2017-06-08T15:27:48.631+02:00, maxNumberOfResults=2, resultAddress=<null>(default)]
      Test success: testPaging
      Test starting: verifyGetFileIDsClientFromFactory
      Test success: verifyGetFileIDsClientFromFactory
    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@255ad15e[correlationID=8f70031e-8ae1-4431-9853-e2c269cc4db1, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=chooseFastestPillarGetFileClient, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), fileID=default-test-file.txt]
          Result: Received event: 8f70031e: 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: 8f70031e: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID THE-AVERAGE-PILLAR
          Result: Received event: 8f70031e: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID THE-FAST-PILLAR
          Result: Received event: 8f70031e: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID THE-SLOW-PILLAR
          Result: Received event: 8f70031e: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [THE-FAST-PILLAR]
          Result: Received event: 8f70031e: 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@512018c3[correlationID=8f70031e-8ae1-4431-9853-e2c269cc4db1, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=chooseFastestPillarGetFileClient, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), pillarID=THE-FAST-PILLAR, fileID=default-test-file.txt, filePart=<null>(default), 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@56b79b06[correlationID=725d5bd9-b81f-4aaa-aada-bfc8a69cf623, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=conversationTimeout, to=Pillar1, version=30, minVersion=24, auditTrailInformation=<null>(default), fileID=default-test-file.txt]
          Result: Received event: 725d5bd9: 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: 725d5bd9: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 725d5bd9: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: 725d5bd9: 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@e14f8a4[correlationID=725d5bd9-b81f-4aaa-aada-bfc8a69cf623, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=conversationTimeout, to=Pillar1, version=30, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileID=default-test-file.txt, filePart=<null>(default), fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt]
        Step: Wait for 1 second
15:27:49.964 WARN  o.b.c.c.m.CollectionBasedConversationMediator - Failing timed out conversation 725d5bd9-b81f-4aaa-aada-bfc8a69cf623 (Age 997ms)
          Result: Received event: 725d5bd9: GET_FILE for file default-test-file.txt: FAILED: , Failing timed out conversation 725d5bd9-b81f-4aaa-aada-bfc8a69cf623
      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@1f05a01a[correlationID=e153045f-02ef-456b-b4eb-961b0ad2be83, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=failureDuringPerform, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), fileID=default-test-file.txt]
          Result: Received event: e153045f: 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: e153045f: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: e153045f: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
          Result: Received event: e153045f: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: e153045f: 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@7587653c[correlationID=e153045f-02ef-456b-b4eb-961b0ad2be83, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=failureDuringPerform, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileID=default-test-file.txt, filePart=<null>(default), fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt]
        Step: Send a failure response from pillar1
          Result: Received event: e153045f: GET_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE
          Result: Received event: e153045f: GET_FILE for file default-test-file.txt: FAILED: , Failed to get file from Pillar1, org.bitrepository.bitrepositoryelements.ResponseInfo@575a5a2f[responseCode=FAILURE, responseText=<null>(default)]
15:27:50.095 ERROR o.b.a.g.conversation.GettingFile - Failing conversation 'GetFileConversationContext{collectionID='TwoPillarCollection', conversationID='e153045f-02ef-456b-b4eb-961b0ad2be83', clientID='failureDuringPerform', fileID='default-test-file.txt', contributors=[Pillar1, Pillar2], monitor=ConversationEventMonitor{, collectionID='TwoPillarCollection', conversationID='e153045f', operationType=GET_FILE, fileID='default-test-file.txt', eventHandler=org.bitrepository.client.TestEventHandler@656d35ae, contributorCompleteEvents=[], contributorFailedEvents=[e153045f: GET_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE], failOnComponentFailure=false}, auditTrailInformation='null', state=org.bitrepository.client.conversation.FinishedState@520ea61a, checksumPillars=[]}' with exception
org.bitrepository.common.exceptions.UnableToFinishException: Failed to get file from Pillar1, org.bitrepository.bitrepositoryelements.ResponseInfo@575a5a2f[responseCode=FAILURE, responseText=<null>(default)]
	at org.bitrepository.access.getfile.conversation.GettingFile.handleFailureResponse(GettingFile.java:78)
	at org.bitrepository.client.conversation.PerformingOperationState.processMessage(PerformingOperationState.java:70)
	at org.bitrepository.client.conversation.GeneralConversationState.handleMessage(GeneralConversationState.java:110)
	at org.bitrepository.client.conversation.StateBasedConversation.onMessage(StateBasedConversation.java:53)
	at org.bitrepository.client.conversation.mediator.CollectionBasedConversationMediator.onMessage(CollectionBasedConversationMediator.java:136)
	at org.bitrepository.protocol.messagebus.SimpleMessageBus.lambda$sendMessage$0(SimpleMessageBus.java:73)
	at java.lang.Iterable.forEach(Iterable.java:75)
	at org.bitrepository.protocol.messagebus.SimpleMessageBus.sendMessage(SimpleMessageBus.java:73)
	at org.bitrepository.access.getfile.GetFileClientComponentTest.failureDuringPerform(GetFileClientComponentTest.java:579)
	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:498)
	at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:86)
	at org.testng.internal.Invoker.invokeMethod(Invoker.java:643)
	at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:820)
	at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1128)
	at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:129)
	at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:112)
	at org.testng.TestRunner.privateRun(TestRunner.java:782)
	at org.testng.TestRunner.run(TestRunner.java:632)
	at org.testng.SuiteRunner.runTest(SuiteRunner.java:366)
	at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:361)
	at org.testng.SuiteRunner.privateRun(SuiteRunner.java:319)
	at org.testng.SuiteRunner.run(SuiteRunner.java:268)
	at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
	at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
	at org.testng.TestNG.runSuitesSequentially(TestNG.java:1244)
	at org.testng.TestNG.runSuitesLocally(TestNG.java:1169)
	at org.testng.TestNG.run(TestNG.java:1064)
	at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:115)
	at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:204)
	at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:107)
	at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:112)
	at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
      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@51e0cc92[correlationID=7f56635d-de2e-44c6-8abc-555280bba43a, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=getFileClientWithChecksumPillarInvolved, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), fileID=default-test-file.txt]
          Result: Received event: 7f56635d: 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: 7f56635d: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
          Result: Received event: 7f56635d: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
          Result: Received event: 7f56635d: 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@647e970a[correlationID=7f56635d-de2e-44c6-8abc-555280bba43a, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=getFileClientWithChecksumPillarInvolved, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar2, fileID=default-test-file.txt, filePart=<null>(default), 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: 7f56635d: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2
          Result: Received event: 7f56635d: 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@7143f0c[correlationID=bff6bc94-f31a-4a16-9b4b-bcb755424add, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=getFileClientWithIdentifyTimeout, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), fileID=default-test-file.txt]
          Result: Received event: bff6bc94: 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: bff6bc94: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
        Step: Wait 1 second.
          Result: Received event: bff6bc94: 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: bff6bc94: GET_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
          Result: Received event: bff6bc94: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: bff6bc94: 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@5166c871[correlationID=bff6bc94-f31a-4a16-9b4b-bcb755424add, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=getFileClientWithIdentifyTimeout, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileID=default-test-file.txt, filePart=<null>(default), 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: bff6bc94: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1
          Result: Received event: bff6bc94: 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@6659507a[correlationID=5bc29cbf-dd84-4984-8411-e332352670a2, collectionID=SinglePillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=getFileFromOtherCollection, to=Pillar2, version=30, minVersion=24, auditTrailInformation=<null>(default), fileID=default-test-file.txt]
          Result: Received event: 5bc29cbf: 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: 5bc29cbf: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
          Result: Received event: 5bc29cbf: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
          Result: Received event: 5bc29cbf: 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@157345d0[correlationID=5bc29cbf-dd84-4984-8411-e332352670a2, collectionID=SinglePillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=getFileFromOtherCollection, to=Pillar2, version=30, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar2, fileID=default-test-file.txt, filePart=<null>(default), fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt]
        Step: Send a complete event from the pillar
          Result: Received event: 5bc29cbf: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2
          Result: Received event: 5bc29cbf: 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@5d688fab[correlationID=f22e41a4-1ffa-4d31-b548-ae8d6b4d8038, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=getFileFromSpecificPillar, to=Pillar2, version=30, minVersion=24, auditTrailInformation=AuditTrailInfo for getFileFromSpecificPillarTest, fileID=default-test-file.txt]
          Result: Received event: f22e41a4: 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: f22e41a4: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
          Result: Received event: f22e41a4: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
          Result: Received event: f22e41a4: 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@76486f75[correlationID=f22e41a4-1ffa-4d31-b548-ae8d6b4d8038, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=getFileFromSpecificPillar, to=Pillar2, version=30, minVersion=24, auditTrailInformation=AuditTrailInfo for getFileFromSpecificPillarTest, pillarID=Pillar2, fileID=default-test-file.txt, filePart=<null>(default), fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt]
        Step: Send a GetFileProgressResponse.
          Result: Received event: f22e41a4: GET_FILE for file default-test-file.txt: PROGRESS: ContributorID Pillar2, First test progress response message
        Step: Send a GetFileFinalResponse.
          Result: Received event: f22e41a4: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2
          Result: Received event: f22e41a4: 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@46f0f8d1[correlationID=3c7db9f9-af48-466d-856f-c1cab8f952b0, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=getFileFromSpecificPillarWithFilePart, to=Pillar1, version=30, minVersion=24, auditTrailInformation=<null>(default), fileID=default-test-file.txt]
          Result: Received event: 3c7db9f9: 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: 3c7db9f9: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
          Result: Received event: 3c7db9f9: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
          Result: Received event: 3c7db9f9: 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@370c1ea2[correlationID=3c7db9f9-af48-466d-856f-c1cab8f952b0, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=getFileFromSpecificPillarWithFilePart, to=Pillar1, version=30, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileID=default-test-file.txt, filePart=org.bitrepository.bitrepositoryelements.FilePart@4939e783[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: 3c7db9f9: 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: 3c7db9f9: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1
          Result: Received event: 3c7db9f9: 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@78ae2183[correlationID=6a25517c-7637-4dcc-b71f-beaeb7a2a966, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=noIdentifyResponse, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), fileID=default-test-file.txt]
          Result: Received event: 6a25517c: GET_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetFile
        Step: Wait for 1 seconds
          Result: Received event: 6a25517c: 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: 6a25517c: GET_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor
          Result: Received event: 6a25517c: GET_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
          Result: Received event: 6a25517c: GET_FILE for file default-test-file.txt: FAILED: , Unable to continue operation, contributors unavailable.
15:27:52.889 ERROR o.b.a.g.c.IdentifyingPillarsForGetFile - Failing conversation 'GetFileConversationContext{collectionID='TwoPillarCollection', conversationID='6a25517c-7637-4dcc-b71f-beaeb7a2a966', clientID='noIdentifyResponse', fileID='default-test-file.txt', contributors=[Pillar1, Pillar2], monitor=ConversationEventMonitor{, collectionID='TwoPillarCollection', conversationID='6a25517c', operationType=GET_FILE, fileID='default-test-file.txt', eventHandler=org.bitrepository.client.TestEventHandler@17ba6052, contributorCompleteEvents=[], contributorFailedEvents=[6a25517c: GET_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor, 6a25517c: GET_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor], failOnComponentFailure=false}, auditTrailInformation='null', state=org.bitrepository.client.conversation.FinishedState@f111074, checksumPillars=[]}' with exception
org.bitrepository.common.exceptions.UnableToFinishException: Unable to continue operation, contributors unavailable.
	at org.bitrepository.client.conversation.IdentifyingState.completeState(IdentifyingState.java:76)
	at org.bitrepository.client.conversation.GeneralConversationState.changeState(GeneralConversationState.java:147)
	at org.bitrepository.client.conversation.GeneralConversationState.access$100(GeneralConversationState.java:48)
	at org.bitrepository.client.conversation.GeneralConversationState$TimeoutHandler.run(GeneralConversationState.java:134)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
      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@1da3e2e6[correlationID=0fa87a9b-1463-42de-92d8-d68542ba1b6f, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=singleComponentFailureDuringIdentify, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), fileID=default-test-file.txt]
          Result: Received event: 0fa87a9b: 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: 0fa87a9b: 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: 0fa87a9b: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
          Result: Received event: 0fa87a9b: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
          Result: Received event: 0fa87a9b: 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@3cd04665[correlationID=0fa87a9b-1463-42de-92d8-d68542ba1b6f, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=singleComponentFailureDuringIdentify, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar2, fileID=default-test-file.txt, filePart=<null>(default), 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: 0fa87a9b: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2
          Result: Received event: 0fa87a9b: 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@3f3134d4[correlationID=d6bb094c-7dd6-4772-8423-1cc25f6d3839, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=testNoSuchFileMultiplePillars, to=<null>(default), version=30, minVersion=24, auditTrailInformation=<null>(default), fileID=ERROR-NO-SUCH-FILE-ERROR]
          Result: Received event: d6bb094c: 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: d6bb094c: 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: d6bb094c: 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: d6bb094c: GET_FILE for file ERROR-NO-SUCH-FILE-ERROR: FAILED: , Unable to continue operation, contributors unavailable.
15:27:53.158 ERROR o.b.a.g.c.IdentifyingPillarsForGetFile - Failing conversation 'GetFileConversationContext{collectionID='TwoPillarCollection', conversationID='d6bb094c-7dd6-4772-8423-1cc25f6d3839', clientID='testNoSuchFileMultiplePillars', fileID='ERROR-NO-SUCH-FILE-ERROR', contributors=[Pillar1, Pillar2], monitor=ConversationEventMonitor{, collectionID='TwoPillarCollection', conversationID='d6bb094c', operationType=GET_FILE, fileID='ERROR-NO-SUCH-FILE-ERROR', eventHandler=org.bitrepository.client.TestEventHandler@4c9232cf, contributorCompleteEvents=[], contributorFailedEvents=[d6bb094c: 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 , d6bb094c: 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 ], failOnComponentFailure=false}, auditTrailInformation='null', state=org.bitrepository.client.conversation.FinishedState@7c29d87f, checksumPillars=[]}' with exception
org.bitrepository.common.exceptions.UnableToFinishException: Unable to continue operation, contributors unavailable.
	at org.bitrepository.client.conversation.IdentifyingState.completeState(IdentifyingState.java:76)
	at org.bitrepository.client.conversation.GeneralConversationState.changeState(GeneralConversationState.java:147)
	at org.bitrepository.client.conversation.GeneralConversationState.handleMessage(GeneralConversationState.java:114)
	at org.bitrepository.client.conversation.StateBasedConversation.onMessage(StateBasedConversation.java:53)
	at org.bitrepository.client.conversation.mediator.CollectionBasedConversationMediator.onMessage(CollectionBasedConversationMediator.java:136)
	at org.bitrepository.protocol.messagebus.SimpleMessageBus.lambda$sendMessage$0(SimpleMessageBus.java:73)
	at java.lang.Iterable.forEach(Iterable.java:75)
	at org.bitrepository.protocol.messagebus.SimpleMessageBus.sendMessage(SimpleMessageBus.java:73)
	at org.bitrepository.access.getfile.GetFileClientComponentTest.testNoSuchFileMultiplePillars(GetFileClientComponentTest.java:444)
	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:498)
	at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:86)
	at org.testng.internal.Invoker.invokeMethod(Invoker.java:643)
	at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:820)
	at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1128)
	at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:129)
	at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:112)
	at org.testng.TestRunner.privateRun(TestRunner.java:782)
	at org.testng.TestRunner.run(TestRunner.java:632)
	at org.testng.SuiteRunner.runTest(SuiteRunner.java:366)
	at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:361)
	at org.testng.SuiteRunner.privateRun(SuiteRunner.java:319)
	at org.testng.SuiteRunner.run(SuiteRunner.java:268)
	at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
	at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
	at org.testng.TestNG.runSuitesSequentially(TestNG.java:1244)
	at org.testng.TestNG.runSuitesLocally(TestNG.java:1169)
	at org.testng.TestNG.run(TestNG.java:1064)
	at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:115)
	at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:204)
	at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:107)
	at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:112)
	at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
      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@3bd01b21[correlationID=dc31da66-618b-4299-8b8c-d1f9b995cc77, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=testNoSuchFileSpecificPillar, to=Pillar1, version=30, minVersion=24, auditTrailInformation=<null>(default), fileID=ERROR-NO-SUCH-FILE-ERROR]
          Result: Received event: dc31da66: 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: dc31da66: 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: dc31da66: GET_FILE for file ERROR-NO-SUCH-FILE-ERROR: FAILED: , Unable to continue operation, contributors unavailable.
15:27:53.263 ERROR o.b.a.g.c.IdentifyingPillarsForGetFile - Failing conversation 'GetFileConversationContext{collectionID='TwoPillarCollection', conversationID='dc31da66-618b-4299-8b8c-d1f9b995cc77', clientID='testNoSuchFileSpecificPillar', fileID='ERROR-NO-SUCH-FILE-ERROR', contributors=[Pillar1], monitor=ConversationEventMonitor{, collectionID='TwoPillarCollection', conversationID='dc31da66', operationType=GET_FILE, fileID='ERROR-NO-SUCH-FILE-ERROR', eventHandler=org.bitrepository.client.TestEventHandler@54775f19, contributorCompleteEvents=[], contributorFailedEvents=[dc31da66: 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], failOnComponentFailure=false}, auditTrailInformation='null', state=org.bitrepository.client.conversation.FinishedState@5a05332e, checksumPillars=[]}' with exception
org.bitrepository.common.exceptions.UnableToFinishException: Unable to continue operation, contributors unavailable.
	at org.bitrepository.client.conversation.IdentifyingState.completeState(IdentifyingState.java:76)
	at org.bitrepository.client.conversation.GeneralConversationState.changeState(GeneralConversationState.java:147)
	at org.bitrepository.client.conversation.GeneralConversationState.handleMessage(GeneralConversationState.java:114)
	at org.bitrepository.client.conversation.StateBasedConversation.onMessage(StateBasedConversation.java:53)
	at org.bitrepository.client.conversation.mediator.CollectionBasedConversationMediator.onMessage(CollectionBasedConversationMediator.java:136)
	at org.bitrepository.protocol.messagebus.SimpleMessageBus.lambda$sendMessage$0(SimpleMessageBus.java:73)
	at java.lang.Iterable.forEach(Iterable.java:75)
	at org.bitrepository.protocol.messagebus.SimpleMessageBus.sendMessage(SimpleMessageBus.java:73)
	at org.bitrepository.access.getfile.GetFileClientComponentTest.testNoSuchFileSpecificPillar(GetFileClientComponentTest.java:405)
	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:498)
	at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:86)
	at org.testng.internal.Invoker.invokeMethod(Invoker.java:643)
	at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:820)
	at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1128)
	at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:129)
	at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:112)
	at org.testng.TestRunner.privateRun(TestRunner.java:782)
	at org.testng.TestRunner.run(TestRunner.java:632)
	at org.testng.SuiteRunner.runTest(SuiteRunner.java:366)
	at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:361)
	at org.testng.SuiteRunner.privateRun(SuiteRunner.java:319)
	at org.testng.SuiteRunner.run(SuiteRunner.java:268)
	at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
	at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
	at org.testng.TestNG.runSuitesSequentially(TestNG.java:1244)
	at org.testng.TestNG.runSuitesLocally(TestNG.java:1169)
	at org.testng.TestNG.run(TestNG.java:1064)
	at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:115)
	at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:204)
	at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:107)
	at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:112)
	at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
      Test success: testNoSuchFileSpecificPillar
      Test starting: verifyGetFileClientFromFactory
      Test success: verifyGetFileClientFromFactory
      Finished testcase
  Finished suite
Finished project
Tests run: 156, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 64.698 sec - in TestSuite

Results :

Tests run: 156, Failures: 0, Errors: 0, Skipped: 0

[JENKINS] Recording test results
[INFO] 
[INFO] --- jacoco-maven-plugin:0.7.5.201505241946:report (report) @ bitrepository-client ---
[INFO] Analyzed bundle 'Bitrepository Client' with 116 classes
[INFO] 
[INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ bitrepository-client ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-client/target/bitrepository-client-1.10-SNAPSHOT.jar
[INFO] 
[INFO] --- maven-jar-plugin:2.4:test-jar (default) @ bitrepository-client ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-client/target/bitrepository-client-1.10-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-reference-test/bitrepository-client/target/bitrepository-client-1.10-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] Downloading: https://sbforge.org/nexus/content/groups/public/org/bitrepository/reference/bitrepository-core/1.10-SNAPSHOT/bitrepository-core-1.10-20170608.132644-5.pom
[INFO] Downloaded: https://sbforge.org/nexus/content/groups/public/org/bitrepository/reference/bitrepository-core/1.10-SNAPSHOT/bitrepository-core-1.10-20170608.132644-5.pom (4 KB at 24.6 KB/sec)
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-client/target/bitrepository-client-1.10-SNAPSHOT-distribution.tar.gz
[INFO] 
[INFO] --- maven-install-plugin:2.5.1:install (default-install) @ bitrepository-client ---
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-client/target/bitrepository-client-1.10-SNAPSHOT.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-client/1.10-SNAPSHOT/bitrepository-client-1.10-SNAPSHOT.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-client/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-client/1.10-SNAPSHOT/bitrepository-client-1.10-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-client/target/bitrepository-client-1.10-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-client/1.10-SNAPSHOT/bitrepository-client-1.10-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-client/target/bitrepository-client-1.10-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-client/1.10-SNAPSHOT/bitrepository-client-1.10-SNAPSHOT-sources.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-client/target/bitrepository-client-1.10-SNAPSHOT-distribution.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-client/1.10-SNAPSHOT/bitrepository-client-1.10-SNAPSHOT-distribution.tar.gz
[INFO] 
[INFO] --- maven-deploy-plugin:2.8.1:deploy (default-deploy) @ bitrepository-client ---
[INFO] Downloading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-client/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-client/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 13.4 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-client/1.10-SNAPSHOT/bitrepository-client-1.10-20170608.132800-5.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-client/1.10-SNAPSHOT/bitrepository-client-1.10-20170608.132800-5.jar (191 KB at 3230.9 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-client/1.10-SNAPSHOT/bitrepository-client-1.10-20170608.132800-5.pom
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-client/1.10-SNAPSHOT/bitrepository-client-1.10-20170608.132800-5.pom (2 KB at 26.0 KB/sec)
[INFO] Downloading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-client/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-client/maven-metadata.xml (447 B at 13.6 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-client/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-client/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 25.1 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-client/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-client/maven-metadata.xml (447 B at 8.6 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-client/1.10-SNAPSHOT/bitrepository-client-1.10-20170608.132800-5-tests.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-client/1.10-SNAPSHOT/bitrepository-client-1.10-20170608.132800-5-tests.jar (114 KB at 2070.6 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-client/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-client/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 38.0 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-client/1.10-SNAPSHOT/bitrepository-client-1.10-20170608.132800-5-sources.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-client/1.10-SNAPSHOT/bitrepository-client-1.10-20170608.132800-5-sources.jar (196 KB at 3315.7 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-client/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-client/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 45.3 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-client/1.10-SNAPSHOT/bitrepository-client-1.10-20170608.132800-5-distribution.tar.gz
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-client/1.10-SNAPSHOT/bitrepository-client-1.10-20170608.132800-5-distribution.tar.gz (7826 KB at 17990.3 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-client/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-client/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 39.0 KB/sec)
[JENKINS] Archiving disabled
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Service 1.10-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-service ---
[INFO] Deleting /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-service/target
[INFO] 
[INFO] --- jacoco-maven-plugin:0.7.5.201505241946:prepare-agent (default) @ bitrepository-service ---
[INFO] argLine set to -javaagent:/home/cibuild01/.m2/repository/org/jacoco/org.jacoco.agent/0.7.5.201505241946/org.jacoco.agent-0.7.5.201505241946-runtime.jar=destfile=/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-service/target/jacoco.exec
[INFO] 
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ bitrepository-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-service ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 53 source files to /home/cibuild01/workspace/Bitrepository-reference-test/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-reference-test/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-reference-test/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 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
15:28:13.458 WARN  o.b.service.database.DatabaseUtils - Migrating AuditContributorDB from version 1 to 2.
15:28:13.844 WARN  o.b.service.database.DatabaseUtils - Migrating AuditContributorDB from version 2 to 3.
15:28:14.800 WARN  o.b.service.database.DatabaseUtils - Migrating AuditContributorDB from version 3 to 4.
15:28:14.911 WARN  o.b.service.database.DatabaseUtils - Migrating AuditContributorDB from version 4 to 5.
      Test success: testMigratingAuditContributorDatabase
    Starting testcase AuditTrailContributorDatabaseTest
      Test starting: testAuditTrailDatabaseExtraction
        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: testAuditTrailDatabaseExtraction
      Test starting: testAuditTrailDatabaseExtractionOrder
        Description: Test the order of extraction
        Step: Setup variables and database connection
        Step: Populate the database.
        Step: Extract 3 audit-trails
        Step: Extract 3 audit-trails, with larger seq-number than the first
      Test success: testAuditTrailDatabaseExtractionOrder
      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 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
        Step: Throw the exception with a ResponseInfo
      Test success: testIdentifyContributor
    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
      Test starting: componentIDTest
      Test success: componentIDTest
      Finished testcase
  Finished suite
Finished project
Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 20.686 sec - in TestSuite

Results :

Tests run: 8, Failures: 0, Errors: 0, Skipped: 0

[JENKINS] Recording test results
[INFO] 
[INFO] --- jacoco-maven-plugin:0.7.5.201505241946:report (report) @ bitrepository-service ---
[INFO] Analyzed bundle 'Bitrepository Service' with 48 classes
[INFO] 
[INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ bitrepository-service ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-service/target/bitrepository-service-1.10-SNAPSHOT.jar
[INFO] 
[INFO] --- maven-jar-plugin:2.4:test-jar (default) @ bitrepository-service ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-service/target/bitrepository-service-1.10-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-reference-test/bitrepository-service/target/bitrepository-service-1.10-SNAPSHOT-sources.jar
[INFO] 
[INFO] --- maven-install-plugin:2.5.1:install (default-install) @ bitrepository-service ---
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-service/target/bitrepository-service-1.10-SNAPSHOT.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-service/1.10-SNAPSHOT/bitrepository-service-1.10-SNAPSHOT.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-service/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-service/1.10-SNAPSHOT/bitrepository-service-1.10-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-service/target/bitrepository-service-1.10-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-service/1.10-SNAPSHOT/bitrepository-service-1.10-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-service/target/bitrepository-service-1.10-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-service/1.10-SNAPSHOT/bitrepository-service-1.10-SNAPSHOT-sources.jar
[INFO] 
[INFO] --- maven-deploy-plugin:2.8.1:deploy (default-deploy) @ bitrepository-service ---
[INFO] Downloading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-service/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-service/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 12.4 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-service/1.10-SNAPSHOT/bitrepository-service-1.10-20170608.132826-5.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-service/1.10-SNAPSHOT/bitrepository-service-1.10-20170608.132826-5.jar (93 KB at 2260.8 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-service/1.10-SNAPSHOT/bitrepository-service-1.10-20170608.132826-5.pom
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-service/1.10-SNAPSHOT/bitrepository-service-1.10-20170608.132826-5.pom (3 KB at 73.5 KB/sec)
[INFO] Downloading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-service/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-service/maven-metadata.xml (448 B at 23.0 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-service/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-service/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 32.2 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-service/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-service/maven-metadata.xml (448 B at 11.2 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-service/1.10-SNAPSHOT/bitrepository-service-1.10-20170608.132826-5-tests.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-service/1.10-SNAPSHOT/bitrepository-service-1.10-20170608.132826-5-tests.jar (255 KB at 4896.8 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-service/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-service/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 23.8 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-service/1.10-SNAPSHOT/bitrepository-service-1.10-20170608.132826-5-sources.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-service/1.10-SNAPSHOT/bitrepository-service-1.10-20170608.132826-5-sources.jar (89 KB at 1848.2 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-service/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-service/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 33.1 KB/sec)
[JENKINS] Archiving disabled
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Integrity Service 1.10-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-integrity-service ---
[INFO] Deleting /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integrity-service/target
[INFO] 
[INFO] --- jacoco-maven-plugin:0.7.5.201505241946:prepare-agent (default) @ bitrepository-integrity-service ---
[INFO] argLine set to -javaagent:/home/cibuild01/.m2/repository/org/jacoco/org.jacoco.agent/0.7.5.201505241946/org.jacoco.agent-0.7.5.201505241946-runtime.jar=destfile=/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integrity-service/target/jacoco.exec
[INFO] 
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ bitrepository-integrity-service ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 15 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ bitrepository-integrity-service ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 71 source files to /home/cibuild01/workspace/Bitrepository-reference-test/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 26 source files to /home/cibuild01/workspace/Bitrepository-reference-test/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-reference-test/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
    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 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
      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 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
15:28:40.695 ERROR o.b.i.c.DelegatingIntegrityInformationCollector - Unexpected failure!
java.lang.RuntimeException: null
	at org.bitrepository.integrityservice.collector.DelegatingIntegrityInformationCollector.getChecksums(DelegatingIntegrityInformationCollector.java:89)
	at org.bitrepository.integrityservice.collector.IntegrityInformationCollectorTest.testCollectorHandleChecksumClientFailures(IntegrityInformationCollectorTest.java:202)
	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:498)
	at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:86)
	at org.testng.internal.Invoker.invokeMethod(Invoker.java:643)
	at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:820)
	at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1128)
	at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:129)
	at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:112)
	at org.testng.TestRunner.privateRun(TestRunner.java:782)
	at org.testng.TestRunner.run(TestRunner.java:632)
	at org.testng.SuiteRunner.runTest(SuiteRunner.java:366)
	at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:361)
	at org.testng.SuiteRunner.privateRun(SuiteRunner.java:319)
	at org.testng.SuiteRunner.run(SuiteRunner.java:268)
	at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
	at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
	at org.testng.TestNG.runSuitesSequentially(TestNG.java:1244)
	at org.testng.TestNG.runSuitesLocally(TestNG.java:1169)
	at org.testng.TestNG.run(TestNG.java:1064)
	at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:115)
	at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:204)
	at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:107)
	at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:112)
	at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
      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
15:28:40.710 ERROR o.b.i.c.DelegatingIntegrityInformationCollector - Unexpected failure!
java.lang.RuntimeException: null
	at org.bitrepository.integrityservice.collector.DelegatingIntegrityInformationCollector.getFile(DelegatingIntegrityInformationCollector.java:100)
	at org.bitrepository.integrityservice.collector.IntegrityInformationCollectorTest.testCollectorHandleGetFileClientFailures(IntegrityInformationCollectorTest.java:241)
	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:498)
	at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:86)
	at org.testng.internal.Invoker.invokeMethod(Invoker.java:643)
	at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:820)
	at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1128)
	at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:129)
	at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:112)
	at org.testng.TestRunner.privateRun(TestRunner.java:782)
	at org.testng.TestRunner.run(TestRunner.java:632)
	at org.testng.SuiteRunner.runTest(SuiteRunner.java:366)
	at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:361)
	at org.testng.SuiteRunner.privateRun(SuiteRunner.java:319)
	at org.testng.SuiteRunner.run(SuiteRunner.java:268)
	at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
	at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
	at org.testng.TestNG.runSuitesSequentially(TestNG.java:1244)
	at org.testng.TestNG.runSuitesLocally(TestNG.java:1169)
	at org.testng.TestNG.run(TestNG.java:1064)
	at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:115)
	at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:204)
	at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:107)
	at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:112)
	at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
      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
15:28:40.719 ERROR o.b.i.c.DelegatingIntegrityInformationCollector - Unexpected failure!
java.lang.RuntimeException: null
	at org.bitrepository.integrityservice.collector.DelegatingIntegrityInformationCollector.getFileIDs(DelegatingIntegrityInformationCollector.java:78)
	at org.bitrepository.integrityservice.collector.IntegrityInformationCollectorTest.testCollectorHandleGetFileIDsClientFailures(IntegrityInformationCollectorTest.java:221)
	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:498)
	at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:86)
	at org.testng.internal.Invoker.invokeMethod(Invoker.java:643)
	at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:820)
	at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1128)
	at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:129)
	at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:112)
	at org.testng.TestRunner.privateRun(TestRunner.java:782)
	at org.testng.TestRunner.run(TestRunner.java:632)
	at org.testng.SuiteRunner.runTest(SuiteRunner.java:366)
	at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:361)
	at org.testng.SuiteRunner.privateRun(SuiteRunner.java:319)
	at org.testng.SuiteRunner.run(SuiteRunner.java:268)
	at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
	at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
	at org.testng.TestNG.runSuitesSequentially(TestNG.java:1244)
	at org.testng.TestNG.runSuitesLocally(TestNG.java:1169)
	at org.testng.TestNG.run(TestNG.java:1064)
	at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:115)
	at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:204)
	at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:107)
	at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:112)
	at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
      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
15:28:40.749 ERROR o.b.i.c.DelegatingIntegrityInformationCollector - Unexpected failure!
java.lang.RuntimeException: null
	at org.bitrepository.integrityservice.collector.DelegatingIntegrityInformationCollector.putFile(DelegatingIntegrityInformationCollector.java:111)
	at org.bitrepository.integrityservice.collector.IntegrityInformationCollectorTest.testCollectorHandlePutFileClientFailures(IntegrityInformationCollectorTest.java:262)
	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:498)
	at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:86)
	at org.testng.internal.Invoker.invokeMethod(Invoker.java:643)
	at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:820)
	at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1128)
	at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:129)
	at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:112)
	at org.testng.TestRunner.privateRun(TestRunner.java:782)
	at org.testng.TestRunner.run(TestRunner.java:632)
	at org.testng.SuiteRunner.runTest(SuiteRunner.java:366)
	at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:361)
	at org.testng.SuiteRunner.privateRun(SuiteRunner.java:319)
	at org.testng.SuiteRunner.run(SuiteRunner.java:268)
	at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
	at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
	at org.testng.TestNG.runSuitesSequentially(TestNG.java:1244)
	at org.testng.TestNG.runSuitesLocally(TestNG.java:1169)
	at org.testng.TestNG.run(TestNG.java:1064)
	at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:115)
	at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:204)
	at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:107)
	at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:112)
	at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
      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 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 .
15:28:41.017 WARN  o.b.i.c.IntegrityCollectorEventHandler - Component failure for 'test-pillar-1'.
15:28:41.019 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 .
15:28:41.498 WARN  o.b.i.c.IntegrityCollectorEventHandler - Component failure for 'test-pillar-1'.
15:28:41.503 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
15:28:42.767 WARN  o.b.i.c.IntegrityCollectorEventHandler - Component failure for 'test-pillar-1'.
15:28:42.767 WARN  o.b.i.c.IntegrityCollectorEventHandler - Failure: null: null: FAILED: , Problem encountered
      Test success: testRetryCollectionWhenNegativeReply
    Starting testcase IntegrityDAOTest
      Test starting: initialStateExtractionTest
        Description: Tests the initial state of the IntegrityModel. Should not contain any data.
      Test success: initialStateExtractionTest
      Test starting: instantiationTest
        Description: Testing the connection to the integrity database.
      Test success: instantiationTest
      Test starting: reinitialiseDatabaseTest
        Description: Testing the connection to the integrity database.
        Step: Setup manually.
        Step: Close the connection and create another one.
      Test success: reinitialiseDatabaseTest
      Test starting: testCorrectDateHandling
        Description: Testing the correct ingest and extraction of file and checksum dates
      Test success: testCorrectDateHandling
      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
        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.
        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
        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.
        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.
        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: testExtractingAllMissingFiles
        Description: Tests that missing files can be extracted.
        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
      Test success: testExtractingAllMissingFiles
      Test starting: testExtractingAllMissingFilesForPillarsLimits
        Description: Tests the limits for extracting missing files for specific pillars.
        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
        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.
        Step: Create data
      Test success: testFindOrphanFiles
      Test starting: testGetFileIDAtIndex
        Description: Tests that a fileID at a given index can be extracted.
        Step: Extract a fileID from the empty database
        Step: Insert test data into database
        Step: Extract the first fileID
        Step: Extract a fileID at an incomprehendable index from the database
      Test success: testGetFileIDAtIndex
      Test starting: testGetLatestChecksumDateEntryForCollection
        Description: Tests that checksum date entries can be retrieved and manipulated.
        Step: Create data
      Test success: testGetLatestChecksumDateEntryForCollection
      Test starting: testGetLatestFileDateEntryForCollection
        Description: Tests that checksum date entries can be retrieved and manipulated.
        Step: Create data
      Test success: testGetLatestFileDateEntryForCollection
      Test starting: testIngestOfChecksumsData
        Description: Tests the ingesting of checksums data
        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
        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.
        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.
        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.
        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.
        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 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 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 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.
15:29:34.480 WARN  o.b.i.c.IntegrityCollectorEventHandler - Component failure for 'test-pillar-1'.
15:29:34.485 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
15:29:34.639 WARN  o.b.i.c.IntegrityCollectorEventHandler - Component failure for 'test-pillar-1'.
15:29:34.640 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
15:29:35.313 WARN  o.b.i.c.IntegrityCollectorEventHandler - Component failure for 'test-pillar-1'.
15:29:35.318 WARN  o.b.i.c.IntegrityCollectorEventHandler - Failure: null: null: FAILED: , Operation failed
      Test success: testRetryCollectionWhenNegativeReply
    Starting testcase IntegrityDBToolsTest
      Test starting: testAddCollectionSuccess
        Description: Tests that a new collection can be added to the integrity database
        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.
        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.
        Step: Extract initial list of collections.
        Step: Attempt to remove the non-existing collection.
      Test success: testRemoveNonExistingCollection
    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 SaltedChecksumWorkflowTest
      Test starting: testInconsistentChecksums
        Description: Test that the workflow discovers and handles inconsistent checksums
        Step: Prepare for calls to mocks
        Step: Run workflow for checking salted checksum.
15:29:41.188 WARN  o.b.i.w.SaltedChecksumWorkflow - Failure in checksum salted checksum: Inconsistent salted checksum found for file 'test-file-1' with checksumspec 'HMAC_MD5' and salt 'dee1c1bffed38f4a15f9e89f0a3b2ab9f8c7'. The pillars had the checksums: {pillar2=efefcefc, pillar1=bfecefef}
      Test success: testInconsistentChecksums
      Test starting: testNoFilesInCollection
        Description: Test that the workflow does nothing, when it has no files in the collection.
        Step: Prepare for calls to mocks
        Step: Run workflow for checking salted checksum.
      Test success: testNoFilesInCollection
      Test starting: testNoReceivedChecksums
        Description: Test that the workflow handles the case, when no checksums are received
        Step: Prepare for calls to mocks
        Step: Run workflow for checking salted checksum.
15:29:41.500 WARN  o.b.i.c.SimpleChecksumEventHandler - Failure: null: null: FAILED: , 
15:29:41.506 WARN  o.b.i.w.SaltedChecksumWorkflow - Failure in checksum salted checksum: No checksums with checksumSpec 'org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1270fd7c[checksumType=HMAC_MD5, checksumSalt={-84,72,-94,86,-4,66,15,79,77,-5,44,-1,-15,-95,68,-50,-66,-14}, otherChecksumType=<null>(default)]' received for file 'test-file-1'.
      Test success: testNoReceivedChecksums
      Test starting: testOneComponentFailureAndTwoOtherAgreeOnChecksum
        Description: Test that the workflow works when both pillars deliver the same checksum.
        Step: Prepare for calls to mocks
        Step: Run workflow for checking salted checksum.
15:29:41.653 WARN  o.b.i.c.SimpleChecksumEventHandler - Component failure for 'pillar3'.
15:29:41.653 WARN  o.b.i.c.SimpleChecksumEventHandler - Failure: null: null: FAILED: , COMPONENT FAILED
      Test success: testOneComponentFailureAndTwoOtherAgreeOnChecksum
      Test starting: testOneComponentFailureAndTwoOtherDisagreeOnChecksum
        Description: Test that the workflow works when both pillars deliver the same checksum.
        Step: Prepare for calls to mocks
        Step: Run workflow for checking salted checksum.
15:29:41.782 WARN  o.b.i.c.SimpleChecksumEventHandler - Component failure for 'pillar3'.
15:29:41.783 WARN  o.b.i.c.SimpleChecksumEventHandler - Failure: null: null: FAILED: , COMPONENT FAILED
15:29:41.784 WARN  o.b.i.w.SaltedChecksumWorkflow - Failure in checksum salted checksum: Inconsistent salted checksum found for file 'test-file-1' with checksumspec 'HMAC_MD5' and salt '10dd47cffae7bf4357fb2cdf46ee01a34a3e'. The pillars had the checksums: {pillar2=efefcefc, pillar1=bfecefef}
      Test success: testOneComponentFailureAndTwoOtherDisagreeOnChecksum
      Test starting: testSuccess
        Description: Test that the workflow works when both pillars deliver the same checksum.
        Step: Prepare for calls to mocks
        Step: Run workflow for checking salted checksum.
      Test success: testSuccess
    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 IntegrityAlerterTest
      Test starting: testIntegrityFailed
        Description: Test the IntegrityFailed method for the IntegrityAlerter
        Step: Call the function for integrity failure.
15:29:42.231 WARN  o.b.i.a.IntegrityAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@547b081e[origDateTime=2017-06-08T15:29:42.230+02:00, alarmCode=INTEGRITY_ISSUE, alarmRaiser=IntegrityAlerterTest, alarmText=Testaintegrity alarm, fileID=<null>(default), collectionID=TwoPillarCollection]
          Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@3471e039[correlationID=de841da0-6c00-4d80-b069-bdae469cecf0, collectionID=TwoPillarCollection, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-IntegrityAlerterTest-cibuild01-contributor, from=IntegrityAlerterTest, to=<null>(default), version=30, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@547b081e[origDateTime=2017-06-08T15:29:42.230+02:00, alarmCode=INTEGRITY_ISSUE, alarmRaiser=IntegrityAlerterTest, alarmText=Testaintegrity alarm, fileID=<null>(default), collectionID=TwoPillarCollection]]
      Test success: testIntegrityFailed
      Test starting: testOperationFailed
        Description: Test the OperationFailed method for the IntegrityAlerter
        Step: Call the function for integrity failure.
15:29:42.793 WARN  o.b.i.a.IntegrityAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@47d91a2d[origDateTime=2017-06-08T15:29:42.792+02:00, alarmCode=FAILED_OPERATION, alarmRaiser=IntegrityAlerterTest, alarmText=Testing the ability to fail., fileID=<null>(default), collectionID=TwoPillarCollection]
          Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@227a0c5a[correlationID=8814653c-7eac-44bc-9798-2b523b7c7cc2, collectionID=TwoPillarCollection, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-IntegrityAlerterTest-cibuild01-contributor, from=IntegrityAlerterTest, to=<null>(default), version=30, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@47d91a2d[origDateTime=2017-06-08T15:29:42.792+02:00, alarmCode=FAILED_OPERATION, alarmRaiser=IntegrityAlerterTest, alarmText=Testing the ability to fail., fileID=<null>(default), collectionID=TwoPillarCollection]]
      Test success: testOperationFailed
    Starting testcase GetChecksumForFileStepTest
      Test starting: testComponentFailure
        Description: Test step for retrieving the checksum of a single file, when one pillar fails.
        Step: Setup mock answers
        Step: Validate the file ids
15:29:42.957 WARN  o.b.i.c.SimpleChecksumEventHandler - Component failure for 'test-pillar-3'.
15:29:42.959 WARN  o.b.i.c.SimpleChecksumEventHandler - Failure: null: null: FAILED: , COMPONENT FAILED
      Test success: testComponentFailure
      Test starting: testFullData
        Description: Test step for retrieving the checksum of a single file, when all three pillars deliver results.
        Step: Setup mock answers
        Step: Validate the checksum results
      Test success: testFullData
      Test starting: testNoResults
        Description: Test step for retrieving the checksum of a single file, when no results are delivered.
        Step: Setup mock answers
        Step: Validate the checksum results
      Test success: testNoResults
    Starting testcase IntegrityDatabaseTest
      Test starting: initialStateExtractionTest
        Description: Tests the initial state of the IntegrityModel. Should not contain any data.
        Step: Test the 'findChecksumsOlderThan'
        Step: Test the 'findMissingChecksums'
        Step: Test the 'findMissingFiles'
        Step: Test the 'getAllFileIDs'
        Step: Test the 'getFileInfos'
        Step: Test the 'getPillarCollectionMetrics'
      Test success: initialStateExtractionTest
      Test starting: instantiationTest
        Description: Tests that the connection can be instantaited.
      Test success: instantiationTest
      Test starting: testDeletingEntry
        Description: Tests the deletion of an FileID entry.
        Step: Create data
        Step: Delete the entry
      Test success: testDeletingEntry
      Test starting: testIngestOfChecksumsData
        Description: Tests the ingesting of checksums data
        Step: Create data
        Step: Extract the data
      Test success: testIngestOfChecksumsData
      Test starting: testIngestOfFileIDsData
        Description: Tests the ingesting of file ids data
        Step: Create data
        Step: Extract the data
      Test success: testIngestOfFileIDsData
    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.
15:29:51.313 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)
	at org.bitrepository.service.workflow.Workflow.performStep(Workflow.java:63)
	at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflow.getFileStep(RepairMissingFilesWorkflow.java:174)
	at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflow.repairMissingFiles(RepairMissingFilesWorkflow.java:114)
	at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflow.start(RepairMissingFilesWorkflow.java:88)
	at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflowTest.testFailedGetFile(RepairMissingFilesWorkflowTest.java:199)
	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:498)
	at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:86)
	at org.testng.internal.Invoker.invokeMethod(Invoker.java:643)
	at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:820)
	at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1128)
	at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:129)
	at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:112)
	at org.testng.TestRunner.privateRun(TestRunner.java:782)
	at org.testng.TestRunner.run(TestRunner.java:632)
	at org.testng.SuiteRunner.runTest(SuiteRunner.java:366)
	at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:361)
	at org.testng.SuiteRunner.privateRun(SuiteRunner.java:319)
	at org.testng.SuiteRunner.run(SuiteRunner.java:268)
	at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
	at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
	at org.testng.TestNG.runSuitesSequentially(TestNG.java:1244)
	at org.testng.TestNG.runSuitesLocally(TestNG.java:1169)
	at org.testng.TestNG.run(TestNG.java:1064)
	at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:115)
	at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:204)
	at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:107)
	at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:112)
	at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
15:29:51.318 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)
	at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflow.getFileStep(RepairMissingFilesWorkflow.java:174)
	at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflow.repairMissingFiles(RepairMissingFilesWorkflow.java:114)
	at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflow.start(RepairMissingFilesWorkflow.java:88)
	at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflowTest.testFailedGetFile(RepairMissingFilesWorkflowTest.java:199)
	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:498)
	at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:86)
	at org.testng.internal.Invoker.invokeMethod(Invoker.java:643)
	at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:820)
	at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1128)
	at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:129)
	at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:112)
	at org.testng.TestRunner.privateRun(TestRunner.java:782)
	at org.testng.TestRunner.run(TestRunner.java:632)
	at org.testng.SuiteRunner.runTest(SuiteRunner.java:366)
	at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:361)
	at org.testng.SuiteRunner.privateRun(SuiteRunner.java:319)
	at org.testng.SuiteRunner.run(SuiteRunner.java:268)
	at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
	at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
	at org.testng.TestNG.runSuitesSequentially(TestNG.java:1244)
	at org.testng.TestNG.runSuitesLocally(TestNG.java:1169)
	at org.testng.TestNG.run(TestNG.java:1064)
	at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:115)
	at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:204)
	at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:107)
	at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:112)
	at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
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)
	at org.bitrepository.service.workflow.Workflow.performStep(Workflow.java:63)
	... 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.
15:29:51.450 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)
	at org.bitrepository.service.workflow.Workflow.performStep(Workflow.java:63)
	at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflow.putFileStep(RepairMissingFilesWorkflow.java:189)
	at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflow.repairMissingFiles(RepairMissingFilesWorkflow.java:115)
	at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflow.start(RepairMissingFilesWorkflow.java:88)
	at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflowTest.testFailedPutFile(RepairMissingFilesWorkflowTest.java:249)
	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:498)
	at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:86)
	at org.testng.internal.Invoker.invokeMethod(Invoker.java:643)
	at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:820)
	at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1128)
	at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:129)
	at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:112)
	at org.testng.TestRunner.privateRun(TestRunner.java:782)
	at org.testng.TestRunner.run(TestRunner.java:632)
	at org.testng.SuiteRunner.runTest(SuiteRunner.java:366)
	at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:361)
	at org.testng.SuiteRunner.privateRun(SuiteRunner.java:319)
	at org.testng.SuiteRunner.run(SuiteRunner.java:268)
	at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
	at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
	at org.testng.TestNG.runSuitesSequentially(TestNG.java:1244)
	at org.testng.TestNG.runSuitesLocally(TestNG.java:1169)
	at org.testng.TestNG.run(TestNG.java:1064)
	at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:115)
	at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:204)
	at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:107)
	at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:112)
	at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
15:29:51.455 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)
	at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflow.putFileStep(RepairMissingFilesWorkflow.java:189)
	at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflow.repairMissingFiles(RepairMissingFilesWorkflow.java:115)
	at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflow.start(RepairMissingFilesWorkflow.java:88)
	at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflowTest.testFailedPutFile(RepairMissingFilesWorkflowTest.java:249)
	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:498)
	at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:86)
	at org.testng.internal.Invoker.invokeMethod(Invoker.java:643)
	at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:820)
	at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1128)
	at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:129)
	at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:112)
	at org.testng.TestRunner.privateRun(TestRunner.java:782)
	at org.testng.TestRunner.run(TestRunner.java:632)
	at org.testng.SuiteRunner.runTest(SuiteRunner.java:366)
	at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:361)
	at org.testng.SuiteRunner.privateRun(SuiteRunner.java:319)
	at org.testng.SuiteRunner.run(SuiteRunner.java:268)
	at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
	at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
	at org.testng.TestNG.runSuitesSequentially(TestNG.java:1244)
	at org.testng.TestNG.runSuitesLocally(TestNG.java:1169)
	at org.testng.TestNG.run(TestNG.java:1064)
	at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:115)
	at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:204)
	at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:107)
	at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:112)
	at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
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)
	at org.bitrepository.service.workflow.Workflow.performStep(Workflow.java:63)
	... 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.
15:29:52.943 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, localhost/0:0:0:0:0:0:0:1] failed: Connection refused (Connection refused)
	at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:151)
	at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:353)
	at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:380)
	at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236)
	at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:184)
	at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:88)
	at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110)
	at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)
	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:107)
	at org.bitrepository.protocol.http.HttpFileExchange.deleteFile(HttpFileExchange.java:261)
	at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflow.deleteUrl(RepairMissingFilesWorkflow.java:204)
	at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflow.repairMissingFiles(RepairMissingFilesWorkflow.java:116)
	at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflow.start(RepairMissingFilesWorkflow.java:88)
	at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflowTest.testSuccesRepair(RepairMissingFilesWorkflowTest.java:160)
	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:498)
	at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:86)
	at org.testng.internal.Invoker.invokeMethod(Invoker.java:643)
	at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:820)
	at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1128)
	at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:129)
	at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:112)
	at org.testng.TestRunner.privateRun(TestRunner.java:782)
	at org.testng.TestRunner.run(TestRunner.java:632)
	at org.testng.SuiteRunner.runTest(SuiteRunner.java:366)
	at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:361)
	at org.testng.SuiteRunner.privateRun(SuiteRunner.java:319)
	at org.testng.SuiteRunner.run(SuiteRunner.java:268)
	at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
	at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
	at org.testng.TestNG.runSuitesSequentially(TestNG.java:1244)
	at org.testng.TestNG.runSuitesLocally(TestNG.java:1169)
	at org.testng.TestNG.run(TestNG.java:1064)
	at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:115)
	at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:204)
	at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:107)
	at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:112)
	at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
Caused by: java.net.ConnectException: Connection refused (Connection refused)
	at java.net.PlainSocketImpl.socketConnect(Native Method)
	at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
	at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
	at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
	at java.net.Socket.connect(Socket.java:589)
	at org.apache.http.conn.socket.PlainConnectionSocketFactory.connectSocket(PlainConnectionSocketFactory.java:74)
	at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:134)
	... 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.
        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.
        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.
        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.
        Step: Validate the file ids
      Test success: testNoData
      Test starting: testSimilarData
        Description: Test the checksum integrity validator when all pillars have similar data.
        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.
        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.
        Step: Add data to the cache
        Step: Perform the step
        Step: Validate the file ids
      Test success: testTwoDisagreeingChecksums
      Finished testcase
  Finished suite
Finished project
Tests run: 101, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 89.216 sec - in TestSuite

Results :

Tests run: 101, Failures: 0, Errors: 0, Skipped: 0

[JENKINS] Recording test results
[INFO] 
[INFO] --- jacoco-maven-plugin:0.7.5.201505241946:report (report) @ bitrepository-integrity-service ---
[INFO] Analyzed bundle 'Bitrepository Integrity Service' with 79 classes
[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-reference-test/bitrepository-integrity-service/target/bitrepository-integrity-service-1.10-SNAPSHOT]
[INFO] Processing war project
[INFO] Copying webapp resources [/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integrity-service/src/main/webapp]
[INFO] Webapp assembled in [306 msecs]
[INFO] Building war: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integrity-service/target/bitrepository-integrity-service-1.10-SNAPSHOT.war
[INFO] 
[INFO] --- maven-jar-plugin:2.4:test-jar (default) @ bitrepository-integrity-service ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integrity-service/target/bitrepository-integrity-service-1.10-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-reference-test/bitrepository-integrity-service/target/bitrepository-integrity-service-1.10-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-reference-test/bitrepository-integrity-service/target/bitrepository-integrity-service-1.10-SNAPSHOT-distribution.tar.gz
[INFO] 
[INFO] --- maven-install-plugin:2.5.1:install (default-install) @ bitrepository-integrity-service ---
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integrity-service/target/bitrepository-integrity-service-1.10-SNAPSHOT.war to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integrity-service/1.10-SNAPSHOT/bitrepository-integrity-service-1.10-SNAPSHOT.war
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integrity-service/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integrity-service/1.10-SNAPSHOT/bitrepository-integrity-service-1.10-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integrity-service/target/bitrepository-integrity-service-1.10-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integrity-service/1.10-SNAPSHOT/bitrepository-integrity-service-1.10-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integrity-service/target/bitrepository-integrity-service-1.10-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integrity-service/1.10-SNAPSHOT/bitrepository-integrity-service-1.10-SNAPSHOT-sources.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integrity-service/target/bitrepository-integrity-service-1.10-SNAPSHOT-distribution.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integrity-service/1.10-SNAPSHOT/bitrepository-integrity-service-1.10-SNAPSHOT-distribution.tar.gz
[INFO] 
[INFO] --- maven-deploy-plugin:2.8.1:deploy (default-deploy) @ bitrepository-integrity-service ---
[INFO] Downloading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integrity-service/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integrity-service/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 7.8 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integrity-service/1.10-SNAPSHOT/bitrepository-integrity-service-1.10-20170608.133010-5.war
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integrity-service/1.10-SNAPSHOT/bitrepository-integrity-service-1.10-20170608.133010-5.war (18208 KB at 22150.3 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integrity-service/1.10-SNAPSHOT/bitrepository-integrity-service-1.10-20170608.133010-5.pom
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integrity-service/1.10-SNAPSHOT/bitrepository-integrity-service-1.10-20170608.133010-5.pom (6 KB at 140.0 KB/sec)
[INFO] Downloading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integrity-service/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integrity-service/maven-metadata.xml (458 B at 28.0 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integrity-service/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integrity-service/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 47.2 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integrity-service/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integrity-service/maven-metadata.xml (458 B at 11.2 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integrity-service/1.10-SNAPSHOT/bitrepository-integrity-service-1.10-20170608.133010-5-tests.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integrity-service/1.10-SNAPSHOT/bitrepository-integrity-service-1.10-20170608.133010-5-tests.jar (186 KB at 3630.0 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integrity-service/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integrity-service/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 33.7 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integrity-service/1.10-SNAPSHOT/bitrepository-integrity-service-1.10-20170608.133010-5-sources.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integrity-service/1.10-SNAPSHOT/bitrepository-integrity-service-1.10-20170608.133010-5-sources.jar (141 KB at 2599.6 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integrity-service/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integrity-service/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 44.3 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integrity-service/1.10-SNAPSHOT/bitrepository-integrity-service-1.10-20170608.133010-5-distribution.tar.gz
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integrity-service/1.10-SNAPSHOT/bitrepository-integrity-service-1.10-20170608.133010-5-distribution.tar.gz (18199 KB at 17482.2 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integrity-service/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integrity-service/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 39.3 KB/sec)
[JENKINS] Archiving disabled
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Alarm Service 1.10-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-alarm-service ---
[INFO] Deleting /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-alarm-service/target
[INFO] 
[INFO] --- jacoco-maven-plugin:0.7.5.201505241946:prepare-agent (default) @ bitrepository-alarm-service ---
[INFO] argLine set to -javaagent:/home/cibuild01/.m2/repository/org/jacoco/org.jacoco.agent/0.7.5.201505241946/org.jacoco.agent-0.7.5.201505241946-runtime.jar=destfile=/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-alarm-service/target/jacoco.exec
[INFO] 
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ bitrepository-alarm-service ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 8 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-reference-test/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-reference-test/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-reference-test/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 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
    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
      Test starting: alarmDatabaseCorrectTimestampTest
        Description: Testing the correct ingest and extraction of alarm dates
        Step: Prepare, check and ingest alarms
        Step: Extract and check alarms
      Test success: alarmDatabaseCorrectTimestampTest
        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
15:30:28.360 WARN  o.b.alarm.handling.AlarmMediator - Recieved unexpected message: 'org.bitrepository.bitrepositorymessages.Message@6626137e[correlationID=<null>(default), collectionID=<null>(default), destination=<null>(default), replyTo=<null>(default), from=<null>(default), to=<null>(default), version=<null>(default), minVersion=<null>(default)]'
        Step: Giv the mediator an AlarmMessage
        Step: Close the mediator.
      Test success: alarmMediatorTest
      Finished testcase
  Finished suite
Finished project
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 11.694 sec - in TestSuite

Results :

Tests run: 6, Failures: 0, Errors: 0, Skipped: 0

[JENKINS] Recording test results
[INFO] 
[INFO] --- jacoco-maven-plugin:0.7.5.201505241946:report (report) @ bitrepository-alarm-service ---
[INFO] Analyzed bundle 'Bitrepository Alarm Service' with 23 classes
[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-reference-test/bitrepository-alarm-service/target/bitrepository-alarm-service-1.10-SNAPSHOT]
[INFO] Processing war project
[INFO] Copying webapp resources [/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-alarm-service/src/main/webapp]
[INFO] Webapp assembled in [134 msecs]
[INFO] Building war: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-alarm-service/target/bitrepository-alarm-service-1.10-SNAPSHOT.war
[INFO] 
[INFO] --- maven-jar-plugin:2.4:test-jar (default) @ bitrepository-alarm-service ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-alarm-service/target/bitrepository-alarm-service-1.10-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-reference-test/bitrepository-alarm-service/target/bitrepository-alarm-service-1.10-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-reference-test/bitrepository-alarm-service/target/bitrepository-alarm-service-1.10-SNAPSHOT-distribution.tar.gz
[INFO] 
[INFO] --- maven-install-plugin:2.5.1:install (default-install) @ bitrepository-alarm-service ---
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-alarm-service/target/bitrepository-alarm-service-1.10-SNAPSHOT.war to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-alarm-service/1.10-SNAPSHOT/bitrepository-alarm-service-1.10-SNAPSHOT.war
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-alarm-service/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-alarm-service/1.10-SNAPSHOT/bitrepository-alarm-service-1.10-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-alarm-service/target/bitrepository-alarm-service-1.10-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-alarm-service/1.10-SNAPSHOT/bitrepository-alarm-service-1.10-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-alarm-service/target/bitrepository-alarm-service-1.10-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-alarm-service/1.10-SNAPSHOT/bitrepository-alarm-service-1.10-SNAPSHOT-sources.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-alarm-service/target/bitrepository-alarm-service-1.10-SNAPSHOT-distribution.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-alarm-service/1.10-SNAPSHOT/bitrepository-alarm-service-1.10-SNAPSHOT-distribution.tar.gz
[INFO] 
[INFO] --- maven-deploy-plugin:2.8.1:deploy (default-deploy) @ bitrepository-alarm-service ---
[INFO] Downloading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-alarm-service/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-alarm-service/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 12.0 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-alarm-service/1.10-SNAPSHOT/bitrepository-alarm-service-1.10-20170608.133032-5.war
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-alarm-service/1.10-SNAPSHOT/bitrepository-alarm-service-1.10-20170608.133032-5.war (18407 KB at 24541.8 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-alarm-service/1.10-SNAPSHOT/bitrepository-alarm-service-1.10-20170608.133032-5.pom
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-alarm-service/1.10-SNAPSHOT/bitrepository-alarm-service-1.10-20170608.133032-5.pom (4 KB at 104.1 KB/sec)
[INFO] Downloading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-alarm-service/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-alarm-service/maven-metadata.xml (454 B at 20.2 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-alarm-service/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-alarm-service/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 45.6 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-alarm-service/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-alarm-service/maven-metadata.xml (454 B at 11.7 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-alarm-service/1.10-SNAPSHOT/bitrepository-alarm-service-1.10-20170608.133032-5-tests.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-alarm-service/1.10-SNAPSHOT/bitrepository-alarm-service-1.10-20170608.133032-5-tests.jar (77 KB at 1561.9 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-alarm-service/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-alarm-service/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 38.2 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-alarm-service/1.10-SNAPSHOT/bitrepository-alarm-service-1.10-20170608.133032-5-sources.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-alarm-service/1.10-SNAPSHOT/bitrepository-alarm-service-1.10-20170608.133032-5-sources.jar (44 KB at 1045.5 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-alarm-service/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-alarm-service/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 30.7 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-alarm-service/1.10-SNAPSHOT/bitrepository-alarm-service-1.10-20170608.133032-5-distribution.tar.gz
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-alarm-service/1.10-SNAPSHOT/bitrepository-alarm-service-1.10-20170608.133032-5-distribution.tar.gz (18405 KB at 27145.7 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-alarm-service/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-alarm-service/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 39.2 KB/sec)
[JENKINS] Archiving disabled
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Audit Trail Service 1.10-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-audit-trail-service ---
[INFO] Deleting /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-audit-trail-service/target
[INFO] 
[INFO] --- jacoco-maven-plugin:0.7.5.201505241946:prepare-agent (default) @ bitrepository-audit-trail-service ---
[INFO] argLine set to -javaagent:/home/cibuild01/.m2/repository/org/jacoco/org.jacoco.agent/0.7.5.201505241946/org.jacoco.agent-0.7.5.201505241946-runtime.jar=destfile=/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-audit-trail-service/target/jacoco.exec
[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 11 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-reference-test/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 8 source files to /home/cibuild01/workspace/Bitrepository-reference-test/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-reference-test/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 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.
15:30:39.996 WARN  o.b.a.collector.IncrementalCollector - Received bad collection id! Expected 'dummy-collection', but got 'FalseCollection1496928639318'.
      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
15:30:40.137 WARN  o.b.a.collector.IncrementalCollector - Event: null: null: COMPONENT_FAILED: ContributorID Contributor1 ResponseCode: REQUEST_NOT_SUPPORTED
15:30:40.165 WARN  o.b.a.collector.IncrementalCollector - Event: null: null: FAILED: , 
15:30:40.183 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:65)
	at org.bitrepository.audittrails.collector.IncrementalCollector.collect(IncrementalCollector.java:134)
	at org.bitrepository.audittrails.collector.IncrementalCollector.performCollection(IncrementalCollector.java:111)
	at org.bitrepository.audittrails.collector.IncrementalCollectorTest$CollectionRunner.run(IncrementalCollectorTest.java:354)
	at java.lang.Thread.run(Thread.java:745)
        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 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
15:30:46.372 WARN  o.b.service.database.DatabaseUtils - Migrating AuditServiceDB from version 2 to 3.
15:30:48.287 WARN  o.b.service.database.DatabaseUtils - Migrating AuditServiceDB from version 3 to 4.
15:30:48.487 WARN  o.b.service.database.DatabaseUtils - Migrating AuditServiceDB from version 4 to 5.
15:30:49.144 WARN  o.b.service.database.DatabaseUtils - Migrating AuditServiceDB from version 5 to 6.
      Test success: testMigratingAuditServiceDatabase
    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 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
      Test starting: auditDatabaseCorrectTimestampTest
        Description: Testing the correct ingest and extraction of audittrail dates
      Test success: auditDatabaseCorrectTimestampTest
    Starting testcase AuditCollectorTest
      Test starting: auditCollectorIntervalTest
        Description: Test that the collector calls the AuditClient at the correct intervals.
      Test success: auditCollectorIntervalTest
    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
      Finished testcase
  Finished suite
Finished project
Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 29.066 sec - in TestSuite

Results :

Tests run: 13, Failures: 0, Errors: 0, Skipped: 0

[JENKINS] Recording test results
[INFO] 
[INFO] --- jacoco-maven-plugin:0.7.5.201505241946:report (report) @ bitrepository-audit-trail-service ---
[INFO] Analyzed bundle 'Bitrepository Audit Trail Service' with 24 classes
[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-reference-test/bitrepository-audit-trail-service/target/bitrepository-audit-trail-service-1.10-SNAPSHOT]
[INFO] Processing war project
[INFO] Copying webapp resources [/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-audit-trail-service/src/main/webapp]
[INFO] Webapp assembled in [176 msecs]
[INFO] Building war: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-audit-trail-service/target/bitrepository-audit-trail-service-1.10-SNAPSHOT.war
[INFO] 
[INFO] --- maven-jar-plugin:2.4:test-jar (default) @ bitrepository-audit-trail-service ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-audit-trail-service/target/bitrepository-audit-trail-service-1.10-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-reference-test/bitrepository-audit-trail-service/target/bitrepository-audit-trail-service-1.10-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-reference-test/bitrepository-audit-trail-service/target/bitrepository-audit-trail-service-1.10-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-reference-test/bitrepository-audit-trail-service/target/bitrepository-audit-trail-service-1.10-SNAPSHOT.war to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-audit-trail-service/1.10-SNAPSHOT/bitrepository-audit-trail-service-1.10-SNAPSHOT.war
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-audit-trail-service/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-audit-trail-service/1.10-SNAPSHOT/bitrepository-audit-trail-service-1.10-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-audit-trail-service/target/bitrepository-audit-trail-service-1.10-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-audit-trail-service/1.10-SNAPSHOT/bitrepository-audit-trail-service-1.10-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-audit-trail-service/target/bitrepository-audit-trail-service-1.10-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-audit-trail-service/1.10-SNAPSHOT/bitrepository-audit-trail-service-1.10-SNAPSHOT-sources.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-audit-trail-service/target/bitrepository-audit-trail-service-1.10-SNAPSHOT-distribution.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-audit-trail-service/1.10-SNAPSHOT/bitrepository-audit-trail-service-1.10-SNAPSHOT-distribution.tar.gz
[INFO] 
[INFO] --- maven-deploy-plugin:2.8.1:deploy (default-deploy) @ bitrepository-audit-trail-service ---
[INFO] Downloading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-audit-trail-service/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-audit-trail-service/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 10.1 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-audit-trail-service/1.10-SNAPSHOT/bitrepository-audit-trail-service-1.10-20170608.133110-5.war
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-audit-trail-service/1.10-SNAPSHOT/bitrepository-audit-trail-service-1.10-20170608.133110-5.war (18110 KB at 19813.6 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-audit-trail-service/1.10-SNAPSHOT/bitrepository-audit-trail-service-1.10-20170608.133110-5.pom
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-audit-trail-service/1.10-SNAPSHOT/bitrepository-audit-trail-service-1.10-20170608.133110-5.pom (4 KB at 49.0 KB/sec)
[INFO] Downloading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-audit-trail-service/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-audit-trail-service/maven-metadata.xml (460 B at 32.1 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-audit-trail-service/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-audit-trail-service/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 37.3 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-audit-trail-service/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-audit-trail-service/maven-metadata.xml (460 B at 7.9 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-audit-trail-service/1.10-SNAPSHOT/bitrepository-audit-trail-service-1.10-20170608.133110-5-tests.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-audit-trail-service/1.10-SNAPSHOT/bitrepository-audit-trail-service-1.10-20170608.133110-5-tests.jar (264 KB at 3657.6 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-audit-trail-service/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-audit-trail-service/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 38.3 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-audit-trail-service/1.10-SNAPSHOT/bitrepository-audit-trail-service-1.10-20170608.133110-5-sources.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-audit-trail-service/1.10-SNAPSHOT/bitrepository-audit-trail-service-1.10-20170608.133110-5-sources.jar (58 KB at 955.6 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-audit-trail-service/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-audit-trail-service/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 34.6 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-audit-trail-service/1.10-SNAPSHOT/bitrepository-audit-trail-service-1.10-20170608.133110-5-distribution.tar.gz
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-audit-trail-service/1.10-SNAPSHOT/bitrepository-audit-trail-service-1.10-20170608.133110-5-distribution.tar.gz (18109 KB at 20838.5 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-audit-trail-service/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-audit-trail-service/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 33.0 KB/sec)
[JENKINS] Archiving disabled
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Reference Pillar 1.10-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] Downloading: https://sbforge.org/nexus/content/groups/public/org/bitrepository/reference/bitrepository-client/1.10-SNAPSHOT/bitrepository-client-1.10-20170608.132800-5-tests.jar
[INFO] Downloaded: https://sbforge.org/nexus/content/groups/public/org/bitrepository/reference/bitrepository-client/1.10-SNAPSHOT/bitrepository-client-1.10-20170608.132800-5-tests.jar (114 KB at 1265.3 KB/sec)
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-reference-pillar ---
[INFO] Deleting /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target
[INFO] 
[INFO] --- jacoco-maven-plugin:0.7.5.201505241946:prepare-agent (default) @ bitrepository-reference-pillar ---
[INFO] argLine set to -javaagent:/home/cibuild01/.m2/repository/org/jacoco/org.jacoco.agent/0.7.5.201505241946/org.jacoco.agent-0.7.5.201505241946-runtime.jar=destfile=/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/jacoco.exec
[INFO] 
[INFO] --- maven-dependency-plugin:2.8:unpack-dependencies (unpack-shared-sqlscripts) @ bitrepository-reference-pillar ---
[INFO] Unpacking /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-service/target/bitrepository-service-1.10-SNAPSHOT.jar to /home/cibuild01/workspace/Bitrepository-reference-test/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 13 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-reference-test/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 13 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-reference-test/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-reference-test/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: testGetChecksumResult
        Description: Tests the restrictions on the GetChecksumResult call to the database.
        Step: Instantiate database with appropriate data.
        Step: Test with no time restrictions
        Step: Test with time restrictions from epoc to now
        Step: Test with very strict time restrictions around the default date
        Step: Test with too new a lower limit
        Step: Test with exact date as both upper and lower limit
        Step: Test with date limit from 1 millis before as lower and exact date a upper limit
        Step: Test with date limit from exact date as lower and 1 millis after date a upper limit
        Step: Test with too old an upper limit
      Test success: testGetChecksumResult
      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: testGetFileIDsWithOldChecksums
        Description: Tests the restrictions on the GetFileIDsWithOldChecksums call to the database.
        Step: Instantiate database with appropriate data.
        Step: Extract all entries with checksum date older than now
        Step: Extract all entries with checksum date older than epoch
        Step: Extract all entries with checksum date older than middle date
      Test success: testGetFileIDsWithOldChecksums
      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 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 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.
15:31:48.727 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 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@391aedcd[correlationID=0f13a756-bbda-45ef-93de-f33f67201333, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsMaximumNumberOfResults-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults, to=Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@53fd4420[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to extract the requested audit trails.], contributor=Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults, resultAddress=<null>(default)]
          Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsMaximumNumberOfResults-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsFinalResponse@171fd7e5[correlationID=0f13a756-bbda-45ef-93de-f33f67201333, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsMaximumNumberOfResults-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults, to=Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@58337c20[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], contributor=Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@7082d3e2[resultAddress=<null>(default), auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@343047c[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@6a0a5b0e[sequenceNumber=1, fileID=fileID1496928709673, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=CHECKSUM_CALCULATED, actionDateTime=2017-06-08T15:31:49.676+02:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@291be813[sequenceNumber=2, fileID=fileID1496928709673, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=DELETE_FILE, actionDateTime=2017-06-08T15:31:49.677+02:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@4fe03311[sequenceNumber=3, fileID=fileID1496928709673, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=FAILURE, actionDateTime=2017-06-08T15:31:49.677+02:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@549bae75[sequenceNumber=4, fileID=fileID1496928709673, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=FILE_MOVED, actionDateTime=2017-06-08T15:31:49.677+02:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@6cf14dc3[sequenceNumber=5, fileID=fileID1496928709673, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=GET_CHECKSUMS, actionDateTime=2017-06-08T15:31:49.677+02: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@70e45ea9[correlationID=af65c305-b9c0-475f-843b-30eb4a61d639, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSpecificRequests-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSpecificRequests, to=Pillar-checksumPillarGetAuditTrailsSpecificRequests, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@1a8bfac8[responseCode=IDENTIFICATION_POSITIVE, responseText=<null>(default)]]
        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@7c41e0f0[correlationID=af65c305-b9c0-475f-843b-30eb4a61d639, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSpecificRequests-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSpecificRequests, to=Pillar-checksumPillarGetAuditTrailsSpecificRequests, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@2e02f8c7[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to extract the requested audit trails.], contributor=Pillar-checksumPillarGetAuditTrailsSpecificRequests, resultAddress=<null>(default)]
          Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsFinalResponse@6b1a0a75[correlationID=af65c305-b9c0-475f-843b-30eb4a61d639, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSpecificRequests-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSpecificRequests, to=Pillar-checksumPillarGetAuditTrailsSpecificRequests, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@6abc82c7[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], contributor=Pillar-checksumPillarGetAuditTrailsSpecificRequests, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@1909b900[resultAddress=<null>(default), auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@2074be26[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@1b0641ff[sequenceNumber=1, fileID=fileID1496928710026, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=OTHER, actionDateTime=2017-06-08T15:31:50.026+02: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@15a242e2[correlationID=af65c305-b9c0-475f-843b-30eb4a61d639, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSpecificRequests-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSpecificRequests, to=Pillar-checksumPillarGetAuditTrailsSpecificRequests, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@413728ef[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to extract the requested audit trails.], contributor=Pillar-checksumPillarGetAuditTrailsSpecificRequests, resultAddress=<null>(default)]
          Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsFinalResponse@44b73b61[correlationID=af65c305-b9c0-475f-843b-30eb4a61d639, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSpecificRequests-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSpecificRequests, to=Pillar-checksumPillarGetAuditTrailsSpecificRequests, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@6d1793b1[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], contributor=Pillar-checksumPillarGetAuditTrailsSpecificRequests, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@6a2579a3[resultAddress=<null>(default), auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@122d4458[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@1b0641ff[sequenceNumber=1, fileID=fileID1496928710026, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=OTHER, actionDateTime=2017-06-08T15:31:50.026+02:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@6f3c094f[sequenceNumber=2, fileID=notThisFile, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=UnknownActor, actionOnFile=FAILURE, actionDateTime=2017-06-08T15:31:50.026+02: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@11d7d941[correlationID=862aa7bc-ac48-46ee-9880-a466d35d4e11, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSuccessful-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSuccessful-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSuccessful, to=Pillar-checksumPillarGetAuditTrailsSuccessful, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@a891214[responseCode=IDENTIFICATION_POSITIVE, responseText=<null>(default)]]
        Step: Make and send the request for the actual GetAuditTrails operation
          Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSuccessful-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsProgressResponse@4f3ea60d[correlationID=862aa7bc-ac48-46ee-9880-a466d35d4e11, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSuccessful-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSuccessful-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSuccessful, to=Pillar-checksumPillarGetAuditTrailsSuccessful, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@191063f0[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to extract the requested audit trails.], contributor=Pillar-checksumPillarGetAuditTrailsSuccessful, resultAddress=<null>(default)]
          Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSuccessful-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsFinalResponse@36a2bc42[correlationID=862aa7bc-ac48-46ee-9880-a466d35d4e11, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSuccessful-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSuccessful-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSuccessful, to=Pillar-checksumPillarGetAuditTrailsSuccessful, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@74791130[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], contributor=Pillar-checksumPillarGetAuditTrailsSuccessful, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@4e4dcf7c[resultAddress=<null>(default), auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@54583aa6[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@773bccc3[sequenceNumber=1, fileID=fileid, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=actor, actionOnFile=OTHER, actionDateTime=2017-06-08T15:31:50.374+02: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 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@26c1f174[correlationID=80614171-62ba-4515-8427-919d637b06dc, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseIdentification-cibuild01-contributor, from=Pillar-badCaseIdentification, to=badCaseIdentification, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@11d264c2[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@1d12d735[fileID=DefaultFilebadCaseIdentification, allFileIDs=<null>(default)], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@71577b6b[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], pillarID=Pillar-badCaseIdentification, pillarChecksumSpec=<null>(default), timeToDeliver=<null>(default)]
        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.
15:31:52.133 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@62e6f2db[correlationID=a06607c8-a366-45ad-b7ad-0e1d6715bd91, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@7ae2d92[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@51cbe7a9[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultingChecksums=<null>(default), partialResult=<null>(default)]
        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@64c8afbe[correlationID=7696d1c1-8836-4424-9bb5-6e86774b0b79, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseIdentification-cibuild01-contributor, from=Pillar-goodCaseIdentification, to=goodCaseIdentification, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@597d339e[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@122a62a1[fileID=DefaultFilegoodCaseIdentification, allFileIDs=<null>(default)], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@49be20c2[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], pillarID=Pillar-goodCaseIdentification, pillarChecksumSpec=<null>(default), timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@682ad314[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@41e8b043[correlationID=4f3e4813-fc01-479e-8158-f9da3c96e50d, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationAllFiles-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationAllFiles-cibuild01-contributor, from=Pillar-goodCaseOperationAllFiles, to=goodCaseOperationAllFiles, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@3f08b915[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to calculate checksums.], pillarID=Pillar-goodCaseOperationAllFiles, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@2aae170c[fileID=<null>(default), allFileIDs=true], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@316eb9b8[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultAddress=<null>(default)]
          Result: Received message on TEST-TOPIC-goodCaseOperationAllFiles-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@66a7e65[correlationID=4f3e4813-fc01-479e-8158-f9da3c96e50d, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationAllFiles-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationAllFiles-cibuild01-contributor, from=Pillar-goodCaseOperationAllFiles, to=goodCaseOperationAllFiles, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@6a89d89b[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], pillarID=Pillar-goodCaseOperationAllFiles, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@316eb9b8[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultingChecksums=org.bitrepository.bitrepositoryelements.ResultingChecksums@3af207fc[resultAddress=<null>(default), checksumDataItems={org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@64918740[fileID=DefaultFile, checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2017-06-08T15:31:54.769+02:00],org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@31dd54e1[fileID=goodCaseOperationAllFiles-cibuild01--Test-File-1496928714753, 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@6ffb07a4[correlationID=b46f1341-a780-43de-bc6e-62572a5e6f77, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationSingleFile-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationSingleFile-cibuild01-contributor, from=Pillar-goodCaseOperationSingleFile, to=goodCaseOperationSingleFile, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@925fa0a[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to calculate checksums.], pillarID=Pillar-goodCaseOperationSingleFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@786d9f87[fileID=DefaultFilegoodCaseOperationSingleFile, allFileIDs=<null>(default)], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6360a442[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultAddress=<null>(default)]
          Result: Received message on TEST-TOPIC-goodCaseOperationSingleFile-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@549159ad[correlationID=b46f1341-a780-43de-bc6e-62572a5e6f77, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationSingleFile-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationSingleFile-cibuild01-contributor, from=Pillar-goodCaseOperationSingleFile, to=goodCaseOperationSingleFile, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@72c21c9f[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], pillarID=Pillar-goodCaseOperationSingleFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6360a442[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultingChecksums=org.bitrepository.bitrepositoryelements.ResultingChecksums@664724e7[resultAddress=<null>(default), checksumDataItems={org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@e3ded9[fileID=DefaultFilegoodCaseOperationSingleFile, checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2017-06-08T15:31:55.081+02: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@76ed86db[correlationID=079b3731-031a-4f9f-8221-0fdadae35092, collectionID=TwoPillarCollection, destination=TEST-TOPIC-testRestrictions-cibuild01, replyTo=TEST-TOPIC-Pillar-testRestrictions-cibuild01-contributor, from=Pillar-testRestrictions, to=testRestrictions, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@23ceb383[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to calculate checksums.], pillarID=Pillar-testRestrictions, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@1ae22dcb[fileID=<null>(default), allFileIDs=true], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@54dfde5b[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultAddress=<null>(default)]
          Result: Received message on TEST-TOPIC-testRestrictions-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@4e9e4145[correlationID=079b3731-031a-4f9f-8221-0fdadae35092, collectionID=TwoPillarCollection, destination=TEST-TOPIC-testRestrictions-cibuild01, replyTo=TEST-TOPIC-Pillar-testRestrictions-cibuild01-contributor, from=Pillar-testRestrictions, to=testRestrictions, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@189ab1be[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], pillarID=Pillar-testRestrictions, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@54dfde5b[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultingChecksums=org.bitrepository.bitrepositoryelements.ResultingChecksums@131d4b13[resultAddress=<null>(default), checksumDataItems={org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@391a622d[fileID=DefaultFile, checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2017-06-08T15:31:55.379+02:00]}], partialResult=false]
        Step: Retrieve the ProgressResponse for the GetChecksums request
        Step: Retrieve the FinalResponse for the GetChecksums request
      Test success: testRestrictions
    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
      Test starting: getPillarCollectionsTest
      Test success: getPillarCollectionsTest
    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: testArchiveDirectoryExistingFolderFile
        Description: Test the ArchiveDirectory when the file exists
        Step: Setup
        Step: Validate the existence of the file
        Step: Delete the file.
      Test success: testArchiveDirectoryExistingFolderFile
      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: testArchiveDirectoryMissingFolderFile
        Description: Test the ArchiveDirectory when the file is missing.
        Step: Setup
        Step: Validate the existence of the file
        Step: Delete the file.
      Test success: testArchiveDirectoryMissingFolderFile
      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: testArchiveDirectoryMoveFolderFileToArchive
        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: testArchiveDirectoryMoveFolderFileToArchive
      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: testArchiveDirectoryNewFolderFile
        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: testArchiveDirectoryNewFolderFile
      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
      Test starting: testArchiveDirectoryRemoveFolderFile
        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: testArchiveDirectoryRemoveFolderFile
    Starting testcase ChecksumDatabaseMigrationTest
      Test starting: testMigratingChecksumDatabaseFromV3ToV4
        Description: Tests that the checksums table can be migrated from version 3 to 4, e.g. changing the column calculatedchecksumdate from timestamp to bigint.
        Step: Ensure cleanup
15:31:55.967 WARN  o.b.common.utils.FileUtils - Could not delete '/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/test/referencepillar/checksumdb-for-migration'
        Step: Unzipping and connecting to checksum database version 3
        Step: Validate setup
        Step: Ingest a entry to the database with a date for the calculationdate
        Step: Perform migration
15:31:56.834 WARN  o.b.service.database.DatabaseUtils - Migrating ChecksumDB from version 3 to 4.
        Step: Validate the migration
      Test success: testMigratingChecksumDatabaseFromV3ToV4
    Starting testcase ChecksumEntryTest
      Test starting: testExtendedTestCase
        Description: Test the ChecksumEntry
        Step: Create a ChecksumEntry
      Test success: testExtendedTestCase
    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@7d474824[correlationID=25d7bc0e-5b2b-4c13-85d0-2964c07e5174, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseIdentification-cibuild01-contributor, from=Pillar-badCaseIdentification, to=badCaseIdentification, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@516acd72[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], fileID=DefaultFilebadCaseIdentification, pillarID=Pillar-badCaseIdentification, pillarChecksumSpec=<null>(default), timeToDeliver=<null>(default)]
        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@5fb927a2[correlationID=8dc60491-ac4b-42d6-9d0b-a464caeb64b9, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationMissingVerification-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationMissingVerification-cibuild01-contributor, from=Pillar-badCaseOperationMissingVerification, to=badCaseOperationMissingVerification, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@e425d41[responseCode=EXISTING_FILE_CHECKSUM_FAILURE, responseText=No mandatory checksum for destructive operation was supplied.], pillarID=Pillar-badCaseOperationMissingVerification, fileID=DefaultFilebadCaseOperationMissingVerification, checksumDataForExistingFile=<null>(default)]
15:31:58.777 WARN  o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@253e291e[origDateTime=2017-06-08T15:31:58.777+02: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@332c8e2c[correlationID=1b0a7b40-5975-4515-8ce5-c895b0f39884, collectionID=TwoPillarCollection, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationMissingVerification-cibuild01-contributor, from=Pillar-badCaseOperationMissingVerification, to=<null>(default), version=30, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@253e291e[origDateTime=2017-06-08T15:31:58.777+02: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@60d501f6[correlationID=034983c5-bc38-4158-bda6-1d8cf3ae0d02, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@7f500542[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileID=DefaultFilebadCaseOperationNoFile, checksumDataForExistingFile=<null>(default)]
          Result: Received message on TEST-TOPIC-badCaseOperationNoFile-cibuild01 : org.bitrepository.bitrepositorymessages.DeleteFileFinalResponse@3e476882[correlationID=034983c5-bc38-4158-bda6-1d8cf3ae0d02, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@76d5040d[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileID=DefaultFilebadCaseOperationNoFile, checksumDataForExistingFile=<null>(default)]
        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@3e476882[correlationID=034983c5-bc38-4158-bda6-1d8cf3ae0d02, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@76d5040d[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileID=DefaultFilebadCaseOperationNoFile, checksumDataForExistingFile=<null>(default)]
15:32:00.057 WARN  o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: 
org.bitrepository.bitrepositorymessages.DeleteFileFinalResponse@3e476882[correlationID=034983c5-bc38-4158-bda6-1d8cf3ae0d02, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@76d5040d[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileID=DefaultFilebadCaseOperationNoFile, checksumDataForExistingFile=<null>(default)]
        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@20f76b7a[correlationID=01c0fb88-7928-442b-88f4-85266ddeeb35, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseIdentification-cibuild01-contributor, from=Pillar-goodCaseIdentification, to=goodCaseIdentification, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@10b34165[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], fileID=DefaultFilegoodCaseIdentification, pillarID=Pillar-goodCaseIdentification, pillarChecksumSpec=<null>(default), timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@c8080e6[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.
15:32:02.626 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)
	at org.bitrepository.pillar.MediatorTest$ErroneousRequestHandler.processRequest(MediatorTest.java:113)
	at org.bitrepository.pillar.messagehandler.PillarMediator.handleRequest(PillarMediator.java:80)
	at org.bitrepository.service.contributor.AbstractContributorMediator$GeneralRequestHandler.onMessage(AbstractContributorMediator.java:101)
	at org.bitrepository.protocol.messagebus.SimpleMessageBus.lambda$sendMessage$0(SimpleMessageBus.java:73)
	at java.lang.Iterable.forEach(Iterable.java:75)
	at org.bitrepository.protocol.messagebus.SimpleMessageBus.sendMessage(SimpleMessageBus.java:73)
	at org.bitrepository.pillar.MediatorTest.testMediatorRuntimeExceptionHandling(MediatorTest.java:84)
	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:498)
	at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:86)
	at org.testng.internal.Invoker.invokeMethod(Invoker.java:643)
	at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:820)
	at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1128)
	at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:129)
	at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:112)
	at org.testng.TestRunner.privateRun(TestRunner.java:782)
	at org.testng.TestRunner.run(TestRunner.java:632)
	at org.testng.SuiteRunner.runTest(SuiteRunner.java:366)
	at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:361)
	at org.testng.SuiteRunner.privateRun(SuiteRunner.java:319)
	at org.testng.SuiteRunner.run(SuiteRunner.java:268)
	at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
	at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
	at org.testng.TestNG.runSuitesSequentially(TestNG.java:1244)
	at org.testng.TestNG.runSuitesLocally(TestNG.java:1169)
	at org.testng.TestNG.run(TestNG.java:1064)
	at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:115)
	at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:204)
	at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:107)
	at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:112)
	at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
          Result: Received message on TEST-TOPIC-testMediatorRuntimeExceptionHandling-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetStatusResponse@5570d921[correlationID=7ee552d8-e4e3-4e51-9e90-be7db4c266d2, collectionID=TwoPillarCollection, destination=TEST-TOPIC-testMediatorRuntimeExceptionHandling-cibuild01, replyTo=TEST-TOPIC-MediatorUnderTest-cibuild01-contributor, from=MediatorUnderTest, to=MediatorUnderTest, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@45ebde80[responseCode=FAILURE, responseText=java.lang.RuntimeException: I am supposed to throw a RuntimeException], contributor=TEST-TOPIC-cibuild01, timeToDeliver=<null>(default)]
15:32:02.630 WARN  o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@21ea8719[origDateTime=2017-06-08T15:32:02.630+02:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MediatorUnderTest, alarmText=java.lang.RuntimeException: I am supposed to throw a RuntimeException, fileID=<null>(default), collectionID=<null>(default)]
          Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@7280fbd4[correlationID=6a3566d7-5872-4001-98b0-ee127a2dff11, collectionID=<null>(default), destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-MediatorUnderTest-cibuild01-contributor, from=MediatorUnderTest, to=<null>(default), version=30, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@21ea8719[origDateTime=2017-06-08T15:32:02.630+02:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MediatorUnderTest, alarmText=java.lang.RuntimeException: I am supposed to throw a RuntimeException, fileID=<null>(default), collectionID=<null>(default)]]
      Test success: testMediatorRuntimeExceptionHandling
    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@4acd47cf[correlationID=8ab67841-2192-4f01-8865-0218d76894ae, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseIdentification-cibuild01-contributor, from=Pillar-badCaseIdentification, to=badCaseIdentification, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@1f7d202[responseCode=DUPLICATE_FILE_FAILURE, responseText=<null>(default)], pillarID=Pillar-badCaseIdentification, fileID=DefaultFilebadCaseIdentification, pillarChecksumSpec=<null>(default), checksumDataForExistingFile=<null>(default), timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@1a293bbf[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@117ea0cf[correlationID=c163fb4e-e0d6-4741-baeb-cd16be1b271a, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationFileAlreadyExists-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationFileAlreadyExists-cibuild01-contributor, from=Pillar-badCaseOperationFileAlreadyExists, to=badCaseOperationFileAlreadyExists, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@57dbd55d[responseCode=DUPLICATE_FILE_FAILURE, responseText=We already have the file], pillarID=Pillar-badCaseOperationFileAlreadyExists, pillarChecksumSpec=<null>(default), fileID=DefaultFilebadCaseOperationFileAlreadyExists, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForNewFile=<null>(default), checksumDataForExistingFile=<null>(default)]
        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@3983d505[correlationID=5da09e2e-3a03-4a2f-9b01-6ef1b02ab291, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCasePutOperationNoValidationChecksum-cibuild01, replyTo=TEST-TOPIC-Pillar-badCasePutOperationNoValidationChecksum-cibuild01-contributor, from=Pillar-badCasePutOperationNoValidationChecksum, to=badCasePutOperationNoValidationChecksum, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@2fc2bb2f[responseCode=NEW_FILE_CHECKSUM_FAILURE, responseText=A checksum is required for the PutFile operation to be performed.], pillarID=Pillar-badCasePutOperationNoValidationChecksum, pillarChecksumSpec=<null>(default), fileID=DefaultFilebadCasePutOperationNoValidationChecksum, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForNewFile=<null>(default), checksumDataForExistingFile=<null>(default)]
15:32:05.449 WARN  o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@22d0b2d0[origDateTime=2017-06-08T15:32:05.448+02: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@3d697f[correlationID=c11bf618-ff99-43f8-947c-b5bda94cef0d, collectionID=TwoPillarCollection, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-Pillar-badCasePutOperationNoValidationChecksum-cibuild01-contributor, from=Pillar-badCasePutOperationNoValidationChecksum, to=<null>(default), version=30, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@22d0b2d0[origDateTime=2017-06-08T15:32:05.448+02: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@47de972[correlationID=690db761-49a5-4446-890c-469577f1c4dc, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseIdentification-cibuild01-contributor, from=Pillar-goodCaseIdentification, to=goodCaseIdentification, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@4275f7b2[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], pillarID=Pillar-goodCaseIdentification, fileID=DefaultFilegoodCaseIdentification, pillarChecksumSpec=<null>(default), checksumDataForExistingFile=<null>(default), timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@4c0c0193[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@5c14f240[correlationID=1f160ae7-ca8a-4fc1-b81f-0fb258504db7, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationWithChecksumReturn-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationWithChecksumReturn-cibuild01-contributor, from=Pillar-goodCaseOperationWithChecksumReturn, to=goodCaseOperationWithChecksumReturn, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@67264fde[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Started to receive data.], pillarID=Pillar-goodCaseOperationWithChecksumReturn, pillarChecksumSpec=<null>(default), 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@15ab7999[correlationID=1f160ae7-ca8a-4fc1-b81f-0fb258504db7, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationWithChecksumReturn-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationWithChecksumReturn-cibuild01-contributor, from=Pillar-goodCaseOperationWithChecksumReturn, to=goodCaseOperationWithChecksumReturn, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@6ed61f9e[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], pillarID=Pillar-goodCaseOperationWithChecksumReturn, pillarChecksumSpec=<null>(default), fileID=DefaultFilegoodCaseOperationWithChecksumReturn, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForNewFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@3bdbf525[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@54d8147d[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2017-06-08T15:32:07.044+02:00], checksumDataForExistingFile=<null>(default)]
        Step: Retrieve the ProgressResponse for the GetFileIDs request
        Step: Retrieve the FinalResponse for the PutFile request
      Test success: goodCaseOperationWithChecksumReturn
    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@f854303[correlationID=9b43bf3b-d9d2-42ac-bf4e-9a22cda56694, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseIdentification-cibuild01-contributor, from=Pillar-badCaseIdentification, to=badCaseIdentification, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@6f9be28e[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], fileID=DefaultFilebadCaseIdentification, pillarID=Pillar-badCaseIdentification, timeToDeliver=<null>(default)]
        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@57ee4fe7[correlationID=cdd70f40-af52-42db-993f-01c216f3e309, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseIdentification-cibuild01-contributor, from=Pillar-goodCaseIdentification, to=goodCaseIdentification, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@5fcf0a35[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], fileID=DefaultFilegoodCaseIdentification, pillarID=Pillar-goodCaseIdentification, timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@1d708904[timeMeasureUnit=MILLISECONDS, timeMeasureValue=1000]]
        Step: Retrieve and validate the response getPillarID() the pillar.
      Test success: goodCaseIdentification
      Test starting: componentIDTest
      Test success: componentIDTest
    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@925b315[correlationID=b6ff2641-5be2-475e-9185-86730f4f0486, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseIdentification-cibuild01-contributor, from=Pillar-badCaseIdentification, to=badCaseIdentification, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@69461c7f[responseCode=FILE_NOT_FOUND_FAILURE, responseText=Could not find the requested file to delete.], fileID=DefaultFile, pillarID=Pillar-badCaseIdentification, pillarChecksumSpec=<null>(default), timeToDeliver=<null>(default)]
        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@f579909[correlationID=3a85f080-6b4a-4683-8ed5-c89ff51e6ad2, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationMissingFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationMissingFile-cibuild01-contributor, from=Pillar-badCaseOperationMissingFile, to=badCaseOperationMissingFile, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@2f24dcc8[responseCode=FILE_NOT_FOUND_FAILURE, responseText=The file 'DefaultFile' has been requested, but we do not have that file!], pillarID=Pillar-badCaseOperationMissingFile, pillarChecksumSpec=<null>(default), fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForExistingFile=<null>(default), checksumDataForNewFile=<null>(default)]
        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@275c1aed[correlationID=a8baa84d-25b2-42b9-b376-ccf155f4ef23, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoDestructiveChecksum-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoDestructiveChecksum-cibuild01-contributor, from=Pillar-badCaseOperationNoDestructiveChecksum, to=badCaseOperationNoDestructiveChecksum, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@4e3617fe[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=<null>(default), fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForExistingFile=<null>(default), checksumDataForNewFile=<null>(default)]
15:32:13.548 WARN  o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@51ffdbc9[origDateTime=2017-06-08T15:32:13.544+02: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@4ab50d80[correlationID=ce0134fc-02db-4da7-816a-9e309f591d55, collectionID=TwoPillarCollection, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoDestructiveChecksum-cibuild01-contributor, from=Pillar-badCaseOperationNoDestructiveChecksum, to=<null>(default), version=30, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@51ffdbc9[origDateTime=2017-06-08T15:32:13.544+02: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@49035687[correlationID=be9d6e8a-0b82-4c02-b752-b9a67430e14f, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoValidationChecksum-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoValidationChecksum-cibuild01-contributor, from=Pillar-badCaseOperationNoValidationChecksum, to=badCaseOperationNoValidationChecksum, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@36987af5[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=<null>(default), fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForExistingFile=<null>(default), checksumDataForNewFile=<null>(default)]
15:32:13.810 WARN  o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@35422a67[origDateTime=2017-06-08T15:32:13.810+02: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@274b79b7[correlationID=2e2aee0c-4e19-4c19-b416-92a402178b21, collectionID=TwoPillarCollection, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoValidationChecksum-cibuild01-contributor, from=Pillar-badCaseOperationNoValidationChecksum, to=<null>(default), version=30, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@35422a67[origDateTime=2017-06-08T15:32:13.810+02: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.
15:32:14.050 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@2794e6d3[correlationID=a522d50a-ee08-4c17-b8db-56af334c943d, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationWrongDestructiveChecksum-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationWrongDestructiveChecksum-cibuild01-contributor, from=Pillar-badCaseOperationWrongDestructiveChecksum, to=badCaseOperationWrongDestructiveChecksum, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@1a787140[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=<null>(default), fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForExistingFile=<null>(default), checksumDataForNewFile=<null>(default)]
15:32:14.056 WARN  o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@1556ae16[origDateTime=2017-06-08T15:32:14.055+02: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@6a093719[correlationID=537a0801-7071-40ee-b997-bce53cf4e234, collectionID=TwoPillarCollection, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationWrongDestructiveChecksum-cibuild01-contributor, from=Pillar-badCaseOperationWrongDestructiveChecksum, to=<null>(default), version=30, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@1556ae16[origDateTime=2017-06-08T15:32:14.055+02: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@3931325f[correlationID=1a582a8b-1e93-4e63-bd2d-7cf153f3ba71, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseIdentification-cibuild01-contributor, from=Pillar-goodCaseIdentification, to=goodCaseIdentification, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@4eb7f0bb[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], fileID=DefaultFile, pillarID=Pillar-goodCaseIdentification, pillarChecksumSpec=<null>(default), timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@5b1b01e6[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@669638a1[correlationID=62372764-d039-4ed0-9225-d614720034fd, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperation-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperation-cibuild01-contributor, from=Pillar-goodCaseOperation, to=goodCaseOperation, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@193117ce[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Performing the ReplaceFileRequest for file 'DefaultFile' at 'TwoPillarCollection'.], pillarID=Pillar-goodCaseOperation, pillarChecksumSpec=<null>(default), 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@6f686c93[correlationID=62372764-d039-4ed0-9225-d614720034fd, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperation-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperation-cibuild01-contributor, from=Pillar-goodCaseOperation, to=goodCaseOperation, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@38ec12ef[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], pillarID=Pillar-goodCaseOperation, pillarChecksumSpec=<null>(default), fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForExistingFile=<null>(default), checksumDataForNewFile=<null>(default)]
        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@a504fd2[correlationID=c1bce431-bde3-49d9-8f7f-0f7563971ca7, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationWithChecksumsReturn-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationWithChecksumsReturn-cibuild01-contributor, from=Pillar-goodCaseOperationWithChecksumsReturn, to=goodCaseOperationWithChecksumsReturn, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@6897dc22[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Performing the ReplaceFileRequest for file 'DefaultFile' at 'TwoPillarCollection'.], pillarID=Pillar-goodCaseOperationWithChecksumsReturn, pillarChecksumSpec=<null>(default), 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@51b40d47[correlationID=c1bce431-bde3-49d9-8f7f-0f7563971ca7, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationWithChecksumsReturn-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationWithChecksumsReturn-cibuild01-contributor, from=Pillar-goodCaseOperationWithChecksumsReturn, to=goodCaseOperationWithChecksumsReturn, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@462709b9[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], pillarID=Pillar-goodCaseOperationWithChecksumsReturn, pillarChecksumSpec=<null>(default), fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@4e01e070[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@18a1435e[checksumType=HMAC_SHA512, checksumSalt={97,98}, otherChecksumType=<null>(default)], checksumValue={18,52,-52,-52,-52,-52,67,34}, calculationTimestamp=2017-06-08T15:32:16.785+02:00], checksumDataForNewFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@690eab38[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@179a0d61[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2017-06-08T15:32:16.786+02:00]]
        Step: Retrieve the ProgressResponse for the GetFileIDs request
        Step: Retrieve the FinalResponse for the ReplaceFile request
      Test success: goodCaseOperationWithChecksumsReturn
    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
        Added fixture: Initialize a new Pillar.
      Test starting: testPillarMessageHandlerValidateFileIDFormatDefaultFileId
        Description: Test the validation of file id formats of the PillarMessageHandler super-class on the default file id
      Test success: testPillarMessageHandlerValidateFileIDFormatDefaultFileId
        Added fixture: Initialize a new Pillar.
      Test starting: testPillarMessageHandlerValidateFileIDFormatEnvHomePathFileId
        Description: Test the validation of file id formats of the PillarMessageHandler super-class on a file id containing path relative paths from the environment variable home folder
      Test success: testPillarMessageHandlerValidateFileIDFormatEnvHomePathFileId
        Added fixture: Initialize a new Pillar.
      Test starting: testPillarMessageHandlerValidateFileIDFormatFolderFileId
        Description: Test the validation of file id formats of the PillarMessageHandler super-class on a file id with directory path
      Test success: testPillarMessageHandlerValidateFileIDFormatFolderFileId
        Added fixture: Initialize a new Pillar.
      Test starting: testPillarMessageHandlerValidateFileIDFormatParentFolderFileId
        Description: Test the validation of file id formats of the PillarMessageHandler super-class on a file id containing path to a parent directory
      Test success: testPillarMessageHandlerValidateFileIDFormatParentFolderFileId
        Added fixture: Initialize a new Pillar.
      Test starting: testPillarMessageHandlerValidateFileIDFormatRootPathFileId
        Description: Test the validation of file id formats of the PillarMessageHandler super-class on a file id containing path from the root folder
      Test success: testPillarMessageHandlerValidateFileIDFormatRootPathFileId
        Added fixture: Initialize a new Pillar.
      Test starting: testPillarMessageHandlerValidateFileIDFormatSubFolderToParentFolderFileId
        Description: Test the validation of file id formats of the PillarMessageHandler super-class on a file id containing path to a parent directory, but starting with a sub-folder
      Test success: testPillarMessageHandlerValidateFileIDFormatSubFolderToParentFolderFileId
        Added fixture: Initialize a new Pillar.
      Test starting: testPillarMessageHandlerValidateFileIDFormatTildeHomePathFileId
        Description: Test the validation of file id formats of the PillarMessageHandler super-class on a file id containing path relative paths from the tilde home folder
      Test success: testPillarMessageHandlerValidateFileIDFormatTildeHomePathFileId
        Added fixture: Initialize a new Pillar.
      Test starting: testPillarMessageHandlerValidateFileIDFormatTooLong
        Description: Test the validation of file id formats of the PillarMessageHandler super-class on a file id which has more characters than required
      Test success: testPillarMessageHandlerValidateFileIDFormatTooLong
    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.
15:32:19.928 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@25817b65[correlationID=8a8dfa1f-0cb5-4635-84fc-b2118ee52215, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseIdentification-cibuild01-contributor, from=Pillar-badCaseIdentification, to=badCaseIdentification, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@700af8ff[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseIdentification, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@4c86efff[fileID=DefaultFilebadCaseIdentification, allFileIDs=<null>(default)], timeToDeliver=<null>(default)]
        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.
15:32:21.157 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@1f29cc72[correlationID=66bc55e3-35cd-4148-b530-3859b1cee2bf, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@208d03da[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@4db96fd[fileID=DefaultFilebadCaseOperationNoFile, allFileIDs=<null>(default)], resultingFileIDs=<null>(default), partialResult=<null>(default)]
15:32:21.166 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@1fa3dd3[correlationID=66bc55e3-35cd-4148-b530-3859b1cee2bf, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@49a16de5[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@4db96fd[fileID=DefaultFilebadCaseOperationNoFile, allFileIDs=<null>(default)], resultingFileIDs=<null>(default), partialResult=<null>(default)]
15:32:21.169 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@31710a8b[correlationID=66bc55e3-35cd-4148-b530-3859b1cee2bf, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@6135bdd3[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@4db96fd[fileID=DefaultFilebadCaseOperationNoFile, allFileIDs=<null>(default)], resultingFileIDs=<null>(default), partialResult=<null>(default)]
        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@1fa3dd3[correlationID=66bc55e3-35cd-4148-b530-3859b1cee2bf, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@49a16de5[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@4db96fd[fileID=DefaultFilebadCaseOperationNoFile, allFileIDs=<null>(default)], resultingFileIDs=<null>(default), partialResult=<null>(default)]
org.bitrepository.bitrepositorymessages.GetFileIDsFinalResponse@31710a8b[correlationID=66bc55e3-35cd-4148-b530-3859b1cee2bf, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@6135bdd3[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@4db96fd[fileID=DefaultFilebadCaseOperationNoFile, allFileIDs=<null>(default)], resultingFileIDs=<null>(default), partialResult=<null>(default)]
15:32:22.176 WARN  o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: 
org.bitrepository.bitrepositorymessages.GetFileIDsFinalResponse@1fa3dd3[correlationID=66bc55e3-35cd-4148-b530-3859b1cee2bf, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@49a16de5[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@4db96fd[fileID=DefaultFilebadCaseOperationNoFile, allFileIDs=<null>(default)], resultingFileIDs=<null>(default), partialResult=<null>(default)]
org.bitrepository.bitrepositorymessages.GetFileIDsFinalResponse@31710a8b[correlationID=66bc55e3-35cd-4148-b530-3859b1cee2bf, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@6135bdd3[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@4db96fd[fileID=DefaultFilebadCaseOperationNoFile, allFileIDs=<null>(default)], resultingFileIDs=<null>(default), partialResult=<null>(default)]
        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@39f202da[correlationID=d5c2f5c1-5595-4eaf-aded-cc1ca8980789, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseIdentification-cibuild01-contributor, from=Pillar-goodCaseIdentification, to=goodCaseIdentification, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@2716700e[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], pillarID=Pillar-goodCaseIdentification, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@5cd84f23[fileID=DefaultFilegoodCaseIdentification, allFileIDs=<null>(default)], timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@650a150c[timeMeasureUnit=MILLISECONDS, timeMeasureValue=1000]]
        Step: Retrieve and validate the response getPillarID() the pillar.
      Test success: goodCaseIdentification
    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
      Finished testcase
  Finished suite
Finished project
Tests run: 72, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 64.556 sec - in TestSuite

Results :

Tests run: 72, Failures: 0, Errors: 0, Skipped: 0

[JENKINS] Recording test results
[INFO] 
[INFO] --- jacoco-maven-plugin:0.7.5.201505241946:report (report) @ bitrepository-reference-pillar ---
[INFO] Analyzed bundle 'Bitrepository Reference Pillar' with 43 classes
[INFO] 
[INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ bitrepository-reference-pillar ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.10-SNAPSHOT.jar
[INFO] 
[INFO] --- maven-jar-plugin:2.4:test-jar (default) @ bitrepository-reference-pillar ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.10-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-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.10-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] Downloading: https://sbforge.org/nexus/content/groups/public/org/bitrepository/reference/bitrepository-client/1.10-SNAPSHOT/bitrepository-client-1.10-20170608.132800-5.pom
[INFO] Downloaded: https://sbforge.org/nexus/content/groups/public/org/bitrepository/reference/bitrepository-client/1.10-SNAPSHOT/bitrepository-client-1.10-20170608.132800-5.pom (2 KB at 21.9 KB/sec)
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.10-SNAPSHOT-distribution.tar.gz
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.10-SNAPSHOT-acceptance-test.tar.gz
[WARNING] Entry: bitrepository-reference-pillar-1.10-SNAPSHOT/lib/bitrepository-reference-pillar-1.10-SNAPSHOT-tests.jar longer than 100 characters.
[WARNING] Resulting tar file can only be processed successfully by GNU compatible tar commands
[WARNING] Entry: bitrepository-reference-pillar-1.10-SNAPSHOT/lib/bitrepository-core-1.10-20170608.132644-5-tests.jar longer than 100 characters.
[WARNING] Entry: bitrepository-reference-pillar-1.10-SNAPSHOT/lib/bitrepository-client-1.10-20170608.132800-5-tests.jar longer than 100 characters.
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.10-SNAPSHOT-deploy.tar.gz
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.10-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-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.10-SNAPSHOT.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-SNAPSHOT.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.10-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.10-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-SNAPSHOT-sources.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.10-SNAPSHOT-distribution.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-SNAPSHOT-distribution.tar.gz
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.10-SNAPSHOT-acceptance-test.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-SNAPSHOT-acceptance-test.tar.gz
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.10-SNAPSHOT-deploy.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-SNAPSHOT-deploy.tar.gz
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.10-SNAPSHOT-acceptance-test-deploy.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-SNAPSHOT-acceptance-test-deploy.tar.gz
[INFO] 
[INFO] --- maven-deploy-plugin:2.8.1:deploy (default-deploy) @ bitrepository-reference-pillar ---
[INFO] Downloading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/maven-metadata.xml (3 KB at 26.9 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20170608.133230-5.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20170608.133230-5.jar (128 KB at 2124.0 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20170608.133230-5.pom
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20170608.133230-5.pom (8 KB at 165.5 KB/sec)
[INFO] Downloading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/maven-metadata.xml (457 B at 18.6 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/maven-metadata.xml (3 KB at 60.9 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/maven-metadata.xml (457 B at 16.5 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20170608.133230-5-tests.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20170608.133230-5-tests.jar (238 KB at 4326.6 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/maven-metadata.xml (3 KB at 62.7 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20170608.133230-5-sources.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20170608.133230-5-sources.jar (104 KB at 2525.6 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/maven-metadata.xml (3 KB at 86.2 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20170608.133230-5-distribution.tar.gz
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20170608.133230-5-distribution.tar.gz (13315 KB at 16938.9 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/maven-metadata.xml (3 KB at 62.7 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20170608.133230-5-acceptance-test.tar.gz
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20170608.133230-5-acceptance-test.tar.gz (12950 KB at 20819.7 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/maven-metadata.xml (3 KB at 71.4 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20170608.133230-5-deploy.tar.gz
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20170608.133230-5-deploy.tar.gz (4 KB at 76.5 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/maven-metadata.xml (3 KB at 59.1 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20170608.133230-5-acceptance-test-deploy.tar.gz
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20170608.133230-5-acceptance-test-deploy.tar.gz (4 KB at 89.1 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/maven-metadata.xml (3 KB at 71.4 KB/sec)
[JENKINS] Archiving disabled
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Monitoring Service 1.10-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-monitoring-service ---
[INFO] Deleting /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/target
[INFO] 
[INFO] --- jacoco-maven-plugin:0.7.5.201505241946:prepare-agent (default) @ bitrepository-monitoring-service ---
[INFO] argLine set to -javaagent:/home/cibuild01/.m2/repository/org/jacoco/org.jacoco.agent/0.7.5.201505241946/org.jacoco.agent-0.7.5.201505241946-runtime.jar=destfile=/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/target/jacoco.exec
[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-reference-test/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-reference-test/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-reference-test/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-reference-test/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-reference-test/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 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
    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 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.
15:32:41.940 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 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.
15:32:44.495 WARN  o.b.m.a.BasicMonitoringServiceAlerter - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@5d6b42cf[origDateTime=2017-06-08T15:32:44.475+02:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MonitorAlerterUnderTest, alarmText=The following components have become unresponsive: [TestMonitorService], fileID=<null>(default), collectionID=<null>(default)]
          Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@5e541ef9[correlationID=3697ba9c-3274-45fe-9297-e228163d6095, collectionID=<null>(default), destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-MonitorAlerterUnderTest-cibuild01-contributor, from=MonitorAlerterUnderTest, to=<null>(default), version=30, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@5d6b42cf[origDateTime=2017-06-08T15:32:44.475+02:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MonitorAlerterUnderTest, alarmText=The following components have become unresponsive: [TestMonitorService], fileID=<null>(default), collectionID=<null>(default)]]
      Test success: testMonitorAlerter
      Finished testcase
  Finished suite
Finished project
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 9.393 sec - in TestSuite

Results :

Tests run: 4, Failures: 0, Errors: 0, Skipped: 0

[JENKINS] Recording test results
[INFO] 
[INFO] --- jacoco-maven-plugin:0.7.5.201505241946:report (report) @ bitrepository-monitoring-service ---
[INFO] Analyzed bundle 'Bitrepository Monitoring Service' with 14 classes
[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-reference-test/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.10-SNAPSHOT]
[INFO] Processing war project
[INFO] Copying webapp resources [/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/src/main/webapp]
[INFO] Webapp assembled in [142 msecs]
[INFO] Building war: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.10-SNAPSHOT.war
[INFO] 
[INFO] --- maven-jar-plugin:2.4:test-jar (default) @ bitrepository-monitoring-service ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.10-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-reference-test/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.10-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-reference-test/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.10-SNAPSHOT-distribution.tar.gz
[INFO] 
[INFO] --- maven-install-plugin:2.5.1:install (default-install) @ bitrepository-monitoring-service ---
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.10-SNAPSHOT.war to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/bitrepository-monitoring-service-1.10-SNAPSHOT.war
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/bitrepository-monitoring-service-1.10-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.10-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/bitrepository-monitoring-service-1.10-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.10-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/bitrepository-monitoring-service-1.10-SNAPSHOT-sources.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.10-SNAPSHOT-distribution.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/bitrepository-monitoring-service-1.10-SNAPSHOT-distribution.tar.gz
[INFO] 
[INFO] --- maven-deploy-plugin:2.8.1:deploy (default-deploy) @ bitrepository-monitoring-service ---
[INFO] Downloading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 24.9 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/bitrepository-monitoring-service-1.10-20170608.133249-5.war
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/bitrepository-monitoring-service-1.10-20170608.133249-5.war (18064 KB at 21326.3 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/bitrepository-monitoring-service-1.10-20170608.133249-5.pom
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/bitrepository-monitoring-service-1.10-20170608.133249-5.pom (4 KB at 110.3 KB/sec)
[INFO] Downloading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/maven-metadata.xml (459 B at 29.9 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 45.7 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/maven-metadata.xml (459 B at 14.5 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/bitrepository-monitoring-service-1.10-20170608.133249-5-tests.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/bitrepository-monitoring-service-1.10-20170608.133249-5-tests.jar (15 KB at 354.7 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 35.4 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/bitrepository-monitoring-service-1.10-20170608.133249-5-sources.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/bitrepository-monitoring-service-1.10-20170608.133249-5-sources.jar (19 KB at 406.9 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 52.5 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/bitrepository-monitoring-service-1.10-20170608.133249-5-distribution.tar.gz
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/bitrepository-monitoring-service-1.10-20170608.133249-5-distribution.tar.gz (18062 KB at 15843.1 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 44.3 KB/sec)
[JENKINS] Archiving disabled
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Webclient 1.10-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-webclient ---
[INFO] Deleting /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/target
[INFO] 
[INFO] --- jacoco-maven-plugin:0.7.5.201505241946:prepare-agent (default) @ bitrepository-webclient ---
[INFO] argLine set to -javaagent:/home/cibuild01/.m2/repository/org/jacoco/org.jacoco.agent/0.7.5.201505241946/org.jacoco.agent-0.7.5.201505241946-runtime.jar=destfile=/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/target/jacoco.exec
[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-reference-test/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-reference-test/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.
[INFO] 
[JENKINS] Recording test results[INFO] --- jacoco-maven-plugin:0.7.5.201505241946:report (report) @ bitrepository-webclient ---
[INFO] Skipping JaCoCo execution due to missing execution data file:/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/target/jacoco.exec

[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-reference-test/bitrepository-webclient/target/bitrepository-webclient-1.10-SNAPSHOT]
[INFO] Processing war project
[INFO] Copying webapp webResources [/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/src/main/webapp] to [/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/target/bitrepository-webclient-1.10-SNAPSHOT]
[INFO] Copying webapp resources [/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/src/main/webapp]
[INFO] Webapp assembled in [546 msecs]
[INFO] Building war: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/target/bitrepository-webclient-1.10-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-reference-test/bitrepository-webclient/target/bitrepository-webclient-1.10-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-reference-test/bitrepository-webclient/target/bitrepository-webclient-1.10-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-reference-test/bitrepository-webclient/target/bitrepository-webclient-1.10-SNAPSHOT-distribution.tar.gz
[INFO] 
[INFO] --- maven-install-plugin:2.5.1:install (default-install) @ bitrepository-webclient ---
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/target/bitrepository-webclient-1.10-SNAPSHOT.war to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/bitrepository-webclient-1.10-SNAPSHOT.war
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/bitrepository-webclient-1.10-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/target/bitrepository-webclient-1.10-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/bitrepository-webclient-1.10-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/target/bitrepository-webclient-1.10-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/bitrepository-webclient-1.10-SNAPSHOT-sources.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/target/bitrepository-webclient-1.10-SNAPSHOT-distribution.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/bitrepository-webclient-1.10-SNAPSHOT-distribution.tar.gz
[INFO] 
[INFO] --- maven-deploy-plugin:2.8.1:deploy (default-deploy) @ bitrepository-webclient ---
[INFO] Downloading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 18.5 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/bitrepository-webclient-1.10-20170608.133255-5.war
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/bitrepository-webclient-1.10-20170608.133255-5.war (12468 KB at 18498.3 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/bitrepository-webclient-1.10-20170608.133255-5.pom
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/bitrepository-webclient-1.10-20170608.133255-5.pom (3 KB at 117.3 KB/sec)
[INFO] Downloading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/maven-metadata.xml (450 B at 14.2 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 56.3 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/maven-metadata.xml (450 B at 19.1 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/bitrepository-webclient-1.10-20170608.133255-5-tests.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/bitrepository-webclient-1.10-20170608.133255-5-tests.jar (3 KB at 70.2 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 61.2 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/bitrepository-webclient-1.10-20170608.133255-5-sources.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/bitrepository-webclient-1.10-20170608.133255-5-sources.jar (17 KB at 440.5 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 48.6 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/bitrepository-webclient-1.10-20170608.133255-5-distribution.tar.gz
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/bitrepository-webclient-1.10-20170608.133255-5-distribution.tar.gz (12463 KB at 22742.3 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 54.2 KB/sec)
[JENKINS] Archiving disabled
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Integration 1.10-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] Downloading: https://sbforge.org/nexus/content/groups/public/org/bitrepository/reference/bitrepository-client/1.10-SNAPSHOT/bitrepository-client-1.10-20170608.132800-5-distribution.tar.gz
[INFO] Downloaded: https://sbforge.org/nexus/content/groups/public/org/bitrepository/reference/bitrepository-client/1.10-SNAPSHOT/bitrepository-client-1.10-20170608.132800-5-distribution.tar.gz (7826 KB at 14049.9 KB/sec)
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-integration ---
[INFO] Deleting /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/target
[INFO] 
[INFO] --- jacoco-maven-plugin:0.7.5.201505241946:prepare-agent (default) @ bitrepository-integration ---
[INFO] argLine set to -javaagent:/home/cibuild01/.m2/repository/org/jacoco/org.jacoco.agent/0.7.5.201505241946/org.jacoco.agent-0.7.5.201505241946-runtime.jar=destfile=/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/target/jacoco.exec
[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] --- jacoco-maven-plugin:0.7.5.201505241946:report (report) @ bitrepository-integration ---
[INFO] Skipping JaCoCo execution due to missing execution data file:/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/target/jacoco.exec
[INFO] 
[INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ bitrepository-integration ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/target/bitrepository-integration-1.10-SNAPSHOT.jar
[INFO] 
[INFO] --- maven-jar-plugin:2.4:test-jar (default) @ bitrepository-integration ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/target/bitrepository-integration-1.10-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-reference-test/bitrepository-integration/target/bitrepository-integration-1.10-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-reference-test/bitrepository-integration/target/bitrepository-integration-1.10-SNAPSHOT-quickstart.tar.gz
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/target/bitrepository-integration-1.10-SNAPSHOT-tools.tar.gz
[WARNING] Entry: bitrepository-integration-1.10-SNAPSHOT/lib/bitrepository-reference-pillar-1.10-SNAPSHOT-distribution.tar.gz longer than 100 characters.
[WARNING] Resulting tar file can only be processed successfully by GNU compatible tar commands
[WARNING] Entry: bitrepository-integration-1.10-SNAPSHOT/lib/bitrepository-client-1.10-20170608.132800-5-distribution.tar.gz longer than 100 characters.
[INFO] 
[INFO] --- maven-install-plugin:2.5.1:install (default-install) @ bitrepository-integration ---
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/target/bitrepository-integration-1.10-SNAPSHOT.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-SNAPSHOT.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/target/bitrepository-integration-1.10-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/target/bitrepository-integration-1.10-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-SNAPSHOT-sources.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/target/bitrepository-integration-1.10-SNAPSHOT-quickstart.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-SNAPSHOT-quickstart.tar.gz
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/target/bitrepository-integration-1.10-SNAPSHOT-tools.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-SNAPSHOT-tools.tar.gz
[INFO] 
[INFO] --- maven-deploy-plugin:2.8.1:deploy (default-deploy) @ bitrepository-integration ---
[INFO] Downloading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 24.5 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-20170608.133315-5.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-20170608.133315-5.jar (33 KB at 951.9 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-20170608.133315-5.pom
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-20170608.133315-5.pom (4 KB at 127.6 KB/sec)
[INFO] Downloading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/maven-metadata.xml (452 B at 22.1 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 53.9 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/maven-metadata.xml (452 B at 11.9 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-20170608.133315-5-tests.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-20170608.133315-5-tests.jar (3 KB at 69.6 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 64.7 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-20170608.133315-5-sources.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-20170608.133315-5-sources.jar (31 KB at 660.2 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 55.8 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-20170608.133315-5-quickstart.tar.gz
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-20170608.133315-5-quickstart.tar.gz (106372 KB at 23990.0 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 50.5 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-20170608.133315-5-tools.tar.gz
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-20170608.133315-5-tools.tar.gz (119631 KB at 23170.7 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 53.9 KB/sec)
[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 [  8.209 s]
[INFO] Bitrepository Reference Settings ................... SUCCESS [ 12.823 s]
[INFO] Bitrepository Core ................................. SUCCESS [ 55.159 s]
[INFO] Bitrepository Client ............................... SUCCESS [01:16 min]
[INFO] Bitrepository Service .............................. SUCCESS [ 26.085 s]
[INFO] Bitrepository Integrity Service .................... SUCCESS [01:45 min]
[INFO] Bitrepository Alarm Service ........................ SUCCESS [ 20.468 s]
[INFO] Bitrepository Audit Trail Service .................. SUCCESS [ 38.423 s]
[INFO] Bitrepository Reference Pillar ..................... SUCCESS [01:19 min]
[INFO] Bitrepository Monitoring Service ................... SUCCESS [ 18.555 s]
[INFO] Bitrepository Webclient ............................ SUCCESS [  5.396 s]
[INFO] Bitrepository Integration .......................... SUCCESS [ 27.808 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 08:02 min
[INFO] Finished at: 2017-06-08T15:33:29+02:00
[INFO] Final Memory: 61M/146M
[INFO] ------------------------------------------------------------------------
channel stopped
Started indexing related Jira issue keys
Successfully indexed related Jira issue keys
Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered
Triggering a new build of Bitrepository-deploy-ci-test
Finished: SUCCESS