Build #1,603

Build: #1603 was successful Changes by Brynjar Eide <>

Build result summary


668 minutes
OpenNMS (develop branch)
fa785cbd6c20c3b3ea3a7f116eb52b5ead92d70f fa785cbd6c20c3b3ea3a7f116eb52b5ead92d70f
OpenNMS Installer
da12784d9ab4ba4aacedec0283d0c04075fd6ebf da12784d9ab4ba4aacedec0283d0c04075fd6ebf
088d710674109759251f42c6720d74ea80cf3f13 088d710674109759251f42c6720d74ea80cf3f13
Smoke Tests
cb1e72265cf2ce10cb4872f58120272b340a1ce1 cb1e72265cf2ce10cb4872f58120272b340a1ce1
OpenNMS Bamboo Utils
a6d144f81c2df6f267b94e79328a0c8497980837 a6d144f81c2df6f267b94e79328a0c8497980837
OpenNMS System Test API
2baceb98eba956ca0f62f0e2d469d9f73b7ffd02 2baceb98eba956ca0f62f0e2d469d9f73b7ffd02
Total tests
First to pass since
#1602 (Changes by Jesse White)


Code commits

OpenNMS (develop branch)
Author Commit Message Commit date
Brynjar Eide <> Brynjar Eide <> fa785cbd6c20c3b3ea3a7f116eb52b5ead92d70f fa785cbd6c20c3b3ea3a7f116eb52b5ead92d70f NMS-10357: Fix Collectd and Pollerd's ThreadPool graphs (#2155)
* Fix Collectd and Pollerd's ThreadPool graphs

Adds missing pool size attribute ('numPoolThreads') to Pollerd's
MBean, and adds all the PoolThreads attributes (num, max, peak) to
the JMX datacollection config for Pollerd.

Also makes it slightly more obvious what numPoolThreads actually is,
by changing the @return comment to match the official javadocs.

Finally, the graph properties for the ThreadPool attributes have been
changed to graph the active threads, peak threads and max pool size.

The original graph included both numPoolThreads and maxPoolThreads,
which seem to be identical when using fixed thread pools.
numPoolThreads was replaced by active threads, which made the
standalone graphs redundant.

* Add core pool size to MBeans and improve the graphs

Instead of graphing the max pool size, which is never used unless
the queue is full, include the current pool size and the core pool

Also replaces peak active with current pool size. With the
current implementation, the current pool size seems to never shrink,
so the peak pool size would be redundant, otherwise it might make
sense to graph both metrics.

Jira issues

Unknown Issue TypeNMS-10357Could not obtain issue details from Jira