BUG: Java Components Hang When Run in Transaction ServerLast reviewed: March 20, 1998Article ID: Q180468 |
The information in this article applies to:
SYMPTOMSWhen 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.
CAUSEMicrosoft Transaction Server does not properly initialize activity threads for Java components.
RESOLUTIONTo 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/ STATUSMicrosoft 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
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |