db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew McIntyre (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-2451) a client can crash connections of another client
Date Fri, 06 Jul 2007 16:29:04 GMT

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

Andrew McIntyre updated DERBY-2451:
-----------------------------------

    Attachment: Server4.trace

I was able to reproduce the behavior when connecting with two different SQL Workbench/J instances.
Attaching the server trace which shows that the second SQL Workbench/J does in fact issue
a shutdown when the application instance is closed (step 8 of quartz' repro). This would be
proper application behavior if this were an embedded database. Apparently SQL Workbench/J
does not distinguish between the embedded and client/server modes.

This is therefore a duplicate of DERBY-256. There is definitely no data coherence risk, since
the database is being shutdown via the normal shutdown mechanism. To prevent this possible
denial of service, upgrade to 10.3, and enable authentication and SQL authorization when starting
up your network server. See also 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
>         Attachments: Server4.trace
>
>
> 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