Error while invoking bean "finder": Instance not found in datasource

Question

Hi All
I am facing Error while trying to execute a BPEL processing using Notification service for sending out mail .
Following is the Error Stack :
<ERROR> <default.collaxa.cube> <BaseCubeSessionBean::logError> Error while invoking bean "finder": Instance not found in datasource.
The process domain was unable to fetch the instance with key "677c0310e56e2b26:26d607:10dca65e80a:-7ffc" from the datasource.
Please check that the instance key "677c0310e56e2b26:26d607:10dca65e80a:-7ffc" refers to a valid instance that has been started and not removed from the process domain.
ORABPEL-02152
Instance not found in datasource.
The process domain was unable to fetch the instance with key "677c0310e56e2b26:26d607:10dca65e80a:-7ffc" from the datasource.
Please check that the instance key "677c0310e56e2b26:26d607:10dca65e80a:-7ffc" refers to a valid instance that has been started and not removed from the process domain.
     at com.collaxa.cube.engine.data.AdminFinder.__lookupInstanceMetaData(AdminFinder.java:314)
     at com.collaxa.cube.engine.data.AdminFinder.__lookupInstanceMetaData(AdminFinder.java:262)
     at com.collaxa.cube.engine.data.AdminFinder.lookupInstanceByConversationId(AdminFinder.java:235)
     at [b]com.collaxa.cube.ejb.impl.FinderBean.lookupInstanceByConversationId(FinderBean.java:177)
     at IFinderBean_StatelessSessionBeanWrapper42.lookupInstanceByConversationId(IFinderBean_StatelessSessionBeanWrapper42.java:669)
     at com.oracle.bpel.client.Locator.lookupInstance(Locator.java:420)
     at displayInstance.jspService(_displayInstance.java:111)
     at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:56)
     at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:350)
     at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:509)
     at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:413)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:824)
     at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:330)
     at com.evermind.server.http.ServletRequestDispatcher.forward(ServletRequestDispatcher.java:222)
     at com.collaxa.cube.fe.DomainFilter.doFilter(DomainFilter.java:152)
     at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:663)
     at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:330)
     at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:830)
     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:285)
     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:126)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:192)
     at java.lang.Thread.run(Thread.java:534)
<2006-09-20 14:55:44,109> <ERROR> <default.collaxa.cube.services> <PCException::<init>> Error in sending e-mail message.
<2006-09-20 14:55:44,119> <ERROR> <default.collaxa.cube.services> <PCException::<init>> Error in sending e-mail message.
The understanding formed till now is that the service is trigged using a stateless session bean wrapper and the lookup for the same is failing.
One option will be to write the java code for performing the lookup using method
lookupInstanceByConversationId(String convId, DomainAuth auth)
but certain information e.g DomainAuth is not available.
I have tried locating information about the dynamic wrapper which is being created.
Any inputs/comments/direction for the above problem are welcomed
Cheers

Answer 1

Thanks Marc.
I checked the domain log (ORA_BPEL_HOME\bpel\domains\default\logs\domain.log) for information. It repeats the same error displayed in the bpel server window.
I have now put some SOPs in my Java embedding activity to see if the process gets instantiated or not. On the BPEL server window, I am able to see these SOPs upto the point where I invoke a method invocation on my remote Java class. Which clearly means the BPEL process is instantiated, contrary to the information in the error (that the BPEL instance cannot be found) I am getting.