My Oracle Support Banner

ESB not Generating Concrete WSDL URL and/or Soap Endpoint URI - Invalid HTTP Proxy Settings (Doc ID 565068.1)

Last updated on MAY 01, 2018

Applies to:

Oracle ESB - Version to
Information in this document applies to any platform.
***Checked for relevance on 12-Sep-2011***


Registered ESB service does not load into ESBRT and ESBDT so the Concrete WSDL URL and Soap Endpoint URI are not accessible from the ESB Control screens.

Steps To Reproduce:

With the ESB services already registered, start the ESBRT and ESBDT servers.

To detect this situation check the log.xml files for the ESBRT and ESBDT and the *~1.log file for the ESBDT in $OH/opmn/logs during the start-up of the ESBRT and ESBDT.

In the log.xml for the ESBRT you will something similar to the following:

    <MSG_TEXT>ESB Service Default.testservice cannot haveSOAP test page as WSDL registration failed!
      Reason: Invalid XML in document at:,
      line: {1}, column: {2}: Start of root element expected.:
      oracle.xml.parser.v2.XMLParseException: Start of root element expected.
    at oracle.xml.parser.v2.XMLError.flushErrors1(
    at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(
    at oracle.xml.parser.v2.NonValidatingParser.parseDocument(
    at oracle.xml.parser.v2.XMLParser.parse(

In the log.xml for the ESBDT you will something similar to the following:

    <MSG_TEXT>unable to get service list</MSG_TEXT>
      An unhandled exception has been thrown in the ESB system. The exception reported is: "".

    at oracle.tip.esb.configuration.util.WSDLGenerator.generateWSDL(
    at oracle.tip.esb.console.XMLConsoleManagerImpl.getGeneratedWSDL(
    at oracle.tip.esb.configuration.wsilbrowser.ESBWSILBrowser.createWSDL(
    at oracle.tip.esb.configuration.wsilbrowser.ESBWSILBrowser.fetch(
    at oracle.tip.esb.configuration.wsilbrowser.WSILBrowserServlet.doGet(
    at javax.servlet.http.HttpServlet.service(

and/or this:

caused by:    : Connection establishment timed out: Failed to read wsdl file at: 

In the ESBDT file *~1.log in $OH/opmn/logs:

08/04/24 08:30:47 Start process
08/04/24 08:31:41 log4j:WARN No appenders could be found for logger (wsif).
08/04/24 08:31:41 log4j:WARN Please initialize the log4j system properly.
08/04/24 08:31:53 Oracle Containers for J2EE 10g (  initialized
08/04/24 08:33:11 oracle.tip.esb.console.exception.ConsoleException: An unhandled exception has been thrown in the ESB system.
  The exception reported is: "Error reading import of
  Failed to read wsdl file at: "", caused by:    : ${}: ${}:
  Failed to read wsdl file at: "", caused by:    : ${}: ${}: ${}: ${}
    at HTTPClient.HTTPConnection$
    at Method)
    at HTTPClient.HTTPConnection.privilegedInetAddressGetAllByName(
    at HTTPClient.HTTPConnection.access$000(
    at HTTPClient.HTTPConnection$



To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.