May 2009 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-2235) View process definition diagram and current activity

by Heiko Braun (JIRA)

View process definition diagram and current activity ---------------------------------------------------- Key: JBPM-2235 URL: https://jira.jboss.org/jira/browse/JBPM-2235 Project: JBoss jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: GWT Console 1.0.0 GA -- 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

2
3
0 / 0

[JBoss JIRA] Created: (JBPM-2275) handle async message jobs after process instance deletion

by Tom Baeyens (JIRA)

handle async message jobs after process instance deletion --------------------------------------------------------- Key: JBPM-2275 URL: https://jira.jboss.org/jira/browse/JBPM-2275 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Runtime Engine Reporter: Tom Baeyens Assignee: Tom Baeyens Priority: Critical Fix For: jBPM 4.0 when a process instance ends, a delete process instance synchronization is issued. but potentially this last transaction also schedules some async continuations or async event listeners. as long as those messages are not processed the jobs should not be deleted. currently they are deleted: in HibernatePvmDbSession.deleteProcessInstance : // delete remaining jobs for this process instance List<JobImpl> jobs = findJobs(processInstanceId); for (JobImpl job: jobs) { session.delete(job); } In case of the normal process instance ending, the process instance is deleted because of the synchronization. In that case, only timers should be deleted there. And a mechanism should be put in place so that the process instance is only deleted after the last async message for that execution has been processed. In case a process instance is deleted as an admin operation, all the jobs (incl messages) should be deleted. At least investigate and clearly document in which cases this goes bananas -- 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

1
5
0 / 0

[JBoss JIRA] Created: (JBPM-2286) create test case with fork and join in one transaction

by Tom Baeyens (JIRA)

create test case with fork and join in one transaction ------------------------------------------------------ Key: JBPM-2286 URL: https://jira.jboss.org/jira/browse/JBPM-2286 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Assignee: Tom Baeyens Fix For: jBPM 4.0 -- 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

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-2289) Upload servlet path is not aligned with the GPD defaults

by Martin Putz (JIRA)

Upload servlet path is not aligned with the GPD defaults -------------------------------------------------------- Key: JBPM-2289 URL: https://jira.jboss.org/jira/browse/JBPM-2289 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jBPM 3.2.5.SP5 Reporter: Martin Putz Fix For: SOA 4.3 CP02 The default configuration in the jbpm-jpdl-3.2.5SP5 package defines the path to the GPD deployer servlet as /app/upload in /deploy/server/default/deploy/jbpm/jsf-console.war/WEB-INF/web.xml: <servlet-mapping> <servlet-name>GDP Deployer Servlet</servlet-name> <url-pattern>/app/upload/*</url-pattern> </servlet-mapping> This doesn't match with the defaults in the GPD/JBDS, and should thus be changed to <url-pattern>/upload/*</url-pattern>. -- 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

2
8
0 / 0

[JBoss JIRA] Created: (JBPM-2212) review string == comparisons for execution.state

by Tom Baeyens (JIRA)

review string == comparisons for execution.state ------------------------------------------------ Key: JBPM-2212 URL: https://jira.jboss.org/jira/browse/JBPM-2212 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Assignee: Tom Baeyens Fix For: jBPM 4.0.0.GA " - De STATE van een execution wordt aangegeven met een String, die later vergeleken wordt met de == operator ... ooit kan die misgaan (als de String pool van JVM te klein wordt). Beter dus een enum gebruiken, die zijn juist gemaakt hiervoor (en dan kan je == blijven gebruiken). " -- 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

1
1
0 / 0

[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

1
2
0 / 0

[JBoss JIRA] Created: (JBPM-2292) Move jBPM3-SOA continuous integration to QA lab

by Alejandro Guizar (JIRA)

Move jBPM3-SOA continuous integration to QA lab ----------------------------------------------- Key: JBPM-2292 URL: https://jira.jboss.org/jira/browse/JBPM-2292 Project: JBoss jBPM Issue Type: Quality Risk Components: Runtime Engine Reporter: Alejandro Guizar Assignee: Alejandro Guizar Priority: Blocker Fix For: jBPM 3.2.5 SP6 Leverage the QA lab infrastructure, in particular the databases installed in multiple hosts, to increase the throughput of the jBPM QA process. -- 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

1
4
0 / 0

[JBoss JIRA] Created: (JBPM-2055) Executions that are ended show up in query

by Heiko Braun (JIRA)

Executions that are ended show up in query ------------------------------------------ Key: JBPM-2055 URL: https://jira.jboss.org/jira/browse/JBPM-2055 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Engine Reporter: Heiko Braun Assignee: Tom Baeyens ExecutionQuery query = execService.createExecutionQuery(); query.processDefinitionId(<ID>); List<Execution> executions = query.execute(); The resulting list contains execution that are already ended. -- 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

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-2124) remove task id property

by Tom Baeyens (JIRA)

remove task id property ----------------------- Key: JBPM-2124 URL: https://jira.jboss.org/jira/browse/JBPM-2124 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Fix For: jBPM 4.0.0.CR1 property task.id (string) has been replaced by dbid (long) in the task service interfaces property still seems to be there and persisted. -- 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

2
5
0 / 0

[JBoss JIRA] Created: (JBPM-1456) testFailOnceMessages fails sometimes

by Tom Baeyens (JIRA)

testFailOnceMessages fails sometimes ------------------------------------ Key: JBPM-1456 URL: https://jira.jboss.org/jira/browse/JBPM-1456 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Tom Baeyens Priority: Critical ideas to investigate this: * increase nbrOfTestMessages, will increace the chance of getting the problem * disabling the logs might also have an effect. if that is the case, this might be a good occasion to configure the http://java.sun.com/j2se/1.4.2/docs/api/java/util/logging/MemoryHandler.html -- 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

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues May 2009