db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "quartz (JIRA)" <j...@apache.org>
Subject [jira] Created: (DERBY-2451) a client can crash connections of another client
Date Wed, 14 Mar 2007 15:58:09 GMT
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.


Mime
View raw message