BPEL process instance not created - Error

Question

I have a BPEL Process that was working fine until I added a couple of sequence activities and I think thats when this problem started. Its wierd.
I have an XML fragment assigned to a variable and when I add a sequence and deploy it, it creates an instance but gives me the XML value error which is because of the whitespaces it adds in the bpel source. I then remove the whitespaces and deploy it. It doesn't create and instance. I add the whitespaces in and deploy it, instance gets created and gives me an error message, but when I fix the whitespaces and deploy it, instance doesn't get cretaed and I see the below message in the domain.log.
Also when I try to create an instance from the BPEL console it gives me a message saying 'Instance is being cretaed asynchronously'. My process is not an asynchronous process. I'm not sure what is happening.
ORABPEL-05002
Message handle error.
An exception occurred while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the exception is: Transaction was rolled back: timed out; nested exception is: java.rmi.RemoteException: No Exception - originate from:java.lang.Exception: No Exception - originate from:; nested exception is:
     java.lang.Exception: No Exception - originate from:
     at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:152)
     at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:70)
     at com.collaxa.cube.engine.ejb.impl.WorkerBean.onMessage(WorkerBean.java:86)
     at com.evermind.server.ejb.MessageDrivenBeanInvocation.run(MessageDrivenBeanInvocation.java:123)
     at com.evermind.server.ejb.MessageDrivenHome.onMessage(MessageDrivenHome.java:755)
     at com.evermind.server.ejb.MessageDrivenHome.run(MessageDrivenHome.java:928)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
     at java.lang.Thread.run(Thread.java:534)
Appreciate all your help.
Thanks
-Prapoorna

Answer 1

If you try what Anirudh suggested you may be able to get some more information.
I am guessing the problem is with the second operation of your web service. You can try throwing a try / catch any exception (bad standards, but sometimes useful for tracking down a problem) in your web service function and returning the exception values.
You can also try throwing a catchall in your BPEL process and use ora:getFaultAsString() to receive the error message. If you are using 10.1.3.1 this requires patch 5672007