Re: Virtual Application - Out of memory errors

From: Alvaro Lozano (alozano_at_st.com.uy)
Date: 03/25/05 

Date: Fri, 25 Mar 2005 20:53:48 -0300

If the interface is forwarded, com+ wont complain but it will throw this
error sometimes (recompile without compatibility, and reinstall the
component) , also check for the unattended execution and retain in memory
project's properties

"Ken" <Ken@discussions.microsoft.com> wrote in message
news:8E652086-FD1B-494E-A0A2-7E23B6EDB2B4@microsoft.com...
> I should clarify my first post. The applications work for six day, and
> process many requests without incident. Then, all of the sudden they start
> throwing out of memory errors, right when trying to instantiate the
object.
>
> "Alvaro Lozano" wrote:
>
> > have you recently change the component?, some times vb doesn't break
the
> > binary compatibility, and compile with a forward interface, and that
have
> > some problems with com+. Try to recompile without binary compatibility
(be
> > careful with early binding).
> >
> > "Ken" <Ken@discussions.microsoft.com> wrote in message
> > news:C1AA2F64-3955-4578-9B87-9BBF1155689C@microsoft.com...
> > > We've recently started having a problem on our production web servers.
The
> > > servers are W2000 sp4 running IIS 5. The applications are highly
isolated.
> > We
> > > have a very lightweight VB component that performs authorization. The
> > > component is hosted in COM+, as a library application. What we're
seeing
> > > periodically is an error message "Ran out of memory". The error is
thrown
> > > when the authorization component is instantiated. The servers are
2.5GB
> > > machines, and at the time of the errors, we have 1GB of physical
memory
> > > available, so I'm not certain that the error message is accurate, and
> > > something else may be causing the problem. The application is not
> > accessable
> > > once this starts, although the web service is not affected, and other
> > > applications continue to work. What tools are available to diagnose
> > symptoms
> > > like this??
> >
> >
> >

Relevant Pages

  • Re: [PATCH v2 2/4] KVM: introduce "xinterface" API for external interaction with guests
    ... and we're better off with slots and virtual memory. ... interface, though admittedly it will probably cover most cases. ... This just assumes a low context switch rate. ...
    (Linux-Kernel)
  • Re: [PATCH RFC] hotplug-memory: refactor online_pages to separate zone growth from page onlining
    ... just throw this interface away or completely disable it. ... I had no intention of globally disabling it. ... to user level for preparing memory add event. ... and gives it to the host. ...
    (Linux-Kernel)
  • Re: CFFA for IIc and IIc+?
    ... RAMWorks interface, without any impact on slot addresses at all. ... At this point I am guessing that the earlier memory interfaces for the //c were based on that RAMWorks style interface? ... Apple never built a RAMWorks-style memory card. ... widely available expansion AUX memory design for the //e. ...
    (comp.sys.apple2)
  • NUMA API
    ... ~ no inclusion of SMT/multicore in the cpu hierarchy ... ~ awkward memory allocation interface ... ~ a completely unacceptable library interface (e.g., ... Interleaved allocation is a property of a specific ...
    (Linux-Kernel)
  • Re: [PATCH RFC] hotplug-memory: refactor online_pages to separate zone growth from page onlining
    ... just throw this interface away or completely disable it. ... I had no intention of globally disabling it. ... But in the xen-balloon case, the memory is added on-demand precisely when its about to be used, and then onlined in pieces as needed. ... For the current balloon driver, ...
    (Linux-Kernel)
Quantcast