Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <8867202.1174186269382.JavaMail.jira@brutus>
Date: Sat, 17 Mar 2007 19:51:09 -0700 (PDT)
From: "Dag H. Wanvik (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-2451) a client can crash connections of
 another client
In-Reply-To: <14263395.1173887889704.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/DERBY-2451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481905 ] 

Dag H. Wanvik commented on DERBY-2451:
--------------------------------------

If a db shutdown takes place, this is probably a duplicate of
DERBY-256.

As for shutdown privilege, this is being restricted in the next
release to the database owner, cf. DERBY-2264.


> a client can crash connections of another client
> ------------------------------------------------
>
>                 Key: DERBY-2451
>                 URL: https://issues.apache.org/jira/browse/DERBY-2451
>             Project: Derby
>          Issue Type: Bug
>          Components: Network Server
>    Affects Versions: 10.2.2.0
>            Reporter: quartz
>            Priority: Critical
>
> Using 10.2.2.0.
> Steps to reproduce:
> 1-Start a NetworkServerControl
> 2-Start a 1st client (sqlworkbench/J), show some rows of some db, table X (stay connected)
> 3-Start a 2nd client (sqlworkbench/J), show some rows of some db, table X.
> 4-disconnect 2nd client
> 5-redo the 1st client query (refresh)
> You get a non architected message, sqlstate 58009, db errorcode -4499.
> In derby log, I see a shutdown of the database, and a restart.
> No matter how badly and corrupted a client connection can get, nor if the client connection is
> a bug in any client,  such corruption should never destabilise a "server",
> certainly not other clients connections.
> It may be that the client tries to shutdown the DB; it shouldn't have such privilege anyway since it
> is a network "client" connection, NOT  an embedded connection.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.