Re: Finding why two UPDATES are send
Re: Finding why two UPDATES are send
- Subject: Re: Finding why two UPDATES are send
- From: Pascal Robert <email@hidden>
- Date: Thu, 22 Apr 2010 14:58:17 -0400
Le 10-04-22 à 13:56, Pascal Robert a écrit :
Le 10-04-22 à 13:17, Chuck Hill a écrit :
Wonder?
#########################################################################
# ERXAdaptorChannelDelegate
#########################################################################
## Enable delegate to emit SQL debugging info. The Logger used is
## log4j.category.er.extensions.ERXAdaptorChannelDelegate.sqlLogging
# er.extensions.ERXAdaptorChannelDelegate.enabled=false
## How long a statement must run to cause a log message. Messages
with longer than
## error also emit a stack-trace
# er.extensions.ERXAdaptorChannelDelegate.trace.milliSeconds.debug=0
# er.extensions.ERXAdaptorChannelDelegate.trace.milliSeconds.info=100
#
er.extensions.ERXAdaptorChannelDelegate.trace.milliSeconds.warn=1000
#
er.extensions.ERXAdaptorChannelDelegate.trace.milliSeconds.error=5000
## MaxLength of the message
# er.extensions.ERXAdaptorChannelDelegate.trace.maxLength = 3000
## What entities to watch
# er.extensions.ERXAdaptorChannelDelegate.trace.entityMatchPattern
= .*
Setting
er.extensions.ERXAdaptorChannelDelegate.enabled=true
er.extensions.ERXAdaptorChannelDelegate.trace.milliSeconds.info=1
er.extensions.ERXAdaptorChannelDelegate.trace.entityMatchPattern = .*
Should give you a stack trace of where the second update originates.
Based on the delay, I'd guess a refresh of some sort from the
browser. Check your Ajax usage. Also override dispatchRequest()
in Application and log out the request.uri() so that you can see
the traffic coming in.
Ah yes, the SQL Server calls does happen in a WOLongResponsePage. So
I will check that out.
The two updates runs in the same request (eg, the URI didn't
change) :-/ In fact, they are running in the same transaction.
Chuck
On Apr 22, 2010, at 8:54 AM, Pascal Robert wrote:
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
--
Chuck Hill Senior Consultant / VP Development
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
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
_______________________________________________
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