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] Commented: (DERBY-2451) a client can crash connections of another client
Date Fri, 06 Jul 2007 12:41:04 GMT

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

quartz commented on DERBY-2451:

That is very easy:

1-goto the bin folder and startNetworkServer.bat

2-start 1 process for sqlworkbench/j and connect (with driver org.apache.derby.jdbc.ClientDriver)

3-run this sql

	  x int NOT NULL default 0,
	  y int NOT NULL default 0

	insert into xy (x,y) values (1,10);
	insert into xy (x,y) values (2,20);
	insert into xy (x,y) values (3,30);

4-verify the data:
	select * from xy;

5-Now start a 2nd sqlworkbench/j process, (new jvm, not a new window...big difference)

6-connect this 2nd instance to the same url

7-verify the data:
	select * from xy;
8-Now , close any of the 2 client (just click the X in the right corner)

9- try to "select * from xy;" on the remining client. Result:

	An error occurred when executing the SQL command:
	A network protocol error was encountered and the connection has
	been terminated: the requested command encountered an unarchitected 
	and implementation-specific condition for which there was no
	architected message [SQL State=58009, DB Errorcode=-4499] 
	Total execution time: 0s
	1 statement(s) failed.

> 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:
>            Reporter: quartz
>            Priority: Critical
> Using
> 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
> 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.

View raw message