It' happening with me also.old NHibernate version 2.0.1.4000 is working fine with same large data set while latest 5.5.1 version is giving timeout error for same large data set. Could anyone please help on this.
Regards, Raju Kushwaha On Thu, 6 Jun, 2024, 22:16 Haritha Naidu, <[email protected]> wrote: > Hi, > > When we were using NHibernate version 2.0.1.4000 for large data, it was > working well. However, after upgrading to 5.5.1, it is not able to load > larger data. > > On Wednesday, June 5, 2024 at 1:11:57 AM UTC+5:30 [email protected] > wrote: > >> Hi, >> >> What is the context in which you are calling for the data. >> >> Your answer has already been supplied to you. >> >> You are working in STA app and should do this work asynchronously. >> >> Large data blocks = long waiting time. >> >> >> >> *From:* [email protected] <[email protected]> *On Behalf Of *Raju >> Kushwaha >> *Sent:* Sunday, June 2, 2024 5:25 PM >> *To:* nhusers <[email protected]> >> *Subject:* [nhusers] Re: Nhibernate 5.5.1 >> >> >> >> Dear NhibernateUsers, >> >> >> >> I am also getting same errors.Could anyone please help on this.For large >> data, *query.List();* taking alot of time and finally giving >> error like " The CLR has been unable to transition from COM context >> 0xd89ba8 to COM context 0xd89af0 for 60 seconds " but for less data It's >> working fine. >> >> >> >> Regards, >> >> Raju Kushwaha >> >> On Sunday, June 2, 2024 at 3:44:42 PM UTC+5:30 [email protected] wrote: >> >> Managed Debugging Assistant 'ContextSwitchDeadlock' >> Message=Managed Debugging Assistant 'ContextSwitchDeadlock' : 'The CLR >> has been unable to transition from COM context 0xd89ba8 to COM context >> 0xd89af0 for 60 seconds. The thread that owns the destination >> context/apartment is most likely either doing a non pumping wait or >> processing a very long running operation without pumping Windows messages. >> This situation generally has a negative performance impact and may even >> lead to the application becoming non responsive or memory usage >> accumulating continually over time. To avoid this problem, all single >> threaded apartment (STA) threads should use pumping wait primitives (such >> as CoWaitForMultipleHandles) and routinely pump messages during long >> running operations.' >> >> >> >> >> >> I am getting above error at below line >> System.Collections.IList list = query.List(); >> >> >> >> and here IQuery is interface of NHibernate. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "nhusers" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/nhusers/7c705f62-3ee9-4a77-aed7-222ee1334467n%40googlegroups.com >> <https://groups.google.com/d/msgid/nhusers/7c705f62-3ee9-4a77-aed7-222ee1334467n%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- > You received this message because you are subscribed to the Google Groups > "nhusers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/nhusers/8f5ba726-2ad7-4b73-bb15-41d5863e5ea2n%40googlegroups.com > <https://groups.google.com/d/msgid/nhusers/8f5ba726-2ad7-4b73-bb15-41d5863e5ea2n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "nhusers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/nhusers/CAHJv0OawYDSd1ORXOYqo9XFmqGdDHTe_GBAiKSM6-RdBDLs%2B%3DA%40mail.gmail.com.
