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 20:39:28 -0400
Le 10-04-22 à 20:37, Chuck Hill a écrit :
On Apr 22, 2010, at 5:26 PM, Pascal Robert wrote:
Le 10-04-22 à 16:31, Pascal Robert a écrit :
Le 10-04-22 à 16:02, Chuck Hill a écrit :
Now that I read the comments in Properties...
Try with
er.extensions.ERXAdaptorChannelDelegate.trace.milliSeconds.error=1
That should get you stack traces (assuming the comments are
correct). That _may_ shed some light on things.
No luck, I have put a 100 ms limit, and it doesn't say that it's
taking too long (but it's a damn cool feature!).
Chuck have sent me his SQLLoggingAdaptorChannelDelegate class, and
I'm going to the exact stack trace! So I did the same calls in
Oracle SQL Developer (yes, it can talk to MS SQL Server too) and
when I do the UPDATE call, SQL Dev told me that executeUpdate can't
return a resultset! But if I do the UPDATE a second time, it's ok.
So it's a mix of the vendor DB who is sending something back + EOF
that think the database was down, hence doing the UPDATE
automatically a second time. This is with WO 5.3.3.
Many thanks to Chuck! I guess I own him a couple of Unibroue
bottles, or he can call me Robert for a month.
I will settle for some Le Cheval Blanc and calling you Bobby for two
weeks. :-P
Cool, so I can die, and come back because it was only a dream! _______________________________________________
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