upgrade jbpm to 3.2.6: how to

[lpiccoli]

jbossportal 2.7.2

hi all,

i am upgrading from jbpm3.2.2 to jbpm3.2.6 in jboss portal 2.7.2.

i made the following changes

1. changed the jbpm-identity.jar, jbpm-jpdl.jar
2. changed the conf/hibernate/workflow/hibernate.cfg.xml
3. modifed the jboss-portal.sar\portal-workflow.sar/jboss-service.xml

But the workflow doesnt deploy due to errors below.

21:10:42,843 ERROR [JobExecutorThread] exception in job executor thread. waiting
 20000 milliseconds
org.jbpm.JbpmException: transaction begin failed
 at org.jbpm.persistence.jta.JtaDbPersistenceService.beginTransaction(Jta
DbPersistenceService.java:74)
 at org.jbpm.persistence.jta.JtaDbPersistenceService.<init>(JtaDbPersiste
nceService.java:48)
 at org.jbpm.persistence.jta.JtaDbPersistenceServiceFactory.openService(J
taDbPersistenceServiceFactory.java:66)
 at org.jbpm.svc.Services.getService(Services.java:156)
 at org.jbpm.svc.Services.getPersistenceService(Services.java:196)
 at org.jbpm.JbpmContext.getPersistenceService(JbpmContext.java:699)
 at org.jbpm.JbpmContext.getJobSession(JbpmContext.java:626)
 at org.jbpm.job.executor.JobExecutorThread.acquireJobs(JobExecutorThread
.java:114)
 at org.jbpm.job.executor.JobExecutorThread.run(JobExecutorThread.java:58
)
Caused by: org.jbpm.JbpmException: could not retrieve user transaction with name
 java:comp/UserTransaction
 at org.jbpm.persistence.jta.JtaDbPersistenceServiceFactory.getUserTransa
ction(JtaDbPersistenceServiceFactory.java:90)

any ideas are most appreciated.

-lp

[lpiccoli]

jbpm 3.2.2 is sept 2007 vintage.

has any one upgrade the jbpm?


-lp

[lpiccoli]

looks the problems seems to be that the JbpmThreadService get started without having a JbpmContext.

JbpmThreadService .java
public void start()
 {
 JbpmConfiguration jbpmConfiguration = workflowService.getJbpmConfiguration();
 jbpmConfiguration.getJobExecutor().start();
 }

I am not entirely sure why, but once i programmatically call createJbpmContext the JbpmThreadService seems to function without error from then.

 context = workflowService.getJbpmConfiguration().createJbpmContext();

Q1. is expected behaviour with JbpmContext?
Q2. should client/portlet code be using the workflowservice?

-lp