January 2008 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-1109) StringInstance hbm configuration column length of 4000 is ignored when generating the DDL

by Kevin Conner (JIRA)

StringInstance hbm configuration column length of 4000 is ignored when generating the DDL ----------------------------------------------------------------------------------------- Key: JBPM-1109 URL: http://jira.jboss.com/jira/browse/JBPM-1109 Project: JBoss jBPM Issue Type: Bug Affects Versions: jBPM jPDL 3.2.2 Reporter: Kevin Conner Assigned To: Tom Baeyens The reason for the discrepancy in the generated DDL files appears to be a conflict between the hibernate definitions for HibernateStringInstance.hbm.xml, StringInstance.hbm.xml and (potentially) JcrNodeInstance.hbm.xml. Each of these VariableInstance subclasses map entries onto the JBPM_VARIABLEINSTANCE using the same field, STRINGVALUE_, but only StringInstance.hbm.xml specifies the length. The length is obviously being ignored when the DDL files are created as the HIbernateStringInstance.hbm.xml is being loaded first. -- 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

16 years, 3 months

2
2
0 / 0

[JBoss JIRA] Updated: (JBPM-836) "ejb local timer lookup problem" in EjbSchedulerService.java

by Ronald van Kuijk (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-836?page=all ] Ronald van Kuijk updated JBPM-836: ---------------------------------- Fix Version/s: jBPM jPDL 3.2.3 > "ejb local timer lookup problem" in EjbSchedulerService.java > ------------------------------------------------------------ > > Key: JBPM-836 > URL: http://jira.jboss.com/jira/browse/JBPM-836 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Affects Versions: jBPM jPDL 3.2 beta 2 > Environment: cvs trunk build, jboss AS 4.0.5GA, ejb3, jms messaging > deploying jbpm-enterprise.ear > Reporter: Chris Russell > Assigned To: Tom Baeyens > Fix For: jBPM jPDL 3.2.3 > > > After deploying the jbpm-enterprise.ear to a jboss 4.0.5ga server getting an exception when trying to signal a transition to the end state. > ===EXCEPTION SEEN=== > 13:04:56,785 ERROR [ProcessInstanceBean$SignalTokenListener] Action threw an exception: ejb local timer lookup problem > JNDI name lookup in EjbSchedulerService using incorrect name/and or the TimerServiceBean not declared in > jboss.xml. > ===CODE FIXES FOR EXCEPTION== > RCS file: /cvsroot/jbpm/jbpm.3/enterprise/src/main/java/org/jbpm/scheduler/ejbtimer/EjbSchedulerService.java,v > retrieving revision 1.1 > diff -r1.1 EjbSchedulerService.java > 31c31,36 > < LocalTimerServiceHome localTimerServiceHome = (LocalTimerServiceHome) initial.lookup("java:comp/env/ejb/LocalTimerServiceBean"); > --- > > > > > > //RSC wrong name used > > //LocalTimerServiceHome localTimerServiceHome = (LocalTimerServiceHome) initial.lookup("java:comp/env/ejb/LocalTimerServiceBean"); > > //See also change to jboss.xml to include TimerServiceBean or this fix wont work either. > > LocalTimerServiceHome localTimerServiceHome = (LocalTimerServiceHome) initial.lookup("TimerServiceBean"); > RCS file: /cvsroot/jbpm/jbpm.3/enterprise/src/main/resources/jar/META-INF/jboss.xml,v > retrieving revision 1.2 > diff -r1.2 jboss.xml > 12a13,20 > >  > > <session> > > <ejb-name>TimerServiceBean</ejb-name> > > <jndi-name>ejb/TimerServiceBean</jndi-name> > > <local-jndi-name>TimerServiceBean</local-jndi-name> > > </session> > > > > -- 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

16 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-1105) jBPM download page missing lates GPD plugin

by Len DiMaggio (JIRA)

jBPM download page missing lates GPD plugin ------------------------------------------- Key: JBPM-1105 URL: http://jira.jboss.com/jira/browse/JBPM-1105 Project: JBoss jBPM Issue Type: Bug Components: Documentation Affects Versions: jBPM jPDL 3.2.2 Reporter: Len DiMaggio Assigned To: Tom Baeyens The problem is that this page lacks the latest jBPM GPD download: ------------------------------ http://www.jboss.com/products/jbpm/downloads JBoss jBPM Process Designer Plugin 3.0.13 9.15 MB 2007-01-25 ------------------------------ It's here: ------------------------------ http://labs.jboss.com/jbossjbpm/downloads/ jbpm-jpdl-designer-3.1.1 Stable 7.7 MB 2007-11-28 jbpm-jpdl-designer-3.0.13 Stable 9.2 MB 2007-01-25 ------------------------------ So - how can we either remove the http://www.jboss.com/products/jbpm/downloads page or get it up-to-date? See: http://jira.jboss.com/jira/browse/JBPM-1088#action_12392651 -- 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

16 years, 3 months

3
4
0 / 0

[JBoss JIRA] Commented: (JBPM-1022) 3.2.1 Admin Console: Any user sees all users tasks

by Sebastien M. (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-1022?page=comments#action_12394664 ] Sebastien M. commented on JBPM-1022: ------------------------------------ Ok, I'll try it this weekend. > 3.2.1 Admin Console: Any user sees all users tasks > --------------------------------------------------- > > Key: JBPM-1022 > URL: http://jira.jboss.com/jira/browse/JBPM-1022 > Project: JBoss jBPM > Issue Type: Bug > Components: Web Interface > Affects Versions: jBPM jPDL 3.2.1, jBPM jPDL 3.2.2 > Reporter: Burr Sutter > Assigned To: Ronald van Kuijk > Priority: Blocker > Fix For: jBPM jPDL 3.2.3 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > In the current Admin Console, any given user will see all other users tasks. Plus a user can "take" another person's assigned tasks even when they are not an "administrator". -- 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

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBPM-1022) 3.2.1 Admin Console: Any user sees all users tasks

by Ronald van Kuijk (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-1022?page=comments#action_12394245 ] Ronald van Kuijk commented on JBPM-1022: ---------------------------------------- might indeed be that I overlooked that. I sometimes have this habit of overlooking the obvious. Well, maybe even seldom, but this might be one of them. Can you give that a try? > 3.2.1 Admin Console: Any user sees all users tasks > --------------------------------------------------- > > Key: JBPM-1022 > URL: http://jira.jboss.com/jira/browse/JBPM-1022 > Project: JBoss jBPM > Issue Type: Bug > Components: Web Interface > Affects Versions: jBPM jPDL 3.2.1, jBPM jPDL 3.2.2 > Reporter: Burr Sutter > Assigned To: Ronald van Kuijk > Priority: Blocker > Fix For: jBPM jPDL 3.2.3 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > In the current Admin Console, any given user will see all other users tasks. Plus a user can "take" another person's assigned tasks even when they are not an "administrator". -- 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

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBPM-1022) 3.2.1 Admin Console: Any user sees all users tasks

by S. Mesnard (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-1022?page=comments#action_12394201 ] S. Mesnard commented on JBPM-1022: ---------------------------------- I might be wrong, but isn't it possible to easily fix it by changing the line in tasks.xhtml : <j4j:listTasks includeEnded="true" target="#{tasks}"/> by this one: <j4j:listTasksForActor actorId="#{request.remoteUser}" target="#{tasks}"/> ? > 3.2.1 Admin Console: Any user sees all users tasks > --------------------------------------------------- > > Key: JBPM-1022 > URL: http://jira.jboss.com/jira/browse/JBPM-1022 > Project: JBoss jBPM > Issue Type: Bug > Components: Web Interface > Affects Versions: jBPM jPDL 3.2.1, jBPM jPDL 3.2.2 > Reporter: Burr Sutter > Assigned To: Ronald van Kuijk > Priority: Blocker > Fix For: jBPM jPDL 3.2.3 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > In the current Admin Console, any given user will see all other users tasks. Plus a user can "take" another person's assigned tasks even when they are not an "administrator". -- 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

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBPM-1071) Possible problem in concurrent signalling from multiple threads

by Tom Baeyens (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-1071?page=comments#action_12394151 ] Tom Baeyens commented on JBPM-1071: ----------------------------------- that last comment is confusing to me. the first part says it's a mysql-on-linux issue. the second part says to leave jbpm-1071 open as that is a jbpm issue. who can shed a light on this ? > Possible problem in concurrent signalling from multiple threads > --------------------------------------------------------------- > > Key: JBPM-1071 > URL: http://jira.jboss.com/jira/browse/JBPM-1071 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Affects Versions: jBPM jPDL 3.2.2 > Environment: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux > MySQL 5.0.22 > Reporter: Jiri Pechanec > Assigned To: Len DiMaggio > Priority: Critical > Attachments: expl.tar.gz, LockingTest.java, log.txt > > > Attached is a simple test case that > 1) Deploys process definition with two nodes > 2) Starts the process instance that will go to the wait state on first node > 3) Starts 20 threads that tries concurrently signal the same process instance > 4) The second node writes a record to the database > The test case needs to be executed multiple times to see the incorrect behaviour. > This is an example of run output > Isol 8 > Action 1 > Action 2 > Action 2 > Action 2 > Action 2 > Action 2 1 > Action 2 1 > Action 2 1 > Action 2 1 > Signalist 5 > Signalist 6 > Signalist 8 > Signalist 12 > Signalist 7 > Signalist 13 > Signalist 14 > Signalist 15 > Signalist 9 > Signalist 16 > Signalist 17 > Signalist 18 > Signalist 4 > Success 7 > Failure 13 > Explanation of the outcome > 4 threads successfully executed the node action including database operation. All database opeartion were comitted (4 new records were created) > 3 threads successfully executed the signal operation but no real action was performed > 13 threads attempted to execute the signal operation but ended with an exception -- 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

16 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues January 2008