Re: Locking of record using SQL in JAVA Websphere application -- JAVA400-L

Subject: Re: Locking of record using SQL in JAVA Websphere application
From: "D*B" <dieter.bender@xxxxxxxxxxxx>
Date: Wed, 10 Oct 2012 14:16:45 +0200
List-archive: <http://archive.midrange.com/java400-l>
List-help: <mailto:java400-l-request@midrange.com?subject=help>
List-id: Java Programming on and around the IBM i <java400-l.midrange.com>
List-post: <mailto:java400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/java400-l>, <mailto:java400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/java400-l>, <mailto:java400-l-request@midrange.com?subject=unsubscribe>

... setTrasnaction is just a guess, maybe the list you're getting has duplicates, maybe from one delivery to the next, or somebody else is inserting records in a non transaction save way...

There is always the possibility, that a SQLException is not thrown, but another SQLState than normal end came up from database; to check this, Connection has a method getWarnings()

con.getWarnings().getSQLState() will bring back the SQLState and the FM will contain the description.

This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.