after a brief chat with in gitter, i'm leaving this note here.
we recently began updating our private IBFT network nodes with pantheon-1.2.3-SNAPSHOT built from the sources. we'd previously been running pantheon-1.1.3-SNAPSHOT, again built from the sources. we did not see this issue in the earlier code. upon launching our nodes (with ./bin/pantheon --config-file=config.toml) , we get the following two exceptions back-to-back:
identified these exceptions as known issues (annoying warnings), although i wasn't able to find a relevant issue in the Jira. so far we have been safely able to ignore them, but they happen every single time we start up the node.
we did manage to find a possibly related issue among the bugs in the Netty project, but it was for an earlier version of Java. i include it here in the hope that it is helpful in some way:
our setup may be a bit peculiar, so i'll include some details here:
we're running in AWS, on a server which cohabitates with apache2 and tomcat. we run some application WAR files in this configuration that control the install of Pantheon through JSON-RPC.
the kernel we use in this configuration is : Linux 4.14.138-89.102.amzn1.x86_64 #1 SMP Thu Aug 15 15:41:44 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux.
this is derived from an Amazon AMI that is their minimal configuration for something they call "Amazon Linux 1," a variant of RHEL.
because Amazon Linux 1 doesn't natively support Java 11, we have utilized Amazon's variant of OpenJDK called Corretto.
the specific java version is : openjdk version "11.0.4" 2019-07-16 LTS
OpenJDK Runtime Environment Corretto-126.96.36.199.1 (build 11.0.4+11-LTS)
OpenJDK 64-Bit Server VM Corretto-188.8.131.52.1 (build 11.0.4+11-LTS, mixed mode)
our pantheon version is: pantheon/v1.2.3-dev-dfec928c/linux-x86_64/corretto-java-11
i'm unsure about how your folks use labels and components here, but i've made my best guesses.