[JBoss JIRA] Resolved: (JBPM-1452) JbpmConfiguration assumes the object factory has a jbpm.job.executor entry
by Thomas Diesler (JIRA)
[ https://jira.jboss.org/jira/browse/JBPM-1452?page=com.atlassian.jira.plug... ]
Thomas Diesler resolved JBPM-1452.
----------------------------------
Fix Version/s: jBPM 3.3.0 CR1
(was: jBPM 3.3.0)
Resolution: Done
> JbpmConfiguration assumes the object factory has a jbpm.job.executor entry
> --------------------------------------------------------------------------
>
> Key: JBPM-1452
> URL: https://jira.jboss.org/jira/browse/JBPM-1452
> Project: JBoss jBPM
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: jBPM 3.3.0 CR1
> Environment: 3.3 snapshot
> Spring
> Reporter: Alejandro Guizar
> Assignee: Alejandro Guizar
> Fix For: jBPM 3.3.0 CR1
>
>
> The following exception is thrown while completing a task that ends a process. The application runs with the 3.3 snapshot JAR.
> org.jbpm.configuration.ConfigurationException: name 'jbpm.job.executor' is not defined in the configuration. configured names: [resource.hibernate.queries.hbm.xml, jbpm.msg.wait.timout, jbpm.task.instance.factory, resource.default.modules, resource.varmapping, resource.business.calendar, resource.action.types, resource.parsers, default.jbpm.context, resource.node.types, resource.converter, jbpm.variable.resolver, jbpm.byte.block.size]
> at org.jbpm.configuration.ObjectFactoryImpl.createObject(ObjectFactoryImpl.java:76)
> at org.jbpm.JbpmConfiguration.getJobExecutor(JbpmConfiguration.java:603)
> at org.jbpm.scheduler.db.DbSchedulerService.<init>(DbSchedulerService.java:51)
> at org.jbpm.scheduler.db.DbSchedulerServiceFactory.openService(DbSchedulerServiceFactory.java:32)
> at org.jbpm.svc.Services.getService(Services.java:156)
> at org.jbpm.svc.Services.getCurrentService(Services.java:94)
> at org.jbpm.graph.exe.ProcessInstance.end(ProcessInstance.java:328)
> at org.jbpm.graph.exe.Token.notifyParentOfTokenEnd(Token.java:329)
> at org.jbpm.graph.exe.Token.end(Token.java:301)
> at org.jbpm.graph.exe.Token.end(Token.java:251)
> at org.jbpm.graph.node.EndState.execute(EndState.java:59)
> The 3.3 snapshot is looking for 'jbpm.job.executor' which is defined in the default.jbpm.cfg.xml, but which the application does not have in its jbpm.cfg.xml. It works with 3.2.2. The JobExecutor is set up manually in a Spring configuration.
--
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
[JBoss JIRA] Reopened: (JBPM-1452) JbpmConfiguration assumes the object factory has a jbpm.job.executor entry
by Thomas Diesler (JIRA)
[ https://jira.jboss.org/jira/browse/JBPM-1452?page=com.atlassian.jira.plug... ]
Thomas Diesler reopened JBPM-1452:
----------------------------------
Hangs with MySQL
> JbpmConfiguration assumes the object factory has a jbpm.job.executor entry
> --------------------------------------------------------------------------
>
> Key: JBPM-1452
> URL: https://jira.jboss.org/jira/browse/JBPM-1452
> Project: JBoss jBPM
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: jBPM 3.3.0 CR1
> Environment: 3.3 snapshot
> Spring
> Reporter: Alejandro Guizar
> Assignee: Alejandro Guizar
> Fix For: jBPM 3.3.0
>
>
> The following exception is thrown while completing a task that ends a process. The application runs with the 3.3 snapshot JAR.
> org.jbpm.configuration.ConfigurationException: name 'jbpm.job.executor' is not defined in the configuration. configured names: [resource.hibernate.queries.hbm.xml, jbpm.msg.wait.timout, jbpm.task.instance.factory, resource.default.modules, resource.varmapping, resource.business.calendar, resource.action.types, resource.parsers, default.jbpm.context, resource.node.types, resource.converter, jbpm.variable.resolver, jbpm.byte.block.size]
> at org.jbpm.configuration.ObjectFactoryImpl.createObject(ObjectFactoryImpl.java:76)
> at org.jbpm.JbpmConfiguration.getJobExecutor(JbpmConfiguration.java:603)
> at org.jbpm.scheduler.db.DbSchedulerService.<init>(DbSchedulerService.java:51)
> at org.jbpm.scheduler.db.DbSchedulerServiceFactory.openService(DbSchedulerServiceFactory.java:32)
> at org.jbpm.svc.Services.getService(Services.java:156)
> at org.jbpm.svc.Services.getCurrentService(Services.java:94)
> at org.jbpm.graph.exe.ProcessInstance.end(ProcessInstance.java:328)
> at org.jbpm.graph.exe.Token.notifyParentOfTokenEnd(Token.java:329)
> at org.jbpm.graph.exe.Token.end(Token.java:301)
> at org.jbpm.graph.exe.Token.end(Token.java:251)
> at org.jbpm.graph.node.EndState.execute(EndState.java:59)
> The 3.3 snapshot is looking for 'jbpm.job.executor' which is defined in the default.jbpm.cfg.xml, but which the application does not have in its jbpm.cfg.xml. It works with 3.2.2. The JobExecutor is set up manually in a Spring configuration.
--
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
[JBoss JIRA] Updated: (JBPM-1452) JbpmConfiguration assumes the object factory has a jbpm.job.executor entry
by Thomas Diesler (JIRA)
[ https://jira.jboss.org/jira/browse/JBPM-1452?page=com.atlassian.jira.plug... ]
Thomas Diesler updated JBPM-1452:
---------------------------------
Fix Version/s: jBPM 3.3.0
(was: jBPM 3.3.0 CR1)
> JbpmConfiguration assumes the object factory has a jbpm.job.executor entry
> --------------------------------------------------------------------------
>
> Key: JBPM-1452
> URL: https://jira.jboss.org/jira/browse/JBPM-1452
> Project: JBoss jBPM
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: jBPM 3.3.0 CR1
> Environment: 3.3 snapshot
> Spring
> Reporter: Alejandro Guizar
> Assignee: Alejandro Guizar
> Fix For: jBPM 3.3.0
>
>
> The following exception is thrown while completing a task that ends a process. The application runs with the 3.3 snapshot JAR.
> org.jbpm.configuration.ConfigurationException: name 'jbpm.job.executor' is not defined in the configuration. configured names: [resource.hibernate.queries.hbm.xml, jbpm.msg.wait.timout, jbpm.task.instance.factory, resource.default.modules, resource.varmapping, resource.business.calendar, resource.action.types, resource.parsers, default.jbpm.context, resource.node.types, resource.converter, jbpm.variable.resolver, jbpm.byte.block.size]
> at org.jbpm.configuration.ObjectFactoryImpl.createObject(ObjectFactoryImpl.java:76)
> at org.jbpm.JbpmConfiguration.getJobExecutor(JbpmConfiguration.java:603)
> at org.jbpm.scheduler.db.DbSchedulerService.<init>(DbSchedulerService.java:51)
> at org.jbpm.scheduler.db.DbSchedulerServiceFactory.openService(DbSchedulerServiceFactory.java:32)
> at org.jbpm.svc.Services.getService(Services.java:156)
> at org.jbpm.svc.Services.getCurrentService(Services.java:94)
> at org.jbpm.graph.exe.ProcessInstance.end(ProcessInstance.java:328)
> at org.jbpm.graph.exe.Token.notifyParentOfTokenEnd(Token.java:329)
> at org.jbpm.graph.exe.Token.end(Token.java:301)
> at org.jbpm.graph.exe.Token.end(Token.java:251)
> at org.jbpm.graph.node.EndState.execute(EndState.java:59)
> The 3.3 snapshot is looking for 'jbpm.job.executor' which is defined in the default.jbpm.cfg.xml, but which the application does not have in its jbpm.cfg.xml. It works with 3.2.2. The JobExecutor is set up manually in a Spring configuration.
--
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
[JBoss JIRA] Deleted: (JBPM-1731) JobLoadSubProcessTest throws couldn't signal token : token has ended
by Thomas Diesler (JIRA)
[ https://jira.jboss.org/jira/browse/JBPM-1731?page=com.atlassian.jira.plug... ]
Thomas Diesler deleted JBPM-1731:
---------------------------------
> JobLoadSubProcessTest throws couldn't signal token : token has ended
> --------------------------------------------------------------------
>
> Key: JBPM-1731
> URL: https://jira.jboss.org/jira/browse/JBPM-1731
> Project: JBoss jBPM
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Thomas Diesler
>
> Running org.jbpm.job.executor.JobLoadSubProcessTest
> Exception in thread "Thread-1" java.lang.IllegalStateException: couldn't signal token : token has ended
> at org.jbpm.graph.exe.ProcessInstance.signal(ProcessInstance.java:268)
> at org.jbpm.graph.node.ProcessState.execute(ProcessState.java:178)
> at org.jbpm.graph.def.Node.enter(Node.java:314)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.invoke(CGLIBLazyInitializer.java:157)
> at org.jbpm.graph.def.Node$$EnhancerByCGLIB$$8c798f57.enter(<generated>)
> at org.jbpm.graph.def.Transition.take(Transition.java:151)
> at org.jbpm.graph.def.Node.leave(Node.java:389)
> at org.jbpm.graph.def.Node.leave(Node.java:353)
> at org.jbpm.graph.def.Node.execute(Node.java:345)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.invoke(CGLIBLazyInitializer.java:157)
> at org.jbpm.graph.def.Node$$EnhancerByCGLIB$$8c798f57.execute(<generated>)
> at org.jbpm.graph.exe.ProcessInstance.<init>(ProcessInstance.java:174)
> at org.jbpm.graph.exe.ProcessInstance.<init>(ProcessInstance.java:92)
> at org.jbpm.JbpmContext.newProcessInstance(JbpmContext.java:409)
> at org.jbpm.job.executor.JobLoadSubProcessTest$StartNewExecutionThread.run(JobLoadSubProcessTest.java:127)
> Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 26.813 sec <<< FAILURE!
--
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
[JBoss JIRA] Created: (JBPM-1731) JobLoadSubProcessTest throws couldn't signal token : token has ended
by Thomas Diesler (JIRA)
JobLoadSubProcessTest throws couldn't signal token : token has ended
--------------------------------------------------------------------
Key: JBPM-1731
URL: https://jira.jboss.org/jira/browse/JBPM-1731
Project: JBoss jBPM
Issue Type: Task
Security Level: Public (Everyone can see)
Components: jPDL 3
Reporter: Thomas Diesler
Fix For: jBPM 3.3.0
Running org.jbpm.job.executor.JobLoadSubProcessTest
Exception in thread "Thread-1" java.lang.IllegalStateException: couldn't signal token : token has ended
at org.jbpm.graph.exe.ProcessInstance.signal(ProcessInstance.java:268)
at org.jbpm.graph.node.ProcessState.execute(ProcessState.java:178)
at org.jbpm.graph.def.Node.enter(Node.java:314)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.invoke(CGLIBLazyInitializer.java:157)
at org.jbpm.graph.def.Node$$EnhancerByCGLIB$$8c798f57.enter(<generated>)
at org.jbpm.graph.def.Transition.take(Transition.java:151)
at org.jbpm.graph.def.Node.leave(Node.java:389)
at org.jbpm.graph.def.Node.leave(Node.java:353)
at org.jbpm.graph.def.Node.execute(Node.java:345)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.invoke(CGLIBLazyInitializer.java:157)
at org.jbpm.graph.def.Node$$EnhancerByCGLIB$$8c798f57.execute(<generated>)
at org.jbpm.graph.exe.ProcessInstance.<init>(ProcessInstance.java:174)
at org.jbpm.graph.exe.ProcessInstance.<init>(ProcessInstance.java:92)
at org.jbpm.JbpmContext.newProcessInstance(JbpmContext.java:409)
at org.jbpm.job.executor.JobLoadSubProcessTest$StartNewExecutionThread.run(JobLoadSubProcessTest.java:127)
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 26.813 sec <<< FAILURE!
--
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
[JBoss JIRA] Updated: (JBPM-1071) Possible problem in concurrent signalling from multiple threads
by Alejandro Guizar (JIRA)
[ https://jira.jboss.org/jira/browse/JBPM-1071?page=com.atlassian.jira.plug... ]
Alejandro Guizar updated JBPM-1071:
-----------------------------------
Assignee: (was: Alejandro Guizar)
Unassigning issues on which I won't work in the near term.
> Possible problem in concurrent signalling from multiple threads
> ---------------------------------------------------------------
>
> Key: JBPM-1071
> URL: https://jira.jboss.org/jira/browse/JBPM-1071
> Project: JBoss jBPM
> Issue Type: Bug
> Components: Core Engine
> Affects Versions: jBPM 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
> 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: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years