Database Reference
In-Depth Information
<Dec 29, 2011 11:45:06 AM EST> <Error> <oracle.soa.mediator.serviceEngine> <BEA-000000> <Got an exception: oracle.fabric.common.FabricInvocationException: Unable to access the following endpoint(s): http://payment-processing-server-dev:7777/proc/servlet/createCustomer
By reviewing the nested exception later on (not shown here), you will find that
this particular error was due to a timeout of the external service. Though technic-
ally this is not a coding error since it is something that occurred only at runtime,
it is not an SOA Infrastructure error either, as it is related to an external service
over which you may have no control. From a development standpoint, the deve-
loper should be able to handle these cases by enabling some type of retry and/
or error logging. You can also enable more detailed logging for these issues by
enabling debugging while starting the server as follows:
-Djavax.net.debug=all
You can also consider increasing the timeout for external service if these errors
SOA Suite 11g
to see how you can do this.
Infrastructure
error—Unable
to
allocate
additional
threads
This
Unable to allocate additional threads
error appears to be
quite serious, but it really is not. This is clearly an infrastructure related issue
though:
<Sep 30, 2011 11:30:04 PM EDT> <Warning> <oracle.integration.platform.instance.store.async> <BEA-000000> <Unable to allocate additional threads, as all the threads [10] are in use. Threads distribution : Fabric Instance Activity = 1,Fabric-Instance-Manager = 9,>
This error is apparently due to a failed transaction that continues to retry, but
there are no issues with ignoring this warning. The Oracle WebLogic Server is
unable to process more messages in parallel, but has run out of threads which
would eventually clear themselves up. It is possible to increase the number of
SOA Suite 11g for Optimum Performance
for more details regarding tuning of
threads.
