I've put a try catch around my code that is triggering the issue, the idea
being that when it re-occurs it will log the entity structure and contents
so maybe I can see a pattern. Up until now the pattern I have been able to
identify is not clear since I generally get  different exception stack and
then intermittently am getting the one you report. That's why I think it is
may be to do with the initialisation state or something of something inside
the broker, since as you saw in my code sample sm is being assigned a null
from the broker. What is also interesting is that the same code and same
data often takes a different execution path, I'm trying to work out what
conditions cause this as I suspect the clue is here.

-----Original Message-----
From: Daryl Stultz [mailto:[email protected]] 
Sent: Thursday, 17 September 2009 8:33 AM
To: [email protected]
Subject: Re: SingleFieldManager crash

On Wed, Sep 16, 2009 at 6:44 PM, C N Davies <[email protected]> wrote:

> I know you said that your key is valid, but have you logged the complete
> entity all the way though the cascaded entities?


No, since I can't reproduce it, I'm fairly hamstrung. I'll try to create a
test case as you are describing.

>
> Also I'm not sure you responded to my question regarding the exception
> being
> very intermittent, when I duplicate this issue, in most cases the
exception
> is like this:

 ...


> But under the very same conditions, I am getting the same exception you
> reported. So my suspicion is that you may be in some way handling the
above
> exception,


I don't believe I am, no. I don't have any "try/catch-do alternative action"
stuff.

>
> I don't yet understand why the exceptions are changing even when the same
> code path and data is being processed,


I think the important thing is that sm appears to be null when it should be
not null. So far, I like your thought that the broker is losing the sm for
the object.

-- 
Daryl Stultz
_____________________________________
6 Degrees Software and Consulting, Inc.
http://www.6degrees.com
mailto:[email protected]

Reply via email to