From: "David Van Couvering" <[EMAIL PROTECTED]> > To me, my itch around this item is debugging, I have had to do a lot of > this in the field, and missing something like a unique identifer for a > connection can be pretty serious in terms of time spent trying to track > down a bug, especially if the bug only rears it head in specific > production situations, or it has only happened once but the impact was > severe.
Hi, Just wanted to add that I have had similar problems when debugging code. Recently, I was faced with a problem when in a multi-threaded environment, the system would run fine for a while and then suddenly the threads would start dying with XA errors. I logged Connection.toString() - and using this log was able to step through what was happening to the connections. I found that the problem always occurred if the connection object was used by another thread in a different transaction, where the first transaction association had been ended, but the transaction had not yet reached completion. That is, if I reused a connection after calling XAResurce.end() in a different thread, then it would fail. BTW, this problem was in Oracle, I have not tried to test this situation in Derby. From: "Kathey Marsden" <[EMAIL PROTECTED]> > For more advanced debugging folks tend to use the derby.log and the > ErrorLogVTI, so if this effort is to assist with advanced debugging, > these may be worth considering before connection toString() so that > they can be hooked up in a meaningful way Can this kind of problem can be debugged using derby.log or ErrorLogVTI? Regards
