Tuesday, September 8, 2009

Oracle ESB 10.1.3.4 ConsoleTransactionException

While starting Oracle SOA instance, all ESB services are not getting started & refreshed before orabpel service starts. When this happens no service can be accessed from the Oracle ESB and the following exception is sighted in the ESB Console.

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:2317) at oracle.tip.esb.console.XMLConsoleManagerImpl.deleteSystem(XMLConsoleManagerImpl.java:637) at oracle.tip.esb.configuration.servlet.command.DeleteSystemCommand.execute(DeleteSystemCommand.java:34) 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) ".
One of the solution to overcome this issue is to ensure that the ESB services are getting started successfully before orabpel service starts. One can follow the following steps to overcome this issue;

1. Login to the 'Application Manager' (em console) and stop the orabpel service under oc4j_soa. Ensure that the hw_service is also stopped.
2. Now change to the \opmn\bin directory via command prompt and issue the following command
opmnctl stopall
3. Once all services are stopped, issue the following command to start all services
opmnctl startall
4. Login back to the Application Manager console and start the orabpel service under oc4j_soa instance

Now, things should work fine.

2 comments:

  1. what is the reason behind this error?

    ReplyDelete
  2. Hi, When you have BPEL processes which are dependent on ESB services and the order of service start must be maintained such that ESB services are started prior to BPEL services. This probably might be a bug in 10.1.3.4 but the workaround is to manually ensure that the service start is in proper sequence.

    ReplyDelete