[
https://issues.apache.org/jira/browse/DERBY-4345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden updated DERBY-4345:
----------------------------------
Attachment: DriverManagerLockIssue.java
Here is a smaller repro (DriverManagerLockIssue.java) for the hang that I am
seeing with IBM 1.6. The problem occurs because with shutdown the Client is
calling DriverManager.getConnection() and the server has code which detects the
shutdown and tries to call DriverManager.getDriver() to restart the server.
Since both are running in the same JVM and both calls are synchronized on the
same object in DriverManager, we get the hang.
This used to be an issue with the Sun JVM as well:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4263113
but appears to no longer be a problem with JDK 1.6 for Sun.
I am really not sure how to resolve this, but at least think I now understand
the problem.
> 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,
> DriverManagerLockIssue.java, 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.
