[jboss-user] [JBoss jBPM] - EJB Timer Lookup problem in BPEL

dhanushgopinath do-not-reply at jboss.com
Tue Jan 20 08:25:21 EST 2009


Hi,

I am using jbpm bpel 1.1.1 with Jboss 4.2.0 and I am extensively using the BPEL process using JBPM/BPEL API's. 

I am getting this exception while the process ends 

18:39:11,128 ERROR [SOAPFaultHelperJAXWS] SOAP request exception
  | org.jbpm.JbpmException: ejb timer entity lookup problem
  | 	at org.jbpm.scheduler.ejbtimer.EntitySchedulerServiceFactory.getTimerEntityHome(EntitySchedulerServiceFactory.java:43)
  | 	at org.jbpm.scheduler.ejbtimer.EntitySchedulerServiceFactory.openService(EntitySchedulerServiceFactory.java:50)
  | 	at org.jbpm.svc.Services.getService(Services.java:150)
  | 	at org.jbpm.svc.Services.getCurrentService(Services.java:94)
  | 	at org.jbpm.graph.exe.ProcessInstance.end(ProcessInstance.java:328)
  | 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  | 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
  | 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  | 	at java.lang.reflect.Method.invoke(Method.java:585)
  | 	at org.hibernate.proxy.pojo.javassist.JavassistLazyInitializer.invoke(JavassistLazyInitializer.java:173)
  | 	at org.jbpm.graph.exe.ProcessInstance_$$_javassist_351.end(ProcessInstance_$$_javassist_351.java)
  | 	at org.jbpm.graph.exe.Token.notifyParentOfTokenEnd(Token.java:329)
  | 	at org.jbpm.graph.exe.Token.end(Token.java:301)

As per the code in CVS the EntitySchedulerServiceFactory class in jbpm bpel is looking up for a JNDI name java:comp/env/ejb/LocalTimerEntityBean and expecting org.jbpm.ejb.LocalTimerEntityHome.

But while deploying the JBPM BPEL it binds the jndi name ejb/LocalTimerEntityBean against the Local Home org.jbpm.ejb.LocalTimerEntityHome. I got this information from the ejb-jar.xml file in jbpm-enterprise.jar (inside jbpm-bpel.ear).

So when the EntitySchedulerServiceFactory code tries to lookup, it doesnt get it and throws the above exception.

This exception ONLY happens when I start the process in API mode. If I use SOAP-UI to test, it works perfectly fine.

Do I need to configure anything extra? Please let me know. I am kind of stuck here.

Thanks in Advance
Dhanush

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4203251#4203251

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4203251



More information about the jboss-user mailing list