TechNote

JRun 4: Known Issues

JRun4 Known Issues

JRun 4 for Windows,
UNIX, and Linux

Last Updated: October 11, 2002

This document describes the known issues in JRun 4. It is organized based on the following categories:

Service Pack 1
Installation/configuration
JRun 3.x migration
Documentation
Enterprise JavaBeans
JRun Management Console and admin server
Web server connectors
Web applications
Session persistence
JMS
JDBC
JRun servers
Server clustering
UNIX and Linux
Class paths
Localization
SSL
Logging
Web services
Flash remoting

Service Pack 1 (SP1)

45035 - When using session failover there is a difference in behavior when using<buddy-name>*</buddy-name> as compared with multiple buddy-name elements that list all the servers in the cluster.
If the origin server goes down, JRun either uses round robin (if * is used) or traverses the server list in the session ID (which causes the servers at the beginning of the list to be hit harder than the ones at the back). This has the most effect when there are only two buddies.
47440 - The latest Apache 2.0 module for JRun/CFMX requires Apache version 2.0.40 and is not backward compatible. Using the module with Apache 2.0.39 will throw the following syntax error when starting Apache:
```
 Syntax error on line xxx of ../Apache2/conf/httpd.conf: Cannot load ../mod_jrun20.dll into server: The specified procedure could not be found.. 
```
48359 - If you are running ColdFusion MX for J2EE on top of JRun 4 SP1, you must resolve the conflict between Axis engines by adding the following top-level element to the ColdFusion application's jrun-web.xml file. Note that this change disables web service support for JSPs and servlets within the coldfusion web application:
```
 <enable-jrun-web-services>false</enable-jrun-web-services> 
```
For more information on this issue, see the JRun 4 SP1 Release Notes.
49364 - When uninstalling JRun 4 on Windows, you must manually remove the directories that are not deleted by the uninstall program (for example, directories created by previously applied hot fixes or patches). Installing JRun over the previous directories can cause errors if you install a new version in the same location.
48402 - If the servers in a cluster are on different physical servers, you cannot run the Web Server Configuration Tool if more than one of the servers is running. To work around this situation, perform the following steps:
1. Ensure that only one of the JRun servers in the cluster is started.
2. Run the Web Server Configuration Tool against the started JRun server.
3. Stop the web server and manually add the JRun servers in the cluster to the proxyservers line injrun_root/lib/wsconfig/number/jrunserver.store. Use the form IP address:JCP port, separating each JRun server with a semi-colon. For example:
```
 proxyservers=1.64.22.137:51000;1.64.22.143:51000;1.64.22.126:51000 
```
  Alternatively, you can delete the jrunserver.store file and the web server connector will create it when the web server starts.
4. Start all the JRun servers in cluster.
5. Restart the web server.

Installation/configuration

After completing the JRun installation on Windows, the admin server and JMC are started automatically. If the admin server is not yet running, you may receive a page not found error in your web browser. If this happens, try refreshing the browser window to display the JMC.
When you start JRun 4, it uses an existing JRUN_HOME if it finds one, or it sets JRUN_HOME to the root directory of your JRun installation. JRun 4 will not run if you have a previous JRun release on your machine and JRUN_HOME is set to the root of that installation.
31952 - Install Anywhere requires you to enter the full path including the Java executable rather than the path containing the Java executable.
31989 - If JAVA_HOME has a space char in it, upon starting JRun you'll get something like:
Files\Javasoft\JRE\1.3.0_01"" was unexpected at this time.
32264 - Uninstall for UNIX and Linux does not to work correctly. The Uninstall script terminates and does not shut down the running servers or uninstall the web server connector. Users should shut down servers manually and look at the script injrun_root//install_data/uncfgws.sh to uninstall the installed web server connectors.
32541 - JRun can hang at startup if DNS returns the wrong IP address for your machine.
jniPath does not work properly for the LauncherInfo service in the jrun_root/servers/jrun_server/SERVER-INF/jrun.xml file. RMI port errors show up when trying to start the server if jniPath is set. A temporary solution is to include JNI path settings in your appropriate environmental variable (PATH for Windows, SHLIB_PATH for UNIX, and LD_LIBRARY_PATH for Linux).
32975 - Uninstall for UNIX and Linux requires all servers to be stopped manually or the servers could remain running after the uninstall. Check if JRun servers are running by entering the following command:
ps -ef | grep jrun
34753 - When you type in an invalid jrun command line argument, JRun displays an exception in addition to the usage statement.
35187 - Entering "jrun start" at the command line does not start all JRun servers.
35405 - The installer does not always correctly identify the version of an old JRE that is not supported.
35654 - With Netscape 4.x as the default browser, clicking on the "JRun Management Console" link on the Windows Start menu causes an error dialog box to appear with the message:
"Cannot find the file 'http://localhost:8000/' (or one of its components). Make sure the path and filename are correct and that all required libraries are available."
A Windows Explorer pop-up with the message"Unable to run this command" follows. Newer Mozilla-family browsers (Netscape 6.x and Mozilla .09x) also do not correctly handle the .url association and render the file contents rather than browsing to the shortcut.
35914 - The Solaris and HP/UX installers require that a JVM already be in your environment path.
35734 - Add/Remove Programs does not delete all of the JRun 4 directory with Windows. You must delete the directory manually, making sure no files are open and that any web servers that might lock any DLLs are down.
36839 - jrunsvc.exe should have the ability to list the servers registered since you need an internal [service-name] to remove a server.
37190 - Uninstalling JRun with the the samples server running (started from the command line or Launcher) can cause an error because the PointBase database is running.
38147 - AIX JDK detection is weak. If, by accident, the installer chooses a JDK that is not supported, the JRun servers do not start. To resolve this problem, edit thejrun_root/bin/jvm.config file after the installation and change the java.home parameter to reference a supported JDK (1.3 or higher).
38164 - The Tru64 installer has InstallAnywhere debug information turned on and throws the following exception:
com.macromedia was unable to be loaded: java.lang.ClassNotFoundException: com.macromedia Execute custom code
java.lang.ClassNotFoundException: com.macromedia 2 class com.macromedia unavailable.
38403 - If you install JRun on Windows with Norton AntiVirus enabled, the last installer screen causes a Norton AntiVirus alert: "Stop this script: (Recommended)." The installer Macromedia uses makes use of VBScript and Norton AntiVirus detects this to warn the user. The user should choose "Allow this activity once" from the Action dropdown.
38539 - Installing JRun on Tru64 clips the hostname for the JMC to 32 characters due to the limit of uname -n on Tru64.
39116 - Before configuring JRun to use the Zeus web server (version 4.0 of higher), you must:
1. Configure Zeus to have NSAPI enabled for the virtual server being used.
2. Set the NSAPI configuration file location to %zeushome%/ns-config.
  If the files obj.conf, magnus.conf and mimes.type do nott already exist in the %zeushome%/ns-config/https-<virtual-server>/config directory, you must create them. Use the links to the skeleton files located in the NSAPI Configuration section of the NSAPI page.
If you have not installed the Zeus administration server under the same $ZEUSHOME location as your Zeus web server, your Zeus virtual server can not be restarted as part of the JRun web server configuration. You must restart your virtual server after you install or remove the JRun web server configuration for Zeus.
44420 - Uninstall deletes all data in the JRun directory structure. This is different than JRun 3.x versions, which preserved deployed applications.
44638 - Security-related errors between machines can be caused by source and target machines not being seen by each other on the network. Make sure you can run nslookup in both directions from source and target machines using IP and machine name. Typical security access restrictions to remote servers return some kind of error like: "Software caused connection abort: socket write error."
444657 - You cannot remotely administer or cluster a server with two IP addresses.
44757 - In the security.properties file, if jrun.trusted.hosts includes a DNS name that resolves to more than one address, only one address is included in the trusted host list. Macromedia recommends using only IP addresses in the trusted host list.

JRun 3.x migration

34873 - The migration tool does not migrate JRun 3.x JMC users.
36776 - In JRun 4, users and roles are defined within each server's scope. According to this principal, while migrating JRun 3.1 users.properties file to jrun-users.xml, it should only be limited to the servers migrated from 3.1. Currently all existing JRun 4 servers are affected, including the admin and samples servers.

Documentation

You can deploy J2EE modules in expanded directories to a cluster when using local server deployment, but not when using a cluster deploy directory. This is not reflected in JRun Assembly and Deployment Guide, which indicates you can only deploy archived modules to a cluster.
The JMC online help and JRun Installation Guide indicate that you must delete JSP source files and classes after migrating web applications with the migration tool. The migration tool does this automatically.
37522 (JMS-related) - Since PointBase is the database JRun ships with, it has been added as the default database for database persistence in the jrun-jms.xml file. Settings for SQL Server are commented out. These settings are in jrun-jms.xml files for the default and samples servers. A PointBase database, jms_private, for JMS has been added to the pointbase/databases directory and a script for starting the database has been added to the pointbase directory. PointBase settings in jrun-jms.xml for both samples and default servers point to this database.
37554 - In jrun-web.dtd (for jrun-web.xml), the class-change-option element under the persistence-config element has been removed. This change is not reflected in the descriptor documentation in the jrun_root/docs/descriptordocs directory or JRun Administrator's Guide. Also note that the persistence-class must implement jrun.servlet.session.SessionStorage.
37589 - The documentation for JDBC-based session persistence states that the id column of your session table should be a varchar(40). However, the minimum is now varchar(100). The id previously was made of only {server name}-{session id}, but it now consists of {server name}-{app name}-{session id}. It changes from application to application and machine to machine.
37679 - For the session persistence documentation inJRun Administrator's Guide, a persistence-class value must implement jrun.servlet.session.SessionStorage. The class-change-option element is not related to persistence-class.
38503 - Adding the StartupCleanup element to the JMSAdapter settings in the jrun.xml file and setting the value to true causes database tables used by the JRun JMS implementation to get cleaned out at startup.
38539 - JRun 4 works with Sonic Software SonicMQ product version 3.5 and 4.0.
Note that when using Sonic version 4.0, their JAR file, formerly named "client.jar" in version 3.5, is now named "sonic_Client.jar". Appropriate accommodations in the JRun configuration steps must be made to account for this name change. Aside from this change, the 3.5 and 4.0 products work identically as far as JRun is concerned.
39589 - The -usage argument of the jrun command is not documented. jrun -usage returns a list of arguments. Users can use the -info switch to get build information and any bad switch including -help to get usage.
44826 - JRun SDK Guide, chapter 3, page 20 (Windows JRun Installers) has the following errors and omissions:
Missing modules:
- JRun4JMCHelp.msm
- JRun4jrunWizard.msm
- JRun4samples.msm

Incorrectly named modules:
- Jrun4JDBCDrivers.msm should be JRunMMDrivers.msm
- Jrunwebservices.msm should be Jrunwebsvc.msm
44415 - Page 23 of JRun Administrator's Guide (Multihosting with Apache) has some errors:
Second paragraph: The LoadModule statement is outside any VirtualHost directives because you can reference it only once at the global level It also needs to be before any of the VirtualHost directives that use JRun.

Example
Replace the # JRun Settings to with the following for an Apache 2 example or change mod_jrun20.c to mod_jrun.c if you want an Apache 1.3 example:

<IfModule mod_jrun20.c>
JRunConfig Verbose false
JRunConfig Apialloc false
JRunConfig Ssl false
JRunConfig Ignoresuffixmap false
JRunConfig Serverstore"C:/JRun4/lib/wsconfig/1/jrunserver.store"
JRunConfig Bootstrap 127.0.0.1:51003
#JRunConfig Errorurl <optionally redirect to this URL on errors>
AddHandler jrun-handler .jsp .jws
</IfModule>

Step 2: Remove entire second paragraph about ports.
Step 3: Replace with: Remove the newhost JRun Web Server using the JMC. Select newhost > Services > Active Web Servers > JRun Web Servers > delete.
Step 5. Add: Each JRun server has a unique serverstore file and bootstrap attribute. The serverstore file does not have to exist but the directory it goes in must exist. The bootstrap is the IP address of the JRun server followed by the Web Server Connector Proxy Port for that server in the form, ip-address:port.
Step 6. Restart the Apache web server. The JRun Apache connector logs to the Apache error log.

Enterprise JavaBeans

44859 - Fixed in SP1 (updated Oct. 11, 2002)
Entity bean primary key classes must be in the system classpath for remote invocations.
The queue named in the resource-env-ref-name element of the jrun-ejb-jar.xml and ejb-jar.xml files, and intended for use as a MessageDrivenBean destination, must match the message queue name defined in the destination-name element of the jrun-resources.xml file.

JRun Management Console and admin server

38276 - The JMC does not preserve the order of User Modules and Role Modules when writing the information to thejrun_root/servers/jrun_server/SERVER-INF/auth.config file. Also, the JMC does not let you change the order of the User Modules and Role Modules. If some of the modules have a security control flag of Requisite or Sufficient, the result of authentication is dependent on the order of the security modules. To set this ordering, update modules through directly through the auth.config file and not through the JMC.
37725 -If you use the JMC to start an active web server with SSL enabled, there is a delay of 30 to 40 seconds between when JMC says that the web server is running and the when the web server actually accepts HTTPS requests.
39552 - Do not customize the JRun admin server.
44850 - On the JMC's JRun Security page, the WindowsLoginModule is not listed as an option as a JAAS Role Module. You can use the WindowsLoginModule for Role Authorization. You can add the WindowsLoginModule by selecting "Custom JAAS Role Module" in the Role Modules section and clicking Add. For the name, enter jrun.security.WindowsLoginModule. In Options, enter"domainName" as name and the domain name you wish to use in the Value field. Alternatively, you can manually edit the auth.config file in a server's SERVER-INF directory. Add a line to the defaultRole as:
jrun.security.WindowsLoginModule optional domainName="<domain>" mode="ROLE";

Web server connectors

32291 - If installing the JRun 4 final release over JRun 4 beta 1, the IIS connector configuration has to be removed before reconfiguring IIS for the final release. The reason is that beta 1 (and JRun 3) installed a global filter for the connector. In the final release, the filter may be installed on at the global level or on a per web site basis, depending on whether "All" is selected for Web Sites or an individual web site name is provided. Since global filters supersede web site filters, the incorrect configuration will be used if you install on a per web site basis and the global filter is not removed.
To use Apache Web Server with JRun, Apache must be built with DSO support using the following commands:

./configure --prefix=(location-where-you-want apache-installed) --enable-module=so
make
make install
35026 - The Apache web server connector does not work with the version of Apache that ships with Solaris 8. It does work with hand-compiled versions of Apache.
35072 - The connector installer does not recognize servers with names containing a space.
37515 - When configuring the JRun 4 IIS ISAPI filter/connector, the previous filter (JRun 3.x) is deleted and replaced with the JRun 4 connector causing prior installations of JRun 3.x to not work.
44656 - JRun assumes local host is number 1 of the local host addresses and 127.0.0.1. When a system has a second localhost address, you cannot run the Web Server Configuration Tool and specify the second localhost.

Web applications

31180 - JRun 4 redeploys web applications that are deployed as WAR files when the server is restarted. If you do not precompile the JSPs in the WAR, all JSPs are recompiled when they are hit the first time.
31842 - When you include precompiled JSP pages in a WAR deployment you must either:
- Not include the corresponding JSP files
- Disable dynamic JSP compilation as described in the JRun Assembly and Deployment Guide.
This is because JRun determines whether or not to recompile a JSP page based on the JSP's timestamp. However, when working with a WAR file, the date becomes the timestamp of when JRun extracted the WAR. Thus, the JSP is always out of sync with the precompiled class.
32173 - jsp:getProperty and jsp:setProperty are not currently working with JRockit 2.2 when dealing with complex properties such as arrays, vectors, and custom objects.
34279 - You currently can not have a custom error page defined to handle 500 errors that is named 500.jsp. 500x.jsp works.
36917 - JSP compilation fails when there are non-ISO-Latin-1 characters in the filename. To fix this problem, remove jikes from jrun_root/bin and restart the server.
Filenames with non-ISO-Latin-1 characters will not be read when using the English version of Windows. To fix this problem, update JRun to use JDK 1.4. More information on this problem can be found here: http://developer.java.sun.com/developer/bugParade/bugs/4185525.html.

Session persistence

34861 - Under moderate load (16 VUs) via a JSP client, a JMS queue linked to a message-driven bean starts throwing jrun.jms.core.persistence.PersistenceException repeatedly after about two minutes. The message.dat file reaches about 5 MB by that time. After a 5 minute test, the file is 30 MB. Using JDBC session persistence could resolve this problem.

JMS

33115 - JMS destinations are always forced to be bound to /jms/queue/<queueJndiName> when the destination type is javax.jms.Queue, and to /jms/topic/<topicName> when the destination type is javax.jms.Topic. Connection factories are always forced to /jms/<ConnectionfactoryJndiName>.
37347 - You can use the JmsAdapter Service Autostart attribute (configured in jrun.xml) to control whether JRun should automatically start an instance of the JMS provider described by that adapter. The attribute can be set to true or false. If true (the default), JRun tries to start the JMS provider. If false, JRun assumes the provider is already running and attempts to connect to it. Note that this attribute is only useful when the adapter specifies a non-native JMS provider (such as SonicMQ). When the adapter specifies the built-in JRun JMS provider, this setting is ignored since it must always be true in that case.
44614 - Fixed in SP1 (updated Oct. 11, 2002)
The JMS client-jndi provider-url in the jrun-jms.xml file is hardcoded as 127.0.0.1:2908. If you create a new server, it always points to 2908 no matter what JNDI port you select for the new server. As a workaround, change the port number to the correct value in the jrun-jms.xml file.

JDBC

36168 - From the JMC, when you create a data source for a DB2 database, you can select "Vendor supplied" driver besides JRun driver. However, you can't specify the driver class and instead it is assumed you will use COM.ibm.db2.jdbc.app.DB2Driver. For DB2, there is also net driver. As a workaround, pick DB2 with a"Not-listed" database driver instead of the DB2 driver the JMC lists for you.
37345 - The JRunResultSet object is used when a data source has native-results set to false in the jrun-resources.xml file. There are numerous issues with JRunResultSet, and it is better to set native-results to true until these issues are resolved.
39064 - You receive an error (ORA-01475) when using the Macromedia driver with ECPerf and Oracle. Workarounds: Use the Oracle type IV driver or set statement pooling to false.
45118 - Calling a SELECT statement twice on the same JRun ResultSet object throws java.util.ConcurrentModificationException. The workaround is to set native-results=true, which is the default.

JRun servers

35997 - The samples server displays the following errormessage in Windows if the currentversion registry key in 'Software\JavaSoft\Java Runtime Environment\CurrentVersion' is 1.1.x:
"Registry key 'Software\JavaSoft\Java Runtime Environment\CurrentVersion'
has value '1.1', but '1.3' is required."
This is a Pointbase internal check done on Windows platforms. This only happens when the "default" JRE is 1.1.x.
36578 - The samples server requires that JAVA_HOME be set to start up. It also requires a JDK bin directory in the SYSTEM path or you will get errors on sample server startup pointing to SERVER-INF/jrun-users.xml. You also will not be able to log on to the compass application.
37338 - You cannot have more than two JRun servers started at the same time on Windows 98.
39589 - On Windows, JRun servers installed as services cannot be stopped from the command line using the "jrun -stopjrun_server" command.
39757 - When using the Bourne shell, using Control-D or typing exit to exit from the shell or Telnet session causes servers started in that session (admin/default/samples) to stop. For those systems (Solaris, etc.) that use a Bourne shell by default, when starting from the command shell, use the -nohup switch on the jrun command. For example:
jrun -nohup -start admin &

This problem does not apply to servers started with the JRun Launcher or the JMC.
44389 - Fixed in SP1 (updated Oct. 11, 2002)
The samples server does not start when using JDK 1.4 on Windows 2000. To fix this problem, comment out the PointBase Service in thejrun_root/servers/samples/SERVER-INF/jrun.xml file.
After disabling the PointBase service, you must manually start the compass, worldmusic, smarticket, and samples databases before starting the samples server. The jrun_root/pointbase directory contains scripts and batch files to start the databases.

Server clustering

Servers in a cluster must have unique names. If everyone on the subnet enables clustering on the default server by setting clustering enabled to true in the jrun.xml file, there will be problems (random access to JNDI) because there will be several default servers on the default clusterDomain. It is good practice to update the clusterDomain name in the jrun.xml file or in the JMC.
32207 - You receive the following harmless warning when starting a cluster-enabled server:

"Warning: file url in codebase component may cause problems(file:/C:/jrun4/lib/ext/reggie.jar) "
There is no such directory jrun4/lib/ext and the .jar file is not installed.
33163 - If you start a server that is part of a cluster and has the same name as another server already running in the cluster, the new server is allowed to join with no warning. Sometimes the new (non-unique) server shows up as added on the server with its same name, but not on the other servers in the cluster.
34922 -You must set the ClusterManager clusterEnabled attribute to true in the jrun.xml file to enable transactions for the default domain.
37795 - After updating an application deployed across a cluster (in the /cluster directory) the changes do not take
effect until the server it is deployed on is restarted.
39501 - Fixed in SP1 (updated Oct. 11, 2002)
For a server to be added to the connector service after the connector install is complete, the proxy service must be activated (deactivated set to false) in the jrun.xml file. If the server is running when connector installer is run, it correctly resets this attribute. However, if a server is later created and added to the cluster using the JMC, this attribute does not get set so the proxy service is not activated. Therefore, when the server starts up in the cluster, it correctly picks up already deployed applications, but is not added to connect (jrunserver.store), etc. Manually updating the jrunserver.store file does not work either.

UNIX and Linux

32376 - Unicode character /u00CD (capital I with accent acute) is being returned as /u00FD (small y with accent acute) on Solaris 8.
34540 -On UNIX console installations, when entering the username and password for the JRun administrator, the password is not masked. Password protection is only available when using the GUI installer.

Class paths

31512 - Classes/files that must be part of a server class path, such as JDBC drivers and tools.jar (for XDoclet), must be placed in the jrun_root//servers/lib directory, and the server must be restarted. These files are not added to the server class path when they are put in thejrun_root/servers/jrun_server/SERVER-INF/lib directory.

Localization

36357 - Double byte characters are not supported in server names or server path names.
36471 - request.getParameter() no longer always encodes Strings in ISO8859-1. Therefore, the code recommended in JRun 3.1 for handling non-English Strings in parameters no longer works consistently:
String input=new String(request.getParameter("text_field").getBytes("ISO-8859-1"),"Shift_JIS");

The workaround is to:

Remove the above code and use request.setCharacterEncoding(String enc) before calling request.getParameter(String param)

or

Create a filter mapped to "/*" that is set up in SERVER-INF/default-web.xml. All the filter has to do is:
request.setCharacterEncoding("ISO-8859-1");
36959 - JRun 4 does not support double byte server names.
39075 - Dynamic class loading and compiling doesn't work with double byte characters.

SSL

37216 -To use SSL between a web server connector and JRun Proxy Service on Solaris, you must have the OpenSSL libraries in your LD_LIBRARY_PATH. You will also need a /dev/random package, which you can get from http://www.cosy.sbg.ac.at/~andi.

Logging

37766 - Sometime the stderr and stdout logs are not written out to either the console or the log file quickly. The appearance of entries in the logs does not
correspond to what has taken place in the servlets. There is often a substantial delay between servlet activity and the appearance of the appropriate log entries. Especially when the server is under load testing, the log information is not written out until you stop the server.

Web services

37768 - You must modify thejrun_root/servers/jrun_server/SERVER-INF/default-web.xml file to enable Axis web services security.

Change:
<servlet>
<servlet-name>AxisServlet</servlet-name>
<display-name>Apache-Axis Servlet</display-name>
<servlet-class>org.apache.axis.transport.http.AxisServlet</servlet-class>
</servlet>
<servlet>

To:
<servlet>
<servlet-name>AxisServlet</servlet-name>
<display-name>Apache-Axis Servlet</display-name>
<servlet-class>org.apache.axis.transport.http.AxisServlet</servlet-class>
<init-param>
<param-name>use-servlet-security</param-name>
<param-value>true</param-value>
</init-param>
</servlet>

Flash Remoting

38492 - The Flash Remoting samples won't open on Netscape. Netscape requires the EMBED parameter and the flashvars attribute as shown in this example: