The following table lists the known issues in the web container of Web Server.
Table 13 Known Issues in Web Container
Problem ID |
Description |
---|---|
4858178 |
Web container writes to stderr. |
6349517 |
Incorrect web application session statistics for MaxProcs > 1 mode. Web Server runs in multi-process mode. The MaxProcs configuration variable in the magnus.conf is used to set the maximum number of processes. If the value for MaxProcs is set to greater than 1, the Web Server uses mmap-based session manager so that the session could be shared among different JVMs. While collecting statistics from multiple processes, web application MBeans provide session for individual MBeans. There is no way to find the true number of sessions by seeing individual MBean's web application session statistics.
|
6394715 |
Web container deletes the disabled web application MBeans object. When the web application is disabled by setting the <enabled> element to false in the server.xml file, the web container deletes the web application's MBeans and hence treats it as a closed or deleted web application. Since disabled objects are deleted, statistics are also lost. |
6419070 |
No information is logged in error logs at the finest log level on successful JNDI resource creation. |
6422200 |
com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse does 1 byte reads. When reading the server.xml file, the first line containing the XML version number and the encoding is read 1 byte at a time. |
6440064 |
Servlet container creates a thread per virtual server. |
6501184 |
REQ_EXIT causes javax.servlet.ServletException. |