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: #2715 was successful Changes by daryl herzmann and Guus der Kinderen

Stages & jobs

  1. Default Stage

  2. Continuous Integration

Build result summary

Details

Completed
Queue duration
< 1 second
Duration
8 minutes
Labels
None
Agent
bamboo-agent-iowa.igniterealtime.org
Revision
a3c6f662594affb2663fd93a2cc0cc6db34f0cb4
Total tests
1742
Successful since
#2672 ()

Tests

Code commits

Author Commit Message Commit date
daryl herzmann daryl herzmann a3c6f662594affb2663fd93a2cc0cc6db34f0cb4 Merge pull request #2694 from guusdk/OF-3027_Netty-parent-eventloop-threadnames
OF-3027: Give Netty threads a recognizable name
Guus der Kinderen Guus der Kinderen 0d4a8ceb24b3bd19c512fcccb18451328f43d223 OF-3027: Give Netty threads a recognizable name
To facilitate debugging, the various threads used by Netty EventLoops should have names that at least contain the type of connection that they're operating for.

This commit changes the name of threads of the
- 'parent' eventloop from `nioEventLoopGroup-7-1` (a Netty default) to `socket_s2s_ssl-acceptor-7`
- 'child' eventloop from `socket_s2s_ssl-thread-3` (a Netty default) to `socket_s2s_ssl-worker-3`

To do this, a new theadpool factory is introduces for the 'parent' eventloop. The new factory is configured to use the same priorty and daemon settings as the default Netty threadpool factory.

Jira issues

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

Shared artifacts

Artifact File size
Unpacked project files 197 MB