Known issues

The following list describes wellknown issues in Tempus Serva.

Engine

Server suddenly crashes with a PermGen error

• Cause: Your application server has too small PermGen memory space.
• Resulotion: Increase to higher value (128 mB)

Tempus Serva loads ressources when needed: This include stuff like Office templates handlers and OLAP cubes. Using the wrong settings, can cause runtime errors when a user suddenly activates a feature that has not been used before. This is behaviour by design, and will not be changed in future releases.

http://tempusserva.dk/mediawiki/index.php?title=Memory_settings

Media files sometimes dont display after a boot

Media files are stored temporaryly within the web application when requested. Depending of the speed of the underlying filesystem, they will not allways be available for the server right away.

• Workaround: Reload the page (F5)
• Resolution: Tweak the configuration parameter mediaFilterDelayMS

Users get SSL warnings in their browsers

This is most likely because you are using a wrapper of a site, where the URL was originally HTTP. Because of this some items in the wrapper may be referenced using HTTP (causing SSL warnings).

Resolve by completing steps in this article

http://tempusserva.dk/mediawiki/index.php?title=Setting_up_SSL/HTTPS#Problems_with_wrappers

Designer

References not fixed during restore where components need renaming (solution/bundles)

Workaround: Correct all parent/child references manually and redeploy solution

Solution configurations cannot be set to an empty value

Workaround: Set value to single whitespace " ".

Old backups from other solutions found in list of backups

When deleting solutions the Designer does not delete corresponding backups (saftety reasons).

In the future a list will be implemented to browse older backups, but untill hen you should just ignore this issue.

Platform specific issues

Tomcat

Warning during server stop

Example

SEVERE: The web application [/sandbox] registered the JDBC driver [com.mysql.jdbc.Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.

The warning is of no importance because the shutdown automatically kills all objects in memory, and no memory leaks are there possible.

JBoss

WARN errors during boot

Example

17:56:40,337 WARN [org.jboss.as.server.deployment] (MSC service thread 1-12) Class Path entry ...

The warnings are due to jar taht have their version number appended to their name. Possible fixes include stripping the names of all jar files in the /WEB-INF/lib/, but recommended solution is ignoring the warnings.

OpenJDK

Problem with missing fonts

Example:

java.lang.Error: Probable fatal error:No fonts found

Fix: Install fonts into java library

https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+got+java.awt.headless+problem