BUG: The IComActivityEvents Interface Causes Infinite Firings Even Without Events and Statistics Enabled on Subscriber (244767)
The information in this article applies to:
This article was previously published under Q244767 SYMPTOMS
When a Subscriber component implements the IComActivityEvents interface, and IComActivityEvents::OnActivityCreate is fired onto the Subscriber, it causes infinite recursive firings and the system is heavily loaded with ActivityCreate and ActivityDestroy calls to the Subscriber.
RESOLUTION
Preventing a new activity for the Subscriber component that implements any of ICom*Events can be accomplished as follows:
- Turn off the Just-in-Time (JIT) Activation property.
- Disable the Synchronization property for the Subscriber component.
STATUSMicrosoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article. MORE INFORMATION
Subscribers to the IComActivityEvents interface should not cause an activity to be created. If the creation of the Subscriber component causes an activity to be created, OnActivityCreate is fired again, and then that one creates the Subscriber, and on and on.
A new activity to the subscriber can be prevented by turning off the JIT Activation property and disabling the Synchronization property for the Subscriber component.
NOTE: This is true for any component that implements any of the ICOM*Events interfaces; such as, IComSecurityEvents, IComInstanceEvents, IComObjectEvents, and so on.
| Modification Type: | Major | Last Reviewed: | 2/21/2002 |
|---|
| Keywords: | kbbug kbCOMPlusLCE kbDSupport KB244767 |
|---|
|