[
https://issues.apache.org/jira/browse/DERBY-4345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12741668#action_12741668
]
Lily Wei commented on DERBY-4345:
---------------------------------
Thanks, Dag!
Yes, with extra ";". The repro can shutdown the server and restart embedded
engine. However, with repro3532, the embedded engine did not get started.
Hence, the network server did not go to boot process. As the result of that,
authentication service is null. Which behavior is the one we prefer?
> 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.
