Pentaho Server issues
Follow the suggestions in these topics to help resolve common issues associated with the Pentaho Server:
- Publishing domain to the Pentaho Server fails
- Library conflicts
- Report parameters that include accented characters fail to validate
- VFS provider XML duplicates
- Tomcat logs report memory leaks
- Windows domains will not authenticate when using the JTDS driver
- PDI cannot access Amazon S3
See Pentaho Troubleshooting articles for additional topics.
Publishing domain to the Pentaho Server fails
- The Pentaho Server is running.
- Your security access is defined as the Pentaho administrator role. The default is admin.
- You did not use trailing or leading slashes in the Web Publish URL or Domain Name.
Determine what versions are correct based on your needs for these third-party libraries. Some known-problematic JARs are:
- commons-collections-3.2.jar (from Pentaho)
- commons-collections.jar (from JBoss in /jboss/server/default/lib/)
- jettison-1.01.jar (from Pentaho)
- jettison.jar (from JBoss in /jboss/default/deploy/jbossws.sar)
Report parameters that include accented characters
To avoid this error message, modify the Tomcat server to include accented character support. This modification is especially necessary if you plan to use Spanish, French, or any other language that use accented character sets.
The following example shows how to implement accented character set support:
Stop the Tomcat service.
sudo /etc/init.d/tomcat stop
Open the /tomcat/server/conf/server.xml file in a text editor.
Locate eachAdd a URIEncoding="UTF-8" parameter to it, as shown in the following sample code block:
Connectornode (typically, there are four in a default Tomcat configuration).
<Connector URIEncoding="UTF-8" port="8080" protocol="HTTP/1.1" connectionTimeout="20000" redirectPort="8443" />
Save and close the file, then restart the Tomcat service.
sudo /etc/init.d/tomcat start
VFS provider XML duplicates
To resolve this issue, merge the multiple files into one canonical edition.
Tomcat logs report memory leaks
Dec 17, 2010 10:18:19 AM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc SEVERE: The web application [/pentaho] registered the JBDC driver [mondrian.olap4j.MondrianOlap4jDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered. Dec 17, 2010 10:18:19 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [/pentaho] appears to have started a thread named [HSQLDB Timer @49cf9f] but has failed to stop it. This is very likely to create a memory leak. Dec 17, 2010 10:18:19 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [/pentaho] appears to have started a thread named [MySQL Statement Cancellation Timer] but has failed to stop it. This is very likely to create a memory leak. Dec 17, 2010 10:18:19 AM org.apache.catalina.loader.WebappClassLoader clearThreadLocalMap SEVERE: The web application [/pentaho] created a ThreadLocal with key of type [java.lang.InheritableThreadLocal] (value [java.lang.InheritableThreadLocal@a1320e]) and a value of type [org.pentaho.platform.engine.security.session.TrustedSystemStartupSession] (value [org.pentaho.platform.engine.security.session.TrustedSystemStartupSession@111089b]) but failed to remove it when the web application was stopped. This is very likely to create a memory leak.These warnings report problems with processes that are being removed while the Tomcat server is shutting down. However, they can be significant if you are restarting or redeploying the Pentaho Server web applications.
To avoid memory leak issues in redeployment, you should restart Tomcat rather than redeploying or restarting the web application with a live server.
Windows domains will not authenticate when using the JTDS driver
The domain must be appended to the end of the URL with a semicolon, as shown in the following example:
Stop the server, if it is running.
Navigate to /tomcat/webapps/pentaho/WEB-INF/classes/org/pentaho/platform/engine/services/runtime.
Open the plugins.properties file with any text editor.
Locate the following component names and remove the hash (#) at the beginning of each line:
Save and close the file.
Restart the server.
PDI cannot access Amazon S3
When trying to access Amazon S3 from the Pentaho Server using the Amazon Command Line Interface (CLI), you may receive an authentication error message. This message may appear when the Pentaho Server is not located on the same machine as the PDI client.
To resolve this error, verify that you are using the same service account to access S3 using the Amazon CLI as you are using to log in to the Pentaho Server.