Skip to main content

LevelBlue Completes Acquisition of Cybereason.  Learn More

LevelBlue Completes Acquisition of Cybereason.  Learn More

Services
Cyber Advisory
Managed Cloud Security
Data Security
Managed Detection & Response
Email Security
Managed Network Infrastructure Security
Exposure Management
Security Operations Platforms
Incident Readiness & Response
SpiderLabs Threat Intelligence
Solutions
BY TOPIC
Offensive Security
Solutions to maximize your security ROI
Operational Technology
End-to-end OT security
Microsoft Security
Unlock the full power of Microsoft Security
Securing the IoT Landscape
Test, monitor and secure network objects
Why LevelBlue
About Us
Awards and Accolades
LevelBlue SpiderLabs
LevelBlue Security Operations Platforms
Security Colony
Partners
Microsoft Security
Unlock the full power of Microsoft Security
Technology Alliance Partners
Key alliances who align and support our ecosystem of security offerings
Loading...
Loading...

PRB: MailMarshal web components are slow to open the initial page

Expand / Collapse


This article applies to:

  • MailMarshal (SEG) Spam Quarantine Management website
  • MailMarshal ECM/MailMarshal Exchange 7.X Quarantine Management website

Symptoms:

  • The Spam Quarantine Management site is slow to open the initial page. Subsequent pages load quickly.

Comments:

This behavior is not due to MailMarshal SQM settings.

The Spam Quarantine Management (SQM) or Quarantine Management (QM) website is an ASP.NET application running under Microsoft IIS. If the site is not in use by any active session, the application could be unloaded from memory on the webserver. Loading the application can take a number of seconds.

This is a known and intended behavior of Microsoft IIS and ASP.NET.

This issue is more likely to be observed in a test environment or in a small organization where few users are online at a time.

Notes:

In IIS 7 and above you can prevent the application from unloading by setting the Application Pool Idle Time-out to 0. 

In IIS 6 you can set a long idle timeout.

Another option is to create a scheduled script that requests a page from the SQM. Periodic requests for any page will force the application to remain loaded.

Note that the default behavior is designed to free up unused resources, and preventing the unloading will force IIS to use these resources. On a very busy server this could potentially be an issue.

 

This article was previously published as:
NETIQKB43213

To contact LevelBlue about this article or to request support:


Rate this Article:
     
Tags:

Add Your Comments


Comment submission is disabled for anonymous users.
Please send feedback to Trustwave Technical Support or the Webmaster
.