.NET hashtable: How to simulate "Load factor too high" exception

Question

Our production repeatedly met "Hashtable insert failed. Load factor too high". 1. How could I simulate this kind of exception? 2. If this sort of exception is thrown, would the existing key/value will disappear?

Thanks for any help.

Do you want to simulate the exception, or the conditions that cause the exception in production? — ProfK, Jan 04 '10 at 05:40

score 2 · Answer 1 · answered Jan 04 '10 at 04:41

2

This contains a relevant explanation: http://blogs.msdn.com/toddca/archive/2007/01/26/hashtable-insert-failed-load-factor-too-high.aspx

answered Jan 04 '10 at 04:41

Woot4Moo

23,987
16
94
151

Why the blog mentioned KB 927579? Isn't it 968432? – Ricky Jan 04 '10 at 06:15
I don't know I didn't write the blog – Woot4Moo Jan 04 '10 at 07:21

Mitch Wheat · Answer 2 · 2010-01-04T04:46:02.603

1

In .NET 2.0, this error is almost always caused by multiple threads modifying the Hashtable at the same time.

There is a HotFix for .NET 3.5

See Hashtable insert failed. Load factor too high and FIX: "InvalidOperationException, Load Factor Too High" When You Use a Hashtable Collection

edited Jan 04 '10 at 04:46

answered Jan 04 '10 at 04:37

Mitch Wheat

295,962
43
465
541

Why the blog mentioned KB 927579? Isn't it 968432? – Ricky Jan 04 '10 at 06:15
Our sys admins indicated 968432 is installed, but the error seemed still existing. – Ricky Jan 04 '10 at 06:18
BTW: we are using .NET 2.0 on Win2003 – Ricky Jan 04 '10 at 06:19

.NET hashtable: How to simulate "Load factor too high" exception

2 Answers2