March 2009 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-1438) Task assigned to different actor-id can be seen and manipulated in jBPM console

by Martin Vecera (JIRA)

Task assigned to different actor-id can be seen and manipulated in jBPM console ------------------------------------------------------------------------------- Key: JBPM-1438 URL: https://jira.jboss.org/jira/browse/JBPM-1438 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Engine Affects Versions: jPDL 3.2.2 Environment: JBossESB server 4.3.GA, bpm_orchestration4 Reporter: Martin Vecera By default JBossESB server 4.3.GA has several jBPM users configured including 'user' and 'manager'. bpm_orchestration4 example contains one process definition which assigns two tasks, first to actor-id 'user' and the second to actor-id 'manager'. The problem is that the 'user' can see and manipulate both of the tasks. Steps to reproduce: 1. download JBossESB server 4.3.GA 2. start it using bin/run.sh 3. go to samples/quickstarts/bpm_orchestration4 4. run one by one: ant deploy, ant deployProcess, ant startProcess 5. open jBPM console and login as 'user' with password 'user' 6. click on Tasks to see the task list and on Examine to open the task, then on Save and Close 7. refresh the task list and you can see second task assigned to 'manager', try to Examine it... -- 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, 9 months

3
8
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, 9 months

3
8
0 / 0

[JBoss JIRA] Created: (JBPM-2048) simplify sessions

by Tom Baeyens (JIRA)

simplify sessions ----------------- Key: JBPM-2048 URL: https://jira.jboss.org/jira/browse/JBPM-2048 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Fix For: jBPM 4.0.0.Beta1 i think that the db-sessions are useless. i don't think this will lead to any form of pluggability that is actually usable. so all DbSessions should be merged into 1 single DbSession. this will simplify the configuration and the implementation. -- 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, 9 months

1
6
0 / 0

[JBoss JIRA] Created: (JBPM-1812) Fix tests that don't cleanup the database

by Thomas Diesler (JIRA)

Fix tests that don't cleanup the database ----------------------------------------- Key: JBPM-1812 URL: https://jira.jboss.org/jira/browse/JBPM-1812 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Core Engine Reporter: Thomas Diesler Fix For: jBPM 3.3.1 GA if ((count == null) || (count != 0)) { hasLeftOvers = true; //System.err.println("FIXME: " + getClass().getName() + "." + getName() + " left " + count + " records in " + tableName); } -- 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, 9 months

2
12
0 / 0

[JBoss JIRA] Created: (JBPM-2026) add superstates

by Tom Baeyens (JIRA)

add superstates --------------- Key: JBPM-2026 URL: https://jira.jboss.org/jira/browse/JBPM-2026 Project: JBoss jBPM Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Assignee: Tom Baeyens Fix For: jBPM 4.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, 10 months

1
13
0 / 0

[JBoss JIRA] Created: (JBPM-2123) rename exclusive to decision

by Tom Baeyens (JIRA)

rename exclusive to decision ---------------------------- Key: JBPM-2123 URL: https://jira.jboss.org/jira/browse/JBPM-2123 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Assignee: Tom Baeyens Fix For: jBPM 4.0.0.Beta2 -- 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, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-2021) JBPM logs to stderr

by Heiko Braun (JIRA)

JBPM logs to stderr ------------------- Key: JBPM-2021 URL: https://jira.jboss.org/jira/browse/JBPM-2021 Project: JBoss jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Core Engine Reporter: Heiko Braun Fix For: jBPM 4.0.0.GA Taken from the enterprise tests (running inside AS) 2009-02-06 10:05:46,847 ERROR [STDERR] (http-127.0.0.1-8080-1) Feb 6, 2009 10:05:46 AM org.jbpm.log.Jdk14Log debug FINE: creating environment factory for jbpm.cfg.xml Why a custom logging implementation anyway? -- 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, 10 months

2
6
0 / 0

[JBoss JIRA] Created: (JBPM-2000) Render task forms based on jbpm4jsf

by Heiko Braun (JIRA)

Render task forms based on jbpm4jsf ------------------------------------ Key: JBPM-2000 URL: https://jira.jboss.org/jira/browse/JBPM-2000 Project: JBoss jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Heiko Braun Assignee: Tom Baeyens Fix For: jBPM 4.0.0.Beta1 MIght require porting of jbpm4jsf to jbpm4 and provide a 'server' component that the GWT console can leverage -- 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, 10 months

2
15
0 / 0

[JBoss JIRA] Created: (JBPM-2083) orchestrating human task demo

by Tom Baeyens (JIRA)

orchestrating human task demo ----------------------------- Key: JBPM-2083 URL: https://jira.jboss.org/jira/browse/JBPM-2083 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Assignee: Heiko Braun Fix For: jBPM 4.0.0.Beta1 See section Orchestrating Human Tasks in http://www.jboss.org/community/docs/DOC-13298 -- 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, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (JBPM-1796) Add process variable view

by Heiko Braun (JIRA)

Add process variable view ------------------------- Key: JBPM-1796 URL: https://jira.jboss.org/jira/browse/JBPM-1796 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: GWT Console 1.0.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, 10 months

1
5
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues March 2009