SuccessConsole Output

[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Core 1.6-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-core ---
[INFO] Deleting /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-core/target
[INFO] 
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ bitrepository-core ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ bitrepository-core ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 89 source files to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-core/target/classes
[INFO] 
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ bitrepository-core ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 11 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ bitrepository-core ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 62 source files to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-core/target/test-classes
[INFO] 
[INFO] --- maven-surefire-plugin:2.17:test (default-test) @ bitrepository-core ---
[INFO] Surefire report directory: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-core/target/surefire-reports

-------------------------------------------------------
 T E S T S
-------------------------------------------------------
Running TestSuite
Configuring TestNG with: TestNG652Configurator
Starting test project Core module test
  Suite: Surefire suite
    Starting testcase ArgumentValidatorTest
      Test starting: testArgumentValidatorArrays
        Description: Test the argument validator for arguments for arrays
        Step: Check against null or empty arrays
      Test success: testArgumentValidatorArrays
      Test starting: testArgumentValidatorBoolean
        Description: Test the argument validator for arguments for booleans
        Step: validate checkTrue
      Test success: testArgumentValidatorBoolean
      Test starting: testArgumentValidatorCollection
        Description: Test the argument validator for arguments for collections
        Step: Check against null or empty collection
      Test success: testArgumentValidatorCollection
      Test starting: testArgumentValidatorInteger
        Description: Test the argument validator for arguments for integers
        Step: Test not negative
        Step: Test positive
      Test success: testArgumentValidatorInteger
      Test starting: testArgumentValidatorLong
        Description: Test the argument validator for arguments for longs
        Step: Test not negative
        Step: Test positive
      Test success: testArgumentValidatorLong
      Test starting: testArgumentValidatorObject
        Description: Test the argument validator for arguments not null
        Step: Test not null
      Test success: testArgumentValidatorObject
      Test starting: testArgumentValidatorString
        Description: Test the argument validator for arguments for strings
        Step: Test empty string
      Test success: testArgumentValidatorString
      Test starting: utilityTester
        Description: Test that the utility class is a proper utility class.
      Test success: utilityTester
    Starting testcase CertificateIDTest
      Test starting: equalTest
        Description: Tests the equality of CertificateIDs
        Step: Setup
        Step: Validate the content of the certificateID
        Step: Test whether it equals it self
        Step: Test with a null as argument
        Step: Test with another class
        Step: Test with same issuer but no serial
        Step: Test with same serial but no issuer
        Step: Test the positive case, with both the issuer and serial 
        Step: Setup an empty certificate
        Step: Test empty certificate against issuer but no serial
        Step: Test empty certificate against serial but no issuer
        Step: Test empty certificate against serial and issuer
        Step: Test the positive case, with neither issuer nor serial
        Step: Check the hash codes for the two certificate
      Test success: equalTest
      Test starting: negativeCertificateIdentificationTest
        Description: Tests that a certificate is not identified based on a incorrect signature.
        Step: Create CertificateID object based on a certificate not used for signing the data
        Step: Create CertificateID object based on signature
        Step: Assert that the two CertificateID objects are equal
      Test success: negativeCertificateIdentificationTest
      Test starting: positiveCertificateIdentificationTest
        Description: Tests that a certificate can be identified based on the correct signature.
        Step: Create CertificateID object based on the certificate used to sign the data
        Step: Create CertificateID object based on signature
        Step: Assert that the two CertificateID objects are equal
      Test success: positiveCertificateIdentificationTest
    Starting testcase ChecksumUtilsTest
      Test starting: calculateDigestChecksums
        Description: Tests whether the utility class for calculating checksums with MessageDigest is able to correctly calculate the checksums.
        Step: Setup variables.
        Step: Test with no text and no key for MD5, SHA1, and SHA256
        Step: Test with text 
        Step: add a salt to the checksum
      Test success: calculateDigestChecksums
      Test starting: calculateHmacChecksums
        Description: Tests whether the utility class for calculating checksums with HMAC is able to correctly calculate predefined examples from : http://en.wikipedia.org/wiki/HMAC#Examples_of_HMAC_.28MD5.2C_SHA1.2C_SHA256_.29
        Step: Setup variables.
        Step: Test with no text and no key for HMAC_MD5, HMAC_SHA1, and HMAC_SHA256
        Step: Test with the text 'The quick brown fox jumps over the lazy dog' and key 'key' for MD5, SHA1, and SHA256
        Step: Try calculating HMAC with a null salt
      Test success: calculateHmacChecksums
      Test starting: testChecksumAlgorithmValidation
        Description: Test the algorithm validation for every single possible checksum algorithm.
        Step: Test 'MD5'
        Step: Test 'SHA1'
        Step: Test 'SHA256'
        Step: Test 'SHA384'
        Step: Test 'SHA512'
        Step: Test 'HMAC_MD5'
        Step: Test 'HMAC_SHA1'
        Step: Test 'HMAC_SHA256'
        Step: Test 'HMAC_SHA384'
        Step: Test 'HMAC_SHA512'
        Step: Test 'OTHER'
      Test success: testChecksumAlgorithmValidation
      Test starting: testChecksumOnFile
        Description: Test the checksum calculation on a file
        Step: Setup
        Step: Calculate the checksum of the file with the different ways of defining the MD5 without salt
      Test success: testChecksumOnFile
      Test starting: testDefaultChecksum
        Description: Test the extraction of the default checksum from settings.
        Step: Setup the settings
        Step: Use utils to extract default checksum spec
      Test success: testDefaultChecksum
      Test starting: utilityTester
        Description: Test that the utility class is a proper utility class.
      Test success: utilityTester
    Starting testcase FileUtilsTest
      Test starting: createDeleteDirectoryTester
        Description: Test the ability to delete directories.
        Step: Test deleting a directory with file and subdirectory
      Test success: createDeleteDirectoryTester
      Test starting: createDirectoryTester
        Description: Test the ability to create directories.
        Step: Test the ability to create a directory
        Step: Test error scenarios, when the directory path is a file
      Test success: createDirectoryTester
      Test starting: createSubDirectoryTester
        Description: Test the ability to create sub directories.
        Step: Test the ability to create sub-directories
        Step: Test that it fails if the 'directory' is actually a file
        Step: Test that it fails, if the parent directory does not allow writing
      Test success: createSubDirectoryTester
      Test starting: deprecateFileTester
        Description: Test the deprecation of a file.
        Step: Setup
        Step: Deprecate the file
      Test success: deprecateFileTester
      Test starting: moveFileTester
        Description: Test the moving of a file.
        Step: Setup
        Step: Move the file
      Test success: moveFileTester
      Test starting: unzipFileTester
        Description: Test unzipping a file.
        Step: Setup
        Step: Unzip the zipfile to the directory
      Test success: unzipFileTester
      Test starting: utilityTester
        Description: Test that the utility class is a proper utility class.
      Test success: utilityTester
      Test starting: writeInputstreamTester
        Description: Test writing an inputstream to a file.
        Step: Setup
        Step: Write the input stream to the file
      Test success: writeInputstreamTester
    Starting testcase GeneralMessageBusTest
      Test starting: busActivityTest
        Description: Tests whether it is possible to create a message listener, and then set it to listen to the topic. Then puts a messageon the topic for the message listener to find, andtests whether it finds the correct message.
        Step: Send a message to the topic
          Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@2a7686a7[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@758a34ce[origDateTime=2011-05-03T11:18:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>]]
        Step: Make sure both listeners received the message
      Test success: busActivityTest
      Test starting: twoListenersForTopicTest
        Description: Verifies that two listeners on the same topic both receive the message
        Step: Make a connection to the message bus and add two listeners
        Step: Send a message to the topic
          Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@4816c290[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@4940809c[origDateTime=2011-05-03T11:18:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>]]
          Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@4816c290[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@4940809c[origDateTime=2011-05-03T11:18:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>]]
          Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@4816c290[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@4940809c[origDateTime=2011-05-03T11:18:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>]]
        Step: Make sure both listeners received the message
      Test success: twoListenersForTopicTest
          Result: The following messages haven't been handled by the testcase: 
org.bitrepository.bitrepositorymessages.AlarmMessage@4816c290[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@4940809c[origDateTime=2011-05-03T11:18:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>]]
02:17:59.727 WARN  o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: 
org.bitrepository.bitrepositorymessages.AlarmMessage@4816c290[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@4940809c[origDateTime=2011-05-03T11:18:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>]]
      Test starting: utilityTester
        Description: Test that the utility class is a proper utility class.
      Test success: utilityTester
    Starting testcase HttpFileExchangeTest
      Test starting: checkUrlEncodingOfFilenamesTest
        Description: Tests that the filename is url-encoded correctly for a configured webdav server
        Step: Check plain filename (a filename that does not see any changes due to urlencoding
        Step: Check that + is encoded as expected
      Test success: checkUrlEncodingOfFilenamesTest
    Starting testcase MessageAuthenticationExceptionTest
      Test starting: testMessageAuthenticationException
        Description: Test the instantiation of the exception
        Step: Setup
        Step: Try to throw such an exception
        Step: Throw the exception with an embedded exception
      Test success: testMessageAuthenticationException
    Starting testcase OperationAuthorizationExceptionTest
      Test starting: testOperationAuthorizationException
        Description: Test the instantiation of the exception
        Step: Setup
        Step: Try to throw such an exception
        Step: Throw the exception with an embedded exception
      Test success: testOperationAuthorizationException
    Starting testcase TimeUtilsTest
      Test starting: shortDateTest
      Test success: shortDateTest
      Test starting: timeTester
        Description: Tests the TimeUtils. Pi days = 271433605 milliseconds
        Step: Test that milliseconds can be converted into human readable seconds
        Step: Test that milliseconds can be converted into human readable minutes.
        Step: Test that milliseconds can be converted into human readable hours.
        Step: Test that milliseconds can be converted into human readable minutes.
        Step: Test the human readable output.
      Test success: timeTester
      Test starting: utilityTester
        Description: Test that the utility class is a proper utility class.
      Test success: utilityTester
      Test starting: zeroIntervalTest
        Description: Verifies that a 0 ms interval is represented correctly
        Step: Call the millisecondsToHuman with 0 ms
      Test success: zeroIntervalTest
    Starting testcase UnableToFinishExceptionTest
      Test starting: testUnableToFinish
        Description: Test the instantiation of the exception
        Step: Setup
        Step: Try to throw such an exception
        Step: Throw the exception with an embedded exception
      Test success: testUnableToFinish
    Starting testcase ActiveMQMessageBusTest
02:18:01.408 WARN  o.a.activemq.broker.BrokerService - Memory Usage for the Broker (1024 mb) is more than the maximum available for the JVM: 487 mb - resetting to 70% of maximum available: 341 mb
02:18:01.409 WARN  o.a.activemq.broker.BrokerService - Temporary Store limit is 51200 mb (current temporary store usage is 0 mb). The temporary data directory: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-core/target only has 10973 mb of usable space - resetting to maximum available disk space: 10973 mb
      Test starting: collectionFilterTest
        Description: Test that message bus filters identify requests to other collection, eg. ignores these.
        Step: Send an identify request with a undefined 'Collection' header property, eg. this identify requests should be handled by everybody.
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@45fd6df9[correlationID=12345, collectionID=MyCollection, destination=topic://collectionTopic, replyTo=topic://clientTopic, from=ClientPillar, to=<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@4b3a9b36[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@7a0e7ecd[correlationID=12345, collectionID=MySla, destination=TEST-TOPIC-cibuild01, replyTo=topic://clientTopic, from=ClientPillar, to=specificReceiver, version=28, minVersion=24, auditTrailInformation=User: Name, Institution: Place, fileID=MyDataID]
      Test success: sendMessageToSpecificComponentTest
      Test starting: toFilterTest
        Description: Test that message bus filters identify requests to other components, eg. ignores these.
        Step: Send an identify request with a undefined 'To' header property, eg. this identify requests should be handled by all components.
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@4f050689[correlationID=12345, collectionID=MySla, destination=TEST-TOPIC-cibuild01, replyTo=topic://clientTopic, from=ClientPillar, to=<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@5e2a3560[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@50edc0d5[correlationID=12345, collectionID=MySla, destination=topic://collectionTopic, replyTo=topic://clientTopic, from=MyPillar, to=<null>, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@54d25e10[responseCode=IDENTIFICATION_POSITIVE, responseText=Ready to delete file 'MyDataID'.], fileID=MyDataID, pillarID=MyPillar, pillarChecksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@11d0caee[checksumType=MD5, checksumSalt={-85,-51}, otherChecksumType=<null>], timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@1e5e6c81[timeMeasureUnit=MILLISECONDS, timeMeasureValue=1000]]
        Step: Send an non-identify request with the 'To' header property set to another component
          Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.DeleteFileRequest@200bfcf7[correlationID=12345, collectionID=MySla, destination=TEST-TOPIC-cibuild01, replyTo=topic://clientTopic, from=ClientPillar, to=<null>, version=28, minVersion=24, auditTrailInformation=User: Name, Institution: Place, pillarID=MyPillar, fileID=MyDataID, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@2c4c0270[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@5c77bf8d[checksumType=MD5, checksumSalt={-85,-85}, otherChecksumType=<null>], checksumValue={19,95,33,86}, calculationTimestamp=2011-02-17T09:47:00], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@5f2544eb[checksumType=MD5, checksumSalt={-85,-51}, otherChecksumType=<null>]]
      Test success: toFilterTest
    Starting testcase CertificateUseExceptionTest
      Test starting: testCertificateUseException
        Description: Test the instantiation of the exception
        Step: Setup
        Step: Try to throw such an exception
        Step: Throw the exception with an embedded exception
      Test success: testCertificateUseException
    Starting testcase ConfigLoaderTest
      Test starting: testLoadingConfig
        Description: Test the loading of a configuration file for the config loader.
        Step: Setup variables
        Step: Test with a invalid file path
        Step: Test when the file is unreadable
        Step: success case
      Test success: testLoadingConfig
    Starting testcase FileIDUtilsTest
      Test starting: fileIDsTest
        Description: Test the utility class for generating FileIDs
        Step: Test 'all file ids'
        Step: Test a specific file id
      Test success: fileIDsTest
      Test starting: utilityTester
        Description: Test that the utility class is a proper utility class.
      Test success: utilityTester
      Test starting: busActivityTest
        Description: Tests whether it is possible to create a message listener, and then set it to listen to the topic. Then puts a messageon the topic for the message listener to find, andtests whether it finds the correct message.
        Step: Send a message to the topic
          Stimuli: Sending message: org.bitrepository.bitrepositorymessages.AlarmMessage@291a4791[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@5b1e88f[origDateTime=2011-05-03T11:18:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>]]
        Step: Make sure both listeners received the message
          Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@666f0438[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@4f367c45[origDateTime=2011-05-03T11:18:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<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@267ff4df[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@7c4b5ceb[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@71ff35a1[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@6fff1c8b[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@1ca8657b[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@5c123e18[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@633bce5d[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@76000ffb[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@71ff35a1[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@6fff1c8b[origDateTime=2011-05-03T11:18:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>]]
02:18:13.781 WARN  o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: 
org.bitrepository.bitrepositorymessages.AlarmMessage@71ff35a1[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@6fff1c8b[origDateTime=2011-05-03T11:18:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>]]
      Test starting: utilityTester
        Description: Test that the utility class is a proper utility class.
      Test success: utilityTester
    Starting testcase ReceivedMessageHandlerTest
      Test starting: manyMessageDispatch
        Description: Tests that many (50) messages can be handled in parallel in the default pool configuration.
        Added fixture: Create a ReceivedMessageHandler with a null configuration. This should create a ReceivedMessageHandler with a single CachedThreadPool.
        Step: Dispatch messages to 49 listeners, where the first 49 are blocking.
        Step: Unblock the blocked listeners
      Test success: manyMessageDispatch
      Test starting: parallelMessageDispatch
        Description: Tests that two messages can be handled in parallel in the default pool configuration.
        Added fixture: Create a ReceivedMessageHandler with a null configuration. This should create a ReceivedMessageHandler with a single CachedThreadPool.
        Step: Dispatch messages to two listeners, the first blocking.
        Step: Unblock the first listener
      Test success: parallelMessageDispatch
      Test starting: singleMessageDispatch
        Description: Tests that a single message is dispatched correctly
      Test success: singleMessageDispatch
      Test starting: singleThreadMessageDispatch
        Description: Tests that two messages will be handled in sequence if a singleThreaded pool is configured.
        Added fixture: Create a ReceivedMessageHandler with a single pool of size 1.
        Step: Dispatch messages to two listeners, the first blocking.
        Step: Unblock the first listener
      Test success: singleThreadMessageDispatch
      Test starting: specificCollectionPoolAndDefaultPool
        Description: Tests it is possible to specify a pool for a specific collection, with a default pool for the remainder.
        Added fixture: Create a ReceivedMessageHandler with a one specific pool for Collection1. The Collection1 pool should be limited to 1 thread.
        Step: Dispatch two messages for collection1, blocking on the processing of the first message.
        Step: Dispatch a message for the other collection.
        Step: Dispatch a message with no collectionID.
        Step: Unblock the blocked collection1 listener
      Test success: specificCollectionPoolAndDefaultPool
      Test starting: specificCollectionPoolWithSpecificMessageTypePool
        Description: Tests it is possible to specify a pool for a specific collection for only a specificmessage type.
        Added fixture: Create a ReceivedMessageHandler with a one specific pool for Collection1 and PutFileRequests. The pool should be limited to 1 thread.
        Step: Dispatch two putFileRequests for collection1, blocking on the processing of the first message.
        Step: Dispatch a putFile request for the other collection.
        Step: Dispatch a status request for collection1.
        Step: Unblock the blocked collection1 listener
      Test success: specificCollectionPoolWithSpecificMessageTypePool
      Test starting: specificMessageCategoryPoolAndDefaultPool
        Description: Tests it is possible to specify a pool for a specific message category, with a default pool for the remainder.
        Added fixture: Create a ReceivedMessageHandler with a one specific pool for slow requests. The put file pool should be limited to 1 thread.
        Step: Dispatch two put messages, blocking on the processing of the first message.
        Step: Dispatch a status request message.
        Step: Unblock the blocked put listener
      Test success: specificMessageCategoryPoolAndDefaultPool
      Test starting: specificMessageNamePoolAndDefaultPool
        Description: Tests it is possible to specify a pool for a specific message type, with a default pool for the remainder.
        Added fixture: Create a ReceivedMessageHandler with a one specific pool for put requests. The put file pool should be limited to 1 thread.
        Step: Dispatch two put messages, blocking on the processing of the first message.
        Step: Dispatch a status request message.
        Step: Unblock the blocked put listener
      Test success: specificMessageNamePoolAndDefaultPool
      Test starting: specificMessagePools
        Description: Tests that different message types can be handled by different executors.
        Added fixture: Create a ReceivedMessageHandler with a two pools, one for status requests and one for put requests. The put file pool should be limited to 1 thread.
        Step: Dispatch two put messages, blocking on the processing of the first message.
        Step: Dispatch a status request message.
        Step: Unblock the blocked put listener
      Test success: specificMessagePools
    Starting testcase SettingsLoaderTest
      Test starting: testDevelopmentCollectionSettingsLoading
      Test success: testDevelopmentCollectionSettingsLoading
      Test starting: testExampleSettingsLoading
      Test success: testExampleSettingsLoading
      Test starting: componentIDTest
      Test success: componentIDTest
      Test starting: reloadTest
      Test success: reloadTest
    Starting testcase Base16UtilsTest
      Test starting: badArgumentTest
        Description: Test bad arguments
        Step: Test with a odd number of characters.
      Test success: badArgumentTest
      Test starting: decodeChecksum
        Description: Validating the decoding of the checksums.
        Step: Decode the checksum and validate.
      Test success: decodeChecksum
      Test starting: encodeChecksum
        Description: Validating the encoding of the checksums.
        Step: Encode the checksum and validate
      Test success: encodeChecksum
      Test starting: utilityTester
        Description: Test that the utility class is a proper utility class.
      Test success: utilityTester
    Starting testcase PermissionStoreTest
      Test starting: certificateFingerprintTest
        Description: Tests that a certificate fingerprint can correctly be retrived for a signer.
        Added fixture: Create signer to lookup fingerprint
        Step: Lookup fingerprint based on signerId
      Test success: certificateFingerprintTest
      Test starting: negativeCertificateRetrievalTest
        Description: Tests that a certificate cannot be retrieved based on the wrong signerId.
        Step: Create signer and modify its ID so lookup will fail
        Step: Lookup certificate based on signerId
      Test success: negativeCertificateRetrievalTest
      Test starting: positiveCertificateRetrievalTest
        Description: Tests that a certificate can be retrieved based on the correct signerId.
        Step: Create signer to lookup certificate
        Step: Lookup certificate based on signerId
      Test success: positiveCertificateRetrievalTest
    Starting testcase SecurityManagerTest
      Test starting: certificateAuthorizationBehaviourTest
        Description: Tests that a certificate is only allowed by registered users (component).
        Step: Check that the registered component is allowed.
        Step: Check that an unregistered component is not allowed.
      Test success: certificateAuthorizationBehaviourTest
      Test starting: negativeSigningAuthenticationRoundtripBadDataTest
        Description: Tests that a roundtrip of signing a request and afterwards authenticating it fails due to bad data
        Description: Tests that a roundtrip of signing a request and afterwards authenticating is succedes.
        Step: Sign a chunck of data.
        Step: Check signature matches the data 
      Test success: negativeSigningAuthenticationRoundtripBadDataTest
      Test starting: negativeSigningAuthenticationRoundtripUnkonwnCertificateTest
        Description: Tests that a roundtrip of signing a request and afterwards authenticating it fails due to a unknown certificate.
        Step: Sign a chunck of data.
        Step: Check signature matches the data
      Test success: negativeSigningAuthenticationRoundtripUnkonwnCertificateTest
      Test starting: operationAuthorizationBehaviourTest
        Description: Tests that a signature only allows the correct requests.
        Step: Check that GET_FILE is allowed.
      Test success: operationAuthorizationBehaviourTest
      Test starting: positiveSigningAuthenticationRoundtripTest
        Description: Tests that a roundtrip of signing a request and afterwards authenticating is succedes.
        Step: Sign a chunck of data.
        Step: Check signature matches the data 
      Test success: positiveSigningAuthenticationRoundtripTest
    Starting testcase UnregisteredPermissionTest
      Test starting: testUnregisteredPermissionException
        Description: Test the instantiation of the exception
        Step: Setup
        Step: Try to throw such an exception
        Step: Throw the exception with an embedded exception
      Test success: testUnregisteredPermissionException
    Starting testcase MessageCreationTest
      Test starting: messageCreationTest
        Description: Tests if we are able to create message objects from xml. The input XML is the example code defined in the message-xml, thereby also testing whether this is valid.
        Step: Creating IdentifyPillarsForGetFileRequest message
        Step: Creating IdentifyPillarsForGetFileResponse message
        Step: Creating GetFileRequest message
        Step: Creating GetFileProgressResponse message
        Step: Creating GetFileFinalResponse message
        Step: Creating IdentifyPillarsForPutFileRequest message
        Step: Creating IdentifyPillarsForPutFileResponse message
        Step: Creating PutFileRequest message
        Step: Creating PutFileProgressResponse message
        Step: Creating PutFileFinalResponse message
        Step: Creating IdentifyPillarsForDeleteFileRequest message
        Step: Creating IdentifyPillarsForDeleteFileResponse message
        Step: Creating DeleteFileRequest message
        Step: Creating DeleteFileProgressResponse message
        Step: Creating DeleteFileFinalResponse message
        Step: Creating IdentifyPillarsForReplaceFileRequest message
        Step: Creating IdentifyPillarsForReplaceFileResponse message
        Step: Creating ReplaceFileRequest message
        Step: Creating ReplaceFileProgressResponse message
        Step: Creating ReplaceFileFinalResponse message
        Step: Creating IdentifyPillarsForGetChecksumsRequest message
        Step: Creating IdentifyPillarsForGetChecksumsResponse message
        Step: Creating GetChecksumsRequest message
        Step: Creating GetChecksumsProgressResponse message
        Step: Creating GetChecksumsFinalResponse message
        Step: Creating IdentifyPillarsForGetFileIDsRequest message
        Step: Creating IdentifyPillarsForGetFileIDsResponse message
        Step: Creating GetFileIDsRequest message
        Step: Creating GetFileIDsProgressResponse message
        Step: Creating GetFileIDsFinalResponse message
        Step: Creating IdentifyContributorsForGetStatusRequest message
        Step: Creating IdentifyContributorsForGetStatusResponse message
        Step: Creating GetStatusRequest message
        Step: Creating GetStatusProgressResponse message
        Step: Creating GetStatusFinalResponse message
        Step: Creating IdentifyContributorsForGetAuditTrailsRequest message
        Step: Creating IdentifyContributorsForGetAuditTrailsResponse message
        Step: Creating GetAuditTrailsRequest message
        Step: Creating GetAuditTrailsProgressResponse message
        Step: Creating GetAuditTrailsFinalResponse message
        Step: Creating AlarmMessage message
      Test success: messageCreationTest
    Starting testcase MultiThreadedMessageBusTest
      Test starting: manyTheadsBeforeFinish
        Description: Tests whether it is possible to start the handling of many threads simultaneously.
        Step: Send one message for each listener
          Stimuli: Sending message: org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileRequest@33f42420[correlationID=12345, collectionID=MySla, destination=BusActivityTest, replyTo=topic://clientTopic, from=ClientPillar, to=<null>, version=28, minVersion=24, auditTrailInformation=User: Name, Institution: Place, fileID=MyDataID]
          Stimuli: Sending message: org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileRequest@33f42420[correlationID=12345, collectionID=MySla, destination=BusActivityTest, replyTo=topic://clientTopic, from=ClientPillar, to=<null>, version=28, minVersion=24, auditTrailInformation=User: Name, Institution: Place, fileID=MyDataID]
          Stimuli: Sending message: org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileRequest@33f42420[correlationID=12345, collectionID=MySla, destination=BusActivityTest, replyTo=topic://clientTopic, from=ClientPillar, to=<null>, version=28, minVersion=24, auditTrailInformation=User: Name, Institution: Place, fileID=MyDataID]
      Test success: manyTheadsBeforeFinish
    Starting testcase TimeMeasurementUtilsTest
      Test starting: testCompareMilliSeconds
        Description: Test the comparison between TimeMeasure units.
      Test success: testCompareMilliSeconds
      Test starting: testCompareMilliSecondsToHours
        Description: Test the comparison between milliseconds and hours.
      Test success: testCompareMilliSecondsToHours
      Test starting: testMaxValue
        Description: Test the Maximum value
      Test success: testMaxValue
      Test starting: utilityTester
        Description: Test that the utility class is a proper utility class.
      Test success: utilityTester
    Starting testcase CalendarUtilsTest
      Test starting: calendarTester
        Description: Test the calendar utility class
        Step: Test the convertion of a date
        Step: Test that a 'null' date is equivalent to epoch
        Step: Test epoch
        Step: Test that a given time in millis is extractable in millis
        Step: Test the 'getNow' function
        Step: Test the reverse conversion, from XMLCalendar to Date
      Test success: calendarTester
      Test starting: utilityTester
        Description: Test that the utility class is a proper utility class.
      Test success: utilityTester
    Starting testcase MessageSignerExceptionTest
      Test starting: testMessageSigningException
        Description: Test the instantiation of the exception
        Step: Setup
        Step: Try to throw such an exception
        Step: Throw the exception with an embedded exception
      Test success: testMessageSigningException
    Starting testcase MessageUtilsTest
      Test starting: testIdentificationResponse
        Description: Tests isIdentifyResponse method in the message utility class.
        Step: validate that it can see a identify response
      Test success: testIdentificationResponse
      Test starting: testPositiveIdentification
        Description: Tests isPositiveIdentifyResponse method in the message utility class.
        Step: validate that it can see a positive identify response
      Test success: testPositiveIdentification
      Test starting: testProgressResponse
        Description: Tests isPositiveProgressResponse method in the message utility class.
        Step: validate progress response
      Test success: testProgressResponse
      Test starting: validateUtilityClass
        Description: Validating that the utility class is actually an utility class.
      Test success: validateUtilityClass
    Starting testcase PermissionStoreExceptionTest
      Test starting: testPermissionStoreException
        Description: Test the instantiation of the exception
        Step: Setup
        Step: Try to throw such an exception
        Step: Throw the exception with an embedded exception
      Test success: testPermissionStoreException
    Starting testcase StreamUtilsTest
      Test starting: streamTester
        Description: Tests the SteamUtils class.
        Step: Setup variables
        Step: Test with null arguments
        Step: Test copying the input stream to the output stream.
      Test success: streamTester
      Test starting: utilityTester
        Description: Test that the utility class is a proper utility class.
      Test success: utilityTester
    Starting testcase FileIDValidatorTest
      Test starting: badRegexTest
        Description: Tests the FileIDValidator handling of bad file id pattern.
        Step: Give the validator a 'null' as allowed file id pattern
        Step: Give the validator an empty string as allowed file id pattern
      Test success: badRegexTest
      Test starting: validatorDefaultTest
        Description: Tests the FileIDValidator class default restrictions. Only the length should fail.
        Step: Setup the validator, where all file ids are allowed at default.
        Step: Test a null as argument
        Step: Test a valid fileID
        Step: Test odd characters
        Step: Test invalid length
        Step: Test too short
      Test success: validatorDefaultTest
      Test starting: validatorTest
        Description: Tests the FileIDValidator class for the input handling based on a given regex.
        Step: Setup the validator
        Step: Test a null as argument
        Step: Test a valid fileID
        Step: Test invalid characters
        Step: Test invalid length
        Step: Test too short
      Test success: validatorTest
    Starting testcase XMLFileSettingsLoaderTest
      Test starting: testCollectionSettingsLoading
      Test success: testCollectionSettingsLoading
    Starting testcase SecurityExceptionTest
      Test starting: testSecurityException
        Description: Test the instantiation of the exception
        Step: Setup
        Step: Try to throw such an exception
        Step: Throw the exception with an embedded exception
      Test success: testSecurityException
    Starting testcase ResponseInfoUtilsTest
      Test starting: responseInfoTester
        Description: Test the response info.
        Step: Validate the positive identification response
        Step: Validate the Progress response
      Test success: responseInfoTester
      Test starting: utilityTester
        Description: Test that the utility class is a proper utility class.
      Test success: utilityTester
      Finished testcase
02:18:26.375 ERROR o.b.protocol.bus.RawMessagebus - JMSException caught: 
javax.jms.JMSException: java.io.EOFException
	at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:54) ~[activemq-client-5.12.1.jar:5.12.1]
	at org.apache.activemq.ActiveMQConnection.onAsyncException(ActiveMQConnection.java:1972) ~[activemq-client-5.12.1.jar:5.12.1]
	at org.apache.activemq.ActiveMQConnection.onException(ActiveMQConnection.java:1991) ~[activemq-client-5.12.1.jar:5.12.1]
	at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:101) ~[activemq-client-5.12.1.jar:5.12.1]
	at org.apache.activemq.transport.ResponseCorrelator.onException(ResponseCorrelator.java:126) ~[activemq-client-5.12.1.jar:5.12.1]
	at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:101) ~[activemq-client-5.12.1.jar:5.12.1]
	at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:101) ~[activemq-client-5.12.1.jar:5.12.1]
	at org.apache.activemq.transport.WireFormatNegotiator.onException(WireFormatNegotiator.java:160) ~[activemq-client-5.12.1.jar:5.12.1]
	at org.apache.activemq.transport.AbstractInactivityMonitor.onException(AbstractInactivityMonitor.java:344) ~[activemq-client-5.12.1.jar:5.12.1]
	at org.apache.activemq.transport.TransportSupport.onException(TransportSupport.java:96) ~[activemq-client-5.12.1.jar:5.12.1]
	at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:200) ~[activemq-client-5.12.1.jar:5.12.1]
	at java.lang.Thread.run(Thread.java:745) [na:1.8.0_11]
Caused by: java.io.EOFException: null
	at java.io.DataInputStream.readInt(DataInputStream.java:392) ~[na:1.8.0_11]
	at org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:267) ~[activemq-client-5.12.1.jar:5.12.1]
	at org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:221) ~[activemq-client-5.12.1.jar:5.12.1]
	at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:213) ~[activemq-client-5.12.1.jar:5.12.1]
	at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:196) ~[activemq-client-5.12.1.jar:5.12.1]
	... 1 common frames omitted
02:18:26.520 ERROR o.b.protocol.bus.RawMessagebus - JMSException caught: 
javax.jms.JMSException: java.io.EOFException
	at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:54) ~[activemq-client-5.12.1.jar:5.12.1]
	at org.apache.activemq.ActiveMQConnection.onAsyncException(ActiveMQConnection.java:1972) ~[activemq-client-5.12.1.jar:5.12.1]
	at org.apache.activemq.ActiveMQConnection.onException(ActiveMQConnection.java:1991) ~[activemq-client-5.12.1.jar:5.12.1]
	at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:101) ~[activemq-client-5.12.1.jar:5.12.1]
	at org.apache.activemq.transport.ResponseCorrelator.onException(ResponseCorrelator.java:126) ~[activemq-client-5.12.1.jar:5.12.1]
	at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:101) ~[activemq-client-5.12.1.jar:5.12.1]
	at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:101) ~[activemq-client-5.12.1.jar:5.12.1]
	at org.apache.activemq.transport.WireFormatNegotiator.onException(WireFormatNegotiator.java:160) ~[activemq-client-5.12.1.jar:5.12.1]
	at org.apache.activemq.transport.AbstractInactivityMonitor.onException(AbstractInactivityMonitor.java:344) ~[activemq-client-5.12.1.jar:5.12.1]
	at org.apache.activemq.transport.TransportSupport.onException(TransportSupport.java:96) ~[activemq-client-5.12.1.jar:5.12.1]
	at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:200) ~[activemq-client-5.12.1.jar:5.12.1]
	at java.lang.Thread.run(Thread.java:745) [na:1.8.0_11]
Caused by: java.io.EOFException: null
	at java.io.DataInputStream.readInt(DataInputStream.java:392) ~[na:1.8.0_11]
	at org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:267) ~[activemq-client-5.12.1.jar:5.12.1]
	at org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:221) ~[activemq-client-5.12.1.jar:5.12.1]
	at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:213) ~[activemq-client-5.12.1.jar:5.12.1]
	at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:196) ~[activemq-client-5.12.1.jar:5.12.1]
	... 1 common frames omitted
02:18:26.539 ERROR o.b.protocol.bus.RawMessagebus - JMSException caught: 
javax.jms.JMSException: java.io.EOFException
	at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:54) ~[activemq-client-5.12.1.jar:5.12.1]
	at org.apache.activemq.ActiveMQConnection.onAsyncException(ActiveMQConnection.java:1972) ~[activemq-client-5.12.1.jar:5.12.1]
	at org.apache.activemq.ActiveMQConnection.onException(ActiveMQConnection.java:1991) ~[activemq-client-5.12.1.jar:5.12.1]
	at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:101) ~[activemq-client-5.12.1.jar:5.12.1]
	at org.apache.activemq.transport.ResponseCorrelator.onException(ResponseCorrelator.java:126) ~[activemq-client-5.12.1.jar:5.12.1]
	at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:101) ~[activemq-client-5.12.1.jar:5.12.1]
	at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:101) ~[activemq-client-5.12.1.jar:5.12.1]
	at org.apache.activemq.transport.WireFormatNegotiator.onException(WireFormatNegotiator.java:160) ~[activemq-client-5.12.1.jar:5.12.1]
	at org.apache.activemq.transport.AbstractInactivityMonitor.onException(AbstractInactivityMonitor.java:344) ~[activemq-client-5.12.1.jar:5.12.1]
	at org.apache.activemq.transport.TransportSupport.onException(TransportSupport.java:96) ~[activemq-client-5.12.1.jar:5.12.1]
	at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:200) ~[activemq-client-5.12.1.jar:5.12.1]
	at java.lang.Thread.run(Thread.java:745) [na:1.8.0_11]
Caused by: java.io.EOFException: null
	at java.io.DataInputStream.readInt(DataInputStream.java:392) ~[na:1.8.0_11]
	at org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:267) ~[activemq-client-5.12.1.jar:5.12.1]
	at org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:221) ~[activemq-client-5.12.1.jar:5.12.1]
	at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:213) ~[activemq-client-5.12.1.jar:5.12.1]
	at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:196) ~[activemq-client-5.12.1.jar:5.12.1]
	... 1 common frames omitted
  Finished suite
Finished project
Tests run: 95, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 33.445 sec - in TestSuite

Results :

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

[JENKINS] Recording test results
log4j:WARN No appenders could be found for logger (org.apache.commons.beanutils.converters.BooleanConverter).
log4j:WARN Please initialize the log4j system properly.
[JENKINS] Archiving disabled
[INFO] 
[INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ bitrepository-core ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-core/target/bitrepository-core-1.6-SNAPSHOT.jar
[INFO] 
[INFO] --- maven-jar-plugin:2.4:test-jar (default) @ bitrepository-core ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-core/target/bitrepository-core-1.6-SNAPSHOT-tests.jar
[INFO] 
[INFO] --- maven-source-plugin:2.2.1:jar-no-fork (attach-sources-no-fork) @ bitrepository-core ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-core/target/bitrepository-core-1.6-SNAPSHOT-sources.jar
[INFO] 
[INFO] --- maven-install-plugin:2.5.1:install (default-install) @ bitrepository-core ---
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-core/target/bitrepository-core-1.6-SNAPSHOT.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-core/1.6-SNAPSHOT/bitrepository-core-1.6-SNAPSHOT.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-core/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-core/1.6-SNAPSHOT/bitrepository-core-1.6-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-core/target/bitrepository-core-1.6-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-core/1.6-SNAPSHOT/bitrepository-core-1.6-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-core/target/bitrepository-core-1.6-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-core/1.6-SNAPSHOT/bitrepository-core-1.6-SNAPSHOT-sources.jar