Currently session is not created for scheduler, so there is no change log saved for scheduler process. We are going to create session as scheduler user, So all change log are recorded
Environment
None
Attachments
1
Activity
Carlos Ruiz April 12, 2018 at 10:32 AM
Hi , no need to save it - I think it can be something in memory - so a server restart, or clicking the reload on the monitor page will create new sessions.
Deepak Pansheriya April 12, 2018 at 6:59 AM
, I think it is possible. We can keep session active per scheduler and use same session. We can store session ID on scheduler as reference too.
Carlos Ruiz April 11, 2018 at 10:55 AM
Thanks
This seems like an important improvement.
However, I think it would be great if is possible to preserve session between calls.
I've seen schedulers programmed to run every minute, so if that's the case it will generate a new session every minute and we'll end with a similar issue like we had with webservices (solved in )
Would it be possible to use a single session per tenant during server lifetime for all schedulers? If not, at least a single session per tenant for every scheduler?
This ticket to address issue related to google chat discussion
https://groups.google.com/forum/#!msg/idempiere/6M3ZHBOsSBg/u-hWMqMEAgAJ
Currently session is not created for scheduler, so there is no change log saved for scheduler process.
We are going to create session as scheduler user, So all change log are recorded