LAE

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: Carl_Morris

Hello,

In the past couple of days two of the jobs I have running have appeared to have become stuck, as I have seen a little image of a disk with a cross through it with the words 'Cannot connect to database' (or something similar). The jobs started successfully and then when I came to check on them after a while, this error was displayed. The strange part is that I noticed the jobs were still running, as the BRS/BRD files were still being output.

I did manage to reset the job, in the automation tool (with a previously provided graph) but it did cause the jobs I have linked to this (via 'Predecessor Succeeded') to run, when I would not have expected them to if the first job was showing as failed.

Do you know why this may have occurred? It has delayed our processing, due to the jobs not fully completing and given sufficient error messages.

Regards,
Carl

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: gmullin

When you ran the graph you have to clear a stuck job did the blue play/start button reappear in Logistics Manager? Could you rerun the whole set of jobs successfully if you kicked them off?

The message "Cannot connect to database" is seen through the Logistics Manager view? I think it's saying there's some issue connecting to the underlying H2 database that LAE uses. There might be more information in the logs - the webapp and stderr ones found in jetty/logs. If you need more help with it you could send them into support.

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: Carl_Morris

Hi,

When I cleared the jobs I was able to rerun them again and they ran successfully.

I will check, if/when, I next receive the error and send some logs into support.

Thanks for the advice.