-
Bug
-
Resolution: Done
-
Major
-
EAP 5.0.0
-
None
-
jboss-log4j.xml has been updated to include the jacorb.config log level. The priority has been set to ERROR to avoid printing unnecessary messages to the console during server startup.
-
Documented as Resolved Issue
jacorb.properties contains the following comments, which appears to be no longer true in EAP 5. To change the logging level you need to alter the priority of the Log4J category "jacorb.config". In addition, the default Log4J settings allow the warning to be printed by default, when previously it was not printed due to the log verbosity setting.
- controls log output (to the console!) during the configuration stage.
- This can help to find out which config files are actually loaded!
- 0 : nothing is logged
- 1,2 : only errors
- 3,4 : info (which config files were loaded)
jacorb.config.log.verbosity=0 - If you set the property above to nonzero, the messages
# - "jacorb.home unset! Will use '.'"
# - and
# - "File ./jacorb.properties for configuration jacorb not found"
# - will appear at the console when the JBoss server starts. These messages
- can be safely ignored.
- relates to
-
JBPAPP-7251 jacorb.config log-level is wrong in production profile's jboss-log4j.xml
- Closed
-
JBPAPP-5924 Upgrade JacORB to 2.3.1jboss-patch-02
- Closed