Finding why two UPDATES are send
Finding why two UPDATES are send
- Subject: Finding why two UPDATES are send
- From: Pascal Robert <email@hidden>
- Date: Thu, 22 Apr 2010 11:54:24 -0400
I have a strange problem, but I don't know how to debug it. We have a
store where we contact our billing system (based on SQL Server
2005...) to create a invoice and tell them order that's complete.
Problem is, two UPDATE calls are sent to SQL Server, and the second
one creates problems. The two UPDATE calls are send in a 700ms to
1200ms interval, and no other SQL calls are done.
So the first UPDATE is sent when I do :
commande.setCommandeComplet(Boolean.TRUE);
ec().saveChanges();
That should do only one UPDATE call, and I enabled log4j debugging in
setCommandeComplet to see if something else was updating the
attribute, and it's updated only one time, so I really don't know why
a second UPDATE call is done 700-1200ms later.
What's the best way to debug this?
----
Pascal Robert
email@hidden
AIM: MacTICanada
Twitter : MacTICanada
LinkedIn : http://www.linkedin.com/in/macti
WO Community profile : http://wocommunity.org/page/member?name=probert
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden