September 2009 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-2500) make console ServerConfigFactory configurable

by Tom Baeyens (JIRA)

make console ServerConfigFactory configurable --------------------------------------------- Key: JBPM-2500 URL: https://jira.jboss.org/jira/browse/JBPM-2500 Project: jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Console Reporter: Tom Baeyens Assignee: Tom Baeyens Fix For: jBPM 4.2 update ServerConfigFactory so that the needed configurations come from our jbpm.cfg.xml. every usage of ServerConfigFactory.getServerConfig().getSomePropertyValue() should be replaced with Configuration.getProcessEngine().get("SomePropertyValue") -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBPM-1966) clean up classloading

by Tom Baeyens (JIRA)

clean up classloading --------------------- Key: JBPM-1966 URL: https://jira.jboss.org/jira/browse/JBPM-1966 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Fix For: jBPM 4.0.0 Alpha2 in all of jbpm codebase, the context classloader should be taken. all classloader members to provide a classloader programmatically should be removed. if users want to configure the classloader, it should be done with a command service interceptor that sets the current thread context classloader. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
13
0 / 0

[JBoss JIRA] Updated: (JBPM-2526) implement jbpm key generation

by Tom Baeyens (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-2526?page=com.atlassian.jira.plug... ] Tom Baeyens updated JBPM-2526: ------------------------------ Priority: Critical (was: Major) > implement jbpm key generation > ----------------------------- > > Key: JBPM-2526 > URL: https://jira.jboss.org/jira/browse/JBPM-2526 > Project: jBPM > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Tom Baeyens > Assignee: Tom Baeyens > Priority: Critical > Fix For: jBPM 4.2 > > > mechanism: > 1) add JBPM4_PROPERTIES table (See also JBPM-2527) > 2) define a property called NEXTID with a long value that is initialized at 1 > 3) define a KeyGeneratorImpl in the process-engine context, with eager initialization > 4) make sure that all hibernate entities during construction get a value from the id generator > - each id generator will acquire a block of ids by updating the NEXTID property > - block acquisition is guarded with optimistic locking > - ids will be consumed from the block (very fast, without db access) > 5) remove all the explicit flushes > 6) implement a DefaultKeyGenerator that only uses in memory key generation in case people work without persistence > public abstract class KeyGenerator { > // similar as ScriptManager > public static KeyGenerator getKeyGenerator() {...} > // similar as ScriptManager > public static KeyGenerator getDefaultKeyGenerator() {...} > public long getNextId() {...} > } > Motivations: > 1) database portability : see also JBPM-2510 > 2) performance > JBPM-2510 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-2531) adding thread level priorities to job execution

by Tiese Barrell (JIRA)

adding thread level priorities to job execution ----------------------------------------------- Key: JBPM-2531 URL: https://jira.jboss.org/jira/browse/JBPM-2531 Project: jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Runtime Engine Reporter: Tiese Barrell Fix For: jBPM 4.x Below is a description of a number of use cases this can be used for. Comment by Tom Baeyens (email): all these use cases boil down to one technical solution: job prioritization on the thread level. potentially in combination with async continuations which we already have. Use Case: Use priority in a system with multiple process definitions of different complexity to enable rapid responses for instances of simple process definitions without human tasks. Description: Our system provides different interface which consume input data and start new process instances to process these data. The data determine the process definition used to create a new process instance. The system currently supports about 20 different process definitions with varying complexity. The processing of some data sets is quite time consuming due to expensive calculations on large data sets (different data sets starting at 100 kB, mostly around 1 MB to 3 MB, sometimes even more than 10 MB) and complex process definitions involving multiple human tasks. Other data sets are smaller requiring much less calculation and the process definition is designed for rapid (a few seconds) responses without any human tasks. We would like to use priorities handled by jBPM in order to implement a mechanism that provides some limited control on the processing order. We do not expect that jBPM stops processing any process instance that it is currently processing just because a new process instance with higher priority was created. However, we would like to see that jBPM pays attention to priority when choosing a new process instance for processing, e.g. when a lot of process instances wait for processing, start with those having the highest priority. The priority values can be configurable values for the different process definitions or submitted by the originator together with the request which starts a new process instance. Use Case: Process priority needed under heavy load Description: We handle messages in different processes for several customers, using a single jBPM instance. The bulk work of the processes (all for one customer) takes a relatively long time to process (there are external systems involved) whereas some processes (for other customers) are more rare and short term processes, but of greater importance so they need to be handled quickly. jBPM offers no way to distinguish between process based on some sort of priority or to define how many processes may be run in parallel. Current solution: Using pooled executors (external lib) with an internal message queue that assign work to jBPM. Each executor has a number of threads it may use towards jBPM. Which executor is used (messages all arrive from a single JMS queue) depends on some characteristic of the message, which indicates the priority. The priority queue has a certain amount of dedicated threads to work with and the chance short running processes get through quicker is therefore greater, although it's not guaranteed. This solution is far from ideal since it requires an extra library and more importantly, management of the thread pool with all related problems (blocked threads, etc.) Use Case: Customer must indicate whether a process should be handled with priority Description: A flag needs to be set by the customer when creating a process that this should be handled with priority. This basically means that if there are two processes on offer to start (arriving on JMS queues), the priority one should be taken first by jBPM. Logically, this involves throttling throughput of work in a general sense since a workload must be maintained for some time to be able to compare priorities. If there is no other work, low priority processes can be started, but if there are high priority processes, these should go first. To ensure this works with a certain tolerance, you would have to postpone immediate execution (or think of some other solution). Current solution: still in development, but we are leaning towards the one described above. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-1907) provide test convenience methods

by Tom Baeyens (JIRA)

provide test convenience methods -------------------------------- Key: JBPM-1907 URL: https://jira.jboss.org/jira/browse/JBPM-1907 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Fix For: jBPM 4.0.0 Alpha2 see the forum post -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

3
8
0 / 0

[JBoss JIRA] Created: (JBPM-2160) put xsd separately in distro

by Tom Baeyens (JIRA)

put xsd separately in distro ---------------------------- Key: JBPM-2160 URL: https://jira.jboss.org/jira/browse/JBPM-2160 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens probably it is more convenient for our users if the xsd is shipped in our runtime distro maybe the designer can take it from the runtime distro and add it to the catalog -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-2465) Add default

by Ronald van Kuijk (JIRA)

Add default ----------- Key: JBPM-2465 URL: https://jira.jboss.org/jira/browse/JBPM-2465 Project: JBoss jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Ronald van Kuijk -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-2464) Add an method to xmlUtil that takes an xPath as param

by Ronald van Kuijk (JIRA)

Add an method to xmlUtil that takes an xPath as param ----------------------------------------------------- Key: JBPM-2464 URL: https://jira.jboss.org/jira/browse/JBPM-2464 Project: JBoss jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Ronald van Kuijk Assignee: Tom Baeyens Fix For: jBPM 4.x Probably very handy in the near future -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBPM-2463) Tasks view should display all tasks

by Hauke Rabe (JIRA)

Tasks view should display all tasks ----------------------------------- Key: JBPM-2463 URL: https://jira.jboss.org/jira/browse/JBPM-2463 Project: JBoss jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Console Affects Versions: jBPM 4.0 Reporter: Hauke Rabe At this time the task view displays only task for the current user. If I logged in as admin I want to see all tasks and additional use a filter criteria to see only tasks for a particular user id. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

3
2
0 / 0

[JBoss JIRA] Created: (JBPM-2272) add process definition cache key based on processDefinitionId

by Tom Baeyens (JIRA)

add process definition cache key based on processDefinitionId ------------------------------------------------------------- Key: JBPM-2272 URL: https://jira.jboss.org/jira/browse/JBPM-2272 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Runtime Engine Reporter: Tom Baeyens Assignee: Tom Baeyens Fix For: GWT Console 1.0.0 GA each time an execution has to resolve a process definition based on the processDefinitionId, it does a query for the deployment dbid. see RepositorySessionImpl.findProcessDefinitionById -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

3
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues September 2009