[
https://issues.apache.org/jira/browse/DERBY-4345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12741625#action_12741625
]
Dag H. Wanvik commented on DERBY-4345:
--------------------------------------
Thanks, Lily!
In my experiment I had "shutdown" as part of the URL, not as a property.
I tried this URL variant which also seems to works (note the extra semicolon):
DriverManager.getConnection("jdbc:derby://localhost:1527/;",p);
> Inconsistent behavior regarding shutting down embedded engine from
> ClientDataSource and ClientDriver/DriverManager
> ------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-4345
> URL: https://issues.apache.org/jira/browse/DERBY-4345
> Project: Derby
> Issue Type: Bug
> Components: Network Server
> Affects Versions: 10.5.1.1
> Environment: Windows Vista with JDK 1.6
> Reporter: Lily Wei
> Priority: Minor
> Attachments: ReproDerby3532.java, ReproDerby4345.java
>
>
> When investigate DERBY-3532, Kathey and I found inconsistent behavior in turn
> of connection modes possible to shut down the engine underneath the network
> server. Currently, users can shutdown from the client remotely with
> ClientDataSource but not with ClientDriver/DriverManager. The two should be
> the same.
> Should we disable the capability for ClientDataSource or enable it for
> ClientDriver? I am leaning toward to disable the capability for
> ClientDataSource. However, I am not sure about the risk of functionality
> disable impact for existing production customers.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
