Book Image

Microsoft Windows Server AppFabric Cookbook

Book Image

Microsoft Windows Server AppFabric Cookbook

Overview of this book

Windows Server AppFabric provides a set of integrated capabilities that extend IIS and the Windows Server platform making it easier to build, scale and manage composite applications today. Windows Server AppFabric delivers the first wave of innovation within an exciting new middleware paradigm which brings performance, scalability and enhanced management capabilities to the platform for applications built on the .NET Framework using Windows Communication Foundation and Windows Workflow Foundation.'Microsoft Windows Server AppFabric Cookbook' shows you how to get the most from WCF and WF services using Windows Server AppFabric leveraging the capabilities for building composite solutions on the .NET platform. Packed with over 60 task-based and immediately reusable recipes, 'Microsoft Windows Server AppFabric Cookbook' starts by showing you how to set up your development environment to start using Windows Server AppFabric quickly. The book then moves on to provide comprehensive coverage of the most important capabilities provided by Windows Server AppFabric, diving right in to hands-on topics such as deploying WCF and WF applications to Windows Server AppFabric and leveraging the distributed caching, scalable hosting, persistence, monitoring and management capabilities that Windows Server AppFabric has to offer, with recipes covering a full spectrum of complexity from simple to intermediate and advanced.
Table of Contents (16 chapters)
Microsoft Windows Server AppFabric Cookbook
Credits
Foreword
About the Authors
About the Reviewers
www.PacktPub.com
Preface

Troubleshooting throttling


We learned about throttling in the Setting up eviction recipe earlier in this chapter. In this recipe we will identify the root causes of throttling and learn how to fix them.

In the Windows Server AppFabric cache, a cache host may enter a throttled state when the available physical memory becomes so low that it can no longer write data to the cache. A cache host remains in throttled state until more memory is made available.

Whenever a cache host enters a throttled state, cache clients will start receiving DataCacheException errors with ErrorCode = RetryLater and SubStatus = Throttled. To validate that a cache host has entered a throttled state, the following steps should be executed:

  1. 1. Use Get-CacheClusterHealth and see if any cache (host) has entered into a Throttled state.

  2. 2. Use performance counters (as highlighted in the previous recipe) and check for AvailableMBytes (under the Memory group of counters in perfmon.exe) on each cache host and validate if its...