The exception reported is: "oracle.tip.esb.console.exception.ConsoleTransactionException:File repository not initialized.May be ESB bootstrap failed

When i try to delete a ESB component from ESB Console, it was throwing the below error message "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) ".
"

Solution: Some time the ESB Components are not loaded properly during that time you will get to see these kind of error messages surface.
Restart the oc4j_soa component using the below command.

> opmnctl restartproc process-type=oc4j_soa

The above command is used to restart only the required component without restarting all the components in the server .

Server Version : SOA Suite 10.1.3.4V

Exception message is: javax.resource.ResourceException: RollbackException: Transaction has been marked for rollback: Timed out

Problem:

When i try to deploy a bpel which is of 30kb size using JDeveloper it was throwing "Exception message is: javax.resource.ResourceException: RollbackException: Transaction has been marked for rollback: Timed out" Exception.

"ORABPEL-04077
Cannot fetch a datasource connection.
The process domain was unable to establish a connection with the datasource with the connection URL "jdbc/BPELServerDataSource". The exception report
ed is: javax.resource.ResourceException: RollbackException: Transaction has been marked for rollback: Timed out"

The JDeveloper/Ant script will take too much time and finally it will say failed to deploy.
SOA Suite Version: 10.1.3.4 and JDeveloper Version : 10.1.3.4.0.4270

Fix: To fix this issue i have to revisit some of the configuration files on the server.

1. Open the transaction-manager.xml file using some editor.

Path for the file : \j2ee\oc4j_soa\config\transaction-manager.xml

Modify the transaction-timeout attribute value to some higher value, i have set the value as transaction-timeout="7200".

2. Open the orion-ejb-jar.xml file using editor

Path for the file : \j2ee\oc4j_soa\application-deployments\orabpel\ejb_ob_engine\orion-ejb-jar.xml

Modify the transaction-timeout attribute, with some higher value.

I have set the value as transaction-timeout="3600".

Note: There will be 6 entries of transaction-timeout attributes. Make sure you change in all the 6 attributes.

3. Reboot the system or only the particular component.

> opmnctl restartproc process-type=oc4j_soa

4. You can deploy now using JDeveloper or ant script.

XPath expression failed to execute. Error while processing xpath expression

If you get this exception while deploying your bpel process, there could be some issue with the xsl file that you have in your bpel process.

To fix this issue, open your bpel process in IDE and double click on the transform activity and click on source part payload and target part payload. Then you deploy.


Before loading the source part and target part if you close the transform box, these kind of issues will stop you from deploying.