Carey Brown wrote:Might be helpful if we knew what the error was.
Dave Tolls wrote:It's the first line of the stack trace:
[6/23/20 9:48:34:833 CDT] 0000008c SystemErr R com.ibm.websphere.ce.cm.DuplicateKeyException: [SQL0803] Duplicate key value specified.
Two things to check.
First, is the DuplicateKeyException you are catching the same as the one being thrown? (I've made that mistake with other exceptions before which had matching names).
Second, is this code actually the deployed code?
Finally, you have a catch clause for Exception in that code, do those println statements appear in the logs? If so, then this really isn't the code being executed.
Steve Dyke wrote:
To the best of my knowledge it is the correct DuplicateKeyException. Yes it is deployed. And no the println do not appear.
Campbell Ritchie wrote:Why are you using exceptions for what should be normal control of program flow? Why have you got the empty catch in line 8?
Stephan van Hulst wrote:
Your query is extremely vulnerable to SQL injection attacks by the way. Why did you ignore our previous advice to handle this issue?
There are 29 Knuts in one Sickle, and 17 Sickles make up a Galleon. 42 tiny ads in a knut:
Devious Experiments for a Truly Passive Greenhouse!https://www.kickstarter.com/projects/paulwheaton/greenhouse-1