Now that I know where to look I'll look at the code and see how this is being committed.
We do have auto commit on which brings up a good question. Is auto commit dangerous? I have talked to some other coders who say they never use it and I am wondering if we should move towards a more manual committing structure to avoid these kinds of possible problems. The error I pasted in the post is all that showed up in the log for this transaction although I have turned off some of my logging output to try to reduce the size of my logs. Which log should I re-enable to send you the info you need? Is there a way to see what operations are sent with each batch transaction? - Kevin --- In flexcoders@yahoogroups.com, "Jeff Vroom" <[EMAIL PROTECTED]> wrote: > > It sounds like somehow those changes are being split into two different > batches. Do you perhaps have auto-commit on or are you calling commit > in the middle? > > > > There was a bug in 2.5.1 where this error was printed sometimes but I > don't think I've seen a case where it caused any problems. If you have > the server debug log for this case though I'd be glad to try and figure > out why that change is not getting saved in this case. > > > > Jeff > > > > ________________________________ > > From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On > Behalf Of Kevin > Sent: Monday, March 03, 2008 1:18 PM > To: flexcoders@yahoogroups.com > Subject: [flexcoders] LCDS Error?? > > > > Has anyone gotten this error in LCDS before? I can't seem to figure > out what it means and what to do about it. > > [Flex] 03/03/2008 18:59:12.466 [ERROR] [Service.Data.General] Can't > find create message for newly created item with message id: > EB473A3B-AF5D-1E26-7831-7600782E18C5 > > I couldn't find anything in google as well. The error was being > thrown when a user tried to commit a nested object for persistence. > > (Such as a new UserVO which contains a new ContactVO as a property) > > I this case the UserVO persisted correctly and the ContactVO > persisted, but the ContactVO id did not save correctly in the users > table and then the user.contact property was null. > > Any thoughts? - Kevin >
