Monday, March 02, 2009

Oracle ESB Cluster deployment

When you have configured Oracle ESB cluster and want to deploy, you could end in deployment issues. While in JDeveloper you have developed your ESB service, it deploys successfully. But when you want to access it, via the browser or via BPEL lookup, you get and error.

XML Parsing Error: no element found
Location: http://host:7777/esb/wsil/MySystem/1_0/HelloESBService?wsdl
Line Number 1, Column 1:

In the log file of the Oracle ESBDT engine (oc4j_ebdt), you see more detailed log.

9/03/02 11:08:22 oracle.tip.esb.console.exception.ConsoleException: An unhandled exception has been thrown in the ESB system.
The exception reported is: "WSDL Parsing Failed: org.apache.slide.structure.ObjectNotFoundException: No object found at /files/ESB_Projects/MySystem/HelloESBService.wsdl: java.lang.RuntimeException: org.apache.slide.structure.ObjectNotFoundException: No object found at

at oracle.tip.esb.server.bootstrap.protocol.esb.ESBURLConnection.connect(Unknown Source)
at oracle.tip.esb.server.bootstrap.protocol

This is is not related to the configuraion of the Oracle ESB server. I assume that this is correctly configured, this also applies for a cluster environment. The error is due to the fact the ESB server expects the services from the database, while the deployed services is pointing to a file based repository.

Normally the ESB server is using a file based repository, in this case the ESB server is configured to use a database repoistory. This is often used in cluster environments.

The solution is to change your ESB service. This means open all your *.esbsvc files and look for XML element


Make sure you replace it with


Check all the 'esbsvc' files if they are using the correct url and not pointing to ESB_projects.

Post a Comment