Sun Java System Application Server Standard and Enterprise Edition 7 2004Q2 Update 7 Release Notes

Administration Infrastructure

This section describes the known administration infrastructure issues and associated solutions.

ID 

Summary 

6635248

*~ wildcard pattern does not work as documented.

See the Sun ONE Application Server 7 Developer's Guide (817–2176) for a list of available wildcard patterns used by Sun Application Server. However, the wildcard pattern with tilde in the ppath does not work as documented.

Solution

Add one of the following to the obj.conf file.

  • <Object ppath="/test[^h].html"> PathCheck fn="htaccess-find" filename=".htaccess"</Object>

  • <Object ppath="*~*(.testh.html|.testh.html/)">PathCheck fn="htaccess-find" filename=".htaccess" </Object>

  • <Object ppath="*~*.testh.html*"> PathCheck fn="htaccess-find" filename=".htaccess" </Object>

6245376

Virtual server’s obj.conf is not removed after deleting the virtual server.

By default, the configuration file for a virtual server is not removed from the filesystem after deleting the virtual server. 

Solution

Manually remove the virtual_server-obj.conf file of the deleted virtual server.

4686003

HTTP Quality of Service limits are not enforced.

Quality of Service (QOS) includes a means of specifying the maximum number of HTTP connections and the bandwidth limit. When these attributes are exceeded, a 503 error should be returned to the client. However, after enabling QOS through the Administration interface, the server does not enforce the QOS limits. 

Solution

To fully enable QOS features, you must manually add an AuthTrans fn=qos-handler line to the top of the default object in the obj.conf file of the virtual server. The qos-handler Server Application Function (SAF) and obj.conf configuration file are described in the Developer’s Guide to NSAPI.

4740022

SNMP: END OF MIB is returned when adding and starting a new instance server.

If you add and start a new instance without shutting down the instance server and subagent, an END OF MIB message is returned.

Solution

  1. To view a new instance, make sure the subagent and all the instance server processes are shut down. Under each server ->Monitoring -> "Enable SNMP Statistics Collection: on", apply the change, then restart each instance server, and start only one subagent process again.

  2. If the subagent is already running, don’t start any extra subagent processes in any instance. There can only be one master agent and one subagent for a Application Server installation (common for all domains/instances).

4865739

Negative test for instance port in server.xml corrupts domains.bin

If the port number and/or IP Address includes a letter character, no new instances can be created and the current instances become unmanageable. 

Solution

  1. Edit the server.xml file and the backup server.xml and correct the port number and/or IP Address.

  2. Execute the asadmin reconfig command using the keepmanualchanges=true option.

  3. Using the Administration Interface, stop the instance by selecting the instance name in the Administration tree.

  4. Restart the administration server and application server instance.