This document provides a snapshot of the latest features that have been added to Pramati Server in this release, along with all the enhancements and modifications made to the product.
| Version | Release Notes | Platform Certification |
|---|
| Server 5.0 SP4 | Release Notes | Platform Certification |
| Server 5.0 SP3 | |
| Server 5.0 SP2 | Release Notes | Platform Certification |
| Server 5.0 SP1 | Release Notes | Platform Certification |
| Server 5.0 GA Release | Release Notes | Platform Certification |
Web | [TOP] | ||
Key bug fixes | |||
| Fix For | Description | Server Configuration Impact | Application Configuration Impact |
|---|---|---|---|
Incorrect Web Log entry when content is served from Dynamic Cache. | Whenever content is served from Web Container Cache, content length was set to zero in webLogs, though response has a content-length header with proper value. This has been fixed to show the correct content length. | No Impact. | No Impact. |
Invalid Web Log entry for a 304 (redirect) response. | Whenever Server wrote a 304 response, the status code was being written as zero in weblog. This has been fixed. | No Impact. | No Impact. |
Expires tag issue in set-cookie header. | If max-Age is set to zero for a cookie, EXPIRES tag in the set-cookie header was set to a wrong value, which was not letting the cookie to expire in the browser. This has been fixed. | No Impact. | No Impact. |
Chunking responses with Webgate plugin. | When using WebGate plug-in, chunked responses were getting corrupted. This has been fixed. | No Impact. | No Impact. |
Using Scriplets in standard tag attributes inside a custom tag. | When a customTag includes a standard-tag in its body, which uses scriplets in its attributes, the translator used to give unresolved variable exceptions. This has been fixed. | No Impact. | No Impact. |
EJB | [TOP] | ||
Key Bug Fixes | |||
| Fix for | Description | Server Configuration Impact | Application Behaviour Impact |
Non-transactional bean method invocation. | In case of non-transactional business method invocation, threadlocal cleanup was not being performed, which could lead to issues during the subsequent business method invocations. This has been fixed. | No Impact. | No Impact. |
EJBException wrapped with cause. | EJBException since J2EE 1.4 doesn't print the stacktrace of the cause, especially when there are two levels of nested causes. This has been fixed. | No Impact. | No Impact. |
New Features and Enhancements | |||
| Feature | Description | Server Configuration Impact | Application Configuration Impact |
Deployment time. | Deployment time performance for EJB applications has been improved by avoiding frequent XML parsing during application prepare and start by caching the XML nodes. | No Impact. | No Impact. |
Resource | [TOP] | ||
Key Bug Fixes | |||
| Fix for | Description | Server Configuration Impact | Application Configuration Impact |
Datasource Connection pool leak. | When datasource is looked up from a client VM, the instances are stored in a WeakHashMap. This leads to faster garbage collection of the datasource instances, and a new instance is created on almost every lookup. However, the underlying pools were not getting garbage collected that lead to client-side connection leaks. This has been fixed. | No Impact. | No Impact. |
Server Administration Console | [TOP] | ||
Key Bug Fixes | |||
| Fix for | Description | Server Configuration Impact | Application Configuration Impact |
Objectnames when passed as query parameters were not URL encoded. | Objectnames when passed as query parameters should be URL encoded, otherwise the object that gets passed will be broken at first occurrence of space on the browser. This has been fixed. | No Impact. | No Impact. |
Stop Cluster fails when the username is not root. | While installing Server, if a username is given other than root, stopping the cluster on adminservice failed. This has been fixed. | No Impact. | No Impact. |
Web session persistence back-up node configuration from Admin Console. | Backup nodes are not enabled in the XMl configuration when the Web Session persistence is set to "in memory". This has been fixed. | No Impact. | No Impact. |