Skip to content

Commit 6b8dcff

Browse files
authored
Merge pull request #4197 from gchq/gh-4196-byte-buffer-pool-msg
PR for #4196 - ByteBufferPoolImpl message is incorrect
2 parents 18032ef + 851c5e3 commit 6b8dcff

File tree

2 files changed

+25
-1
lines changed

2 files changed

+25
-1
lines changed

stroom-lmdb/src/main/java/stroom/bytebuffer/ByteBufferPoolImpl4.java

+1-1
Original file line numberDiff line numberDiff line change
@@ -516,7 +516,7 @@ private ByteBuffer createNewBufferIfAllowed(final int offset) {
516516
LOGGER.warn("Hit {}% ({}) of the limit of {} for pooled buffers of size {}.",
517517
byteBufferPoolConfigProvider.get().getWarningThresholdPercentage(),
518518
warningThreshold,
519-
newBufferCount,
519+
maxBufferCount,
520520
ModelStringUtil.formatCsv(bufferSizes[offset]));
521521
} else if (newBufferCount == maxBufferCount) {
522522
LOGGER.warn("Hit limit of {} for pooled buffers of size {}. " +
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
* Issue **#4196** : Fix warning message when the byte buffer pool hits its threshold.
2+
3+
4+
```sh
5+
# ********************************************************************************
6+
# Issue title: ByteBufferPoolImpl message is incorrect
7+
# Issue link: https://github.com/gchq/stroom/issues/4196
8+
# ********************************************************************************
9+
10+
# ONLY the top line will be included as a change entry in the CHANGELOG.
11+
# The entry should be in GitHub flavour markdown and should be written on a SINGLE
12+
# line with no hard breaks. You can have multiple change files for a single GitHub issue.
13+
# The entry should be written in the imperative mood, i.e. 'Fix nasty bug' rather than
14+
# 'Fixed nasty bug'.
15+
#
16+
# Examples of acceptable entries are:
17+
#
18+
#
19+
# * Issue **123** : Fix bug with an associated GitHub issue in this repository
20+
#
21+
# * Issue **namespace/other-repo#456** : Fix bug with an associated GitHub issue in another repository
22+
#
23+
# * Fix bug with no associated GitHub issue.
24+
```

0 commit comments

Comments
 (0)