[jboss-user] [JBoss jBPM] - Re: async pain

[kukeltje]

"ax666" wrote : Ronald, you're absolutely right, but there's nothing I can do now.
  | Our hacks are not of a quality for a patch. I can quickly describe what we did:
  | - new job executor who is starting 1 job reader thread
  | - job reader thread uses java executor service for thread pool
  | - reads jobs from db and starts new single job execution thread for each job
  | - synchronize on "exclusive" and on process id/node
  | - wait 1 second in each single job execution thread to not interfere with other jobs still running, this is the worst part, but it works
  | - changes are extensions, no patches. new job executor configured in jbpm config
  | 
  | 

I asked one of the core developers to comment on this, so let's wait on that. Mind that real-time processing was never one of the main requirements of jBPM, so the 1 second is not to bad imo (jms could do this automatically for you with the retry-timeout)

"ax666" wrote : 
  | too bad above doesn't work with 3.2.1

Hmm... so you mean there is a difference in this area between 3.2 and 3.2.1? 

"ax666" wrote : 
  | how many is "many people" ?
  | 

A few hundred.... no just kidding... getting it in the top 10 of most voted issues should be enough.. 3-5 votes i think

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

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