KNOWLEDGE BASE

Error: "Unknown Error" When Viewing a Published Workbook that Contains Multiple Filters and Marks in a View


Published: 03 Feb 2017
Last Modified Date: 17 Feb 2017

Issue

When publishing a dashboard to Tableau Server, accessing a certain view that rendered well in Tableau Desktop results in the following error in a Tableau Server: 
Unknown Error.

Additionally, the following behaviors can be witnessed: 
  • The same error occurs when trying to reset the view. 
  • The view contains multiple quick filters and/or hundreds of marks
  • Apache (httpd) logs indicate a 500 error, but no error occurs in the vizql C++ or Java layer logs. The tomcat log indicates the following: 
<Date & Time> org.apache.catalina.core.ApplicationDispatcher invoke SEVERE: Servlet.service() for servlet Spring MVC Dispatcher Servlet threw exception java.lang.OutOfMemoryError: Java heap space

 

Environment

Tableau Server

Resolution

Simplification of the view such as limiting the number of Quick Filters to less than 10 or limiting the data set may prevent the error from occurring.

Alternatively, increase the vizql maximum heap space from the default of 512MB (Xmx512m) to 1024MB (Xmx1024m) via the following tabadmin commands (executed from the bin folder in Command Prompt as Administrator):

tabadmin stop
tabadmin set vizqlserver.vmopts '"-XX:+UseConcMarkSweepGC -Xmx1024m -Xms256m -XX:NewRatio=2 -XX:SurvivorRatio=6 -XX:+UseParNewGC -XX:+CMSParallelRemarkEnabled -XX:TargetSurvivorRatio=90 -XX:MaxTenuringThreshold=15"' 
tabadmin config
tabadmin start

Cause

The complexity of the view is resulting in vizql exhausting the default allotment of memory.

Additional Information

The tabadmin set command in the Resolution is sensitive to the exact use of single quote, double quote, setting, double quote, single quote. The default setting allows for maximum heap space memory of 512MB (Xmx512m), as recorded in the workgroup.yml:
vizqlserver.vmopts: -XX:+UseConcMarkSweepGC -Xmx512m -Xms256m -XX:NewRatio=2 -XX:SurvivorRatio=6 -XX:+UseParNewGC -XX:+CMSParallelRemarkEnabled -XX:TargetSurvivorRatio=90 -XX:MaxTenuringThreshold=15

Increasing the heap space for vizql to 1024MB should have no impact on performance or trigger any issues. However, increasing to sizes larger than 1024MB may cause issues with what the browser can handle via HTML.
Did this article resolve the issue?