Verifies the integrety of the projects, as builds are executed immediately after a code change was detected. This plan provides no artifiacts (use a nightly build instead).

Build: #2560 was successful Changes by Guus der Kinderen

Build result summary

Details

Completed
Queue duration
< 1 second
Duration
11 minutes
Labels
None
Agent
Default Agent
Revision
d83b5ec0e517dc114b48c1359ac84457d1028a56
Total tests
1396
Successful since
#2551 ()

Tests

Code commits

Author Commit Message Commit date
Guus der Kinderen Guus der Kinderen 86e4fec01bf94a71658ec8f9a73c2c3d38dde5d0 OF-2651: Give distinct names to Netty threads
Netty uses various Executor services, that each generate threads. These threads are given a default name, which leads to thread names like: `nioEventLoopGroup-4-1`

This name is not very descriptive. It is helpful, for debugging purposes, to have a name that identifies the source / functionality that relates to the a particular thread.

This commit restores the naming that was used prior to switching to Netty.
Guus der Kinderen Guus der Kinderen 672d06601e6cf998765dda3a0ebe32a4704d0b6c OF-2788: (re)introduce threadpool per IO type
Prior to introducing Netty, every connection type (client, component, server) had its own thread pool that was used for processing inbound data.

This commit re-introduces that concept.
Guus der Kinderen Guus der Kinderen d83b5ec0e517dc114b48c1359ac84457d1028a56 Remove old, unused MINA references
With the replacement of MINA with Netty, these references are no longer in use.
Guus der Kinderen Guus der Kinderen d39fc74eb2fdbb20e3692c175f710ec1ed0808b0 Add JIRA refererences to IPv6-related TODO comments

Jira issues

IssueDescriptionStatus
Unknown Issue TypeOF-2651Could not obtain issue details from Jira
Unknown Issue TypeOF-2788Could not obtain issue details from Jira