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 6.0 SP1 | You are here! | Platform Certification |
| Server 6.0 GA Release | Release Notes| Platform Certification |
Web | [TOP] | ||
Key bug fixes | |||
| Fix For | Description | Server Configuration Impact | Application Configuration Impact |
|---|---|---|---|
Infinite re-direction when accessing a restricted page. |
When a restricted page is accessed without user login, the page is infinitely redirected to a secured location. This has been fixed. |
No Impact. |
No Impact. |
Sending Not-Modified response for deleted content. |
If a request is made on a deleted static resource, a 304 NOT_MODIFIED response is sent. Fixed this to send a 404 NOT_FOUND response. |
No Impact. |
No Impact. |
JSESSIONID is not sent when session is created immediately after invalidation. |
When a request joins an existing session and if the application invalidates the old session and creates a new session, the new JSESSIONID is not sent. This has been fixed. |
No Impact. |
No Impact. |
New Features and Enhancements | |||
| Feature | Description | Server Configuration Impact | Application Configuration Impact |
Improved download speed from Server. |
Using default socket buffer sizes configured by the underlying operating system improves the download speed. |
No Impact. | No Impact. |
Timing Diagnostics for JSF component life-cycle phases. |
Added support for diagnosing time taken for each phase in JSF request processing life cycle. |
Enable PramatiJSFDiagnosticsConfigurationListener listener in default-web.xml. | No Impact. |
EJB | [TOP] | ||
Key Bug Fixes | |||
| Fix for | Description | Server Configuration Impact | Application Configuration Impact |
Sending a javax.jms.ObjectMessage with EJBHandle set within it fails. |
The serialization of EJBHandle over custom I/O streams has been fixed. |
No Impact. |
No Impact. |
Deployment failure when @TransactionAttribute annotation is specified on a callback method of bean class. |
When @TransactionAttribute annotation is placed on a bean callback method, an improper element is added to ejb-jar.xml which fails during schema validation. This has been fixed. |
No Impact. |
No Impact. |
Injecting dependencies into EJB 3.0 Interceptors and their superclasses. |
In the previous releases, dependencies other than javax.ejb.EJBContext and org.omg.corba.ORB were not injected into the EJB interceptors. This has been fixed. |
No Impact. |
No Impact. |
New Features and Enhancements | |||
| Feature | Description | Server Configuration Impact | Application Configuration Impact |
Timing diagnostics for EJB 3.0 session, MDB and JPA Entity bean invocation. |
Added support for diagnosing performance bottlenecks in invocation of EJB 3.0 and JPA components. |
No Impact. | No Impact. |
Added support for timed invocation of EJB 3.0 beans. |
EJB 3.0 Session and Message Driven beans are now exposed for timer notification callbacks. |
No Impact. | No Impact. |
JMS | [TOP] | ||
New Features and Enhancements | |||
| Feature | Description | Server Configuration Impact | Application Configuration Impact |
Added support for configuring client and server socket properties for JMS. |
Client and Server socket properties can be configured using the rmi-properties tag within the jms-config.xml. |
Added optional tag rmi-properties to pramati-jms-service_4_1.dtd. | No Impact. |
Resource | [TOP] | ||
Key Bug Fixes | |||
| Fix for | Description | Server Configuration Impact | Application Configuration Impact |
Allowing multiple JMS resources to be configured for a remote JMS adapter in resource-config.xml. |
A remote JMS Adapter can be configured to have resources that can be looked up locally using InitialContext. In the previous releases, we allowed a single resource to be configured. The configuration has been changed to allow more than one resource. |
Changed pramati-resource-service_4_1.dtd to allow multiple jms-resource tags under jms-adapter. |
No Impact. |
New Features and Enhancements | |||
| Feature | Description | Server Configuration Impact | Application Configuration Impact |
Improved connection pool performance during heavy load. |
Connection pool at heavy load now performs well with better throughput. |
No Impact. |
No Impact. |
Security | [TOP] | ||
Key Bug Fixes | |||
| Fix for | Description | Server Configuration Impact | Application Configuration Impact |
java.lang.SecurityException: access denied (javax.management.MBeanTrustPermission register) while creating JMS Connection. |
When the SecurityManager is set on the Server-side, MBean registration fails. This has been fixed. |
No Impact. |
No Impact. |
Clean shutdown doesn't happen when Server is configured as a Service through the Java Service wrapper. |
This has been fixed. |
No Impact. |
No Impact. |
Clusters | [TOP] | ||
Key Bug Fixes | |||
| Fix for | Description | Server Configuration Impact | Application Configuration Impact |
Exception while stopping JMS cluster from the Admin Console. |
When the AdminService makes subsequent requests to a Server node in the same thread, the Admin Service subject validation fails. This has been fixed. |
No Impact. |
No Impact. |
New Features and Enhancements | |||
| Feature | Description | Server Configuration Impact | Application Configuration Impact |
Added support for configuring client socket properties for cluster communication backbone. |
SO_TIMEOUT and SO_LINGER socket properties are made configurable through cluster-config.xml. Socket timeout value is also configurable through System property com.pramati.cluster.framework.heartbeat and this takes precedence over the value configured through cluster-config.xml. |
Modified pramati-cluster-service_5_0.dtd to take optional socket-properties element with attributes socket-timeout-secs and socket-linger. | No Impact. |
Deploy | [TOP] | ||
Key Bug Fixes | |||
| Fix for | Description | Server Configuration Impact | Application Configuration Impact |
Sharing utility jars across WAR modules within an EAR. |
When an EAR is packaged to have only WAR modules without an EJB jar, utility jars were not able to be shared across the WAR modules. This has been fixed. |
No Impact. |
No Impact. |
NPE while deploying multiple applications within a group. |
When multiple applications are deployed as part of a group, application start-time dependencies are not taken care and this might result in an NPE. This has been fixed. |
No Impact. |
No Impact. |
NPE while opening archive when DeployTool is launched in a separate VM. |
This has been fixed. |
No Impact. |
No Impact. |