| To: | users@xxxxxxxxxx |
|---|---|
| Subject: | Re: [cinjug-users] Request for help: Intermittent bug in Struts app |
| From: | Troy Davis <troy@xxxxxxxxxxxxxxxxxx> |
| Date: | Wed, 29 Dec 2004 17:13:24 -0500 |
| Delivered-to: | mailing list users@cinjug.org |
| In-reply-to: | <20041229205842.88977.qmail@web50104.mail.yahoo.com> |
| Mailing-list: | contact users-help@cinjug.org; run by ezmlm |
| References: | <20041229205842.88977.qmail@web50104.mail.yahoo.com> |
|
Thank you for replying, but there's no evidence of any other statements
failing, just the insertion of the article order data. I also turned on
query logging on the server and inspected the logs the last three times
this happened, there was no insert statements for the order data after
each bug report. However, there were plenty of similar transactions
before and after that happened successfully, including the insertion of
ordering data. The other thing that confuses me is that it's not reproducible. It happens much less often than 1 in 10 times, probably 1 in 50 or 1 in 100. Thank You, Troy On Dec 29, 2004, at 3:58 PM, Jason Kretzer wrote: Have you tried executing a 'Commit' to the database before and after the insert? I know DB2 has this problem even when autocommit is set to true. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Terri Connor is out of the office., Terri_Connor |
|---|---|
| Next by Date: | Re: [cinjug-users] Request for help: Intermittent bug in Struts app, Farhan Shah |
| Previous by Thread: | Re: [cinjug-users] Request for help: Intermittent bug in Struts app, Jason Kretzer |
| Next by Thread: | Re: [cinjug-users] Request for help: Intermittent bug in Struts app, Farhan Shah |
| Indexes: | [Date] [Thread] [Top] [All Lists] |