Configuring Tomcat to use 64-bit Java VM on sparcv9
Assuming that the 64-bit JRE is installed, you will need to edit
$CATALINA_HOME/bin/setclasspath.sh, replacing all occurrences of
"$JAVA_HOME"/bin with "$JAVA_HOME"/bin/sparcv9.
Note that the 64-bit JVM will take up considerably more memory than the 32-bit version, and may also be slower.
"SQLException: No suitable driver"
Assuming that you have the driver installed correctly, here are some less obvious causes:
- Make sure that your context file resides as:
$CATALINA_HOME/conf/[Engine]/[Host]/[web-app-name].xml - Some JDBC drivers will not work if the password field is left empty. Set a password for the user that you are connecting as.
JSP EL is disabled by default in Tomcat 5.5.x
JSP EL is ignored by default if you are using a pre-2.4 web.xml
file. The opening <web-app> tag for a 2.4 web.xml
file looks like this:
<web-app xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd" version="2.4">
JSTL not recognized when upgrading to 1.2 libraries
Assuming that the proper taglib URIs are specified, and the proper versions of jstl.jar and standard.jar are installed, delete the taglib cache in the context's work directory.
For details, see this thread on the Sun Java Forums.
"WARNING: No Mapping for [path] in DispatcherServlet with name 'servletname'" with the Spring Framework
Spring's URL Handler Mapping classes match paths within the servlet. To match the URL '/context/path/to/servlet/foo', the URL pattern for the handler mapping would be '/foo'. This behavior can be changed by setting the 'alwaysUseFullPath' property for the handler mapping bean.