db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Van Couvering (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-243) connection toString should uniquely identify the connection
Date Wed, 08 Jun 2005 04:30:47 GMT
     [ http://issues.apache.org/jira/browse/DERBY-243?page=all ]

David Van Couvering updated DERBY-243:

    Attachment: DERBY-243.diff

Updated patch for this issue.  Here is a summary of what I changed.  A lot of what I did was
remove code I had put in, 
so I think you'll see a much simpler patch.

- Reverted back to using a simple integer for the GenericLanguageConnectionContext id
- All trace and log statements and the ErrorLogReader VTI go back to using the simple integer
- EmbedConnection uses the LCC ID as its toString value
- BrokeredConnection continues to use the underlying physical connection's toString value
for it's toString value
- EmbedPooledConnection now uses a simple integer instead of a UUID
- Reworked the tests to open 10 connections and make sure they are all unique.  It does this
for a DriverManager
  connection, a connection from a DataSource, a PooledConnection from a ConnectionPoolDataSource
and an
  XAConnection from an XADataSource.  It also ensures connections obtained from the same PooledConnection
  have the same toString() value
- I no longer print out the toString() value in the test.
- I modified lang/miscerrors.sql to select from the ErrorLogReader VTI so we can validate
that this output is

Ran derbyall, everything passed except for a strange error in encryptionAll/multi/stress which
appears completely
unrelated.  Every now and then my stress tests fail for reasons I don't fully fathom.  Should
I be investigating these
or is this a known issue?

Here is the output of svn status:

M      java/engine/org/apache/derby/impl/jdbc/EmbedConnection.java
M      java/engine/org/apache/derby/iapi/jdbc/BrokeredConnection.java
M      java/engine/org/apache/derby/jdbc/EmbedPooledConnection.java
M      java/testing/org/apache/derbyTesting/functionTests/tests/lang/miscerrors.sql
M      java/testing/org/apache/derbyTesting/functionTests/tests/jdbcapi/checkDataSource.java
M      java/testing/org/apache/derbyTesting/functionTests/tests/jdbcapi/checkDataSource30.java
M      java/testing/org/apache/derbyTesting/functionTests/master/miscerrors.out

> connection toString should uniquely identify the connection
> -----------------------------------------------------------
>          Key: DERBY-243
>          URL: http://issues.apache.org/jira/browse/DERBY-243
>      Project: Derby
>         Type: Improvement
>   Components: JDBC
>     Versions:,,,
>     Reporter: Kathey Marsden
>     Assignee: David Van Couvering
>     Priority: Trivial
>      Fix For:
>  Attachments: DERBY-243.diff
> The toString() on the Derby connection doesn't print 
> unique information.
> for example  System.out.println(conn) prints:
> EmbedConnection  in the case of derby embedded
> It would be great if the toString() method for connections could be used to differentiate
one connection from another.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message