June 2009 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-2338) FF3 ad IE show blank page upon login

by Heiko Braun (JIRA)

FF3 ad IE show blank page upon login ------------------------------------ Key: JBPM-2338 URL: https://jira.jboss.org/jira/browse/JBPM-2338 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Console Affects Versions: GWT Console 1.0.0 CR1 Reporter: Heiko Braun Assignee: Heiko Braun Fix For: GWT Console 1.0.0 GA The script elements require closing tags in order to solve the problem -- 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

1
1
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

1
5
0 / 0

[JBoss JIRA] Resolved: (JBPM-1214) check optimistic locking in case of loops

by Joram Barrez (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1214?page=com.atlassian.jira.plug... ] Joram Barrez resolved JBPM-1214. -------------------------------- Resolution: Done Added tests for self-transition/loop back to same wait state in one transaction. No problems found. > check optimistic locking in case of loops > ----------------------------------------- > > Key: JBPM-1214 > URL: https://jira.jboss.org/jira/browse/JBPM-1214 > Project: JBoss jBPM > Issue Type: Task > Reporter: Tom Baeyens > Assignee: Joram Barrez > Priority: Minor > Fix For: jBPM 4.0 > > > When a self transition (or bigger loop) comes back to the same wait state in one transaction, potentially, there might be no updates flushed to the DB. > So we have to check if in that case optimistic locking works as expected and fix it if necessary. -- 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

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-2313) Unabled to enlist resource exception

by Jeff Yu (JIRA)

Unabled to enlist resource exception ------------------------------------ Key: JBPM-2313 URL: https://jira.jboss.org/jira/browse/JBPM-2313 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jBPM 4.0.CR1 Reporter: Jeff Yu Assignee: Jeff Yu I am integrating the jBPM and jboss Identity Management projects, and then I had the following exception. the scenario is: jBPM has its own HibernateSessionFactory, and the jboss identity Management also use another one HibernateSessionFactory, both two datasource were configured in the XA datasource. The error stack trace is: ----------------- Caused by: org.jboss.util.NestedSQLException: Could not enlist in transaction on entering meta-aware object!; - nested throwable: (javax.transaction.SystemException: java.lang.Throwable: Unabled to enlist resou rce, see the previous warnings. tx=TransactionImple < ac, BasicAction: 7f000001:baaf:4a2cc2f1:dc status: ActionStatus.ABORT_ONLY >); - nested throwable: (org.jboss.resource.JBossResourceException: Could not enlist in transaction on e ntering meta-aware object!; - nested throwable: (javax.transaction.SystemException: java.lang.Throwable: Unabled to enlist resou rce, see the previous warnings. tx=TransactionImple < ac, BasicAction: 7f000001:baaf:4a2cc2f1:dc status: ActionStatus.ABORT_ONLY >)) at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:95) at org.hibernate.connection.DatasourceConnectionProvider.getConnection(DatasourceConnectionProvider .java:92) at org.hibernate.jdbc.ConnectionManager.openConnection(ConnectionManager.java:446) at org.hibernate.jdbc.ConnectionManager.getConnection(ConnectionManager.java:167) at org.hibernate.jdbc.AbstractBatcher.prepareQueryStatement(AbstractBatcher.java:161) at org.hibernate.loader.Loader.prepareQueryStatement(Loader.java:1573) at org.hibernate.loader.Loader.doQuery(Loader.java:696) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:259) at org.hibernate.loader.Loader.doList(Loader.java:2228) at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2125) at org.hibernate.loader.Loader.list(Loader.java:2120) at org.hibernate.loader.hql.QueryLoader.list(QueryLoader.java:401) at org.hibernate.hql.ast.QueryTranslatorImpl.list(QueryTranslatorImpl.java:361) at org.hibernate.engine.query.HQLQueryPlan.performList(HQLQueryPlan.java:196) at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1148) at org.hibernate.impl.QueryImpl.list(QueryImpl.java:102) at org.jbpm.pvm.internal.query.AbstractQuery.execute(AbstractQuery.java:96) at org.jbpm.pvm.internal.query.AbstractQuery.execute(AbstractQuery.java:88) at org.jbpm.pvm.internal.svc.DefaultCommandService.execute(DefaultCommandService.java:42) at org.jbpm.pvm.internal.svc.EnvironmentInterceptor.execute(EnvironmentInterceptor.java:54) at org.jbpm.enterprise.internal.jta.JtaTransactionInterceptor.execute(JtaTransactionInterceptor.jav a:73) at org.jbpm.enterprise.internal.ejb.CommandExecutorSLSB.execute(CommandExecutorSLSB.java:102) 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.invocation.Invocation.performCall(Invocation.java:386) at org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(StatelessSessionContainer.ja va:228) at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionIntercep tor.java:156) at org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invoke(StatelessSessionInstanceInterce ptor.java:173) 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.process(SecurityInterceptor.java:228) at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:211) at org.jboss.ejb.plugins.security.PreSecurityInterceptor.process(PreSecurityInterceptor.java:97) at org.jboss.ejb.plugins.security.PreSecurityInterceptor.invoke(PreSecurityInterceptor.java:81) at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:205) at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:13 8) at org.jboss.ejb.SessionContainer.internalInvoke(SessionContainer.java:650) at org.jboss.ejb.Container.invoke(Container.java:1029) at sun.reflect.GeneratedMethodAccessor275.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) at org.jboss.invocation.unified.server.UnifiedInvoker.invoke(UnifiedInvoker.java:232) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:908) at org.jboss.remoting.transport.socket.ServerThread.completeInvocation(ServerThread.java:742) at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:695) at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:549) at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:230) Caused by: org.jboss.resource.JBossResourceException: Could not enlist in transaction on entering me ta-aware object!; - nested throwable: (javax.transaction.SystemException: java.lang.Throwable: Unabl ed to enlist resource, see the previous warnings. tx=TransactionImple < ac, BasicAction: 7f000001:baaf:4a2cc2f1:dc status: ActionStatus.ABORT_ONLY >) at org.jboss.resource.connectionmanager.TxConnectionManager.managedConnectionReconnected(TxConnecti onManager.java:409) at org.jboss.resource.connectionmanager.BaseConnectionManager2.reconnectManagedConnection(BaseConne ctionManager2.java:625) at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionMan ager2.java:499) at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConne ction(BaseConnectionManager2.java:941) at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:89) ... 55 more Caused by: javax.transaction.SystemException: java.lang.Throwable: Unabled to enlist resource, see t he previous warnings. tx=TransactionImple < ac, BasicAction: 7f000001:baaf:4a2cc2f1:dc status: ActionStatus.ABORT_ONLY > at org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener$TransactionSy nchronization.checkEnlisted(TxConnectionManager.java:879) at org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener.enlist(TxConn ectionManager.java:675) at org.jboss.resource.connectionmanager.TxConnectionManager.managedConnectionReconnected(TxConnecti onManager.java:403) ... 59 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

15 years

1
3
0 / 0

[JBoss JIRA] Work started: (JBPM-1214) check optimistic locking in case of loops

by Joram Barrez (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1214?page=com.atlassian.jira.plug... ] Work on JBPM-1214 started by Joram Barrez. > check optimistic locking in case of loops > ----------------------------------------- > > Key: JBPM-1214 > URL: https://jira.jboss.org/jira/browse/JBPM-1214 > Project: JBoss jBPM > Issue Type: Task > Reporter: Tom Baeyens > Assignee: Joram Barrez > Priority: Minor > Fix For: jBPM 4.0 > > > When a self transition (or bigger loop) comes back to the same wait state in one transaction, potentially, there might be no updates flushed to the DB. > So we have to check if in that case optimistic locking works as expected and fix it if necessary. -- 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

1
0
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

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

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

1
1
0 / 0

[JBoss JIRA] Created: (JBPM-2305) Implement a method in TaskService to return all active tasks of a process instance

by Ronald van Kuijk (JIRA)

Implement a method in TaskService to return all active tasks of a process instance ---------------------------------------------------------------------------------- Key: JBPM-2305 URL: https://jira.jboss.org/jira/browse/JBPM-2305 Project: JBoss jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Runtime Engine Environment: N/A Reporter: Ronald van Kuijk Priority: Minor Fix For: jBPM 4.1 On several occasions I had to show all open tasks in a process instance. I implemented that via a query, but it would be nice if jBPM had this in the 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

3
5
0 / 0

[JBoss JIRA] Created: (JBPM-2332) task query candidate problem

by Tom Baeyens (JIRA)

task query candidate problem ---------------------------- Key: JBPM-2332 URL: https://jira.jboss.org/jira/browse/JBPM-2332 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Runtime Engine Reporter: Tom Baeyens Assignee: Tom Baeyens Fix For: jBPM 4.0 when i use jbpm4.CR1, invoke taskService.findGroupTasks("chief1"), then i can get all tasks not only just for user chief1 and chief1's group chief. i read the TaskQueryImpl.java file, find this appendWhereClause("(participant.userId = :candidateUserId) or (participant.groupId in (:candidateGroupIds) )", hql); seems here lose a (), like this: appendWhereClause("((participant.userId = :candidateUserId) or (participant.groupId in (:candidateGroupIds) ))", hql); so i change the source file , then rebuild this class, that's ok. so who can tell me you also find this problem? why have so simple mistake in this version? -- 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

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues June 2009