Vic Ricker <[EMAIL PROTECTED]> writes: > Can anyone give me any suggestions on how to debug this issue?
Derby uses exception chaining. The call stack you posted only show the place where an SqlException was caught and transformed to an SQLException which was then thrown. To see the full stack trace you need to do traverse the chain of exceptions using SQLException.getNextException(). With that we should at least be able to tell where in driver the network problem is detected... -- dt
