Started by an SCM change
Building remotely on Local activeMQ in workspace /home/cibuild01/workspace/Bitrepository-sonar
> git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> git config remote.origin.url https://github.com/bitrepository/reference.git # timeout=10
Fetching upstream changes from https://github.com/bitrepository/reference.git
> git --version # timeout=10
> git -c core.askpass=true fetch --tags --progress https://github.com/bitrepository/reference.git +refs/heads/master:refs/remotes/origin/master
> git rev-parse refs/remotes/origin/master^{commit} # timeout=10
> git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision 7d318a1a6703c315221a275f438c75949e71d42f (refs/remotes/origin/master)
> git config core.sparsecheckout # timeout=10
> git checkout -f 7d318a1a6703c315221a275f438c75949e71d42f
> git rev-list 5dd8fba4ea986f76eecaf09d542caadfea4349e3 # timeout=10
> git tag -a -f -m Jenkins Build #71 jenkins-Bitrepository-sonar-71 # timeout=10
Parsing POMs
Established TCP socket on 50947
maven32-agent.jar already up to date
maven32-interceptor.jar already up to date
maven3-interceptor-commons.jar already up to date
[Bitrepository-sonar] $ /usr/java/java-1.8.0-oracle-1.8.0.11.x86_64/bin/java -Xmx512m -XX:MaxPermSize=128m -cp /home/cibuild01/maven32-agent.jar:/home/cibuild01/tools/hudson.tasks.Maven_MavenInstallation/Maven3.2/boot/plexus-classworlds-2.5.1.jar:/home/cibuild01/tools/hudson.tasks.Maven_MavenInstallation/Maven3.2/conf/logging jenkins.maven3.agent.Maven32Main /home/cibuild01/tools/hudson.tasks.Maven_MavenInstallation/Maven3.2 /home/cibuild01/slave.jar /home/cibuild01/maven32-interceptor.jar /home/cibuild01/maven3-interceptor-commons.jar 50947
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=128m; support was removed in 8.0
<===[JENKINS REMOTING CAPACITY]===> channel started
Executing Maven: -B -f /home/cibuild01/workspace/Bitrepository-sonar/pom.xml clean install
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO]
[INFO] Bitrepository
[INFO] Bitrepository Reference Settings
[INFO] Bitrepository Core
[INFO] Bitrepository Client
[INFO] Bitrepository Service
[INFO] Bitrepository Integrity Service
[INFO] Bitrepository Alarm Service
[INFO] Bitrepository Audit Trail Service
[INFO] Bitrepository Reference Pillar
[INFO] Bitrepository Monitoring Service
[INFO] Bitrepository Webclient
[INFO] Bitrepository Integration
[INFO]
[INFO] Using the builder org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder with a thread count of 1
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository 1.6-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-parent ---
[INFO] Deleting /home/cibuild01/workspace/Bitrepository-sonar/target
[INFO]
[INFO] --- maven-jar-plugin:2.4:test-jar (default) @ bitrepository-parent ---
[WARNING] JAR will be empty - no content was marked for inclusion!
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/target/bitrepository-parent-1.6-SNAPSHOT-tests.jar
[INFO]
[INFO] --- maven-source-plugin:2.2.1:jar-no-fork (attach-sources-no-fork) @ bitrepository-parent ---
[INFO]
[INFO] --- maven-install-plugin:2.5.1:install (default-install) @ bitrepository-parent ---
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-parent/1.6-SNAPSHOT/bitrepository-parent-1.6-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/target/bitrepository-parent-1.6-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-parent/1.6-SNAPSHOT/bitrepository-parent-1.6-SNAPSHOT-tests.jar
[JENKINS] Archiving disabled
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Reference Settings 1.6-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-reference-settings ---
[INFO] Deleting /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-settings/target
[INFO]
[INFO] --- maven-resources-plugin:2.6:copy-resources (copy-resources) @ bitrepository-reference-settings ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO]
[INFO] --- maven-jaxb2-plugin:0.11.0:generate (generate-classes-from-xsds) @ bitrepository-reference-settings ---
[INFO] Sources are not up-to-date, XJC will be executed.
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ bitrepository-reference-settings ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO] Copying 1 resource
[INFO] Copying 1 resource
[INFO]
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ bitrepository-reference-settings ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 38 source files to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-settings/target/classes
[INFO]
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ bitrepository-reference-settings ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-settings/src/test/resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ bitrepository-reference-settings ---
[INFO] No sources to compile
[INFO]
[INFO] --- maven-surefire-plugin:2.17:test (default-test) @ bitrepository-reference-settings ---
[INFO] No tests to run.
[JENKINS] Recording test results
[INFO]
[INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ bitrepository-reference-settings ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-settings/target/bitrepository-reference-settings-1.6-SNAPSHOT.jar
[INFO]
[INFO] --- maven-jar-plugin:2.4:test-jar (default) @ bitrepository-reference-settings ---
[WARNING] JAR will be empty - no content was marked for inclusion!
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-settings/target/bitrepository-reference-settings-1.6-SNAPSHOT-tests.jar
[INFO]
[INFO] --- maven-source-plugin:2.2.1:jar-no-fork (attach-sources-no-fork) @ bitrepository-reference-settings ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-settings/target/bitrepository-reference-settings-1.6-SNAPSHOT-sources.jar
[INFO]
[INFO] --- maven-install-plugin:2.5.1:install (default-install) @ bitrepository-reference-settings ---
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-settings/target/bitrepository-reference-settings-1.6-SNAPSHOT.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-settings/1.6-SNAPSHOT/bitrepository-reference-settings-1.6-SNAPSHOT.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-settings/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-settings/1.6-SNAPSHOT/bitrepository-reference-settings-1.6-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-settings/target/bitrepository-reference-settings-1.6-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-settings/1.6-SNAPSHOT/bitrepository-reference-settings-1.6-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-settings/target/bitrepository-reference-settings-1.6-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-settings/1.6-SNAPSHOT/bitrepository-reference-settings-1.6-SNAPSHOT-sources.jar
[JENKINS] Archiving disabled
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Core 1.6-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-core ---
[INFO] Deleting /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-core/target
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ bitrepository-core ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ bitrepository-core ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 89 source files to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-core/target/classes
[WARNING] /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-core/src/main/java/org/bitrepository/protocol/messagebus/SimpleMessageBus.java:[5,46] sun.reflect.generics.reflectiveObjects.NotImplementedException is internal proprietary API and may be removed in a future release
[INFO]
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ bitrepository-core ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 11 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ bitrepository-core ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 62 source files to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-core/target/test-classes
[INFO]
[INFO] --- maven-surefire-plugin:2.17:test (default-test) @ bitrepository-core ---
[INFO] Surefire report directory: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-core/target/surefire-reports
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running TestSuite
Configuring TestNG with: TestNG652Configurator
Starting test project Core module test
Suite: Surefire suite
Starting testcase 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 MultiThreadedMessageBusTest
02:18:11.222 WARN o.a.activemq.broker.BrokerService - Memory Usage for the Broker (1024 mb) is more than the maximum available for the JVM: 487 mb - resetting to 70% of maximum available: 341 mb
02:18:11.283 WARN o.a.activemq.broker.BrokerService - Temporary Store limit is 51200 mb, whilst the temporary data directory: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-core/target/activemq-data/localhost/tmp_storage only has 11117 mb of usable space - resetting to maximum available 11117 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@4bc28c33[correlationID=12345, collectionID=MySla, destination=BusActivityTest, replyTo=topic://clientTopic, from=ClientPillar, to=<null>, version=28, minVersion=24, auditTrailInformation=User: Name, Institution: Place, fileID=MyDataID]
Stimuli: Sending message: org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileRequest@4bc28c33[correlationID=12345, collectionID=MySla, destination=BusActivityTest, replyTo=topic://clientTopic, from=ClientPillar, to=<null>, version=28, minVersion=24, auditTrailInformation=User: Name, Institution: Place, fileID=MyDataID]
Stimuli: Sending message: org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileRequest@4bc28c33[correlationID=12345, collectionID=MySla, destination=BusActivityTest, replyTo=topic://clientTopic, from=ClientPillar, to=<null>, version=28, minVersion=24, auditTrailInformation=User: Name, Institution: Place, fileID=MyDataID]
Test success: manyTheadsBeforeFinish
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 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 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 SecurityManagerTest
Test starting: certificateAuthorizationBehaviourTest
Description: Tests that a certificate is only allowed by registered users (component).
Step: Check that the registered component is allowed.
Step: Check that an unregistered component is not allowed.
Test success: certificateAuthorizationBehaviourTest
Test starting: negativeSigningAuthenticationRoundtripBadDataTest
Description: Tests that a roundtrip of signing a request and afterwards authenticating it fails due to bad data
Description: Tests that a roundtrip of signing a request and afterwards authenticating is succedes.
Step: Sign a chunck of data.
Step: Check signature matches the data
Test success: negativeSigningAuthenticationRoundtripBadDataTest
Test starting: negativeSigningAuthenticationRoundtripUnkonwnCertificateTest
Description: Tests that a roundtrip of signing a request and afterwards authenticating it fails due to a unknown certificate.
Step: Sign a chunck of data.
Step: Check signature matches the data
Test success: negativeSigningAuthenticationRoundtripUnkonwnCertificateTest
Test starting: operationAuthorizationBehaviourTest
Description: Tests that a signature only allows the correct requests.
Step: Check that GET_FILE is allowed.
Test success: operationAuthorizationBehaviourTest
Test starting: positiveSigningAuthenticationRoundtripTest
Description: Tests that a roundtrip of signing a request and afterwards authenticating is succedes.
Step: Sign a chunck of data.
Step: Check signature matches the data
Test success: positiveSigningAuthenticationRoundtripTest
Starting testcase SettingsLoaderTest
Test starting: testDevelopmentCollectionSettingsLoading
Test success: testDevelopmentCollectionSettingsLoading
Test starting: testExampleSettingsLoading
Test success: testExampleSettingsLoading
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 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 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@4caa6cbe[correlationID=12345, collectionID=MyCollection, destination=topic://collectionTopic, replyTo=topic://clientTopic, from=ClientPillar, to=<null>, version=28, minVersion=24, auditTrailInformation=User: Name, Institution: Place, fileID=MyDataID]
Step: Send an identify request with the 'Collection' header property set to my collection
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@426d9b5b[correlationID=12345, collectionID=MyCollection, destination=topic://collectionTopic, replyTo=topic://clientTopic, from=ClientPillar, to=<null>, version=28, minVersion=24, auditTrailInformation=User: Name, Institution: Place, fileID=MyDataID]
Step: Send an invalid message with the 'Receiver' header property set to another specific component
Test success: collectionFilterTest
Test starting: sendMessageToSpecificComponentTest
Description: Test that message bus correct uses the 'to' header property to indicated that the message is meant for a specific component
Step: Send a message with the 'Recipient' parameter set to at specific component
Stimuli: Sending message: org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@321c2a7[correlationID=12345, collectionID=MySla, destination=TEST-TOPIC-cibuild01, replyTo=topic://clientTopic, from=ClientPillar, to=specificReceiver, version=28, minVersion=24, auditTrailInformation=User: Name, Institution: Place, fileID=MyDataID]
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@465207ce[correlationID=12345, collectionID=MySla, destination=TEST-TOPIC-cibuild01, replyTo=topic://clientTopic, from=ClientPillar, to=specificReceiver, version=28, minVersion=24, auditTrailInformation=User: Name, Institution: Place, fileID=MyDataID]
Test success: sendMessageToSpecificComponentTest
Result: The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@465207ce[correlationID=12345, collectionID=MySla, destination=TEST-TOPIC-cibuild01, replyTo=topic://clientTopic, from=ClientPillar, to=specificReceiver, version=28, minVersion=24, auditTrailInformation=User: Name, Institution: Place, fileID=MyDataID]
02:18:27.202 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@465207ce[correlationID=12345, collectionID=MySla, destination=TEST-TOPIC-cibuild01, replyTo=topic://clientTopic, from=ClientPillar, to=specificReceiver, version=28, minVersion=24, auditTrailInformation=User: Name, Institution: Place, fileID=MyDataID]
Test 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@3509160[correlationID=12345, collectionID=MySla, destination=TEST-TOPIC-cibuild01, replyTo=topic://clientTopic, from=ClientPillar, to=<null>, version=28, minVersion=24, auditTrailInformation=User: Name, Institution: Place, fileID=MyDataID]
Step: Send an identify request with the 'To' header property set to this component
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@1c80d228[correlationID=12345, collectionID=MySla, destination=TEST-TOPIC-cibuild01, replyTo=topic://clientTopic, from=ClientPillar, to=<null>, version=28, minVersion=24, auditTrailInformation=User: Name, Institution: Place, fileID=MyDataID]
Step: Send an invalid identify request with the 'To' header property set to another specific component
Step: Send an identify response with the 'To' header property set to another component
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileResponse@329935a0[correlationID=12345, collectionID=MySla, destination=topic://collectionTopic, replyTo=topic://clientTopic, from=MyPillar, to=<null>, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@64a3284a[responseCode=IDENTIFICATION_POSITIVE, responseText=Ready to delete file 'MyDataID'.], fileID=MyDataID, pillarID=MyPillar, pillarChecksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@637f6e2f[checksumType=MD5, checksumSalt={-85,-51}, otherChecksumType=<null>], timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@79f4e1fa[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@23bff51[correlationID=12345, collectionID=MySla, destination=TEST-TOPIC-cibuild01, replyTo=topic://clientTopic, from=ClientPillar, to=<null>, version=28, minVersion=24, auditTrailInformation=User: Name, Institution: Place, pillarID=MyPillar, fileID=MyDataID, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@60204abe[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@49dae82b[checksumType=MD5, checksumSalt={-85,-85}, otherChecksumType=<null>], checksumValue={19,95,33,86}, calculationTimestamp=2011-02-17T09:47:00], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@723397f[checksumType=MD5, checksumSalt={-85,-51}, otherChecksumType=<null>]]
Test success: toFilterTest
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 CalendarUtilsTest
Test starting: calendarTester
Description: Test the calendar utility class
Step: Test the convertion of a date
Step: Test that a 'null' date is equivalent to epoch
Step: Test epoch
Step: Test that a given time in millis is extractable in millis
Step: Test the 'getNow' function
Step: Test the reverse conversion, from XMLCalendar to Date
Test success: calendarTester
Test starting: utilityTester
Description: Test that the utility class is a proper utility class.
Test success: utilityTester
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@4270705f[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@6f69b0ba[origDateTime=2011-05-03T11:18:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>]]
Step: Make sure both listeners received the message
Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@7fa76624[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@5521a3c8[origDateTime=2011-05-03T11:18:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>]]
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@31a80c88[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@7602c65d[origDateTime=2011-05-03T11:18:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>]]
Step: Make sure both listeners received the message
Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@673171e9[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@4a606a7b[origDateTime=2011-05-03T11:18:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>]]
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@55a07f97[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@33986be7[origDateTime=2011-05-03T11:18:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>]]
Step: Make sure both listeners received the message
Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@3994a7c4[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@1840989a[origDateTime=2011-05-03T11:18:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>]]
Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@648806d0[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@3ce2bfd2[origDateTime=2011-05-03T11:18:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>]]
Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@205ada23[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@6099ac8[origDateTime=2011-05-03T11:18:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>]]
Test success: twoListenersForTopicTest
Result: The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.AlarmMessage@3994a7c4[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@1840989a[origDateTime=2011-05-03T11:18:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>]]
02:18:32.877 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.AlarmMessage@3994a7c4[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@1840989a[origDateTime=2011-05-03T11:18:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>]]
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@3328db4f[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@4f9e9c21[origDateTime=2011-05-03T11:18:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>]]
Step: Make sure both listeners received the message
Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@4c8859f8[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@4322ca2e[origDateTime=2011-05-03T11:18:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>]]
Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@503e7d2a[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@295cd187[origDateTime=2011-05-03T11:18:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>]]
Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@74a44f7b[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@3907c683[origDateTime=2011-05-03T11:18:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>]]
Test success: twoListenersForTopicTest
Result: The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.AlarmMessage@4c8859f8[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@4322ca2e[origDateTime=2011-05-03T11:18:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>]]
02:18:33.815 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.AlarmMessage@4c8859f8[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@4322ca2e[origDateTime=2011-05-03T11:18:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>]]
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 MessageSignerExceptionTest
Test starting: testMessageSigningException
Description: Test the instantiation of the exception
Step: Setup
Step: Try to throw such an exception
Step: Throw the exception with an embedded exception
Test success: testMessageSigningException
Starting testcase MessageUtilsTest
Test starting: testIdentificationResponse
Description: Tests isIdentifyResponse method in the message utility class.
Step: validate that it can see a identify response
Test success: testIdentificationResponse
Test starting: testPositiveIdentification
Description: Tests isPositiveIdentifyResponse method in the message utility class.
Step: validate that it can see a positive identify response
Test success: testPositiveIdentification
Test starting: testProgressResponse
Description: Tests isPositiveProgressResponse method in the message utility class.
Step: validate progress response
Test success: testProgressResponse
Test starting: validateUtilityClass
Description: Validating that the utility class is actually an utility class.
Test success: validateUtilityClass
Starting testcase PermissionStoreExceptionTest
Test starting: testPermissionStoreException
Description: Test the instantiation of the exception
Step: Setup
Step: Try to throw such an exception
Step: Throw the exception with an embedded exception
Test success: testPermissionStoreException
Starting testcase 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 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 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 MessageCreationTest
Test starting: messageCreationTest
Description: Tests if we are able to create message objects from xml. The input XML is the example code defined in the message-xml, thereby also testing whether this is valid.
Step: Creating IdentifyPillarsForGetFileRequest message
Step: Creating IdentifyPillarsForGetFileResponse message
Step: Creating GetFileRequest message
Step: Creating GetFileProgressResponse message
Step: Creating GetFileFinalResponse message
Step: Creating IdentifyPillarsForPutFileRequest message
Step: Creating IdentifyPillarsForPutFileResponse message
Step: Creating PutFileRequest message
Step: Creating PutFileProgressResponse message
Step: Creating PutFileFinalResponse message
Step: Creating IdentifyPillarsForDeleteFileRequest message
Step: Creating IdentifyPillarsForDeleteFileResponse message
Step: Creating DeleteFileRequest message
Step: Creating DeleteFileProgressResponse message
Step: Creating DeleteFileFinalResponse message
Step: Creating IdentifyPillarsForReplaceFileRequest message
Step: Creating IdentifyPillarsForReplaceFileResponse message
Step: Creating ReplaceFileRequest message
Step: Creating ReplaceFileProgressResponse message
Step: Creating ReplaceFileFinalResponse message
Step: Creating IdentifyPillarsForGetChecksumsRequest message
Step: Creating IdentifyPillarsForGetChecksumsResponse message
Step: Creating GetChecksumsRequest message
Step: Creating GetChecksumsProgressResponse message
Step: Creating GetChecksumsFinalResponse message
Step: Creating IdentifyPillarsForGetFileIDsRequest message
Step: Creating IdentifyPillarsForGetFileIDsResponse message
Step: Creating GetFileIDsRequest message
Step: Creating GetFileIDsProgressResponse message
Step: Creating GetFileIDsFinalResponse message
Step: Creating IdentifyContributorsForGetStatusRequest message
Step: Creating IdentifyContributorsForGetStatusResponse message
Step: Creating GetStatusRequest message
Step: Creating GetStatusProgressResponse message
Step: Creating GetStatusFinalResponse message
Step: Creating IdentifyContributorsForGetAuditTrailsRequest message
Step: Creating IdentifyContributorsForGetAuditTrailsResponse message
Step: Creating GetAuditTrailsRequest message
Step: Creating GetAuditTrailsProgressResponse message
Step: Creating GetAuditTrailsFinalResponse message
Step: Creating AlarmMessage message
Test success: messageCreationTest
Starting testcase 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 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 CertificateUseExceptionTest
Test starting: testCertificateUseException
Description: Test the instantiation of the exception
Step: Setup
Step: Try to throw such an exception
Step: Throw the exception with an embedded exception
Test success: testCertificateUseException
Starting testcase ConfigLoaderTest
Test starting: testLoadingConfig
Description: Test the loading of a configuration file for the config loader.
Step: Setup variables
Step: Test with a invalid file path
Step: Test when the file is unreadable
Step: success case
Test success: testLoadingConfig
Starting testcase FileUtilsTest
Test starting: createDeleteDirectoryTester
Description: Test the ability to delete directories.
Step: Test deleting a directory with file and subdirectory
Test success: createDeleteDirectoryTester
Test starting: createDirectoryTester
Description: Test the ability to create directories.
Step: Test the ability to create a directory
Step: Test error scenarios, when the directory path is a file
Test success: createDirectoryTester
Test starting: createSubDirectoryTester
Description: Test the ability to create sub directories.
Step: Test the ability to create sub-directories
Step: Test that it fails if the 'directory' is actually a file
Step: Test that it fails, if the parent directory does not allow writing
Test success: createSubDirectoryTester
Test starting: deprecateFileTester
Description: Test the deprecation of a file.
Step: Setup
Step: Deprecate the file
Test success: deprecateFileTester
Test starting: moveFileTester
Description: Test the moving of a file.
Step: Setup
Step: Move the file
Test success: moveFileTester
Test starting: unzipFileTester
Description: Test unzipping a file.
Step: Setup
Step: Unzip the zipfile to the directory
Test success: unzipFileTester
Test starting: utilityTester
Description: Test that the utility class is a proper utility class.
Test success: utilityTester
Test starting: writeInputstreamTester
Description: Test writing an inputstream to a file.
Step: Setup
Step: Write the input stream to the file
Test success: writeInputstreamTester
Starting testcase XMLFileSettingsLoaderTest
Test starting: testCollectionSettingsLoading
Test success: testCollectionSettingsLoading
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 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 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: componentIDTest
Test success: componentIDTest
Test starting: reloadTest
Test success: reloadTest
Finished testcase
02:18:40.334 ERROR o.b.protocol.bus.RawMessagebus - JMSException caught:
javax.jms.JMSException: java.io.EOFException
at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:54) ~[activemq-client-5.11.1.jar:5.11.1]
at org.apache.activemq.ActiveMQConnection.onAsyncException(ActiveMQConnection.java:1997) ~[activemq-client-5.11.1.jar:5.11.1]
at org.apache.activemq.ActiveMQConnection.onException(ActiveMQConnection.java:2016) ~[activemq-client-5.11.1.jar:5.11.1]
at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:101) ~[activemq-client-5.11.1.jar:5.11.1]
at org.apache.activemq.transport.ResponseCorrelator.onException(ResponseCorrelator.java:126) ~[activemq-client-5.11.1.jar:5.11.1]
at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:101) ~[activemq-client-5.11.1.jar:5.11.1]
at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:101) ~[activemq-client-5.11.1.jar:5.11.1]
at org.apache.activemq.transport.WireFormatNegotiator.onException(WireFormatNegotiator.java:160) ~[activemq-client-5.11.1.jar:5.11.1]
at org.apache.activemq.transport.AbstractInactivityMonitor.onException(AbstractInactivityMonitor.java:314) ~[activemq-client-5.11.1.jar:5.11.1]
at org.apache.activemq.transport.TransportSupport.onException(TransportSupport.java:96) ~[activemq-client-5.11.1.jar:5.11.1]
at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:200) ~[activemq-client-5.11.1.jar:5.11.1]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_11]
Caused by: java.io.EOFException: null
at java.io.DataInputStream.readInt(DataInputStream.java:392) ~[na:1.8.0_11]
at org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:258) ~[activemq-client-5.11.1.jar:5.11.1]
at org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:221) ~[activemq-client-5.11.1.jar:5.11.1]
at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:213) ~[activemq-client-5.11.1.jar:5.11.1]
at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:196) ~[activemq-client-5.11.1.jar:5.11.1]
... 1 common frames omitted
02:18:40.444 ERROR o.b.protocol.bus.RawMessagebus - JMSException caught:
javax.jms.JMSException: java.io.EOFException
at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:54) ~[activemq-client-5.11.1.jar:5.11.1]
at org.apache.activemq.ActiveMQConnection.onAsyncException(ActiveMQConnection.java:1997) ~[activemq-client-5.11.1.jar:5.11.1]
at org.apache.activemq.ActiveMQConnection.onException(ActiveMQConnection.java:2016) ~[activemq-client-5.11.1.jar:5.11.1]
at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:101) ~[activemq-client-5.11.1.jar:5.11.1]
at org.apache.activemq.transport.ResponseCorrelator.onException(ResponseCorrelator.java:126) ~[activemq-client-5.11.1.jar:5.11.1]
at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:101) ~[activemq-client-5.11.1.jar:5.11.1]
at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:101) ~[activemq-client-5.11.1.jar:5.11.1]
at org.apache.activemq.transport.WireFormatNegotiator.onException(WireFormatNegotiator.java:160) ~[activemq-client-5.11.1.jar:5.11.1]
at org.apache.activemq.transport.AbstractInactivityMonitor.onException(AbstractInactivityMonitor.java:314) ~[activemq-client-5.11.1.jar:5.11.1]
at org.apache.activemq.transport.TransportSupport.onException(TransportSupport.java:96) ~[activemq-client-5.11.1.jar:5.11.1]
at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:200) ~[activemq-client-5.11.1.jar:5.11.1]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_11]
Caused by: java.io.EOFException: null
at java.io.DataInputStream.readInt(DataInputStream.java:392) ~[na:1.8.0_11]
at org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:258) ~[activemq-client-5.11.1.jar:5.11.1]
at org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:221) ~[activemq-client-5.11.1.jar:5.11.1]
at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:213) ~[activemq-client-5.11.1.jar:5.11.1]
at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:196) ~[activemq-client-5.11.1.jar:5.11.1]
... 1 common frames omitted
02:18:40.451 ERROR o.b.protocol.bus.RawMessagebus - JMSException caught:
javax.jms.JMSException: java.io.EOFException
at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:54) ~[activemq-client-5.11.1.jar:5.11.1]
at org.apache.activemq.ActiveMQConnection.onAsyncException(ActiveMQConnection.java:1997) ~[activemq-client-5.11.1.jar:5.11.1]
at org.apache.activemq.ActiveMQConnection.onException(ActiveMQConnection.java:2016) ~[activemq-client-5.11.1.jar:5.11.1]
at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:101) ~[activemq-client-5.11.1.jar:5.11.1]
at org.apache.activemq.transport.ResponseCorrelator.onException(ResponseCorrelator.java:126) ~[activemq-client-5.11.1.jar:5.11.1]
at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:101) ~[activemq-client-5.11.1.jar:5.11.1]
at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:101) ~[activemq-client-5.11.1.jar:5.11.1]
at org.apache.activemq.transport.WireFormatNegotiator.onException(WireFormatNegotiator.java:160) ~[activemq-client-5.11.1.jar:5.11.1]
at org.apache.activemq.transport.AbstractInactivityMonitor.onException(AbstractInactivityMonitor.java:314) ~[activemq-client-5.11.1.jar:5.11.1]
at org.apache.activemq.transport.TransportSupport.onException(TransportSupport.java:96) ~[activemq-client-5.11.1.jar:5.11.1]
at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:200) ~[activemq-client-5.11.1.jar:5.11.1]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_11]
Caused by: java.io.EOFException: null
at java.io.DataInputStream.readInt(DataInputStream.java:392) ~[na:1.8.0_11]
at org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:258) ~[activemq-client-5.11.1.jar:5.11.1]
at org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:221) ~[activemq-client-5.11.1.jar:5.11.1]
at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:213) ~[activemq-client-5.11.1.jar:5.11.1]
at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:196) ~[activemq-client-5.11.1.jar:5.11.1]
... 1 common frames omitted
Finished suite
Finished project
Tests run: 95, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 35.64 sec - in TestSuite
Results :
Tests run: 95, Failures: 0, Errors: 0, Skipped: 0
[JENKINS] Recording test results
log4j:WARN No appenders could be found for logger (org.apache.commons.beanutils.converters.BooleanConverter).
log4j:WARN Please initialize the log4j system properly.
[INFO]
[INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ bitrepository-core ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-core/target/bitrepository-core-1.6-SNAPSHOT.jar
[INFO]
[INFO] --- maven-jar-plugin:2.4:test-jar (default) @ bitrepository-core ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-core/target/bitrepository-core-1.6-SNAPSHOT-tests.jar
[INFO]
[INFO] --- maven-source-plugin:2.2.1:jar-no-fork (attach-sources-no-fork) @ bitrepository-core ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-core/target/bitrepository-core-1.6-SNAPSHOT-sources.jar
[INFO]
[INFO] --- maven-install-plugin:2.5.1:install (default-install) @ bitrepository-core ---
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-core/target/bitrepository-core-1.6-SNAPSHOT.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-core/1.6-SNAPSHOT/bitrepository-core-1.6-SNAPSHOT.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-core/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-core/1.6-SNAPSHOT/bitrepository-core-1.6-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-core/target/bitrepository-core-1.6-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-core/1.6-SNAPSHOT/bitrepository-core-1.6-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-core/target/bitrepository-core-1.6-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-core/1.6-SNAPSHOT/bitrepository-core-1.6-SNAPSHOT-sources.jar
[JENKINS] Archiving disabled
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Client 1.6-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-client ---
[INFO] Deleting /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/target
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ bitrepository-client ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 4 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ bitrepository-client ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 130 source files to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/target/classes
[INFO]
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ bitrepository-client ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/src/test/resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ bitrepository-client ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 41 source files to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/target/test-classes
[INFO]
[INFO] --- maven-surefire-plugin:2.17:test (default-test) @ bitrepository-client ---
[INFO] Surefire report directory: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/target/surefire-reports
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running TestSuite
Configuring TestNG with: TestNG652Configurator
Starting test project Core module test
Suite: Surefire suite
Starting testcase AuditTrailClientComponentTest
Test starting: getAllAuditTrailsTest
Description: Tests the simplest case of getting all audit trail event for all contributers.
Step: Create a AuditTrailClient.
Step: Retrieve all audit trails from the collection by calling with a null componentQueries array
Stimuli: Calling getAuditTrails(null, default-test-file.txt, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@72d6b3ba[correlationID=7ebb84c7-e99d-474b-8108-109a6acf9555, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=getAllAuditTrailsTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
Result: Received event: 7ebb84c7: 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: 7ebb84c7: GET_AUDIT_TRAILS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 7ebb84c7: GET_AUDIT_TRAILS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 7ebb84c7: GET_AUDIT_TRAILS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2, Pillar1]
Result: Received event: 7ebb84c7: 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@6ca18a14[correlationID=7ebb84c7-e99d-474b-8108-109a6acf9555, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=getAllAuditTrailsTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar1, fileID=default-test-file.txt, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@51bd8b5c[correlationID=7ebb84c7-e99d-474b-8108-109a6acf9555, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=getAllAuditTrailsTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar2, fileID=default-test-file.txt, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
Step: Send a final response from pillar 1
Result: Received event: 7ebb84c7: 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: 7ebb84c7: GET_AUDIT_TRAILS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2, NumberOfAuditTrailEvents=2, PartialResult=false
Result: Received event: 7ebb84c7: 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@4b41dd5c[correlationID=fec5ac95-bf4e-4503-88b3-735961914136, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=getSomeAuditTrailsTest, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>]
Result: Received event: fec5ac95: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
Step: Send a identifyResponse from pillar1
Result: Received event: fec5ac95: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: fec5ac95: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: fec5ac95: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1], Sending request for audit trails
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@5d066c7d[correlationID=fec5ac95-bf4e-4503-88b3-735961914136, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=getSomeAuditTrailsTest, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar1, fileID=<null>, minSequenceNumber=1, maxSequenceNumber=3, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=10000, resultAddress=<null>]
Step: Verify no request is sent to pillar2
Step: Send a final response from pillar 1
Result: Received event: fec5ac95: GET_AUDIT_TRAILS: COMPONENT_COMPLETE: ContributorID Pillar1, NumberOfAuditTrailEvents=2, PartialResult=false
Result: Received event: fec5ac95: 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@c2db68f[correlationID=444b1ae7-0fc3-45b1-aa56-8969b3cdce4d, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=incompleteSetOfFinalResponsesTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
Result: Received event: 444b1ae7: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
Step: Send a identifyResponse from each of the two pillars
Result: Received event: 444b1ae7: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 444b1ae7: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 444b1ae7: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2]
Result: Received event: 444b1ae7: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for audit trails
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@61ce23ac[correlationID=444b1ae7-0fc3-45b1-aa56-8969b3cdce4d, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=incompleteSetOfFinalResponsesTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar1, fileID=<null>, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@3668d4[correlationID=444b1ae7-0fc3-45b1-aa56-8969b3cdce4d, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=incompleteSetOfFinalResponsesTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar2, fileID=<null>, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
Test success: incompleteSetOfFinalResponsesTest
Result: The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@3668d4[correlationID=444b1ae7-0fc3-45b1-aa56-8969b3cdce4d, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=incompleteSetOfFinalResponsesTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar2, fileID=<null>, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
02:19:06.605 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@3668d4[correlationID=444b1ae7-0fc3-45b1-aa56-8969b3cdce4d, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=incompleteSetOfFinalResponsesTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar2, fileID=<null>, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
Result: Received event: 444b1ae7: GET_AUDIT_TRAILS: FAILED: , Failed to receive responses from all contributors before timeout(500ms). Missing contributors [Pillar1, Pillar2]
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@4d098f9b[correlationID=0aa3f010-58f9-4c08-910e-9e1c26a19cfe, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=negativeGetAuditTrailsResponseTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
Result: Received event: 0aa3f010: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
Step: Send a identifyResponse from each of the two pillars
Result: Received event: 0aa3f010: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 0aa3f010: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 0aa3f010: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2]
Result: Received event: 0aa3f010: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for audit trails
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@7fc44dec[correlationID=0aa3f010-58f9-4c08-910e-9e1c26a19cfe, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=negativeGetAuditTrailsResponseTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar1, fileID=<null>, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@7e3060d8[correlationID=0aa3f010-58f9-4c08-910e-9e1c26a19cfe, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=negativeGetAuditTrailsResponseTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar2, fileID=<null>, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
Step: Send a failed response from pillar 1
Result: Received event: 0aa3f010: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE, GetAuditTrails failed
Step: Send a final response from pillar 2
Result: Received event: 0aa3f010: GET_AUDIT_TRAILS: COMPONENT_COMPLETE: ContributorID Pillar2, NumberOfAuditTrailEvents=2, PartialResult=false
Result: Received event: 0aa3f010: GET_AUDIT_TRAILS: FAILED: , Failed operation. Cause(s):
[0aa3f010: 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@5c1bd44c[correlationID=29d10061-2453-4bb5-99df-28a19bb022ee, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noFinalResponsesTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
Result: Received event: 29d10061: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
Step: Send a identifyResponse from each of the two pillars
Result: Received event: 29d10061: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 29d10061: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 29d10061: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2]
Result: Received event: 29d10061: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for audit trails
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@2e77b8cf[correlationID=29d10061-2453-4bb5-99df-28a19bb022ee, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noFinalResponsesTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar1, fileID=<null>, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@2c4ca0f9[correlationID=29d10061-2453-4bb5-99df-28a19bb022ee, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noFinalResponsesTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar2, fileID=<null>, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
Step: Wait for 1 second
Result: Received event: 29d10061: GET_AUDIT_TRAILS: FAILED: , Failed to receive responses from all contributors before timeout(100ms). Missing contributors [Pillar1, Pillar2]
Test success: noFinalResponsesTest
Result: The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@2e77b8cf[correlationID=29d10061-2453-4bb5-99df-28a19bb022ee, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noFinalResponsesTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar1, fileID=<null>, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
02:19:08.671 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@2e77b8cf[correlationID=29d10061-2453-4bb5-99df-28a19bb022ee, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noFinalResponsesTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar1, fileID=<null>, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
Result: The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@2c4ca0f9[correlationID=29d10061-2453-4bb5-99df-28a19bb022ee, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noFinalResponsesTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar2, fileID=<null>, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
02:19:08.673 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@2c4ca0f9[correlationID=29d10061-2453-4bb5-99df-28a19bb022ee, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noFinalResponsesTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar2, fileID=<null>, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
Test starting: progressEventsTest
Description: Tests that progress events are handled correctly.
Step: Create a AuditTrailClient.
Step: Retrieve all audit trails from the collection by calling with a null componentQueries array
Stimuli: Calling getAuditTrails(null, null, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@772485dd[correlationID=2af7fed0-dd2b-437f-9a82-5d88d69d9264, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=progressEventsTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
Result: Received event: 2af7fed0: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
Step: Send a identifyResponse from each of the two pillars
Result: Received event: 2af7fed0: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 2af7fed0: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 2af7fed0: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2]
Result: Received event: 2af7fed0: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for audit trails
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@6e5bfdfc[correlationID=2af7fed0-dd2b-437f-9a82-5d88d69d9264, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=progressEventsTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar1, fileID=<null>, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@3d829787[correlationID=2af7fed0-dd2b-437f-9a82-5d88d69d9264, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=progressEventsTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar2, fileID=<null>, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
Step: Send a progress accepted response from pillar 1
Result: Received event: 2af7fed0: GET_AUDIT_TRAILS: PROGRESS: ContributorID Pillar1, GetAuditTrails request accepted
Step: Send a general progress response from pillar 2
Result: Received event: 2af7fed0: GET_AUDIT_TRAILS: PROGRESS: ContributorID Pillar2, Still progressing
Test success: progressEventsTest
Test starting: verifyAuditTrailClientFromFactory
Test success: verifyAuditTrailClientFromFactory
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
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@78c1a023[correlationID=97fc3ad0-e6e6-4b97-8656-af7f8f19cbb8, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=collectionIDIncludedInEventsTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
Result: Received event: 97fc3ad0: 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: 97fc3ad0: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 97fc3ad0: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE
Result: Received event: 97fc3ad0: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 97fc3ad0: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1], Sending request for audit trails
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@6a10b263[correlationID=97fc3ad0-e6e6-4b97-8656-af7f8f19cbb8, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=collectionIDIncludedInEventsTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar1, fileID=<null>, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
Step: Wait for 1 second
Result: Received event: 97fc3ad0: GET_AUDIT_TRAILS: FAILED: , Failed to receive responses from all contributors before timeout(500ms). Missing contributors [Pillar1]
Test success: collectionIDIncludedInEventsTest
Starting testcase GetChecksumsClientComponentTest
Test starting: collectionIDIncludedInEventsTest
Description: Tests the the client provides collectionID in events.
Step: Set a 0.5 second operation timeout.
Step: Start the operation
Stimuli: Calling getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@5136207f, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@50194e8d[correlationID=6668aaf6-e5ed-4ec2-8e4c-4f8cb8ac74fa, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=collectionIDIncludedInEventsTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@3cee53dc[fileID=<null>, allFileIDs=true], checksumRequestForExistingFile=<null>]
Result: Received event: 6668aaf6: 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: 6668aaf6: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 6668aaf6: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE
Result: Received event: 6668aaf6: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 6668aaf6: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar1], Sending GetFileIDsRequest's
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@69da0b12[correlationID=6668aaf6-e5ed-4ec2-8e4c-4f8cb8ac74fa, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=collectionIDIncludedInEventsTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@2764c546[fileID=<null>, allFileIDs=true], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, checksumRequestForExistingFile=<null>, resultAddress=<null>]
Step: Wait for 1 second
Result: Received event: 6668aaf6: GET_CHECKSUMS: FAILED: , Failed to receive responses from all contributors before timeout(500ms). Missing contributors [Pillar1]
Test success: collectionIDIncludedInEventsTest
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@338cc75f)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@4f453e63[correlationID=f6ecc9d6-f460-4491-8a4f-371be5981845, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=collectionIDIncludedInEventsTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@7c9bdee9[fileID=<null>, allFileIDs=true]]
Result: Received event: f6ecc9d6: 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: f6ecc9d6: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: f6ecc9d6: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE
Result: Received event: f6ecc9d6: GET_FILE_IDS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: f6ecc9d6: GET_FILE_IDS: REQUEST_SENT: ContributorID [Pillar1], Sending request for get fileIDs
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@49c8f6e8[correlationID=f6ecc9d6-f460-4491-8a4f-371be5981845, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=collectionIDIncludedInEventsTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@6b0615ae[fileID=<null>, allFileIDs=true], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
Step: Wait for 1 second
Result: Received event: f6ecc9d6: GET_FILE_IDS: FAILED: , Failed to receive responses from all contributors before timeout(500ms). Missing contributors [Pillar1]
Test success: collectionIDIncludedInEventsTest
Test starting: conversationTimeoutTest
Description: Tests the the client handles lack of IdentifyPillarResponses gracefully
Step: Set a 100 ms ConversationTimeout.
Step: Start the operation
Stimuli: Calling getAuditTrails(null, null, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@47b67fcb[correlationID=c1e20a2a-e68b-440e-b979-358dd75380a8, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=conversationTimeoutTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
Result: Received event: c1e20a2a: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
02:19:13.879 WARN o.b.c.c.m.CollectionBasedConversationMediator - Failing timed out conversation c1e20a2a-e68b-440e-b979-358dd75380a8 (Age 1008ms)
Result: Received event: c1e20a2a: GET_AUDIT_TRAILS: FAILED: , Failing timed out conversation c1e20a2a-e68b-440e-b979-358dd75380a8
Test success: conversationTimeoutTest
Test starting: conversationTimeoutTest
Description: Tests the the client handles lack of IdentifyPillarResponses gracefully
Step: Set a 100 ms ConversationTimeout.
Step: Start the operation
Stimuli: Calling getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@5136207f, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@3c5dbdf8[correlationID=8a28ee57-1795-4082-bc04-24da87b1edb8, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=conversationTimeoutTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@352c44a8[fileID=<null>, allFileIDs=true], checksumRequestForExistingFile=<null>]
Result: Received event: 8a28ee57: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums
02:19:15.080 WARN o.b.c.c.m.CollectionBasedConversationMediator - Failing timed out conversation 8a28ee57-1795-4082-bc04-24da87b1edb8 (Age 1006ms)
Result: Received event: 8a28ee57: GET_CHECKSUMS: FAILED: , Failing timed out conversation 8a28ee57-1795-4082-bc04-24da87b1edb8
Test success: conversationTimeoutTest
Test starting: conversationTimeoutTest
Description: Tests the the client handles lack of IdentifyPillarResponses gracefully
Step: Set a 100 ms ConversationTimeout.
Step: Start the operation
Stimuli: Calling getFileIDs(null, null, null, org.bitrepository.client.TestEventHandler@338cc75f)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@797c3c3b[correlationID=ef1efe2b-db99-4ae7-8b98-2a5589bbefd9, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=conversationTimeoutTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@4012d5bc[fileID=<null>, allFileIDs=true]]
Result: Received event: ef1efe2b: GET_FILE_IDS: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs
02:19:16.292 WARN o.b.c.c.m.CollectionBasedConversationMediator - Failing timed out conversation ef1efe2b-db99-4ae7-8b98-2a5589bbefd9 (Age 1011ms)
Result: Received event: ef1efe2b: GET_FILE_IDS: FAILED: , Failing timed out conversation ef1efe2b-db99-4ae7-8b98-2a5589bbefd9
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@575e572f[correlationID=d11a0359-dd4a-47ec-8d18-8ee32e34b999, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=identificationFailureTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
Result: Received event: d11a0359: 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: d11a0359: 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: d11a0359: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: d11a0359: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: d11a0359: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar2], Sending request for audit trails
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@4d3c6593[correlationID=d11a0359-dd4a-47ec-8d18-8ee32e34b999, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=identificationFailureTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar2, fileID=<null>, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
Step: Verify that the client continues to the performing phase.
Step: Send a final response message from contributor2
Result: Received event: d11a0359: GET_AUDIT_TRAILS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false
Result: Received event: d11a0359: GET_AUDIT_TRAILS: FAILED: , Failed operation. Cause(s):
[d11a0359: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE]
Test success: identificationFailureTest
Test starting: identificationFailureTest
Description: Verify that the client works correctly when a contributor sends a failure response.
Step: Start the operation.
Stimuli: Calling getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@5136207f, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@2db2a05f[correlationID=e51cf8e4-3819-42f8-a1ca-9751bc3405fa, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=identificationFailureTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@695c938d[fileID=<null>, allFileIDs=true], checksumRequestForExistingFile=<null>]
Result: Received event: e51cf8e4: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums
Step: Send a identification response from contributor1 with a FAILURE response code.
Result: Received event: e51cf8e4: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE
Step: Send a identification response from contributor2 with a IDENTIFICATION_POSITIVE response code .
Result: Received event: e51cf8e4: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: e51cf8e4: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: e51cf8e4: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar2], Sending GetFileIDsRequest's
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@7ed3df3b[correlationID=e51cf8e4-3819-42f8-a1ca-9751bc3405fa, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=identificationFailureTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@465b38e6[fileID=<null>, allFileIDs=true], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, checksumRequestForExistingFile=<null>, resultAddress=<null>]
Step: Verify that the client continues to the performing phase.
Step: Send a final response message from contributor2
Result: Received event: e51cf8e4: GET_CHECKSUMS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false
Result: Received event: e51cf8e4: GET_CHECKSUMS: FAILED: , Failed operation. Cause(s):
[e51cf8e4: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE]
Test success: identificationFailureTest
Test starting: identificationFailureTest
Description: Verify that the client works correctly when a contributor sends a failure response.
Step: Start the operation.
Stimuli: Calling getFileIDs(null, null, null, org.bitrepository.client.TestEventHandler@338cc75f)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@4ed9f7b1[correlationID=6f60d7ef-e2a8-49c5-a5f1-c7e84cb89ac4, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=identificationFailureTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@2d119405[fileID=<null>, allFileIDs=true]]
Result: Received event: 6f60d7ef: 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: 6f60d7ef: 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: 6f60d7ef: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 6f60d7ef: GET_FILE_IDS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: 6f60d7ef: GET_FILE_IDS: REQUEST_SENT: ContributorID [Pillar2], Sending request for get fileIDs
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@20580d4e[correlationID=6f60d7ef-e2a8-49c5-a5f1-c7e84cb89ac4, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=identificationFailureTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@21bd128b[fileID=<null>, allFileIDs=true], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
Step: Verify that the client continues to the performing phase.
Step: Send a final response message from contributor2
Result: Received event: 6f60d7ef: GET_FILE_IDS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false
Result: Received event: 6f60d7ef: GET_FILE_IDS: FAILED: , Failed operation. Cause(s):
[6f60d7ef: 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 getAuditTrails(null, null, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@1e957e2f[correlationID=5c1898b5-7d02-48b4-b5a9-ba91410b3c7f, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=identificationNegativeTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
Result: Received event: 5c1898b5: 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: 5c1898b5: 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: 5c1898b5: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 5c1898b5: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: 5c1898b5: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar2], Sending request for audit trails
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@3db432c2[correlationID=5c1898b5-7d02-48b4-b5a9-ba91410b3c7f, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=identificationNegativeTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar2, fileID=<null>, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
Step: Verify that the client continues to the performing phase.
Step: Send a final response message from contributor2
Result: Received event: 5c1898b5: GET_AUDIT_TRAILS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false
Result: Received event: 5c1898b5: GET_AUDIT_TRAILS: FAILED: , Failed operation. Cause(s):
[5c1898b5: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: IDENTIFICATION_NEGATIVE]
Test success: identificationNegativeTest
Test starting: identificationNegativeTest
Description: Verify that the client works correctly when a contributor sends a negative response.
Step: Start the operation.
Stimuli: Calling getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@5136207f, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@1d4f5506[correlationID=01667b4c-011c-4354-b821-58bf65d273dd, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=identificationNegativeTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@7dee835[fileID=<null>, allFileIDs=true], checksumRequestForExistingFile=<null>]
Result: Received event: 01667b4c: 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: 01667b4c: 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: 01667b4c: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 01667b4c: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: 01667b4c: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar2], Sending GetFileIDsRequest's
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@6e02721d[correlationID=01667b4c-011c-4354-b821-58bf65d273dd, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=identificationNegativeTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@902fdbe[fileID=<null>, allFileIDs=true], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, checksumRequestForExistingFile=<null>, resultAddress=<null>]
Step: Verify that the client continues to the performing phase.
Step: Send a final response message from contributor2
Result: Received event: 01667b4c: GET_CHECKSUMS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false
Result: Received event: 01667b4c: GET_CHECKSUMS: FAILED: , Failed operation. Cause(s):
[01667b4c: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: IDENTIFICATION_NEGATIVE]
Test success: identificationNegativeTest
Test starting: identificationNegativeTest
Description: Verify that the client works correctly when a contributor sends a negative response.
Step: Start the operation.
Stimuli: Calling getFileIDs(null, null, null, org.bitrepository.client.TestEventHandler@338cc75f)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@110e9982[correlationID=d4938d51-71e1-4c87-9cb0-6babed95563e, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=identificationNegativeTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@5eb0a686[fileID=<null>, allFileIDs=true]]
Result: Received event: d4938d51: 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: d4938d51: 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: d4938d51: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: d4938d51: GET_FILE_IDS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: d4938d51: GET_FILE_IDS: REQUEST_SENT: ContributorID [Pillar2], Sending request for get fileIDs
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@67f9cb52[correlationID=d4938d51-71e1-4c87-9cb0-6babed95563e, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=identificationNegativeTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@2de9ca6[fileID=<null>, allFileIDs=true], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
Step: Verify that the client continues to the performing phase.
Step: Send a final response message from contributor2
Result: Received event: d4938d51: GET_FILE_IDS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false
Result: Received event: d4938d51: GET_FILE_IDS: FAILED: , Failed operation. Cause(s):
[d4938d51: 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 getAuditTrails(null, null, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@615efd1c[correlationID=2b9d52f6-bd57-449f-ab8f-e85759dc2bfd, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noContributorsRespondingTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
Result: Received event: 2b9d52f6: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
Step: Wait for 1 second
Result: Received event: 2b9d52f6: GET_AUDIT_TRAILS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar1, Pillar2]
Result: Received event: 2b9d52f6: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor
Result: Received event: 2b9d52f6: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
Result: Received event: 2b9d52f6: GET_AUDIT_TRAILS: FAILED: , Unable to continue operation, contributors unavailable.
Test success: noContributorsRespondingTest
Result: The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@615efd1c[correlationID=2b9d52f6-bd57-449f-ab8f-e85759dc2bfd, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noContributorsRespondingTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
02:19:25.602 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@615efd1c[correlationID=2b9d52f6-bd57-449f-ab8f-e85759dc2bfd, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noContributorsRespondingTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
Test starting: noContributorsRespondingTest
Description: Tests the the client handles lack of a IdentifyResponse gracefully. More concrete this means that the occurrence of a identification timeout should be handled correctly
Step: Set a 100 ms timeout for identifying contributors.
Step: Start the operation.
Stimuli: Calling getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@5136207f, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@9b367c8[correlationID=fa400d80-105d-4114-b791-f00f72e63b1d, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=noContributorsRespondingTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@34c62fdf[fileID=<null>, allFileIDs=true], checksumRequestForExistingFile=<null>]
Result: Received event: fa400d80: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums
Step: Wait for 1 second
Result: Received event: fa400d80: GET_CHECKSUMS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar1, Pillar2]
Result: Received event: fa400d80: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor
Result: Received event: fa400d80: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
Result: Received event: fa400d80: 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@9b367c8[correlationID=fa400d80-105d-4114-b791-f00f72e63b1d, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=noContributorsRespondingTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@34c62fdf[fileID=<null>, allFileIDs=true], checksumRequestForExistingFile=<null>]
02:19:25.935 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@9b367c8[correlationID=fa400d80-105d-4114-b791-f00f72e63b1d, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=noContributorsRespondingTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@34c62fdf[fileID=<null>, allFileIDs=true], checksumRequestForExistingFile=<null>]
Test starting: noContributorsRespondingTest
Description: Tests the the client handles lack of a IdentifyResponse gracefully. More concrete this means that the occurrence of a identification timeout should be handled correctly
Step: Set a 100 ms timeout for identifying contributors.
Step: Start the operation.
Stimuli: Calling getFileIDs(null, null, null, org.bitrepository.client.TestEventHandler@338cc75f)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@7d66a126[correlationID=6071886c-fb18-4ee6-bddb-bcb7678ae064, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=noContributorsRespondingTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@1132baa3[fileID=<null>, allFileIDs=true]]
Result: Received event: 6071886c: GET_FILE_IDS: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs
Step: Wait for 1 second
Result: Received event: 6071886c: GET_FILE_IDS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar1, Pillar2]
Result: Received event: 6071886c: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor
Result: Received event: 6071886c: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
Result: Received event: 6071886c: GET_FILE_IDS: FAILED: , Unable to continue operation, contributors unavailable.
Test success: noContributorsRespondingTest
Result: The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@7d66a126[correlationID=6071886c-fb18-4ee6-bddb-bcb7678ae064, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=noContributorsRespondingTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@1132baa3[fileID=<null>, allFileIDs=true]]
02:19:26.238 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@7d66a126[correlationID=6071886c-fb18-4ee6-bddb-bcb7678ae064, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=noContributorsRespondingTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@1132baa3[fileID=<null>, allFileIDs=true]]
Test starting: oneContributorNotRespondingTest
Description: Verify that the client works correct without receiving identification responses from all contributors.
Added fixture: Set the a identification timeout to 100 ms.
Step: Start the operation.
Stimuli: Calling getAuditTrails(null, null, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@56d6a1b1[correlationID=078d3270-c1a0-4e85-a43e-03d7dfc27f9a, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=oneContributorNotRespondingTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
Result: Received event: 078d3270: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
Step: Send a identification response from contributor1.
Result: Received event: 078d3270: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Step: Wait 1 second.
Result: Received event: 078d3270: GET_AUDIT_TRAILS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar2]
Result: Received event: 078d3270: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
Result: Received event: 078d3270: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 078d3270: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1], Sending request for audit trails
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@4894453e[correlationID=078d3270-c1a0-4e85-a43e-03d7dfc27f9a, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=oneContributorNotRespondingTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar1, fileID=<null>, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
Step: Verify that the client continues to the performing phase.
Step: Send a final response upload message
Result: Received event: 078d3270: GET_AUDIT_TRAILS: COMPONENT_COMPLETE: ContributorID Pillar1, PartialResult=false
Result: Received event: 078d3270: GET_AUDIT_TRAILS: FAILED: , Failed operation. Cause(s):
[078d3270: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor]
Test success: oneContributorNotRespondingTest
Test starting: oneContributorNotRespondingTest
Description: Verify that the client works correct without receiving identification responses from all contributors.
Added fixture: Set the a identification timeout to 100 ms.
Step: Start the operation.
Stimuli: Calling getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@5136207f, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@2342f1ff[correlationID=7234ce85-8eb6-42d7-bcd1-3dcfb9781768, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=oneContributorNotRespondingTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@3303e89e[fileID=<null>, allFileIDs=true], checksumRequestForExistingFile=<null>]
Result: Received event: 7234ce85: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums
Step: Send a identification response from contributor1.
Result: Received event: 7234ce85: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Step: Wait 1 second.
Result: Received event: 7234ce85: GET_CHECKSUMS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar2]
Result: Received event: 7234ce85: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
Result: Received event: 7234ce85: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 7234ce85: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar1], Sending GetFileIDsRequest's
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@4653b25c[correlationID=7234ce85-8eb6-42d7-bcd1-3dcfb9781768, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=oneContributorNotRespondingTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@426c2e4e[fileID=<null>, allFileIDs=true], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, checksumRequestForExistingFile=<null>, resultAddress=<null>]
Step: Verify that the client continues to the performing phase.
Step: Send a final response upload message
Result: Received event: 7234ce85: GET_CHECKSUMS: COMPONENT_COMPLETE: ContributorID Pillar1, PartialResult=false
Result: Received event: 7234ce85: GET_CHECKSUMS: FAILED: , Failed operation. Cause(s):
[7234ce85: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor]
Test success: oneContributorNotRespondingTest
Test starting: oneContributorNotRespondingTest
Description: Verify that the client works correct without receiving identification responses from all contributors.
Added fixture: Set the a identification timeout to 100 ms.
Step: Start the operation.
Stimuli: Calling getFileIDs(null, null, null, org.bitrepository.client.TestEventHandler@338cc75f)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@3b5da0b0[correlationID=943b2d3b-2e6f-4238-a331-e29dfc5465db, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=oneContributorNotRespondingTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@2c9cafa5[fileID=<null>, allFileIDs=true]]
Result: Received event: 943b2d3b: GET_FILE_IDS: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs
Step: Send a identification response from contributor1.
Result: Received event: 943b2d3b: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Step: Wait 1 second.
Result: Received event: 943b2d3b: GET_FILE_IDS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar2]
Result: Received event: 943b2d3b: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
Result: Received event: 943b2d3b: GET_FILE_IDS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 943b2d3b: GET_FILE_IDS: REQUEST_SENT: ContributorID [Pillar1], Sending request for get fileIDs
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@76eb867[correlationID=943b2d3b-2e6f-4238-a331-e29dfc5465db, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=oneContributorNotRespondingTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@6d39a001[fileID=<null>, allFileIDs=true], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
Step: Verify that the client continues to the performing phase.
Step: Send a final response upload message
Result: Received event: 943b2d3b: GET_FILE_IDS: COMPONENT_COMPLETE: ContributorID Pillar1, PartialResult=false
Result: Received event: 943b2d3b: GET_FILE_IDS: FAILED: , Failed operation. Cause(s):
[943b2d3b: 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 getAuditTrails(null, null, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@55061418[correlationID=29a053b2-5507-47c1-a50b-1630896dc7c6, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=operationTimeoutTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
Result: Received event: 29a053b2: 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: 29a053b2: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 29a053b2: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE
Result: Received event: 29a053b2: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 29a053b2: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1], Sending request for audit trails
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@6ec3d8e4[correlationID=29a053b2-5507-47c1-a50b-1630896dc7c6, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=operationTimeoutTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar1, fileID=<null>, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
Step: Wait for 1 second
Result: Received event: 29a053b2: GET_AUDIT_TRAILS: FAILED: , Failed to receive responses from all contributors before timeout(100ms). Missing contributors [Pillar1]
Test success: operationTimeoutTest
Test starting: operationTimeoutTest
Description: Tests the the client handles lack of final responses gracefully.
Step: Set a 100 ms operation timeout.
Step: Start the operation
Stimuli: Calling getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@5136207f, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@abc7005[correlationID=47724c2c-c89d-42b0-91be-3b49106be475, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=operationTimeoutTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@595ec862[fileID=<null>, allFileIDs=true], checksumRequestForExistingFile=<null>]
Result: Received event: 47724c2c: 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: 47724c2c: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 47724c2c: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE
Result: Received event: 47724c2c: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 47724c2c: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar1], Sending GetFileIDsRequest's
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@102af1bb[correlationID=47724c2c-c89d-42b0-91be-3b49106be475, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=operationTimeoutTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@797f97e3[fileID=<null>, allFileIDs=true], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, checksumRequestForExistingFile=<null>, resultAddress=<null>]
Step: Wait for 1 second
Result: Received event: 47724c2c: GET_CHECKSUMS: FAILED: , Failed to receive responses from all contributors before timeout(100ms). Missing contributors [Pillar1]
Test success: operationTimeoutTest
Test starting: operationTimeoutTest
Description: Tests the the client handles lack of final responses gracefully.
Step: Set a 100 ms operation timeout.
Step: Start the operation
Stimuli: Calling getFileIDs(null, null, null, org.bitrepository.client.TestEventHandler@338cc75f)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@164dea80[correlationID=187a3fa9-824d-45ca-a1e4-7f1d1c8a0919, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=operationTimeoutTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@4392362c[fileID=<null>, allFileIDs=true]]
Result: Received event: 187a3fa9: 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: 187a3fa9: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 187a3fa9: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE
Result: Received event: 187a3fa9: GET_FILE_IDS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 187a3fa9: GET_FILE_IDS: REQUEST_SENT: ContributorID [Pillar1], Sending request for get fileIDs
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@839755f[correlationID=187a3fa9-824d-45ca-a1e4-7f1d1c8a0919, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=operationTimeoutTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@71d99732[fileID=<null>, allFileIDs=true], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
Step: Wait for 1 second
Result: Received event: 187a3fa9: GET_FILE_IDS: FAILED: , Failed to receive responses from all contributors before timeout(100ms). Missing contributors [Pillar1]
Test success: operationTimeoutTest
Test starting: getChecksumsDeliveredAtUrl
Description: Tests the delivery of checksums from all pillars at a given URL.
Step: Ensure the delivery file isn't already present on the http server
Step: Request the delivery of the checksum of a file from all pillars.
Stimuli: Calling getChecksums(null, default-test-file.txt, null, file:../bitrepository-core/src/test/resources/test-files//TEST-CHECKSUM-DELIVERY.xml, org.bitrepository.client.TestEventHandler@51d88c38, TEST-AUDIT)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@3ea2f72e[correlationID=ed1c5d7a-2015-48b0-9453-3db129547dff, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=getChecksumsDeliveredAtUrl, to=<null>, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@57b33c29[fileID=default-test-file.txt, allFileIDs=<null>], checksumRequestForExistingFile=<null>]
Result: Received event: ed1c5d7a: 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: ed1c5d7a: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: ed1c5d7a: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: ed1c5d7a: GET_CHECKSUMS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2]
Result: Received event: ed1c5d7a: 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@3a8b9458[correlationID=ed1c5d7a-2015-48b0-9453-3db129547dff, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=getChecksumsDeliveredAtUrl, to=<null>, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@7497a554[fileID=default-test-file.txt, allFileIDs=<null>], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, checksumRequestForExistingFile=<null>, resultAddress=file:../bitrepository-core/src/test/resources/test-files//TEST-CHECKSUM-DELIVERY.xml-Pillar1]
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@5dd23809[correlationID=ed1c5d7a-2015-48b0-9453-3db129547dff, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=getChecksumsDeliveredAtUrl, to=<null>, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT, pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@664f49f[fileID=default-test-file.txt, allFileIDs=<null>], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, checksumRequestForExistingFile=<null>, resultAddress=file:../bitrepository-core/src/test/resources/test-files//TEST-CHECKSUM-DELIVERY.xml-Pillar2]
Step: Sends a final response from each pillar
Result: Received event: ed1c5d7a: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, NumberOfChecksums=0, PartialResult=false
Result: Received event: ed1c5d7a: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2, NumberOfChecksums=0, PartialResult=false
Result: Received event: ed1c5d7a: 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@5dd23809[correlationID=ed1c5d7a-2015-48b0-9453-3db129547dff, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=getChecksumsDeliveredAtUrl, to=<null>, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT, pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@664f49f[fileID=default-test-file.txt, allFileIDs=<null>], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, checksumRequestForExistingFile=<null>, resultAddress=file:../bitrepository-core/src/test/resources/test-files//TEST-CHECKSUM-DELIVERY.xml-Pillar2]
02:19:28.128 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.GetChecksumsRequest@5dd23809[correlationID=ed1c5d7a-2015-48b0-9453-3db129547dff, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=getChecksumsDeliveredAtUrl, to=<null>, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT, pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@664f49f[fileID=default-test-file.txt, allFileIDs=<null>], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, checksumRequestForExistingFile=<null>, resultAddress=file:../bitrepository-core/src/test/resources/test-files//TEST-CHECKSUM-DELIVERY.xml-Pillar2]
Test starting: getChecksumsFromOtherCollection
Description: Tests the getChecksums client will correctly try to get from a second collection if required
Added fixture: Configure collection1 to contain both pillars and collection 2 to only contain pillar2
Step: Request the putting of a file through the PutClient for collection2
Stimuli: Calling getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@1e482ecd, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@58b5f7d2[correlationID=0765e8dc-8276-4f41-afaa-fe1751ef74d2, collectionID=SinglePillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=getChecksumsFromOtherCollection, to=Pillar2, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@bc52a41[fileID=<null>, allFileIDs=true], checksumRequestForExistingFile=<null>]
Result: Received event: 0765e8dc: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums
Step: Send an identification response from pillar2.
Result: Received event: 0765e8dc: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 0765e8dc: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: 0765e8dc: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar2], Sending GetFileIDsRequest's
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@5615f82d[correlationID=0765e8dc-8276-4f41-afaa-fe1751ef74d2, collectionID=SinglePillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=getChecksumsFromOtherCollection, to=Pillar2, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@21698e5a[fileID=<null>, allFileIDs=true], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, checksumRequestForExistingFile=<null>, resultAddress=<null>]
Step: Send a complete event from the pillar
Result: Received event: 0765e8dc: GET_CHECKSUMS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false
Result: Received event: 0765e8dc: 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@66dd04e2[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], null, org.bitrepository.client.TestEventHandler@495e8a3, TEST-AUDIT)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@6a7aa675[correlationID=32fdb137-9550-4cd8-9631-fdd22e8e57c2, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=getChecksumsFromSinglePillar, to=Pillar1, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@6eded11a[fileID=default-test-file.txt, allFileIDs=<null>], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@66dd04e2[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>]]
Result: Received event: 32fdb137: 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: 32fdb137: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 32fdb137: GET_CHECKSUMS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 32fdb137: 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@4b511e61[correlationID=32fdb137-9550-4cd8-9631-fdd22e8e57c2, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=getChecksumsFromSinglePillar, to=Pillar1, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@74a74070[fileID=default-test-file.txt, allFileIDs=<null>], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@66dd04e2[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], resultAddress=<null>]
Step: Send a GetChecksumsFinalResponse to the client from pillar1
Result: Received event: 32fdb137: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, NumberOfChecksums=0, PartialResult=false
Result: Received event: 32fdb137: 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@67396475, TEST-AUDIT)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@55b74e6b[correlationID=150e1817-96ea-45ec-9a1f-237c73a58007, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=testNoSuchFile, to=Pillar1, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@3c1908c8[fileID=default-test-file.txt, allFileIDs=<null>], checksumRequestForExistingFile=<null>]
Result: Received event: 150e1817: 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: 150e1817: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 150e1817: GET_CHECKSUMS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 150e1817: 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@47f0e078[correlationID=150e1817-96ea-45ec-9a1f-237c73a58007, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=testNoSuchFile, to=Pillar1, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@28db2afb[fileID=default-test-file.txt, allFileIDs=<null>], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, checksumRequestForExistingFile=<null>, resultAddress=<null>]
Step: Send a error that the file cannot be found.
Result: Received event: 150e1817: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FILE_NOT_FOUND_FAILURE, No such file.
Result: Received event: 150e1817: GET_CHECKSUMS for file default-test-file.txt: FAILED: , Failed operation. Cause(s):
[150e1817: 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=Sat Nov 21 02:19:28 CET 2015, maxTimestamp=Sat Nov 21 02:19:29 CET 2015, maxNumberOfResults=1}, ContributorQuery{componentID='Pillar2, minTimestamp=Sat Nov 21 02:19:29 CET 2015, maxTimestamp=Sat Nov 21 02:19:29 CET 2015, maxNumberOfResults=2}], null, null, null, org.bitrepository.client.TestEventHandler@5136207f, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@217fd3c[correlationID=e45259a4-deed-4976-8a87-72707431a0b6, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=testPaging, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@69ac5752[fileID=<null>, allFileIDs=true], checksumRequestForExistingFile=<null>]
Result: Received event: e45259a4: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums
Step: Send a IdentifyPillarsForGetChecksumsResponse from both pillars.
Result: Received event: e45259a4: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: e45259a4: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: e45259a4: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2]
Result: Received event: e45259a4: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending GetFileIDsRequest's
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@36eb8e07[correlationID=e45259a4-deed-4976-8a87-72707431a0b6, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=testPaging, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@3df6494f[fileID=<null>, allFileIDs=true], minTimestamp=2015-11-21T02:19:28.808+01:00, maxTimestamp=2015-11-21T02:19:29.708+01:00, maxNumberOfResults=1, checksumRequestForExistingFile=<null>, resultAddress=<null>]
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@1b5f960a[correlationID=e45259a4-deed-4976-8a87-72707431a0b6, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=testPaging, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@53ddabc6[fileID=<null>, allFileIDs=true], minTimestamp=2015-11-21T02:19:29.708+01:00, maxTimestamp=2015-11-21T02:19:29.808+01:00, maxNumberOfResults=2, checksumRequestForExistingFile=<null>, resultAddress=<null>]
Test success: testPaging
Test starting: verifyGetChecksumsClientFromFactory
Test success: verifyGetChecksumsClientFromFactory
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@338cc75f)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@17fb5184[correlationID=1a9a211c-a415-4fee-a0bd-0dea65a949f7, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=getFileIDsDeliveredAtUrl, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@184bb873[fileID=default-test-file.txt, allFileIDs=<null>]]
Result: Received event: 1a9a211c: 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: 1a9a211c: GET_FILE_IDS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 1a9a211c: GET_FILE_IDS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 1a9a211c: 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@5eba9e41[correlationID=1a9a211c-a415-4fee-a0bd-0dea65a949f7, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=getFileIDsDeliveredAtUrl, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@13809363[fileID=default-test-file.txt, allFileIDs=<null>], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=file:../bitrepository-core/src/test/resources/test-files//TEST-FILE-IDS-DELIVERY.xml-Pillar1]
Step: The pillar sends a getFileIDsProgressResponse to the GetFileIDsClient.
Result: Received event: 1a9a211c: 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: 1a9a211c: GET_FILE_IDS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, PartialResult=false
Result: Received event: 1a9a211c: 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@338cc75f)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@34d5eac[correlationID=90162447-ada8-4c4f-a0bf-5ac5984c1029, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=getFileIDsDeliveredThroughMessage, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@2c1a95a2[fileID=default-test-file.txt, allFileIDs=<null>]]
Result: Received event: 90162447: 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: 90162447: GET_FILE_IDS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 90162447: GET_FILE_IDS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 90162447: 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@72b53f27[correlationID=90162447-ada8-4c4f-a0bf-5ac5984c1029, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=getFileIDsDeliveredThroughMessage, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@1be4a7e3[fileID=default-test-file.txt, allFileIDs=<null>], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
Step: The pillar sends a getFileIDsProgressResponse to the GetFileIDsClient.
Result: Received event: 90162447: 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: 90162447: GET_FILE_IDS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, NumberOfFileIDs=1, PartialResult=false
Result: Received event: 90162447: 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@2a9565d7)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@2e38d44e[correlationID=6b221bfd-4af8-4d5d-8403-4a04de47f848, collectionID=SinglePillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=getFileIDsFromOtherCollection, to=Pillar2, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@6c25123e[fileID=default-test-file.txt, allFileIDs=<null>]]
Result: Received event: 6b221bfd: 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: 6b221bfd: GET_FILE_IDS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 6b221bfd: GET_FILE_IDS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: 6b221bfd: 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@5e66733b[correlationID=6b221bfd-4af8-4d5d-8403-4a04de47f848, collectionID=SinglePillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=getFileIDsFromOtherCollection, to=Pillar2, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@3694461d[fileID=default-test-file.txt, allFileIDs=<null>], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
Step: Send a complete event from the pillar
Result: Received event: 6b221bfd: GET_FILE_IDS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false
Result: Received event: 6b221bfd: 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@338cc75f)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@7b6b466a[correlationID=9990f33f-a558-46d4-b2d7-d2cf0a8ad4de, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=testNoSuchFile, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@6686507b[fileID=default-test-file.txt, allFileIDs=<null>]]
Result: Received event: 9990f33f: 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: 9990f33f: GET_FILE_IDS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 9990f33f: GET_FILE_IDS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 9990f33f: 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@2e5c7cd5[correlationID=9990f33f-a558-46d4-b2d7-d2cf0a8ad4de, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=testNoSuchFile, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@f252762[fileID=default-test-file.txt, allFileIDs=<null>], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=file:../bitrepository-core/src/test/resources/test-files//TEST-FILE-IDS-DELIVERY.xml-Pillar1]
Step: Send a error that the file cannot be found.
Result: Received event: 9990f33f: GET_FILE_IDS for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FILE_NOT_FOUND_FAILURE, No such file.
Result: Received event: 9990f33f: GET_FILE_IDS for file default-test-file.txt: FAILED: , Failed operation. Cause(s):
[9990f33f: 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=Sat Nov 21 02:19:29 CET 2015, maxTimestamp=Sat Nov 21 02:19:30 CET 2015, maxNumberOfResults=1}, ContributorQuery{componentID='Pillar2, minTimestamp=Sat Nov 21 02:19:30 CET 2015, maxTimestamp=Sat Nov 21 02:19:30 CET 2015, maxNumberOfResults=2}], null, null, org.bitrepository.client.TestEventHandler@338cc75f)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@799206ad[correlationID=7d3b31ac-0b1e-4465-9a0d-fe120e8b4354, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=testPaging, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@60251ddb[fileID=<null>, allFileIDs=true]]
Result: Received event: 7d3b31ac: GET_FILE_IDS: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs
Step: Send a IdentifyPillarsForGetFileIDsResponse from both pillars.
Result: Received event: 7d3b31ac: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 7d3b31ac: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 7d3b31ac: GET_FILE_IDS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2, Pillar1]
Result: Received event: 7d3b31ac: GET_FILE_IDS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for get fileIDs
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@46c475ba[correlationID=7d3b31ac-0b1e-4465-9a0d-fe120e8b4354, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=testPaging, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@e47637c[fileID=<null>, allFileIDs=true], minTimestamp=2015-11-21T02:19:29.422+01:00, maxTimestamp=2015-11-21T02:19:30.322+01:00, maxNumberOfResults=1, resultAddress=<null>]
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@606f0f70[correlationID=7d3b31ac-0b1e-4465-9a0d-fe120e8b4354, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=testPaging, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@1a53ac0c[fileID=<null>, allFileIDs=true], minTimestamp=2015-11-21T02:19:30.322+01:00, maxTimestamp=2015-11-21T02:19:30.422+01:00, maxNumberOfResults=2, resultAddress=<null>]
Test success: testPaging
Test starting: verifyGetFileIDsClientFromFactory
Test success: verifyGetFileIDsClientFromFactory
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:
-p [OPTIONAL] The id of the pillar where the should be performed. If undefined the operations is performed on all pillars.
-s The path to the directory with the settings files for the client
-c The id for the collection to perform the operation on.
-v Makes the client more verbose
-i The id for the file to perform the operation on.
-k The path to the file containing the private key.
Missing argument: c
Test success: missingCollectionArgumentTest
Test starting: 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: Random1448068771754pillar 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@69e58566[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], org.bitrepository.client.TestEventHandler@2e41e0c, TEST-AUDIT-TRAIL)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@2e214d39[correlationID=41f992c7-dc17-4b4f-ab0d-b828c73686ea, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=defaultReturnChecksumsWithChecksumPillar, to=<null>, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, fileID=default-test-file.txt, fileSize=0]
Result: Received event: 41f992c7: 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: 41f992c7: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Step: Send an normal identification response from pillar2.
Result: Received event: 41f992c7: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 41f992c7: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2, Pillar1]
Result: Received event: 41f992c7: 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@2dc54b50[correlationID=41f992c7-dc17-4b4f-ab0d-b828c73686ea, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=defaultReturnChecksumsWithChecksumPillar, to=<null>, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>, checksumRequestForNewFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@69e58566[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>]]
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@19370af1[correlationID=41f992c7-dc17-4b4f-ab0d-b828c73686ea, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=defaultReturnChecksumsWithChecksumPillar, to=<null>, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, pillarID=Pillar2, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>, checksumRequestForNewFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@69e58566[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>]]
Test success: defaultReturnChecksumsWithChecksumPillar
Test starting: fileExistsOnPillarChecksumFromPillarNoClientChecksum
Description: Tests that PutClient handles the presence of a file correctly, when the pillar returns a checksum but the putFile was called without a checksum.
Step: Call putFile.
Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, null, org.bitrepository.client.TestEventHandler@62b8dd6a, TEST-AUDIT-TRAIL)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@758e6acd[correlationID=296b2cc3-5092-44b0-b3ab-a4e6c4b02a76, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=fileExistsOnPillarChecksumFromPillarNoClientChecksum, to=<null>, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, fileID=default-test-file.txt, fileSize=0]
Result: Received event: 296b2cc3: 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: 296b2cc3: 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@7df994ec[responseCode=DUPLICATE_FILE_FAILURE, responseText=Testing the handling of 'DUPLICATE FILE' identification.] (existing file checksum does not match)
Result: Received event: 296b2cc3: PUT_FILE for file default-test-file.txt: FAILED: , Can not put file default-test-file.txt, as an different file already exists on pillar Pillar1
Test success: fileExistsOnPillarChecksumFromPillarNoClientChecksum
Test starting: fileExistsOnPillarDifferentChecksumFromPillar
Description: Tests that PutClient handles the presence of a file correctly, when the pillar returns a checksum different from the file being put.
Step: Call putFile.
Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@39d62e47[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1ced1fb9[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={-70}, calculationTimestamp=2015-11-21T02:19:32.299+01:00], null, org.bitrepository.client.TestEventHandler@5d28e108, TEST-AUDIT-TRAIL)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@4d2bcca8[correlationID=6712e94e-d1cd-41f3-9272-81d707c725a5, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=fileExistsOnPillarDifferentChecksumFromPillar, to=<null>, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, fileID=default-test-file.txt, fileSize=0]
Result: Received event: 6712e94e: 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: 6712e94e: 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@2b592f17[responseCode=DUPLICATE_FILE_FAILURE, responseText=Testing the handling of 'DUPLICATE FILE' identification.] (existing file checksum does not match)
Result: Received event: 6712e94e: PUT_FILE for file default-test-file.txt: FAILED: , Can not put file default-test-file.txt, as an different file already exists on pillar Pillar1
Test success: fileExistsOnPillarDifferentChecksumFromPillar
Test starting: fileExistsOnPillarNoChecksumFromPillar
Description: Tests that PutClient handles the presence of a file correctly, when the pillar doesn't return a checksum in the identification response.
Step: Call putFile.
Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, null, org.bitrepository.client.TestEventHandler@2fedae96, TEST-AUDIT-TRAIL)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@4945cd1f[correlationID=814a2e49-577e-4fbe-8761-2daa651d4dd6, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=fileExistsOnPillarNoChecksumFromPillar, to=<null>, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, fileID=default-test-file.txt, fileSize=0]
Result: Received event: 814a2e49: 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: 814a2e49: 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@2dbfcbe4[responseCode=DUPLICATE_FILE_FAILURE, responseText=Testing the handling of 'DUPLICATE FILE' identification.]
Result: Received event: 814a2e49: PUT_FILE for file default-test-file.txt: FAILED: , Can not put file default-test-file.txt, as an file already exists on pillar Pillar1
Test success: fileExistsOnPillarNoChecksumFromPillar
Test starting: noPillarsResponding
Description: Tests the handling of missing identification responses from all pillar
Added fixture: Sets the identification timeout to 100 ms.
Step: Request the putting of a file through the PutClient
Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, null, org.bitrepository.client.TestEventHandler@3ff83cc8, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@6dd8ac29[correlationID=ab9a0fc9-a974-4011-895a-bc2d055c715b, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=noPillarsResponding, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt, fileSize=0]
Result: Received event: ab9a0fc9: 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: ab9a0fc9: 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: ab9a0fc9: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor
Result: Received event: ab9a0fc9: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
Result: Received event: ab9a0fc9: PUT_FILE for file default-test-file.txt: FAILED: , Unable to continue operation, contributors unavailable.
Test success: noPillarsResponding
Test starting: noReturnChecksumsWithChecksumPillar
Description: Tests that PutClient handles the presence of a ChecksumPillar correctly, when no return checksum is requested.
Step: Call putFile while requesting a salted checksum to be returned.
Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, null, org.bitrepository.client.TestEventHandler@7225583d, TEST-AUDIT-TRAIL)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@5fe7454c[correlationID=bccd1b8f-da08-438e-8a87-c0d978978794, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=noReturnChecksumsWithChecksumPillar, to=<null>, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, fileID=default-test-file.txt, fileSize=0]
Result: Received event: bccd1b8f: 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: bccd1b8f: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Step: Send an normal identification response from pillar2.
Result: Received event: bccd1b8f: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: bccd1b8f: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2, Pillar1]
Result: Received event: bccd1b8f: 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@71c1e70f[correlationID=bccd1b8f-da08-438e-8a87-c0d978978794, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=noReturnChecksumsWithChecksumPillar, to=<null>, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>, checksumRequestForNewFile=<null>]
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@1469015e[correlationID=bccd1b8f-da08-438e-8a87-c0d978978794, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=noReturnChecksumsWithChecksumPillar, to=<null>, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, pillarID=Pillar2, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>, checksumRequestForNewFile=<null>]
Test success: noReturnChecksumsWithChecksumPillar
Test starting: normalPutFile
Description: Tests the PutClient. Makes a whole conversation for the put client for a 'good' scenario.
Added fixture: Initialise the number of pillars to one
Step: Ensure that the test-file is placed on the HTTP server.
Step: Request the delivery of a file from a specific pillar. A callback listener should be supplied.
Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, null, org.bitrepository.client.TestEventHandler@5d38758a, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@4acae4c7[correlationID=63178d73-d271-4fd9-9161-bc76ed4df008, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=normalPutFile, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt, fileSize=0]
Result: Received event: 63178d73: 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: 63178d73: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 63178d73: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 63178d73: 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@27bfa57f[correlationID=63178d73-d271-4fd9-9161-bc76ed4df008, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=normalPutFile, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>, checksumRequestForNewFile=<null>]
Step: Validate the steps of the PutClient by going through the events.
Step: The pillar sends a progress response to the PutClient.
Result: Received event: 63178d73: 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: 63178d73: PUT_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, requestedChecksumResult=null
Result: Received event: 63178d73: 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@310df168, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@3606c525[correlationID=e5192a73-5f04-4828-85c0-66ce51b2e70a, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarPutRetryFailure, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt, fileSize=0]
Result: Received event: e5192a73: 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: e5192a73: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: e5192a73: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: e5192a73: 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@27959922[correlationID=e5192a73-5f04-4828-85c0-66ce51b2e70a, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarPutRetryFailure, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>, checksumRequestForNewFile=<null>]
Step: The client should proceed to send a putFileOperation request to the responding pillar.
Step: Send a PutFileFinalResponse indicating a FILE_TRANSFER_FAILURE
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@794daa09[correlationID=e5192a73-5f04-4828-85c0-66ce51b2e70a, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarPutRetryFailure, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>, checksumRequestForNewFile=<null>]
Result: Received event: e5192a73: 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@796267e8[correlationID=e5192a73-5f04-4828-85c0-66ce51b2e70a, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarPutRetryFailure, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>, checksumRequestForNewFile=<null>]
Result: Received event: e5192a73: 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: e5192a73: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FILE_TRANSFER_FAILURE
Result: Received event: e5192a73: PUT_FILE for file default-test-file.txt: FAILED: , Failed operation. Cause(s):
[e5192a73: 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@2c2c1790, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@645a9649[correlationID=c15655aa-ce0d-45d3-acbe-4a16afb35475, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarPutRetrySuccess, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt, fileSize=0]
Result: Received event: c15655aa: 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: c15655aa: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: c15655aa: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: c15655aa: 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@7631fb3e[correlationID=c15655aa-ce0d-45d3-acbe-4a16afb35475, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarPutRetrySuccess, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>, checksumRequestForNewFile=<null>]
Step: The client should proceed to send a putFileOperation request to the responding pillar.
Step: Send a PutFileFinalResponse indicating a FILE_TRANSFER_FAILURE
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@3aede2ff[correlationID=c15655aa-ce0d-45d3-acbe-4a16afb35475, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarPutRetrySuccess, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>, checksumRequestForNewFile=<null>]
Result: Received event: c15655aa: 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: c15655aa: PUT_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, requestedChecksumResult=null
Result: Received event: c15655aa: 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@3b538e2a, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@7262532a[correlationID=fdd38dfb-4679-4053-b4d2-2766f32291d0, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarRespondingWithPartialPutAllowed, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt, fileSize=0]
Result: Received event: fdd38dfb: 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: fdd38dfb: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Step: Await the timeout.
Result: Received event: fdd38dfb: 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: fdd38dfb: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
Result: Received event: fdd38dfb: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: fdd38dfb: 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@36a33ea8[correlationID=fdd38dfb-4679-4053-b4d2-2766f32291d0, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarRespondingWithPartialPutAllowed, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>, checksumRequestForNewFile=<null>]
Step: The client should proceed to send a putFileOperation request to the responding pillar.
Step: Send a pillar complete event
Result: Received event: fdd38dfb: PUT_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, requestedChecksumResult=null
Result: Received event: fdd38dfb: PUT_FILE for file default-test-file.txt: FAILED: , Failed operation. Cause(s):
[fdd38dfb: 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@1d7135c, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@2c2f4769[correlationID=07a4eb7d-4109-4ae2-9ecb-2ccd8204b52c, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarRespondingWithPartialPutDisallowed, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt, fileSize=0]
Result: Received event: 07a4eb7d: 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: 07a4eb7d: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Step: Await the timeout.
Result: Received event: 07a4eb7d: 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: 07a4eb7d: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
Result: Received event: 07a4eb7d: PUT_FILE for file default-test-file.txt: FAILED: , Unable to continue operation, contributors unavailable.
Test success: onePillarRespondingWithPartialPutDisallowed
Test starting: putClientOperationTimeout
Description: Tests the handling of a failed operation for the PutClient
Step: Initialise the number of pillars and the PutClient. Sets the operation timeout to 100 ms.
Step: Request the putting of a file through the PutClient
Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, null, org.bitrepository.client.TestEventHandler@3057728e, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@5dbd7f00[correlationID=c6937414-314c-4f67-a713-25739d6ce369, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=putClientOperationTimeout, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt, fileSize=0]
Result: Received event: c6937414: 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: c6937414: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: c6937414: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: c6937414: 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@138c2ba[correlationID=c6937414-314c-4f67-a713-25739d6ce369, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=putClientOperationTimeout, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>, checksumRequestForNewFile=<null>]
Step: Validate the steps of the PutClient by going through the events.
Step: Do not respond. Just await the timeout.
Result: Received event: c6937414: PUT_FILE for file default-test-file.txt: FAILED: , Failed to receive responses from all contributors before timeout(100ms). Missing contributors [Pillar1]
Test success: putClientOperationTimeout
Test starting: putClientPillarOperationFailed
Description: Tests the handling of a operation failure for the PutClient.
Step: Initialise the number of pillars to one
Step: Ensure that the test-file is placed on the HTTP server.
Step: Request the delivery of a file from a specific pillar. A callback listener should be supplied.
Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, null, org.bitrepository.client.TestEventHandler@36dab184, TEST-AUDIT-TRAIL)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@71b9b035[correlationID=e047a5f7-5c29-4084-a16a-4a89891c596d, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=putClientPillarOperationFailed, to=Pillar1, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, fileID=default-test-file.txt, fileSize=0]
Result: Received event: e047a5f7: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file
Step: Send pillar response.
Result: Received event: e047a5f7: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: e047a5f7: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: e047a5f7: 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@724945[correlationID=e047a5f7-5c29-4084-a16a-4a89891c596d, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=putClientPillarOperationFailed, to=Pillar1, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>, checksumRequestForNewFile=<null>]
Step: Validate the steps of the PutClient by going through the events.
Step: Send a failed response message to the PutClient.
Result: Received event: e047a5f7: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE, Verifying that a failure can be understood!
Result: Received event: e047a5f7: PUT_FILE for file default-test-file.txt: FAILED: , Failed operation. Cause(s):
[e047a5f7: 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@5af7a7, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@685e8e17[correlationID=28e3e6a7-7e93-4147-ad33-d547a892897a, collectionID=SinglePillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=putToOtherCollection, to=Pillar2, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt, fileSize=0]
Result: Received event: 28e3e6a7: 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: 28e3e6a7: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 28e3e6a7: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: 28e3e6a7: 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@5f3705e7[correlationID=28e3e6a7-7e93-4147-ad33-d547a892897a, collectionID=SinglePillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=putToOtherCollection, to=Pillar2, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar2, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>, checksumRequestForNewFile=<null>]
Step: Send a put complete event from the pillar
Result: Received event: 28e3e6a7: PUT_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2, requestedChecksumResult=null
Result: Received event: 28e3e6a7: 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@28ea7f58[checksumType=HMAC_MD5, checksumSalt={-86}, otherChecksumType=<null>], org.bitrepository.client.TestEventHandler@2cf7ada5, TEST-AUDIT-TRAIL)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@14c6d1b7[correlationID=a5c0699e-c869-4744-abdf-42b2261583f4, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=saltedReturnChecksumsWithChecksumPillar, to=<null>, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, fileID=default-test-file.txt, fileSize=0]
Result: Received event: a5c0699e: 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: a5c0699e: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Step: Send an normal identification response from pillar2.
Result: Received event: a5c0699e: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: a5c0699e: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2, Pillar1]
Result: Received event: a5c0699e: 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@664c6bbc[correlationID=a5c0699e-c869-4744-abdf-42b2261583f4, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=saltedReturnChecksumsWithChecksumPillar, to=<null>, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>, checksumRequestForNewFile=<null>]
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@442545ab[correlationID=a5c0699e-c869-4744-abdf-42b2261583f4, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=saltedReturnChecksumsWithChecksumPillar, to=<null>, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, pillarID=Pillar2, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>, checksumRequestForNewFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@28ea7f58[checksumType=HMAC_MD5, checksumSalt={-86}, otherChecksumType=<null>]]
Test success: saltedReturnChecksumsWithChecksumPillar
Test starting: sameFileExistsOnOnePillar
Description: Tests that PutClient handles the presence of a file correctly, when the pillar returns a checksum equal the file being put (idempotent).
Step: Call putFile.
Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@26ae9861[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@5b1b5daf[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-11-21T02:19:34.695+01:00], null, org.bitrepository.client.TestEventHandler@66e74d3, TEST-AUDIT-TRAIL)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@1e1c1634[correlationID=64169c3f-b485-427e-acce-b7f3aa720cdc, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=sameFileExistsOnOnePillar, to=<null>, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, fileID=default-test-file.txt, fileSize=0]
Result: Received event: 64169c3f: 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: 64169c3f: PUT_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, requestedChecksumResult=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@38691f8d[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@463a0302[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-11-21T02:19:34.695+01:00], File already existed on Pillar1
Step: Send an identification response from the second pillar.
Result: Received event: 64169c3f: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 64169c3f: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: 64169c3f: 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@79228440[correlationID=64169c3f-b485-427e-acce-b7f3aa720cdc, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=sameFileExistsOnOnePillar, to=<null>, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, pillarID=Pillar2, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@26ae9861[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@5b1b5daf[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-11-21T02:19:34.695+01:00], checksumRequestForNewFile=<null>]
Step: The client should proceed to send a putFileOperation request to the second pillar.
Step: Send a pillar complete event
Result: Received event: 64169c3f: PUT_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2, requestedChecksumResult=null
Result: Received event: 64169c3f: 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 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@345f429[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@3464d24c[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@341f2f4c[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, 10, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@68754439[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@3464d24c[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@341f2f4c[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], org.bitrepository.client.TestEventHandler@44bd11a2, null
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileRequest@56595dcb[correlationID=bc9713e3-b279-4abf-9033-ab3339a78e73, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-ReplaceFileClientComponentTest-cibuild01, from=replaceClientIdentificationTimeout, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt, fileSize=<null>]
Result: Received event: bc9713e3: 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: bc9713e3: 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: bc9713e3: REPLACE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor
Result: Received event: bc9713e3: REPLACE_FILE for file default-test-file.txt: FAILED: , Unable to continue operation, contributors unavailable.
Test success: replaceClientIdentificationTimeout
Test starting: replaceClientOperationTimeout
Description: Tests the handling of a failed operation for the ReplaceClient
Step: Initialise the number of pillars and the DeleteClient. Sets the operation timeout to 100 ms.
Step: Request a file to be replaced on the default pillar.
Stimuli: replaceFile(default-test-file.txt, Pillar1, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@51dcf51b[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6eb58fdd[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7a0619a8[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, 10, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@5df9d890[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6eb58fdd[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7a0619a8[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], org.bitrepository.client.TestEventHandler@6b3b9a19, null
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileRequest@29b23bc4[correlationID=fdd1b63a-f68b-44b7-bbb0-eaf4fe9d3575, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-ReplaceFileClientComponentTest-cibuild01, from=replaceClientOperationTimeout, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt, fileSize=<null>]
Result: Received event: fdd1b63a: 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: fdd1b63a: REPLACE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: fdd1b63a: REPLACE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: fdd1b63a: 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@701dc5ad[correlationID=fdd1b63a-f68b-44b7-bbb0-eaf4fe9d3575, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-ReplaceFileClientComponentTest-cibuild01, from=replaceClientOperationTimeout, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@51dcf51b[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6eb58fdd[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7a0619a8[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=10, checksumDataForNewFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@5df9d890[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6eb58fdd[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], checksumRequestForNewFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7a0619a8[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>]]
Step: Validate the steps of the ReplaceClient by going through the events.
Step: Do not respond. Just await the timeout.
Result: Received event: fdd1b63a: REPLACE_FILE for file default-test-file.txt: FAILED: , Failed to receive responses from all contributors before timeout(100ms). Missing contributors [Pillar1]
Test success: replaceClientOperationTimeout
Test starting: replaceClientPillarFailed
Description: Tests the handling of a operation failure for the ReplaceClient.
Step: Initialise the number of pillars to one
Step: Request a file to be replaced on the default pillar.
Stimuli: replaceFile(default-test-file.txt, Pillar1, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@5c8d22de[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@71ef3f0c[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@471021f8[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, 0, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@3bbd9232[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@71ef3f0c[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@471021f8[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], org.bitrepository.client.TestEventHandler@e13cc49, null
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileRequest@60c95d8[correlationID=395fdb5d-9e10-4e71-8e56-682d175ab503, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-ReplaceFileClientComponentTest-cibuild01, from=replaceClientPillarFailed, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt, fileSize=<null>]
Result: Received event: 395fdb5d: 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: 395fdb5d: REPLACE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 395fdb5d: REPLACE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 395fdb5d: 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@172e4d3a[correlationID=395fdb5d-9e10-4e71-8e56-682d175ab503, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-ReplaceFileClientComponentTest-cibuild01, from=replaceClientPillarFailed, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@5c8d22de[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@71ef3f0c[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@471021f8[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@3bbd9232[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@71ef3f0c[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], checksumRequestForNewFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@471021f8[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>]]
Step: Validate the steps of the ReplaceClient by going through the events.
Step: Send a failed response message to the ReplaceClient.
Result: Received event: 395fdb5d: REPLACE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE, Verifying that a failure can be understood!
Result: Received event: 395fdb5d: REPLACE_FILE for file default-test-file.txt: FAILED: , Failed operation. Cause(s):
[395fdb5d: 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@31dd8a0b[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@346e62d7[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@59d64b60[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, 10, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@60e72ced[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@346e62d7[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@59d64b60[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], org.bitrepository.client.TestEventHandler@3d376f28, null
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileRequest@7a08da83[correlationID=21c6c29e-516c-4d98-995c-8325f75f0ee0, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-ReplaceFileClientComponentTest-cibuild01, from=replaceClientTester, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt, fileSize=<null>]
Result: Received event: 21c6c29e: 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: 21c6c29e: REPLACE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 21c6c29e: REPLACE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 21c6c29e: 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@4837c56d[correlationID=21c6c29e-516c-4d98-995c-8325f75f0ee0, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-ReplaceFileClientComponentTest-cibuild01, from=replaceClientTester, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@31dd8a0b[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@346e62d7[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@59d64b60[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=10, checksumDataForNewFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@60e72ced[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@346e62d7[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], checksumRequestForNewFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@59d64b60[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>]]
Step: Validate the steps of the ReplaceClient by going through the events.
Step: The pillar sends a progress response to the ReplaceClient.
Result: Received event: 21c6c29e: 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: 21c6c29e: REPLACE_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, checksum for new file: 'org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@60e72ced[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@346e62d7[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00]',checksum for replaced file: 'null'
Result: Received event: 21c6c29e: 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@b79953e[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6c743da[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], null, file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, 0, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@722af653[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6c743da[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@71fff0b[checksumType=MD5, checksumSalt={-86}, otherChecksumType=<null>], org.bitrepository.client.TestEventHandler@40085ab3, null
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileRequest@7c6d18fb[correlationID=129c39a6-f027-4e8c-8e43-4660e9ee2da7, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-ReplaceFileClientComponentTest-cibuild01, from=saltedReturnChecksumsForNewFileWithChecksumPillar, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt, fileSize=<null>]
Result: Received event: 129c39a6: 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: 129c39a6: REPLACE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 129c39a6: REPLACE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 129c39a6: 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@214faadd[correlationID=129c39a6-f027-4e8c-8e43-4660e9ee2da7, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-ReplaceFileClientComponentTest-cibuild01, from=saltedReturnChecksumsForNewFileWithChecksumPillar, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@b79953e[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6c743da[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], checksumRequestForExistingFile=<null>, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@722af653[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6c743da[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], checksumRequestForNewFile=<null>]
Test success: saltedReturnChecksumsForNewFileWithChecksumPillar
Test starting: verifyReplaceFileClientFromFactory
Description: Testing the initialization through the ModifyComponentFactory.
Step: Use the ModifyComponentFactory to instantiate a ReplaceFileClient.
Test success: verifyReplaceFileClientFromFactory
Starting testcase AuditTrailQueryTest
Test starting: testBothSequenceNumberFailure
Description: Test the creation of a AuditTrailQuery with both SequenceNumber, where max is smalle than min.
Test success: testBothSequenceNumberFailure
Test starting: testBothSequenceNumberSuccess
Description: Test the creation of a AuditTrailQuery with both SequenceNumber, where max is larger than min.
Test success: testBothSequenceNumberSuccess
Test starting: testNoSequenceNumbers
Description: Test that a AuditTrailQuery can be created without any sequence numbers.
Test success: testNoSequenceNumbers
Test starting: testOnlyMinSequenceNumber
Description: Test the creation of a AuditTrailQuery with only the minSequenceNumber
Test success: testOnlyMinSequenceNumber
Starting testcase DeleteFileCmdTest
Test starting: checksumArgumentNonSaltAlgorithmWitoutSaltTest
Description: Test MD5 checksum without salt -> no failure
Test success: checksumArgumentNonSaltAlgorithmWitoutSaltTest
Test starting: checksumArgumentSaltAlgorithmWithSaltTest
Description: Test HMAC_SHA256 checksum with salt -> No failure
Test success: checksumArgumentSaltAlgorithmWithSaltTest
Test starting: defaultSuccessScenarioTest
Description: Tests simplest arguments for running the CmdLineClient
Test success: defaultSuccessScenarioTest
Test starting: missingCollectionArgumentTest
Description: Tests the scenario, where the collection arguments is missing.
Takes the following arguments:
-p [OPTIONAL] The id of the pillar where the should be performed. If undefined the operations is performed on all pillars.
-R [OPTIONAL] The algorithm of checksum to request in the response from the pillars.
-s The path to the directory with the settings files for the client
-c The id for the collection to perform the operation on.
-C [OPTIONAL] The checksum of the file to be delete.
-S [OPTIONAL] The salt of checksum to request in the response. Requires the ChecksumType argument.
-v Makes the client more verbose
-i The id for the file to perform the operation on.
-k The path to the file containing the private key.
Missing argument: c
Test success: missingCollectionArgumentTest
Test starting: missingFileIDArgumentTest
Description: Tests the scenario, where no arguments for file id argument is given.
Takes the following arguments:
-p [OPTIONAL] The id of the pillar where the should be performed. If undefined the operations is performed on all pillars.
-R [OPTIONAL] The algorithm of checksum to request in the response from the pillars.
-s The path to the directory with the settings files for the client
-c The id for the collection to perform the operation on.
-C [OPTIONAL] The checksum of the file to be delete.
-S [OPTIONAL] The salt of checksum to request in the response. Requires the ChecksumType argument.
-v Makes the client more verbose
-i The id for the file to perform the operation on.
-k The path to the file containing the private key.
Missing argument: i
Test success: missingFileIDArgumentTest
Test starting: missingPillarArgumentTest
Description: Tests the different scenarios, with the pillar argument.
Invalid argument: The pillar argument -p must defined for the delete operation, only single pillar deletes are allowed
Test success: missingPillarArgumentTest
Test starting: unknownPillarArgumentTest
Step: Testing against a non-existing pillar id
Invalid argument: Random1448068777015pillar is not a valid pillar for collection TwoPillarCollection
The collection contains the following pillars: [Pillar1, Pillar2]
Test success: unknownPillarArgumentTest
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:
-p [OPTIONAL] The id of the pillar where the should be performed. If undefined the operations is performed on all pillars.
-R [OPTIONAL] The algorithm of checksum to request in the response from the pillars. If no such argument is given, then the default from settings is retrieved.
-s The path to the directory with the settings files for the client
-c The id for the collection to perform the operation on.
-S [OPTIONAL] The salt of checksum to request in the response. Requires the ChecksumType argument.
-v Makes the client more verbose
-i The id for the file to perform the operation on.
-k The path to the file containing the private key.
Missing argument: c
Test success: missingCollectionArgumentTest
Test starting: 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: Random1448068777865pillar 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 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@135a2a14[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1464019a[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@4339a2e5[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], eventHandler, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@68645c77[correlationID=2f147acd-fe70-4636-9acd-d48e94441038, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientIdentificationTimeout, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt]
Result: Received event: 2f147acd: 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: 2f147acd: 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: 2f147acd: DELETE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor
Result: Received event: 2f147acd: DELETE_FILE for file default-test-file.txt: FAILED: , Unable to continue operation, contributors unavailable.
Test success: deleteClientIdentificationTimeout
Test starting: deleteClientOperationTimeout
Description: Tests the handling of a failed operation for the DeleteClient
Step: Initialise the number of pillars and the DeleteClient. Sets the operation timeout to 100 ms.
Step: Request a file to be deleted on the default pillar.
Stimuli: Calling deleteFile(default-test-file.txt, Pillar1, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@1456ada1[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@699f5e36[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1e09f286[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], eventHandler, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@55fc6954[correlationID=9d6f9591-27a2-4a0a-a88a-e3882c092c37, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientOperationTimeout, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt]
Result: Received event: 9d6f9591: 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: 9d6f9591: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 9d6f9591: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 9d6f9591: 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@679b73ab[correlationID=9d6f9591-27a2-4a0a-a88a-e3882c092c37, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientOperationTimeout, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@1456ada1[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@699f5e36[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1e09f286[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>]]
Step: Validate the steps of the DeleteClient by going through the events.
Step: Do not respond. Just await the timeout.
Result: Received event: 9d6f9591: DELETE_FILE for file default-test-file.txt: FAILED: , Failed to receive responses from all contributors before timeout(100ms). Missing contributors [Pillar1]
Test success: deleteClientOperationTimeout
Test starting: deleteClientOtherPillarFailedDuringIdentification
Description: Tests the handling of a identification failure for a pillar for the DeleteClient.
Step: Request a file to be deleted on the pillar1.
Stimuli: Calling deleteFile(default-test-file.txt, Pillar1, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@6818550d[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@4d310fe6[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-11-21T02:19:39.877+01:00], null, eventHandler, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@34923f7f[correlationID=1a7d55e5-7607-452a-8b8c-d08a5fa6f508, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientOtherPillarFailedDuringIdentification, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt]
Result: Received event: 1a7d55e5: 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: 1a7d55e5: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 1a7d55e5: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 1a7d55e5: 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@28d38288[correlationID=1a7d55e5-7607-452a-8b8c-d08a5fa6f508, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientOtherPillarFailedDuringIdentification, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@6818550d[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@4d310fe6[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-11-21T02:19:39.877+01:00], checksumRequestForExistingFile=<null>]
Step: Send a final response message from pillar 1 to the DeleteClient.
Result: Received event: 1a7d55e5: DELETE_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, DeleteFileResult=null
Result: Received event: 1a7d55e5: 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@6afa82fe[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7cb8b526[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@797b2044[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], eventHandler, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@45cfbcc2[correlationID=3ca07d41-7faa-4519-bef6-9c76e9eedd73, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientPillarFailedDuringPerform, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt]
Result: Received event: 3ca07d41: 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: 3ca07d41: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 3ca07d41: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 3ca07d41: 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@42b4b037[correlationID=3ca07d41-7faa-4519-bef6-9c76e9eedd73, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientPillarFailedDuringPerform, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@6afa82fe[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7cb8b526[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@797b2044[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>]]
Step: Validate the steps of the DeleteClient by going through the events.
Step: Send a failed response message to the DeleteClient.
Result: Received event: 3ca07d41: DELETE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE, Verifying that a failure can be understood!
Result: Received event: 3ca07d41: DELETE_FILE for file default-test-file.txt: FAILED: , Failed operation. Cause(s):
[3ca07d41: 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@6c8d6a2f[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@394c61cb[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-11-21T02:19:41.903+01:00], null, eventHandler, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@71713254[correlationID=234cb80c-e1a0-41d3-867e-1f2a7988b7ff, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientSpecifiedPillarFailedDuringIdentification, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt]
Result: Received event: 234cb80c: 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: 234cb80c: DELETE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: IDENTIFICATION_NEGATIVE
Result: Received event: 234cb80c: DELETE_FILE for file default-test-file.txt: FAILED: , Can not continue with delete operation, as Pillar1 is unable to perform the deletion.
Test success: deleteClientSpecifiedPillarFailedDuringIdentification
Test starting: deleteClientTester
Description: Tests the DeleteClient. Makes a whole conversation for the delete client for a 'good' scenario.
Step: Initialise the number of pillars to one
Step: Request a file to be deleted on all pillars (which means only the default pillar).
Stimuli: Calling deleteFile(default-test-file.txt, Pillar1, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@32144b3c[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@3601fb92[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@64434d5c[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], eventHandler, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@4a57771a[correlationID=126b9cc8-37ba-4de0-a5dd-8a9fbd0930cb, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientTester, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt]
Result: Received event: 126b9cc8: 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: 126b9cc8: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 126b9cc8: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 126b9cc8: 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@636e356f[correlationID=126b9cc8-37ba-4de0-a5dd-8a9fbd0930cb, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientTester, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@32144b3c[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@3601fb92[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@64434d5c[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>]]
Step: Validate the steps of the DeleteClient by going through the events.
Step: The pillar sends a progress response to the DeleteClient.
Result: Received event: 126b9cc8: 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: 126b9cc8: DELETE_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, DeleteFileResult=null
Result: Received event: 126b9cc8: 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@20defbeb[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1eb738e5[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-11-21T02:19:42.807+01:00], null, eventHandler, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@456c2b84[correlationID=ae657321-a5a5-4cf2-b045-d7b62e695984, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteOnChecksumPillar, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt]
Result: Received event: ae657321: 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: ae657321: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: ae657321: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: ae657321: 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@6f3679a7[correlationID=ae657321-a5a5-4cf2-b045-d7b62e695984, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteOnChecksumPillar, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@20defbeb[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1eb738e5[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-11-21T02:19:42.807+01:00], checksumRequestForExistingFile=<null>]
Test success: deleteOnChecksumPillar
Test starting: deleteOnChecksumPillarWithDefaultReturnChecksumType
Description: Verify that the DeleteClient works correctly when a return checksum of the default typeis requested.
Step: Request a file to be deleted on the pillar1. The call should include a request for a check sum of the default type
Stimuli: Calling deleteFile(default-test-file.txt, Pillar1, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@6b2f16b9[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@67d15f2[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-11-21T02:19:45.000+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1fb25bca[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], eventHandler, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@2e1e02b8[correlationID=9fe12e16-513f-4387-bbce-c8d8b1d2d843, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteOnChecksumPillarWithDefaultReturnChecksumType, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt]
Result: Received event: 9fe12e16: 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: 9fe12e16: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 9fe12e16: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 9fe12e16: 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@53ab03c9[correlationID=9fe12e16-513f-4387-bbce-c8d8b1d2d843, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteOnChecksumPillarWithDefaultReturnChecksumType, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@6b2f16b9[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@67d15f2[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-11-21T02:19:45.000+01:00], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1fb25bca[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>]]
Test success: deleteOnChecksumPillarWithDefaultReturnChecksumType
Test starting: deleteOnChecksumPillarWithSaltedReturnChecksumType
Description: Verify that the DeleteClient works correctly when a return checksum with a salt is requested.
Step: Request a file to be deleted on the pillar1. The call should include a request for a salted check sum
Stimuli: Calling deleteFile(default-test-file.txt, Pillar1, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@360ea519[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2e643cad[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-11-21T02:19:45.207+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@14270971[checksumType=MD5, checksumSalt={-86}, otherChecksumType=<null>], eventHandler, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@21c64b8e[correlationID=5f75b2f0-59b2-49e2-bbfe-ee2d7b953065, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteOnChecksumPillarWithSaltedReturnChecksumType, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt]
Result: Received event: 5f75b2f0: 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: 5f75b2f0: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 5f75b2f0: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 5f75b2f0: 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@6d2dcd7f[correlationID=5f75b2f0-59b2-49e2-bbfe-ee2d7b953065, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteOnChecksumPillarWithSaltedReturnChecksumType, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@360ea519[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2e643cad[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-11-21T02:19:45.207+01:00], checksumRequestForExistingFile=<null>]
Test success: deleteOnChecksumPillarWithSaltedReturnChecksumType
Test starting: fileAlreadyDeletedFromPillar
Description: Test that a delete on a pillar completes successfully when the file is missing (has already been deleted). This is a test of the Idempotent behaviour of the delete client
Step: Request a file to be deleted on pillar1.
Stimuli: Calling deleteFile(default-test-file.txt, Pillar1, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@117eac4a[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@cdb12a5[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2015-11-21T02:19:45.387+01:00], null, eventHandler, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@59732214[correlationID=7cbfed0f-7b03-4c18-a0e6-9fc237942390, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=fileAlreadyDeletedFromPillar, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt]
Result: Received event: 7cbfed0f: 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: 7cbfed0f: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 7cbfed0f: DELETE_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, DeleteFileResult=null
Result: Received event: 7cbfed0f: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: []
Result: Received event: 7cbfed0f: DELETE_FILE for file default-test-file.txt: COMPLETE:
Step: The client should then continue to the performing phase and finish immediately as the pillar has already had the file removed apparently .
Step: Send a identify response from Pillar2
Test success: fileAlreadyDeletedFromPillar
Test starting: verifyDeleteClientFromFactory
Description: Testing the initialization through the ModifyComponentFactory.
Step: Use the ModifyComponentFactory to instantiate a PutFileClient.
Test success: verifyDeleteClientFromFactory
Starting testcase 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@15db58c9[correlationID=9054fa87-2f98-4aa1-9b0c-6152e925d964, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=chooseFastestPillarGetFileClient, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt]
Result: Received event: 9054fa87: 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: 9054fa87: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID THE-AVERAGE-PILLAR
Result: Received event: 9054fa87: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID THE-FAST-PILLAR
Result: Received event: 9054fa87: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID THE-SLOW-PILLAR
Result: Received event: 9054fa87: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [THE-FAST-PILLAR]
Result: Received event: 9054fa87: 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@3f88558d[correlationID=9054fa87-2f98-4aa1-9b0c-6152e925d964, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=chooseFastestPillarGetFileClient, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=THE-FAST-PILLAR, fileID=default-test-file.txt, filePart=<null>, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt]
Test success: chooseFastestPillarGetFileClient
Test starting: conversationTimeout
Description: Tests the the GetFileClient handles lack of IdentifyPillarResponses gracefully
Step: Set the number of pillars to 100ms and a 300 ms timeout for the conversation.
Step: Request the delivery of a file from a specific pillar. A callback listener should be supplied.
Stimuli: Calling getFileFromSpecificPillar(default-test-file.txt, file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, Pillar1)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileRequest@78f2bb1b[correlationID=90431d5a-2702-4e4f-949c-3f7f8b41c52f, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=conversationTimeout, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt]
Result: Received event: 90431d5a: 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: 90431d5a: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 90431d5a: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 90431d5a: 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@10323056[correlationID=90431d5a-2702-4e4f-949c-3f7f8b41c52f, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=conversationTimeout, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, filePart=<null>, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt]
Step: Wait for 1 second
02:19:48.149 WARN o.b.c.c.m.CollectionBasedConversationMediator - Failing timed out conversation 90431d5a-2702-4e4f-949c-3f7f8b41c52f (Age 999ms)
Result: Received event: 90431d5a: GET_FILE for file default-test-file.txt: FAILED: , Failing timed out conversation 90431d5a-2702-4e4f-949c-3f7f8b41c52f
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@5b9e7722[correlationID=7d6ed10e-1084-49e6-91ff-bc131f591a36, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=failureDuringPerform, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt]
Result: Received event: 7d6ed10e: 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: 7d6ed10e: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 7d6ed10e: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 7d6ed10e: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 7d6ed10e: 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@48efa366[correlationID=7d6ed10e-1084-49e6-91ff-bc131f591a36, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=failureDuringPerform, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, filePart=<null>, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt]
Step: Send a failure response from pillar1
Result: Received event: 7d6ed10e: GET_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE
Result: Received event: 7d6ed10e: GET_FILE for file default-test-file.txt: FAILED: , Failed to get file from Pillar1, org.bitrepository.bitrepositoryelements.ResponseInfo@1487c3b3[responseCode=FAILURE, responseText=<null>]
Test success: failureDuringPerform
Test starting: getFileClientWithChecksumPillarInvolved
Description: Verify that the GetFile works correctly when a checksum pillar respond.
Step: Call getFile form fastest pillar.
Stimuli: Calling getFileFromFastestPillar(default-test-file.txt, file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileRequest@79749108[correlationID=c60761d9-2d41-4030-9731-a7239c23a14a, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=getFileClientWithChecksumPillarInvolved, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt]
Result: Received event: c60761d9: 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: c60761d9: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: c60761d9: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: c60761d9: 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@f284a7a[correlationID=c60761d9-2d41-4030-9731-a7239c23a14a, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=getFileClientWithChecksumPillarInvolved, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar2, fileID=default-test-file.txt, filePart=<null>, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt]
Step: Verify that the client continues to the performing phase.
Step: Send a final response upload message
Result: Received event: c60761d9: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2
Result: Received event: c60761d9: 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@4d3c0cce[correlationID=c02d48d0-462d-4d5a-a94a-f13a16b71a44, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=getFileClientWithIdentifyTimeout, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt]
Result: Received event: c02d48d0: 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: c02d48d0: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Step: Wait 1 second.
Result: Received event: c02d48d0: 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: c02d48d0: GET_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
Result: Received event: c02d48d0: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: c02d48d0: 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@151e786c[correlationID=c02d48d0-462d-4d5a-a94a-f13a16b71a44, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=getFileClientWithIdentifyTimeout, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, filePart=<null>, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt]
Step: Verify that the client continues to the performing phase.
Step: Send a final response upload message
Result: Received event: c02d48d0: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1
Result: Received event: c02d48d0: 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@27a4a890[correlationID=f6ac1680-d1ad-4816-944e-08515c21bb10, collectionID=SinglePillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=getFileFromOtherCollection, to=Pillar2, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt]
Result: Received event: f6ac1680: 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: f6ac1680: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: f6ac1680: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: f6ac1680: 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@19b5f793[correlationID=f6ac1680-d1ad-4816-944e-08515c21bb10, collectionID=SinglePillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=getFileFromOtherCollection, to=Pillar2, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar2, fileID=default-test-file.txt, filePart=<null>, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt]
Step: Send a complete event from the pillar
Result: Received event: f6ac1680: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2
Result: Received event: f6ac1680: 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@19cc4b7d[correlationID=4ff592f4-834c-443d-bc3c-7ce8f0fbec57, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=getFileFromSpecificPillar, to=Pillar2, version=28, minVersion=24, auditTrailInformation=AuditTrailInfo for getFileFromSpecificPillarTest, fileID=default-test-file.txt]
Result: Received event: 4ff592f4: 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: 4ff592f4: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 4ff592f4: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: 4ff592f4: 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@1d6d1a18[correlationID=4ff592f4-834c-443d-bc3c-7ce8f0fbec57, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=getFileFromSpecificPillar, to=Pillar2, version=28, minVersion=24, auditTrailInformation=AuditTrailInfo for getFileFromSpecificPillarTest, pillarID=Pillar2, fileID=default-test-file.txt, filePart=<null>, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt]
Step: Send a GetFileProgressResponse.
Result: Received event: 4ff592f4: GET_FILE for file default-test-file.txt: PROGRESS: ContributorID Pillar2, First test progress response message
Step: Send a GetFileFinalResponse.
Result: Received event: 4ff592f4: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2
Result: Received event: 4ff592f4: 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@55f2a26d[correlationID=759783a5-694d-4a6d-8e27-fb089623e4b7, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=getFileFromSpecificPillarWithFilePart, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt]
Result: Received event: 759783a5: 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: 759783a5: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 759783a5: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 759783a5: 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@16987824[correlationID=759783a5-694d-4a6d-8e27-fb089623e4b7, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=getFileFromSpecificPillarWithFilePart, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, filePart=org.bitrepository.bitrepositoryelements.FilePart@3f3cacde[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: 759783a5: 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: 759783a5: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1
Result: Received event: 759783a5: 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@19bc42ea[correlationID=658f3e84-6629-4ec1-9bd0-f75b75edac2d, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=noIdentifyResponse, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt]
Result: Received event: 658f3e84: GET_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetFile
Step: Wait for 1 seconds
Result: Received event: 658f3e84: 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: 658f3e84: GET_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor
Result: Received event: 658f3e84: GET_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
Result: Received event: 658f3e84: GET_FILE for file default-test-file.txt: FAILED: , Unable to continue operation, contributors unavailable.
Test success: noIdentifyResponse
Test starting: singleComponentFailureDuringIdentify
Description: Verify that the GetFile reports a complete (not failed), in case of a component failing during the identify phase.
Step: Call getFile from the fastest pillar.
Stimuli: Calling getFileFromFastestPillar(default-test-file.txt, file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileRequest@1bb6b61c[correlationID=d5e4f410-568d-4b6d-9237-05a4064aaec3, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=singleComponentFailureDuringIdentify, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt]
Result: Received event: d5e4f410: 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: d5e4f410: 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: d5e4f410: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: d5e4f410: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: d5e4f410: 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@4e2c656a[correlationID=d5e4f410-568d-4b6d-9237-05a4064aaec3, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=singleComponentFailureDuringIdentify, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar2, fileID=default-test-file.txt, filePart=<null>, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt]
Step: Verify that the client continues to the performing phase.
Step: Send a final response upload message
Result: Received event: d5e4f410: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2
Result: Received event: d5e4f410: 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@ca129b5[correlationID=c63ca31f-40fb-4419-bbfc-daf4591b8116, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=testNoSuchFileMultiplePillars, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileID=ERROR-NO-SUCH-FILE-ERROR]
Result: Received event: c63ca31f: 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: c63ca31f: 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: c63ca31f: 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: c63ca31f: GET_FILE for file ERROR-NO-SUCH-FILE-ERROR: FAILED: , Unable to continue operation, contributors unavailable.
Test success: testNoSuchFileMultiplePillars
Test starting: testNoSuchFileSpecificPillar
Description: Testing how a request for a non-existing file is handled on a specific pillar request.
Step: Define 1 pillar.
Step: Call getFileFromSpecificPillar.
Stimuli: Calling getFileFromSpecificPillar(ERROR-NO-SUCH-FILE-ERROR, file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, Pillar1)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileRequest@5eb8dfd0[correlationID=a8f2c34c-5584-44bf-a5a4-50cc798f459d, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=testNoSuchFileSpecificPillar, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=ERROR-NO-SUCH-FILE-ERROR]
Result: Received event: a8f2c34c: 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: a8f2c34c: 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: a8f2c34c: GET_FILE for file ERROR-NO-SUCH-FILE-ERROR: FAILED: , Unable to continue operation, contributors unavailable.
Test success: testNoSuchFileSpecificPillar
Test starting: verifyGetFileClientFromFactory
Test success: verifyGetFileClientFromFactory
Starting testcase PutFileCmdTest
Test starting: checksumArgumentNonSaltAlgorithmWitoutSaltTest
Description: Test MD5 checksum without salt -> no failure
Test success: checksumArgumentNonSaltAlgorithmWitoutSaltTest
Test starting: checksumArgumentSaltAlgorithmWithSaltTest
Description: Test HMAC_SHA256 checksum with salt -> No failure
Test success: checksumArgumentSaltAlgorithmWithSaltTest
Test starting: defaultSuccessScenarioTest
Description: Tests simplest arguments for running the CmdLineClient
Test success: defaultSuccessScenarioTest
Test starting: missingChecksumWhenFileArgumentTest
Description: Tests the scenario, where no checksum argument is given, but a file is given.
Test success: missingChecksumWhenFileArgumentTest
Test starting: missingChecksumWhenURLArgumentTest
Description: Tests the scenario, where no checksum argument is given, but a URL is given.
Invalid argument: The URL argument requires also the checksum argument (-c).
Test success: missingChecksumWhenURLArgumentTest
Test starting: missingCollectionArgumentTest
Description: Tests the scenario, where the collection arguments is missing.
Takes the following arguments:
-p [OPTIONAL] The id of the pillar where the should be performed. If undefined the operations is performed on all pillars.
-R [OPTIONAL] The algorithm of checksum to request in the response from the pillars.
-s The path to the directory with the settings files for the client
-c The id for the collection to perform the operation on.
-C The checksum for the file to be retreived. Required if using an URL.
-S [OPTIONAL] The salt of checksum to request in the response. Requires the ChecksumType argument.
-d If this argument is present, then the file will be removed from the server, when the operation is complete.
-u The URL for the file to be put. Is required, unless the actual file is given.
-v Makes the client more verbose
-f The path to the file, which is wanted to be put. Is required, unless a URL is given.
-i The id for the file to perform the operation on.
-k The path to the file containing the private key.
Missing argument: c
Test success: missingCollectionArgumentTest
Test starting: missingFileIDWhenFileArgumentTest
Description: Tests the scenario, where no checksum argument is given, but a URL is given.
Test success: missingFileIDWhenFileArgumentTest
Test starting: missingFileIDWhenURLArgumentTest
Description: Tests the scenario, where no checksum argument is given, but a URL is given.
Invalid argument: The URL argument requires also the argument for the ID of the file (-i).
Test success: missingFileIDWhenURLArgumentTest
Test starting: missingFileOrURLArgumentTest
Description: Tests the scenario, where no arguments for file or url is given.
Invalid argument: Requires either the file argument (-f) or the URL argument (-u).
Test success: missingFileOrURLArgumentTest
Test starting: specificPillarArgumentTest
Description: Test argument for a specific pillar
Test success: specificPillarArgumentTest
Test starting: unknownPillarArgumentTest
Description: Testing against a non-existing pillar id -> Should fail
Invalid argument: Random1448068794364pillar 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:
-c The id for the collection to perform the operation on.
-C [OPTIONAL] The checksum of the file to be replaced.
-d If this argument is present, then the file will be removed from the server, when the operation is complete.
-f The path to the new file for the replacement. Required unless using the URL argument.
-i The id for the file to perform the operation on.
-k The path to the file containing the private key.
-p [OPTIONAL] The id of the pillar where the should be performed. If undefined the operations is performed on all pillars.
-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 The path to the directory with the settings files for the client
-S [OPTIONAL] The salt of checksum to request in the response. Requires the ChecksumType argument.
-u The URL for the file to be retreived. Is required, unless the actual file is given.
-v Makes the client more verbose
Missing argument: c
Test success: missingCollectionArgumentTest
Test starting: missingFileIDWhenFileArgumentTest
Description: Tests the scenario, where no checksum argument is given, but a URL is given.
Test success: missingFileIDWhenFileArgumentTest
Test starting: missingFileIDWhenURLArgumentTest
Description: Tests the scenario, where no checksum argument is given, but a URL is given.
Invalid argument: The URL argument requires also the argument for the ID of the file (-i).
Test success: missingFileIDWhenURLArgumentTest
Test starting: missingFileOrURLArgumentTest
Description: Tests the scenario, where no arguments for file or url is given.
Invalid argument: Requires either the file argument (-f) or the URL argument (-u).
Test success: missingFileOrURLArgumentTest
Test starting: 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: Random1448068797194pillar is not a valid pillar for collection TwoPillarCollection
The collection contains the following pillars: [Pillar1, Pillar2]
Test success: unknownPillarArgumentTest
Starting testcase UnexpectedResponseExceptionTest
Test starting: testUnexpectedResponse
Description: Test the instantiation of the exception
Step: Setup
Step: Try to throw such an exception
Step: Throw the exception with an embedded exception
Test success: testUnexpectedResponse
Starting testcase 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: ac3349b4: GET_STATUS: IDENTIFY_REQUEST_SENT: , Identifying contributors for getting status
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetStatusRequest@7751d800[correlationID=ac3349b4-d02d-451d-9190-c0236d1aaf2c, collectionID=<null>, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetStatusClientComponentTest-cibuild01, from=getAllStatuses, to=<null>, version=28, minVersion=24, auditTrailInformation=]
Step: Send a identifyResponse from each pillar
Result: Received event: ac3349b4: GET_STATUS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: ac3349b4: GET_STATUS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: ac3349b4: GET_STATUS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2]
Result: Received event: ac3349b4: GET_STATUS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending GetStatusRequest
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetStatusRequest@2dac8ef8[correlationID=ac3349b4-d02d-451d-9190-c0236d1aaf2c, collectionID=<null>, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetStatusClientComponentTest-cibuild01, from=getAllStatuses, to=<null>, version=28, minVersion=24, auditTrailInformation=, contributor=Pillar1]
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetStatusRequest@6fe0e4a9[correlationID=ac3349b4-d02d-451d-9190-c0236d1aaf2c, collectionID=<null>, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetStatusClientComponentTest-cibuild01, from=getAllStatuses, to=<null>, version=28, minVersion=24, auditTrailInformation=, contributor=Pillar2]
Step: Send a final response from pillar 1
Result: Received event: ac3349b4: GET_STATUS: COMPONENT_COMPLETE: ContributorID Pillar1, resulting status: org.bitrepository.bitrepositoryelements.ResultingStatus@41de65[statusInfo=org.bitrepository.bitrepositoryelements.StatusInfo@1aa96f4f[statusCode=OK, statusText=Everythings fine..], statusTimestamp=2015-11-21T02:19:57.320+01:00]
Step: Send a final response from pillar 2
Result: Received event: ac3349b4: GET_STATUS: COMPONENT_COMPLETE: ContributorID Pillar2, resulting status: org.bitrepository.bitrepositoryelements.ResultingStatus@689e5e35[statusInfo=org.bitrepository.bitrepositoryelements.StatusInfo@1960074f[statusCode=OK, statusText=Everythings fine..], statusTimestamp=2015-11-21T02:19:57.320+01:00]
Result: Received event: ac3349b4: 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: a9e73ed9: GET_STATUS: IDENTIFY_REQUEST_SENT: , Identifying contributors for getting status
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetStatusRequest@524d3f70[correlationID=a9e73ed9-76c7-4fa5-a5c0-36d6a45a0728, collectionID=<null>, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetStatusClientComponentTest-cibuild01, from=incompleteSetOfIdendifyResponses, to=<null>, version=28, minVersion=24, auditTrailInformation=]
Step: Send a identifyResponse from pillar 1
Result: Received event: a9e73ed9: GET_STATUS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Step: Wait for timeout event
Result: Received event: a9e73ed9: GET_STATUS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar2]
Result: Received event: a9e73ed9: GET_STATUS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
Result: Received event: a9e73ed9: GET_STATUS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: a9e73ed9: GET_STATUS: REQUEST_SENT: ContributorID [Pillar1], Sending GetStatusRequest
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetStatusRequest@67414728[correlationID=a9e73ed9-76c7-4fa5-a5c0-36d6a45a0728, collectionID=<null>, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetStatusClientComponentTest-cibuild01, from=incompleteSetOfIdendifyResponses, to=<null>, version=28, minVersion=24, auditTrailInformation=, contributor=Pillar1]
Test success: incompleteSetOfIdendifyResponses
Test starting: verifyGetStatusClientFromFactory
Test success: verifyGetStatusClientFromFactory
Starting testcase ChecksumExtractionUtilsTest
Test starting: testDefaultChecksumSpec
Description: Test that the default checksum is retrieved when no arguments are given.
Test success: testDefaultChecksumSpec
Test starting: testDefaultChecksumSpecWithSaltArgument
Description: Test that the HMAC version of default checksum is retrieved when the salt arguments are given.
Test success: testDefaultChecksumSpecWithSaltArgument
Test starting: testNonSaltChecksumSpecWithSaltArgument
Description: Test that a salt checksum type is retrieved even though a non-salt checksum algorithm it is given as argument, but a salt argument also is given.
Test success: testNonSaltChecksumSpecWithSaltArgument
Test starting: testNonSaltChecksumSpecWithoutSaltArgument
Description: Test that a non-salt checksum type is retrieved when it is given as argument, and no salt arguments are given.
Test success: testNonSaltChecksumSpecWithoutSaltArgument
Test starting: testSaltChecksumSpecWithSaltArgument
Description: Test that a salt checksum type is retrieved when the salt checksum algorithm it is given as argument, and a salt argument also is given.
Test success: testSaltChecksumSpecWithSaltArgument
Test starting: testSaltChecksumSpecWithoutSaltArgument
Description: Test that a non-salt checksum type is retrieved even though a salt checksum algorithm it is given as argument, but no salt argument also is given.
Test success: testSaltChecksumSpecWithoutSaltArgument
Starting testcase 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:
-p [OPTIONAL] The id of the pillar where the should be performed. If undefined the operations is performed on all pillars.
-s The path to the directory with the settings files for the client
-c The id for the collection to perform the operation on.
-v Makes the client more verbose
-i The id for the file to perform the operation on.
-k The path to the file containing the private key.
-l [OPTIONAL] The location where the file should be placed (either total path or directory). If no argument, then in the directory where the script is located.
Missing argument: c
Test success: missingCollectionArgumentTest
Test starting: missingFileIDArgumentTest
Description: Tests the scenario, where no arguments for file id argument is given.
Takes the following arguments:
-p [OPTIONAL] The id of the pillar where the should be performed. If undefined the operations is performed on all pillars.
-s The path to the directory with the settings files for the client
-c The id for the collection to perform the operation on.
-v Makes the client more verbose
-i The id for the file to perform the operation on.
-k The path to the file containing the private key.
-l [OPTIONAL] The location where the file should be placed (either total path or directory). If no argument, then in the directory where the script is located.
Missing argument: 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: Random1448068801113pillar is not a valid pillar for collection TwoPillarCollection
The collection contains the following pillars: [Pillar1, Pillar2]
Test success: unknownPillarArgumentTest
Finished testcase
Finished suite
Finished project
Tests run: 156, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 65.424 sec - in TestSuite
Results :
Tests run: 156, Failures: 0, Errors: 0, Skipped: 0
[JENKINS] Recording test results
[INFO]
[INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ bitrepository-client ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/target/bitrepository-client-1.6-SNAPSHOT.jar
[INFO]
[INFO] --- maven-jar-plugin:2.4:test-jar (default) @ bitrepository-client ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/target/bitrepository-client-1.6-SNAPSHOT-tests.jar
[INFO]
[INFO] --- maven-source-plugin:2.2.1:jar-no-fork (attach-sources-no-fork) @ bitrepository-client ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/target/bitrepository-client-1.6-SNAPSHOT-sources.jar
[INFO]
[INFO] --- maven-assembly-plugin:2.4:single (make-assembly) @ bitrepository-client ---
[INFO] Reading assembly descriptor: src/main/assembly/assembly.xml
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/target/bitrepository-client-1.6-SNAPSHOT-distribution.tar.gz
[INFO]
[INFO] --- maven-install-plugin:2.5.1:install (default-install) @ bitrepository-client ---
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/target/bitrepository-client-1.6-SNAPSHOT.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-client/1.6-SNAPSHOT/bitrepository-client-1.6-SNAPSHOT.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-client/1.6-SNAPSHOT/bitrepository-client-1.6-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/target/bitrepository-client-1.6-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-client/1.6-SNAPSHOT/bitrepository-client-1.6-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/target/bitrepository-client-1.6-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-client/1.6-SNAPSHOT/bitrepository-client-1.6-SNAPSHOT-sources.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/target/bitrepository-client-1.6-SNAPSHOT-distribution.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-client/1.6-SNAPSHOT/bitrepository-client-1.6-SNAPSHOT-distribution.tar.gz
[JENKINS] Archiving disabled
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Service 1.6-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-service ---
[INFO] Deleting /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-service/target
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ bitrepository-service ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 7 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ bitrepository-service ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 53 source files to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-service/target/classes
[INFO]
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ bitrepository-service ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 3 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ bitrepository-service ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 9 source files to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-service/target/test-classes
[INFO]
[INFO] --- maven-surefire-plugin:2.17:test (default-test) @ bitrepository-service ---
[INFO] Surefire report directory: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-service/target/surefire-reports
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running TestSuite
Configuring TestNG with: TestNG652Configurator
Starting test project Core module test
Suite: Surefire suite
Starting testcase IdentifyContributorExceptionTest
Test starting: testIdentifyContributor
Description: Test the instantiation of the exception
Step: Setup
Step: Try to throw such an exception
Step: Throw the exception with an embedded exception
Test success: testIdentifyContributor
Starting testcase InvalidMessageExceptionTest
Test starting: testIdentifyContributor
Description: Test the instantiation of the exception
Step: Setup
Step: Try to throw such an exception
Step: Throw the exception with an embedded exception
Test success: testIdentifyContributor
Starting testcase AuditTrailContributorDatabaseMigrationTest
Test starting: testMigratingAuditContributorDatabase
Description: Tests that the database can be migrated to latest version with the provided scripts.
Step: Validate setup
Step: Ingest a entry to the database without the collection id
Step: Perform migration
02:20:17.368 WARN o.b.service.database.DatabaseUtils - Migrating AuditContributorDB from version 1 to 2.
02:20:17.590 WARN o.b.service.database.DatabaseUtils - Migrating AuditContributorDB from version 2 to 3.
02:20:17.981 WARN o.b.service.database.DatabaseUtils - Migrating AuditContributorDB from version 3 to 4.
Test success: testMigratingAuditContributorDatabase
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 AuditTrailContributorDatabaseTest
Test starting: testAuditTrailDatabaseFunctions
Description: Testing the basic functions of the audit trail database interface.
Step: Setup varibles and the database connection.
Step: Populate the database.
Step: Test extracting all the events
Step: Test extracting the events for fileID1
Step: Test extracting the events for fileID2
Step: Test extracting the events with the sequence number at least equal to the largest sequence number.
Step: Test extracting the events for fileID1 with sequence number 2 or more
Step: Test extracting the events for fileID1 with at most sequence number 2
Step: Test extracting at most 3 events
Step: Test extracting at most 1000 events
Step: Test extracting from another collection
Test success: testAuditTrailDatabaseFunctions
Test starting: testAuditTrailDatabaseIngest
Description: Testing the ingest of data.
Step: Setup varibles and the database connection.
Step: Test with all data.
Step: Test with no collection
Step: Test with with no file id.
Step: Test with with no actor.
Step: Test with with no info.
Step: Test with with no audittrail.
Step: Test with with no operationID.
Step: Test with with no certificateID.
Step: Test with with no action.
Step: Test with with very large file id.
Step: Test with with very large actor name.
Step: Test with with very large info.
Step: Test with with very large audittrail.
Test success: testAuditTrailDatabaseIngest
Test starting: componentIDTest
Test success: componentIDTest
Finished testcase
Finished suite
Finished project
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 8.945 sec - in TestSuite
Results :
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0
[JENKINS] Recording test results
[INFO]
[INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ bitrepository-service ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-service/target/bitrepository-service-1.6-SNAPSHOT.jar
[INFO]
[INFO] --- maven-jar-plugin:2.4:test-jar (default) @ bitrepository-service ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-service/target/bitrepository-service-1.6-SNAPSHOT-tests.jar
[INFO]
[INFO] --- maven-source-plugin:2.2.1:jar-no-fork (attach-sources-no-fork) @ bitrepository-service ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-service/target/bitrepository-service-1.6-SNAPSHOT-sources.jar
[INFO]
[INFO] --- maven-install-plugin:2.5.1:install (default-install) @ bitrepository-service ---
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-service/target/bitrepository-service-1.6-SNAPSHOT.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-service/1.6-SNAPSHOT/bitrepository-service-1.6-SNAPSHOT.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-service/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-service/1.6-SNAPSHOT/bitrepository-service-1.6-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-service/target/bitrepository-service-1.6-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-service/1.6-SNAPSHOT/bitrepository-service-1.6-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-service/target/bitrepository-service-1.6-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-service/1.6-SNAPSHOT/bitrepository-service-1.6-SNAPSHOT-sources.jar
[JENKINS] Archiving disabled
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Integrity Service 1.6-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-integrity-service ---
[INFO] Deleting /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integrity-service/target
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ bitrepository-integrity-service ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 12 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ bitrepository-integrity-service ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 63 source files to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integrity-service/target/classes
[INFO]
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ bitrepository-integrity-service ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 3 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ bitrepository-integrity-service ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 21 source files to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integrity-service/target/test-classes
[INFO]
[INFO] --- maven-surefire-plugin:2.17:test (default-test) @ bitrepository-integrity-service ---
[INFO] Surefire report directory: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integrity-service/target/surefire-reports
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running TestSuite
Configuring TestNG with: TestNG652Configurator
Starting test project Integration Service Test
Suite: Surefire suite
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
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 IntegrityDAOTest
Test starting: initialStateExtractionTest
Description: Tests the initial state of the IntegrityModel. Should not contain any data.
02:20:41.053 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:20:41.061 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Test success: initialStateExtractionTest
Test starting: instantiationTest
Description: Testing the connection to the integrity database.
02:20:44.778 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:20:44.784 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Test success: instantiationTest
Test starting: reinitialiseDatabaseTest
Description: Testing the connection to the integrity database.
Step: Setup manually.
02:20:47.917 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:20:47.929 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Step: Close the connection and create another one.
Test success: reinitialiseDatabaseTest
Test starting: testDeletingEntry
Description: Tests the deletion of an FileID entry from a collection. Checks that it does not effect another collection with a fileID equal to the deleted
02:20:52.266 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:20:52.277 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Step: Create data
Step: Ensure that the data is present
Step: Delete the entry for the first pillar
Step: Delete the entry for the second pillar
Step: Check that the data in the extra collection is still present
Test success: testDeletingEntry
Test starting: testDeletingNonExistingEntry
Description: Tests the deletion of an nonexisting FileID entry.
02:20:56.253 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:20:56.256 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Step: Create data
Step: Delete a nonexisting entry
Test success: testDeletingNonExistingEntry
Test starting: testExtractCollectionFileSize
Description: Tests that the accumulated size of the collection can be extracted
02:21:00.164 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:21:00.171 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Step: Insert test data into database
Step: Check the reported size of the first pillar in the collection
Step: Check the reported size of the second pillar in the collection
Step: Check the reported size of the whole collection
Test success: testExtractCollectionFileSize
Test starting: testExtractingAllKnownFilesForPillars
Description: Tests that known files can be extracted for specific pillars.
02:21:02.408 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:21:02.425 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Step: Insert two files into database for a pillar
Step: Insert a file to the extra collection for the common pillar
Step: Extract all the existing file ids for the pillar for collection 'TwoPillarCollection'
Step: Extract the single fileID for the extra collection
Step: Extract all the existing file ids for another pillar
Test success: testExtractingAllKnownFilesForPillars
Test starting: testExtractingAllKnownFilesForPillarsLimits
Description: Tests the limits for extracting files for specific pillars.
02:21:06.039 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:21:06.046 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Step: Insert two files into database for a pillar
Step: Extract with a maximum of 1
Step: Extract with a minimum of 1 and maximum of infinite
Test success: testExtractingAllKnownFilesForPillarsLimits
Test starting: testExtractingAllMissingFilesForPillars
Description: Tests that missing files can be extracted for specific pillars.
02:21:08.296 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:21:08.302 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Step: Insert two files into database for a pillar and mark them as missing
Step: Check the number of files in collection and on pillars
Step: Extract missing files from the first pillar
Step: Extract missing files from the second pillar
Test success: testExtractingAllMissingFilesForPillars
Test starting: testExtractingAllMissingFilesForPillarsLimits
Description: Tests the limits for extracting missing files for specific pillars.
02:21:10.847 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:21:10.858 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Step: Insert two files into database for a pillar and set them to missing
Step: Extract with a maximum of 1
Step: Extract with a minimum of 1 and maximum of infinite
Test success: testExtractingAllMissingFilesForPillarsLimits
Test starting: testFindInconsistentChecksum
Description: Testing the localization of inconsistent checksums
02:21:13.141 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:21:13.142 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Step: Update the database with 2 inconsistent files and one consistent file.
Step: Find the files with inconsistent checksums
Test success: testFindInconsistentChecksum
Test starting: testFindOrphanFiles
Description: Tests the ability to find orphan files.
02:21:15.998 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:21:15.999 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Step: Create data
Test success: testFindOrphanFiles
Test starting: testGetLatestChecksumDateEntryForCollection
Description: Tests that checksum date entries can be retrieved and manipulated.
02:21:19.102 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:21:19.102 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Step: Create data
Test success: testGetLatestChecksumDateEntryForCollection
Test starting: testGetLatestFileDateEntryForCollection
Description: Tests that checksum date entries can be retrieved and manipulated.
02:21:21.494 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:21:21.495 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Step: Create data
Test success: testGetLatestFileDateEntryForCollection
Test starting: testIngestOfChecksumsData
Description: Tests the ingesting of checksums data
02:21:24.721 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:21:24.722 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Step: Create data
Step: Extract the data
Step: Check that the extra collection is untouched by the ingest
Test success: testIngestOfChecksumsData
Test starting: testIngestOfFileIDsData
Description: Tests the ingesting of file ids data
02:21:25.964 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:21:25.967 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Step: Create data
Step: Extract the data
Step: Check that the extra collection is untouched by the ingest
Test success: testIngestOfFileIDsData
Test starting: testMissingChecksums
Description: Testing the checksum validation, when only one pillar has a checksum for a file.
02:21:28.858 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:21:28.860 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Step: Update the database with 1 file, missing its checksum on one pillar.
Step: Finding the files with inconsistent checksums
Test success: testMissingChecksums
Test starting: testMissingChecksumsChecksumNotUpdated
Description: Testing the checksum validation, when only one pillar has a checksum for a file.
02:21:31.111 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:21:31.113 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Step: Update the database with 1 file, no missing checksums.
Step: Finding the files with inconsistent checksums
Step: Updating the checksum for one pillar, and checking that the other pillars checksum is now missing
Step: Finding the files with inconsistent checksums
Test success: testMissingChecksumsChecksumNotUpdated
Test starting: testNoChecksums
Description: Testing the checksum validation, when no checksums exists.
02:21:33.633 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:21:33.640 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Step: Update the database with 2 inconsistent files and one consistent file.
Step: Finding the files with inconsistent checksums
Test success: testNoChecksums
Test starting: testOutdatedChecksums
Description: Testing the checksum validation, when only one pillar has a checksum for a file.
02:21:35.525 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:21:35.527 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Step: Update the database with one file, one pillar having an outdated checksum.
Step: Finding the files with inconsistent checksums
Test success: testOutdatedChecksums
Starting testcase 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 HandleChecksumValidationStepTest
Test starting: testAuditTrailsForChecksumErrors
Description: Test audit trails for checksum errors. Verify that a pillar with a single checksum will be pointed out as the possible cause.
02:21:38.845 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:21:38.847 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Step: Test step on data without checksum error
Step: Test step on data where only two pillars have the file and they disagree about the checksum.
number of files in the collection2
number of fileinfos: 3
Step: remove the last auditinfo
Step: Test step on data where two pillars have one checksum and the last pillar has a different one
Test success: testAuditTrailsForChecksumErrors
Test starting: testChecksumMajority
Description: Test the checksum integrity validator when two pillars have one checksum and the last pillar has another checksum.
02:21:41.380 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:21:41.382 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Step: Add data to the cache
Step: Perform the checksum validation step
Step: Validate the file ids
Test success: testChecksumMajority
Test starting: testMissingAtOnePillar
Description: Test the checksum integrity validator when one pillar is missing the data.
02:21:44.103 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:21:44.106 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Step: Update the cache with identitical data for both pillars.
Step: Perform the step
Step: Validate the file ids
Test success: testMissingAtOnePillar
Test starting: testNoData
Description: Test the checksum integrity validator without any data in the cache.
02:21:46.036 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:21:46.037 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Step: Validate the file ids
Test success: testNoData
Test starting: testSimilarData
Description: Test the checksum integrity validator when all pillars have similar data.
02:21:48.021 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:21:48.022 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Step: Add data to the cache
Step: Perform the step
Step: Validate the file ids
Test success: testSimilarData
Test starting: testThreeDisagreeingChecksums
Description: Test the checksum integrity validator when all pillars have different checksums.
02:21:49.223 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:21:49.226 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Step: Add data to the cache
Step: Perform the step
Step: Validate the file ids
Test success: testThreeDisagreeingChecksums
Test starting: testTwoDisagreeingChecksums
Description: Test the checksum integrity validator when only two pillar has data, but it it different.
02:21:50.879 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:21:50.880 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Step: Add data to the cache
Step: Perform the step
Step: Validate the file ids
Test success: testTwoDisagreeingChecksums
Starting testcase IntegrityAlerterTest
Test starting: testIntegrityFailed
Description: Test the IntegrityFailed method for the IntegrityAlerter
Step: Call the function for integrity failure.
02:21:52.314 WARN o.b.i.a.IntegrityAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@1f9e42d2[origDateTime=2015-11-21T02:21:52.313+01:00, alarmCode=INTEGRITY_ISSUE, alarmRaiser=IntegrityAlerterTest, alarmText=Testaintegrity alarm, fileID=<null>, collectionID=TwoPillarCollection]
Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@1a6aecec[correlationID=a95f63b7-dcc9-43e3-8c8f-afa72a1d22c1, collectionID=TwoPillarCollection, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-IntegrityAlerterTest-cibuild01-contributor, from=IntegrityAlerterTest, to=<null>, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@1f9e42d2[origDateTime=2015-11-21T02:21:52.313+01:00, alarmCode=INTEGRITY_ISSUE, alarmRaiser=IntegrityAlerterTest, alarmText=Testaintegrity alarm, fileID=<null>, collectionID=TwoPillarCollection]]
Test success: testIntegrityFailed
Test starting: testOperationFailed
Description: Test the OperationFailed method for the IntegrityAlerter
Step: Call the function for integrity failure.
02:21:54.568 WARN o.b.i.a.IntegrityAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@57064d38[origDateTime=2015-11-21T02:21:54.567+01:00, alarmCode=FAILED_OPERATION, alarmRaiser=IntegrityAlerterTest, alarmText=Testing the ability to fail., fileID=<null>, collectionID=TwoPillarCollection]
Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@2667a238[correlationID=bcf8ee40-7ebb-4904-ad1a-fb66fa2c5628, collectionID=TwoPillarCollection, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-IntegrityAlerterTest-cibuild01-contributor, from=IntegrityAlerterTest, to=<null>, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@57064d38[origDateTime=2015-11-21T02:21:54.567+01:00, alarmCode=FAILED_OPERATION, alarmRaiser=IntegrityAlerterTest, alarmText=Testing the ability to fail., fileID=<null>, collectionID=TwoPillarCollection]]
Test success: testOperationFailed
Starting testcase IntegrityDatabaseTest
Test starting: initialStateExtractionTest
Description: Tests the initial state of the IntegrityModel. Should not contain any data.
02:21:56.397 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:21:56.398 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Step: Test the 'findChecksumsOlderThan'
Step: Test the 'findMissingChecksums'
Step: Test the 'findMissingFiles'
Step: Test the 'getAllFileIDs'
Step: Test the 'getFileInfos'
Step: Test the 'getNumberOfFiles'
Test success: initialStateExtractionTest
Test starting: instantiationTest
Description: Tests that the connection can be instantaited.
02:21:57.634 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:21:57.635 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Test success: instantiationTest
Test starting: testDeletingEntry
Description: Tests the deletion of an FileID entry.
02:21:58.581 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:21:58.585 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Step: Create data
Step: Delete the entry
Test success: testDeletingEntry
Test starting: testIngestOfChecksumsData
Description: Tests the ingesting of checksums data
02:21:59.680 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:21:59.681 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Step: Create data
Step: Extract the data
Test success: testIngestOfChecksumsData
Test starting: testIngestOfFileIDsData
Description: Tests the ingesting of file ids data
02:22:01.461 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:22:01.462 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Step: Create data
Step: Extract the data
Test success: testIngestOfFileIDsData
Starting testcase 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 IntegrityDBToolsTest
Test starting: testAddCollectionSuccess
Description: Tests that a new collection can be added to the integrity database
02:22:03.742 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:22:03.744 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Step: Extract initial list of collections
Step: Add the new collection
Test success: testAddCollectionSuccess
Test starting: testAddExistingCollection
Description: Tests that an existing collectionID cannot be added to the integrity database.
02:22:04.819 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:22:04.827 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Step: Extract initial list of collections.
Step: Attempt to add the new collection.
Test success: testAddExistingCollection
Test starting: testRemoveNonExistingCollection
Description: Tests that a non existing collection can't be removed from the integrity database.
02:22:06.441 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:22:06.442 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Step: Extract initial list of collections.
Step: Attempt to remove the non-existing collection.
Test success: testRemoveNonExistingCollection
Starting testcase 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 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: 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 FailingGetChecksumClient for test purpose.
Step: Verify that the collector does not fail, just because the GetChecksumClient does so
02:22:06.498 ERROR o.b.i.c.DelegatingIntegrityInformationCollector - Unexpected failure!
java.lang.RuntimeException: My purpose is to die!
at org.bitrepository.integrityservice.collector.IntegrityInformationCollectorTest$DyingGetChecksumClient.getChecksums(IntegrityInformationCollectorTest.java:151) ~[test-classes/:na]
at org.bitrepository.integrityservice.collector.DelegatingIntegrityInformationCollector.getChecksums(DelegatingIntegrityInformationCollector.java:77) ~[classes/:na]
at org.bitrepository.integrityservice.collector.IntegrityInformationCollectorTest.testCollectorHandleChecksumClientFailures(IntegrityInformationCollectorTest.java:144) [test-classes/:na]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_11]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_11]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_11]
at java.lang.reflect.Method.invoke(Method.java:483) ~[na:1.8.0_11]
at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84) [testng-6.8.8.jar:na]
at org.testng.internal.Invoker.invokeMethod(Invoker.java:714) [testng-6.8.8.jar:na]
at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901) [testng-6.8.8.jar:na]
at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231) [testng-6.8.8.jar:na]
at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127) [testng-6.8.8.jar:na]
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111) [testng-6.8.8.jar:na]
at org.testng.TestRunner.privateRun(TestRunner.java:767) [testng-6.8.8.jar:na]
at org.testng.TestRunner.run(TestRunner.java:617) [testng-6.8.8.jar:na]
at org.testng.SuiteRunner.runTest(SuiteRunner.java:348) [testng-6.8.8.jar:na]
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:343) [testng-6.8.8.jar:na]
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:305) [testng-6.8.8.jar:na]
at org.testng.SuiteRunner.run(SuiteRunner.java:254) [testng-6.8.8.jar:na]
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) [testng-6.8.8.jar:na]
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) [testng-6.8.8.jar:na]
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1224) [testng-6.8.8.jar:na]
at org.testng.TestNG.runSuitesLocally(TestNG.java:1149) [testng-6.8.8.jar:na]
at org.testng.TestNG.run(TestNG.java:1057) [testng-6.8.8.jar:na]
at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:115) [surefire-testng-2.17.jar:2.17]
at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:204) [surefire-testng-2.17.jar:2.17]
at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:107) [surefire-testng-2.17.jar:2.17]
at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:112) [surefire-testng-2.17.jar:2.17]
at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) [surefire-booter-2.17.jar:2.17]
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) [surefire-booter-2.17.jar:2.17]
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) [surefire-booter-2.17.jar:2.17]
Test success: testCollectorHandleChecksumClientFailures
Test starting: testCollectorHandleGetFileIDsClientFailures
Description: Test that the IntegrityInformationCollector works as a fault-barrier.
Step: Setup variables for the test
Step: Setup a FailingGetChecksumClient for test purpose.
Step: Verify that the collector does not fail, just because the GetChecksumClient does so
02:22:06.500 ERROR o.b.i.c.DelegatingIntegrityInformationCollector - Unexpected failure!
java.lang.RuntimeException: My purpose is to die!
at org.bitrepository.integrityservice.collector.IntegrityInformationCollectorTest$DyingGetFileIDsClient.getFileIDs(IntegrityInformationCollectorTest.java:179) ~[test-classes/:na]
at org.bitrepository.integrityservice.collector.DelegatingIntegrityInformationCollector.getFileIDs(DelegatingIntegrityInformationCollector.java:66) ~[classes/:na]
at org.bitrepository.integrityservice.collector.IntegrityInformationCollectorTest.testCollectorHandleGetFileIDsClientFailures(IntegrityInformationCollectorTest.java:171) [test-classes/:na]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_11]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_11]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_11]
at java.lang.reflect.Method.invoke(Method.java:483) ~[na:1.8.0_11]
at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84) [testng-6.8.8.jar:na]
at org.testng.internal.Invoker.invokeMethod(Invoker.java:714) [testng-6.8.8.jar:na]
at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901) [testng-6.8.8.jar:na]
at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231) [testng-6.8.8.jar:na]
at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127) [testng-6.8.8.jar:na]
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111) [testng-6.8.8.jar:na]
at org.testng.TestRunner.privateRun(TestRunner.java:767) [testng-6.8.8.jar:na]
at org.testng.TestRunner.run(TestRunner.java:617) [testng-6.8.8.jar:na]
at org.testng.SuiteRunner.runTest(SuiteRunner.java:348) [testng-6.8.8.jar:na]
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:343) [testng-6.8.8.jar:na]
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:305) [testng-6.8.8.jar:na]
at org.testng.SuiteRunner.run(SuiteRunner.java:254) [testng-6.8.8.jar:na]
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) [testng-6.8.8.jar:na]
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) [testng-6.8.8.jar:na]
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1224) [testng-6.8.8.jar:na]
at org.testng.TestNG.runSuitesLocally(TestNG.java:1149) [testng-6.8.8.jar:na]
at org.testng.TestNG.run(TestNG.java:1057) [testng-6.8.8.jar:na]
at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:115) [surefire-testng-2.17.jar:2.17]
at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:204) [surefire-testng-2.17.jar:2.17]
at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:107) [surefire-testng-2.17.jar:2.17]
at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:112) [surefire-testng-2.17.jar:2.17]
at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) [surefire-booter-2.17.jar:2.17]
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) [surefire-booter-2.17.jar:2.17]
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) [surefire-booter-2.17.jar:2.17]
Test success: testCollectorHandleGetFileIDsClientFailures
Starting testcase UpdateChecksumsStepTest
Test starting: testAbortWorkflowWhenNegativeReply
Description: Test the step for updating the checksums will abort the workflow in case of FAILURE operation event and AbortOnFailedContributor = true .
02:22:06.644 WARN o.b.i.c.IntegrityCollectorEventHandler - Component failure for 'test-pillar-1'.
02:22:06.645 WARN o.b.i.c.IntegrityCollectorEventHandler - Failure: null: null: FAILED: , Problem encountered
Test success: testAbortWorkflowWhenNegativeReply
Test starting: testCallForChangingChecksumStates
Description: Test the step for updating the checksums delivers the results to the integrity model.
Test success: testCallForChangingChecksumStates
Test starting: testContinueWorkflowNegativeReply
Description: Test the step for updating the checksums will continue the workflow in case of FAILURE operation event and AbortOnFailedContributor = false .
02:22:06.914 WARN o.b.i.c.IntegrityCollectorEventHandler - Component failure for 'test-pillar-1'.
02:22:06.915 WARN o.b.i.c.IntegrityCollectorEventHandler - Failure: null: null: FAILED: , Problem encountered
Test success: testContinueWorkflowNegativeReply
Test starting: testFullChecksumCollection
Description: Test that the full list of checksums is requested.
Test success: testFullChecksumCollection
Test starting: testIncrementalChecksumCollection
Description: Test that only the list of new checksums is requested.
Test success: testIncrementalChecksumCollection
Test starting: testIngestOfResults
Description: Test the step for updating the checksums delivers the results to the integrity model.
Test success: testIngestOfResults
Test starting: testPartialResults
Description: Test that the number of partial is used for generating more than one request.
Step: Setup the collector mock to generate a isPartialResult=true event the first time and a isPartialResult=false the second time
Test success: testPartialResults
Test starting: testPositiveReply
Description: Test the step for updating the checksums can handle COMPLETE operation event.
Test success: testPositiveReply
Test starting: testRetryCollectionWhenNegativeReply
Description: Test the step for updating the file ids will retry on a FAILED event
02:22:07.728 WARN o.b.i.c.IntegrityCollectorEventHandler - Component failure for 'test-pillar-1'.
02:22:07.728 WARN o.b.i.c.IntegrityCollectorEventHandler - Failure: null: null: FAILED: , Problem encountered
Test success: testRetryCollectionWhenNegativeReply
Starting testcase UpdateFileIDsStepTest
Test starting: testAbortWorkflowWhenNegativeReply
Description: Test the step for updating the file ids will throw an WorkflowAbortedExceptionwhen AbortOnFailedContributor is set to true and a FAILED event is received.
02:22:08.565 WARN o.b.i.c.IntegrityCollectorEventHandler - Component failure for 'test-pillar-1'.
02:22:08.565 WARN o.b.i.c.IntegrityCollectorEventHandler - Failure: null: null: FAILED: , Operation failed
Test success: testAbortWorkflowWhenNegativeReply
Test starting: testContinueWorkflowWhenNegativeReply
Description: Test the step for updating the file ids will continue when getting an FAILED operation event when AbortOnFailedContributor is set to false
02:22:08.630 WARN o.b.i.c.IntegrityCollectorEventHandler - Component failure for 'test-pillar-1'.
02:22:08.630 WARN o.b.i.c.IntegrityCollectorEventHandler - Failure: null: null: FAILED: , Operation failed
Test success: testContinueWorkflowWhenNegativeReply
Test starting: testIngestOfResults
Description: Test the step for updating the file ids can ingest the data correctly into the store.
Test success: testIngestOfResults
Test starting: testPartialResults
Description: Test that the number of partial is used for generating more than one request.
Step: Setup the collector mock to generate a isPartialResult=true event the first time and a isPartialResult=false the second time
Test success: testPartialResults
Test starting: testPositiveReply
Description: Test the step for updating the file ids can handle COMPLETE operation event.
Test success: testPositiveReply
Test starting: testRetryCollectionWhenNegativeReply
Description: Test the step for updating the file ids will retry on a FAILED event
02:22:08.952 WARN o.b.i.c.IntegrityCollectorEventHandler - Component failure for 'test-pillar-1'.
02:22:08.953 WARN o.b.i.c.IntegrityCollectorEventHandler - Failure: null: null: FAILED: , Operation failed
Test success: testRetryCollectionWhenNegativeReply
Finished testcase
Finished suite
Finished project
Tests run: 78, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 100.253 sec - in TestSuite
Results :
Tests run: 78, Failures: 0, Errors: 0, Skipped: 0
[JENKINS] Recording test results
[INFO]
[INFO] --- maven-war-plugin:2.4:war (default-war) @ bitrepository-integrity-service ---
[INFO] Packaging webapp
[INFO] Assembling webapp [bitrepository-integrity-service] in [/home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integrity-service/target/bitrepository-integrity-service-1.6-SNAPSHOT]
[INFO] Processing war project
[INFO] Copying webapp resources [/home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integrity-service/src/main/webapp]
[INFO] Webapp assembled in [576 msecs]
[INFO] Building war: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integrity-service/target/bitrepository-integrity-service-1.6-SNAPSHOT.war
[INFO]
[INFO] --- maven-jar-plugin:2.4:test-jar (default) @ bitrepository-integrity-service ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integrity-service/target/bitrepository-integrity-service-1.6-SNAPSHOT-tests.jar
[INFO]
[INFO] --- maven-source-plugin:2.2.1:jar-no-fork (attach-sources-no-fork) @ bitrepository-integrity-service ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integrity-service/target/bitrepository-integrity-service-1.6-SNAPSHOT-sources.jar
[INFO]
[INFO] --- maven-assembly-plugin:2.4:single (distribution) @ bitrepository-integrity-service ---
[INFO] Reading assembly descriptor: src/main/assembly/assembly.xml
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integrity-service/target/bitrepository-integrity-service-1.6-SNAPSHOT-distribution.tar.gz
[INFO]
[INFO] --- maven-install-plugin:2.5.1:install (default-install) @ bitrepository-integrity-service ---
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integrity-service/target/bitrepository-integrity-service-1.6-SNAPSHOT.war to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integrity-service/1.6-SNAPSHOT/bitrepository-integrity-service-1.6-SNAPSHOT.war
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integrity-service/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integrity-service/1.6-SNAPSHOT/bitrepository-integrity-service-1.6-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integrity-service/target/bitrepository-integrity-service-1.6-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integrity-service/1.6-SNAPSHOT/bitrepository-integrity-service-1.6-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integrity-service/target/bitrepository-integrity-service-1.6-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integrity-service/1.6-SNAPSHOT/bitrepository-integrity-service-1.6-SNAPSHOT-sources.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integrity-service/target/bitrepository-integrity-service-1.6-SNAPSHOT-distribution.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integrity-service/1.6-SNAPSHOT/bitrepository-integrity-service-1.6-SNAPSHOT-distribution.tar.gz
[JENKINS] Archiving disabled
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Alarm Service 1.6-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-alarm-service ---
[INFO] Deleting /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-alarm-service/target
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ bitrepository-alarm-service ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 5 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ bitrepository-alarm-service ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 26 source files to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-alarm-service/target/classes
[INFO]
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ bitrepository-alarm-service ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ bitrepository-alarm-service ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 6 source files to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-alarm-service/target/test-classes
[INFO]
[INFO] --- maven-surefire-plugin:2.17:test (default-test) @ bitrepository-alarm-service ---
[INFO] Surefire report directory: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-alarm-service/target/surefire-reports
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running TestSuite
Configuring TestNG with: TestNG652Configurator
Starting test project Alarm Service Test
Suite: Surefire suite
Starting testcase 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 AlarmHandlerTest
Test starting: alarmMediatorTest
Description: Test the mediator handling of alarm messages.
Step: Setup mediator and create alarm handler.
Step: Try giving it a non-alarm message
02:22:24.347 WARN o.b.alarm.handling.AlarmMediator - Recieved unexpected message: 'org.bitrepository.bitrepositorymessages.Message@6e6f2380[correlationID=<null>, collectionID=<null>, destination=<null>, replyTo=<null>, from=<null>, to=<null>, version=<null>, minVersion=<null>]'
Step: Giv the mediator an AlarmMessage
Step: Close the mediator.
Test success: alarmMediatorTest
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
Step: Cleanup after test.
Finished testcase
Finished suite
Finished project
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 20.562 sec - in TestSuite
Results :
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0
[JENKINS] Recording test results
[INFO]
[INFO] --- maven-war-plugin:2.4:war (default-war) @ bitrepository-alarm-service ---
[INFO] Packaging webapp
[INFO] Assembling webapp [bitrepository-alarm-service] in [/home/cibuild01/workspace/Bitrepository-sonar/bitrepository-alarm-service/target/bitrepository-alarm-service-1.6-SNAPSHOT]
[INFO] Processing war project
[INFO] Copying webapp resources [/home/cibuild01/workspace/Bitrepository-sonar/bitrepository-alarm-service/src/main/webapp]
[INFO] Webapp assembled in [266 msecs]
[INFO] Building war: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-alarm-service/target/bitrepository-alarm-service-1.6-SNAPSHOT.war
[INFO]
[INFO] --- maven-jar-plugin:2.4:test-jar (default) @ bitrepository-alarm-service ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-alarm-service/target/bitrepository-alarm-service-1.6-SNAPSHOT-tests.jar
[INFO]
[INFO] --- maven-source-plugin:2.2.1:jar-no-fork (attach-sources-no-fork) @ bitrepository-alarm-service ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-alarm-service/target/bitrepository-alarm-service-1.6-SNAPSHOT-sources.jar
[INFO]
[INFO] --- maven-assembly-plugin:2.4:single (distribution) @ bitrepository-alarm-service ---
[INFO] Reading assembly descriptor: src/main/assembly/assembly.xml
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-alarm-service/target/bitrepository-alarm-service-1.6-SNAPSHOT-distribution.tar.gz
[INFO]
[INFO] --- maven-install-plugin:2.5.1:install (default-install) @ bitrepository-alarm-service ---
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-alarm-service/target/bitrepository-alarm-service-1.6-SNAPSHOT.war to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-alarm-service/1.6-SNAPSHOT/bitrepository-alarm-service-1.6-SNAPSHOT.war
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-alarm-service/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-alarm-service/1.6-SNAPSHOT/bitrepository-alarm-service-1.6-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-alarm-service/target/bitrepository-alarm-service-1.6-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-alarm-service/1.6-SNAPSHOT/bitrepository-alarm-service-1.6-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-alarm-service/target/bitrepository-alarm-service-1.6-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-alarm-service/1.6-SNAPSHOT/bitrepository-alarm-service-1.6-SNAPSHOT-sources.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-alarm-service/target/bitrepository-alarm-service-1.6-SNAPSHOT-distribution.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-alarm-service/1.6-SNAPSHOT/bitrepository-alarm-service-1.6-SNAPSHOT-distribution.tar.gz
[JENKINS] Archiving disabled
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Audit Trail Service 1.6-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-audit-trail-service ---
[INFO] Deleting /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-audit-trail-service/target
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ bitrepository-audit-trail-service ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 9 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ bitrepository-audit-trail-service ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 23 source files to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-audit-trail-service/target/classes
[INFO]
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ bitrepository-audit-trail-service ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 3 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ bitrepository-audit-trail-service ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 11 source files to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-audit-trail-service/target/test-classes
[INFO]
[INFO] --- maven-surefire-plugin:2.17:test (default-test) @ bitrepository-audit-trail-service ---
[INFO] Surefire report directory: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-audit-trail-service/target/surefire-reports
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running TestSuite
Configuring TestNG with: TestNG652Configurator
Starting test project Core module test
Suite: Surefire suite
Starting testcase AuditCollectorTest
Test starting: auditCollectorIntervalTest
Description: Test that the collector calls the AuditClient at the correct intervals.
02:22:52.041 WARN o.b.a.collector.IncrementalCollector - Received bad collection id! Expected 'TwoPillarCollection', but got 'dummy-collection'.
02:22:53.065 WARN o.b.a.collector.IncrementalCollector - Received bad collection id! Expected 'TwoPillarCollection', but got 'dummy-collection'.
Test success: auditCollectorIntervalTest
Starting testcase AuditServiceDatabaseMigrationTest
Test starting: testMigratingAuditServiceDatabase
Description: Tests that the database can be migrated to latest version with the provided scripts.
Step: Validate setup
Step: Perform migration
02:22:57.208 WARN o.b.service.database.DatabaseUtils - Migrating AuditServiceDB from version 2 to 3.
02:22:57.896 WARN o.b.service.database.DatabaseUtils - Migrating AuditServiceDB from version 3 to 4.
02:22:58.099 WARN o.b.service.database.DatabaseUtils - Migrating AuditServiceDB from version 4 to 5.
Test success: testMigratingAuditServiceDatabase
Starting testcase AuditDatabaseTest
Test starting: AuditDatabaseExtractionTest
Description: Testing the connection to the audit trail service database especially with regards to extracting the data from it.
Step: Setup the variables and constants.
Step: Adds the variables to the settings and instantaites the database cache
Step: Validate that the database is empty and then populate it.
Step: Extract the audit trails
Step: Test the extraction of FileID
Step: Test the extraction of CollectionID
Step: Perform extraction based on the component id.
Step: Perform extraction based on the sequence number restriction
Step: Perform extraction based on actor id restriction.
Step: Perform extraction based on operation restriction.
Step: Perform extraction based on date restriction.
Step: Perform extraction based on fingerprint restriction.
Step: Perform extraction based on operationID restriction.
Test success: AuditDatabaseExtractionTest
Test starting: AuditDatabaseGoodIngestTest
Description: Testing good case ingest of audittrails into the database
Step: Adds the variables to the settings and instantaites the database cache
Step: Build test data
Test success: AuditDatabaseGoodIngestTest
Test starting: AuditDatabaseIngestTest
Description: Testing ingest of audittrails into the database
Step: Adds the variables to the settings and instantaites the database cache
Step: Test ingesting with all data
Step: Test ingesting with no timestamp
Step: Test ingesting with no file action
Step: Test ingesting with no actor
Step: Test ingesting with no audit info
Step: Test ingesting with no file id
Step: Test ingesting with no info
Step: Test ingesting with no component id
Step: Test ingesting with no sequence number
Step: Test ingest with very long auditInfo (255+)
Step: Test ingest with very long info (255+)
Test success: AuditDatabaseIngestTest
Test starting: AuditDatabasePreservationTest
Description: Tests the functions related to the preservation of the database.
Step: Adds the variables to the settings and instantaites the database cache
Step: Validate the preservation sequence number
Step: Validate the insertion of the preservation sequence number
Test success: AuditDatabasePreservationTest
Starting testcase 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 AuditPreservationEventHandlerTest
Test starting: auditPreservationEventHandlerTest
Description: Test the handling of the audit trail event handler.
Step: Setup
Step: Test the handling of another complete event.
Test success: auditPreservationEventHandlerTest
Starting testcase IncrementalCollectorTest
Test starting: collectionIdFailureTest
Description: Tests what happens when a wrong collection id is received.
Step:
Step: Start a collection with two contributors
Step: Send an auditTrail result from contributor 1 with a wrong collection id.
02:23:16.257 WARN o.b.a.collector.IncrementalCollector - Received bad collection id! Expected 'dummy-collection', but got 'FalseCollection1448068996143'.
Test success: collectionIdFailureTest
Test starting: contributorFailureTest
Description: Tests that the collector is able to collect from the remaining contributors if a contributor fails.
Step:
Step: Start a collection with two contributors
Step: Send a audit trail result from contributor 2 with the PartialResults boolean set to true and a failed event from contributor 1
02:23:16.379 WARN o.b.a.collector.IncrementalCollector - Event: null: null: COMPONENT_FAILED: ContributorID Contributor1 ResponseCode: REQUEST_NOT_SUPPORTED
02:23:16.380 WARN o.b.a.collector.IncrementalCollector - Event: null: null: FAILED: ,
02:23:16.385 ERROR o.b.a.collector.IncrementalCollector - Problem in collecting audittrails, collection will not be complete for collection 'dummy-collection'
org.bitrepository.client.exceptions.NegativeResponseException:
at org.bitrepository.access.getaudittrails.BlockingAuditTrailClient.getAuditTrails(BlockingAuditTrailClient.java:61) ~[bitrepository-client-1.6-SNAPSHOT.jar:1.6-SNAPSHOT]
at org.bitrepository.audittrails.collector.IncrementalCollector.collect(IncrementalCollector.java:135) [classes/:na]
at org.bitrepository.audittrails.collector.IncrementalCollector.performCollection(IncrementalCollector.java:112) [classes/:na]
at org.bitrepository.audittrails.collector.IncrementalCollectorTest$CollectionRunner.run(IncrementalCollectorTest.java:288) [test-classes/:na]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_11]
Step: Send another audit trail result from contributor 2 with PartialResults set to false
Test success: contributorFailureTest
Test starting: multipleIncrementTest
Description: Verifies the behaviour in the case where the adit trails needs to be reteived in multiple requests because of MaxNumberOfResults limits.
Step: Start a collection with two contributors
Step: Send a audit trail result from contributor 1 and 2 with the PartialResults boolean set to true
Step: Send another audit trail result from the contributors, now with PartialResults set to false
Test success: multipleIncrementTest
Test starting: singleIncrementTest
Description: Verifies the behaviour in the simplest case with just one result set
Step: Start a collection with two contributors
Step: Send a audit trail result from contributor 1
Step: Send a audit trail result from contributor 2
Test success: singleIncrementTest
Finished testcase
Finished suite
Finished project
Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 28.792 sec - in TestSuite
Results :
Tests run: 12, Failures: 0, Errors: 0, Skipped: 0
[JENKINS] Recording test results
[INFO]
[INFO] --- maven-war-plugin:2.4:war (default-war) @ bitrepository-audit-trail-service ---
[INFO] Packaging webapp
[INFO] Assembling webapp [bitrepository-audit-trail-service] in [/home/cibuild01/workspace/Bitrepository-sonar/bitrepository-audit-trail-service/target/bitrepository-audit-trail-service-1.6-SNAPSHOT]
[INFO] Processing war project
[INFO] Copying webapp resources [/home/cibuild01/workspace/Bitrepository-sonar/bitrepository-audit-trail-service/src/main/webapp]
[INFO] Webapp assembled in [96 msecs]
[INFO] Building war: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-audit-trail-service/target/bitrepository-audit-trail-service-1.6-SNAPSHOT.war
[INFO]
[INFO] --- maven-jar-plugin:2.4:test-jar (default) @ bitrepository-audit-trail-service ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-audit-trail-service/target/bitrepository-audit-trail-service-1.6-SNAPSHOT-tests.jar
[INFO]
[INFO] --- maven-source-plugin:2.2.1:jar-no-fork (attach-sources-no-fork) @ bitrepository-audit-trail-service ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-audit-trail-service/target/bitrepository-audit-trail-service-1.6-SNAPSHOT-sources.jar
[INFO]
[INFO] --- maven-assembly-plugin:2.4:single (distribution) @ bitrepository-audit-trail-service ---
[INFO] Reading assembly descriptor: src/main/assembly/assembly.xml
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-audit-trail-service/target/bitrepository-audit-trail-service-1.6-SNAPSHOT-distribution.tar.gz
[INFO]
[INFO] --- maven-install-plugin:2.5.1:install (default-install) @ bitrepository-audit-trail-service ---
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-audit-trail-service/target/bitrepository-audit-trail-service-1.6-SNAPSHOT.war to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-audit-trail-service/1.6-SNAPSHOT/bitrepository-audit-trail-service-1.6-SNAPSHOT.war
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-audit-trail-service/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-audit-trail-service/1.6-SNAPSHOT/bitrepository-audit-trail-service-1.6-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-audit-trail-service/target/bitrepository-audit-trail-service-1.6-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-audit-trail-service/1.6-SNAPSHOT/bitrepository-audit-trail-service-1.6-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-audit-trail-service/target/bitrepository-audit-trail-service-1.6-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-audit-trail-service/1.6-SNAPSHOT/bitrepository-audit-trail-service-1.6-SNAPSHOT-sources.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-audit-trail-service/target/bitrepository-audit-trail-service-1.6-SNAPSHOT-distribution.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-audit-trail-service/1.6-SNAPSHOT/bitrepository-audit-trail-service-1.6-SNAPSHOT-distribution.tar.gz
[JENKINS] Archiving disabled
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Reference Pillar 1.6-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-reference-pillar ---
[INFO] Deleting /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target
[INFO]
[INFO] --- maven-dependency-plugin:2.8:unpack-dependencies (unpack-shared-sqlscripts) @ bitrepository-reference-pillar ---
[INFO] Unpacking /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-service/target/bitrepository-service-1.6-SNAPSHOT.jar to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/classes with includes "**/*.sql" and excludes ""
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ bitrepository-reference-pillar ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 10 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ bitrepository-reference-pillar ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 44 source files to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/classes
[INFO]
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ bitrepository-reference-pillar ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 12 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ bitrepository-reference-pillar ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 70 source files to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/test-classes
[INFO]
[INFO] --- maven-surefire-plugin:2.17:test (default-test) @ bitrepository-reference-pillar ---
[INFO] Surefire report directory: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/surefire-reports
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running TestSuite
Configuring TestNG with: TestNG652Configurator
Starting test project Reference Pillar Test
Suite: Surefire suite
Starting testcase ArchiveDirectoryTest
Test starting: testArchiveDirectoryExistingFile
Description: Test the ArchiveDirectory when the file exists
Step: Setup
Step: Validate the existence of the file
Step: Delete the file.
Test success: testArchiveDirectoryExistingFile
Test starting: testArchiveDirectoryMissingFile
Description: Test the ArchiveDirectory when the file is missing.
Step: Setup
Step: Validate the existence of the file
Step: Delete the file.
Test success: testArchiveDirectoryMissingFile
Test starting: testArchiveDirectoryMoveFileToArchive
Description: Testing the error scenarios when moving a file from tmp to archive for the ArchiveDirectory.
Step: Setup
Step: Moving file from tmp to archive
Step: Create file in both tmp and archive.
Step: Moving file from tmp to archive
Step: Remove the file from archive and try again
Test success: testArchiveDirectoryMoveFileToArchive
Test starting: testArchiveDirectoryNewFile
Description: Testing the ArchiveDirectory handling of a new file.
Step: Setup
Step: Retrieve tmp file
Step: Request a new file for the tmp dir
Step: Retrieve tmp file
Step: Request another new file with the same name
Step: Move the file from tmp to archive
Test success: testArchiveDirectoryNewFile
Test starting: testArchiveDirectoryRemoveFile
Description: Testing the error scenarios when removing files from the archive.
Step: Setup
Step: Remove nonexisting file from archive
Step: Remove nonexisting file from tmp
Step: Create file in both tmp, archive and retain directories.
Step: Remove the file from archive and tmp
Test success: testArchiveDirectoryRemoveFile
Starting testcase 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 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@47da3952[correlationID=4f2cf200-f270-4ea2-8f88-67c43698dec5, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseIdentification-cibuild01-contributor, from=Pillar-badCaseIdentification, to=badCaseIdentification, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@51e4ccb3[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], fileID=DefaultFilebadCaseIdentification, pillarID=Pillar-badCaseIdentification, pillarChecksumSpec=<null>, timeToDeliver=<null>]
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@6c451c9c[correlationID=fb6603e8-8a21-4a72-b65b-59cb4c292c4e, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationMissingVerification-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationMissingVerification-cibuild01-contributor, from=Pillar-badCaseOperationMissingVerification, to=badCaseOperationMissingVerification, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@31c269fd[responseCode=EXISTING_FILE_CHECKSUM_FAILURE, responseText=No mandatory checksum for destructive operation was supplied.], pillarID=Pillar-badCaseOperationMissingVerification, fileID=DefaultFilebadCaseOperationMissingVerification, checksumDataForExistingFile=<null>]
02:23:38.279 WARN o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@47747fb9[origDateTime=2015-11-21T02:23:38.279+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCaseOperationMissingVerification, alarmText=No mandatory checksum for destructive operation was supplied., fileID=DefaultFilebadCaseOperationMissingVerification, collectionID=TwoPillarCollection]
Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@3113a37[correlationID=96c9c136-5751-4c18-8b06-d52e9f32cf39, collectionID=TwoPillarCollection, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationMissingVerification-cibuild01-contributor, from=Pillar-badCaseOperationMissingVerification, to=<null>, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@47747fb9[origDateTime=2015-11-21T02:23:38.279+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCaseOperationMissingVerification, alarmText=No mandatory checksum for destructive operation was supplied., fileID=DefaultFilebadCaseOperationMissingVerification, collectionID=TwoPillarCollection]]
Step: Retrieve the FinalResponse for the DeleteFile request
Step: Pillar should have sent an alarm
Test success: badCaseOperationMissingVerification
Added fixture: Initialize a new Pillar.
Test starting: badCaseOperationNoFile
Description: Tests the DeleteFile functionality of the pillar for the failure scenario, where it does not have the file.
Step: Set up constants and variables.
Step: Setup for delivering pillar id and not having the file
Step: Create and send the actual DeleteFile message to the pillar.
Result: Received message on TEST-TOPIC-badCaseOperationNoFile-cibuild01 : org.bitrepository.bitrepositorymessages.DeleteFileFinalResponse@2c30b71f[correlationID=3629e22d-a607-4a9e-b019-e6df11baa151, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@1d81e101[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileID=DefaultFilebadCaseOperationNoFile, checksumDataForExistingFile=<null>]
Step: Retrieve the FinalResponse for the DeleteFile request
Test success: badCaseOperationNoFile
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@64f555e7[correlationID=9a6d47c8-1f15-4c3e-8a9a-eb487d858f32, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseIdentification-cibuild01-contributor, from=Pillar-goodCaseIdentification, to=goodCaseIdentification, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@71178a52[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], fileID=DefaultFilegoodCaseIdentification, pillarID=Pillar-goodCaseIdentification, pillarChecksumSpec=<null>, timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@ff6077[timeMeasureUnit=MILLISECONDS, timeMeasureValue=1000]]
Step: Retrieve and validate the response getPillarID() the pillar.
Test success: goodCaseIdentification
Starting testcase FullPillarModelTest
Test starting: testPillarModelBasicFunctionality
Description: Test the basic functions of the full reference pillar model.
Step: Check the pillar id in the pillar model
Step: Ask whether it can handle a file of size 0
Step: Ask whether it can handle a file of maximum size
Step: Check the ChecksumPillarSpec
Test success: testPillarModelBasicFunctionality
Test starting: testPillarModelHasFile
Description: Test that the file exists, when placed in the archive and cache
Step: Setup
Step: Check whether file exists and retrieve it.
Step: Verify that no exceptions are thrown when verifying file existance.
Step: Check retrieval of non-default checksum
Test success: testPillarModelHasFile
Test starting: testPillarModelNoFile
Description: Test that the file exists, when placed in the archive and cache
Step: Setup
Step: Check whether file exists and try to retrieve it.
Step: Verify that anexceptions are thrown when verifying file existance.
02:23:45.104 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@54d8c20d[correlationID=b041becf-af72-434b-a579-f560bc2b5909, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsMaximumNumberOfResults-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults, to=Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@4b65d9f4[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to extract the requested audit trails.], contributor=Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults, resultAddress=<null>]
Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsMaximumNumberOfResults-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsFinalResponse@4d21c56e[correlationID=b041becf-af72-434b-a579-f560bc2b5909, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsMaximumNumberOfResults-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults, to=Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@726aa968[responseCode=OPERATION_COMPLETED, responseText=<null>], contributor=Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@7100dea[resultAddress=<null>, auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@712cfb63[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@32e54a9d[sequenceNumber=1, fileID=fileId1448069025386, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=CHECKSUM_CALCULATED, actionDateTime=2015-11-21T02:23:45.388+01:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@15639440[sequenceNumber=2, fileID=fileId1448069025386, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=DELETE_FILE, actionDateTime=2015-11-21T02:23:45.388+01:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@121bb45b[sequenceNumber=3, fileID=fileId1448069025386, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=FAILURE, actionDateTime=2015-11-21T02:23:45.388+01:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@4faa298[sequenceNumber=4, fileID=fileId1448069025386, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=FILE_MOVED, actionDateTime=2015-11-21T02:23:45.389+01:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@1cd3b138[sequenceNumber=5, fileID=fileId1448069025386, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=GET_CHECKSUMS, actionDateTime=2015-11-21T02:23:45.389+01:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails]}]], partialResult=true]
Step: Validate the final response
Test success: checksumPillarGetAuditTrailsMaximumNumberOfResults
Added fixture: Initialize a new Pillar.
Test starting: checksumPillarGetAuditTrailsSpecificRequests
Description: Tests the GetAuditTrails functionality of the pillar for the successful scenario, where a specific audit trail are requested.
Step: Set up constants and variables.
Step: Send the identification request
Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsResponse@a4b5ce3[correlationID=6f6d2ad5-ef35-41a3-ab15-5e3e489c52ba, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSpecificRequests-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSpecificRequests, to=Pillar-checksumPillarGetAuditTrailsSpecificRequests, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@f5b6e78[responseCode=IDENTIFICATION_POSITIVE, responseText=<null>]]
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@71926a36[correlationID=6f6d2ad5-ef35-41a3-ab15-5e3e489c52ba, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSpecificRequests-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSpecificRequests, to=Pillar-checksumPillarGetAuditTrailsSpecificRequests, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@216e9ca3[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to extract the requested audit trails.], contributor=Pillar-checksumPillarGetAuditTrailsSpecificRequests, resultAddress=<null>]
Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsFinalResponse@75120e58[correlationID=6f6d2ad5-ef35-41a3-ab15-5e3e489c52ba, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSpecificRequests-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSpecificRequests, to=Pillar-checksumPillarGetAuditTrailsSpecificRequests, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@48976e6d[responseCode=OPERATION_COMPLETED, responseText=<null>], contributor=Pillar-checksumPillarGetAuditTrailsSpecificRequests, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@2a367e93[resultAddress=<null>, auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@7f6874f2[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@1a6dc589[sequenceNumber=1, fileID=fileId1448069026084, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=OTHER, actionDateTime=2015-11-21T02:23:46.084+01:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails]}]], partialResult=false]
Step: Receive and validate the progress response.
Step: Receive and validate the final response
Step: Make another request, where both ingested audit trails is requested
Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsProgressResponse@697a34af[correlationID=6f6d2ad5-ef35-41a3-ab15-5e3e489c52ba, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSpecificRequests-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSpecificRequests, to=Pillar-checksumPillarGetAuditTrailsSpecificRequests, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@70211df5[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to extract the requested audit trails.], contributor=Pillar-checksumPillarGetAuditTrailsSpecificRequests, resultAddress=<null>]
Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsFinalResponse@4c5228e7[correlationID=6f6d2ad5-ef35-41a3-ab15-5e3e489c52ba, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSpecificRequests-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSpecificRequests, to=Pillar-checksumPillarGetAuditTrailsSpecificRequests, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@38e7ed69[responseCode=OPERATION_COMPLETED, responseText=<null>], contributor=Pillar-checksumPillarGetAuditTrailsSpecificRequests, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@806996[resultAddress=<null>, auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@78b612c6[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@1a6dc589[sequenceNumber=1, fileID=fileId1448069026084, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=OTHER, actionDateTime=2015-11-21T02:23:46.084+01:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@257e0827[sequenceNumber=2, fileID=notThisFile, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=UnknownActor, actionOnFile=FAILURE, actionDateTime=2015-11-21T02:23:46.084+01:00, info=badInfo, operationID=operationID, certificateID=certificateid, auditTrailInformation=WrongAuditTrail]}]], partialResult=false]
Step: Receive and validate the progress response.
Step: Receive and validate the final response
Test success: checksumPillarGetAuditTrailsSpecificRequests
Added fixture: Initialize a new Pillar.
Test starting: checksumPillarGetAuditTrailsSuccessful
Description: Tests the GetAuditTrails functionality of the pillar for the successful scenario, where all audit trails are requested.
Step: Set up constants and variables.
Step: Send the identification request
Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSuccessful-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsResponse@1c7350b0[correlationID=b40a8bf3-3841-4a8b-970e-81a50b55502a, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSuccessful-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSuccessful-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSuccessful, to=Pillar-checksumPillarGetAuditTrailsSuccessful, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@55651434[responseCode=IDENTIFICATION_POSITIVE, responseText=<null>]]
Step: Make and send the request for the actual GetAuditTrails operation
Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSuccessful-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsProgressResponse@3bc4ef12[correlationID=b40a8bf3-3841-4a8b-970e-81a50b55502a, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSuccessful-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSuccessful-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSuccessful, to=Pillar-checksumPillarGetAuditTrailsSuccessful, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@50448409[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to extract the requested audit trails.], contributor=Pillar-checksumPillarGetAuditTrailsSuccessful, resultAddress=<null>]
Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSuccessful-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsFinalResponse@5634a861[correlationID=b40a8bf3-3841-4a8b-970e-81a50b55502a, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSuccessful-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSuccessful-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSuccessful, to=Pillar-checksumPillarGetAuditTrailsSuccessful, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@2b0dc227[responseCode=OPERATION_COMPLETED, responseText=<null>], contributor=Pillar-checksumPillarGetAuditTrailsSuccessful, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@37ad042b[resultAddress=<null>, auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@43bdaa1b[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@30b975ad[sequenceNumber=1, fileID=fileid, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=actor, actionOnFile=OTHER, actionDateTime=2015-11-21T02:23:46.680+01:00, info=info, operationID=operationID, certificateID=certificateID, auditTrailInformation=auditTrail]}]], partialResult=false]
Step: Receive and validate the progress response.
Step: Receive and validate the final response
Test success: checksumPillarGetAuditTrailsSuccessful
Starting testcase MediatorTest
Test starting: testMediatorRuntimeExceptionHandling
Description: Tests the handling of a runtime exception
Step: Setup create and start the mediator.
Step: Send a request to the mediator.
02:23:47.982 WARN o.b.pillar.MediatorTest$TestMediator - Unexpected exception caught.
java.lang.RuntimeException: I am supposed to throw a RuntimeException
at org.bitrepository.pillar.MediatorTest$ErroneousRequestHandler.processRequest(MediatorTest.java:122) ~[test-classes/:na]
at org.bitrepository.pillar.MediatorTest$ErroneousRequestHandler.processRequest(MediatorTest.java:113) ~[test-classes/:na]
at org.bitrepository.pillar.messagehandler.PillarMediator.handleRequest(PillarMediator.java:76) ~[classes/:na]
at org.bitrepository.service.contributor.AbstractContributorMediator$GeneralRequestHandler.onMessage(AbstractContributorMediator.java:101) [bitrepository-service-1.6-SNAPSHOT.jar:1.6-SNAPSHOT]
at org.bitrepository.protocol.messagebus.SimpleMessageBus.lambda$sendMessage$0(SimpleMessageBus.java:48) [bitrepository-core-1.6-SNAPSHOT.jar:1.6-SNAPSHOT]
at org.bitrepository.protocol.messagebus.SimpleMessageBus$$Lambda$1/2044825144.accept(Unknown Source) [bitrepository-core-1.6-SNAPSHOT.jar:1.6-SNAPSHOT]
at java.lang.Iterable.forEach(Iterable.java:75) [na:1.8.0_11]
at org.bitrepository.protocol.messagebus.SimpleMessageBus.sendMessage(SimpleMessageBus.java:48) [bitrepository-core-1.6-SNAPSHOT.jar:1.6-SNAPSHOT]
at org.bitrepository.pillar.MediatorTest.testMediatorRuntimeExceptionHandling(MediatorTest.java:84) [test-classes/:na]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_11]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_11]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_11]
at java.lang.reflect.Method.invoke(Method.java:483) ~[na:1.8.0_11]
at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84) [testng-6.8.8.jar:na]
at org.testng.internal.Invoker.invokeMethod(Invoker.java:714) [testng-6.8.8.jar:na]
at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901) [testng-6.8.8.jar:na]
at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231) [testng-6.8.8.jar:na]
at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127) [testng-6.8.8.jar:na]
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111) [testng-6.8.8.jar:na]
at org.testng.TestRunner.privateRun(TestRunner.java:767) [testng-6.8.8.jar:na]
at org.testng.TestRunner.run(TestRunner.java:617) [testng-6.8.8.jar:na]
at org.testng.SuiteRunner.runTest(SuiteRunner.java:348) [testng-6.8.8.jar:na]
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:343) [testng-6.8.8.jar:na]
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:305) [testng-6.8.8.jar:na]
at org.testng.SuiteRunner.run(SuiteRunner.java:254) [testng-6.8.8.jar:na]
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) [testng-6.8.8.jar:na]
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) [testng-6.8.8.jar:na]
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1224) [testng-6.8.8.jar:na]
at org.testng.TestNG.runSuitesLocally(TestNG.java:1149) [testng-6.8.8.jar:na]
at org.testng.TestNG.run(TestNG.java:1057) [testng-6.8.8.jar:na]
at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:115) [surefire-testng-2.17.jar:2.17]
at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:204) [surefire-testng-2.17.jar:2.17]
at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:107) [surefire-testng-2.17.jar:2.17]
at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:112) [surefire-testng-2.17.jar:2.17]
at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) [surefire-booter-2.17.jar:2.17]
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) [surefire-booter-2.17.jar:2.17]
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) [surefire-booter-2.17.jar:2.17]
Result: Received message on TEST-TOPIC-testMediatorRuntimeExceptionHandling-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetStatusResponse@631cb129[correlationID=5fb73490-0631-40e2-b6dd-7afc74aed2da, collectionID=TwoPillarCollection, destination=TEST-TOPIC-testMediatorRuntimeExceptionHandling-cibuild01, replyTo=TEST-TOPIC-MediatorUnderTest-cibuild01-contributor, from=MediatorUnderTest, to=MediatorUnderTest, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@3d20e575[responseCode=FAILURE, responseText=java.lang.RuntimeException: I am supposed to throw a RuntimeException], contributor=TEST-TOPIC-cibuild01, timeToDeliver=<null>]
02:23:48.008 WARN o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@2b4b96a4[origDateTime=2015-11-21T02:23:48.006+01:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MediatorUnderTest, alarmText=java.lang.RuntimeException: I am supposed to throw a RuntimeException, fileID=<null>, collectionID=<null>]
Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@2dd8ff1d[correlationID=669e4a10-8489-474f-aac0-af4f117da629, collectionID=<null>, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-MediatorUnderTest-cibuild01-contributor, from=MediatorUnderTest, to=<null>, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@2b4b96a4[origDateTime=2015-11-21T02:23:48.006+01:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MediatorUnderTest, alarmText=java.lang.RuntimeException: I am supposed to throw a RuntimeException, fileID=<null>, collectionID=<null>]]
Test success: testMediatorRuntimeExceptionHandling
Test starting: componentIDTest
Test success: componentIDTest
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
Starting testcase ReferenceArchiveTest
Added fixture: Initialize the Reference pillar cache with an empty file in default collection TwoPillarCollection
Test starting: testReferenceArchive
Description: Test the ReferenceArchive.
Step: Setup
Step: test 'hasFile'
Step: Test 'getFile'
Step: Test getAllFileIDs
Step: Test 'getFileAsInputstream'
Step: Delete, recreate and delete again
Step: Try to delete missing file.
Step: Replace a file, which does not exist in the filedir.
Step: Copy a file into the tmpDir and then use replace.
Step: Try performing the replace, when the file in the tempdir has been removed.
Test success: testReferenceArchive
Starting testcase 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@2f2e4bde[correlationID=375c1e6f-dc06-47b7-b6b3-0d78efedd6b9, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseIdentification-cibuild01-contributor, from=Pillar-badCaseIdentification, to=badCaseIdentification, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@6222391a[responseCode=FILE_NOT_FOUND_FAILURE, responseText=Could not find the requested file to delete.], fileID=DefaultFile, pillarID=Pillar-badCaseIdentification, pillarChecksumSpec=<null>, timeToDeliver=<null>]
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@4f811029[correlationID=ea09d454-042a-4a2f-a297-c16c831b6572, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationMissingFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationMissingFile-cibuild01-contributor, from=Pillar-badCaseOperationMissingFile, to=badCaseOperationMissingFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@7f2b584b[responseCode=FILE_NOT_FOUND_FAILURE, responseText=The file 'DefaultFile' has been requested, but we do not have that file!], pillarID=Pillar-badCaseOperationMissingFile, pillarChecksumSpec=<null>, fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForExistingFile=<null>, checksumDataForNewFile=<null>]
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@383cdd4d[correlationID=8cec7681-ab0a-41e4-8a1e-c6fb6f3e5204, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoDestructiveChecksum-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoDestructiveChecksum-cibuild01-contributor, from=Pillar-badCaseOperationNoDestructiveChecksum, to=badCaseOperationNoDestructiveChecksum, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@65036e8d[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>, fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForExistingFile=<null>, checksumDataForNewFile=<null>]
02:23:54.975 WARN o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@48ccbb32[origDateTime=2015-11-21T02:23:54.974+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCaseOperationNoDestructiveChecksum, alarmText=According to the contract a checksum for file to be deleted during the replacing operation is required., fileID=DefaultFile, collectionID=TwoPillarCollection]
Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@36551e97[correlationID=ea303244-287b-4c7e-b4d4-327a97fd9d0d, collectionID=TwoPillarCollection, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoDestructiveChecksum-cibuild01-contributor, from=Pillar-badCaseOperationNoDestructiveChecksum, to=<null>, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@48ccbb32[origDateTime=2015-11-21T02:23:54.974+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCaseOperationNoDestructiveChecksum, alarmText=According to the contract a checksum for file to be deleted during the replacing operation is required., fileID=DefaultFile, collectionID=TwoPillarCollection]]
Step: Retrieve the FinalResponse for the ReplaceFile request
Step: Pillar should have sent an alarm
Test success: badCaseOperationNoDestructiveChecksum
Added fixture: Initialize a new Pillar.
Test starting: badCaseOperationNoValidationChecksum
Description: Tests the ReplaceFile operation on the pillar for the failure scenario, when no validation checksum is given for the new file, but though is required.
Step: Set up constants and variables.
Step: Setup for having the file and delivering pillar id
Step: Create and send the identify request message.
Result: Received message on TEST-TOPIC-badCaseOperationNoValidationChecksum-cibuild01 : org.bitrepository.bitrepositorymessages.ReplaceFileFinalResponse@77ccded4[correlationID=ed74d4e9-2f7e-40a7-86a7-c7ef6c7c6335, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoValidationChecksum-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoValidationChecksum-cibuild01-contributor, from=Pillar-badCaseOperationNoValidationChecksum, to=badCaseOperationNoValidationChecksum, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@64c8fcfb[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>, fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForExistingFile=<null>, checksumDataForNewFile=<null>]
02:23:55.291 WARN o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@21be14c2[origDateTime=2015-11-21T02:23:55.291+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCaseOperationNoValidationChecksum, alarmText=According to the contract a checksum for new file in the replacing operation is required., fileID=DefaultFile, collectionID=TwoPillarCollection]
Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@19105a87[correlationID=0dadeb30-bd0f-49f4-9326-bce63362a448, collectionID=TwoPillarCollection, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoValidationChecksum-cibuild01-contributor, from=Pillar-badCaseOperationNoValidationChecksum, to=<null>, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@21be14c2[origDateTime=2015-11-21T02:23:55.291+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCaseOperationNoValidationChecksum, alarmText=According to the contract a checksum for new file in the replacing operation is required., fileID=DefaultFile, collectionID=TwoPillarCollection]]
Step: Retrieve the FinalResponse for the ReplaceFile request
Step: Pillar should have sent an alarm
Test success: badCaseOperationNoValidationChecksum
Added fixture: Initialize a new Pillar.
Test starting: badCaseOperationWrongDestructiveChecksum
Description: Tests the ReplaceFile operation on the pillar for the failure scenario, when the checksum for the destructive action is different from the one in the cache.
Step: Set up constants and variables.
Step: Setup for having the file and delivering pillar id
Step: Create and send the identify request message.
02:23:55.787 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@30cafd13[correlationID=6f2e897d-72bd-46bb-b042-1e0bf343ee33, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationWrongDestructiveChecksum-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationWrongDestructiveChecksum-cibuild01-contributor, from=Pillar-badCaseOperationWrongDestructiveChecksum, to=badCaseOperationWrongDestructiveChecksum, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@1d226f27[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>, fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForExistingFile=<null>, checksumDataForNewFile=<null>]
02:23:55.790 WARN o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@1d944fc0[origDateTime=2015-11-21T02:23:55.790+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCaseOperationWrongDestructiveChecksum, alarmText=Requested to replace the file 'DefaultFile' with checksum '1234cccccccc4321', but our file had a different checksum., fileID=DefaultFile, collectionID=TwoPillarCollection]
Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@7c3c453b[correlationID=e1b28fb4-4487-4013-ac88-a2e304a937a8, collectionID=TwoPillarCollection, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationWrongDestructiveChecksum-cibuild01-contributor, from=Pillar-badCaseOperationWrongDestructiveChecksum, to=<null>, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@1d944fc0[origDateTime=2015-11-21T02:23:55.790+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCaseOperationWrongDestructiveChecksum, alarmText=Requested to replace the file 'DefaultFile' with checksum '1234cccccccc4321', but our file had a different checksum., fileID=DefaultFile, collectionID=TwoPillarCollection]]
Step: Retrieve the FinalResponse for the ReplaceFile request
Step: Pillar should have sent an alarm
Test success: badCaseOperationWrongDestructiveChecksum
Added fixture: Initialize a new Pillar.
Test starting: goodCaseIdentification
Description: Tests the identification for a ReplaceFile operation on the pillar for the successful scenario.
Step: Set up constants and variables.
Step: Setup for having the file and delivering pillar id
Step: Create and send the identify request message.
Result: Received message on TEST-TOPIC-goodCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileResponse@42ecc554[correlationID=943f004a-0ca8-4ffd-be0f-77e865f9cb4c, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseIdentification-cibuild01-contributor, from=Pillar-goodCaseIdentification, to=goodCaseIdentification, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@443af394[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], fileID=DefaultFile, pillarID=Pillar-goodCaseIdentification, pillarChecksumSpec=<null>, timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@734f8317[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@271e851e[correlationID=f23153aa-aec5-4fde-875c-3f10ab67f0c4, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperation-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperation-cibuild01-contributor, from=Pillar-goodCaseOperation, to=goodCaseOperation, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@ff21443[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Performing the ReplaceFileRequest for file 'DefaultFile' at 'TwoPillarCollection'.], pillarID=Pillar-goodCaseOperation, pillarChecksumSpec=<null>, 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@31b6b0c7[correlationID=f23153aa-aec5-4fde-875c-3f10ab67f0c4, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperation-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperation-cibuild01-contributor, from=Pillar-goodCaseOperation, to=goodCaseOperation, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@6253e59a[responseCode=OPERATION_COMPLETED, responseText=<null>], pillarID=Pillar-goodCaseOperation, pillarChecksumSpec=<null>, fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForExistingFile=<null>, checksumDataForNewFile=<null>]
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@7cdc4070[correlationID=ec9f11c7-84d7-4ff2-8bf2-981cbdb3f84e, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationWithChecksumsReturn-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationWithChecksumsReturn-cibuild01-contributor, from=Pillar-goodCaseOperationWithChecksumsReturn, to=goodCaseOperationWithChecksumsReturn, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@553fbe94[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Performing the ReplaceFileRequest for file 'DefaultFile' at 'TwoPillarCollection'.], pillarID=Pillar-goodCaseOperationWithChecksumsReturn, pillarChecksumSpec=<null>, 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@6abe62bb[correlationID=ec9f11c7-84d7-4ff2-8bf2-981cbdb3f84e, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationWithChecksumsReturn-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationWithChecksumsReturn-cibuild01-contributor, from=Pillar-goodCaseOperationWithChecksumsReturn, to=goodCaseOperationWithChecksumsReturn, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@1f60824e[responseCode=OPERATION_COMPLETED, responseText=<null>], pillarID=Pillar-goodCaseOperationWithChecksumsReturn, pillarChecksumSpec=<null>, fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@1218e12[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@29c25bbc[checksumType=HMAC_SHA512, checksumSalt={97,98}, otherChecksumType=<null>], checksumValue={18,52,-52,-52,-52,-52,67,34}, calculationTimestamp=2015-11-21T02:23:59.342+01:00], checksumDataForNewFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@30704f85[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2b99c937[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2015-11-21T02:23:59.345+01:00]]
Step: Retrieve the ProgressResponse for the GetFileIDs request
Step: Retrieve the FinalResponse for the ReplaceFile request
Test success: goodCaseOperationWithChecksumsReturn
Starting testcase ChecksumEntryTest
Test starting: testExtendedTestCase
Description: Test the ChecksumEntry
Step: Create a ChecksumEntry
Step: Change the value of the checksum
Step: Change the value of the calculation date
Test success: testExtendedTestCase
Starting testcase GeneralMessageHandlingTest
Added fixture: Initialize a new Pillar.
Test starting: testPillarMessageHandler
Description: Test the handling of the PillarMessageHandler super-class.
Step: Setup
Step: Test the pillar ID
Test success: testPillarMessageHandler
Starting testcase 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@707f4647[correlationID=54716f33-892f-43ba-8552-a24598d733e3, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseIdentification-cibuild01-contributor, from=Pillar-badCaseIdentification, to=badCaseIdentification, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@4b8a0d03[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@54f373d4[fileID=DefaultFilebadCaseIdentification, allFileIDs=<null>], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1c53bd49[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], pillarID=Pillar-badCaseIdentification, pillarChecksumSpec=<null>, timeToDeliver=<null>]
Step: Retrieve and validate the response getPillarID() the pillar.
Test success: badCaseIdentification
Added fixture: Initialize a new Pillar.
Test starting: badCaseOperationNoFile
Description: Tests the GetChecksums functionality of the pillar for the failure scenario, where it does not have the file.
Step: Set up constants and variables.
Step: Setup for not having the file
Step: Create and send the actual GetChecksums message to the pillar.
02:24:03.494 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@a7ae340[correlationID=381a1643-fa42-4519-bd89-3a68a516fc7c, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@5e8bd498[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@335972a5[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], resultingChecksums=<null>, partialResult=<null>]
02:24:03.517 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@4b00d59[correlationID=381a1643-fa42-4519-bd89-3a68a516fc7c, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@7c048b30[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@335972a5[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], resultingChecksums=<null>, partialResult=<null>]
Step: Retrieve the FinalResponse for the GetChecksums request
Test success: badCaseOperationNoFile
Result: The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@4b00d59[correlationID=381a1643-fa42-4519-bd89-3a68a516fc7c, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@7c048b30[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@335972a5[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], resultingChecksums=<null>, partialResult=<null>]
02:24:04.539 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@4b00d59[correlationID=381a1643-fa42-4519-bd89-3a68a516fc7c, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@7c048b30[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@335972a5[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], resultingChecksums=<null>, partialResult=<null>]
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@69d021c1[correlationID=349475ea-e723-4030-a5a2-06d49d352d05, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseIdentification-cibuild01-contributor, from=Pillar-goodCaseIdentification, to=goodCaseIdentification, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@6d5508a5[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@103bcc9f[fileID=DefaultFilegoodCaseIdentification, allFileIDs=<null>], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@106802ea[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], pillarID=Pillar-goodCaseIdentification, pillarChecksumSpec=<null>, timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@785ef70f[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@3e55d844[correlationID=4783c33f-bb05-4124-a9f6-5512655055f3, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationAllFiles-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationAllFiles-cibuild01-contributor, from=Pillar-goodCaseOperationAllFiles, to=goodCaseOperationAllFiles, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@1f521c69[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to calculate checksums.], pillarID=Pillar-goodCaseOperationAllFiles, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@2b3abeeb[fileID=<null>, allFileIDs=true], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@3aeb267[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], resultAddress=<null>]
Result: Received message on TEST-TOPIC-goodCaseOperationAllFiles-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@146fa9c0[correlationID=4783c33f-bb05-4124-a9f6-5512655055f3, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationAllFiles-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationAllFiles-cibuild01-contributor, from=Pillar-goodCaseOperationAllFiles, to=goodCaseOperationAllFiles, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@49f6c25e[responseCode=OPERATION_COMPLETED, responseText=<null>], pillarID=Pillar-goodCaseOperationAllFiles, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@3aeb267[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], resultingChecksums=org.bitrepository.bitrepositoryelements.ResultingChecksums@6c13019c[resultAddress=<null>, checksumDataItems={org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@2e66f1bd[fileID=DefaultFile, checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2015-11-21T02:24:06.606+01:00],org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@47ae6c18[fileID=goodCaseOperationAllFiles-cibuild01--Test-File-1448069046596, 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@215c6ec0[correlationID=16d56894-7e25-4098-9873-79b2ed70085e, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationSingleFile-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationSingleFile-cibuild01-contributor, from=Pillar-goodCaseOperationSingleFile, to=goodCaseOperationSingleFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@2b19b346[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to calculate checksums.], pillarID=Pillar-goodCaseOperationSingleFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@37c5b8e8[fileID=DefaultFilegoodCaseOperationSingleFile, allFileIDs=<null>], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@706d2bae[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], resultAddress=<null>]
Result: Received message on TEST-TOPIC-goodCaseOperationSingleFile-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@3205610d[correlationID=16d56894-7e25-4098-9873-79b2ed70085e, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationSingleFile-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationSingleFile-cibuild01-contributor, from=Pillar-goodCaseOperationSingleFile, to=goodCaseOperationSingleFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@54e06788[responseCode=OPERATION_COMPLETED, responseText=<null>], pillarID=Pillar-goodCaseOperationSingleFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@706d2bae[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], resultingChecksums=org.bitrepository.bitrepositoryelements.ResultingChecksums@4e789704[resultAddress=<null>, checksumDataItems={org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@5751e53e[fileID=DefaultFilegoodCaseOperationSingleFile, checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2015-11-21T02:24:06.763+01:00]}], partialResult=false]
Step: Retrieve the ProgressResponse for the GetChecksums request
Step: Retrieve the FinalResponse for the GetChecksums request
Test success: goodCaseOperationSingleFile
Added fixture: Initialize a new Pillar.
Test starting: testRestrictions
Description: Tests that the restrictions are correctly passed on to the cache.
Step: Set up constants and variables.
Step: Setup for only delivering result-set when the correct restrictions are given.
Step: Create and send the actual GetChecksums message to the pillar.
Result: Received message on TEST-TOPIC-testRestrictions-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsProgressResponse@2674ca88[correlationID=2373739b-b4fd-4104-90d0-328e833ddca8, collectionID=TwoPillarCollection, destination=TEST-TOPIC-testRestrictions-cibuild01, replyTo=TEST-TOPIC-Pillar-testRestrictions-cibuild01-contributor, from=Pillar-testRestrictions, to=testRestrictions, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@67a3dd86[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to calculate checksums.], pillarID=Pillar-testRestrictions, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@430212cb[fileID=<null>, allFileIDs=true], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1eb52131[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], resultAddress=<null>]
Result: Received message on TEST-TOPIC-testRestrictions-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@1e1598e5[correlationID=2373739b-b4fd-4104-90d0-328e833ddca8, collectionID=TwoPillarCollection, destination=TEST-TOPIC-testRestrictions-cibuild01, replyTo=TEST-TOPIC-Pillar-testRestrictions-cibuild01-contributor, from=Pillar-testRestrictions, to=testRestrictions, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@67a3394c[responseCode=OPERATION_COMPLETED, responseText=<null>], pillarID=Pillar-testRestrictions, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1eb52131[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], resultingChecksums=org.bitrepository.bitrepositoryelements.ResultingChecksums@34e4fb39[resultAddress=<null>, checksumDataItems={org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@36fe83d[fileID=DefaultFile, checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2015-11-21T02:24:06.986+01:00]}], partialResult=false]
Step: Retrieve the ProgressResponse for the GetChecksums request
Step: Retrieve the FinalResponse for the GetChecksums request
Test success: testRestrictions
Starting testcase GetFileIDsTest
Added fixture: Initialize a new Pillar.
Test starting: badCaseIdentification
Description: Tests the identification for a GetFileIDs operation on the pillar for the failure scenario, when the file is missing.
Step: Set up constants and variables.
Step: Setup for delivering pillar id and not having the file
Step: Create and send the identify request message.
02:24:07.156 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@74787609[correlationID=24751613-f3b0-497d-89bc-660723ab125e, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseIdentification-cibuild01-contributor, from=Pillar-badCaseIdentification, to=badCaseIdentification, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@36cdcae0[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseIdentification, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@51fa09c7[fileID=DefaultFilebadCaseIdentification, allFileIDs=<null>], timeToDeliver=<null>]
Step: Retrieve and validate the response getPillarID() the pillar.
Test success: badCaseIdentification
Added fixture: Initialize a new Pillar.
Test starting: badCaseOperationNoFile
Description: Tests the GetFileIDs functionality of the pillar for the failure scenario, where it does not have the file.
Step: Set up constants and variables.
Step: Setup for not having the file
Step: Create and send the actual GetFileIDs message to the pillar.
02:24:08.527 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@4b5f022f[correlationID=107a1f54-b23c-4f7f-afa0-f09cb0fcd521, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@7a569672[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@49f41c2e[fileID=DefaultFilebadCaseOperationNoFile, allFileIDs=<null>], resultingFileIDs=<null>, partialResult=<null>]
02:24:08.532 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@64186f60[correlationID=107a1f54-b23c-4f7f-afa0-f09cb0fcd521, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@de40aa1[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@49f41c2e[fileID=DefaultFilebadCaseOperationNoFile, allFileIDs=<null>], resultingFileIDs=<null>, partialResult=<null>]
02:24:08.537 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@70bc9070[correlationID=107a1f54-b23c-4f7f-afa0-f09cb0fcd521, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@5d202dc4[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@49f41c2e[fileID=DefaultFilebadCaseOperationNoFile, allFileIDs=<null>], resultingFileIDs=<null>, partialResult=<null>]
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@64186f60[correlationID=107a1f54-b23c-4f7f-afa0-f09cb0fcd521, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@de40aa1[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@49f41c2e[fileID=DefaultFilebadCaseOperationNoFile, allFileIDs=<null>], resultingFileIDs=<null>, partialResult=<null>]
org.bitrepository.bitrepositorymessages.GetFileIDsFinalResponse@70bc9070[correlationID=107a1f54-b23c-4f7f-afa0-f09cb0fcd521, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@5d202dc4[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@49f41c2e[fileID=DefaultFilebadCaseOperationNoFile, allFileIDs=<null>], resultingFileIDs=<null>, partialResult=<null>]
02:24:09.558 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.GetFileIDsFinalResponse@64186f60[correlationID=107a1f54-b23c-4f7f-afa0-f09cb0fcd521, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@de40aa1[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@49f41c2e[fileID=DefaultFilebadCaseOperationNoFile, allFileIDs=<null>], resultingFileIDs=<null>, partialResult=<null>]
org.bitrepository.bitrepositorymessages.GetFileIDsFinalResponse@70bc9070[correlationID=107a1f54-b23c-4f7f-afa0-f09cb0fcd521, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@5d202dc4[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@49f41c2e[fileID=DefaultFilebadCaseOperationNoFile, allFileIDs=<null>], resultingFileIDs=<null>, partialResult=<null>]
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@2d117280[correlationID=9efeea56-64ac-434e-a53e-6a5e7de0bfb0, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseIdentification-cibuild01-contributor, from=Pillar-goodCaseIdentification, to=goodCaseIdentification, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@6c2be147[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], pillarID=Pillar-goodCaseIdentification, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@dddcd91[fileID=DefaultFilegoodCaseIdentification, allFileIDs=<null>], timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@21bd6fd1[timeMeasureUnit=MILLISECONDS, timeMeasureValue=1000]]
Step: Retrieve and validate the response getPillarID() the pillar.
Test success: goodCaseIdentification
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@33f4844b[correlationID=73088ef3-7ff6-4725-a68c-e2b950783da1, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseIdentification-cibuild01-contributor, from=Pillar-badCaseIdentification, to=badCaseIdentification, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@201b52f7[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], fileID=DefaultFilebadCaseIdentification, pillarID=Pillar-badCaseIdentification, timeToDeliver=<null>]
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@60f1f95b[correlationID=fafcc57e-4e1d-43ee-b056-b8c8b1616d02, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseIdentification-cibuild01-contributor, from=Pillar-goodCaseIdentification, to=goodCaseIdentification, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@786cc1df[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], fileID=DefaultFilegoodCaseIdentification, pillarID=Pillar-goodCaseIdentification, timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@1ddb6abb[timeMeasureUnit=MILLISECONDS, timeMeasureValue=1000]]
Step: Retrieve and validate the response getPillarID() the pillar.
Test success: goodCaseIdentification
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@106f2425[correlationID=2bb32f06-6930-4743-b89e-2190cbe384e6, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseIdentification-cibuild01-contributor, from=Pillar-badCaseIdentification, to=badCaseIdentification, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@b666366[responseCode=DUPLICATE_FILE_FAILURE, responseText=<null>], pillarID=Pillar-badCaseIdentification, fileID=DefaultFilebadCaseIdentification, pillarChecksumSpec=<null>, checksumDataForExistingFile=<null>, timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@362fd4e9[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@2f11d889[correlationID=16ea34bc-2bc0-415f-a0fa-628b4f7a3d5c, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationFileAlreadyExists-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationFileAlreadyExists-cibuild01-contributor, from=Pillar-badCaseOperationFileAlreadyExists, to=badCaseOperationFileAlreadyExists, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@d1973e8[responseCode=DUPLICATE_FILE_FAILURE, responseText=We already have the file], pillarID=Pillar-badCaseOperationFileAlreadyExists, pillarChecksumSpec=<null>, fileID=DefaultFilebadCaseOperationFileAlreadyExists, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForNewFile=<null>, checksumDataForExistingFile=<null>]
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@225fb75e[correlationID=fc0b3d6b-4069-4734-bda8-840e137a02b9, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCasePutOperationNoValidationChecksum-cibuild01, replyTo=TEST-TOPIC-Pillar-badCasePutOperationNoValidationChecksum-cibuild01-contributor, from=Pillar-badCasePutOperationNoValidationChecksum, to=badCasePutOperationNoValidationChecksum, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@61d9dd15[responseCode=NEW_FILE_CHECKSUM_FAILURE, responseText=A checksum is required for the PutFile operation to be performed.], pillarID=Pillar-badCasePutOperationNoValidationChecksum, pillarChecksumSpec=<null>, fileID=DefaultFilebadCasePutOperationNoValidationChecksum, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForNewFile=<null>, checksumDataForExistingFile=<null>]
02:24:16.739 WARN o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@4936fbc6[origDateTime=2015-11-21T02:24:16.739+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCasePutOperationNoValidationChecksum, alarmText=A checksum is required for the PutFile operation to be performed., fileID=DefaultFilebadCasePutOperationNoValidationChecksum, collectionID=TwoPillarCollection]
Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@b4c89b6[correlationID=75cb7c5b-135d-4f3c-a5d4-e8e57fdc78ad, collectionID=TwoPillarCollection, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-Pillar-badCasePutOperationNoValidationChecksum-cibuild01-contributor, from=Pillar-badCasePutOperationNoValidationChecksum, to=<null>, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@4936fbc6[origDateTime=2015-11-21T02:24:16.739+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCasePutOperationNoValidationChecksum, alarmText=A checksum is required for the PutFile operation to be performed., fileID=DefaultFilebadCasePutOperationNoValidationChecksum, collectionID=TwoPillarCollection]]
Step: Retrieve the FinalResponse for the PutFile request
Step: Pillar should have sent an alarm
Test success: badCasePutOperationNoValidationChecksum
Added fixture: Initialize a new Pillar.
Test starting: goodCaseIdentification
Description: Tests the identification for a PutFile operation on the pillar for the successful scenario.
Step: Set up constants and variables.
Step: Setup for not already having the file and delivering pillar id
Step: Create and send the identify request message.
Result: Received message on TEST-TOPIC-goodCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileResponse@401d83ce[correlationID=79aa9d58-4893-4438-9eda-b444897c5851, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseIdentification-cibuild01-contributor, from=Pillar-goodCaseIdentification, to=goodCaseIdentification, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@3b7b099b[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], pillarID=Pillar-goodCaseIdentification, fileID=DefaultFilegoodCaseIdentification, pillarChecksumSpec=<null>, checksumDataForExistingFile=<null>, timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@5abc488d[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@15d68a50[correlationID=187d3069-ff9b-4b8a-88d2-3f1307147ed3, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationWithChecksumReturn-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationWithChecksumReturn-cibuild01-contributor, from=Pillar-goodCaseOperationWithChecksumReturn, to=goodCaseOperationWithChecksumReturn, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@a1689e8[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Started to receive data.], pillarID=Pillar-goodCaseOperationWithChecksumReturn, pillarChecksumSpec=<null>, 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@23b3afb4[correlationID=187d3069-ff9b-4b8a-88d2-3f1307147ed3, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationWithChecksumReturn-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationWithChecksumReturn-cibuild01-contributor, from=Pillar-goodCaseOperationWithChecksumReturn, to=goodCaseOperationWithChecksumReturn, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@2162598[responseCode=OPERATION_COMPLETED, responseText=<null>], pillarID=Pillar-goodCaseOperationWithChecksumReturn, pillarChecksumSpec=<null>, fileID=DefaultFilegoodCaseOperationWithChecksumReturn, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForNewFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@3cf1b5fb[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@4598961d[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2015-11-21T02:24:18.634+01:00], checksumDataForExistingFile=<null>]
Step: Retrieve the ProgressResponse for the GetFileIDs request
Step: Retrieve the FinalResponse for the PutFile request
Test success: goodCaseOperationWithChecksumReturn
Starting testcase ChecksumDatabaseMigrationTest
Test starting: testMigratingDatabaseChecksumsTable
Description: Tests that the checksums table can be migrated from version 1 to 2, e.g. getting the column collectionid, which should be set to the default in settings.
Step: Validate setup
Step: Ingest a entry to the database without the collection id
Step: Perform migration
02:24:23.013 WARN o.b.service.database.DatabaseUtils - Migrating the checksums table from version 1 to 2 in the ChecksumDatabase.
02:24:23.082 WARN o.b.service.database.DatabaseUtils - Migrating ChecksumDB from version 2 to 3.
Step: Validate the entry
Test success: testMigratingDatabaseChecksumsTable
Test starting: getPillarCollectionsTest
Test success: getPillarCollectionsTest
Starting testcase ChecksumDatabaseTest
Test starting: testChecksumDatabaseExtraction
Description: Test the extraction of data from the checksum database.
Step: Check whether the default entry exists.
Step: Extract calculation date
Step: Extract the checksum
Step: Extract the whole entry
Step: Extract all entries
Test success: testChecksumDatabaseExtraction
Test starting: testDeletion
Description: Test that data can be deleted from the database.
Step: Check whether the default entry exists.
Step: Remove the default entry
Test success: testDeletion
Test starting: testExtractionOfMissingData
Description: Test the handling of bad arguments.
Step: Try to get the date of a wrong file id.
Step: Try to get the date of a wrong file id.
Step: Try to remove a bad file id
Test success: testExtractionOfMissingData
Test starting: testGetFileIDsRestrictions
Description: Tests the restrictions on the GetFileIDs call to the database.
Step: Instantiate database with appropriate data.
Step: Test with no time restrictions and 10000 max_results
Step: Test with minimum-date earlier than first file
Step: Test with maximum-date earlier than first file
Step: Test with minimum-date set to later than second file.
Step: Test with maximum-date set to later than second file.
Step: Test with minimum-date set to middle date.
Step: Test with maximum-date set to middle date.
Step: Test with both minimum-date and maximum-date set to middle date.
Step: Test the first file-id, with no other restrictions
Step: Test the second file-id, with no other restrictions
Step: Test the date for the first file-id, while requesting the second file-id
Test success: testGetFileIDsRestrictions
Test starting: testReplacingExistingEntry
Description: Test that an entry can be replaced by another in the database.
Step: Check whether the default entry exists.
Step: Replace the checksum and date
Test success: testReplacingExistingEntry
Test starting: testSpecifiedEntryExtraction
Description: Test that specific entries can be extracted. Has two entries in the database: one for the current timestamp and one for the epoch.
Step: Instantiate database with appropriate data.
Step: Extract with out restrictions
Step: Extract with a maximum of 1 entry
Step: Extract all dates older than this tests instantiation
Step: Extract all dates newer than this tests instantiation
Step: Extract all dates older than the newest instance
Step: Extract all dates newer than the oldest instantiation
Test success: testSpecifiedEntryExtraction
Finished testcase
Finished suite
Finished project
Tests run: 57, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 71.227 sec - in TestSuite
Results :
Tests run: 57, Failures: 0, Errors: 0, Skipped: 0
[JENKINS] Recording test results
[INFO]
[INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ bitrepository-reference-pillar ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.6-SNAPSHOT.jar
[INFO]
[INFO] --- maven-jar-plugin:2.4:test-jar (default) @ bitrepository-reference-pillar ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.6-SNAPSHOT-tests.jar
[INFO]
[INFO] --- maven-source-plugin:2.2.1:jar-no-fork (attach-sources-no-fork) @ bitrepository-reference-pillar ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.6-SNAPSHOT-sources.jar
[INFO]
[INFO] --- maven-assembly-plugin:2.4:single (distribution) @ bitrepository-reference-pillar ---
[INFO] Reading assembly descriptor: src/main/assembly/assembly.xml
[INFO] Reading assembly descriptor: src/test/assembly/assembly.xml
[INFO] Reading assembly descriptor: src/main/assembly/deploy-assembly.xml
[INFO] Reading assembly descriptor: src/test/assembly/test-deploy-assembly.xml
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.6-SNAPSHOT-distribution.tar.gz
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.6-SNAPSHOT-acceptance-test.tar.gz
[WARNING] Entry: bitrepository-reference-pillar-1.6-SNAPSHOT/lib/bitrepository-reference-pillar-1.6-SNAPSHOT-tests.jar longer than 100 characters.
[WARNING] Resulting tar file can only be processed successfully by GNU compatible tar commands
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.6-SNAPSHOT-deploy.tar.gz
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.6-SNAPSHOT-acceptance-test-deploy.tar.gz
[INFO]
[INFO] --- maven-install-plugin:2.5.1:install (default-install) @ bitrepository-reference-pillar ---
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.6-SNAPSHOT.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.6-SNAPSHOT/bitrepository-reference-pillar-1.6-SNAPSHOT.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.6-SNAPSHOT/bitrepository-reference-pillar-1.6-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.6-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.6-SNAPSHOT/bitrepository-reference-pillar-1.6-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.6-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.6-SNAPSHOT/bitrepository-reference-pillar-1.6-SNAPSHOT-sources.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.6-SNAPSHOT-distribution.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.6-SNAPSHOT/bitrepository-reference-pillar-1.6-SNAPSHOT-distribution.tar.gz
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.6-SNAPSHOT-acceptance-test.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.6-SNAPSHOT/bitrepository-reference-pillar-1.6-SNAPSHOT-acceptance-test.tar.gz
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.6-SNAPSHOT-deploy.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.6-SNAPSHOT/bitrepository-reference-pillar-1.6-SNAPSHOT-deploy.tar.gz
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.6-SNAPSHOT-acceptance-test-deploy.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.6-SNAPSHOT/bitrepository-reference-pillar-1.6-SNAPSHOT-acceptance-test-deploy.tar.gz
[JENKINS] Archiving disabled
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Monitoring Service 1.6-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-monitoring-service ---
[INFO] Deleting /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-monitoring-service/target
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ bitrepository-monitoring-service ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-monitoring-service/src/main/resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ bitrepository-monitoring-service ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 14 source files to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-monitoring-service/target/classes
[INFO]
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ bitrepository-monitoring-service ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-monitoring-service/src/test/resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ bitrepository-monitoring-service ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 7 source files to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-monitoring-service/target/test-classes
[INFO]
[INFO] --- maven-surefire-plugin:2.17:test (default-test) @ bitrepository-monitoring-service ---
[INFO] Surefire report directory: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-monitoring-service/target/surefire-reports
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running TestSuite
Configuring TestNG with: TestNG652Configurator
Starting test project Core module test
Suite: Surefire suite
Starting testcase 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 MonitorAlerterTest
Test starting: testMonitorAlerter
Description: Tests the org.bitrepository.monitoringservice.alarm.BasicMonitoringServiceAlerter
Step: Setup
Step: Create the alerter, but ignore the part of actually sending the alarms. Just log it.
Step: Check statuses with an empty map.
Step: Check the status when a positive entry exists.
Step: Check the status when a negative entry exists.
02:24:55.478 WARN o.b.m.a.BasicMonitoringServiceAlerter - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@12591ac8[origDateTime=2015-11-21T02:24:55.470+01:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MonitorAlerterUnderTest, alarmText=The following components have become unresponsive: [TestMonitorService], fileID=<null>, collectionID=<null>]
Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@2bdd8394[correlationID=d32039b1-cdcd-4f95-a2fd-56d23e1ee218, collectionID=<null>, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-MonitorAlerterUnderTest-cibuild01-contributor, from=MonitorAlerterUnderTest, to=<null>, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@12591ac8[origDateTime=2015-11-21T02:24:55.470+01:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MonitorAlerterUnderTest, alarmText=The following components have become unresponsive: [TestMonitorService], fileID=<null>, collectionID=<null>]]
Test success: testMonitorAlerter
Starting testcase ComponentStatusStoreTest
Test starting: testComponentStatus
Description: Tests the compontent status
Step: Setup
Step: Validate the initial content
Step: Update the replay counts and validate
Step: Test what happens when an invalid component id attempted to be updated.
02:24:56.230 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
Finished testcase
Finished suite
Finished project
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 8.378 sec - in TestSuite
Results :
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0
[JENKINS] Recording test results
[INFO]
[INFO] --- maven-war-plugin:2.4:war (default-war) @ bitrepository-monitoring-service ---
[INFO] Packaging webapp
[INFO] Assembling webapp [bitrepository-monitoring-service] in [/home/cibuild01/workspace/Bitrepository-sonar/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.6-SNAPSHOT]
[INFO] Processing war project
[INFO] Copying webapp resources [/home/cibuild01/workspace/Bitrepository-sonar/bitrepository-monitoring-service/src/main/webapp]
[INFO] Webapp assembled in [324 msecs]
[INFO] Building war: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.6-SNAPSHOT.war
[INFO]
[INFO] --- maven-jar-plugin:2.4:test-jar (default) @ bitrepository-monitoring-service ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.6-SNAPSHOT-tests.jar
[INFO]
[INFO] --- maven-source-plugin:2.2.1:jar-no-fork (attach-sources-no-fork) @ bitrepository-monitoring-service ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.6-SNAPSHOT-sources.jar
[INFO]
[INFO] --- maven-assembly-plugin:2.4:single (distribution) @ bitrepository-monitoring-service ---
[INFO] Reading assembly descriptor: src/main/assembly/assembly.xml
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.6-SNAPSHOT-distribution.tar.gz
[INFO]
[INFO] --- maven-install-plugin:2.5.1:install (default-install) @ bitrepository-monitoring-service ---
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.6-SNAPSHOT.war to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-monitoring-service/1.6-SNAPSHOT/bitrepository-monitoring-service-1.6-SNAPSHOT.war
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-monitoring-service/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-monitoring-service/1.6-SNAPSHOT/bitrepository-monitoring-service-1.6-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.6-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-monitoring-service/1.6-SNAPSHOT/bitrepository-monitoring-service-1.6-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.6-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-monitoring-service/1.6-SNAPSHOT/bitrepository-monitoring-service-1.6-SNAPSHOT-sources.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.6-SNAPSHOT-distribution.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-monitoring-service/1.6-SNAPSHOT/bitrepository-monitoring-service-1.6-SNAPSHOT-distribution.tar.gz
[JENKINS] Archiving disabled
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Webclient 1.6-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-webclient ---
[INFO] Deleting /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-webclient/target
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ bitrepository-webclient ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ bitrepository-webclient ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 12 source files to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-webclient/target/classes
[INFO]
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ bitrepository-webclient ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-webclient/src/test/resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ bitrepository-webclient ---
[INFO] No sources to compile
[INFO]
[INFO] --- maven-surefire-plugin:2.17:test (default-test) @ bitrepository-webclient ---
[INFO] No tests to run.
[JENKINS] Recording test results
[INFO]
[INFO] --- maven-war-plugin:2.4:war (default-war) @ bitrepository-webclient ---
[INFO] Packaging webapp
[INFO] Assembling webapp [bitrepository-webclient] in [/home/cibuild01/workspace/Bitrepository-sonar/bitrepository-webclient/target/bitrepository-webclient-1.6-SNAPSHOT]
[INFO] Processing war project
[INFO] Copying webapp webResources [/home/cibuild01/workspace/Bitrepository-sonar/bitrepository-webclient/src/main/webapp] to [/home/cibuild01/workspace/Bitrepository-sonar/bitrepository-webclient/target/bitrepository-webclient-1.6-SNAPSHOT]
[INFO] Copying webapp resources [/home/cibuild01/workspace/Bitrepository-sonar/bitrepository-webclient/src/main/webapp]
[INFO] Webapp assembled in [982 msecs]
[INFO] Building war: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-webclient/target/bitrepository-webclient-1.6-SNAPSHOT.war
[INFO]
[INFO] --- maven-jar-plugin:2.4:test-jar (default) @ bitrepository-webclient ---
[WARNING] JAR will be empty - no content was marked for inclusion!
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-webclient/target/bitrepository-webclient-1.6-SNAPSHOT-tests.jar
[INFO]
[INFO] --- maven-source-plugin:2.2.1:jar-no-fork (attach-sources-no-fork) @ bitrepository-webclient ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-webclient/target/bitrepository-webclient-1.6-SNAPSHOT-sources.jar
[INFO]
[INFO] --- maven-assembly-plugin:2.4:single (distribution) @ bitrepository-webclient ---
[INFO] Reading assembly descriptor: src/main/assembly/assembly.xml
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-webclient/target/bitrepository-webclient-1.6-SNAPSHOT-distribution.tar.gz
[INFO]
[INFO] --- maven-install-plugin:2.5.1:install (default-install) @ bitrepository-webclient ---
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-webclient/target/bitrepository-webclient-1.6-SNAPSHOT.war to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-webclient/1.6-SNAPSHOT/bitrepository-webclient-1.6-SNAPSHOT.war
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-webclient/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-webclient/1.6-SNAPSHOT/bitrepository-webclient-1.6-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-webclient/target/bitrepository-webclient-1.6-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-webclient/1.6-SNAPSHOT/bitrepository-webclient-1.6-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-webclient/target/bitrepository-webclient-1.6-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-webclient/1.6-SNAPSHOT/bitrepository-webclient-1.6-SNAPSHOT-sources.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-webclient/target/bitrepository-webclient-1.6-SNAPSHOT-distribution.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-webclient/1.6-SNAPSHOT/bitrepository-webclient-1.6-SNAPSHOT-distribution.tar.gz
[JENKINS] Archiving disabled
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Integration 1.6-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-integration ---
[INFO] Deleting /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integration/target
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ bitrepository-integration ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 33 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ bitrepository-integration ---
[INFO] No sources to compile
[INFO]
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ bitrepository-integration ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO]
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ bitrepository-integration ---
[INFO] No sources to compile
[INFO]
[INFO] --- maven-surefire-plugin:2.17:test (default-test) @ bitrepository-integration ---
[JENKINS] Recording test results
[INFO]
[INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ bitrepository-integration ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integration/target/bitrepository-integration-1.6-SNAPSHOT.jar
[INFO]
[INFO] --- maven-jar-plugin:2.4:test-jar (default) @ bitrepository-integration ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integration/target/bitrepository-integration-1.6-SNAPSHOT-tests.jar
[INFO]
[INFO] --- maven-source-plugin:2.2.1:jar-no-fork (attach-sources-no-fork) @ bitrepository-integration ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integration/target/bitrepository-integration-1.6-SNAPSHOT-sources.jar
[INFO]
[INFO] --- maven-assembly-plugin:2.4:single (make-assembly) @ bitrepository-integration ---
[INFO] Reading assembly descriptor: src/main/assembly/assembly.xml
[INFO] Reading assembly descriptor: src/main/assembly/tools-assembly.xml
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integration/target/bitrepository-integration-1.6-SNAPSHOT-quickstart.tar.gz
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integration/target/bitrepository-integration-1.6-SNAPSHOT-tools.tar.gz
[WARNING] Entry: bitrepository-integration-1.6-SNAPSHOT/lib/bitrepository-reference-pillar-1.6-SNAPSHOT-distribution.tar.gz longer than 100 characters.
[WARNING] Resulting tar file can only be processed successfully by GNU compatible tar commands
[INFO]
[INFO] --- maven-install-plugin:2.5.1:install (default-install) @ bitrepository-integration ---
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integration/target/bitrepository-integration-1.6-SNAPSHOT.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integration/1.6-SNAPSHOT/bitrepository-integration-1.6-SNAPSHOT.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integration/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integration/1.6-SNAPSHOT/bitrepository-integration-1.6-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integration/target/bitrepository-integration-1.6-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integration/1.6-SNAPSHOT/bitrepository-integration-1.6-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integration/target/bitrepository-integration-1.6-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integration/1.6-SNAPSHOT/bitrepository-integration-1.6-SNAPSHOT-sources.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integration/target/bitrepository-integration-1.6-SNAPSHOT-quickstart.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integration/1.6-SNAPSHOT/bitrepository-integration-1.6-SNAPSHOT-quickstart.tar.gz
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integration/target/bitrepository-integration-1.6-SNAPSHOT-tools.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integration/1.6-SNAPSHOT/bitrepository-integration-1.6-SNAPSHOT-tools.tar.gz
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Bitrepository ..................................... SUCCESS [ 9.339 s]
[INFO] Bitrepository Reference Settings .................. SUCCESS [ 18.422 s]
[INFO] Bitrepository Core ................................ SUCCESS [ 52.351 s]
[INFO] Bitrepository Client .............................. SUCCESS [01:17 min]
[INFO] Bitrepository Service ............................. SUCCESS [ 13.911 s]
[INFO] Bitrepository Integrity Service ................... SUCCESS [01:54 min]
[INFO] Bitrepository Alarm Service ....................... SUCCESS [ 26.669 s]
[INFO] Bitrepository Audit Trail Service ................. SUCCESS [ 37.319 s]
[INFO] Bitrepository Reference Pillar .................... SUCCESS [01:22 min]
[INFO] Bitrepository Monitoring Service .................. SUCCESS [ 15.477 s]
[INFO] Bitrepository Webclient ........................... SUCCESS [ 4.930 s]
[INFO] Bitrepository Integration ......................... SUCCESS [ 18.942 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 08:01 min
[INFO] Finished at: 2015-11-21T02:25:29+01:00
[INFO] Final Memory: 52M/131M
[INFO] ------------------------------------------------------------------------
channel stopped
[Bitrepository-sonar] $ /home/cibuild01/tools/hudson.tasks.Maven_MavenInstallation/Maven3.2/bin/mvn -f /home/cibuild01/workspace/Bitrepository-sonar/pom.xml -e -B sonar:sonar -Dsonar.jdbc.url=jdbc:postgresql://leda/sonar ******** ******** -Dsonar.host.url=https://sbforge.org/sonar
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=128m; support was removed in 8.0
[INFO] Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO]
[INFO] Bitrepository
[INFO] Bitrepository Reference Settings
[INFO] Bitrepository Core
[INFO] Bitrepository Client
[INFO] Bitrepository Service
[INFO] Bitrepository Integrity Service
[INFO] Bitrepository Alarm Service
[INFO] Bitrepository Audit Trail Service
[INFO] Bitrepository Reference Pillar
[INFO] Bitrepository Monitoring Service
[INFO] Bitrepository Webclient
[INFO] Bitrepository Integration
[INFO] Downloading: https://sbforge.org/nexus/content/groups/public/org/apache/maven/plugins/maven-metadata.xml
[INFO] Downloading: https://sbforge.org/nexus/content/groups/public/org/codehaus/mojo/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/groups/public/org/apache/maven/plugins/maven-metadata.xml (14 KB at 2.2 KB/sec)
[INFO] Downloaded: https://sbforge.org/nexus/content/groups/public/org/codehaus/mojo/maven-metadata.xml (23 KB at 3.1 KB/sec)
[INFO] Downloading: https://sbforge.org/nexus/content/groups/public/org/codehaus/mojo/sonar-maven-plugin/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/groups/public/org/codehaus/mojo/sonar-maven-plugin/maven-metadata.xml (892 B at 0.7 KB/sec)
[INFO]
[INFO] Using the builder org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder with a thread count of 1
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository 1.6-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- sonar-maven-plugin:2.7.1:sonar (default-cli) @ bitrepository-parent ---
[INFO] User cache: /home/cibuild01/.sonar/cache
[INFO] SonarQube version: 4.4
[INFO] Default locale: "en_US", source code encoding: "UTF-8"
[INFO] [02:26:02.065] Load global settings
[INFO] [02:26:02.705] User cache: /home/cibuild01/.sonar/cache
[INFO] [02:26:02.833] Install plugins
[INFO] [02:26:04.722] Install JDBC driver
[INFO] [02:26:04.909] Create JDBC datasource for jdbc:postgresql://leda/sonar
[INFO] [02:26:05.322] Initializing Hibernate
[ERROR] [02:26:16.253] Invalid value of sonar.sources for org.bitrepository.reference:bitrepository-reference-settings
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Bitrepository ..................................... FAILURE [ 25.065 s]
[INFO] Bitrepository Reference Settings .................. SKIPPED
[INFO] Bitrepository Core ................................ SKIPPED
[INFO] Bitrepository Client .............................. SKIPPED
[INFO] Bitrepository Service ............................. SKIPPED
[INFO] Bitrepository Integrity Service ................... SKIPPED
[INFO] Bitrepository Alarm Service ....................... SKIPPED
[INFO] Bitrepository Audit Trail Service ................. SKIPPED
[INFO] Bitrepository Reference Pillar .................... SKIPPED
[INFO] Bitrepository Monitoring Service .................. SKIPPED
[INFO] Bitrepository Webclient ........................... SKIPPED
[INFO] Bitrepository Integration ......................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 42.081 s
[INFO] Finished at: 2015-11-21T02:26:16+01:00
[INFO] Final Memory: 25M/69M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.codehaus.mojo:sonar-maven-plugin:2.7.1:sonar (default-cli) on project bitrepository-parent: The folder '/home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-settings/pom.xml' does not exist for 'org.bitrepository.reference:bitrepository-reference-settings' (base directory = /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-settings) -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.codehaus.mojo:sonar-maven-plugin:2.7.1:sonar (default-cli) on project bitrepository-parent: The folder '/home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-settings/pom.xml' does not exist for 'org.bitrepository.reference:bitrepository-reference-settings' (base directory = /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-settings)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:108)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:76)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:116)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:361)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:213)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:157)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.apache.maven.plugin.MojoExecutionException: The folder '/home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-settings/pom.xml' does not exist for 'org.bitrepository.reference:bitrepository-reference-settings' (base directory = /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-settings)
at org.codehaus.mojo.sonar.bootstrap.ExceptionHandling.handle(ExceptionHandling.java:41)
at org.codehaus.mojo.sonar.bootstrap.RunnerBootstrapper.execute(RunnerBootstrapper.java:104)
at org.codehaus.mojo.sonar.SonarMojo.execute(SonarMojo.java:135)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:133)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
... 19 more
Caused by: java.lang.IllegalStateException: The folder '/home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-settings/pom.xml' does not exist for 'org.bitrepository.reference:bitrepository-reference-settings' (base directory = /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-settings)
at org.sonar.batch.scan.ProjectReactorBuilder.checkExistenceOfDirectories(ProjectReactorBuilder.java:423)
at org.sonar.batch.scan.ProjectReactorBuilder.cleanAndCheckModuleProperties(ProjectReactorBuilder.java:336)
at org.sonar.batch.scan.ProjectReactorBuilder.cleanAndCheckProjectDefinitions(ProjectReactorBuilder.java:319)
at org.sonar.batch.scan.ProjectReactorBuilder.cleanAndCheckProjectDefinitions(ProjectReactorBuilder.java:325)
at org.sonar.batch.scan.ProjectReactorBuilder.execute(ProjectReactorBuilder.java:117)
at org.sonar.batch.scan.ProjectScanContainer.projectBootstrap(ProjectScanContainer.java:114)
at org.sonar.batch.scan.ProjectScanContainer.doBeforeStart(ProjectScanContainer.java:92)
at org.sonar.api.platform.ComponentContainer.startComponents(ComponentContainer.java:90)
at org.sonar.api.platform.ComponentContainer.execute(ComponentContainer.java:77)
at org.sonar.batch.scan.ScanTask.scan(ScanTask.java:64)
at org.sonar.batch.scan.ScanTask.execute(ScanTask.java:51)
at org.sonar.batch.bootstrap.TaskContainer.doAfterStart(TaskContainer.java:110)
at org.sonar.api.platform.ComponentContainer.startComponents(ComponentContainer.java:92)
at org.sonar.api.platform.ComponentContainer.execute(ComponentContainer.java:77)
at org.sonar.batch.bootstrap.BootstrapContainer.executeTask(BootstrapContainer.java:185)
at org.sonar.batch.bootstrapper.Batch.executeTask(Batch.java:95)
at org.sonar.batch.bootstrapper.Batch.execute(Batch.java:67)
at org.sonar.runner.batch.BatchIsolatedLauncher.executeOldVersion(BatchIsolatedLauncher.java:92)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at org.sonar.runner.impl.IsolatedLauncherProxy.invoke(IsolatedLauncherProxy.java:61)
at com.sun.proxy.$Proxy21.executeOldVersion(Unknown Source)
at org.sonar.runner.api.EmbeddedRunner.doExecute(EmbeddedRunner.java:284)
at org.sonar.runner.api.EmbeddedRunner.runAnalysis(EmbeddedRunner.java:166)
at org.sonar.runner.api.EmbeddedRunner.runAnalysis(EmbeddedRunner.java:153)
at org.codehaus.mojo.sonar.bootstrap.RunnerBootstrapper.execute(RunnerBootstrapper.java:99)
... 22 more
[ERROR]
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionExceptionSonarQube analysis completed: FAILURE
Build step 'SonarQube' changed build result to FAILURE
Build step 'SonarQube' marked build as failure
Sending e-mails to: ktc@statsbiblioteket.dk abr@statsbiblioteket.dk
Finished: FAILURE
Console Output
Help us localize this page