db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "A B (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-1434) Client can send incorrect database name to server after having made multiple connections to different databases.
Date Wed, 21 Jun 2006 22:03:30 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1434?page=all ]

A B updated DERBY-1434:

    Attachment: d1434.java

Attaching a simple repro of the problem.  To run, start the server with tracing on:

> java -Dderby.drda.traceAll=true org.apache.derby.drda.NetworkServerControl start -p 1527

Then run the repro:

> java d1434

A look at the client trace in _driver_1 shows that the client is sending "SECONDDB_2" for
the authentication phase--i.e. for the EXCSAT, ACCSEC, SECCHK, and ACCRDB codepoints--but
then it's sending "FIRSTDB_1" for the EXCSQLIMM codepoint.  However, a look at the the actual
Connection object name shows that it is (correctly) the connection object for SECONDDB_2--so
the connection is correct, but the database name is wrong.

And a look at the server trace (Server2.trace) shows that the server is in fact receiving
the wrong database name.

I've attached the server and client traces for the repro when run against 10.1.

> Client can send incorrect database name to server after having made multiple connections
to different databases.
> ----------------------------------------------------------------------------------------------------------------
>          Key: DERBY-1434
>          URL: http://issues.apache.org/jira/browse/DERBY-1434
>      Project: Derby
>         Type: Bug

>   Components: Network Client
>     Versions:,,
>     Reporter: A B
>     Priority: Minor
>      Fix For:
>  Attachments: Server2.trace, _driver_1, d1434.java
> I have a simple program that connects to a database using the Derby Client, executes
a simple query, then connects to a different database using a different Connection object
and executes another simple query on that second connection.  The queries both execute without
error, so it appears that the connections are correct--i.e. each query will only work on one
of the databases, and both queries work, therefore each must be getting executed against the
correct database.
> But in looking at the client and server traces, I noticed that for the query on the second
database, the client is actually sending the name of the *first* database as RDBNAM, which
(I think?) is wrong--it should be sending the name of the second database, since the query
is being executed on the second Connection object.
> This behavior does not appear to occur for JCC.

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