March 2009 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-1162) Problem with exception handling within the Decision nodes

by Jon Folland (JIRA)

Problem with exception handling within the Decision nodes --------------------------------------------------------- Key: JBPM-1162 URL: http://jira.jboss.com/jira/browse/JBPM-1162 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM jPDL 3.2.2 Environment: Vaio laptop running Windows Vista, Java 1.5, JBPM 3.2.2 Reporter: Jon Folland Assigned To: Tom Baeyens I believe there may be a bug in the Decision class where exception handling is concerned which causes this failure: If the line: String transitionName = decisionHandler.decide(executionContext); ... ...in the method public void execute(ExecutionContext executionContext) throws an exception, which is caught here in the same method: raiseException(exception, executionContext); We miss the block: if (transition==null) { transition = getDefaultLeavingTransition(); log.debug("decision didn't select transition, taking default "+transition); } So when executionContext.leaveNode(transition); is called at the bottom, there wil be no transition set. I believe we need to check for a tranistion==null condition regardless of whether an excpetion has been handled. Otherwise you will never be able to handle an exception in a Decision without another unhandled exception being thrown (which kind of defeits the point :-) -- 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

14 years, 7 months

3
6
0 / 0

[JBoss JIRA] Created: (JBPM-1158) Missing query JobSession.findJobsWithOverdueLockTime in hibernate.queries.hbm.xml

by Julien Kronegg (JIRA)

Missing query JobSession.findJobsWithOverdueLockTime in hibernate.queries.hbm.xml --------------------------------------------------------------------------------- Key: JBPM-1158 URL: http://jira.jboss.com/jira/browse/JBPM-1158 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM jPDL 3.2.2 Environment: zip file downloaded from http://www.jboss.org/downloading/?projectId=jbossjbpm&url=http://download... Reporter: Julien Kronegg Assigned To: Tom Baeyens The org.jbpm.db.JobSession class has a findJobsWithOverdueLockTime(Date) method which use a query named "JobSession.findJobsWithOverdueLockTime". In similar methods of the same class, the queries are located in org.jbpm.db.hibernate.queries.hbm.xml, which is not the case for this query. The "JobSession.findJobsWithOverdueLockTime" string could not be found elsewhere in the project. Conclusion: the "JobSession.findJobsWithOverdueLockTime" query seems to be missing in hibernate.queries.hbm.xml (or the method should be removed from the class). -- 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

14 years, 7 months

3
3
0 / 0

[JBoss JIRA] Created: (JBPM-1139) The ClassUtil class is not thread-safe

by Wojciech Gdela (JIRA)

The ClassUtil class is not thread-safe -------------------------------------- Key: JBPM-1139 URL: http://jira.jboss.com/jira/browse/JBPM-1139 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM jPDL 3.2.3 Reporter: Wojciech Gdela Assigned To: Tom Baeyens Attachments: ClassUtil-concurrency-issue.zip The ClassUtil class is not thread-safe. The exception will occur when two thread simultanously try do deserialize variables from two different process definitions. Look at the code: {code} public ContextObjectInputStream(final InputStream in, ProcessInstance processInstance) throws IOException { super(in); this.setProcessInstance(processInstance); ClassUtil.setProcessInstance(processInstance); } ... protected Class resolveClass(final ObjectStreamClass desc) throws IOException, ClassNotFoundException { return ClassUtil.forName(desc.getName(), ContextObjectInputStream.class); } ... ContextObjectInputStream cois = new ContextObjectInputStream(bais, definition.createProcessInstance()); // when here another thread tries to execute the same code with another process instance there will be a problem return cois.readObject(); {/code} Further description of issue is in attached test case. -- 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

14 years, 7 months

3
5
0 / 0

[JBoss JIRA] Created: (JBPM-1136) CancelProcessInstanceCommand doesn't delete jobs

by Jérôme Tellier (JIRA)

CancelProcessInstanceCommand doesn't delete jobs ------------------------------------------------ Key: JBPM-1136 URL: http://jira.jboss.com/jira/browse/JBPM-1136 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM jPDL 3.2.2 Reporter: Jérôme Tellier Assigned To: Tom Baeyens Priority: Minor the CancelProcessInstanceCommand doesn't delete jobs of the main process and subprocesses , I think a cancel process should not have job any more. -- 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

14 years, 8 months

3
3
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-2045) Database maintenance scripts

by Len DiMaggio (JIRA)

Database maintenance scripts ---------------------------- Key: JBPM-2045 URL: https://jira.jboss.org/jira/browse/JBPM-2045 Project: JBoss jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Productization Affects Versions: jBPM 3.2.5 GA Reporter: Len DiMaggio Project JIRA for SOA-P platform JIRA: https://jira.jboss.org/jira/browse/SOA-310 -- 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

3
3
0 / 0

[JBoss JIRA] Created: (JBPM-2047) PersistenceDbServiceTest and PersistenceServiceDbTest are dependent

by Jiri Pechanec (JIRA)

PersistenceDbServiceTest and PersistenceServiceDbTest are dependent ------------------------------------------------------------------- Key: JBPM-2047 URL: https://jira.jboss.org/jira/browse/JBPM-2047 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Engine Affects Versions: jBPM-3.2.5.SP1 Reporter: Jiri Pechanec Assignee: Thomas Diesler The tests can fail based on the execution order of these tests. If PersistenceDbServiceTest is executed first then it sets session factory to MockSessionFactory. Unfortunately it seems that the setting is SAME for ALL future newly created JbpmContexts. PersistenceServiceDbTest then tests that the factory is null but it is not assertNull(persistenceServiceFactory.sessionFactory). The same test also tests few more features that ends in calls of unsupported operations on the MockSessionFactory. I am not sure if this is a problem of test - then the sessionFactory should be cleard after test or if it is wrong that the setting is shared for all JBpmContexts. -- 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, 11 months

4
11
0 / 0

[JBoss JIRA] Created: (JBPM-1707) pageflow parsing is slow

by Alejandro Guizar (JIRA)

pageflow parsing is slow ------------------------ Key: JBPM-1707 URL: https://jira.jboss.org/jira/browse/JBPM-1707 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Engine Affects Versions: jBPM 3.2.3 Environment: Red Hat Enterprise Linux AS release 4 (Nahant Update 7) enterprise-installer-4.3.0.GA-1.ep1.8.jar jdk-1.5.0_16-fcs Reporter: Alejandro Guizar Assignee: Alejandro Guizar Fix For: jBPM 3.3.0 CR1 On a RHEL machine, while deploying a seam based ear, which contains 13 pageflow definitions, the parsing of these 13 pageflow files takes more than 34 minutes (!). The culprit seems to be the usage of the original systemId (http://jboss.com/products/seam/pageflow-2.0.xsd) in the org.jbpm.jdpl.xml.JpdlParser$JpdlEntityResolver class, as this apparently results in slow internet lookups: log.debug("original systemId as input source"); inputSource = new InputSource(systemId); Using a null InputSource: inputSource = new InputSource((InputStream)null); brings the parsing time down to less than 1 second. Of course it would be better to actually pass in a reference to the local pageflow-2.0.xsd file, which is inside the jboss-seam.jar. -- 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, 11 months

4
12
0 / 0

[JBoss JIRA] Created: (JBPM-1771) Fix JobExecutorDbTest on postgresql

by Thomas Diesler (JIRA)

Fix JobExecutorDbTest on postgresql ----------------------------------- Key: JBPM-1771 URL: https://jira.jboss.org/jira/browse/JBPM-1771 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: jBPM 3.3.1 GA expected:<[10X, 10Y, 10Z, 10a, 10b, 10c, 10d, 10e, 11X, 11Y, 11Z, 11a, 11b, 11c, 11d, 11e, 12X, 12Y, 12Z, 12a, 12b, 12c, 12d, 12e, 13X, 13Y, 13Z, 13a, 13b, 13c, 13d, 13e, 14X, 14Y, 14Z, 14a, 14b, 14c, 14d, 14e, 15X, 15Y, 15Z, 15a, 15b, 15c, 15d, 15e, 16X, 16Y, 16Z, 16a, 16b, 16c, 16d, 16e, 17X, 17Y, 17Z, 17a, 17b, 17c, 17d, 17e, 18X, 18Y, 18Z, 18a, 18b, 18c, 18d, 18e, 19X, 19Y, 19Z, 19a, 19b, 19c, 19d, 19e, 1X, 1Y, 1Z, 1a, 1b, 1c, 1d, 1e, 20X, 20Y, 20Z, 20a, 20b, 20c, 20d, 20e, 2X, 2Y, 2Z, 2a, 2b, 2c, 2d, 2e, 3X, 3Y, 3Z, 3a, 3b, 3c, 3d, 3e, 4X, 4Y, 4Z, 4a, 4b, 4c, 4d, 4e, 5X, 5Y, 5Z, 5a, 5b, 5c, 5d, 5e, 6X, 6Y, 6Z, 6a, 6b, 6c, 6d, 6e, 7X, 7Y, 7Z, 7a, 7b, 7c, 7d, 7e, 8X, 8Y, 8Z, 8a, 8b, 8c, 8d, 8e, 9X, 9Y, 9Z, 9a, 9b, 9c, 9d, 9e]> but was:<[100X, 100Y, 100Z, 100a, 100b, 100c, 100d, 100e, 108X, 108Y, 108Z, 108a, 108b, 108c, 108d, 108e, 116X, 116Y, 116Z, 116a, 116b, 116c, 116d, 116e, 124X, 124Y, 124Z, 124a, 124b, 124c, 124d, 124e, 132X, 132Y, 132Z, 132a, 132b, 132c, 132d, 132e, 140X, 140Y, 140Z, 140a, 140b, 140c, 140d, 140e, 148X, 148Y, 148Z, 148a, 148b, 148c, 148d, 148e, 156X, 156Y, 156Z, 156a, 156b, 156c, 156d, 156e, 164X, 164Y, 164Z, 164a, 164b, 164c, 164d, 164e, 172X, 172Y, 172Z, 172a, 172b, 172c, 172d, 172e, 180X, 180Y, 180Z, 180a, 180b, 180c, 180d, 180e, 188X, 188Y, 188Z, 188a, 188b, 188c, 188d, 188e, 36X, 36Y, 36Z, 36a, 36b, 36c, 36d, 36e, 44X, 44Y, 44Z, 44a, 44b, 44c, 44d, 44e, 52X, 52Y, 52Z, 52a, 52b, 52c, 52d, 52e, 60X, 60Y, 60Z, 60a, 60b, 60c, 60d, 60e, 68X, 68Y, 68Z, 68a, 68b, 68c, 68d, 68e, 76X, 76Y, 76Z, 76a, 76b, 76c, 76d, 76e, 84X, 84Y, 84Z, 84a, 84b, 84c, 84d, 84e, 92X, 92Y, 92Z, 92a, 92b, 92c, 92d, 92e]> -- 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, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (JBPM-1958) Security issue allows arbitrary java code to be deployed and executed

by Thomas Diesler (JIRA)

Security issue allows arbitrary java code to be deployed and executed --------------------------------------------------------------------- Key: JBPM-1958 URL: https://jira.jboss.org/jira/browse/JBPM-1958 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Console Reporter: Thomas Diesler Assignee: Koen Aers Priority: Critical Fix For: jBPM 3.3.2 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

14 years, 11 months

3
14
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues March 2009