[DERBY-2451] a client can crash connections of another client

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Duplicate
• Affects Version/s: 10.2.2.0
• Fix Version/s: 10.3.1.4
• Component/s: Network Server
• Urgency: Normal
• Assignee: Unassigned
• Reporter: quartz
• Created: 14/Mar/07 15:57
• Updated: 21/Jan/11 17:49
• Resolved: 06/Jul/07 16:29

Description

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.

Issue Links

• relates to: DERBY-256 ASSERTION when attempting to execute a statement after shutdown of database with network Server
• relates to: DERBY-1737 Network Server should check for current open and active connections before shutting down a database
• relates to: DERBY-2264 Restrict shutdown, upgrade, and encryption powers to the database owner