stackoverflow exception on System.Data.Linq.dll

Question

I'm recently working on a asp.net web application. that use linq to sql ORM to data access layer (DAL). In a specific case of my queries faces with stackoverflow exception on clr Level.

i use filter expression generator to get specific data (such as load with specific constrient) that we send more than 1500 parameters to the store procedure.

NOTE: we consider RPC (Remote Procedure Calling) limitation that's exactly 2100 parameters in sql server default setting.

but i don't know why i face with stackoverflow exception? it's interesting to know this problem only occur on iis and no problem in asp.net web development server.

and i'm nearly find out problem that be caused the large number of parameters.

i was grateful from someone that help me?

Exception Detail

 public List<HSEPersonnelComplexPaging> SelectHSEPersonnelPaging(PagingPropertiesDTO pagingProps, out int recCount)
    {
        using (HRPaidTimeOffDataContext db = new HRPaidTimeOffDataContext(DBHelper.GetConnectionString()))
        {
            Expression<Func<HSEPersonnelComplexPaging, bool>> expr =
                PredicateBuilder.GetFilterExpression<HSEPersonnelComplexPaging>(pagingProps);
            db.DeferredLoadingEnabled = false;

            var items = from at in db.HSEPersonnels
                        where at.IsDeleted == false
                        select new HSEPersonnelComplexPaging
                        {
                            ID = at.HSEPersonnelId,
                            PersonnelyNo = at.PersonnelyNo,
                            Name = at.Name,
                            Family = at.Family,
                            BirthPlace = at.BirthPlace,
                            Birthdate = at.Birthdate,
                            Father = at.Father,
                            IdNo = at.IdNo,
                            NationalCode = at.NationalCode,
                            IsNotActive =  at.IsNotActive,
                            IsDeleted = at.IsDeleted,
                            InsertDate = at.InsertDate,
                            UpdateDate = at.UpdateDate,
                            InsertENTUserAccountId = at.InsertENTUserAccountId

                        };
            var result = items.Where(expr);
            recCount = result.Count();
            return
                result.ApplySortExpression(pagingProps.SortSet).Skip(pagingProps.CurrentPageIndex *
                                                                     pagingProps.CurrentPageSize).Take(
                                                                         pagingProps.CurrentPageSize).ToList();
        }

"we send more than 1500 parameters to the store procedure" - oh my. — CodeCaster
– CodeCaster, Commented Jul 23, 2013 at 11:58
@doctorlove to resolve load by paging i exactly need list<T> and record count to telerik radgrid UI. — Reza Nabati
– Reza Nabati, Commented Jul 23, 2013 at 11:59
@CodeCaster ,oh yeah in Linq To Sql we can'nt send table value paramter to query!!! — Reza Nabati
– Reza Nabati, Commented Jul 23, 2013 at 12:01

ErikHeemskerk · Accepted Answer · 2013-07-23 13:39:34Z

1

The problem might lie in the predicate you're building. When you enumerate the expression (which you're doing in the call to Count()), LINQ to SQL will walk down the expression tree to determine what it is you're trying to query. Is it possible that somewhere you're creating a cyclic reference?

answered Jul 23, 2013 at 13:39

ErikHeemskerk

1,71114 silver badges30 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Reza Nabati Over a year ago

yes my expression tree in this case is so long,but there's no way to send table value parameter to the query in Linq To SQL! do you have suggest for me?

ErikHeemskerk Over a year ago

Create a temporary table; store your data in there and reference the temporary table in your LINQ query. Much more robust anyway.

Vladimir Gondarev · Accepted Answer · 2013-07-23 11:53:31Z

1

maybe this is a some kind of explanation: http://support.microsoft.com/kb/932909 All child processes created by IIS have a 256kb stack size

Try this weird thing:

Thread thread = new Thread(() => YourMethod(),4194304);
thread .Start();
thread .Join();

The point is to execute your method in a separate thread that has a bigger stack size..

edited Jul 23, 2013 at 11:53

answered Jul 23, 2013 at 11:46

Vladimir Gondarev

1,2537 silver badges14 bronze badges

2 Comments

ErikHeemskerk Over a year ago

I've never seen the 'limited' stack size be a problem. IMO, if you need to execute code that way, you're doing something wrong.

Vladimir Gondarev Over a year ago

I've never seen it also. This is why I wrote "weird thing".

Collectives™ on Stack Overflow

stackoverflow exception on System.Data.Linq.dll

2 Answers 2

2 Comments

2 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

2 Comments

2 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related