[JBoss JIRA] Created: (JBPM-2103) Deleting timer in JSF console prints stack trace
by Alejandro Guizar (JIRA)
Deleting timer in JSF console prints stack trace
------------------------------------------------
Key: JBPM-2103
URL: https://jira.jboss.org/jira/browse/JBPM-2103
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Console
Affects Versions: jBPM 3.2.6.SP1
Reporter: Alejandro Guizar
Assignee: Alejandro Guizar
Priority: Minor
Fix For: jBPM 3.2.7 GA
The "Delete" action in the JSF console goes straight to JobSession.deleteJob instead of going through SchedulerService.deleteTimer. The EntitySchedulerService is not given the chance to cancel the EJB timer it created, resulting in the exception below the next time the EJB timer fires. The issue is noncritical because the EJB container rolls back the transaction, retries the ejbTimeout call once, and gives up.
NoSuchEntityException in method: public abstract void javax.ejb.TimedObject.ejbTimeout(javax.ejb.Timer):
javax.ejb.NoSuchEntityException: Entity not found: primaryKey=1
at org.jboss.ejb.plugins.cmp.jdbc.JDBCLoadEntityCommand.execute(JDBCLoadEntityCommand.java:238)
at org.jboss.ejb.plugins.cmp.jdbc.JDBCLoadEntityCommand.execute(JDBCLoadEntityCommand.java:88)
at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.loadEntity(JDBCStoreManager.java:646)
at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.loadEntity(JDBCStoreManager.java:628)
at org.jboss.ejb.plugins.CMPPersistenceManager.loadEntity(CMPPersistenceManager.java:406)
at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.loadEntity(CachedConnectionInterceptor.java:252)
at org.jboss.ejb.plugins.EntitySynchronizationInterceptor.invoke(EntitySynchronizationInterceptor.java:243)
at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:158)
at org.jboss.ejb.plugins.EntityReentranceInterceptor.invoke(EntityReentranceInterceptor.java:126)
at org.jboss.ejb.plugins.EntityInstanceInterceptor.invoke(EntityInstanceInterceptor.java:278)
at org.jboss.ejb.plugins.EntityLockInterceptor.invoke(EntityLockInterceptor.java:104)
at org.jboss.ejb.plugins.EntityCreationInterceptor.invoke(EntityCreationInterceptor.java:76)
at org.jboss.ejb.plugins.CallValidationInterceptor.invoke(CallValidationInterceptor.java:63)
at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:121)
at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:350)
at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:181)
at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:168)
at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:205)
at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:138)
at org.jboss.ejb.EntityContainer.internalInvoke(EntityContainer.java:527)
at org.jboss.ejb.Container.invoke(Container.java:960)
at org.jboss.ejb.txtimer.TimedObjectInvokerImpl.callTimeout(TimedObjectInvokerImpl.java:99)
at org.jboss.ejb.txtimer.TimerImpl$TimerTaskImpl.run(TimerImpl.java:561)
at java.util.TimerThread.mainLoop(Timer.java:534)
at java.util.TimerThread.run(Timer.java:484)
A similar problem may occur with ExecuteNodeJob/ExecuteActionJob and the JmsMessageService. If it does occur, one possible solution is to check whether the job still exists in JobListenerBean.
--
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
15 years, 6 months
[JBoss JIRA] Created: (JBPM-2315) jBPM Spring Unable to deploy process definition
by sri r (JIRA)
jBPM Spring Unable to deploy process definition
-----------------------------------------------
Key: JBPM-2315
URL: https://jira.jboss.org/jira/browse/JBPM-2315
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: jBPM 4.0.CR1
Environment: jbpm 4.0 CR1, HSQL, Spring 2.5 Hibernate 3.3 GA
Reporter: sri r
I have defined spring config with AOP have a txManager advice with propagation=required and also defined my session factory, datasource, etc in config files.
jbpm.cfg.xml
<?xml version="1.0" encoding="UTF-8"?>
<jbpm-configuration>
<import resource="jbpmrc1_hsql/jbpm.default.cfg.xml" />
<import resource="jbpmrc1_hsql/jbpm.tx.hibernate.cfg.xml" />
<import resource="jbpmrc1_hsql/jbpm.jpdl.cfg.xml" />
<import resource="jbpmrc1_hsql/jbpm.identity.cfg.xml" />
<!-- Job executor is excluded for running the example test cases. -->
<!-- To enable timers and messages in production use, this should be included. -->
<!--
<import resource="jbpm.jobexecutor.cfg.xml" />
-->
<!--<import resource="jbpm.mail.templates.examples.xml" />-->
</jbpm-configuration>
When i try to deploy a sample process def, i encounter the below error.
Error:
Caused by: org.jbpm.api.JbpmException: No platformTransaction manager defined.
at org.jbpm.pvm.internal.tx.SpringTransactionInterceptor.execute(SpringTransactionInterceptor.java:60)
at org.jbpm.pvm.internal.svc.EnvironmentInterceptor.execute(EnvironmentInterceptor.java:54)
at org.jbpm.pvm.internal.svc.RetryInterceptor.execute(RetryInterceptor.java:55)
at org.jbpm.pvm.internal.query.AbstractQuery.untypedList(AbstractQuery.java:70)
at org.jbpm.pvm.internal.query.AbstractQuery.untypedUniqueResult(AbstractQuery.java:76)
at org.jbpm.pvm.internal.query.ProcessDefinitionQueryImpl.uniqueResult(ProcessDefinitionQueryImpl.java:151)
at
--
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
15 years, 6 months
[JBoss JIRA] Updated: (JBPM-2135) Next TaskInstance is not created
by Jasphior S (JIRA)
[ https://jira.jboss.org/jira/browse/JBPM-2135?page=com.atlassian.jira.plug... ]
Jasphior S updated JBPM-2135:
-----------------------------
Security: Public (was: JBoss Internal)
> Next TaskInstance is not created
> --------------------------------
>
> Key: JBPM-2135
> URL: https://jira.jboss.org/jira/browse/JBPM-2135
> Project: JBoss jBPM
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Runtime Engine
> Affects Versions: jBPM 3.3.0 GA
> Environment: jBOSS 4.2.2, ORACLE 10, JBoss jBPM3 - Core 3.3.0.GA, Struts 2, EJB3
> Reporter: Jasphior S
> Priority: Critical
>
> I have a process definition with linear task nodes of about 11 each containing a single task, to finish the task & start the next task(if the flow is not @ the end), as described in the jBPM docs, I usually get the taskinstance by the id and invoke end() to finish that task & the next task's instance gets auto created... however, at times the next task is not created for unknown reasons(no exception thrown!), even when the taskinstance over which the end() is invoked is tagged by jBPM as ended...
> This happens unpredictably!!!
> The only work around i have as of now is to explicitly make the so pitifully ended task open by setting the taskinstance's end_ value to null and again call the end()...
> As of now this is how I'm finding whether the next task is successfully created or not...
> taskInstance.end();
> getJbpmContext().save(taskInstance);
> flushJbpmSession();
> boolean next = true;
> if(taskInstance.getProcessInstance().getEnd() == null) {
> Collection<TaskInstance> list = (Collection<TaskInstance>)taskInstance.getTaskMgmtInstance().getTaskInstances();
> for(TaskInstance instance : list) {
> if(instance.isOpen() && (instance.getCreate().equals(taskInstance.getEnd()) ||
> instance.getCreate().after(taskInstance.getEnd()))){
> next = false;
> break;
> }
> }
> } else {
> next = false;
> }
> if(next) {
> throw new RuntimeException("Task Creation has been skipped! -"+ taskInstance.getId());
> }
> ------------------
> As I'm using the transaction manager, I'm not explicitly closing the jbpmcontext... is the problem due to this?
> also please refer the below link for config info and the other issue...
> https://jira.jboss.org/jira/browse/JBPM-2128
--
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
15 years, 6 months
[JBoss JIRA] Created: (JBPM-2287) Can't fork to Task
by Oliver Lauer (JIRA)
Can't fork to Task
------------------
Key: JBPM-2287
URL: https://jira.jboss.org/jira/browse/JBPM-2287
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: jBPM 4.0.0.Beta2
Environment: JBPM 4.0 Beta2 with JBoss 5.0 Windows XP
Reporter: Oliver Lauer
Hi,
I can't fork to a or several tasks. I get the following exception:
19:33:30,514 INF | [DefaultCommandService] exception while executing command org.jbpm.pvm.internal.cmd.StartProcessInstanceInLatestCmd@1075056
org.jbpm.api.JbpmException: unsuppported extension org.jbpm.jpdl.internal.model.JpdlExecution
at org.jbpm.pvm.internal.model.ExecutionImpl.getExtension(ExecutionImpl.java:1108)
at org.jbpm.jpdl.internal.activity.TaskActivity.execute(TaskActivity.java:48)
When I debug the source code I see the last method called is the following which always throw an exception:
public <T> T getExtension(Class<T> extensionClass) {
if (extensionClass == null) {
throw new JbpmException(
"extensionClass is null. and this execution doesn't support extensions");
}
throw new JbpmException("unsuppported extension "
+ extensionClass.getName());
}
--
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
15 years, 6 months
[JBoss JIRA] Created: (JBPM-2079) optimistic locking test
by Tom Baeyens (JIRA)
optimistic locking test
-----------------------
Key: JBPM-2079
URL: https://jira.jboss.org/jira/browse/JBPM-2079
Project: JBoss jBPM
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Tom Baeyens
Assignee: Alejandro Guizar
Fix For: jBPM 4.0.0.Beta1
create a minimal test that produces an optimistic locking failure.
I believe the simplest way to test this is something like this:
Start a process instance with 2 wait states and put it in the first wait state.
EnvironmentFactory environmentFactory = get it from some configuration file
Environment environment1 = environmentFactory.openEnvironment();
Session session1 = environment1.get(Session.class);
ExecutionImpl processInstance1 = session1.load(ExecutionImpl.class, processInstanceDbid);
Environment environment2 = environmentFactory.openEnvironment();
Session session2 = environment2.get(Session.class);
ExecutionImpl processInstance2 = session2.load(ExecutionImpl.class, processInstanceDbid);
processInstance1.signal();
processInstance2.signal();
environment2.close();
environment1.close();
--
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
15 years, 6 months