db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julius Stroffek (JIRA)" <j...@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, 15 Nov 2006 16:22:40 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1434?page=all ]

Julius Stroffek updated DERBY-1434:

    Attachment: derby1434-try2.diff

I have to modify also a protocolTest.java because it was sending a wrong database name in
PKGNAMCSN in all cases. I added two more tests.

1.) drda protocol test to protocol.tests which ensures that the error of wrong RDBNAM field
sent in PKGNAMCSN is handled correctly

2.) junit test derbynet/DRDAProtocolTest.java which checks that on an application level the
connections to different databases are handled correctly. The database files are not deleted
yet after running a test. I have created a DERBY-2087 to handle this.

Please review my change.

> 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
>          Issue Type: Bug
>          Components: Network Client
>    Affects Versions:,
>            Reporter: A B
>         Assigned To: Julius Stroffek
>             Fix For:
>         Attachments: _driver_1, d1434.java, d1434_v2.java, derby-1434-trunk-diff.txt,
derby1434-try2.diff, derby1434-try2.diff, derby1434-try2.stat, Server2.trace
> 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: http://issues.apache.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message