BUG: Java Components Hang When Run in Transaction Server

ID: Q180468

The information in this article applies to:

• Microsoft Transaction Server version 2.0
• Microsoft Visual J++, versions 1.1 and 2.0

SYMPTOMS

When accessing a Java component that is running in Microsoft Transaction Server (MTS) from more than one client, the first call will succeed, but all subsequent calls will fail to return. The application stops responding (hangs) until the first client releases its reference.

CAUSE

Microsoft Transaction Server does not properly initialize activity threads for Java components.

RESOLUTION

To resolve this problem, obtain the no charge fix. It is available for download on the Microsoft anonymous ftp server:

   ftp://ftp.microsoft.com/bussys/distapps/MTS/Public-Fixes/usa/JavaFix/ 

STATUS

Microsoft has confirmed this to be a problem in Microsoft Transaction Server version 2.0. A limited release fix is now available, but has not been fully regression- tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Technical Support for more information.

Additional query words: hang hung crash

Keywords          : kbbug2.00 TSrvJava TSrvTransaction 
Version           : WINDOWS:1.1,2.0; WINNT:2.0
Platform          : WINDOWS winnt
Issue type        : kbbug
Solution Type     : kbpending

Last Reviewed: September 5, 1998