Skip to main content
Pentaho Documentation

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

See Pentaho Troubleshooting articles for additional topics.

Publishing Domain to the Pentaho Server Fails

If publishing a domain to the Pentaho Server fails, confirm the following statements are true:

  • 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.

Library Conflicts

The Pentaho Server relies on many third-party libraries. These libraries provide everything from database connectivity to specific Java classes. If you have incompatible versions of any of these third-party libraries in your application server's global lib folder, they can cause a variety of problems related to starting and running the Pentaho Server.

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

If you run a report containing parameters with accented characters, you may get an error message which reads, "This parameter value is of an invalid value."

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:

  1. Stop the Tomcat service.
    sudo /etc/init.d/tomcat stop
  2. Open the /tomcat/server/conf/server.xml file in a text editor.
  3. Locate each Connector node (typically, there are four in a default Tomcat configuration) and add a URIEncoding="UTF-8" parameter to it, as shown in the following sample code block:
    <Connector URIEncoding="UTF-8" port="8080" protocol="HTTP/1.1"
                   connectionTimeout="20000"
                   redirectPort="8443" />
  4. Save and close the file, then restart the Tomcat service.
    sudo /etc/init.d/tomcat start

VFS Provider XML Duplicates

The vfs-provider.xml configuration file may be present in other application JARs that you have deployed to your Java application server. Having multiple instances of this file will cause classpath errors.

To resolve this issue, merge the multiple files into one canonical edition.

Tomcat Logs Report Memory Leaks

When shutting down Tomcat, you may see some SEVERE-level warnings similar to the following messages:

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

If you are using a JTDS JDBC driver and you want to use a Windows domain user to authenticate to a Microsoft SQL Server, the Windows syntax will not work for specifying the domain and user.

The domain must be appended to the end of the URL with a semicolon, as shown in the following example:

jdbc:jtds:sqlserver://svn-devel.example.com:1533/reportsInProgress;domain=testdomain