db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-1434) Client can send incorrect database name to server after having made multiple connections to different databases.
Date Thu, 22 Jun 2006 19:27:30 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1434?page=comments#action_12417352 ] 

Kathey Marsden commented on DERBY-1434:

Well, I guess I have a little to say about the client code.
It looks like our client SectionManager logic is fatally flawed when it comes to two databases.
It has these two static variables  for hold and non-hold  package names and consistency tokens.

// noHoldPKGNAMCBytes stores PKGNAMCBytes when holdability is no hold
    public static byte[] holdPKGNAMCBytes = null;
    public static byte[] noHoldPKGNAMCBytes = null;

There seems to be a databaseName parameter for each SectionManager, so I don't understand
why these  are static.

> 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
>      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