Thursday, January 24, 2013

Be careful when setting logger levels in Oracle SOA Suite 11g

There are two catches I want to share with you about setting logger levels in Oracle SOA Suite 11g.

1. Logger levels are tied to individual managed servers

Did you know that when you change the logger level in the EM Console that it is not a global configuration?

Basically, when you right-click on soa-infra and click on Log Configuration, you are either setting it on soa_server1 or soa_server2, depending on which soa-infra you right-clicked on (see image below). The configuration change you made will not apply to both and you must repeat it on each node of your cluster.

Keep this in mind when you consider changing your logger levels.



2. Certain logger configuration is lost if you restart the server

When configuring logger levels, be aware of which loggers you are updating; Runtime Loggers or Loggers With Persistent Log Level State.

When you make a change to Runtime Loggers, the settings will be lost when you bounce the server. On the other hand, Loggers With Persistent Log Level State will remain in effect even if you bounce the server.


Application versions:
  • Oracle SOA Suite 11g (11.1.1+)

References:

No comments: