I've just double checked the changes. The ThreadSafeDictionary looks a bit suspicious. I've removed it and updated the code that used to use it to lock the access to the dictionary. Please give it a try again.
On Tue, Jan 6, 2009 at 4:43 AM, hammett <[email protected]> wrote: > Ok, I will re-review the commit and worst case scenario I'll revert it. > Thanks > > On Tue, Jan 6, 2009 at 4:37 AM, Yuriy Ostapenko <[email protected]> wrote: >> >> Didn't dig too much really, but threads stop executing at different >> points that involve proxied calls. >> I guess they are getting into some deadlock. >> The same method calls can execute 5 times in a row and then get >> blocked, next time it's a completely different method call... no >> system really, >> but probably, since NHibernate uses DynamicProxy more extensively than >> I do with Windsor, it happens mostly inside actual queries, >> so using LingFu for NHibernate helps making those locks occur way less >> often. >> >> If you can point me at what other info might be useful, please do so. >> >> Thanks >> >> On Jan 6, 1:25 pm, hammett <[email protected]> wrote: >>> Please expand on "some really weird locking issues all over the place" >>> >>> >>> >>> On Tue, Jan 6, 2009 at 4:06 AM, Yuriy Ostapenko <[email protected]> wrote: >>> >>> > Hello all, >>> >>> > Today I updated to the latest Castle trunk. >>> > After that my project gone crazy - seems like some really weird >>> > locking issues all over the place. >>> > Please note I use Windsor all over the place and NHibernate uses it as >>> > well (I use it through AR). >>> > Not sure if this issue only occurs within a web context, but this is >>> > 99% sure a fault of this patch. >>> > I tried NHibernate.ByteCode.LingFu and it works way better this way >>> > but threads sometimes still seem to get lost when Windsor proxies are >>> > used. >>> > Then i simply rolled (only) DynamicProxy stuff to rev. 5471 and >>> > everything is ok now. >>> > Has anyone else experienced issues similar to mine and can confirm >>> > this? >>> >>> > Thanks >>> > On Jan 4, 2:52 am, Staxxx <[email protected]> wrote: >>> >> I don't have time to work on this any time soon, but this may be >>> >> helpful???http://weblogs.asp.net/mschwarz/archive/2007/06/05/how-to-create-silv... >>> >>> >> On Sat, Jan 3, 2009 at 5:21 PM, Staxxx <[email protected]> wrote: >>> >>> >> > Yes, that's a good start... It would be Silverlight 2.0, but I'm not >>> >> > sure >>> >> > how to use csc w/ Silverlight (yet). >>> >>> >> > Thanks >>> >>> >> > On Sat, Jan 3, 2009 at 5:08 PM, Jonathon Rossi <[email protected]> >>> >> > wrote: >>> >>> >> >> At work, we're just using MSBuild to build the silverlight projects >>> >> >> files >>> >> >>> etc... How do you want them to build? >>> >>> >> >> Just about all of castle is build with csc. We have net-2.0, net-3.5 >>> >> >> and >>> >> >> mono-1.0 directories in the build output, maybe a silverlight-1.0 >>> >> >> directory >>> >> >> (if this is actually targeting 1.0). The build scripts would also >>> >> >> need to >>> >> >> run the unit tests for the Core and DP2. I can't remember how the >>> >> >> scripts >>> >> >> are written to know how hard it would be to just be able to build >>> >> >> Core and >>> >> >> DP2 when doing a silverlight build. >>> >>> >> >> Is that what you meant by "how do you want them to build"? >>> >>> >> >> -- >>> >> >> Jonathon Rossi >>> >>> -- >>> Cheers, >>> hammetthttp://hammett.castleproject.org/ >> >> >> > > > > -- > Cheers, > hammett > http://hammett.castleproject.org/ > -- Cheers, hammett http://hammett.castleproject.org/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
