Hi all, Occassionally we have errors on our live systems with an exception message that reads like the following:
System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> Airtrade.Business.Logging.AirtradeException: GetAPIAccount failed for name=xxx ---> NHibernate.Exceptions.GenericADOException: could not execute query [ query cut for brevity ] Positional parameters: #0>xxx [SQL: query cut for brevity = @p0] ---> System.IndexOutOfRangeException: RelationId6_0_ at System.Data.ProviderBase.FieldNameLookup.GetOrdinal(String fieldName) The query, when taken out of the exception message, always runs just fine, and the exception is not consistent, that is, it only happens occasionally. Searching the net to find a solution to this problem, it looks like we are encountering a connectionPool problem. I was wondering if a patch that was suggested in an earlier post, has made it to the NH3.0 code base / release: http://groups.google.com/group/nhusers/browse_thread/thread/829f0278cf54a40/f8aeaebabb44e7a7?lnk=gst&q=getordinal#f8aeaebabb44e7a7 We have our threading in order (always using a new NHibernate session for subsequent threads/http connections) We are currently running with the NH3.0 release and I am wondering if this connectionpool problem was related to what was mentioned about the 'static methods' in the NHibernate source code, or is this a known ADO.NET problem perhaps? Anybody has any pointers on this? Thanks in advance, Melle -- 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.
