January 2010 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-2560) Task definition does not have some properties set from jPDL task element

by Phil Bingley (JIRA)

Task definition does not have some properties set from jPDL task element ------------------------------------------------------------------------ Key: JBPM-2560 URL: https://jira.jboss.org/jira/browse/JBPM-2560 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jBPM 4.1 Environment: jBPM 4.1 Reporter: Phil Bingley The duedate and priority values in a jPDL task definition are not set on the task definition when parsed. This means that the due date is not automatically set when the task is created, nor the priority. -- 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

14 years, 10 months

6
28
0 / 0

[JBoss JIRA] Created: (JBPM-2609) Extend API to be able to list all outgoing transitions of active activities

by Sebastian Schneider (JIRA)

Extend API to be able to list all outgoing transitions of active activities --------------------------------------------------------------------------- Key: JBPM-2609 URL: https://jira.jboss.org/jira/browse/JBPM-2609 Project: jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.1, jBPM 4.2 Reporter: Sebastian Schneider Priority: Minor Fix For: jBPM 4.3 use case supplied by bwestrich: In our application, it is possible for a user to send an invalid transition to jBPM. When this occurs, there is a requirement for the server to display an error message that lists the valid transitions. -- 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

14 years, 10 months

4
6
0 / 0

[JBoss JIRA] Created: (JBPM-2517) Timer with due date set > 24 days in jPDL process definition will cause the timer to be set in the past

by Tobias Groothuyse (JIRA)

Timer with due date set > 24 days in jPDL process definition will cause the timer to be set in the past ------------------------------------------------------------------------------------------------------- Key: JBPM-2517 URL: https://jira.jboss.org/jira/browse/JBPM-2517 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.0 Reporter: Tobias Groothuyse I have a process with <time duedate="5 weeks"/> However when this timer gets instantiated in a running process it's actual duedate which is calculated is in the past. I traced this bug to the following piece of code: TimerImpl.class {code} } else { long millis = duration.getMillis() + 1000*( duration.getSeconds() + 60*( duration.getMinutes() + 60*( duration.getHours() + 24*( duration.getDays() + 7*duration.getWeeks())))); dueDate = new Date(now.getTime() + millis); } {code} Because all the fields from the duration object are of type int, when duration.getDays() is larger then 24 or a weeks larger than 4 for that matter an int overflow will occur and long millis will have a negative value. It is probably best to use the normale calendar operations in all cases to add intervals to the current systime. -- 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

14 years, 10 months

3
2
0 / 0

[JBoss JIRA] Created: (JBPM-2562) Hard-coded host and port for Tomcat

by aa bb (JIRA)

Hard-coded host and port for Tomcat ----------------------------------- Key: JBPM-2562 URL: https://jira.jboss.org/jira/browse/JBPM-2562 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Console Affects Versions: jBPM 4.1 Environment: RHEL 5, Tomcat 6.0.14, jdk 1.6.02 Reporter: aa bb When JBPM 4.1 is deployed on Tomcat, the "formUrl" attribute of process definitions is always "http://localhost:8080/...". The problem is in org.jbpm.integration.spi.mgmt.ServerConfigFactory which create an org.jbpm.integration.spi.mgmt.DefaultServerConfig for Tomcat. And DefaultServerConfig's methods getWebServiceHost and getWebServicePort always return "localhost" and "8080". -- 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

14 years, 10 months

4
9
0 / 0

[JBoss JIRA] Created: (JBPM-2740) BPMN2: embedded subprocess

by Joram Barrez (JIRA)

BPMN2: embedded subprocess -------------------------- Key: JBPM-2740 URL: https://jira.jboss.org/jira/browse/JBPM-2740 Project: jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Joram Barrez Assignee: Joram Barrez Fix For: jBPM 4.4 -- 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

14 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPM-2604) Saving a JPM4 process in Eclipse looses the transictions condition and script nodes

by Paul Smith (JIRA)

Saving a JPM4 process in Eclipse looses the transictions condition and script nodes ----------------------------------------------------------------------------------- Key: JBPM-2604 URL: https://jira.jboss.org/jira/browse/JBPM-2604 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: GPD Affects Versions: jBPM 4.1 Environment: Running Eclipse Ganymede Version: 3.4.2 Build id: M20090211-1700. JBPM 4.1 Tools. Reporter: Paul Smith Priority: Critical Running the JpdlConverterTool over a JBPM3.2 process xml file correctly converts the file. However if you open the file using GPD, move one of the nodes and then save the file then all of the transition nodes condition and script nodes disappear. I have attached a process that this can be tested with. -- 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

14 years, 10 months

3
4
0 / 0

[JBoss JIRA] Created: (JBPM-2626) Console login fails on tomcat

by Heiko Braun (JIRA)

Console login fails on tomcat ----------------------------- Key: JBPM-2626 URL: https://jira.jboss.org/jira/browse/JBPM-2626 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Console Affects Versions: jBPM 4.2 Reporter: Heiko Braun Fix For: jBPM 4.2 The actual reason is that the gwt-console-server module doesn't deploy: catalina out: INFO: Deploying web application archive gwt-console-server.war log4j:WARN No appenders could be found for logger (org.jboss.resteasy.plugins.server.servlet.ResteasyBootstrap). log4j:WARN Please initialize the log4j system properly. Nov 4, 2009 3:40:11 PM org.apache.catalina.core.StandardContext start SEVERE: Error listenerStart Nov 4, 2009 3:40:11 PM org.apache.catalina.core.StandardContext start SEVERE: Context [/gwt-console-server] startup failed due to previous errors tomcat logs: Nov 4, 2009 3:40:11 PM org.apache.catalina.core.StandardContext listenerStart SEVERE: Exception sending context initialized event to listener instance of class org.jboss.resteasy.plugins.server.servlet.ResteasyBootstrap java.lang.NullPointerException at org.jboss.bpm.report.JMXServerConfig.getServerDataDir(JMXServerConfig.java:88) at org.jboss.bpm.report.ReportFacade.initBirtService(ReportFacade.java:87) at org.jboss.bpm.report.ReportFacade.<init>(ReportFacade.java:71) at org.jboss.bpm.console.server.ConsoleServerApplication.<init>(ConsoleServerApplication.java:48) -- 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

14 years, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (JBPM-2691) Save exceptions thrown while executing a job in a separate transaction

by Alejandro Guizar (JIRA)

Save exceptions thrown while executing a job in a separate transaction ---------------------------------------------------------------------- Key: JBPM-2691 URL: https://jira.jboss.org/jira/browse/JBPM-2691 Project: jBPM Issue Type: Bug Affects Versions: jBPM 3.2.8 Reporter: Alejandro Guizar Assignee: Alejandro Guizar Fix For: jBPM 3.2.9 Currently the stack trace printout is saved in the same transaction provided the exception is not related to persistence. This scheme has two drawbacks: 1. Exceptions not related to persistence may still leave the job and the process instance as a whole in an inconsistent state. 2. Persistence exceptions are never saved. Hence saving the stack trace in a separate transaction would be preferable. -- 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

14 years, 11 months

2
14
0 / 0

[JBoss JIRA] Created: (JBPM-2047) PersistenceDbServiceTest and PersistenceServiceDbTest are dependent

by Jiri Pechanec (JIRA)

PersistenceDbServiceTest and PersistenceServiceDbTest are dependent ------------------------------------------------------------------- Key: JBPM-2047 URL: https://jira.jboss.org/jira/browse/JBPM-2047 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Engine Affects Versions: jBPM-3.2.5.SP1 Reporter: Jiri Pechanec Assignee: Thomas Diesler The tests can fail based on the execution order of these tests. If PersistenceDbServiceTest is executed first then it sets session factory to MockSessionFactory. Unfortunately it seems that the setting is SAME for ALL future newly created JbpmContexts. PersistenceServiceDbTest then tests that the factory is null but it is not assertNull(persistenceServiceFactory.sessionFactory). The same test also tests few more features that ends in calls of unsupported operations on the MockSessionFactory. I am not sure if this is a problem of test - then the sessionFactory should be cleard after test or if it is wrong that the setting is shared for all JBpmContexts. -- 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

14 years, 11 months

4
11
0 / 0

[JBoss JIRA] Created: (JBPM-1707) pageflow parsing is slow

by Alejandro Guizar (JIRA)

pageflow parsing is slow ------------------------ Key: JBPM-1707 URL: https://jira.jboss.org/jira/browse/JBPM-1707 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Engine Affects Versions: jBPM 3.2.3 Environment: Red Hat Enterprise Linux AS release 4 (Nahant Update 7) enterprise-installer-4.3.0.GA-1.ep1.8.jar jdk-1.5.0_16-fcs Reporter: Alejandro Guizar Assignee: Alejandro Guizar Fix For: jBPM 3.3.0 CR1 On a RHEL machine, while deploying a seam based ear, which contains 13 pageflow definitions, the parsing of these 13 pageflow files takes more than 34 minutes (!). The culprit seems to be the usage of the original systemId (http://jboss.com/products/seam/pageflow-2.0.xsd) in the org.jbpm.jdpl.xml.JpdlParser$JpdlEntityResolver class, as this apparently results in slow internet lookups: log.debug("original systemId as input source"); inputSource = new InputSource(systemId); Using a null InputSource: inputSource = new InputSource((InputStream)null); brings the parsing time down to less than 1 second. Of course it would be better to actually pass in a reference to the local pageflow-2.0.xsd file, which is inside the jboss-seam.jar. -- 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

14 years, 11 months

4
12
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues January 2010