Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 71460 invoked from network); 21 Jun 2006 21:56:56 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 21 Jun 2006 21:56:56 -0000 Received: (qmail 27237 invoked by uid 500); 21 Jun 2006 21:56:56 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 27013 invoked by uid 500); 21 Jun 2006 21:56:55 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 26995 invoked by uid 99); 21 Jun 2006 21:56:55 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Jun 2006 14:56:55 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [209.237.227.198] (HELO brutus.apache.org) (209.237.227.198) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Jun 2006 14:56:54 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id DB827410007 for ; Wed, 21 Jun 2006 21:55:29 +0000 (GMT) Message-ID: <6507467.1150926929896.JavaMail.jira@brutus> Date: Wed, 21 Jun 2006 21:55:29 +0000 (GMT+00:00) From: "A B (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Created: (DERBY-1434) Client can send incorrect database name to server after having made multiple connections to different databases. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N 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: 10.2.0.0, 10.1.3.0, 10.1.2.5 Reporter: A B Priority: Minor Fix For: 10.2.0.0 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