8.5

Edit

Automation Business Process complete, but there are no charts on Automation tab

Case 1

A user gets the Resource not found message.

Solution

Check the GET method in the console. If the link includes ${tableau.new.automation.workbook}, the tableau.new.automation.workbook property is not specified for the instance.

For new models, the tableau.new.automation.workbook property value equals to WF-Automation-j.

Case 2

Empty space instead of charts.

Solution

  1. Data saved to an incorrect Tableau database.
    1. Check that tableau.db.url is specified:
      1. If yes, check that tableau.automation.host matches tableau.db.url.
      2. If no, contact the OPS team.
    2. Restart training.
  2. Check the startEval plugin properties in the Training Business Process (config: Start Train&Evaluation). It should contain the use-tableau='true' option.
  3. If Tableau is enabled, check that workbooks are configured correctly, or contact the Tableau team.
  4. If Tableau is disabled, check that wfbi-service and tableau db use the same database.

Case 3

A wrong configuration of wfbi/tableauDb.

Solution

  1. Check that the JDBC parameter table is configured for the database used by the current WorkFusion instance.
  2. Open /opt/tomcat/conf/Catalina/localhost/workfusion.xml or /opt/tomcat/cont/context.xml if the previous file does not exist.
  3. Find the following parameters:
    • tableau/db/url: Tableau database
    • tableau/host/automation: Tableau server
  4. Make sure that the Tableau service configured in tableau/host/automation is set to use the database defined in tableau/db/url. Contact the system administrator to get more help.

Case 4

An error saving data to Tableau because the port is not open.

Solution

Log in to the Mesos master and check logs: /data/vds/eval/vds/<egid>/process/logs/workflow-000000.log.

When the port is not open, C3P0 pool improperly detects this situation as a deadlock as the connection does not return to pool for a long period. So, search for the error as shown below:

APPARENT DEADLOCK!!! Creating emergency threads for unassigned pending tasks!
2017-05-12 10:52:59,500 WARN  ThreadPoolAsynchronousRunner [4:eval_26.FEaT_8.SSTT] com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@67f53442 -- APPARENT DEADLOCK!!! Complete Status:
        Managed Threads: 3
        Active Threads: 3
        Active Tasks:
                com.mchange.v2.resourcepool.BasicResourcePool$ScatteredAcquireTask@1a56afdd
                        on thread: C3P0PooledConnectionPoolManager[identityToken->2so18a9n1y01lxnoxjmf0|63028e09]-HelperThread-#0
                com.mchange.v2.resourcepool.BasicResourcePool$ScatteredAcquireTask@6c88a44
                        on thread: C3P0PooledConnectionPoolManager[identityToken->2so18a9n1y01lxnoxjmf0|63028e09]-HelperThread-#2
                com.mchange.v2.resourcepool.BasicResourcePool$ScatteredAcquireTask@556423fa
                        on thread: C3P0PooledConnectionPoolManager[identityToken->2so18a9n1y01lxnoxjmf0|63028e09]-HelperThread-#1
        Pending Tasks:
                com.mchange.v2.resourcepool.BasicResourcePool$ScatteredAcquireTask@789191b3
                com.mchange.v2.resourcepool.BasicResourcePool$ScatteredAcquireTask@3a49ae4f
← PreviousNext →