[JBoss JIRA] Created: (JBPM-2785) Description tag on activity not parsed
by Sofie Ravyts (JIRA)
Description tag on activity not parsed
--------------------------------------
Key: JBPM-2785
URL: https://jira.jboss.org/jira/browse/JBPM-2785
Project: jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: jBPM 4.x
Reporter: Sofie Ravyts
Fix For: jBPM 4.x
When adding descriptions to the activities in the jpdl, these are not parsed:
In JpdlParser.java line 308 the description of the process xml element is read instead of the nestedElement (the activity):
Element descriptionElement = XmlUtil.element(documentElement, "description");
if (descriptionElement!=null) {
String description = XmlUtil.getContentText(descriptionElement);
activity.setDescription(description);
}
--
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
14 years, 7 months
[JBoss JIRA] Created: (JBPM-2794) Constraint vailoation when moving from wait state using timer that result in looping back to the same wait state
by Maciej Swiderski (JIRA)
Constraint vailoation when moving from wait state using timer that result in looping back to the same wait state
----------------------------------------------------------------------------------------------------------------
Key: JBPM-2794
URL: https://jira.jboss.org/jira/browse/JBPM-2794
Project: jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.3, jBPM 4.4
Environment: Windows XP, Java 1.6, Test case, JBoss 5.1.0
Reporter: Maciej Swiderski
Attachments: jbpm-testcase.zip
It is impossible to go from one state where transition is made by timer that goes thru java activity and decision point and gets back to the same state for retry.
Problem only exists if timer is assigned to a wait state and all nodes are executed synchnously.
Error that is thrown is:
10:57:13,382 WRN | [JDBCExceptionReporter] SQL Error: -104, SQLState: 23000
10:57:13,382 SEV | [JDBCExceptionReporter] Violation of unique constraint $$: duplicate value(s) for column(s) $$: SYS_CT_50 in statement [update JBPM4_EXECUTION set DBVERSION_=?, ACTIVITYNAME_=?, PROCDEFID_=?, HASVARS_=?, NAME_=?, KEY_=?, ID_=?, STATE_=?, SUSPHISTSTATE_=?, PRIORITY_=?, HISACTINST_=?, PARENT_=?, INSTANCE_=?, SUPEREXEC_=?, SUBPROCINST_=? where DBID_=? and DBVERSION_=?]
### EXCEPTION ###########################################
10:57:13,382 SEV | [AbstractFlushingEventListener] Could not synchronize database state with session
org.hibernate.exception.ConstraintViolationException: could not update: [org.jbpm.pvm.internal.model.ExecutionImpl#15]
Attached is a eclipse project with minimal test case for it that illustrates the problem. The same test project is attached to discussion on forum.
Workaround is to make one on the nodes between states to be async.
--
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
14 years, 7 months
[JBoss JIRA] Created: (JBPM-2750) need delete the duplicated field 'state' in TaskImpl
by Huisheng Xu (JIRA)
need delete the duplicated field 'state' in TaskImpl
----------------------------------------------------
Key: JBPM-2750
URL: https://jira.jboss.org/jira/browse/JBPM-2750
Project: jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.3
Environment: Windows XP, JDK1.5.0_15, Maven-2.2.1
Reporter: Huisheng Xu
Fix For: jBPM 4.4
How could we find out this bug?
If you invoke repositoryService.suspendDeployment(deploymentDbid), you will find out that the state of relative tasks is still 'open'.
Because there is a duplicated field 'state' in both TaskImpl and ScopeInstanceImpl. when we invoke 'taskImpl.suspend()' method, this method is defined in ScopeInstanceImpl.
in this method, the 'state' of ScopeInstanceImpl field will be changed to 'suspend', but the 'state' of TaskImpl field still be 'open', so in the end, no matter how we invoke the suspend() method, the TaskImpl is still open, it won't be suspended.
So I think we should delete the duplicated field 'state' of TaskImpl.
--
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
14 years, 7 months
[JBoss JIRA] Created: (JBPM-2755) EL support in task
by henry donnell (JIRA)
EL support in task
-------------------
Key: JBPM-2755
URL: https://jira.jboss.org/jira/browse/JBPM-2755
Project: jBPM
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: jBPM 4.4
Reporter: henry donnell
Fix For: jBPM 4.4
it would be helpful to be able to use EL in the <description> tag of the (human) task node.
This will allow to create dynamical task descriptions based on the process variables.
Example:
<task name="review_task">
<description>Review order nr.#{order.nr} from customer #{order.customer.name}</description>
</task>
The main purpose is to make human task descriptions in the task list more readable and user-friendly.
Because if you have 20 task instances of the same task and they are all called "Review order from customer" it is really hard to see at a first glance which task is related to which customer.
--
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
14 years, 7 months
[JBoss JIRA] Created: (JBPM-2642) A patch to support DB2 on zOS
by Richard L. Burton III (JIRA)
A patch to support DB2 on zOS
-----------------------------
Key: JBPM-2642
URL: https://jira.jboss.org/jira/browse/JBPM-2642
Project: jBPM
Issue Type: Patch
Security Level: Public (Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 3.2.8, jBPM 3.2.7
Environment: Java version: 1.6.0_16,Sun Microsystems Inc., OS-System: Windows XP 5.1,x86, jboss-soa-p.4.3.0, DB2, version: DSN09015, Hibernate 3.2.4.sp1.cp08
Reporter: Richard L. Burton III
Priority: Blocker
Attachments: findJobsWithOverdueLockTime.patch
When using jBPM with DB2 on zOS the JobSession object throws an exception when trying to find jobs with overdue lock time. The exception thrown is:
DB2 SQL error: SQLCODE: -180, SQLSTATE: 22007, SQLERRMC: 1
I attached a patch which corrects this problem. Currently JobSession#findJobsWithOverdueLockTime(Date) is using Query#setDate(..) instead of Query#setTimestamp(...)
This isn't a problem when using the DB2 Universal version on windows, only on zOS.
--
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
14 years, 7 months
[JBoss JIRA] Created: (JBPM-1139) The ClassUtil class is not thread-safe
by Wojciech Gdela (JIRA)
The ClassUtil class is not thread-safe
--------------------------------------
Key: JBPM-1139
URL: http://jira.jboss.com/jira/browse/JBPM-1139
Project: JBoss jBPM
Issue Type: Bug
Components: Core Engine
Affects Versions: jBPM jPDL 3.2.3
Reporter: Wojciech Gdela
Assigned To: Tom Baeyens
Attachments: ClassUtil-concurrency-issue.zip
The ClassUtil class is not thread-safe. The exception will occur when two thread simultanously try do deserialize variables from two different process definitions. Look at the code:
{code}
public ContextObjectInputStream(final InputStream in,
ProcessInstance processInstance) throws IOException {
super(in);
this.setProcessInstance(processInstance);
ClassUtil.setProcessInstance(processInstance);
}
...
protected Class resolveClass(final ObjectStreamClass desc)
throws IOException, ClassNotFoundException {
return ClassUtil.forName(desc.getName(), ContextObjectInputStream.class);
}
...
ContextObjectInputStream cois = new ContextObjectInputStream(bais, definition.createProcessInstance());
// when here another thread tries to execute the same code with another process instance there will be a problem
return cois.readObject();
{/code}
Further description of issue is in attached test case.
--
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
14 years, 7 months
[JBoss JIRA] Created: (JBPM-2591) Simulation module has transitive dependency on commons-beanutils
by Alejandro Guizar (JIRA)
Simulation module has transitive dependency on commons-beanutils
----------------------------------------------------------------
Key: JBPM-2591
URL: https://jira.jboss.org/jira/browse/JBPM-2591
Project: jBPM
Issue Type: Task
Components: Runtime Engine
Affects Versions: jBPM 3.2.8
Environment: hsqldb
java14
linux
Reporter: Alejandro Guizar
Priority: Minor
Fix For: jBPM 3.2.x
A recent CI build failed due to:
[INFO] Compilation failure
/qa/hudson_ws/workspace/jbpm3-jboss405/database/hsqldb/jdk/java14/label/linux/jbpm/modules/simulation/src/main/java/org/jbpm/sim/def/JbpmSimulationModel.java:[10,36] package org.apache.commons.beanutils does not exist
/qa/hudson_ws/workspace/jbpm3-jboss405/database/hsqldb/jdk/java14/label/linux/jbpm/modules/simulation/src/main/java/org/jbpm/sim/def/JbpmSimulationModel.java:[607,8] cannot find symbol
symbol : variable PropertyUtils
location: class org.jbpm.sim.def.JbpmSimulationModel
/qa/hudson_ws/workspace/jbpm3-jboss405/database/hsqldb/jdk/java14/label/linux/jbpm/modules/simulation/src/main/java/org/jbpm/sim/def/JbpmSimulationModel.java:[609,23] cannot find symbol
symbol : variable PropertyUtils
location: class org.jbpm.sim.def.JbpmSimulationModel
jbpm-simulation depends on jasperreports which in turn depends on commons-beanutils. Yet jbpm-simulation uses commons-beanutils directly, and should not rely on jasperreports' dependencies.
--
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
14 years, 7 months