TechNote (Archived)

JRun 4 Updater 5 Known Issues

??? | Français

JRun 4 Updater 5 for Windows, UNIX, Linux, and MacOSX

This document describes the known issues in JRun 4 Updater 5. For a list of known issues with prior releases of JRun 4, see JRun 4 Updater 4 known issues (build 84683).

Installer

• 57037 - Solaris installations fail when reporting "ERROR" in the preinstallation summary "Available space" section. This occurs when there is approximately 6 GB of free space or more on the partition. Systems with less than 6 GB free space work correctly.
• 56942 - RedHat AS 2.1. Updater hangs when it unpacks files if the IBM JDK 1.3.1 is the default JDK.
• 59348 - RedHat Linux AS 3.0. JSPs throw error. Jikes needs a newer libstdc++ than currently in /usr/lib.
  500 Translator.CompilationFailedExceptionCompiler errors:/opt/jrun4/bin/jikesw: error while loading shared libraries: libstdc++-libc6.1-1.so.2: cannot open shared object file: No such file or directory
  
  /usr/lib/libstdc++.so.5.0.3 is the version installed in this case
  
  To find the version of libstc++
  
  rpm -ql libstdc++
/usr/lib/libstdc++.so.5
/usr/lib/libstdc++.so.5.0.3
• 60086 - On Windows 2003 systems with Service Pack 1 (SP1), the installer immediately exits in the "preparing to install" dialog before extracting files. This worked previously on Windows 2003 without SP1. See TechNote b39c1803 for more details.

Connectors/Clustering

• 56293 - Beginning with Sun One 6.1, the NSAPI connector cannot co-exist in the same virtual server or virtual server class with the built-in J2EE/JSP engine because both try to handle .jsp mappings, servlet mappings, and so on. The Sun One built-in search uses the Sun J2EE engine, so it must be put in a virtual server that is separate from the JRun server.
• 56864 - If Apache is running while the Updater is applied, the connector upgrade does not automatically restart Apache. You must manually start Apache.
• 56969 - JRun connector build 82803 configured for IIS 5 on Win2k in distributed mode will generate "JRun Connector protocol error" errors for every page request after the first one if the IIS setting for "cache ISAPI applications" is not checked.
• 59359 - JRun throws 500 error when cluster have a member with the default context root of "/" and other members with a non-default context root [lets say /A]. To work around this issue, all cluster members need either the context root of "/" or a context root not using "/" (/A, /B, /C).
• 59367 - For RedHat 3.0, make sure the "Legacy Software Applications" package is installed or the Apache connector will hang. This installs the correct compat-* libraries to run the connector.
  
  rpm -query libstdc++
rpm -query glibcif glibc 2.2.5.x or higher, this compatibility package is required
  
  Other possible workarounds:
  • compile the connector manually from source (instructions in wsconfig.jar ApacheModule.zip)
  • use java -jar wsconfig.jar with the new -apxs switch (re-compiles and configures all in one step)
  • use the [Advanced] options / [Build Apache module from source...] checkbox through the Web Server Config Tool (wsconfig.jar) GUI. (needs gcc on system)
    
    Note: The following Novell SuSE Linux versions will have similar problems as RedHat AS 3.0.
    • SuSE Linux Enterprise Server 8
    • SuSE 8.1 (2.4.19 kernel)
    • SuSE 7.3 (2.4.10 kernel)
    • SuSE 9

Miscellaneous

• 56180 - JRun does not launch when using IBM JDK 1.4.1 and generates the following message: "Could not create the Java virtual machine."
• 51752 - MacOSX support for JDK 1.4.1. java.home from jvm.config is not used for the Mac. The launcher uses the JVM pointed to by /System/Library/Frameworks/JavaVM.framework/Versions/Current, which is always JDK 1.4.1.
• 56180 - RedHat AS 2.1. Starting JRun server with IBM JDK 1.4.1 throws "JVMLH049: Guard page creation failed (errno=12)".
  To work around this issue, enter the following command: java -jar ./jrun.jar -start default
• 56903 - RedHat AS 3.0. Regression from Updater 3. Double clicking on wsconfig launches JRun Launcher UI instead of the wsconfig (Web Server Configuration) wizard. All binaries except jrun were changed to symbolic links for UNIX in Updater 4, which caused this side-effect. All /jrun4/bin binaries are identical to the executable renamed for each purpose (for example, sniffer, wsconfig, and so on.) To work around this issue:
  1. Delete the wsconfig symbolic link.
  2. Copy {jrun.home}/bin/jrun binary to wsconfig (for example, cp jrun wsconfig).
  
  Note: The preceding behavior occurs for other binaries in the {jrun.home}/bin directory that include symbolic links to "jrun". You can use the preceding workaround for these binaries (for example, cp jrun sniffer). This behavior does not occur if you launch wsconfig from the command line using the java -jar wsconfig command.
• 59254 - Possible issues when using JDK 1.4.1 on Compaq Tru64. To work around this problem, use JDK 1.3.1 with the operating system.
• 59486 - Log rotation doesn't work for {server}-err.log and {server}-out.log. To make all logs (event, err, out) roll over at 200k, edit the jrun.xml and make the changes shown below. This has been fixed in the /servers/template.zip used to create new servers.
  
  jrun.xml:
  <service outputclass="jrunx.logger.LoggerService" name="LoggerService">
  ..
  <attribute name="filename">{jrun.rootdir}/logs/{jrun.server.name}-event.log</attribute>
  
  should be:
  <attribute name="filename">{jrun.rootdir}/logs/{jrun.server.name}-{log.level}.log</attribute>
  
  Note: This change also replaces the event log - {server}-event.log - with separate -info, -warning and -user message logs. Ex: default-info.log, default-warning.log, default-user.log

Search Support

---