-
Bug
-
Resolution: Won't Do
-
Major
-
None
-
jBPM 3.2.0
-
None
After deploying the jbpm-enterprise.ear to a jboss 4.0.5ga server getting an exception when trying to signal a transition to the end state.
===EXCEPTION SEEN===
13:04:56,785 ERROR [ProcessInstanceBean$SignalTokenListener] Action threw an exception: ejb local timer lookup problem
JNDI name lookup in EjbSchedulerService using incorrect name/and or the TimerServiceBean not declared in
jboss.xml.
===CODE FIXES FOR EXCEPTION==
RCS file: /cvsroot/jbpm/jbpm.3/enterprise/src/main/java/org/jbpm/scheduler/ejbtimer/EjbSchedulerService.java,v
retrieving revision 1.1
diff -r1.1 EjbSchedulerService.java
31c31,36
< LocalTimerServiceHome localTimerServiceHome = (LocalTimerServiceHome) initial.lookup("java:comp/env/ejb/LocalTimerServiceBean");
—
>
>
> //RSC wrong name used
> //LocalTimerServiceHome localTimerServiceHome = (LocalTimerServiceHome) initial.lookup("java:comp/env/ejb/LocalTimerServiceBean");
> //See also change to jboss.xml to include TimerServiceBean or this fix wont work either.
> LocalTimerServiceHome localTimerServiceHome = (LocalTimerServiceHome) initial.lookup("TimerServiceBean");
RCS file: /cvsroot/jbpm/jbpm.3/enterprise/src/main/resources/jar/META-INF/jboss.xml,v
retrieving revision 1.2
diff -r1.2 jboss.xml
12a13,20
> <!-- RSC ADDED THIS -->
> <session>
> <ejb-name>TimerServiceBean</ejb-name>
> <jndi-name>ejb/TimerServiceBean</jndi-name>
> <local-jndi-name>TimerServiceBean</local-jndi-name>
> </session>
>
>
- is incorporated by
-
JBPM-1180 describe in detail the ejb components and the enterprise service factories
- Closed
- is related to
-
JBPM-1046 JobExecutorServlet cannot use local JNDI name to access datasource
- Closed
- relates to
-
JBPM-1119 Timers using EjbSchedulerService are not persisted across JBoss restarts
- Closed