Thank you very much for your answer. It is the first time that someone help me as you in a forum !!!!
Nicko Cadell wrote: > > Looking at the source to the > BT2006DeployWithNAntExtraTools_3.0\log4net.Ext.Serializable library I > see that the SLog.InstanceId property you are using is marked as > obsolete with the following message: "This member was discovered to not > be threadsafe. Use the PropertiesCollectionEx class and associated > overrides for Info/Log/Warn/Debug instead." > > Can you try not using the SLog.InstanceId and Slog.Properties. > > Cheers, > Nicko > >> -----Original Message----- >> From: Drano [mailto:[EMAIL PROTECTED] >> Sent: 20 March 2007 13:35 >> To: [email protected] >> Subject: RE: InvalidOperation: Collection was modified >> >> >> I am using BizTalk 2006 and the wrapper log4net >> http://www.traceofthought.net/misc/BT2006DeployWithNAntExtraTo >> ols_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(Microsof >> t.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-modif >> ied-tf3426882.html#a9572539 >> 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#a9589661 Sent from the Log4net - Users mailing list archive at Nabble.com.
