BPEL Process Manager Server (10.1.3.4) Connection Failed

After upgrading to Oracle SOA 10.1.3.4 Integration Server connection cannot be established through JDeveloper. When looking into the OPMN log files the following error was logged;

java.lang.IllegalStateException: MessageDrivenHome:: application state=3 - Application: 'hw_services' is not in RUNNING state.
at com.evermind.server.ejb.MessageDrivenHome.checkRunningState(MessageDrivenHome.java:1216)
at com.evermind.server.ejb.MessageDrivenConsumer.run(MessageDrivenConsumer.java:162)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:298)
at java.lang.Thread.run(Thread.java:595)

To overcome this issue, login to the em console (Application Manager) [http://hostname:portname/em] and restart the hw_services available under the oc4j_soa instance. This should resolve the connection issue & a retry for establishing connection via JDeveloper will succeed.

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.

Oracle ESB org.apache.slide.structure.ObjectNotFoundException

"org.apache.slide.structure.ObjectNotFoundException" exception is thrown in ESB console during runtime. This error occurs when ESB artifacts are developed on JDeveloper and moved from one workspace to another. The JDeveloper will not be able to eventually update the file locations in the related artifacts when the project is moved from one application/workspace to another.

Detailed Error Description: (As logged in ESB Error Trace)

Error occured while transforming payload using XSL "esb:///ESB_Projects/Application1_***/***.xsl". Reason : Could not load XSL transform into the cache for XSL/XSLT "esb:///ESB_Projects/Application1_***/***.xsl"! Reason : org.apache.slide.structure.ObjectNotFoundException: No object found at /files/ESB_Projects/Application1_***!

Solution:
DO NOT move the ESB projects to a different JDeveloper workspace, as this is not supported by Oracle ESB (till 10.1.3.4)