Internet Express for Tru64 UNIX Version 6.8 Release Notes (14235)

Table Of Contents
19 Mailman in a Cluster Environment
The new release of Mailman provided in Internet ExpressVersion 6.8 does not support TruClusters,
and should not be installed in a TruCluster environment. Mailman is restricted to running on a
single member of a cluster.
20 Batik with Java 1.4.1 May Cause Segmentation Violations
Batik may abort with segmentation violations when using Java 1.4.1. To avoid potential issues,
use Java versions 1.3.1 or 1.4.2.
21 IMP Webmail Administration
You can use the IMP Webmail Administration utility to perform such tasks as enabling and
disabling IMP Webmail, modifying the mail server, and modifying preference driver. This utility
can be used to modify the configuration parameters of IMP Webmail. . Configuration information
is available on the Horde Web site in the Horde Administrator's FAQ at:
http://wiki.horde.org/FAQ
22 Tomcat Default Java Environment
Tomcat Version 5.5.x (Tomcat version of Internet Express Version 6.7 release) is designed to run
on J2SE 1.4. Therefore, you must make java14x as default java environment for Tomcat to work.
If there are constraints for a user to have Java14x as the default Java environment, that user can
edit /usr/internet/httpd/tomcat/bin/setenv.sh to change JAVA_HOME and
JAVA_CMD to point to the java14x environment. After making this change, a restart of Tomcat
is required.
23 Tomcat Security issue with snoop.jsp
It is possible that a remote attacker could use snoop.jsp to view internal IP addresses and other
sensitive information of the server. Therefore, in Internet Express Version 6.5, HP has removed
snoop.jsp from jsp-examples, retaining the source code for reference which is in simple
HTML format. For the clients who are not willing to upgrade Tomcat, HP recommends removing
snoop.jsp from the
/usr/internet/httpd/tomcat/webapps/tomcat/jsp-examples/snp/ directory.
24 Logging In With SOAP and Cocoon Enabled
When configured with SOAP/Axis and Cocoon, Tomcat may not create desired logs. Logs can
be initialized by following these steps:
1. Create a file called log4j.properties with the following content and save it into
common/classes.
log4j.rootLogger=debug, R
log4j.appender.R=org.apache.log4j.RollingFileAppender
log4j.appender.R.File=${catalina.home}/logs/catalina.log
log4j.appender.R.MaxFileSize=10MB
log4j.appender.R.MaxBackupIndex=10
log4j.appender.R.layout=org.apache.log4j.PatternLayout
log4j.appender.R.layout.ConversionPattern=%p %t %c - %m%n
log4j.logger.org.apache.catalina=DEBUG, R
2. Restart Tomcat.
By default, this option is not enabled because it can produce a large debug log file, which can
impact performance. This level should be used sparingly when you need to debug internal
Tomcat operations.
8