On Feb 12, 9:10 am, paszczi <[email protected]> wrote: > Hi, I'm using latest builds of Castle (1040). I've come across this > prolbme while releasing object previously resolved from the container: > > Unhandled Exception: System.ApplicationException: The thread does not > have any reader or writer locks. > > Server stack trace: > at System.Threading.ReaderWriterLock.ReleaseReaderLock () [0x00000] > at Castle.MicroKernel.Releasers.AllComponentsReleasePolicy.Release > (System.Object instance) [0x00000] > at Castle.MicroKernel.DefaultKernel.ReleaseComponent (System.Object > instance) [0x00000] > at Castle.Windsor.WindsorContainer.Release (System.Object instance) > [0x00000] > at SecPL.Return.Core.Server.InitializeConfiguration () [0x00000] > > The issue is only present on mono-2.2. Any suggestions?
Temporary solution for this problem is to set: m_container.Kernel.ReleasePolicy = new Castle.MicroKernel.Releasers.NoTrackingReleasePolicy(); But I'm not sure whether it's really elegant solution. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Castle Project Development List" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en -~----------~----~----~----~------~----~------~--~---
