[JBoss JIRA] Assigned: (JBPM-165) process instance versioning
by Tom Baeyens (JIRA)
[ https://jira.jboss.org/jira/browse/JBPM-165?page=com.atlassian.jira.plugi... ]
Tom Baeyens reassigned JBPM-165:
--------------------------------
Assignee: (was: Tom Baeyens)
> process instance versioning
> ---------------------------
>
> Key: JBPM-165
> URL: https://jira.jboss.org/jira/browse/JBPM-165
> Project: JBoss jBPM
> Issue Type: Feature Request
> Components: Core Engine
> Reporter: Tom Baeyens
> Fix For: jBPM 3.3.1 GA
>
>
> i think jbpm could offer some degree of assistence in process instance versioning.
> when a new version of a process is deployed, jbpm could do the following conversion for a process instance :
> * input required: mapping of the nodes from the old to the new definition.
> * cancel the old process instance
> * create a new process instance and copy the runtime (exe) information such as tokens and process variables from the old process instance.
> * then establish a special link between the 2 process instances to indicate that the new process instance is the continuation of the old process instance.
> this way we can avoid the problematic conversion of logs, while still keeping them in the system.
--
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
16 years, 1 month
[JBoss JIRA] Updated: (JBPM-1223) Add "and" to duration language in timers
by Tom Baeyens (JIRA)
[ https://jira.jboss.org/jira/browse/JBPM-1223?page=com.atlassian.jira.plug... ]
Tom Baeyens updated JBPM-1223:
------------------------------
Fix Version/s: jBPM 4.0.0 Alpha2
(was: jBPM 4.0.0 Alpha1)
this should be decided/handled when we introduce the business calendar capaiblity in jbpm 4
> Add "and" to duration language in timers
> ----------------------------------------
>
> Key: JBPM-1223
> URL: https://jira.jboss.org/jira/browse/JBPM-1223
> Project: JBoss jBPM
> Issue Type: Task
> Components: PVM
> Environment: All
> Reporter: Jim Rigsbee
> Assignee: Tom Baeyens
> Priority: Minor
> Fix For: jBPM 4.0.0 Alpha2
>
>
> Currently the PDL allows for duration expressions of the type <quantity> {business} <unit>, e.g. 5 business hours or 5 days. Please expand this to allow the word "and" between multiple nodes. The time should be aggregated as milliseconds. Some examples,
> 5 business days and 2 hours,
> 1 month and 25 days and 2 minutes
> Tom's suggestion is that if business appears anywhere in the string that the entire duration is considered to be in "business time".
--
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
16 years, 1 month
[JBoss JIRA] Created: (JBPM-1829) Sybase transaction log full - dump needed
by Thomas Diesler (JIRA)
Sybase transaction log full - dump needed
-----------------------------------------
Key: JBPM-1829
URL: https://jira.jboss.org/jira/browse/JBPM-1829
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Productization
Reporter: Thomas Diesler
Fix For: jBPM 3.3.1 GA
After multiple QA runs, the sybase transaction log becomes full and the testsuite stops
Running org.jbpm.examples.raise.RaiseRequestTest
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1,001.558 sec
As a system admin you can dump the log like this.
[sybase@jbws ~]$ isql -Usa -P -SJBPM -Djbpmtest
1> dump transaction jbpmtest with truncate_only
2> go
Please monitor db transactions and explain why there are so many open transactions the stay open for a long time.
Run a continous test against sybase and monitor the db state.
I fear that we have a jdbc connection leak or uncommited transactions.
Anyway, the db should not just log because the Tx log becomes full
--
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
16 years, 1 month