I was getting this error often. Can I know the reason?
This is affecting my application.
Hi Ajit i think your question is incomplete may i know which error you are getting ?
Thanks
Rajendra Singh
Hi,
You already asked this question here: https://www.outsystems.com/forums/discussion/38406/timer/
Please, avoid opening new posts for the same question.If you need, give an UP in the original question, providing more information, like the code of the Timer, what it is doing, etc.
Also, provide information about the state of your environment, as an application being invalidate (I think) may be caused by problems with the server.
Cheers.
Sorry will raise in same Eduardo.
Raj & Eduardo Please help me with this as it is affecting production environment.
This is how the error is logged.
And timer execution is stopped as well.
Please, provide all the information on the error (with the Stack Trace, etc).Also, please, when does this errors happens? Could you provide an image of the logging list in Service Center with the times?
P.S.
As it was explained in the other thread, the timer stops because it is raising a TIME OUT.
So, whatever you're doing in the timer, is taking longer than the time out defined (60 seconds). This will abort the timer.
You need to investigate if you can solve this issue increasing the time out of the timer, or if you need to take a different approach.
What I would like to understand is if this has any relation with the other error (cache invalidation)
Eduardo Jauch wrote:
Eduardo regarding that error I could see the application is published at the same time when the error Invalidate cache is logged.
Timeout for the timer configured is 20 minutes.
Below is the error log captured
Hi Ajithkumar.
The error about the invalidate cache is completely normal, so.
Everytime you publish a module or deploy an application, the cache of the application is invalidate, as there is a new application that must be loaded.
Regarding the timer, if the timeout of the timer itself is 20 minutes, there is another thing that is timing out and this is raising an exception.
Without knowing what your timer is doing, is hard to help.
I think we could both as same. Because after invalidating cache the error for timer is thrown. So the timer is interrupted because of the publish hope so.
The timer will deploy and install outsys application in the specified path.
Ajithkumar,
How is this affecting your application?
I mean, If you are publishing/deploying the application, yes, this will have inpact (that's the reason we don't do this often for production, but deploy very carefully).
What exactly is your concern?
The deploy is failing?
Hi Eduardo,
Apart from manually publishing the application. Is there any case by which the platform will kill and publish the application automatically?