February 2010 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-2426) mail attachment example

by Alejandro Guizar (JIRA)

mail attachment example ----------------------- Key: JBPM-2426 URL: https://jira.jboss.org/jira/browse/JBPM-2426 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Runtime Engine Reporter: Alejandro Guizar Assignee: Alejandro Guizar Fix For: jBPM 4.1 Provide an example that shows how to attach files to outgoing emails. -- 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

14 years, 8 months

2
7
0 / 0

[JBoss JIRA] Created: (JBPM-1708) CommandServiceBean cannot access UserTransaction

by Thomas Diesler (JIRA)

CommandServiceBean cannot access UserTransaction ------------------------------------------------ Key: JBPM-1708 URL: https://jira.jboss.org/jira/browse/JBPM-1708 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: jBPM 3.3.0 Caused by: org.jbpm.JbpmException: couldn't start JTA transaction at org.jbpm.persistence.jta.JtaDbPersistenceService.beginJtaTransaction(JtaDbPersistenceService.java:74) at org.jbpm.persistence.jta.JtaDbPersistenceService.<init>(JtaDbPersistenceService.java:47) at org.jbpm.persistence.jta.JtaDbPersistenceServiceFactory.openService(JtaDbPersistenceServiceFactory.java:63) at org.jbpm.svc.Services.getService(Services.java:156) at org.jbpm.svc.Services.getPersistenceService(Services.java:195) at org.jbpm.JbpmContext.getPersistenceService(JbpmContext.java:622) at org.jbpm.JbpmContext.getGraphSession(JbpmContext.java:566) at org.jbpm.JbpmContext.deployProcessDefinition(JbpmContext.java:173) at org.jbpm.command.DeployProcessCommand.execute(DeployProcessCommand.java:68) at org.jbpm.ejb.impl.CommandServiceBean.execute(CommandServiceBean.java:146) 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.jboss.invocation.Invocation.performCall(Invocation.java:359) at org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(StatelessSessionContainer.java:237) at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:158) at org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invoke(StatelessSessionInstanceInterceptor.java:169) 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) ... 45 more Caused by: org.jbpm.JbpmException: could not retrieve user transaction with name java:comp/UserTransaction at org.jbpm.persistence.jta.JtaDbPersistenceServiceFactory.getUserTransaction(JtaDbPersistenceServiceFactory.java:84) at org.jbpm.persistence.jta.JtaDbPersistenceService.beginJtaTransaction(JtaDbPersistenceService.java:71) ... 68 more -- 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

14 years, 8 months

2
25
0 / 0

[JBoss JIRA] Created: (JBPM-2393) expand task history to full audit logs

by Tom Baeyens (JIRA)

expand task history to full audit logs -------------------------------------- Key: JBPM-2393 URL: https://jira.jboss.org/jira/browse/JBPM-2393 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Runtime Engine Reporter: Tom Baeyens Assignee: Tom Baeyens Fix For: jBPM 4.1 -- 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

14 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-2661) BPMN2: Exclusive gateway

by Joram Barrez (JIRA)

BPMN2: Exclusive gateway ------------------------ Key: JBPM-2661 URL: https://jira.jboss.org/jira/browse/JBPM-2661 Project: jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Joram Barrez Assignee: Joram Barrez Fix For: jBPM 4.3 * Verify what's currently in the codebase. * Enhance where needed * Document the usage of the construct. -- 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

14 years, 9 months

3
4
0 / 0

[JBoss JIRA] Created: (JBPM-2413) productize group activity

by Tom Baeyens (JIRA)

productize group activity ------------------------- Key: JBPM-2413 URL: https://jira.jboss.org/jira/browse/JBPM-2413 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Assignee: Tom Baeyens Fix For: jBPM 4.1 -- 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

14 years, 9 months

5
12
0 / 0

[JBoss JIRA] Created: (JBPM-2787) Process instances stuck in a fork

by Alejandro Guizar (JIRA)

Process instances stuck in a fork --------------------------------- Key: JBPM-2787 URL: https://jira.jboss.org/jira/browse/JBPM-2787 Project: jBPM Issue Type: Bug Components: Runtime Engine Affects Versions: jBPM 3.2.8 Environment: SOA 4.3 CP02 with jBPM 3.2.8_SOA 2 node cluster Oracle DB with xa datasources JMS-based messaging/scheduler services from the SOA-P Reporter: Alejandro Guizar Assignee: Alejandro Guizar Priority: Critical Fix For: jBPM 3.2.9 There are problems with a jBPM process which contains a fork/join when running in a cluster. If run with just one node, the processes end properly, but with two nodes the child tokens don't reactivate the parent token Any ideas? Such as: * specifying <transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation> on the JbpmDS * trying lock="UPGRADE_NOWAIT" on the join -- 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

14 years, 9 months

1
4
0 / 0

[JBoss JIRA] Created: (JBPM-2767) JobExecutor doesn't roll back the transaction even if the action handler throws Exception

by Toshiya Kobayashi (JIRA)

JobExecutor doesn't roll back the transaction even if the action handler throws Exception ----------------------------------------------------------------------------------------- Key: JBPM-2767 URL: https://jira.jboss.org/jira/browse/JBPM-2767 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 3.2.8 Reporter: Toshiya Kobayashi In case that Job execution of an async node is processed by JobExecutor, the transaction is not rolled back even if the action handler throws Exception/RuntimeException. The transaction is commtted and no retry happens. It looks inconsistent with docs: http://www.redhat.com/docs/en-US/JBoss_SOA_Platform/4.3.CP02/html-single/... ============ If execution of a command message fails, the transaction will be rolled back. After that, a new transaction will be started that adds the error message to the message in the database. The command executor filters out all messages that contain an exception. ============ I've attatched a reproducer. - unzip jobexecution.zip - modify build.properties - ant deploypar - ant deploy - ant ejbclient (or access jbpm-console to start process instance) - access jbpm-console to check process instance's id which is created by the action handler (which should be rolled back) -- 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

14 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBPM-2784) Schema doesn't accept condition attribute in transition

by Toshiya Kobayashi (JIRA)

Schema doesn't accept condition attribute in transition ------------------------------------------------------- Key: JBPM-2784 URL: https://jira.jboss.org/jira/browse/JBPM-2784 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 3.2.8 Reporter: Toshiya Kobayashi In case you write process definition like: <decision name="node1"> <transition to="node2" condition="#{AAA == null}"></transition> <transition to="node3"></transition> </decision> Schema will reject. org.jbpm.jpdl.JpdlException: [[ERROR] cvc-complex-type.3.2.2: Attribute 'condition' is not allowed to appear in element 'transition'. line 10] at org.jbpm.jpdl.xml.JpdlXmlReader.readProcessDefinition(JpdlXmlReader.java:173) at org.jbpm.jpdl.par.JpdlArchiveParser.readFromArchive(JpdlArchiveParser.java:51) at org.jbpm.jpdl.par.ProcessArchive.parseProcessDefinition(ProcessArchive.java:82) at org.jbpm.graph.def.ProcessDefinition.parseParZipInputStream(ProcessDefinition.java:211) at org.jbpm.web.ProcessUploadServlet.parseProcessArchive(ProcessUploadServlet.java:147) at org.jbpm.web.ProcessUploadServlet.doPost(ProcessUploadServlet.java:81) at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) According to docs, condition can be "attribute or element text" http://www.redhat.com/docs/en-US/JBoss_SOA_Platform/4.3.CP02/html-single/... -- 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

14 years, 9 months

3
6
0 / 0

[JBoss JIRA] Created: (JBPM-2637) TaskMgmtSession.findTaskInstancesByIds() fails if taskInstanceIds is an empty list

by Toshiya Kobayashi (JIRA)

TaskMgmtSession.findTaskInstancesByIds() fails if taskInstanceIds is an empty list ---------------------------------------------------------------------------------- Key: JBPM-2637 URL: https://jira.jboss.org/jira/browse/JBPM-2637 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 3.2.8, jBPM 3.2.7 Reporter: Toshiya Kobayashi org.jbpm.command.GetTaskListCommand.execute() throws JbpmPersistenceException if there is no pooled task instances for a given actor even if the actor has personally assigned task instaces. ===== org.jbpm.persistence.JbpmPersistenceException: couldn't get task instances by ids '[]' at org.jbpm.db.TaskMgmtSession.findTaskInstancesByIds(TaskMgmtSession.java:204) at org.jbpm.db.TaskMgmtSession.findPooledTaskInstances(TaskMgmtSession.java:123) at org.jbpm.JbpmContext.getGroupTaskList(JbpmContext.java:194) at org.jbpm.command.GetTaskListCommand.execute(GetTaskListCommand.java:54) at sample.task.ws.TaskSampleWS.test(TaskSampleWS.java:52) ===== In case of CP01, GetTaskListCommand returns the personal task list without Exception. This behavior is caused by the change introduced by r4076 in org.jbpm.db.TaskMgmtSession.findTaskInstancesByIds(). r4705 === public List<TaskInstance> findTaskInstancesByIds(List<Long> taskInstanceIds) { List<TaskInstance> result; if (taskInstanceIds.isEmpty()) { result = Collections.emptyList(); } else { try { Query query = session.getNamedQuery("TaskMgmtSession.findTaskInstancesByIds"); query.setParameterList("taskInstanceIds", taskInstanceIds); result = CollectionUtil.checkList(query.list(), TaskInstance.class); } catch (Exception e) { handle(e); throw new JbpmException("couldn't get task instances by ids '" + taskInstanceIds + "'", e); } } return result; } === r4706 === public List findTaskInstancesByIds(List taskInstanceIds) { try { return session.getNamedQuery("TaskMgmtSession.findTaskInstancesByIds") .setParameterList("taskInstanceIds", taskInstanceIds) .list(); } catch (HibernateException e) { handle(e); throw new JbpmPersistenceException("couldn't get task instances by ids '" + taskInstanceIds + "'", e); } } === The change was related to JBPM-2205 and removed the empty check because the method Collections.emptyList() is not supported in jdk1.4. But I think an equivalent empty check should be restored. -- 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

14 years, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (JBPM-2581) Problems with nested Forks

by Sebastian Castellanos (JIRA)

Problems with nested Forks --------------------------- Key: JBPM-2581 URL: https://jira.jboss.org/jira/browse/JBPM-2581 Project: jBPM Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: jBPM 4.0 Environment: Windows xp, Eclipse galileo and jbpm integred with spring and hibernate. Reporter: Sebastian Castellanos Priority: Critical First off, I apologize for not having made the unit tests, but do not have time at the moment and I think it is a conceptual problem and a unit test would not provide much. I am integrating jBPM version 4.1 and it proves there too. The situation is this: When launched a nested Fork1 another in the second Fork repeats one of its tasks. In the xml it becomes clear what the situation. Maybe it is a conceptual issue, and I who is mishandled. I would be grateful if I can help, as I searched in different places this situation and found no alternative but to post it here. Greetings. Sebastian. -- 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

14 years, 10 months

6
19
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues February 2010