Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 182890 - Last Review: March 16, 2005 - Revision: 3.3
PRB: Problems Using ASP Intrinsic Objects in Java Components
This article was previously published under Q182890
When overriding OnStartPage and OnEndPage in Active Server Pages (ASP)
components written in Java, you may encounter problems when using ASP
intrinsic object interfaces. In particular, if your component stores
references to the intrinsic objects in the Java class, the Inetinfo process
may stop after the call to OnEndPage if more than one copy of your
component is currently in use.
This problem is caused by a combination of the way ASP manipulates its
intrinsic objects and of the way the Virtual Machine for Java cleans up
references to COM interfaces. After OnEndPage is called, ASP assumes it is
safe to remove the intrinsic objects such as the Session object. Because of
the way Java's garbage collection routines work, it is possible that the
Virtual Machine for Java will attempt to release the interface after ASP
has already removed it. Such an attempt will cause a GP Fault that can stop
the Inetinfo process.
In order to avoid this problem, you should use the ComLib.release() to
force the Virtual Machine for Java to do an immediate release on the
intrinsic object interface pointers you are using. This prevents the delay
that is typically present when garbage collection is used to release the
interfaces.
Here's an example:
import com.ms.com.*;
. . .
. . .
public void OnEndPage( ) {
//Force immediate release of the Response interface member
ComLib.release(my_response);
my_response = null;
}
APPLIES TO
- Microsoft Active Server Pages 1.0
- Microsoft Internet Information Server 4.0
- Microsoft Internet Information Services 5.0
| kbaspobj kbjava kbprb KB182890 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate
Be the first to leave feedback, to help others about this knowledge base
article.
(Optional) Name
(Optional)
Public URL Or Email
Comments
No
HTML -- Text Only Please