Wrong dates. Activiti deployment date.

[vipi_voxa]

Hello Fellows!

I experience this strange product behavior, quite critical thing i must admit. The processes i am deploying via activiti explorer are getting wrong deployment date. And what is more crucial - instance actions also randomly gets wrong start_time_ and end_time_. 

Well, with a deployment i can replicate it quite easily. I just go to activiti admin (logged as  kermit_ and deploy my test processes. (Screenshot attached. You can see in a screen shot that OS date and time as well as DB date and time are fine). With instance actions i have not found a straight path to replicate, it is just happening, and it is a complete stopper to use the product, since it is not possible to analyze when the action happened. 

Maybe somebody can assist me with a solution. Hope it's kind of configuration or something... 

thank you in advance!

activit 5.22.0

db oracle 11g

app server: (wildfly) Jboss eap 7.0.0.GA

os jboss running on - windows 7 pro 

[cjose]

The process is most likely not getting deployed if there is no change to your bpmn xml. There is filtering in place that prevents duplicate deployments (Please see Activiti User Guide). If this is not the case, could you please provide a unit test to easily reproduce this issue?

Regards,

Ciju

[gdharley]

Just to clarify what Ciju said (which is absolutely correct).
When a new bar, zip or bpmn xml file is deployed, the deployment code checks to see if there were any changes to the bpmn files. Only if the bpmn file is updated or modified is the process redeployed. This can really cause confusion when other assets in the bar/zip may have changed.

[vipi_voxa]

Guys thank you at looking at this!

well, just to make it absolutely clear, the new deployment is successfully deployed. Before the deployment of the new process there are no similar deployments deployed (you probably can notice it in the deployment list on the first screenshot, left side - list of deployments consist only of demo reports and demo processes).

Table act_re_deployment does not hold any records about the new deployment on the moment of the deployment. I hope it is clear enough now.

After new deployment is done, the record appears in act_re_deployment not only with the wrong date but with the wrong time as well (date is in a past). 

Can you please guide me a of how to create a test case for this scenario? I can replicate it every time i deploy any process. 

[gdharley]

A couple of things we need in order to be able to reproduce this.

1. How are you deploying the app (REST, Java, spring auto deploy)?

2. What timezone is your laptop/computer in?

3. What timezone is the server in?
4. What timezone is the database in?

I have trouble seeing the specific dates in the database snapshot (I'm old and my eyes dont work very well) and without understanding the deployment mechanism and time it occurred (from your perspective) it's hard to piece together a scenario.

Thx,

Greg

‌