October 2008 - jbpm-users - Jboss List Archives

by letitbe

anyone have an idea or comments really appreciated? thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4181716#4181716 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4181716

16 years

1
0
0 / 0

[JBoss jBPM] - Re: Action not executing in timer

by oravecz

I have confirmed the above suspicion. By adding a context.close() call before I go to sleep, the job is flushed to the database and the JobExecutorThread can update it without the Lock wait timeout exception. Is this a bug or an accepted workaround? I would expect that when I close the context in my unit test, I will now have to reopen it again to lookup a process definition or other such tasks. I feel that the engine should take care of properly commiting as necessary. I can see why commits may want to be deferred for performance reasons, but that strategy falls apart when there are other threads of execution (ala JobExecutor, custom web service, etc.) that is needing to update the database. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4181714#4181714 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4181714

16 years

1
0
0 / 0

[JBoss jBPM] - Re: Action not executing in timer

by oravecz

I am noticing that after the insert of the job by the main thread, the sql is issued but there is no flush from hibernate or subsequent commit. When the JobExecutorThread fires it loads the job, presumably from the second-level cache. When it updates the job and attempts to commit its transaction, I am assuming it is blocked from doing so by the main thread. In fact, the main thread only issues one commit when the process definition is inserted into the database at startup. Is there a way to cause jBPM to flush and commit transactions more frequently, like with every transition? How about after the creation of a job? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4181713#4181713 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4181713

16 years

1
0
0 / 0

[JBoss jBPM] - Re: Action not executing in timer

by oravecz

I removed the signal call, with the same results. I can trace the problem to the JobExecutorThread's acquireJobs() method. The job is read from the db, and it is not "exclusive". Because of this, a lock is acquired on the job. I'm perplexed how this will have any bearing on whether the job is executed later or not. It doesn't really matter however, because the next step is to close the jbpmContext. During this process, the thread doesn't return for a minute or so. When it does eventually return, I receive the following exception: | update JBPM_JOB set VERSION_=1, DUEDATE_=2008-10-12 15:41:51.0, PROCESSINSTANCE_=3, TOKEN_=3, | TASKINSTANCE_=null, ISSUSPENDED_=false, ISEXCLUSIVE_=false, LOCKOWNER_='JbpmJobExecutor:10.1.1.22:1', | LOCKTIME_=2008-10-12 15:41:51.009, EXCEPTION_=null, RETRIES_=1, NAME_='timer1', REPEAT_=null, | TRANSITIONNAME_='end', ACTION_=80, GRAPHELEMENTTYPE_='org.jbpm.graph.node.State', GRAPHELEMENT_=82 | where ID_=3 and VERSION_=0 | java.sql.SQLException: Lock wait timeout exceeded; try restarting transaction | at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1055) | at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:956) | at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3491) | at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3423) | at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1936) | at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2060) | at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2542) | at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:1734) | at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2019) | at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:1937) | at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:1922) | at net.sf.log4jdbc.PreparedStatementSpy.executeUpdate(PreparedStatementSpy.java:1006) | at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:102) | at org.hibernate.persister.entity.AbstractEntityPersister.update(AbstractEntityPersister.java:2435) | at org.hibernate.persister.entity.AbstractEntityPersister.updateOrInsert(AbstractEntityPersister.java:2335) | at org.hibernate.persister.entity.AbstractEntityPersister.update(AbstractEntityPersister.java:2635) | at org.hibernate.action.EntityUpdateAction.execute(EntityUpdateAction.java:115) | at org.hibernate.engine.ActionQueue.execute(ActionQueue.java:279) | at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:263) | at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:168) | at org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:321) | at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:50) | at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1027) | at org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java:365) | at org.hibernate.transaction.JDBCTransaction.commit(JDBCTransaction.java:137) | at org.jbpm.persistence.db.DbPersistenceService.commit(DbPersistenceService.java:263) | at org.jbpm.persistence.db.DbPersistenceService.close(DbPersistenceService.java:218) | at org.jbpm.svc.Services.close(Services.java:236) | at org.jbpm.JbpmContext.close(JbpmContext.java:136) | at org.jbpm.job.executor.JobExecutorThread.acquireJobs(JobExecutorThread.java:138) | at org.jbpm.job.executor.JobExecutorThread.run(JobExecutorThread.java:52) | I don't yet understand the transaction boundaries in place in jBPM. Any time DbPersistenceService.getSession() is called, a new transaction is started. When jbpmContext is closed, the sql is flushed, and transactions are commited. Is it possible that the transactions are started, but do not commit in a timely (or balanced) manner? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4181712#4181712 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4181712

16 years

1
0
0 / 0

[JBoss jBPM] - Re: endTransaction never called in DBPersistenceService

by oravecz

How do I wire in an external transaction manager. Do I replace the TxServiceFactory? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4181711#4181711 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4181711

16 years

1
0
0 / 0

[JBoss jBPM] - Re: endTransaction never called in DBPersistenceService

by kukeltje

when you close the JbpmContext, the transaction is ended if it is configured that jBPM should do this. Otherwise (e.g. if an external transactionmanager is used) it is left to that View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4181707#4181707 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4181707

16 years

1
0
0 / 0

[JBoss jBPM] - Re: Problem with java.sql.Date as Variable

by kukeltje

the same object? or the same value? A small wrapper to convert it for you is much easier I think then making changes to the jBPM core. Or you can even try to write a converter for jBPM. (see the testcases in the source how this can be done). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4181706#4181706 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4181706

16 years

1
0
0 / 0

[JBoss jBPM] - Re: Action not executing in timer

by kukeltje

Try the change I proposed and see. There have been (very recently) similar 'problems' due to this 'misconfiguration' View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4181705#4181705 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4181705

16 years

1
0
0 / 0

[JBoss jBPM] - endTransaction never called in DBPersistenceService

by oravecz

As I'm trying to root out what appears to be transaction troubles, I can't seem to see where the endTransaction() method is called in the class org.jbpm.persistence.db.DbPersistenceService. It seems important as this is where the transaction is committed and data is flushed to the database. Is this an oversight, or is this work handled elsewhere? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4181700#4181700 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4181700

16 years

1
0
0 / 0

[JBoss jBPM] - Re: Job Executor and Spring

by oravecz

I don't want to quibble over configuration placement. For those applications that make heavy use of Spring configuration already, doing some or all of this configuration makes sense, especially when it comes to a unified transaction manager. After all, jBPM has an object factory for a reason. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4181695#4181695 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4181695

16 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

jbpm-users October 2008