January 2009 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Commented: (JBPM-445) getActorId in ProcessLog broken

by Gregory KISLING (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-445?page=com.atlassian.jira.plugi... ] Gregory KISLING commented on JBPM-445: -------------------------------------- I confirm this issue is not solve. (in 3.2.3 version neither) Is there any intention of reopen this issue ? Thanks, Greg. > getActorId in ProcessLog broken > ------------------------------- > > Key: JBPM-445 > URL: https://jira.jboss.org/jira/browse/JBPM-445 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Affects Versions: jBPM 3.0.1, jBPM 3.0.2, jBPM 3.1.0 > Reporter: michael lawley > Assignee: Tom Baeyens > > ProcessLog.getActorId() always delegates to its parent (if any) and the comment says that getActorId is overridden in AuthenticationLog. However there is no AuthenticationLog and there is no subclass of ProcessLog that overrides getActorId so this method _always_ returns null. > Perhaps a better approach would be to grav the actorId using Authentication.getAuthenticatedActorId(); in the ProcessLog constructor. Naturally this would require adding a new instance variable to ProcessLog. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-1990) JBPM-Enterprise ejb-jar.xml spelling error

by Aslak (JIRA)

JBPM-Enterprise ejb-jar.xml spelling error ------------------------------------------ Key: JBPM-1990 URL: https://jira.jboss.org/jira/browse/JBPM-1990 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Engine Affects Versions: jBPM 3.3.1 GA Reporter: Aslak The EJB 2.1 deployment descriptor for the CommandServiceBean contains a spelling error in the resource-ref element: {code} <res-type>javax.jms.ConnnectionFactory</res-type> {code} this should be(only 2 'n's): {code} <res-type>javax.jms.ConnectionFactory</res-type> {code} [http://anonsvn.jboss.org/repos/jbpm/jbpm3/trunk/modules/enterprise/src/ma...] This causes some interesting issues on Weblogic since the resource-ref element describes if the ConnectionFactory returned from JNDI is pooled and auto enlisted in XA([http://e-docs.bea.com/wls/docs103/jms/j2ee.html]). This is described correctly in the web.xml file, so async steps in a process with, jms configured only works if JBPM first was initialized via the web context(That way JmsMessageServiceFactoryImpl holds a ref to the 'correct' ConnectionFactory). -- 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, 11 months

2
2
0 / 0

Remote access to Jbpm Jboss

by Alexis Ducastel

Hello everybody ! We currently have to develop a Wf-XML interface for JBOSS JBPM. We are working on JBPM community 3.3 We really need to remotely instantiate a process by example, on a jbpm engine working on Jboss. This stuff could be well done on the jbpm-console. In parrallel we have tried to do this by using jbpm API unsuccessfully. Could anyone help us by providing us some advises, pieces of code, tutorials, or whatever you want .... Thanks a lot. Alexis

15 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (JBPM-1988) Suppression of StaleObjectStateExcpetion stack traces does not work with JtaDbPersistenceServiceFactory

by Martin Putz (JIRA)

Suppression of StaleObjectStateExcpetion stack traces does not work with JtaDbPersistenceServiceFactory ------------------------------------------------------------------------------------------------------- Key: JBPM-1988 URL: https://jira.jboss.org/jira/browse/JBPM-1988 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: SOA 4.2 CP03, jBPM 3.3.1 GA Reporter: Martin Putz Assignee: Alejandro Guizar As per Chapter 6.5 of the User Guide: "When running in a cluster, jBPM synchronizes on the database. By default with optimistic locking. This means that each operation is performed in a transaction. And if at the end a collision is detected, then the transaction is rolled back and has to be handled. E.g. by a retry. So optimistic locking exceptions are usually part of the normal operation. Therefor, by default, the org.hibernate.StateObjectStateExceptions the that hibernate throws in that case are not logged with error and a stack trace, but instead a simple info message 'optimistic locking failed' is displayed. Hibernate itself will log the StateObjectStateException including a stack trace. If you want to get rid of these stack traces, put the level of org.hibernate.event.def.AbstractFlushingEventListener to FATAL. " This does not work when the JtaDbPersistenceServiceFactory is used, as JtaDbPersistenceService.endUserTransaction() throws a *JbpmException*, and not a JbpmPersistenceException. -- 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, 11 months

3
2
0 / 0

[JBoss JIRA] Resolved: (JBPM-1989) Null Pointer Exception in jBPM JobExecutor on server shutdown

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1989?page=com.atlassian.jira.plug... ] Thomas Diesler resolved JBPM-1989. ---------------------------------- Resolution: Done Done > Null Pointer Exception in jBPM JobExecutor on server shutdown > ------------------------------------------------------------- > > Key: JBPM-1989 > URL: https://jira.jboss.org/jira/browse/JBPM-1989 > Project: JBoss jBPM > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core Engine > Affects Versions: jBPM 3.2.4 GA > Environment: SOA 4.3.0 CP01 pre-release with jBPM 3.2.4 and JSF console 3.3.1.GA > Reporter: Julian Coleman > Assignee: Thomas Diesler > Priority: Minor > > Observe following in log on server shutdown: > > WARN [org.jboss.soa.esb.services.jbpm.configuration.JbpmService] Stopping failed jboss.esb:service=JbpmService > > java.lang.NullPointerException > > at org.jbpm.job.executor.JobExecutor.stopAndJoin(JobExecutor.java:84) > > at org.jboss.soa.esb.services.jbpm.configuration.JbpmService.stopService(JbpmService.java:52) > > at org.jboss.system.ServiceMBeanSupport.jbossInternalStop(ServiceMBeanSupport.java:315) > > at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:247) -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-1989) Null Pointer Exception in jBPM JobExecutor on server shutdown

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1989?page=com.atlassian.jira.plug... ] Thomas Diesler updated JBPM-1989: --------------------------------- Fix Version/s: jBPM-3.2.4.SP1 jBPM 3.2.6 GA > Null Pointer Exception in jBPM JobExecutor on server shutdown > ------------------------------------------------------------- > > Key: JBPM-1989 > URL: https://jira.jboss.org/jira/browse/JBPM-1989 > Project: JBoss jBPM > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core Engine > Affects Versions: jBPM 3.2.4 GA > Environment: SOA 4.3.0 CP01 pre-release with jBPM 3.2.4 and JSF console 3.3.1.GA > Reporter: Julian Coleman > Assignee: Thomas Diesler > Priority: Minor > Fix For: jBPM-3.2.4.SP1, jBPM 3.2.6 GA > > > Observe following in log on server shutdown: > > WARN [org.jboss.soa.esb.services.jbpm.configuration.JbpmService] Stopping failed jboss.esb:service=JbpmService > > java.lang.NullPointerException > > at org.jbpm.job.executor.JobExecutor.stopAndJoin(JobExecutor.java:84) > > at org.jboss.soa.esb.services.jbpm.configuration.JbpmService.stopService(JbpmService.java:52) > > at org.jboss.system.ServiceMBeanSupport.jbossInternalStop(ServiceMBeanSupport.java:315) > > at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:247) -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Moved: (JBPM-1989) Null Pointer Exception in jBPM JobExecutor on server shutdown

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1989?page=com.atlassian.jira.plug... ] Thomas Diesler moved SOA-1149 to JBPM-1989: ------------------------------------------- Project: JBoss jBPM (was: SOA Platform) Key: JBPM-1989 (was: SOA-1149) Component/s: Core Engine (was: jBPM) Affects Version/s: jBPM 3.2.4 GA (was: 4.3 CP01) > Null Pointer Exception in jBPM JobExecutor on server shutdown > ------------------------------------------------------------- > > Key: JBPM-1989 > URL: https://jira.jboss.org/jira/browse/JBPM-1989 > Project: JBoss jBPM > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core Engine > Affects Versions: jBPM 3.2.4 GA > Environment: SOA 4.3.0 CP01 pre-release with jBPM 3.2.4 and JSF console 3.3.1.GA > Reporter: Julian Coleman > Assignee: Thomas Diesler > Priority: Minor > > Observe following in log on server shutdown: > > WARN [org.jboss.soa.esb.services.jbpm.configuration.JbpmService] Stopping failed jboss.esb:service=JbpmService > > java.lang.NullPointerException > > at org.jbpm.job.executor.JobExecutor.stopAndJoin(JobExecutor.java:84) > > at org.jboss.soa.esb.services.jbpm.configuration.JbpmService.stopService(JbpmService.java:52) > > at org.jboss.system.ServiceMBeanSupport.jbossInternalStop(ServiceMBeanSupport.java:315) > > at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:247) -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-1753) review event names

by Tom Baeyens (JIRA)

review event names ------------------ Key: JBPM-1753 URL: https://jira.jboss.org/jira/browse/JBPM-1753 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: PVM Reporter: Tom Baeyens Fix For: PVM 1.0.0 Beta1 process events should be start stop to be in sync with the API start-stop. node-begin and node-end might be changed to activity-start and activity-stop maybe process and activity event names could be unified ? -- 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, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (JBPM-1971) fix test-load hudson job in qa lab

by Tom Baeyens (JIRA)

fix test-load hudson job in qa lab ---------------------------------- Key: JBPM-1971 URL: https://jira.jboss.org/jira/browse/JBPM-1971 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Fix For: jBPM 4.0.0 Alpha2 http://hudson.qa.jboss.com/hudson/view/JBPM4/job/jbpm4-load/ -- 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, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (JBPM-1974) rename node to activity

by Tom Baeyens (JIRA)

rename node to activity ----------------------- Key: JBPM-1974 URL: https://jira.jboss.org/jira/browse/JBPM-1974 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Priority: Critical Fix For: jBPM 4.0.0 Alpha2 -- 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, 11 months

3
8
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues January 2009