db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lily Wei (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4345) Inconsistent behavior regarding shutting down embedded engine from ClientDataSource and ClientDriver/DriverManager
Date Fri, 11 Sep 2009 05:28:57 GMT

    [ https://issues.apache.org/jira/browse/DERBY-4345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12754010#action_12754010
] 

Lily Wei commented on DERBY-4345:
---------------------------------

Hmm... This is very strange. I just run it with trunk (revision 813232). management.InactiveManagementMBeanTest
pass for me.
$ java junit.textui.TestRunner org.apache.derbyTesting.functionTests.tests.mana
gement.InactiveManagementMBeanTest
..
Time: 5.521

OK (2 tests)

Looking from the dump, it is waiting for thread to finish. I did not change anything in DRDAConnThread.java.
I will keep looking. Will this be different SDK issue?

> 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: DERBY-4345-2.diff, DERBY-4345.diff, javacore.20090908.140353.4296.0001.txt,
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.


Mime
View raw message