Description:
Product Name    : TIBCO iProcess Web Services Server Plug-in (Generic)
Release Version    : 10.5.0-HF07
Release Date    : June 2007
======================================================================
This hotfix corrects the issues listed in the next section. It
includes the issues corrected in HF05 as listed below.

This hotfix applies to the TIBCO iProcess Web Services Server
Plug-in, Version 10.5.0 running on all platforms.
======================================================================
Closed Issues in 10.5.0-HF07

Defect Id: CR 19780

XML over JMS (JMSClient transport) calls wait indefinitely for a
response.

Corrected.  See further information below:

New functionality has been introduced that can be controlled by
setting 4 parameters in the
$JETTY_HOME/staffware/serverconfig.properties file.  
These parameters and their behavior are described below (all times
are in milliseconds):
    
    - ServerEngineConfigMBean.JMSClient.ResponseTimeout
      (Default: 20000)
      This timeout controls how long a WebService response should be
      awaited before dropping into one of the scenarios below.
    
    - ServerEngineConfigMBean.JMSClient.ConsumeTimeout (Default: 500)
      In a scenario where a JMS Message fails to respond in a timely
      fashion (before the responseTimeout), the outgoing message is
      reconsumed in an attempt to keep iProcess Engine and the remote
      system in sync about which calls have been made. This timeout
      controls how long the WebServices Plug-in waits to reconsume
      this message.
    
    - ServerEngineConfigMBean.JMSClient.DeadlockTimeout
      (Default: 240000)
      In a scenario where the outgoing message could not be
      reconsumed, it is assumed that the remote system is working on
      the call but is very slow. This timeout controls how long
      the response is awaited in this scenario.
    
    - ServerEngineConfigMBean.JMSClient.ExpiryTimeout
      (Default: 0, off)
      As an additional failsafe, the outgoing JMS Message can have
      an expiry set on it, which will cause it to be removed from
      the queue if it is not processed by that time.  NOTE: This
      functionality requires that the server running Jetty and the
      JMS Provider have synchronized clocks.  Using this option
      without that could cause undesirable behaviour.

Closed Issues in 10.5.0-HF05

Defect Id: CR 19639.

When using XML over JMS for Web Service calls, the CorrelationID in
the JMS message could be set to match the iProcess unique message key
for the request so that duplicate retried messages can be detected.

======================================================================
The TIBCO iProcess Web Services Server Plug-in (Generic) HotFix 07 can be downloaded from our support-ftp.tibco.com. You will be able to download by clicking on the link below after you provide your TIBCO Support Web username and password in the url:

                     ftp://username:password@support-ftp.tibco.com

Directory path:
StaffwareProcessSuite/iProcess/plugins/WebServices/10.5.0/hotfix-07