[JBoss JIRA] Commented: (JBPM-228) Allow <variable> to have "any" content for user metadata
by Ronald van Kuijk (JIRA)
[ http://jira.jboss.com/jira/browse/JBPM-228?page=comments#action_12391057 ]
Ronald van Kuijk commented on JBPM-228:
---------------------------------------
This can be retrieved by reading the processdefinition.xml from the context, parsing it to a Dom and/or String and getting the data out of it. This 'issue' was only for changing the xsd
> Allow <variable> to have "any" content for user metadata
> --------------------------------------------------------
>
> Key: JBPM-228
> URL: http://jira.jboss.com/jira/browse/JBPM-228
> Project: JBoss jBPM
> Issue Type: Feature Request
> Components: Core Engine
> Affects Versions: jBPM 3.0 beta 2
> Environment: All
> Reporter: Jim Rigsbee
> Assigned To: Tom Baeyens
> Priority: Minor
> Fix For: jBPM 3.1, jBPM jPDL 3.2
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> Please allow the <variable> element allow "any" schema content just like the "handlers". This would allow the user to store custom metadata for their purposes. This data should be persisted to the database and the API should allow its retrieval just like <action>, <assignment>, and <decision>/<handler>, etc.
> We intend on using this to assist with driving the user interface from the work flow engine. One type of meta data we need is the "java type" for the variable.
--
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
17 years
[JBoss JIRA] Commented: (JBPM-1072) Concurrent JobExecutors can process the same job in parallel
by Len DiMaggio (JIRA)
[ http://jira.jboss.com/jira/browse/JBPM-1072?page=comments#action_12390548 ]
Len DiMaggio commented on JBPM-1072:
------------------------------------
Dec 1 - Jirka
I have tried the following configs
jBPM-win MySQL-win OK
jBPM-linux MySQL-win OK
jBPM-win MySQL-linux FAIL
So the problem is probably related to MySQL on linux
Just talking to Jirka - apparently the this problem is MySQL version specific. He's seeing it pass on Linux with 5.0.27 and fail with 5.0.45
Current disposition for this JIRA:
* SOA-54 and SOA-55 - Mark these as 'resolved', reopen if made necessary - unlikely - by jBPM rework
* JBPM-1071, JBPM-1072 - leave these open as they are jBPM issues
* SOA-195 - New JIRA to require SOA-P to document in Release Notes that when jBPM is used then it is not safe to use MySQL on Linux
* SOA-196 - The jBPM does not work with MySQL/Linux combo - mark as fix in 4.3
* JBPM-1095- Project bug for SOA-196
> Concurrent JobExecutors can process the same job in parallel
> ------------------------------------------------------------
>
> Key: JBPM-1072
> URL: http://jira.jboss.com/jira/browse/JBPM-1072
> Project: JBoss jBPM
> Issue Type: Bug
> Components: Core Engine
> Affects Versions: jBPM jPDL 3.2.2
> Environment: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux
> MySQL 5.0.22
> Reporter: Jiri Pechanec
> Assigned To: Koen Aers
> Attachments: expl.tar.gz
>
>
> Attached is a simple test case that
> 1) Deploys process definition with two nodes
> 2) Starts 20 executor threads
> 2) Starts the process instance that will asynchronously execute action on the second node
> 4) The second node writes a record to the database
> The test case needs to be executed multiple times to see the incorrect behaviour.
> This is an example of run output
> Isol 8
> Action 1
> Success 0
> Failure 0
> Action 2
> Action 2 1
> Action 2
> Action 2 1
> Action 2
> Action 2 1
> Action 2
> Action 2 1
> Action 2
> Action 2 1
> Action 2
> Action 2 1
> Action 2
> Action 2
> Action 2 1
> Action 2 1
> Action 2
> Action 2 1
> Explanation of the outcome
> 9 job executors successfully executed the node action (same job) including database operation. All database operations were comitted (9 new records were created)
--
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
17 years
[JBoss JIRA] Commented: (JBPM-1071) Possible problem in concurrent signalling from multiple threads
by Len DiMaggio (JIRA)
[ http://jira.jboss.com/jira/browse/JBPM-1071?page=comments#action_12390547 ]
Len DiMaggio commented on JBPM-1071:
------------------------------------
Dec 1 - Jirka
I have tried the following configs
jBPM-win MySQL-win OK
jBPM-linux MySQL-win OK
jBPM-win MySQL-linux FAIL
So the problem is probably related to MySQL on linux
Just talking to Jirka - apparently the this problem is MySQL version specific. He's seeing it pass on Linux with 5.0.27 and fail with 5.0.45
Current disposition for this JIRA:
* SOA-54 and SOA-55 - Mark these as 'resolved', reopen if made necessary - unlikely - by jBPM rework
* JBPM-1071, JBPM-1072 - leave these open as they are jBPM issues
* SOA-195 - New JIRA to require SOA-P to document in Release Notes that when jBPM is used then it is not safe to use MySQL on Linux
* SOA-196 - The jBPM does not work with MySQL/Linux combo - mark as fix in 4.3
* JBPM-1095- Project bug for SOA-196
> Possible problem in concurrent signalling from multiple threads
> ---------------------------------------------------------------
>
> Key: JBPM-1071
> URL: http://jira.jboss.com/jira/browse/JBPM-1071
> Project: JBoss jBPM
> Issue Type: Bug
> Components: Core Engine
> Affects Versions: jBPM jPDL 3.2.2
> Environment: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux
> MySQL 5.0.22
> Reporter: Jiri Pechanec
> Assigned To: Len DiMaggio
> Priority: Critical
> Attachments: expl.tar.gz, LockingTest.java, log.txt
>
>
> Attached is a simple test case that
> 1) Deploys process definition with two nodes
> 2) Starts the process instance that will go to the wait state on first node
> 3) Starts 20 threads that tries concurrently signal the same process instance
> 4) The second node writes a record to the database
> The test case needs to be executed multiple times to see the incorrect behaviour.
> This is an example of run output
> Isol 8
> Action 1
> Action 2
> Action 2
> Action 2
> Action 2
> Action 2 1
> Action 2 1
> Action 2 1
> Action 2 1
> Signalist 5
> Signalist 6
> Signalist 8
> Signalist 12
> Signalist 7
> Signalist 13
> Signalist 14
> Signalist 15
> Signalist 9
> Signalist 16
> Signalist 17
> Signalist 18
> Signalist 4
> Success 7
> Failure 13
> Explanation of the outcome
> 4 threads successfully executed the node action including database operation. All database opeartion were comitted (4 new records were created)
> 3 threads successfully executed the signal operation but no real action was performed
> 13 threads attempted to execute the signal operation but ended with an exception
--
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
17 years
[JBoss JIRA] Commented: (JBPM-228) Allow <variable> to have "any" content for user metadata
by Ronald van Kuijk (JIRA)
[ http://jira.jboss.com/jira/browse/JBPM-228?page=comments#action_12390303 ]
Ronald van Kuijk commented on JBPM-228:
---------------------------------------
what feature? The any content? The issues is closed, so yes
> Allow <variable> to have "any" content for user metadata
> --------------------------------------------------------
>
> Key: JBPM-228
> URL: http://jira.jboss.com/jira/browse/JBPM-228
> Project: JBoss jBPM
> Issue Type: Feature Request
> Components: Core Engine
> Affects Versions: jBPM 3.0 beta 2
> Environment: All
> Reporter: Jim Rigsbee
> Assigned To: Tom Baeyens
> Priority: Minor
> Fix For: jBPM 3.1, jBPM jPDL 3.2
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> Please allow the <variable> element allow "any" schema content just like the "handlers". This would allow the user to store custom metadata for their purposes. This data should be persisted to the database and the API should allow its retrieval just like <action>, <assignment>, and <decision>/<handler>, etc.
> We intend on using this to assist with driving the user interface from the work flow engine. One type of meta data we need is the "java type" for the variable.
--
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
17 years