The Problem
Our user has attempted to upgrade JasperReports Server (JRS) 7.1 to 7.9 using buildomatic js-upgrade-newdb script. "The script seems to have run fine and generated new encryption keys". However when deploying the JRS WAR into JBoss, user is getting the following error:
ERROR [org.jboss.logmanager.log4j.status] (ServerService Thread Pool -- 114) LogManager returned an instance of org.jboss.logmanager.log4j.JBossLoggerContextFactory which does not implement org.apache.logging.log4j.core.impl.Log4jContextFactory. Unable to initialize Log4j.
The Cause
JBoss provides highly configurable logging facilities for both its own internal use and for use by deployed applications. It appears the logging subsystem in the user's JBoss deployment contains stale, not up to date content incompatible with the JRS 7.9 deployment.
The Solution
By excluding logging subsystems in the JBoss deployment descriptor, the user is able to deploy JRS 7.9 WAR into JBoss successfully.
=================================================
TTC-20220330-2095506
Recommended Comments
There are no comments to display.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now