[JBoss JIRA] Closed: (JBPM-586) check out quartz for scheduling and messaging
by Tom Baeyens (JIRA)
[ http://jira.jboss.com/jira/browse/JBPM-586?page=all ]
Tom Baeyens closed JBPM-586.
----------------------------
Fix Version/s: (was: jBPM 3.2 alpha 2)
Resolution: Rejected
i evaluated and didn't opt for quartz. integrating it into jBPM was too hard. mainly the db connection management would be really hacky to get quartz to use the same jdbc connection as jBPM. That is what we needed to run fine in a standard environment.
also the extra indirection layer between quartz and jBPM would have added extra unnecessary complexity.
i did get inspired by reading their code and i have developed a unified job scheduler that is used for both asynchronous messaging and timers in jbpm. there's also a completely new locking mechanism.
> check out quartz for scheduling and messaging
> ---------------------------------------------
>
> Key: JBPM-586
> URL: http://jira.jboss.com/jira/browse/JBPM-586
> Project: JBoss jBPM
> Issue Type: Task
> Components: Core Engine
> Reporter: Tom Baeyens
> Assigned To: Tom Baeyens
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 6 months
[JBoss JIRA] Created: (JBPM-754) job scheduler persistence
by Tom Baeyens (JIRA)
job scheduler persistence
-------------------------
Key: JBPM-754
URL: http://jira.jboss.com/jira/browse/JBPM-754
Project: JBoss jBPM
Issue Type: Bug
Components: Core Engine
Reporter: Tom Baeyens
Assigned To: Tom Baeyens
Priority: Critical
Fix For: jBPM 3.2 alpha 2
some unexplainable hibernate problem while trying to lock jobs for execution:
16:08:22,843 [main] DEBUG GraphElement : event 'task-create' on 'Task(clean ceiling)' for 'Token(/)'
16:08:22,875 [main] DEBUG GraphElement : executing action 'CreateTimerAction(dc9766)'
16:08:22,875 [main] DEBUG GraphElement : event 'timer-create' on 'Task(clean ceiling)' for 'Token(/)'
16:08:22,875 [main] DEBUG GraphElement : event 'after-signal' on 'StartState(979f67)' for 'Token(/)'
16:08:22,875 [main] DEBUG Services : executing default save operations
16:08:22,875 [main] DEBUG HibernateSaveOperation : saving process instance
16:08:22,875 [main] DEBUG SaveLogsOperation : flushing logs to logging service.
16:08:22,890 [main] DEBUG CascadeSaveOperation : cascading save of 'org.jbpm.graph.exe.ProcessInstance@ffd135'
16:08:22,890 [main] DEBUG JbpmContext : closing JbpmContext
16:08:22,890 [main] DEBUG Services : closing service 'persistence': org.jbpm.persistence.db.DbPersistenceService@6d2380
16:08:22,890 [main] DEBUG DbPersistenceService : committing hibernate transaction
16:08:22,890 [main] DEBUG DbPersistenceService : closing hibernate session
16:08:22,890 [main] DEBUG Services : closing service 'tx': org.jbpm.tx.TxService@159780d
16:08:22,890 [main] DEBUG Services : closing service 'scheduler': org.jbpm.scheduler.db.DbSchedulerService@d8ca48
16:08:22,890 [main] DEBUG Services : closing service 'logging': org.jbpm.logging.db.DbLoggingService@c8570c
16:08:23,218 [main] DEBUG JobExecutor : starting thread group 'JbpmJobExector'...
16:08:23,218 [main] DEBUG JobExecutor : starting new job executor thread 'JbpmJobExector:192.168.1.100:1'
16:08:23,218 [JbpmJobExector:192.168.1.100:1] DEBUG JbpmContextInfo : creating jbpm context with service factories '[tx, message, scheduler, logging, persistence, authentication]'
16:08:23,218 [JbpmJobExector:192.168.1.100:1] DEBUG JbpmContext : creating JbpmContext
16:08:23,218 [JbpmJobExector:192.168.1.100:1] DEBUG DbPersistenceServiceFactory : creating persistence service
16:08:23,218 [JbpmJobExector:192.168.1.100:1] DEBUG DbPersistenceService : creating hibernate session
16:08:23,218 [main] DEBUG AbstractDbTestCase : going to sleep for 200 millis, waiting for the job executor to process more jobs
16:08:23,218 [JbpmJobExector:192.168.1.100:1] DEBUG DbPersistenceService : beginning hibernate transaction
16:08:23,218 [JbpmJobExector:192.168.1.100:1] DEBUG JobExecutorThread : querying for acquirable job...
16:08:23,375 [JbpmJobExector:192.168.1.100:1] DEBUG JobExecutorThread : trying to obtain a lock for 'timer(ceiling-timer,org.jbpm.taskmgmt.exe.TaskTimerExecutionDbTest$PlusPlus,16:08:22,875)'
16:08:23,406 [JbpmJobExector:192.168.1.100:1] ERROR AssertionFailure : an assertion failure occured (this may indicate a bug in Hibernate, but is more likely due to unsafe use of the session)
org.hibernate.AssertionFailure: collection was not processed by flush(), role=org.jbpm.taskmgmt.def.Task.events
at org.hibernate.engine.CollectionEntry.postFlush(CollectionEntry.java:183)
at org.hibernate.event.def.AbstractFlushingEventListener.postFlush(AbstractFlushingEventListener.java:328)
at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:28)
at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:980)
at org.jbpm.job.executor.JobExecutorThread.acquireJobs(JobExecutorThread.java:125)
at org.jbpm.job.executor.JobExecutorThread.run(JobExecutorThread.java:54)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 6 months