Database Reference
In-Depth Information
cific composite or instance, the same error, in more detail, can be found in the
soa_server1.log
file, which will provide you with that information. Rest as-
sured, this exception will also appear in the composite instance fault on the con-
sole:
<Aug 6, 2011 10:10:33 AM EDT> <Error> <oracle.soa.mediator.serviceEngine> <BEA-000000> <Got an exception: oracle.fabric.common.FabricInvocationException: javax.xml.ws.soap.SOAPFaultException: CreateOrder failed with Message: Cannot insert the value NULL into column 'OrderID', table '@Orders'; column does not allow nulls. INSERT fails.
The error is obvious; a table column does not allow
NULL
and, therefore, inser-
tion is rejected by the database.
Infrastructure error—DeploymentException
Some infrastructure exceptions are related to the backend components not be-
ing available or configured properly. Some of them may be categorized by a
warning and not an error, but this is still a problem. Note the following error
that appears to be related to a WebLogic JMS Server. In this case, the JMS
Server named
CustomJMSServer
is referencing a persistent file store
Cus-
tomFileStore
that does not exist:
<Dec 25, 2011 7:30:41 PM EST> <Warning> <Management> <BEA-141197> <The deployment of CustomJMSServer failed. weblogic.management.DeploymentException: Internalerror activating the JMS Server CustomJMSServer: weblogic.management.DeploymentException: The persistent store "CustomFileStore" does not exist
Such exceptions can be resolved by making sure the backbone infrastructure
required is in place. This can be resolved by creating the required filestore and
restarting the servers.
Composite instance error—FabricInvocationException
FabricInvocationException
is the most generic error reported by the
Oracle SOA Suite 11g SOA Infrastructure. This could be caused by invalid
SOAP requests, WS-Addressing issues, or even due to non-accessible end-
points. The following
FabricInvocationException
error provides a little in-
formation about its probable cause. Furthermore the
Unable to access the
following endpoint(s)
explanation is also inadequate and in most cases
could be misleading, as it may be related to any number of exceptions.
