David W. Van Couvering wrote:
Thanks to both Brian and Dyre for their tips. The patch for Brian's bug didn't help, but both your emails got me thinking and I discovered I was getting info out of the SQLCA structure earlier than the code used to do, and I think this was incorrectly trying to pull information over the server.
This makes sense. The exception processing in the client/server case is interesting, because the client-side SQLException classes have methods in them which go across the network to fetch server information. For example, calling "getMessage" on a SQL Exception in the client may result in network calls to fetch the correctly-localized text from the server. It generates a call to a system procedure, I believe. There was some conversation about this on the mailing list a few months back because I was investigating a bug in which the getMessage() result is truncated in client/server cases due to a hard limit on the output parameter length in this system procedure. So if you were changing the implementation of the SQL Exception handling, you definitely could have interacted with this code. Glad you resolved it. bryan
