By deadlock I mean the system simply hang there, it seems to me that the delete work and add work block each other, the index file is also locked by the system(you can't remove them), if I debug and pause between the two works, the deadlock never happen, and it only occurs in the website randomly, can't repeat it in unit test.
On 12/12/08, Ayende Rahien <[email protected]> wrote: > That shouldn't happen, can you explain what you mean by deadlock? > > On Fri, Dec 12, 2008 at 1:05 AM, Kailuo Wang <[email protected]> wrote: > >> >> In my web project, entity update randomly causes index directory >> deadlock. It only happen with the WorkType.Update, so I tried change >> the work type in the update event listener from WorkType.Update to >> WorkType.Index, and it works fine for me so far. Does this approach >> have any down side? Did anyone experence the same kind of dead lock? >> >> On 5/5/08, Fabio Maulo <[email protected]> wrote: >> > 2008/5/5 Gustavo Ringel <[email protected]>: >> > >> >> You only wrote like 100.000 code and now you abandon it...that's not >> ok... >> >> I expected 1.000.000 at least from you! :) >> >> I'll try to end some of the tests i will bother you in gmail from time >> to >> >> time. >> >> >> > >> > 100.000 in NHC ? not yet. >> > What I would like to see is people working with NH+NHB+NHV and NHSearch >> > (where needed) and NHMA for people Attribute-funs >> > >> > Fabio Maulo >> > >> > > >> > >> >> -- >> Sent from my mobile device >> >> > >> > > > > -- Sent from my mobile device --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "NHibernate Contrib - Development Group" 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.ar/group/nhcdevs?hl=en -~----------~----~----~----~------~----~------~--~---
