Ok, but I never accessed a collection in my code. The problem would be inside log4net or inside wrapper log4net of BizTalk.
Dan Essin wrote: > > If you iterate over the members of a collection you cannot do anything > that modifies any of the members, you can only read their properties. If > you need to modify the items you need a for loop. > > Dan Essin > > Drano wrote: >> I am using BizTalk 2006 and the wrapper log4net >> http://www.traceofthought.net/misc/BT2006DeployWithNAntExtraTools_3.0.zip >> >> I don't know if it used MDC, NDC... >> >> Example how I use it: >> >> varLogger = >> log4net.Ext.Serializable.SLogManager.GetLogger(@"BizTalk.Utils",log4net.helpers.CallersTypeName.Name); >> varLogger.RegistryConfigurator(); >> varLogger.InstanceId = >> MyOrchestration.Orchestrations.orcMyOrchestrationType(Microsoft.XLANGs.BaseTypes.InstanceId); >> >> >> nicko wrote: >> >>> Which version of log4net are you using, which framework are you running >>> on? >>> Are you using any of MDC, NDC, GlobalContext, ThreadContext, >>> LogicalThreadContext? >>> >>> Do you have any more stack trace than that, I would like to understand >>> what is serialising the object. >>> >>> Thanks, >>> Nicko >>> >>> >>>> -----Original Message----- >>>> From: Drano [mailto:[EMAIL PROTECTED] >>>> Sent: 19 March 2007 14:18 >>>> To: [email protected] >>>> Subject: Re: InvalidOperation: Collection was modified >>>> >>>> >>>> Exception type: InvalidOperationException >>>> Source: mscorlib >>>> Target Site: Boolean MoveNext() >>>> The following is a stack trace that identifies the location >>>> where the exception occured >>>> >>>> at System.Collections.Hashtable.HashtableEnumerator.MoveNext() >>>> at >>>> log4net.Util.ReadOnlyPropertiesDictionary.GetObjectData(Serial >>>> izationInfo >>>> info, StreamingContext c >>>> >>>> >>>> >>>> Ron Grabowski wrote: >>>> >>>>> Do you have a stack trace for the message? >>>>> >>>>> ----- Original Message ---- >>>>> From: Drano <[EMAIL PROTECTED]> >>>>> To: [email protected] >>>>> Sent: Monday, March 19, 2007 9:08:36 AM >>>>> Subject: InvalidOperation: Collection was modified >>>>> >>>>> >>>>> We are using log4net for several months in production >>>>> >>>> environment. And >>>> >>>>> sometimes we are received a message error "InvalidOperation: >>>>> Collection was modified; enumeration operation may not >>>>> >>>> execute". This >>>> >>>>> message is provided by log4net. Someone knows this problem ? >>>>> >>>>> Thank you >>>>> -- >>>>> View this message in context: >>>>> >>>>> >>>> http://www.nabble.com/InvalidOperation%3A-Collection-was-modified-tf34 >>>> >>>>> 26882.html#a9551617 Sent from the Log4net - Users mailing >>>>> >>>> list archive >>>> >>>>> at Nabble.com. >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>> -- >>>> View this message in context: >>>> http://www.nabble.com/InvalidOperation%3A-Collection-was-modif >>>> ied-tf3426882.html#a9552895 >>>> Sent from the Log4net - Users mailing list archive at Nabble.com. >>>> >>>> >>>> >>> >> >> > > -- View this message in context: http://www.nabble.com/InvalidOperation%3A-Collection-was-modified-tf3426882.html#a9577578 Sent from the Log4net - Users mailing list archive at Nabble.com.
