PRB: Problems Using ASP Intrinsic Objects in Java Components

• Microsoft Active Server Pages, versions 1.0, 1.0b

SYMPTOMS

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.

CAUSE

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.

RESOLUTION

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; 

   } 

STATUS

Microsoft is researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Additional query words:

Keywords          : kbASPObj kbJScript kbGrpASP 
Version           : 
Platform          : winnt 
Issue type        : kbprb 

Last Reviewed: May 27, 1999