Database Reference
In-Depth Information
Logger levels can help in providing more information on pretty much everything.
The top-level logger names are shown in the preceding screenshot. For ex-
ample, some of the loggers that can be modified include DVMs (
or-
acle.soa.dvm
), BPEL engine (
oracle.soa.bpel.engine.*
), Mediator fil-
ters (
oracle.soa.mediator.filter
), human workflow (
or-
acle.soa.services.workflow.*
), Enterprise Manager console (
or-
acle.sysman
), and Oracle Web Services Manager (
oracle.wsm.*
). There
are too many loggers to mention and there is no comprehensive list that de-
scribes each one of them. However, many are self-descriptive, and often Oracle
Support can guide you as to what you may need to increase during your
troubleshooting efforts. The logs themselves can point you to a logger. Observe
the logger highlighted in the following snippet:
<Aug 5, 2011 12:00:02 AM EDT> <Error> <oracle.soa.bpel.engine.dispatch> <BEA-000000> <failed to handle message
javax.ejb.EJBException: EJB Exception: : java.lang.StackOverflowError
Here, the
oracle.soa.bpel.engine.dispatch
logger threw the
Stack-
OverflowError
exception. Increasing this specific logger may (or may not)
yield additional useful information.
An important thing to keep in mind is that loggers contain hierarchies. Exercise
caution when setting root level loggers to
FINE, FINER
, or
FINEST
. Consider
the preceding case where you have encountered an EJB exception in the
BPEL engine. If the root logger (that is,
oracle.soa.bpel.engine)
is
set to
FINEST
, all the descendants that inherit from it will have the same
logging level. As a result, a large amount of unused log entries are produced,
which might actually make troubleshooting the issue much more difficult. There-
fore, if possible, you should set only the corresponding child logger (
or-
acle.soa.bpel.engine.dispatch
) to a higher level without enabling the
root logger.
