Problem with 1.4.2

[Chris Tinsley]

I'm not sure when I can look into this, but we deployed our application
to production with the 1.4.2 NEO release, and the CPU on the DB server
went bonkers.  We rapidly rebuilt the app with the same code but with
the 1.4.1 NEO dll and everything was fine.  Someone on our team is
researching the issue, but we have yet to get to the bottom of it, and I
need to re-allocate the resource to other tasks.  
 
We do have areas in the code where we use Spans to pull in related
entities, and I suspect that it's re-querying for the related entities
one at a time rather than using what's in ObjectContext.  However, I
have no evidence to substantiate that yet, it's only a hunch.
 
One other issue I had with NEO and 2.0 of the .net framework is this:
on the ObjectRelationBase this method is getting called and
e.EntityObject == null, so it throws a NullReference exception.
 
  protected void OnEntityObjectChanged(object sender,
EntityObjectChangeEventArgs e)
  {
   if (e.Action == EntityObjectAction.Change)
   {
    if(foreignTableName == e.EntityObject.Row.Table.TableName)
    {
     int index = innerList.IndexOf(e.EntityObject);
     if(index > -1)
      OnListChanged(new
ListChangedEventArgs(ListChangedType.ItemChanged, index ));
    }
   }
  }
 
 
 We have some entities that we watch for changes on, so that's why this
is getting called, but I haven't tracked down why the EntityObject is
null.  Something must have changed in the events for the ADO.Net
DataTable.  As a short term fix, I just put a null reference check at
the first if statement so it looks like this:

  protected void OnEntityObjectChanged(object sender,
EntityObjectChangeEventArgs e)
  {
   if (e.EntityObject != null && e.Action == EntityObjectAction.Change)
   {
    if(foreignTableName == e.EntityObject.Row.Table.TableName)
    {
     int index = innerList.IndexOf(e.EntityObject);
     if(index > -1)
      OnListChanged(new
ListChangedEventArgs(ListChangedType.ItemChanged, index ));
    }
   }
  }

I apologize for only providing errors and no fixes, but I'm hoping that
someone with some more free time can track down the underlying cause :-(

Chris Tinsley

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

[Erik Dörnenburg]

Chris Tinsley wrote:

> I'm not sure when I can look into this, but we deployed our application
> to production with the 1.4.2 NEO release, and the CPU on the DB server
> went bonkers.  We rapidly rebuilt the app with the same code but with
> the 1.4.1 NEO dll and everything was fine.  Someone on our team is
> researching the issue, but we have yet to get to the bottom of it, and I
> need to re-allocate the resource to other tasks.  
>  
> We do have areas in the code where we use Spans to pull in related
> entities, and I suspect that it's re-querying for the related entities
> one at a time rather than using what's in ObjectContext.  However, I
> have no evidence to substantiate that yet, it's only a hunch.

This is really strange because the only change between Neo 1.4.1 and
1.4.2 is a fix in the installer to properly register the VisualStudio
plugin with COM. The change is in the installer project and only affects
the installation of the plugin. The actual run-time code should be
identical.

erik



---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

[Chris Tinsley]

Erik,
I stand corrected.  We were using 1.4.0.  We never did the 1.4.1
upgrade.  So that means it was something added between 1.4.0 and 1.4.1.

Chris



-----Original Message-----
From: Erik Doernenburg [mailto:erik@...]
Sent: Wednesday, June 21, 2006 7:18 PM
To: user@...
Subject: Re: [neo-user] Problem with 1.4.2

Chris Tinsley wrote:
> I'm not sure when I can look into this, but we deployed our
> application to production with the 1.4.2 NEO release, and the CPU on
> the DB server went bonkers.  We rapidly rebuilt the app with the same
> code but with the 1.4.1 NEO dll and everything was fine.  Someone on
> our team is researching the issue, but we have yet to get to the
> bottom of it, and I need to re-allocate the resource to other tasks.
>  
> We do have areas in the code where we use Spans to pull in related
> entities, and I suspect that it's re-querying for the related entities

> one at a time rather than using what's in ObjectContext.  However, I
> have no evidence to substantiate that yet, it's only a hunch.
This is really strange because the only change between Neo 1.4.1 and
1.4.2 is a fix in the installer to properly register the VisualStudio
plugin with COM. The change is in the installer project and only affects
the installation of the plugin. The actual run-time code should be
identical.

erik



---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email


---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email