[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
[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, 10 months