Database Reference
In-Depth Information
Using logs
You will likely notice a lot of errors in the
soa_server1.out
log file. The
key is to be able to differentiate between infrastructure errors and composite in-
stance errors. In most cases it is obvious, though some cases may require fur-
ther troubleshooting. Here, we describe eight such examples of various error
categories and how they are differentiated.
Infrastructure error—StackOverflowError
StackOverflowError
is usually an indication of an infrastructure error, as the
error does not appear tied to any specific composite. Based on the logger
or-
acle.soa.bpel.engine.dispatch
, it is thrown by the BPEL dispatch en-
gine:
<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
For errors like this, when you have little or no information even after you
throttle all your loggers to full, it is wise to search My Oracle Support (
ht-
tp://support.oracle.com
)
or engage Oracle Support. In this particular error, it was
actually related to a bug in the
Oracle Platform Security Services (OPSS)
module in Oracle WebLogic Server 11g (10.3.5), specifically in the
jps-
api.jar
library. A patch was later released to address this issue.
Composite instance error—SOAPFaultException
There may be a large number of instances in the infrastructure that receive
processing faults from external systems they are interacting with. Here, the
Mediator Service Engine (as shown by the
or-
acle.soa.mediator.serviceEngine
logger) appears to have thrown a
SOAPFaultException
, which in itself is not very useful. However, the details
of the error are quite clear. This is a business exception thrown by some external
service or resource. Though there is no information here to tie it back to a spe-
