My Oracle Support Banner

ESB fails to initialize due to failures Pinging designtimeTime servlet (Doc ID 1313679.1)

Last updated on AUGUST 17, 2018

Applies to:

Oracle SOA Suite - Version 11.1.1.1.0 and later
Information in this document applies to any platform.
***Checked for relevance on 28-Feb-2013***

Symptoms

You recently completed a new installation of Oracle Service Bus 10g Release 3 (version 10.1.3.x) which ran cleanly (with no errors) and completed successfully. However after the installation the ESB Design Time (ESB-DT) and ESB Runtime (ESB-RT) components fail to initialize.

When you review the log files of the associated OC4J instances you see related errors in two different logs:

    1. OPMN log
      (e.g. $ORACLE_HOME/opmn/logs/ESBDT_GROUP_OC4J_ESBDT_ESBDT_GROUP_1.log)
      11/04/08 18:24:59 oracle.tip.esb.console.exception.ConsoleTransactionException:
      An unhandled exception has been thrown in the ESB system.
      The exception reported is: "oracle.tip.esb.console.exception.ConsoleTransactionException:
      File repository not initialized. May be ESB bootstrap failed
      Please review ESB prameters for their correctness.

      at oracle.tip.esb.console.XMLConsoleManagerImpl.commit(XMLConsoleManagerImpl.java:2411)
      at oracle.tip.esb.console.XMLConsoleManagerImpl.commit(XMLConsoleManagerImpl.java:2380)
      at oracle.tip.esb.console.XMLConsoleManagerImpl.updateSystemInRepository(XMLConsoleManagerImpl.java:920)
      at oracle.tip.esb.console.XMLConsoleManagerImpl.updateSystemFromElement(XMLConsoleManagerImpl.java:596)
      at oracle.tip.esb.console.XMLConsoleManagerImpl.updateSystem(XMLConsoleManagerImpl.java:574)
      at oracle.tip.esb.configuration.servlet.command.UpdateSystemCommand.execute(UpdateSystemCommand.java:61)
      at oracle.tip.esb.configuration.servlet.CommandServlet.doJob(CommandServlet.java:109)
      at oracle.tip.esb.configuration.servlet.CommandServlet.doPost(CommandServlet.java:76)
      at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
      at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
      at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)
      at oracle.security.jazn.oc4j.JAZNFilter$1.run(JAZNFilter.java:400)
      at java.security.AccessController.doPrivileged(Native Method)
      at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
      at oracle.security.jazn.oc4j.JAZNFilter.doFilter(JAZNFilter.java:414)
      at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:623)
      at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370)
      at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:871)
      at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:453)
      at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:313)
      at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:199)
      at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
      at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
      at java.lang.Thread.run(Thread.java:595)

 

  1. Oracle Diagnostic log
    (e.g. $ORACLE_HOME/j2ee/OC4J_ESBDT/logs/ESBDT_GROUP~OC4J_ESBDT~1/ESBDT_GROUP~OC4J_ESBDT~1/oc4j/log.xml )

    Here, you will also be able to locate errors similar to the above but leading up to that ultimate failure you will see multiple log entries whose message text is similar to the following:
    <MSG_TEXT>Pinging designtimeTime servlet {http://yourHostorVirtualHostname:7777/esb/ESBConsoleMain.html} for 1/15</MSG_TEXT>
    <MSG_TEXT>Pinging designtimeTime servlet {http://yourHostorVirtualHostname:7777/esb/ESBConsoleMain.html} for 2/15</MSG_TEXT>
    ...
    <MSG_TEXT>Pinging designtimeTime servlet {http://vs_srjisoaia.admcablemas.net:7777/esb/ESBConsoleMain.html} for 15/15</MSG_TEXT>

Changes

It is possible to see this error for multiple installation topologies, but the error is perhaps more commonly encountered when following the Oracle Enterprise Deployment Guide to create a clustered installation topology. Specifically, this problem is more likely to be seen when HTTP requests being made to the cluster through a virtual hostname, that directs requests to a load balancer for further distribution across the ESB nodes of the cluster.

See also:

Oracle Application Server
Enterprise Deployment Guide
10g Release 3 (10.1.3.5.0)
E15355-01
October 2009

HTML: http://download.oracle.com/docs/cd/E14101_01/doc.1013/e15355/toc.htm
PDF: http://download.oracle.com/docs/cd/E14101_01/doc.1013/e15355.pdf

Chapter 3: Installing and Configuring the mySOACompany Web and Application Tiers
3.23 Updating the Oracle Enterprise Service Bus Metadata

Cause

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
Symptoms
Changes
Cause
Solution
References


This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.