Yea, basically beyond what little overhead in terms of the container
being aware of the application (which is minor), the disabled app is
basically an undeployed app. It's more consuming disk resources on the
server than anything else.
The memory footprint of a deployed app is obviously dependent on the
app itself when it's idle. For example things like servlet can be lazy
loaded when they are first accessed, which wouldn't consume anything
until they are actually accessed.
Regards,
Will Hartung
(willh_at_mirthcorp.com)
On Wed, Feb 4, 2015 at 5:07 AM, John Brennan <johndbrennan_at_gmail.com> wrote:
> Quick question. For deploying applications (e.g. simple war file), there is
> an option to make the application disabled. I am wondering does a disabled
> application use less memory and resources than a deployed app which isn’t
> serving requests (i.e. not in use). How do these two states compare? Is a
> disabled application equivalent to an undeployed app from a memory and
> resources/performance point of view?
--
This message, and any documents attached hereto, may contain confidential
or proprietary information intended only for the use of the addressee(s)
named above or may contain information that is legally privileged. If you
are not the intended addressee, or the person responsible for delivering it
to the intended addressee, you are hereby notified that reading,
disseminating, distributing or copying this message is strictly prohibited.
If you have received this message by mistake, please immediately notify us
by replying to the message and delete the original message and any copies
immediately thereafter. Thank you for your cooperation.