Timestamp issues

dan1 — Tue, 19 Jul 2016 13:36:15 GMT

Hi,I have the following setup:Activiti 5.21Tomcat 8Java 8Postgresql 9.4.1208I'm having issues with the timestamps stored in ACT_RU_TASK and ACT_HI_ACTINST by Activiti Engine. The timestamp provided by the engine is roughly a day behind the system time. Both Java and Postgres have the correct time. A

Re: Timestamp issues

martin_grofcik — Wed, 20 Jul 2016 08:30:00 GMT

Hi,

the best would be jUnit test.
It seems that you are setting a clock to -1D value somewhere in the code. That why clock implementation returns always the same value.

Regards
Martin

Re: Timestamp issues

dan1 — Wed, 20 Jul 2016 10:30:27 GMT

Hi Martin,

I'm using Activiti Engine and Explorer out of the box other than db, log4j, and engine property settings. I haven't modified any code. I decided to try one more thing. I went back to the original activiti-custom-context.xml WITHOUT my workaround to reproduce the issue. When the issue happens, I see this when tomcat starts up:

<code>
05:18:36,309 [Thread-5] INFO org.activiti.engine.impl.asyncexecutor.AcquireTimerJobsRunnable - starting to acquire async jobs due
05:18:36,349 [localhost-startStop-1] INFO org.activiti.explorer.conf.DemoDataConfiguration - Initializing demo groups
05:18:36,418 [localhost-startStop-1] INFO org.activiti.explorer.conf.DemoDataConfiguration - Initializing demo users
05:18:36,512 [localhost-startStop-1] INFO org.activiti.explorer.conf.DemoDataConfiguration - Initializing demo report data
05:18:36,514 [Thread-7] INFO org.activiti.engine.impl.asyncexecutor.AbstractAsyncJobExecutor - Shutting down the default async job executor [org.activiti.engine.impl.asyncexecutor.DefaultAsyncJobExecutor].
05:18:36,515 [Thread-5] INFO org.activiti.engine.impl.asyncexecutor.AcquireTimerJobsRunnable - stopped async job due acquisition
05:18:36,515 [Thread-6] INFO org.activiti.engine.impl.asyncexecutor.AcquireAsyncJobsDueRunnable - stopped async job due acquisition
Exception in thread "Thread-7" org.activiti.engine.ActivitiObjectNotFoundException: no processes deployed with key 'reviewSaledLead'
at org.activiti.engine.impl.persistence.deploy.DeploymentManager.findDeployedLatestProcessDefinitionByKey(DeploymentManager.java:145)
at org.activiti.engine.impl.cmd.StartProcessInstanceCmd.execute(StartProcessInstanceCmd.java:79)
at org.activiti.engine.impl.cmd.StartProcessInstanceCmd.execute(StartProcessInstanceCmd.java:37)
at org.activiti.engine.impl.interceptor.CommandInvoker.execute(CommandInvoker.java:24)
at org.activiti.engine.impl.interceptor.CommandContextInterceptor.execute(CommandContextInterceptor.java:57)
at org.activiti.spring.SpringTransactionInterceptor$1.doInTransaction(SpringTransactionInterceptor.java:47)
at org.springframework.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:133)
at org.activiti.spring.SpringTransactionInterceptor.execute(SpringTransactionInterceptor.java:45)
at org.activiti.engine.impl.interceptor.LogInterceptor.execute(LogInterceptor.java:31)
at org.activiti.engine.impl.cfg.CommandExecutorImpl.execute(CommandExecutorImpl.java:40)
at org.activiti.engine.impl.cfg.CommandExecutorImpl.execute(CommandExecutorImpl.java:35)
at org.activiti.engine.impl.RuntimeServiceImpl.startProcessInstanceByKey(RuntimeServiceImpl.java:82)
at org.activiti.explorer.conf.DemoDataConfiguration$1.run(DemoDataConfiguration.java:247)
at java.lang.Thread.run(Thread.java:745)
</code>

If I set create.demo.reports=false in the db.properties, tomcat starts up and deploys explorer without that exception and the system behaves as expected.

Here is my working db.properties (and I don't need the afore mentioned workaround where I reset the clock in activiti-custom-context.xml):

<code>
# demo data properties
create.demo.users=true
create.demo.definitions=false
create.demo.models=false
create.demo.reports=true

# engine properties
engine.schema.update=true
engine.activate.jobexecutor=true
engine.asyncexecutor.enabled=true
engine.asyncexecutor.activate=true
engine.history.level=full
</code>

Ultimately, it seems there is a hole where that exception occurs that causes the clock to get jacked up.

For now, I'm am fine since I no longer need my hacked up workaround. And I don't depend on the out of box reports since they need to be modified for Java 8 anyway.

Thanks,
Dan

topic Re: Timestamp issues in Alfresco Archive

Timestamp issues

Re: Timestamp issues

Re: Timestamp issues