from your logs i see you are running your server on a windows-machine. We experienced problems in resuming the session thus timers did not fire when you are using a new session (e.g. server restart), caused by windows not writing a particular file.
You may want to check out the bug report: [JBPM-4788] Windows: GAV-jbpmSessionId.ser filename contains invalid characters - JBoss Issue Tracker
Did you experience the same problem in a single (not clustered) environment?
Thanks for sharing the details , let me also validate that it is dues to the same reason. appreciate your help @Dan Bu
I was not using quartz when I was deploying in the standalone mode. When I started doing the clustering I actually started configuring the quartz for the clustered deployment and hence right now actually I am trying to deploy standalone since the cluster one seems to not work. will let you know my update on standalone with the quartz how did it go.
Hi Dan Bu ,
I tried to deploy and set up using standalone mode , with quartz , I see that there is something more of the issue. in standalone mode the kjar is not even getting deployed. quartz is getting instanstiated though. more details can be found in here. in another thread which is related with the standalone with quartz deployment issue.
So I am actually stuck in here now . I think when i did the clustered deployment atleast I was able to deploy the kjar and was able to see the processes but in the standalone it is not at all allowing me to deploy the kjar if i start the JBPM with the quartz using the jDBC store persistence.
With the help of Maciej( Thanks) i was able to solve the issue, the main issue was that I didnt created the separate managed and non managed datasources which led to Quartz not triggering at all. - Thanks