[JBoss JIRA] Created: (BPEL-271) NPE when a start IMA references a nonglobal variable
by Alejandro Guizar (JIRA)
NPE when a start IMA references a nonglobal variable
----------------------------------------------------
Key: BPEL-271
URL: http://jira.jboss.com/jira/browse/BPEL-271
Project: JBoss jBPM BPEL
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Engine
Affects Versions: jBPM BPEL 1.1 beta 3
Reporter: Alejandro Guizar
Assigned To: Alejandro Guizar
Priority: Critical
Fix For: jBPM BPEL 1.1 GA
A start IMA (inbound message activity) can legally occur inside a scope and variables local to that scope. The revised ATM example illustrates this scenario. When jBPM BPEL delivers a message to the aforementioned IMA, it causes a NPE because it initializes global variables only.
This problem affects references to non-global partner links and correlation sets as well.
--
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
16 years, 7 months
[JBoss JIRA] Created: (BPEL-262) redeliver messages whose handling fails due to stale state exceptions
by Alejandro Guizar (JIRA)
redeliver messages whose handling fails due to stale state exceptions
---------------------------------------------------------------------
Key: BPEL-262
URL: http://jira.jboss.com/jira/browse/BPEL-262
Project: JBoss jBPM BPEL
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Engine
Reporter: Alejandro Guizar
Assigned To: Alejandro Guizar
Fix For: jBPM BPEL 1.1 GA
PROBLEM. Upon message reception, a new transaction begins and process execution proceeds. It is possible that other portions of the process execute in separate transactions. Concurrent process execution may cause stale state or lock acquisition exceptions to be thrown in one or more transactions.
PROPOSAL. Detect stale state and lock acquisition exceptions in JMS message listeners. Do not acknowledge the affected message. Recover the JMS session.
--
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
16 years, 7 months
[JBoss JIRA] Created: (BPEL-263) incorporate enterprise support features from jpdl
by Alejandro Guizar (JIRA)
incorporate enterprise support features from jpdl
-------------------------------------------------
Key: BPEL-263
URL: http://jira.jboss.com/jira/browse/BPEL-263
Project: JBoss jBPM BPEL
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Engine
Affects Versions: jBPM BPEL 1.1 beta 3
Reporter: Alejandro Guizar
Assigned To: Alejandro Guizar
Priority: Critical
Fix For: jBPM BPEL 1.1 GA
jBPM jPDL 3.2 introduced a number of enterprise features, including a scheduler service based on the EJB timer service and a persistence service configured for JTA. Due to its reliance on J2EE Web Services, jBPM BPEL always runs in an enterprise environment. Incorporating the enterprise features available in jPDL is a clear step towards taking better advantage of the functionality offered by the application server.
--
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
16 years, 7 months
[JBoss JIRA] Created: (BPEL-266) incorporate targetNamespace in process definition versioning
by Alejandro Guizar (JIRA)
incorporate targetNamespace in process definition versioning
------------------------------------------------------------
Key: BPEL-266
URL: http://jira.jboss.com/jira/browse/BPEL-266
Project: JBoss jBPM BPEL
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Engine
Affects Versions: jBPM BPEL 1.1 beta 3
Reporter: Alejandro Guizar
Assigned To: Alejandro Guizar
Fix For: jBPM BPEL 1.1 GA
PROBLEM So far, process definition versioning has ignored the targetNamespace attribute. Unlike jPDL, BPEL uses qualified names for processes. The targetNamespace attribute is mandatory and must be taken into account when determining the latest process definition for a given name.
SOLUTION Extend the existing GraphSession with process deployment/query methods that explicitly take the targetNamespace as a parameter.
--
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
16 years, 7 months
[JBoss JIRA] Created: (BPEL-257) rename correlation patterns
by Alejandro Guizar (JIRA)
rename correlation patterns
---------------------------
Key: BPEL-257
URL: http://jira.jboss.com/jira/browse/BPEL-257
Project: JBoss jBPM BPEL
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Engine
Affects Versions: jBPM BPEL 1.1 beta 3
Reporter: Alejandro Guizar
Assigned To: Alejandro Guizar
Fix For: jBPM BPEL 1.1 GA
PROBLEM:
In BPEL 2, the enumerated values of the pattern attribute in <correlation> occurrences within <invoke> changed from the obscure "out", "in" and "out-in" to the much clearer "request", "response" and "request-response".
PROPOSAL:
Update the parser and the upgrade xsl templates to accommodate the new enumerated values.
--
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
16 years, 7 months
[JBoss JIRA] Created: (BPEL-260) Flow activity might not reactivate parent token in race condition
by Alejandro Guizar (JIRA)
Flow activity might not reactivate parent token in race condition
-----------------------------------------------------------------
Key: BPEL-260
URL: http://jira.jboss.com/jira/browse/BPEL-260
Project: JBoss jBPM BPEL
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Engine
Affects Versions: jBPM BPEL 1.1 beta 3
Reporter: Alejandro Guizar
Assigned To: Alejandro Guizar
Priority: Critical
Fix For: jBPM BPEL 1.1 GA
The flow activity suffers from the same problem as the join node in jPDL. When child tokens performing each nested activity finish concurrently, it is possible that all of them determine that the parent token must not be reactivated yet, leading to deadlock. The cause of this behavior is transaction isolation.
To prevent this problem, the code to leave the flow must acquire exclusive access to the state of the concurrent tokens.
--
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
16 years, 7 months