Article ID: 891564
Article Last Modified on 12/4/2007
APPLIES TO
- Microsoft Host Integration Server 2004 Standard Edition
- Microsoft Host Integration Server 2000 Standard Edition
Note The behavior that this article describes applies to Transaction Integrator (TI) in Microsoft Host Integration Server 2004 and to COM Transaction Integrator for CICS and IMS (COMTI) in Microsoft Host Integration Server 2000. Transaction Integrator (TI) it used throughout the article to indicate both TI and COMTI except where an explicit difference between the two versions exists.
SYMPTOMS
Transaction Integrator transactions that communicate over TCP/IP may not time-out in the time-out period that is configured in the TI Remote Environment (RE). A TI transaction may not time-out unless the time that is required for the host application to respond is more than double the time-out value that is configured in the RE. Therefore, TI transactions may not time out as quickly as you want.
For example, if you have specified a time-out value of 4 seconds, a transaction may not time out unless the host application does not respond for longer than 9.5 seconds.
Note To configure the TI time-out in Host Integration Server 2004, enter a value in the Receive box under the Time out in seconds option in the RE properties.
To configure the COMTI time-out in Host Integration Server 2000, enable the Timeout if no response within value
seconds option.
When a TI transaction is eventually timed out, a message that is similar to the following is logged in the event log:
CAUSE
TI calls the recv function by using the MSG_PEEK flag to gather response time values. TI uses these values to monitor performance. As soon as the first recv function call is completed, TI issues another recv function without using the MSG_PEEK flag. This call enables TI to receive the actual data that the host application is returning.
If the first recv function call fails because the host application did not respond before the configured time-out expires, TI does not report a time-out exception (error 1434). However, if the second recv function call fails because the configured time-out has expired, TI returns the time-out exception. This behavior causes an effective TI time-out that is more than double the configured time-out.
RESOLUTION
After you apply the following hotfix, TI will return the time-out exception if the first recv function call that uses the MSG_PEEK flag fails because the configured time-out has expired. This behavior enables the TI transaction to detect time-out conditions in the time that you have specified in the RE properties.
Host Integration Server 2004
Hotfix information
A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.
To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:
Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:
File information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date Time Version Size File name --------------------------------------------------- 07-Jan-2005 23:26 6.0.1925.0 85,504 Trantcp.dll
Note Because of file dependencies, the most recent hotfix that contains these files may contain additional files.
Host Integration Server 2000
Hotfix information
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Host Integration Server 2000 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
File information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date Time Version Size File name ----------------------------------------------------- 22-Apr-2005 01:23 5.0.0.2061 323,856 Cedrmsgs.dll 22-Apr-2005 01:23 5.0.0.2061 311,568 Mobase.dll 22-Apr-2005 01:23 5.0.0.2061 119,056 Tagen.dll 22-Apr-2005 01:23 5.0.0.2061 82,192 Tranlu62.dll 22-Apr-2005 01:23 5.0.0.2061 114,960 Trantcp.dll
Note Because of file dependencies, the most recent hotfix that contains these files may contain additional files.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
MORE INFORMATION
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Additional query words: HIS2000 HIS2004
Keywords: kbbug kbfix kbhostintegserv2000 kbqfe kbpubtypekc kbhotfixserver kbhis2004 KB891564