7.2 Web logic server log displays <Emergency> without any emergent info
We are on PRPC 7.2 with weblogic 12c and oracle 12c.
There are lots of <Emergency> logs in the weblogic server log, when the server start up.
####<2016/06/13 15:55:46 JST> <Emergency> <com.pega.pegarules.internal.bootstrap.PRBootstrap> <ritrap1f> <ADMIN_XXX> <[ACTIVE] ExecuteThread: '72' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic2> <> <> <1465800946783> <BEA-000000> <prbootstrap.properties merged with prbootstrap entries in Data-Admin-System-Settings>
####<2016/06/13 15:55:53 JST> <Emergency> <com.pega.pegarules.internal.bootstrap.phase2.PRBootstrapImpl> <ritrap1f> <ADMIN_XXX> <[ACTIVE] ExecuteThread: '72' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic2> <> <> <1465800953533> <BEA-000000> <PegaRULES class will be loaded from the database>
This causes the log monitoring software catch these messages and raise alert to operation team.
Can anyone explain why these log messages are <Emergency>?
In my opinion they are normal PRPC start up log messages, and should be categorized as <Info>.
According to the Weblogic logging service online help "The Level of the LogRecord is automatically converted to one of the standard WebLogic logging service severity levels when the log message redirected." and JavaDoc for Level class tells that default value for each level is SEVERE 1000, WARNING 900, INFO 800. Perhaps, Weblogic simply interpreted the number "19830421" into <Emergenchy> log level, because the number is enormously grater than the default SEVERE level value 1000.
This odd number, 19830421 may come from Pegasystems' founded date, April 21st, 1983 possibly. If that is the case, WebLogic will surely throw errors as it is more than 1000! It has to be fixed as different number to eliminate this Emergency although it is charming.