DERBY-6125 Code cleanup in client driver

Patch derby-6125-visibility-01-b; details

- limits visibility of many classes, methods and fields to what's
  necessary,

- adds final specification to ClobWriter#clob_ and

- removes ClientPooledConnection.getNetXAConnection by inlining its
  content in the one usage location.

git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1465956 13f79535-47bb-0310-9956-ffa450edef68
DERBY-6045 (in list multi-probe by primary key not chosen on tables with >256 rows)

These tests are similar to the ones added by revision 1465830 except that here we use parameters in the WHERE clause to pass the constants and check that we are still using index scan



git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1466097 13f79535-47bb-0310-9956-ffa450edef68
DERBY-6122 -  InterruptResilienceTest fails with: junit.framework.ComparisonFailure: Database shutdown expected:<[08006]> but was:<[XBDA0]> 

The core problem that led to this assert was that an attempt by the
test to shutdown the database timed out with:
Caused by: java.sql.SQLException: Login timeout exceeded. 

The test had set a 10 second timeout assuming that was large enough such that
no timeout would be encountered, but failed a few times in public IBM lab 
nightly regression runs.  Raising the number to 1000.



git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1466225 13f79535-47bb-0310-9956-ffa450edef68
DERBY-6092: IOException when closing LOBFile at end of transaction

A bug in Java 5 may cause IOException if two threads attempt to
close the same RandomAccessFile at the same time.

Avoid this situation by removing the LOBFile from the list of open
files before closing it from LOBStreamControl's finalizer. Then the
cleanup code at the end of the transaction won't find the file and
try to close it if the finalizer is about to close it.

git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1466362 13f79535-47bb-0310-9956-ffa450edef68