July 2008 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-1292) Integrate simulation tests in automated testrun

by Thomas Diesler (JIRA)

Integrate simulation tests in automated testrun ----------------------------------------------- Key: JBPM-1292 URL: http://jira.jboss.com/jira/browse/JBPM-1292 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: jBPM jPDL 3.2.4 -- 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

15 years, 5 months

4
24
0 / 0

[JBoss JIRA] Created: (JBPM-1357) Add QA for db2

by Thomas Diesler (JIRA)

Add QA for db2 -------------- Key: JBPM-1357 URL: http://jira.jboss.com/jira/browse/JBPM-1357 Project: JBoss jBPM Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Productization Reporter: Thomas Diesler -- 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

15 years, 6 months

2
10
0 / 0

[JBoss JIRA] Created: (JBPM-1352) Support Seam use cases

by Thomas Diesler (JIRA)

Support Seam use cases ---------------------- Key: JBPM-1352 URL: http://jira.jboss.com/jira/browse/JBPM-1352 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: API Reporter: Thomas Diesler Fix For: API 1.0.0.Beta Seam consumes the jbpm API, and it would be great if you could include the methods we use as part of the stable API you are developing. http://fisheye.jboss.org/browse/Seam/trunk/src/main/org/jboss/seam/bpm and http://fisheye.jboss.org/browse/Seam/trunk/src/main/org/jboss/seam/pageflow is our integration code - ping me if you want to discuss this further offline. -- 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

15 years, 6 months

2
8
0 / 0

[JBoss JIRA] Created: (JBPM-1285) add fixed date timer support

by Tom Baeyens (JIRA)

add fixed date timer support ---------------------------- Key: JBPM-1285 URL: http://jira.jboss.com/jira/browse/JBPM-1285 Project: JBoss jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Components: PVM Reporter: Tom Baeyens add support in the TimerDefinition for fixed dueDates this should be done by adding a dueDate (type java.util.Date) property to the TimerDefinition and adding the necessary logic in the timer creation. -- 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

15 years, 6 months

4
10
0 / 0

[JBoss JIRA] Created: (JBPM-1189) Create a story for the xsd

by Koen Aers (JIRA)

Create a story for the xsd --------------------------- Key: JBPM-1189 URL: http://jira.jboss.com/jira/browse/JBPM-1189 Project: JBoss jBPM Issue Type: Task Reporter: Koen Aers Assigned To: Tom Baeyens Currently the jpdl xsd appears in multiple locations: - the runtime - the designer - online These should be synchronized at regular times. There should be a strategy to make sure this happens. -- 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

15 years, 6 months

5
7
0 / 0

[JBoss JIRA] Created: (JBPM-1288) evaluate the previous methods

by Tom Baeyens (JIRA)

evaluate the previous methods ----------------------------- Key: JBPM-1288 URL: http://jira.jboss.com/jira/browse/JBPM-1288 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: PVM Reporter: Tom Baeyens this relates to Execution.getPreviousNode() Execution.getPreviousTransition() Node.isPreviousNeeded() Comment in Execution.java: // TODO evaluate the previous methods // these methods are kind of performance optimisations. a sequence and // some other specific control flow implementations can be optimised if they // have access to the previous node or transition. // Those activities could also be implemented by letting the activities store // the contextual information in process variables or some other execution // context. But with the previous properties as done now, these control flow // nodes can be implemented without storing an extra record. It's only a property // that is only updated when the node configuration indicates that it's needed. // (see also Node.isPreviousNeeded()) -- 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

15 years, 6 months

1
7
0 / 0

[JBoss JIRA] Created: (JBPM-1113) Maximum number of cursors exceeded: ResultSet not closed?

by Martin Vecera (JIRA)

Maximum number of cursors exceeded: ResultSet not closed? --------------------------------------------------------- Key: JBPM-1113 URL: http://jira.jboss.com/jira/browse/JBPM-1113 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM jPDL 3.2.2 Environment: SOA-P 4.2.0.beta2 (JBossESB 4.2.1), Oracle 10g Reporter: Martin Vecera Assigned To: Tom Baeyens We deployed a performance test (see attached file) based on bpm_orchestration2. When we generated a large backlog of messages (10,000) there started to be problems with cursors. This doesn't happen when BPM is not used. See attached file for server log. 11:59:10,560 WARN [JDBCSupport] SQLException caught, SQLState 72000 code:1000- assuming deadlock detected, try:23 java.sql.SQLException: ORA-01000: maximum open cursors exceeded at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:288) at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:743) at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:216) at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:955) at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1168) at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3316) at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3400) at org.jboss.resource.adapter.jdbc.WrappedPreparedStatement.executeUpdate(WrappedPreparedStatement.java:251) at org.jboss.messaging.core.impl.JDBCPersistenceManager$1HandleBeforeCommit1PCRunner.doTransaction(JDBCPersistenceManager.java:1593) at org.jboss.messaging.core.impl.JDBCSupport$JDBCTxRunner2.execute(JDBCSupport.java:465) at org.jboss.messaging.core.impl.JDBCSupport$JDBCTxRunner2.executeWithRetry(JDBCSupport.java:503) at org.jboss.messaging.core.impl.JDBCPersistenceManager.handleBeforeCommit1PC(JDBCPersistenceManager.java:1680) at org.jboss.messaging.core.impl.JDBCPersistenceManager$TransactionCallback.beforeCommit(JDBCPersistenceManager.java:2790) at org.jboss.messaging.core.impl.tx.Transaction.commit(Transaction.java:208) at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.sendTransaction(ServerConnectionEndpoint.java:474) at org.jboss.jms.server.endpoint.advised.ConnectionAdvised.org$jboss$jms$server$endpoint$advised$ConnectionAdvised$sendTransaction$aop(ConnectionAdvised.java:101) at org.jboss.jms.server.endpoint.advised.ConnectionAdvised$sendTransaction_N3268650789275322226.invokeNext(ConnectionAdvised$sendTransaction_N3268650789275322226.java) at org.jboss.jms.server.container.SecurityAspect.handleSendTransaction(SecurityAspect.java:195) 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:585) at org.jboss.aop.advice.PerInstanceAdvice.invoke(PerInstanceAdvice.java:121) at org.jboss.jms.server.endpoint.advised.ConnectionAdvised$sendTransaction_N3268650789275322226.invokeNext(ConnectionAdvised$sendTransaction_N3268650789275322226.java) at org.jboss.jms.server.container.ServerLogInterceptor.invoke(ServerLogInterceptor.java:105) at org.jboss.jms.server.endpoint.advised.ConnectionAdvised$sendTransaction_N3268650789275322226.invokeNext(ConnectionAdvised$sendTransaction_N3268650789275322226.java) at org.jboss.jms.server.endpoint.advised.ConnectionAdvised.sendTransaction(ConnectionAdvised.java) at org.jboss.jms.wireformat.ConnectionSendTransactionRequest.serverInvoke(ConnectionSendTransactionRequest.java:82) at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:143) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:795) at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:573) at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:387) at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166) -- 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

15 years, 6 months

3
8
0 / 0

[JBoss JIRA] Created: (JBPM-1236) fix for undescriptive NullPointerException when jbpm4jsf-config.xml is missing

by Gergely Nagy (JIRA)

fix for undescriptive NullPointerException when jbpm4jsf-config.xml is missing ------------------------------------------------------------------------------ Key: JBPM-1236 URL: http://jira.jboss.com/jira/browse/JBPM-1236 Project: JBoss jBPM Issue Type: Patch Security Level: Public (Everyone can see) Components: Web Interface Reporter: Gergely Nagy An undescriptive error page is shown when jbpm4jsf-config.xml is missing: simple error 500 page with no indication to the cause of the error. I could only track this down by debugging jbpm4jsf, and it took me a while to figure this out. The attached patch includes a check for null, and a descriptive error message. -- 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

15 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-1185) Node, State and ProcessState don't support Conditions on Transitions

by Britt Miner (JIRA)

Node, State and ProcessState don't support Conditions on Transitions -------------------------------------------------------------------- Key: JBPM-1185 URL: http://jira.jboss.com/jira/browse/JBPM-1185 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM jPDL 3.2.2 Reporter: Britt Miner Assigned To: Tom Baeyens Node, State, and ProcessState don't provide any preliminary check for conditions provided on transitions. No check is performed until the transition is signaled, at which point the process will barf if a condition is present on the default transition, and that condition evaluates to false. Regardless if a person "should" be using transition conditions in Node or State, the schema allows it, the documentation doesn't forbid it, and the current behavior of a Transition element in the jpdl is inconsistent. The fix to make everything consistent is fairly simple--only org.jbpm.graph.def.Node needs to really be altered (and a one-liner in ProcessState): In org.jbpm.graph.def.Node, add the following method: // BRITT-- public Transition calculateLeavingTransition(ExecutionContext executionContext) { Transition transition = null; boolean hasTransitioned = false; Iterator iter = leavingTransitions.iterator(); while (iter.hasNext()) { Transition candidate = (Transition) iter.next(); String conditionExpression = candidate.getCondition(); if (conditionExpression != null) { Object result = JbpmExpressionEvaluator.evaluate(conditionExpression, executionContext); if (Boolean.TRUE.equals(result)) { transition = candidate; } } else { transition = candidate; } } if (!hasTransitioned) { this.getDefaultLeavingTransition().removeConditionEnforcement(); log.warn("All transition conditions have evaluated to 'false'. Taking the default transition."); transition = this.getDefaultLeavingTransition(); } return transition; } // --BRITT ...and modify "leave(ExecutionContext executionContext)": // BRITT --replace the following line with the code below // to check conditions before selecting the transition to take... //leave(executionContext, getDefaultLeavingTransition()); //original line leave(executionContext, calculateLeavingTransition(executionContext)); // --BRITT For consistency, ProcessState should also have one line modified at the very end of it's "leave(ExecutionContext, Transition)" method: // BRITT-- rather than specify which transition, let the super class decide... //super.leave(executionContext, getDefaultLeavingTransition()); super.leave(executionContext, calculateLeavingTransition(executionContext)); // --BRITT -- 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

15 years, 9 months

5
11
0 / 0

[JBoss JIRA] Created: (JBPM-1280) QA job executor

by Tom Baeyens (JIRA)

QA job executor --------------- Key: JBPM-1280 URL: http://jira.jboss.com/jira/browse/JBPM-1280 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: PVM Reporter: Tom Baeyens First, we need to establish what we're going to QA and how. I see 3 distinct types of tests for the job executor 1) Using JobSession to create jobs and then use the JobExecutor API's to control the execution of those jobs. This way, all these tests can and should be done in a single thread. * a commit for processing an asynchronous message * a commit for processing a timer * a commit for the combination of a an asynchronous message and a timer * a commit with a custom resource in the standard transaction * test a rollback caused by a user code exception in an asynchronous continuation * test a rollback caused by a user code exception in an timer * test a rollback caused by a user code exception with a custom resource in the standard transaction * test a rollback caused by an optimistic locking exception in an asynchronous continuation * test a rollback caused by an optimistic locking exception in an timer * test a rollback caused by an optimistic locking with a custom resource in the standard transaction 2) If we only use the public, stable API's, we'll be a lot more limited in what we're able to test. We can e.g. run this test suite against the jBPM 3 codebase. * create and execute a process with a couple of asynchronous continuation in it. * create and execute a process with asynchronous continuations in a concurrent section. * create and execute a process with a couple of timers in it. * create and execute a process with a couple of timers in a concurrent section * a combination of a timer and an asynchronous continuation 3) Load and stress tests. Also these should only make use of public API's and ways to deploy processes. So that this test suite is configurable/runnable on different environments (and also against the jBPM 3 codebase) -- 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

15 years, 10 months

3
19
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues July 2008