Release Notes for Pramati Server 5.0 SP4

Incorrect webLog entry in the Load Balancer for some error responses.

In case of requests from Load Balancer to back end nodes, if the response code was one among 503, 404, or 500, web log entries in the Load Balancer showed invalid values for content-length and status code. This has been fixed.

No Impact.

No Impact.

Web Session replication does not work in cluster.

This has now been fixed.

No Impact.

No Impact.

Range requests with range starting at byte 0 fails.

When a request was made with range as 0-<somelength>, the earlier versions of Pramati Server used to fail by responding with a zero content. This has been fixed.

No Impact.

No Impact.

Sometimes duplicate entries are returned from javax.servlet.ServletRequest getParamaterValues().

request.getParamaterValues() used to return duplicate entries if request encoding was changed. This has been fixed.

No Impact.

No Impact.

request.getLocalPort() always returns 0.

request.getLocalPort() now returns the correct value.

No Impact.

No Impact.

Http Sessions expire even when session time out is set to -1.

Session should not expire if the session timeout is defined as -1 in web.xml. In earlier versions of Pramati Server, the default value of session timeout was 30 mins (thus, the sessions expired after 30 mins). This has been fixed and the sessions do not expire if timeout is -1.

Sessions with timeout -1 do not expire by default. But for old applications, which expect the session to be invalidated after 30 mins, a system property com.pramati.web.session.defaultInfiniteTimeOutMins is provided (which is used if timeout is -1). The time out value should be given in minutes.

No Impact.

Incorrect cookie expires date format.

The date format of the expiry date is EEE, dd-MMM-yyyy HH:mm:ss z in accordance with RFC 2109 (Cookie specification).

Auto Rollback of uncommitted transactions at the end of service method.

If a UserTransaction is not committed at the end of the service method, the transaction is automatically rolled back. An exception is logged in the log files. If the response is not already committed, an error page is sent to the browser.

The new system property com.pramati.web.tx.rollback.leniency allows the transaction to exist until the requestDestroyed() event on javax.servlet.ServletRequestListener has been invoked. In this case, the transaction is rolledback after this event is dispatched and after the response has been committed.

No Impact.

Configuration to enable/disable particular ciphers.

Added configuration to enable/disable SSL cipher-suites and protocols. This configuration can be used by system administrators to disable old/weak ciphers/protocols.

In case of network disruption, JMS connections to IBM MQ server stop working.

This has now been fixed.

No Impact.

No Impact.

New BMP Locking Options.

Support is now provided for more fine tuned options for locking and caching of BMP Entity beans. BMP Locking and caching can be configured at three levels:

• Default BMP behaviour: The Container locks the entity bean instances within a transaction. As long as the entity is available in the cache, the ejbLoad() callback is never invoked.
• Pre50 behaviour: The Container locks the entity bean instances participating in a transaction and the ejbLoad() callback is given at the beginning of every transaction.
• No Lock BMP behaviour: Entity bean instances are not locked at the Container level and the ejbLoad() callback is given at the beginning of every transaction.

Too many "invalid subject" messages in logs.

This has now been fixed.

No Impact.

No Impact.

Added support for load balancing and high availability of web service requests.

Due to this support, when a web service is deployed now, the WSDL being published will have the updated endpoint address that can point to the load balancer host and port.

Tools for Web Service Artifact generation.

The JAX-RPC tools for web services artifact generation, wsdl2java.bat and java2wsdl.bat, have been packaged along with the server. The tools can be found at $server_home/bin directory.

Rotation of stdOut and stdErr streams.

When Pramati Server is started with -redirect option, System.err and System.out streams are redirected to stdOut.log and stdErr.log files. With this release, these streams are redirected to files that are rotated and compressed like the server activity logs.

Added support for specifying login information through config-topology.xml file for Node Creator.

Node creator's config topology file for both standalone and cluster nodes takes admin user, password, and realm properties. When the node is created with the specified login details, an admin user is created within the security realm and the same details are updated to server-config.xml.