Sun Java System Web Server 6.1 2005Q4 SP5 Release Notes

Issues Resolved in 6.1 SP3

The following table lists the issues resolved in Sun Java System Web Server 6.1 SP3.

Table 6 Issues Resolved in Sun Java System Web Server 6.1 SP3

Problem ID 

Description 

4798461 

GUI does not correctly reflect when `Transmit File' is turned off. 

4904896 

I18N search: sort encoding list of Default Encoding on search Admin GUI. 

4905412 

GUI doesn't seem to permit manage users in keyfile database. 

4991338 

Web Server Admin console does not show all the tabs (in Mozilla browser). 

5001819 

Web Server 6.1 Nova Search Engine sometimes misses to pick up document. 

5014693 

Java filters, HTTP compression, and SHTML fail to interoperate. 

5021077 

Encountering java.lang.NullPointerException if you click on OK button without selecting the Directory Server. 

5025617 

Web Server's JNDI needs to map resource-env-ref's from sun-web.xml. 

5042676 

Request flow problem with Client tag code=302. 

5056989 

Enable prefixing of hostname in session ID. 

Note: you can enable prefixing hostname in session ID (as in 6.0SPx) for the web-app by setting the value of the property prefixSessionIDWithHostname under manager-properties to any of the values, yes, true, or on, in the web-app's sun-web.xml.

In the following example, prefixing hostname in session ID is enabled for the web-app by setting the parameter value to true. The sun-web.xml looks like: 


<session-config>
<session-manager>
<manager-properties>
<property name="prefixSessionIDWithHostname" value="true"/>
</manager-properties>
</session-manager>
</session-config>

5057749 

Web Server 6.1 SP2: plug-in defined in certmap.conf does not load. 

6041356 

Memory leak when AdminLanguage and/or DefaultLanguage is specified in magnus.conf. 

6057426 

The load balancer plug-in (formerly Resonate plug-in), loadbal.so, does not work on SPARC Solaris. 

Note that the location of the loadbal.so plug-in is: <server_root>/plugins/loadbal.so

5065017 

Servlet session data problem. 

5048051 

Create collection fails on Linux with RPM install. 

5029954 

StackSize is ignored when ConnQueueSize/RqThrottle is 0. 

4898077 

Inconsistent behavior between HttpServerAdmin and iWS console. 

5013100 

Two ports like 2500 and 02500 are added in server.xml as different ports. 

5046634 

2 byte character in http header and plug-in programs. 

You can enable response header encoding at either at the web-app level by setting the value of the configuration parameter use-responseCT-for-headers to any of the values, yes, true, or on, in the web-app's sun-web.xml. In the following example, response header encoding is enabled for the web-app setting the parameter value to true. The sun-web.xml looks like: 


<sun-web-app> 
<parameter-encoding form-hint-field="j_encoding"/> 
<property name="use-responseCT-for-headers" value="true" /> 
<session-config> 
<session-manager/> 
</session-config> 
<jsp-config/> 
</sun-web-app>