2 connections, either one can throw an exception

Question

In my application I have 2 connections open to the different DBs at the same time. Either operation ( select/update etc ) can throw an exception. I don't want to embrace every SQL statement with the different "try ... catch" block, because it will be too messy. Is there any way to determine what connection threw an exception.
Sample :
try{
Connection conn1 = ...
Connection conn2 = ...
PreparedStatement ps1 = conn1.getPreparedStatement(...);
PreparedStatement ps2 = conn2.getPreparedStatement(...);
ps1.executeQuery(qstring1);
ps2.executeQuery(qstring2);
catch ( SQLException ex){
// Can I put some logic here which will tell me whether the problem related to conn1 or conn2 ?
System.out.println("Exception : " + ex);
}

Answer 1

vs777 wrote:
I have a "global" DB instance where my metadata and instance-specific data resides ( domestice data ). I also have "secondary" DB instance with ( foreign data ) to which I might connect at the run-time if the application logic requires. I am updating metadata Sounds like you want to do "change data capture". If that's the case, I'd recommend looking into your database vendor's capabilities rather than doing this in Java. I'd also look into database links and triggers if your database supports them. Sounds like you're doing something that's best left to the database, not your application. It could be done behind the scenes. It sounds like more of a pure database play rather than business logic.
throughout the application "metadata"? What does that word mean to you? Please explain.
So you're changing the schema dynamically? Metadata means describing the tables and columns. That's changing as the app runs? Sounds confusing.
as well as retrieve and update data in one of the instances depending on conditions, so it's really inconvinient for me to wrap every SQL statement ( execute/select/delete method ) with "try ... catch" block.Inconvenient, but necessary. Somebody has to handle exceptions.
Sounds like you need to think about a way to not repeat code.
I have an application up-and-running for several months already and "2 DB instances" requirement came up just recently, so I am not planning to redesign an application but to handle SQL exceptions properly.So what do you want here? What are you asking if you're not willing to redesign anything?
You're probably not even aware of two phase commit. What happens to your app if the insert of the data succeeds but the metadata does not? Ooops, out of synch. Do you roll back manually? How does the app alert you to the need to do so?
%