May 2009 - jbpm-issues - Jboss List Archives

[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-2294) examples fail against postgresql

by Alejandro Guizar (JIRA)

examples fail against postgresql -------------------------------- Key: JBPM-2294 URL: https://jira.jboss.org/jira/browse/JBPM-2294 Project: JBoss jBPM Issue Type: Feature Request Components: Runtime Engine Affects Versions: jBPM 4.0.0.Beta2 Reporter: Alejandro Guizar Assignee: Alejandro Guizar Priority: Minor Fix For: jBPM 4.0.CR1 The failure occurs under any JDK and JBoss AS version. For details see the Hudson run. http://hudson.qa.jboss.com/hudson/view/JBPM4/job/jbpm4-jboss/26/ -- 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
9
0 / 0

[JBoss JIRA] Created: (JBPM-2216) add activity-behaviour activity

by Tom Baeyens (JIRA)

add activity-behaviour activity ------------------------------- Key: JBPM-2216 URL: https://jira.jboss.org/jira/browse/JBPM-2216 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Assignee: Tom Baeyens Fix For: jBPM 4.0.0.CR1 consistent with event-listener -- 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
3
0 / 0

[JBoss JIRA] Created: (JBPM-2214) consider sub process parameters

by Tom Baeyens (JIRA)

consider sub process parameters ------------------------------- Key: JBPM-2214 URL: https://jira.jboss.org/jira/browse/JBPM-2214 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Assignee: Tom Baeyens Fix For: jBPM 4.0.0.CR1 evaluate if the current variables sub elements of sub-process and task should be replaced with <parameter type="in|out|in-out" name="parameterName" value="expression" /> -- 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, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (JBPM-2252) update api usage of the state activity docs

by Tom Baeyens (JIRA)

update api usage of the state activity docs ------------------------------------------- Key: JBPM-2252 URL: https://jira.jboss.org/jira/browse/JBPM-2252 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.0.0.CR1 those are not yet updated to use the new ProcessInstance api -- 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, 7 months

1
3
0 / 0

[JBoss JIRA] Created: (JBPM-2215) make the set of value types concrete

by Tom Baeyens (JIRA)

make the set of value types concrete ------------------------------------ Key: JBPM-2215 URL: https://jira.jboss.org/jira/browse/JBPM-2215 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Assignee: Tom Baeyens Fix For: jBPM 4.0.0.CR1 here and there you can specify values (wire objects) in the process e.g. in field and arg injections in java method invocations the types should be synchronized over XSD, runtime engine (done), docs and designer. at least the java example in the docs refers to the hibernate session with an <env injection. that should be removed. with Koen I discussed that we'll support <string and <object wire values to start with. -- 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, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (JBPM-2283) document migration strategy and limitations

by Tom Baeyens (JIRA)

document migration strategy and limitations ------------------------------------------- Key: JBPM-2283 URL: https://jira.jboss.org/jira/browse/JBPM-2283 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.0.CR1 -- 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, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPM-2228) review esb activity

by Tom Baeyens (JIRA)

review esb activity ------------------- Key: JBPM-2228 URL: https://jira.jboss.org/jira/browse/JBPM-2228 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.0.0.CR1 determine whether the configuration options are valid for general usage. determine whether all users should get this or if this should only be visible in case users have jboss esb available (e.g. as part of the soa platform). we can decide to move esb activity to dev guide for now. -- 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, 7 months

1
4
0 / 0

[JBoss JIRA] Created: (JBPM-2282) document how to deploy a process

by Tom Baeyens (JIRA)

document how to deploy a process -------------------------------- Key: JBPM-2282 URL: https://jira.jboss.org/jira/browse/JBPM-2282 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.0.CR1 add a section in the userguide that explains the basics of the ant task for process deployment. -- 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, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPM-2243) add task forms to task examples

by Tom Baeyens (JIRA)

add task forms to task examples ------------------------------- Key: JBPM-2243 URL: https://jira.jboss.org/jira/browse/JBPM-2243 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Assignee: Heiko Braun Fix For: jBPM 4.0.0.CR1 the goal is that after the task processes have been deployed as part of the demo.setup, that users can just execute a full process with task forms. maybe a special example could be created which has 2 participants. so that a demo can be given that involves multilple people. it might be that the current gwt authentication even allows multiple browser tabs to show different users. that would be really nice. -- 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, 7 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