February 2008 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-1112) <mail> action not allowed in <timer>

by Tong Zheng (JIRA)

<mail> action not allowed in <timer> ------------------------------------ Key: JBPM-1112 URL: http://jira.jboss.com/jira/browse/JBPM-1112 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM jPDL 3.2.2 Environment: JDK 1.5, jPDL 3.2.2 Reporter: Tong Zheng Assigned To: Tom Baeyens It's mentioned in the doc that "Anywhere you are allowed to specify actions in the process, you can specify a mail action". But mail action doesn't work inside timer. sample code: <state name="resolve-issue"> <event type="node-enter"> <mail name="notification" to="user1@localhost" template="notification"> </mail> </event> <timer name="timer-reminder-1" duedate="5 seconds"> <mail name="reminder-1" to="user1@localhost" template="reminder"> </mail> </timer> <transition to="end"></transition> </state> Got exception while deploying the definition: org.jbpm.jpdl.JpdlException: [[ERROR] line 20: cvc-complex-type.2.4.a: Invalid content was found starting with element 'mail'. One of '{"urn:jbpm.org:jpdl-3.2":action, "urn:jbpm.org:jpdl-3.2":script}' is expected.] at org.jbpm.jpdl.xml.JpdlXmlReader.readProcessDefinition(JpdlXmlReader.java:172) at org.jbpm.graph.def.ProcessDefinition.parseXmlInputStream(ProcessDefinition.java:180) at org.jbpm.graph.def.ProcessDefinition.parseXmlResource(ProcessDefinition.java:161) at org.albertahealth.waitlist.workflow.app.DeployProcess.deployProcessFromXml(DeployProcess.java:61) at com.albertahealth.waitlist.workflow.app.DeployEWProcessTest.testDeployProcessDefinition(DeployEWProcessTest.java:23) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:615) at junit.framework.TestCase.runTest(TestCase.java:154) at junit.framework.TestCase.runBare(TestCase.java:127) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:118) at junit.framework.TestSuite.runTest(TestSuite.java:208) at junit.framework.TestSuite.run(TestSuite.java:203) at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:128) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) -- 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, 10 months

5
10
0 / 0

[JBoss JIRA] Created: (JBPM-1084) NPE in VariableAccess with Oracle persistence

by Tom Baeyens (JIRA)

NPE in VariableAccess with Oracle persistence --------------------------------------------- Key: JBPM-1084 URL: http://jira.jboss.com/jira/browse/JBPM-1084 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM jPDL 3.2.2 Reporter: Tom Baeyens Assigned To: Tom Baeyens Oracle treats empty strings as null values. So the Access component value object is removed after storage and retrieval fronm the db in case the Access value field is an empty string. As a solution, an empty string is replaced with a space in case an Access object is created with an empty string. -- 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, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-1137) Leap Year Date Calculations

by Alejandro Guizar (JIRA)

Leap Year Date Calculations --------------------------- Key: JBPM-1137 URL: http://jira.jboss.com/jira/browse/JBPM-1137 Project: JBoss jBPM Issue Type: Support Patch Components: Core Engine Affects Versions: jBPM jPDL 3.2.2 Reporter: Alejandro Guizar Assigned To: Tom Baeyens Based on JBPM-1098 there is concern over date calculations in in jBPM 3.1 and 3.2. There might be issues around the end of Feb. Durations that are not expressed in months or years work correctly under the current model. Consider the following expression. endDate = new Date(startDate.getTime() + interval); If startDate is February 28, 2008 and interval is 1 day, then endDate will be February 29, 2008. Every day has the same duration even on leap years. The presentation layer is responsible of converting the milliseconds in a Date to a suitable representation in the calendar system. The Java APIs are all aware of leap years, so this is covered as well. The situation is different for months and years. If the interval above was 1 year, then endDate would be February 27, 2009. Because of the extra day in 2008, the expected endDate has shifted backwards one day. To fix this, our Duration class has to preserve the original unit of time instead of converting to milliseconds up front. Then we can do the following. startCalendar = Calendar.getInstance(); startCalendar.setTime(startDate); startCalendar.add(unit, interval); endDate = startCalendar.getTime(); -- 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, 1 month

6
25
0 / 0

[JBoss JIRA] Created: (JBPM-1085) Join of new process instance fails in Oracle

by Tom Baeyens (JIRA)

Join of new process instance fails in Oracle -------------------------------------------- Key: JBPM-1085 URL: http://jira.jboss.com/jira/browse/JBPM-1085 Project: JBoss jBPM Issue Type: Bug Affects Versions: jBPM jPDL 3.2.2 Reporter: Tom Baeyens Assigned To: Tom Baeyens Fix For: jBPM jPDL 3.2.3, jBPM 3.2.2 SOA 1 If in one transaction you create a new process instance and reach a join, you'll get a invalid StaleObjectStateException. The cause is that in case of oracle, hibernate will not insert the record in the database before the forced version increment in the join will be executed. That results in 0 rows updated and hence a StaleStateObjectException. The fix applied is that we added a flush before the forced version update in the join -- 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, 1 month

1
3
0 / 0

[JBoss JIRA] Created: (JBPM-1142) Deploying the jBPM 'websale' sample application - if any of the /src dirs are deployed - fails - project JIRA for SOA-445

by Len DiMaggio (JIRA)

Deploying the jBPM 'websale' sample application - if any of the /src dirs are deployed - fails - project JIRA for SOA-445 ------------------------------------------------------------------------------------------------------------------------- Key: JBPM-1142 URL: http://jira.jboss.com/jira/browse/JBPM-1142 Project: JBoss jBPM Issue Type: Bug Components: Training Affects Versions: jBPM jPDL 3.2.2 Environment: JBoss Developer Studio Build id: 1.0.0.GA SOA-P GA /opt/GA/soa-4.2.0.GA.zip /opt/GA/standalone-soa-4.2.0.GA.zip RHEL5 Linux ldimaggi.csb 2.6.18-53.1.13.el5 #1 SMP Mon Feb 11 13:27:52 EST 2008 i686 i686 i386 GNU/Linux Sun Java 1.5 java version "1.5.0_14" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_14-b03) Java HotSpot(TM) Client VM (build 1.5.0_14-b03, mixed mode) RDBMS H2, version: 1.0.66 (2008-01-18) CPU cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 13 model name : Intel(R) Pentium(R) M processor 1.70GHz stepping : 6 cpu MHz : 1700.000 cache size : 2048 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 2 wp : yes flags : fpu vme de pse tsc msr mce cx8 mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss tm pbe up est tm2 bogomips : 3398.35 Reporter: Len DiMaggio Assigned To: Tom Baeyens Details are in: http://jira.jboss.com/jira/browse/SOA-445 -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] Updated: (JBPM-751) unnecessary warning on valid process definition

by Ronald van Kuijk (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-751?page=all ] Ronald van Kuijk updated JBPM-751: ---------------------------------- Issue Type: Feature Request (was: Bug) Affects Version/s: jBPM jPDL 3.2.2 jBPM jPDL 3.2.1 jBPM jPDL 3.2 jBPM 3.1.4 jBPM 3.1.3 > unnecessary warning on valid process definition > ----------------------------------------------- > > Key: JBPM-751 > URL: http://jira.jboss.com/jira/browse/JBPM-751 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Affects Versions: jBPM 3.1.2, jBPM jPDL 3.2.2, jBPM jPDL 3.2.1, jBPM jPDL 3.2, jBPM 3.1.4, jBPM 3.1.3 > Reporter: Alex Burgel > Assigned To: Tom Baeyens > Priority: Trivial > > i get this warning: > process xml warning: warning: no swimlane or assignment specified for task '<task xmlns="urn:jbpm.org:jpdl-3.1" name="schedule" blocking="false" signalling="true" priority="normal"/>' > it seems a bit odd to generate a warning on a valid process definition. > i think it should either be illegal to have a task without an assignment or swimlane, or there shouldn't be any warning at all (maybe lower the logging level to INFO). -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBPM-1024) Serializable variables are not being deserialized when retrieved from process

by Wojciech Gdela (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-1024?page=comments#action_12399853 ] Wojciech Gdela commented on JBPM-1024: -------------------------------------- I've also encountered this bug. The "couldn't deserialize object" message appears in jbpm-console on task form screen. This is true for jpdl-3.2.2 suite running on jboss-4.0.4.GA (the one included in the suite). But the same process running in junit tests goes smoothly. Yesterday I checked out fresh jbpm.3 from CVS HEAD and built jbpm-console. On this console the bug didn't appear. > Serializable variables are not being deserialized when retrieved from process > ----------------------------------------------------------------------------- > > Key: JBPM-1024 > URL: http://jira.jboss.com/jira/browse/JBPM-1024 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Affects Versions: jBPM 3.1.4 > Reporter: thilker > Assigned To: Tom Baeyens > > Storing an serializable object in a process should write an "R" in the column "converter" in table JBPM_VARIABLEINSTANCE. > But the value of the field is "null". > The cause: > The converter ID is retrieved in class org.jbpm.db.hibernate.Converter at line 63. > For the case of the SerializableToByteArrayConverter the ID is "null". > Regards, > Thorsten -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-1090) JBPM.3 SOA-P branch - merge recent database tests fixes from trunk

by Aleksandar Kostadinov (JIRA)

JBPM.3 SOA-P branch - merge recent database tests fixes from trunk ------------------------------------------------------------------ Key: JBPM-1090 URL: http://jira.jboss.com/jira/browse/JBPM-1090 Project: JBoss jBPM Issue Type: Task Reporter: Aleksandar Kostadinov Assigned To: Koen Aers Fix For: jBPM 3.2.2 SOA 1 Recently Fady Matar fixed jpdl database tests in trunk. These changes need to be merged into the SOA-P branch. -- 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, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBPM-1094) some database tests fail when hsql configuration is removed

by Aleksandar Kostadinov (JIRA)

some database tests fail when hsql configuration is removed ----------------------------------------------------------- Key: JBPM-1094 URL: http://jira.jboss.com/jira/browse/JBPM-1094 Project: JBoss jBPM Issue Type: Bug Reporter: Aleksandar Kostadinov Assigned To: Fady Matar Tests org.jbpm.AllTests.testCustomVariableClassWithLongId org.jbpm.AllTests.testCustomVariableClassWithStringId org.jbpm.AllTests.testProcessDeployment fail with any database if hsqldb configuration from hibernate.cfg.xml is removed. Probably these are not picking up some configuration. See http://hudson.qa.jboss.com/hudson/view/jbpm/ for a reference. Assigning to Fady since he worked on database tests last time. Please reassign as appropriate. -- 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, 2 months

3
7
0 / 0

[JBoss JIRA] Created: (JBPM-1131) jpdl test suite hangs with pgsql

by Aleksandar Kostadinov (JIRA)

jpdl test suite hangs with pgsql -------------------------------- Key: JBPM-1131 URL: http://jira.jboss.com/jira/browse/JBPM-1131 Project: JBoss jBPM Issue Type: Bug Affects Versions: jBPM 3.2.2 SOA 1 Reporter: Aleksandar Kostadinov Assigned To: Fady Matar Fix For: jBPM 3.2.2 SOA 1 jpdl test suite hangs when run on pgsql. When looking at database connections I see: select * from pg_stat_activity where usename='jbpmsoa'; datid | datname | procpid | usesysid | usename | current_query | waiting | query_start | backend_start | client_addr | client_port ----------+---------+---------+----------+---------+----------------------------------------------------+---------+-------------------------------+-------------------------------+-------------+------------- 25965744 | jbpmsoa | 6880 | 25965743 | jbpmsoa | alter table JBPM_JOB drop constraint FK_JOB_PRINST | t | 2008-02-07 12:52:20.042304-05 | 2008-02-07 12:52:17.339142-05 | 10.18.0.131 | 58016 25965744 | jbpmsoa | 5781 | 25965743 | jbpmsoa | <IDLE> in transaction | f | 2008-02-07 12:52:17.334733-05 | 2008-02-07 12:32:49.631273-05 | 10.18.0.131 | 57703 When I killed 5781 then test suite continued. Then hanged again on: 25965744 | jbpmsoa | 18794 | 25965743 | jbpmsoa | <IDLE> in transaction | f | 2008-02-08 10:07:40.825724-05 | 2008-02-08 10:07:40.734023-05 | 10.18.0.131 | 59979 25965744 | jbpmsoa | 18795 | 25965743 | jbpmsoa | alter table JBPM_JOB drop constraint FK_JOB_PRINST | t | 2008-02-08 10:07:44.991683-05 | 2008-02-08 10:07:40.853339-05 | 10.18.0.131 | 59980 Probably a test is not finishing transaction. I hope to see it failed after the build. Will comment later with the results. -- 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, 2 months

2
9
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues February 2008