]
Paul Ferraro moved JBEAP-19886 to WFLY-13657:
---------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-13657 (was: JBEAP-19886)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Clustering
(was: Clustering)
Affects Version/s: 20.0.1.Final
(was: 7.4.0.CD20-CR1)
JGroups subsystem logs "version is missing in the configuration
file" warning without a log code on deployment using JPA 2LC
----------------------------------------------------------------------------------------------------------------------------
Key: WFLY-13657
URL:
https://issues.redhat.com/browse/WFLY-13657
Project: WildFly
Issue Type: Bug
Components: Clustering
Affects Versions: 20.0.1.Final
Reporter: Paul Ferraro
Assignee: Paul Ferraro
Priority: Critical
This warning without a log code is logged upon deployment of application:
{code}
13:06:16,312 WARNING [org.jgroups.conf.XmlConfigurator] (ServerService Thread Pool --
101) version is missing in the configuration file
{code}
I can see this with several EAP Quickstarts, the exact list from CD20 is:
batch-processing, bmt, cmt, greeter, hibernate, kitchensink, kitchensink-jsp,
kitchensink-ml, managed-executor-service, spring-greeter, spring-kitchensink-basic,
tasks-jsf, thread-racing
Not sure if it's relevant, but I have noticed all the above mentioned QS use H2. None
of the QS that don't use H2 has the warning logged.
This can be reproduced with [WildFly 20 Final
release|https://wildfly.org/downloads/] and
[WildFly 20 Final
QS|https://github.com/wildfly/quickstart/tree/20.0.0.Final] as well:
1. Start the server with {{$JBOSS_HOME/bin/standalone.sh}}
2. Deploy one of the above mentioned QS with {{mvn clean package wildfly:deploy}}
This warning was not present in CD19 and earlier releases.
The same warning was also logged on startup, which has been fixed with JBEAP-19734 and
WFLY-13590.