All that I am doing is using Reflection on the IDbConnection to obtain the SAConnection and from there read the ConnectionId property from the underlying SAInternalConnection. There's no (deliberate!) functional change. This is to troubleshoot my actual problem (leaky connections). This posting is not (directly) trying to solve that, I am just interested in why the connections are being spawned.
On Mar 18, 9:32 pm, Fabio Maulo <[email protected]> wrote: > 2009/3/18 Jason Grundy <[email protected]> > > > I am using a custom build of NHibernate > > (a slightly modified 2.0.x) as I want to know ASA's internal > > connection ID (the idea is that I might be able to tie the leaky > > connections with something specific that I am doing in the app). But I > > see a lot of activity after the EndRequest event fires on the > > HTTPApplication. And I don't know why. > > > Can someone explain to me what is going on? > > Do you can explain what you have done in your custom-NH ? > -- > Fabio Maulo --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "nhusers" 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/nhusers?hl=en -~----------~----~----~----~------~----~------~--~---
