Question

3
Replies
98
Views
Chunzhi_Hong Member since 2013 138 posts
PEGA
Posted: June 13, 2016
Last activity: June 14, 2016
Closed
Solved

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.

For example,

####<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>.


System Administration
Moderation Team has archived post
Share this page LinkedIn