[INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building Bitrepository Core 1.10-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] Downloading: https://sbforge.org/nexus/content/groups/public/org/bitrepository/bitrepository-message-xml-xsd/31-SNAPSHOT/maven-metadata.xml [INFO] Downloaded: https://sbforge.org/nexus/content/groups/public/org/bitrepository/bitrepository-message-xml-xsd/31-SNAPSHOT/maven-metadata.xml (1002 B at 36.2 KB/sec) [INFO] Downloading: https://sbforge.org/nexus/content/groups/public/org/bitrepository/bitrepository-message-xml/31-SNAPSHOT/maven-metadata.xml [INFO] Downloaded: https://sbforge.org/nexus/content/groups/public/org/bitrepository/bitrepository-message-xml/31-SNAPSHOT/maven-metadata.xml (615 B at 33.4 KB/sec) [INFO] Downloading: https://sbforge.org/nexus/content/groups/public/org/bitrepository/bitrepository-message-xml-java/31-SNAPSHOT/maven-metadata.xml [INFO] Downloaded: https://sbforge.org/nexus/content/groups/public/org/bitrepository/bitrepository-message-xml-java/31-SNAPSHOT/maven-metadata.xml (1003 B at 54.4 KB/sec) [INFO] [INFO] --- maven-clean-plugin:3.1.0:clean (default-clean) @ bitrepository-core --- [INFO] [INFO] --- maven-enforcer-plugin:3.0.0-M3:enforce (enforce-maven) @ bitrepository-core --- [INFO] [INFO] --- jacoco-maven-plugin:0.8.5:prepare-agent (default) @ bitrepository-core --- [INFO] argLine set to -javaagent:/home/cibuild01/.m2/repository/org/jacoco/org.jacoco.agent/0.8.5/org.jacoco.agent-0.8.5-runtime.jar=destfile=/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-core/target/jacoco.exec [INFO] [INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ bitrepository-core --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 2 resources [INFO] [INFO] --- maven-compiler-plugin:3.8.1:compile (default-compile) @ bitrepository-core --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 91 source files to /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-core/target/classes [WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-core/src/main/java/org/bitrepository/protocol/security/BasicSecurityManager.java:[196,40] redundant cast to org.bouncycastle.cms.SignerInformation [WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-core/src/main/java/org/bitrepository/protocol/security/BasicSecurityManager.java:[224,40] redundant cast to org.bouncycastle.cms.SignerInformation [WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-core/src/main/java/org/bitrepository/protocol/security/BasicMessageAuthenticator.java:[59,40] redundant cast to org.bouncycastle.cms.SignerInformation [WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-core/src/main/java/org/bitrepository/common/settings/XMLFileSettingsLoader.java:[97,24] redundant cast to T [INFO] [INFO] --- forbiddenapis:2.7:check (default) @ bitrepository-core --- [INFO] Scanning for classes to check... [INFO] Reading bundled API signatures: jdk-unsafe-1.8 [INFO] Reading bundled API signatures: jdk-deprecated-1.8 [INFO] Reading bundled API signatures: jdk-non-portable [INFO] Reading bundled API signatures: jdk-reflection [INFO] Loading classes to check... [INFO] Scanning classes for violations... [INFO] Scanned 101 class file(s) for forbidden API invocations (in 0.46s), 0 error(s). [INFO] [INFO] --- forbiddenapis:2.7:testCheck (default) @ bitrepository-core --- [INFO] Scanning for classes to check... [WARNING] Classes directory does not exist, forbiddenapis check skipped: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-core/target/test-classes [INFO] [INFO] --- maven-resources-plugin:3.1.0:testResources (default-testResources) @ bitrepository-core --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 11 resources [INFO] [INFO] --- maven-compiler-plugin:3.8.1:testCompile (default-testCompile) @ bitrepository-core --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 66 source files to /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-core/target/test-classes [WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-core/src/test/java/org/bitrepository/common/DefaultThreadFactoryTest.java:[33,58] unchecked conversion required: ch.qos.logback.core.Appender found: ch.qos.logback.core.Appender [WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-core/src/test/java/org/bitrepository/protocol/fileexchange/LocalFileExchangeTest.java:[131,37] toString(java.io.InputStream) in org.apache.commons.io.IOUtils has been deprecated [WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-core/src/test/java/org/bitrepository/protocol/security/CertificateIDTest.java:[60,36] redundant cast to org.bouncycastle.cms.SignerInformation [WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-core/src/test/java/org/bitrepository/protocol/security/CertificateIDTest.java:[85,36] redundant cast to org.bouncycastle.cms.SignerInformation [WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-core/src/test/java/org/bitrepository/protocol/message/ExampleMessageFactory.java:[60,23] toString(java.io.InputStream) in org.apache.commons.io.IOUtils has been deprecated [WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-core/src/test/java/org/bitrepository/protocol/MessageCreationTest.java:[76,33] toString(java.io.InputStream) in org.apache.commons.io.IOUtils has been deprecated [WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-core/src/test/java/org/bitrepository/protocol/security/PermissionStoreTest.java:[60,36] redundant cast to org.bouncycastle.cms.SignerInformation [WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-core/src/test/java/org/bitrepository/protocol/security/PermissionStoreTest.java:[78,36] redundant cast to org.bouncycastle.cms.SignerInformation [WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-core/src/test/java/org/bitrepository/protocol/security/PermissionStoreTest.java:[110,36] redundant cast to org.bouncycastle.cms.SignerInformation [INFO] [INFO] --- maven-surefire-plugin:3.0.0-M4:test (default-test) @ bitrepository-core --- [INFO] [INFO] ------------------------------------------------------- [INFO] T E S T S [INFO] ------------------------------------------------------- [INFO] Running TestSuite 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 CalendarUtilsTest Test starting: calendarTester Description: Test the calendar utility class Step: Test the convertion of a date Step: Test that a 'null' date is equivalent to epoch Step: Test epoch Step: Test that a given time in millis is extractable in millis Step: Test the 'getNow' function Step: Test the reverse conversion, from XMLCalendar to Date Test success: calendarTester Test starting: endDateRolloverTest Description: Test that the end date is correctly rolls over a year and month change. Test success: endDateRolloverTest Test starting: endDateTest Description: Test that the end date is considered as localtime and converted into UTC. Test success: endDateTest Test starting: startDateTest Description: Test that the start date is considered as localtime and converted into UTC. Test success: startDateTest Test starting: testBeginningOfDay Description: Tests that the time is converted to the beginning of the day localtime, not UTC expectedSTartofDayInUTC parsed: 1454281200000 Test success: testBeginningOfDay Test starting: testEndOfDay Description: Tests that the time is converted to the beginning of the day localtime, not UTC Test success: testEndOfDay Test starting: testSummerWinterTimeChange Description: Test that the interval between start and end date on a summertime to wintertime change is 25 hours (-1 millisecond). Test success: testSummerWinterTimeChange Test starting: testWinterSummerTimeChange Description: Test that the interval between start and end date on a wintertime to summertime change is 23 hours (-1 millisecond). Test success: testWinterSummerTimeChange Starting testcase 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 FileUtilsTest Test starting: cleanupEmptyDirectoriesTester Description: Test the cleanup of empty directories. Step: Cleanup non-empty folder Step: Cleanup when dir and root are the same Step: Test succes case, when the directory is empty Step: Test with a file. Test success: cleanupEmptyDirectoriesTester Test starting: createDeleteDirectoryTester Description: Test the ability to delete directories. Step: Test deleting a directory with file and subdirectory Test success: createDeleteDirectoryTester Test starting: createDirectoryTester Description: Test the ability to create directories. Step: Test the ability to create a directory Step: Test error scenarios, when the directory path is a file Test success: createDirectoryTester Test starting: createSubDirectoryTester Description: Test the ability to create sub directories. Step: Test the ability to create sub-directories Step: Test that it fails if the 'directory' is actually a file Step: Test that it fails, if the parent directory does not allow writing Test success: createSubDirectoryTester Test starting: deprecateFileTester Description: Test the deprecation of a file. Step: Setup Step: Deprecate the file Test success: deprecateFileTester Test starting: moveFileTester Description: Test the moving of a file. Step: Setup Step: Move the file Test success: moveFileTester Test starting: unzipFileTester Description: Test unzipping a file. Step: Setup Step: Unzip the zipfile to the directory Test success: unzipFileTester Test starting: utilityTester Description: Test that the utility class is a proper utility class. Test success: utilityTester Test starting: writeInputstreamTester Description: Test writing an inputstream to a file. Step: Setup Step: Write the input stream to the file Test success: writeInputstreamTester Starting testcase 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@2213854b[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=(default), version=31, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@6c2be147[origDateTime=2011-05-03T11:18:00Z, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=(default)]] 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@43201f84[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=(default), version=31, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@2c51c756[origDateTime=2011-05-03T11:18:00Z, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=(default)]] Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@43201f84[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=(default), version=31, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@2c51c756[origDateTime=2011-05-03T11:18:00Z, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=(default)]] Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@43201f84[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=(default), version=31, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@2c51c756[origDateTime=2011-05-03T11:18:00Z, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=(default)]] 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@43201f84[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=(default), version=31, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@2c51c756[origDateTime=2011-05-03T11:18:00Z, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=(default)]] 13:43:36.717 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: org.bitrepository.bitrepositorymessages.AlarmMessage@43201f84[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=(default), version=31, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@2c51c756[origDateTime=2011-05-03T11:18:00Z, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=(default)]] 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 MessageCreationTest Test starting: badDateMessageTest Description: Test to ensure that messages carrying dates must provide offset. Test success: badDateMessageTest Test starting: messageCreationTest Description: Tests if we are able to create message objects from xml. The input XML is the example code defined in the message-xml, thereby also testing whether this is valid. Step: Creating IdentifyPillarsForGetFileRequest message Step: Creating IdentifyPillarsForGetFileResponse message Step: Creating GetFileRequest message Step: Creating GetFileProgressResponse message Step: Creating GetFileFinalResponse message Step: Creating IdentifyPillarsForPutFileRequest message Step: Creating IdentifyPillarsForPutFileResponse message Step: Creating PutFileRequest message Step: Creating PutFileProgressResponse message Step: Creating PutFileFinalResponse message Step: Creating IdentifyPillarsForDeleteFileRequest message Step: Creating IdentifyPillarsForDeleteFileResponse message Step: Creating DeleteFileRequest message Step: Creating DeleteFileProgressResponse message Step: Creating DeleteFileFinalResponse message Step: Creating IdentifyPillarsForReplaceFileRequest message Step: Creating IdentifyPillarsForReplaceFileResponse message Step: Creating ReplaceFileRequest message Step: Creating ReplaceFileProgressResponse message Step: Creating ReplaceFileFinalResponse message Step: Creating IdentifyPillarsForGetChecksumsRequest message Step: Creating IdentifyPillarsForGetChecksumsResponse message Step: Creating GetChecksumsRequest message Step: Creating GetChecksumsProgressResponse message Step: Creating GetChecksumsFinalResponse message Step: Creating IdentifyPillarsForGetFileIDsRequest message Step: Creating IdentifyPillarsForGetFileIDsResponse message Step: Creating GetFileIDsRequest message Step: Creating GetFileIDsProgressResponse message Step: Creating GetFileIDsFinalResponse message Step: Creating IdentifyContributorsForGetStatusRequest message Step: Creating IdentifyContributorsForGetStatusResponse message Step: Creating GetStatusRequest message Step: Creating GetStatusProgressResponse message Step: Creating GetStatusFinalResponse message Step: Creating IdentifyContributorsForGetAuditTrailsRequest message Step: Creating IdentifyContributorsForGetAuditTrailsResponse message Step: Creating GetAuditTrailsRequest message Step: Creating GetAuditTrailsProgressResponse message Step: Creating GetAuditTrailsFinalResponse message Step: Creating AlarmMessage message Test success: messageCreationTest Starting testcase 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 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 13:43:44.614 WARN o.a.activemq.broker.BrokerService - Memory Usage for the Broker (1024mb) is more than the maximum available for the JVM: 444 mb - resetting to 70% of maximum available: 311 mb 13:43:45.098 WARN o.a.activemq.broker.BrokerService - Temporary Store limit is 51200 mb (current store usage is 0 mb). The data directory: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-core/target only has 1609 mb of usable space. - resetting to maximum available disk space: 1609 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@59c92f61[correlationID=12345, collectionID=MyCollection, destination=topic://collectionTopic, replyTo=topic://clientTopic, from=ClientPillar, to=(default), version=31, 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@570eca28[correlationID=12345, collectionID=MyCollection, destination=topic://collectionTopic, replyTo=topic://clientTopic, from=ClientPillar, to=(default), version=31, 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@6ec6adcc[correlationID=12345, collectionID=MySla, destination=TEST-TOPIC-cibuild01, replyTo=topic://clientTopic, from=ClientPillar, to=specificReceiver, version=31, minVersion=24, auditTrailInformation=User: Name, Institution: Place, fileID=MyDataID] Test success: sendMessageToSpecificComponentTest Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@53314411[correlationID=12345, collectionID=MySla, destination=TEST-TOPIC-cibuild01, replyTo=topic://clientTopic, from=ClientPillar, to=specificReceiver, version=31, minVersion=24, auditTrailInformation=User: Name, Institution: Place, fileID=MyDataID] Result: The following messages haven't been handled by the testcase: org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@53314411[correlationID=12345, collectionID=MySla, destination=TEST-TOPIC-cibuild01, replyTo=topic://clientTopic, from=ClientPillar, to=specificReceiver, version=31, minVersion=24, auditTrailInformation=User: Name, Institution: Place, fileID=MyDataID] 13:43:48.307 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@53314411[correlationID=12345, collectionID=MySla, destination=TEST-TOPIC-cibuild01, replyTo=topic://clientTopic, from=ClientPillar, to=specificReceiver, version=31, 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@1633c013[correlationID=12345, collectionID=MySla, destination=TEST-TOPIC-cibuild01, replyTo=topic://clientTopic, from=ClientPillar, to=(default), version=31, 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@6115793[correlationID=12345, collectionID=MySla, destination=TEST-TOPIC-cibuild01, replyTo=topic://clientTopic, from=ClientPillar, to=(default), version=31, 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@276f92f3[correlationID=12345, collectionID=MySla, destination=topic://clientTopic, replyTo=queue://pillarQueue, from=MyPillar, to=(default), version=31, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@7ea75bc3[responseCode=IDENTIFICATION_POSITIVE, responseText=Ready to delete file 'MyDataID'.], fileID=MyDataID, pillarID=MyPillar, pillarChecksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@761c3f5c[checksumType=MD5, checksumSalt={-85,-51}, otherChecksumType=(default)], timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@7abd43c3[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@219eae6d[correlationID=12345, collectionID=MySla, destination=TEST-TOPIC-cibuild01, replyTo=topic://clientTopic, from=ClientPillar, to=(default), version=31, minVersion=24, auditTrailInformation=User: Name, Institution: Place, pillarID=MyPillar, fileID=MyDataID, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@56c056c0[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2ec09ad4[checksumType=MD5, checksumSalt={-85,-85}, otherChecksumType=(default)], checksumValue={19,95,33,86}, calculationTimestamp=2011-02-17T09:47:00.000+01:00], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2c8da091[checksumType=MD5, checksumSalt={-85,-51}, otherChecksumType=(default)]] Test success: toFilterTest 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 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 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@3fd2dbe2[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=(default), version=31, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@55f2a26d[origDateTime=2011-05-03T11:18:00Z, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=(default)]] Step: Make sure both listeners received the message Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@65a390de[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=(default), version=31, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@2f1f3101[origDateTime=2011-05-03T11:18:00Z, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=(default)]] Test success: busActivityTest Test starting: twoListenersForTopicTest Description: Verifies that two listeners on the same topic both receive the message Step: Make a connection to the message bus and add two listeners Step: Send a message to the topic Stimuli: Sending message: org.bitrepository.bitrepositorymessages.AlarmMessage@578a1c1a[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=(default), version=31, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@526388ee[origDateTime=2011-05-03T11:18:00Z, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=(default)]] Step: Make sure both listeners received the message Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@7252a5e9[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=(default), version=31, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@38ed34bc[origDateTime=2011-05-03T11:18:00Z, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=(default)]] Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@62e1533b[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=(default), version=31, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@268cea3c[origDateTime=2011-05-03T11:18:00Z, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=(default)]] Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@36d874cc[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=(default), version=31, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@154fd912[origDateTime=2011-05-03T11:18:00Z, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=(default)]] Test success: twoListenersForTopicTest Result: The following messages haven't been handled by the testcase: org.bitrepository.bitrepositorymessages.AlarmMessage@7252a5e9[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=(default), version=31, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@38ed34bc[origDateTime=2011-05-03T11:18:00Z, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=(default)]] 13:43:52.909 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: org.bitrepository.bitrepositorymessages.AlarmMessage@7252a5e9[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=(default), version=31, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@38ed34bc[origDateTime=2011-05-03T11:18:00Z, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=(default)]] Test starting: utilityTester Description: Test that the utility class is a proper utility class. Test success: utilityTester 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 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 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 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 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 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 SecurityManagerTest Test starting: certificateAuthorizationBehaviourTest Description: Tests that a certificate is only allowed by registered users (component). Step: Check that the registered component is allowed. Step: Check that an unregistered component is not allowed. Test success: certificateAuthorizationBehaviourTest Test starting: negativeSigningAuthenticationRoundtripBadDataTest Description: Tests that a roundtrip of signing a request and afterwards authenticating it fails due to bad data Description: Tests that a roundtrip of signing a request and afterwards authenticating is succedes. Step: Sign a chunck of data. Step: Check signature matches the data Test success: negativeSigningAuthenticationRoundtripBadDataTest Test starting: negativeSigningAuthenticationRoundtripUnkonwnCertificateTest Description: Tests that a roundtrip of signing a request and afterwards authenticating it fails due to a unknown certificate. Step: Sign a chunck of data. Step: Check signature matches the data Test success: negativeSigningAuthenticationRoundtripUnkonwnCertificateTest Test starting: operationAuthorizationBehaviourTest Description: Tests that a signature only allows the correct requests. Step: Check that PUT_FILE is allowed for both collections. Step: Check that GET_FILE is only allowed for the first collection. Test success: operationAuthorizationBehaviourTest Test starting: positiveSigningAuthenticationRoundtripTest Description: Tests that a roundtrip of signing a request and afterwards authenticating is succedes. Step: Sign a chunck of data. Step: Check signature matches the data Test success: positiveSigningAuthenticationRoundtripTest Starting testcase 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 Test starting: testUncaughtExceptionHandler 13:43:58.690 ERROR o.b.common.DefaultThreadFactoryTest - UncaughtExceptionHandler caught Exception: java.lang.RuntimeException: Hey this is the message I want to see at org.bitrepository.common.DefaultThreadFactoryTest.lambda$testUncaughtExceptionHandler$0(DefaultThreadFactoryTest.java:50) at java.lang.Thread.run(Thread.java:745) Test success: testUncaughtExceptionHandler Starting testcase 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 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 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 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 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 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@3d64f938[correlationID=12345, collectionID=MySla, destination=BusActivityTest, replyTo=topic://clientTopic, from=ClientPillar, to=(default), version=31, minVersion=24, auditTrailInformation=User: Name, Institution: Place, fileID=MyDataID] Stimuli: Sending message: org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileRequest@3d64f938[correlationID=12345, collectionID=MySla, destination=BusActivityTest, replyTo=topic://clientTopic, from=ClientPillar, to=(default), version=31, minVersion=24, auditTrailInformation=User: Name, Institution: Place, fileID=MyDataID] Stimuli: Sending message: org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileRequest@3d64f938[correlationID=12345, collectionID=MySla, destination=BusActivityTest, replyTo=topic://clientTopic, from=ClientPillar, to=(default), version=31, minVersion=24, auditTrailInformation=User: Name, Institution: Place, fileID=MyDataID] Test success: manyTheadsBeforeFinish 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 SettingsLoaderTest Test starting: testDevelopmentCollectionSettingsLoading Test success: testDevelopmentCollectionSettingsLoading Test starting: testExampleSettingsLoading Test success: testExampleSettingsLoading Finished testcase 13:44:00.688 ERROR o.b.protocol.bus.RawMessagebus - JMSException caught: javax.jms.JMSException: java.io.EOFException at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:54) at org.apache.activemq.ActiveMQConnection.onAsyncException(ActiveMQConnection.java:1960) at org.apache.activemq.ActiveMQConnection.onException(ActiveMQConnection.java:1979) at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:114) at org.apache.activemq.transport.ResponseCorrelator.onException(ResponseCorrelator.java:126) at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:114) at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:114) at org.apache.activemq.transport.WireFormatNegotiator.onException(WireFormatNegotiator.java:173) at org.apache.activemq.transport.AbstractInactivityMonitor.onException(AbstractInactivityMonitor.java:345) at org.apache.activemq.transport.TransportSupport.onException(TransportSupport.java:96) at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:219) at java.lang.Thread.run(Thread.java:745) Caused by: java.io.EOFException: null at java.io.DataInputStream.readInt(DataInputStream.java:392) at org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:268) at org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:240) at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:232) at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:215) ... 1 common frames omitted 13:44:00.702 ERROR o.b.protocol.bus.RawMessagebus - JMSException caught: javax.jms.JMSException: java.io.EOFException at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:54) at org.apache.activemq.ActiveMQConnection.onAsyncException(ActiveMQConnection.java:1960) at org.apache.activemq.ActiveMQConnection.onException(ActiveMQConnection.java:1979) at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:114) at org.apache.activemq.transport.ResponseCorrelator.onException(ResponseCorrelator.java:126) at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:114) at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:114) at org.apache.activemq.transport.WireFormatNegotiator.onException(WireFormatNegotiator.java:173) at org.apache.activemq.transport.AbstractInactivityMonitor.onException(AbstractInactivityMonitor.java:345) at org.apache.activemq.transport.TransportSupport.onException(TransportSupport.java:96) at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:219) at java.lang.Thread.run(Thread.java:745) Caused by: java.io.EOFException: null at java.io.DataInputStream.readInt(DataInputStream.java:392) at org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:268) at org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:240) at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:232) at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:215) ... 1 common frames omitted 13:44:00.721 ERROR o.b.protocol.bus.RawMessagebus - JMSException caught: javax.jms.JMSException: java.io.EOFException at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:54) at org.apache.activemq.ActiveMQConnection.onAsyncException(ActiveMQConnection.java:1960) at org.apache.activemq.ActiveMQConnection.onException(ActiveMQConnection.java:1979) at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:114) at org.apache.activemq.transport.ResponseCorrelator.onException(ResponseCorrelator.java:126) at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:114) at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:114) at org.apache.activemq.transport.WireFormatNegotiator.onException(WireFormatNegotiator.java:173) at org.apache.activemq.transport.AbstractInactivityMonitor.onException(AbstractInactivityMonitor.java:345) at org.apache.activemq.transport.TransportSupport.onException(TransportSupport.java:96) at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:219) at java.lang.Thread.run(Thread.java:745) Caused by: java.io.EOFException: null at java.io.DataInputStream.readInt(DataInputStream.java:392) at org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:268) at org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:240) at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:232) at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:215) ... 1 common frames omitted Finished suite Finished project [INFO] Tests run: 104, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 29.846 s - in TestSuite [INFO] [INFO] Results: [INFO] [INFO] Tests run: 104, Failures: 0, Errors: 0, Skipped: 0 [INFO] [JENKINS] Recording test results log4j:WARN No appenders could be found for logger (org.apache.commons.beanutils.converters.BooleanConverter). log4j:WARN Please initialize the log4j system properly. [INFO] [INFO] --- jacoco-maven-plugin:0.8.5:report (report) @ bitrepository-core --- [INFO] Loading execution data file /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-core/target/jacoco.exec [INFO] Analyzed bundle 'Bitrepository Core' with 86 classes [INFO] [INFO] --- maven-jar-plugin:3.2.0:jar (default-jar) @ bitrepository-core --- [INFO] Building jar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-core/target/bitrepository-core-1.10-SNAPSHOT.jar [INFO] [INFO] --- maven-jar-plugin:3.2.0:test-jar (default) @ bitrepository-core --- [INFO] Building jar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-core/target/bitrepository-core-1.10-SNAPSHOT-tests.jar [INFO] [INFO] --- maven-source-plugin:3.2.1:jar-no-fork (attach-sources-no-fork) @ bitrepository-core --- [INFO] Building jar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-core/target/bitrepository-core-1.10-SNAPSHOT-sources.jar [INFO] [INFO] --- maven-install-plugin:3.0.0-M1:install (default-install) @ bitrepository-core --- [INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-core/target/bitrepository-core-1.10-SNAPSHOT.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-core/1.10-SNAPSHOT/bitrepository-core-1.10-SNAPSHOT.jar [INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-core/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-core/1.10-SNAPSHOT/bitrepository-core-1.10-SNAPSHOT.pom [INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-core/target/bitrepository-core-1.10-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-core/1.10-SNAPSHOT/bitrepository-core-1.10-SNAPSHOT-tests.jar [INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-core/target/bitrepository-core-1.10-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-core/1.10-SNAPSHOT/bitrepository-core-1.10-SNAPSHOT-sources.jar [INFO] [INFO] --- maven-deploy-plugin:3.0.0-M1:deploy (default-deploy) @ bitrepository-core --- [INFO] Downloading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-core/1.10-SNAPSHOT/maven-metadata.xml [INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-core/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 49.7 KB/sec) [INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-core/1.10-SNAPSHOT/bitrepository-core-1.10-20220215.124405-64.jar [INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-core/1.10-SNAPSHOT/bitrepository-core-1.10-20220215.124405-64.jar (146 KB at 3169.2 KB/sec) [INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-core/1.10-SNAPSHOT/bitrepository-core-1.10-20220215.124405-64.pom [INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-core/1.10-SNAPSHOT/bitrepository-core-1.10-20220215.124405-64.pom (4 KB at 109.9 KB/sec) [INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-core/1.10-SNAPSHOT/bitrepository-core-1.10-20220215.124405-64-tests.jar [INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-core/1.10-SNAPSHOT/bitrepository-core-1.10-20220215.124405-64-tests.jar (169 KB at 4203.6 KB/sec) [INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-core/1.10-SNAPSHOT/bitrepository-core-1.10-20220215.124405-64-sources.jar [INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-core/1.10-SNAPSHOT/bitrepository-core-1.10-20220215.124405-64-sources.jar (142 KB at 4053.5 KB/sec) [INFO] Downloading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-core/maven-metadata.xml [INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-core/maven-metadata.xml (482 B at 47.1 KB/sec) [INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-core/1.10-SNAPSHOT/maven-metadata.xml [INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-core/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 31.4 KB/sec) [INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-core/maven-metadata.xml [INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-core/maven-metadata.xml (482 B at 15.7 KB/sec) [JENKINS] Archiving disabled