When TIBCO Live Datamart starts our project we see warning messages like:

• MemoryConfigTooLow: Maximum heap size configured to be 3,072 MB, which is below recommended size for LiveView production configurations
• lv-web/plugins does not exist
• lv-web/theme does not exist
• Inefficient time-window query : TimeField (transactionTime) should be indexed

What do these mean?

You may have seen all of these messages when running your own project or our LiveView Web sample project. These are mostly harmless, but if a feature or configuration setting was expected that these identify are missing, then further action should be taken.

Explanation

1) MemoryConfigTooLow
 

(fragment deploy): 2019-05-15 13:41:00.246000-0400 [12952:AsyncLogger] WARN  MemoryConfigTooLow: 
Maximum heap size configured to be 3,072 MB, which is below recommended size for LiveView production 
configurations

The recommended minimum JVM Heap size for Live Datamart is 4GB, or setting "-Xmx4g" in the server configuration. When no size is set then the server defaults to 3GB so that this message appears to alert the administrator that additional configuration is needed. When running in a Production environment explicitly configure JVM settings that will accommodate the amount of information expected to be retained in physical RAM.

2) lv-web/plugins does not exist
 

(fragment deploy): 2019-05-15 13:39:24.460000-0400 [12952:JettyService] WARN  
com.streambase.liveview.server.core.dashboard.plugins.PluginsLoader: 
C:\Users\user\Documents\workspace\MyWorkspace\.nodes\sample_lv_sample_lvweb.user\
fragments\liveview0/liveview/server/lv-web/plugins does not exist

LiveView Web checks for optional plugins. If there are none, then this message is reported to alert the administrator that there may be a problem. If you know there are no plugins, then this message may be ignored.

3) lv-web/theme does not exist

This one may be reported twice as:

(fragment deploy): 2019-05-15 13:39:24.475000-0400 [12952:JettyService] WARN  
com.streambase.liveview.server.core.dashboard.plugins.PluginsLoader: 
C:\Users\user\Documents\workspace\MyWorkspace\.nodes\sample_lv_sample_lvweb.user\fragments\
liveview0/liveview/server/lv-web/theme does not exist

and

(fragment deploy): 2019-05-15 13:39:24.475000-0400 [12952:JettyService] WARN  
com.streambase.liveview.server.core.dashboard.plugins.PluginsLoader: 
C:/Users/user/Documents/ws/MyWorkspace/sample_lv_sample_lvweb/src/main/liveview/lv-web/theme does not exist

LiveView Web checks for optional theme configuration. If there is none, then this message is reported to alert the administrator that there may be a problem. If you know there is no theme customization, then this message may be ignored. It is typical for production deployments that a branded theme is supplied to replace the TIBCO default branding.

4) Inefficient time-window query
 

(fragment deploy): 2019-05-15 13:41:41.952000-0400 [12952:RingBufferThread - 
ItemsSales.QueryInRef1.PopulateIndexField:0] WARN  com.streambase.liveview.engine.operator.ExtractIndicesOperator: 
ItemsSales: Inefficient time-window query : TimeField (transactionTime) should be indexed

This message is reported to indicate that there is a query registered which could run more efficiently by adding a secondary index to the table for the indicated field. The warning reports the table name ("ItemsSales" in this example) and the field name ("transactionTime") so a developer can find the table to modify easily.

When the query predicate selection criteria references an un-indexed field, then many rows may need to be inspected in order to satisfy the query and this will take additional time and processing power whenever a new query snapshot must be calculated. New snapshots are created when a client connects or reconnects, or a new query is submitted, or when sufficient rows change so that it is more efficient to report a new snapshot instead of report all add and remove events. 

Explanations for common startup warnings