Release Notes for Pramati Server 6.0 SP4

Server crashes on 64-bit hotspot JVM while serving web requests.

The crash is reported during hotspot compilation of method DefaultHttpHeader._parseRequestUri, as part of the request processing. As a workaround, this method was excluded from hotspot compilation in the previous releases. This can be avoided from this release.

In case if the fix doesn't work, the above method can still be excluded from hotspot compilation through the java VM option -XX:CompileCommand=exclude,
com/pramati/web/servlet/core/
DefaultHttpHeader,_parseRequestUri.

No Impact.

Partial content for Range requests in IE6.

In IE6 Range header is sent with spaces in between the range values, due to which some of the ranges are ignored. Fixed this.

No Impact.

No Impact.

Partial response when static content is included with If-Modified-Since header in the request.

When client sends If-Modified-Since header as part of the request, the header should not be applied for included static page requests. The included static page content must always be written to the response.

No Impact.

No Impact.

For tags with scriplets, compilation sometime fails with message, Compilation Error: code too large.

Due to restriction on the maximum method size in Java, code generated for jsps with too many child tags fails to compile. Fixed this by breaking the generated code into different methods for the child tags.

System property com.pramati.jsp.tags.codegen.
enableFunctionBasedForChildTags should be enabled to avoid this problem.

No Impact.

HTTP OPTIONS method does not work.

Fixed HttpServletRequest.getMethod() to return OPTIONS instead of OPTION.

No Impact.

No Impact.

Improved acknowledgement processing and flow control for JMS client in the event of connectivity failures.

In the previous releases, connection failure to JMS Server or Persistence store used to stall message processing, requiring a re-start of JMS client VM. The client side flow control mechanism has now been improved to automatically resume processing, after restoring the connection back.

Introduced Server System properties com.pramati.jms.failedack.retryinterval for configuring the retry interval, default: 60 seconds and com.pramati.jms.failedack.maxretries for retry attempts default: 20.

No Impact.

Message loss during heavy load when the same connection is used to receive messages from Queues and Topics.

When the same JMS connection is shared by both Queues and Topics, messages for Topic consumers might get lost when there is heavy load on Queues.

No Impact.

No Impact.

EOFException in HP-UX sometimes on closing a started JMS connection.

This has been fixed.

No Impact.

No Impact.

New policy option introduced for Queues to forward messages to a configured user Queue as a re-delivery limit overflow policy.

In the previous releases, messages were either discarded or added to Dead Message Queue (DMQ) on reaching the re-delivery limit at a Queue. Allowing the messages to be forwarded to a user Queue in this release, enables applications to handle re-delivery failures, by registering failure handler MDBs or asynchronous listeners to the Queue.

Configuration snippet:

   <queue>
      <name>JMSQueue</name>
      <redelivery-delay-millis>
            500
      </redelivery-delay-millis>
      <redelivery-limit-overflow-policy>
            move-to-exception-destination
      </redelivery-limit-overflow-policy>
      <exception-destination>
            MyExceptionQueue
      </exception-destination>
   </queue>

redelivery-limit-overflow-policy should be configured to move-to-exception-destination and exception-destination element has to be added specifying the custom destination.

A default exception-destination can also be provided under default-destination-properties element.

No Impact.

Deployment process can now take HTTP and FTP urls.

With the help of the URL protocol handler, any URL can be used for deployment. This support can be extended to deploy archives from Storage services like Amazon S3, using their custom protocol. URL protocol handler classes can be added using the Extension classloading mechanism.

System property com.pramati.url.protocol.extensions takes a comma separated list of protocol names that are allowed to be plugged-in using the handler mechanism.

No Impact.

Datasource's first getConnection() fails for Oracle DataDirect XA driver with message, Pooled connection reclaimation not supported.

This has been fixed.

No Impact.

No Impact.

Improved datasource getConnection() performance when there are failed datasource instances in a clustered datasource.

This has been fixed.

No Impact.

No Impact.

Applications can now perform job scheduling within Servlet and EJBs with the help of Scheduled Executors.

One time or periodic tasks can be submitted from within JEE components with support for application context propagation, thread management and execution statistics. The functionality is compliant with the proposed JSR-236 & JSR-237.

Scheduled thread pool executor instances can be created through resource shell. Scheduled Executor instances can be looked up using JNDI or injected with the @Resource annotation.

The existing command create_managed_executor prompts for a new Scheduled option, which can be set to true to create a Scheduled Executor. Configuration for Executor resources is modified to take scheduled option in resource-config.xml.

@Resource annotation can be specified for resource type com.pramati.services.admin.spi.ManagedScheduledExecutorService or java.util.concurrent.ScheduledThreadPoolExecutor within a EJB or Servlet to request the containers for injecting Executor.

An alternative to java.util.concurrent.Executors for applications to create Executors with better thread management and statistics.

Applications can now create managed executor instances with API com.pramati.services.admin.executor.
ManagedExecutors whose lifetime is same as that of application. Executor instances have support for application context propagation, thread death handling, MBean registration, thread execution dump, usage and timing statistics.

Base shell command status resource is enhanced to provide status for Application created executor instances.

Applications should use the API com.pramati.services.admin.executor.ManagedExecutors for creating Executor instances.

LDAP realm authentication fails with Active Directory when the Common Name(CN) contains forward slashes.

Active Directory adds Quotes to Common Name(CN), if it has forward slashes, due to which the CN comparisons fail. Fixed this.

No Impact.

No Impact.

Log file rotation on daily basis.

Web logs, Server text message and Server xml logs can be configured to rotate at 12:01AM everyday.

Configuration option ByEveryDayAndFileSize for the rotation-type element in logging-config.xml enables this feature.

No Impact.