February 2008 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Resolved: (JBPM-725) Set auto-import="false" for all hibernate-mapping elements in hibernate mapping files.

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-725?page=all ] Alejandro Guizar resolved JBPM-725. ----------------------------------- Resolution: Done All subtasks have been resolved. > Set auto-import="false" for all hibernate-mapping elements in hibernate mapping files. > -------------------------------------------------------------------------------------- > > Key: JBPM-725 > URL: http://jira.jboss.com/jira/browse/JBPM-725 > Project: JBoss jBPM > Issue Type: Bug > Affects Versions: jBPM 3.1.2, jBPM 3.1.1, jBPM jPDL 3.2, jBPM jPDL 3.2.1 > Reporter: Stefan Lang > Assigned To: Kevin Klinemeier > Fix For: jBPM jPDL 3.2.2 > > > The auto-import attribute of the hibernate-mapping elements in all hbm.xml files is not set. > Thus it is possible to use unqualified class names in Hibernate queries. > The problem is that name clashes with client code are very probable. > E.g. we have an "Event" entity class, jbpm has one too, so the following: > "select Event as e ..." > causes a hibernate exception. > We have set the auto-import attribute to "false" in all jbpm hbm files and > it works now as expected. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-725) Set auto-import="false" for all hibernate-mapping elements in hibernate mapping files.

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-725?page=all ] Alejandro Guizar updated JBPM-725: ---------------------------------- Fix Version/s: jBPM jPDL 3.2.2 > Set auto-import="false" for all hibernate-mapping elements in hibernate mapping files. > -------------------------------------------------------------------------------------- > > Key: JBPM-725 > URL: http://jira.jboss.com/jira/browse/JBPM-725 > Project: JBoss jBPM > Issue Type: Bug > Affects Versions: jBPM 3.1.2, jBPM 3.1.1, jBPM jPDL 3.2, jBPM jPDL 3.2.1 > Reporter: Stefan Lang > Assigned To: Kevin Klinemeier > Fix For: jBPM jPDL 3.2.2 > > > The auto-import attribute of the hibernate-mapping elements in all hbm.xml files is not set. > Thus it is possible to use unqualified class names in Hibernate queries. > The problem is that name clashes with client code are very probable. > E.g. we have an "Event" entity class, jbpm has one too, so the following: > "select Event as e ..." > causes a hibernate exception. > We have set the auto-import attribute to "false" in all jbpm hbm files and > it works now as expected. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBPM-1072) Concurrent JobExecutors can process the same job in parallel

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-1072?page=comments#action_12398860 ] Alejandro Guizar commented on JBPM-1072: ---------------------------------------- I have applied the above changes to Services and JobExecutorThread. I also committed an adapted version of the MultiJobExecutorTest. Note that even if acquireJobs() returns an empty list upon a StaleObjectStateException, jobs keep being processed in parallel, but to a lesser extent. What really does the trick is giving each job executor a different name. When this is done, no two job executors process the same job. Plus, no stale state exceptions get thrown. > 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: Alejandro Guizar > 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

16 years, 2 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBPM-1072) Concurrent JobExecutors can process the same job in parallel

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-1072?page=all ] Alejandro Guizar reassigned JBPM-1072: -------------------------------------- Assignee: Alejandro Guizar (was: Koen Aers) > 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: Alejandro Guizar > 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

16 years, 2 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBPM-1072) Concurrent JobExecutors can process the same job in parallel

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-1072?page=comments#action_12398851 ] Alejandro Guizar commented on JBPM-1072: ---------------------------------------- JobExecutorThreads lock jobs using their name. The name is constructed as follows: jobExecutorName : hostAddress : index Indeed, if you start n job executors on the same machine, you will end up with n threads with the same name. Each job could be executed up to n times! This situation does not occur if you give a different name to each job executor In addition to the changes in my previous comment, job executors running in the same machine must be given different names. > 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

16 years, 2 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBPM-1072) Concurrent JobExecutors can process the same job in parallel

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-1072?page=comments#action_12398846 ] Alejandro Guizar commented on JBPM-1072: ---------------------------------------- Consider the following code. protected Collection acquireJobs() { Collection acquiredJobs = null; log.debug("acquiring jobs for execution..."); JbpmContext jbpmContext = jbpmConfiguration.createJbpmContext(); try { try { ... } finally { jbpmContext.close(); } acquiredJobs = jobsToLock; log.debug("obtained locks on following jobs: "+acquiredJobs); } catch (StaleStateException e) { log.debug("couldn't acquire lock on job(s): "+jobsToLock); } return acquiredJobs; } The catch block is never executed if a StaleStateException is thrown inside jbpmContext.close(). This is because: 1) DbPersistenceService.close() catches it, rolls back the transaction and wraps it into a JbpmPersistenceException 12:09:42,687 [JbpmJobExector:192.168.125.34:1] INFO DbPersistenceService : optimistic locking failed 12:09:42,687 [JbpmJobExector:192.168.125.34:1] DEBUG DbPersistenceService : rolling back hibernate transaction 12:09:42,687 [JbpmJobExector:192.168.125.34:1] DEBUG DbPersistenceService : closing hibernate session 2) Services.close() logs the JbpmPersistenceException but does not rethrow it. 12:09:42,687 [JbpmJobExector:192.168.125.34:1] INFO Services : problem closing service 'persistence': optimistic locking failed 3) The exception does not reach the JobExecutorThread, which proceeds as if nothing had happened. 12:09:42,687 [JbpmJobExector:192.168.125.34:1] DEBUG JobExecutorThread : obtained locks on following jobs: [job[444795]] As I see it, Services.close() has to rethrow the JbpmPersistenceException, even if the cause is a StaleObjectStateException. Currently it suppresses *any* JbpmPersistenceException! In turn, JobExecutorThread has to catch JbpmPersistenceException instead of StaleStateException. > 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

16 years, 2 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBPM-1072) Concurrent JobExecutors can process the same job in parallel

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-1072?page=comments#action_12398842 ] Alejandro Guizar commented on JBPM-1072: ---------------------------------------- Alexey Kostylev said: Yes, you are right. If we have 1 job executor on 1 machine all is working fine. The problem was if launching several job executors on 1 machine. But this is also is not a real problem for us. The real problem is [that] the result of query 'JobSession.getFirstAcquirableJob' is always returned from the method acquireJobs() not depending on if optimistic locking is failed or not [as posted above]. > 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

16 years, 2 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBPM-1072) Concurrent JobExecutors can process the same job in parallel

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-1072?page=comments#action_12398841 ] Alejandro Guizar commented on JBPM-1072: ---------------------------------------- Alexey Kostylev said: Yes, you are right. If we have 1 job executor on 1 machine all is working fine. The problem was if launching several job executors on 1 machine. But this is also is not a real problem for us. The real problem is: The result of query 'JobSession.getFirstAcquirableJob' is always returned from the method acquireJobs() not depending on if optimistic locking is failed or not. Here is the log: ... 12:09:42,687 [JbpmJobExector:192.168.125.34:1] DEBUG JobExecutorThread : querying for acquirable job... 12:09:42,687 [JbpmJobExector:192.168.125.34:1] DEBUG JobExecutorThread : trying to obtain a lock for 'job[444795]' 12:09:42,687 [JbpmJobExector:192.168.125.34:1] DEBUG JbpmContext : closing jbpmContext org.jbpm.JbpmContext@274874 <mailto:org.jbpm.JbpmContext@274874> 12:09:42,687 [JbpmJobExector:192.168.125.34:1] DEBUG Services : closing service 'persistence': org.jbpm.persistence.db.DbPersistenceService@116ce6e <mailto:org.jbpm.persistence.db.DbPersistenceService@116ce6e> 12:09:42,687 [JbpmJobExector:192.168.125.34:1] DEBUG DbPersistenceService : committing hibernate transaction org.hibernate.transaction.JDBCTransaction@105f759 <mailto:org.hibernate.transaction.JDBCTransaction@105f759> 12:09:42,687 [JbpmJobExector:192.168.125.34:1] INFO DbPersistenceService : optimistic locking failed 12:09:42,687 [JbpmJobExector:192.168.125.34:1] DEBUG DbPersistenceService : rolling back hibernate transaction 12:09:42,687 [JbpmJobExector:192.168.125.34:1] DEBUG DbPersistenceService : closing hibernate session 12:09:42,687 [JbpmJobExector:192.168.125.34:1] INFO Services : problem closing service 'persistence': optimistic locking failed 12:09:42,687 [JbpmJobExector:192.168.125.34:1] DEBUG Services : closing service 'tx': org.jbpm.tx.TxService@4aa085 <mailto:org.jbpm.tx.TxService@4aa085> 12:09:42,687 [JbpmJobExector:192.168.125.34:1] DEBUG JobExecutorThread : obtained locks on following jobs: [job[444795]] ... > 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

16 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-1072) Concurrent JobExecutors can process the same job in parallel

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-1072?page=all ] Alejandro Guizar updated JBPM-1072: ----------------------------------- Comment: was deleted > 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

16 years, 2 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBPM-1072) Concurrent JobExecutors can process the same job in parallel

by Tom Baeyens (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-1072?page=comments#action_12398458 ] Tom Baeyens commented on JBPM-1072: ----------------------------------- " As I investigate this issue I find that the problem with running several JobExecutor instances on the same machine is in query condition: where ( (job.lockOwner is null) or (job.lockOwner = :lockOwner) ) So 'lockOwner' is the same for all instances on the same machine, so every instance capture jobs that are executing on other instances at that time. " first, every *thread* has its own name. each thread within the same job executor should get it's own sequence number. so it's ip-address:thread-sequence-number. so locking is based on thread, not on the machine level. this should work as long as you have 1 job executor on one machine. i read that query as 'get all jobs that are not yet locked or for which I am the lock owner'. that should be good, no ? > 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

16 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues February 2008