|
dev
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
.Net 2.0 Hashtable Insert Failed. Load factor too highHi,
I am currently getting System.InvalidOperationException: Hashtable insert failed. Load factor too high error. I noticed that this only seems to happen, when we are trying to do run a Stress Tool with a few users(5-10). I know this is a known issue in .net 1.1, but there seems to be no report of this in .net 2.0. Has anyone experienced this issue before? Many thanks for the reply. Regards Ranga. We also appear to be having this problem under .net 2.0 when we serialize an
object that contains a (large) hashtable: (InvalidOperationException) Hashtable insert failed. Load factor too high. - at System.Collections.Hashtable.Insert(Object key, Object nvalue, Boolean add) - at System.Collections.Hashtable.set_Item(Object key, Object value) - at System.Runtime.Serialization.SerializationEventsCache.GetSerializationEventsForType(Type t) - at System.Runtime.Serialization.SerializationObjectManager.RegisterObject(Object obj) - at System.Runtime.Serialization.Formatters.Binary.WriteObjectInfo.InitSerialize(Object obj, ISurrogateSelector surrogateSelector, StreamingContext context, SerObjectInfoInit serObjectInfoInit, IFormatterConverter converter, ObjectWriter objectWriter) - at System.Runtime.Serialization.Formatters.Binary.WriteObjectInfo.Serialize(Object obj, ISurrogateSelector surrogateSelector, StreamingContext context, SerObjectInfoInit serObjectInfoInit, IFormatterConverter converter, ObjectWriter objectWriter) - at System.Runtime.Serialization.Formatters.Binary.ObjectWriter.Serialize(Object graph, Header[] inHeaders, __BinaryWriter serWriter, Boolean fCheck) - at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Serialize(Stream serializationStream, Object graph, Header[] headers, Boolean fCheck) Any insight would be appreciated! Thanks! Mike Show quote "Ranga" wrote: > Hi, > > I am currently getting System.InvalidOperationException: Hashtable insert > failed. Load factor too high error. I noticed that this only seems to > happen, when we are trying to do run a Stress Tool with a few users(5-10). > I know this is a known issue in .net 1.1, but there seems to be no report of > this in .net 2.0. > > Has anyone experienced this issue before? Many thanks for the reply. > > Regards > > Ranga. > |
|||||||||||||||||||||||