KBEC-00263 - Stalled jobs on ElectricFlow using the built-in database

Problem

Note: This article refers specifically to the built-in database shipped with ElectricFlow.

Using the built-in database supplied by ElectricFlow exposed some obscure scenarios that you may require some workarounds:

  • Flow takes an unexpectedly long time to start up
  • Your Flow instance has jobs that never end
  • You cannot delete some jobs from the Flow UI
  • Flow is unable to export your projects because of these same jobs

Solution for 4.2.x

Below is a description of how to access the built-in database directly, for example, how to remove a job you cannot kill through the Commander UI.

1. Stop ElectricCommander. (If it's still running, the databse lock will prevent you from accessing it.)

2. Go to to the Commander installation directory and start the database web UI console:

 jre/bin/java -jar server/lib/h2.jar -web -webAllowOthers

     Options used:

      -web: launch the database's web UI console

      -webAllowOthers: allow access to the database's web UI console from remote hosts

3. Type http://<CommanderServerHostname>:8082 in the browser address bar to access the built-in database's web UI console.

4. Use the following parameters when asked to log in:

    Driver class: org.h2.Driver

    JDBC URL: jdbc:h2:builtin/commander

    login: sa

    pwd: sa

5. Click Connect. The interface that appears in your browser allows you to look at the tables and/or create SQL statements.

    Example: To kill a job with ID '550558' run the following commands:  

update ec_job_step set status = 'completed' where job_id = 55058;

 delete from ec_resource_usage where job_id = 55058;

 update ec_resource set job_id = null where job_id = 55058;

7. Before restarting ElectricCommander, stop the database's web UI console by pressing <Ctrl-C> in the terminal.

    Note: Some database tips (http://www.h2database.com/html/tutorial.html) that may be useful.

Have more questions? Submit a request

Comments

Powered by Zendesk