[
https://issues.apache.org/jira/browse/DERBY-300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden resolved DERBY-300.
----------------------------------
Resolution: Won't Fix
Won't fix since 1.3.1 is no longer supported.
> Creation of SQLWarning on a getConnection causes hang on 131 vms when server
> and client are in same vm.
> -------------------------------------------------------------------------------------------------------
>
> Key: DERBY-300
> URL: https://issues.apache.org/jira/browse/DERBY-300
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.1.1.0
> Environment: seems to occur on 131 vms, hang seen on both sun 1.3.1
> and ibm 1.3.1
> Reporter: Sunitha Kambhampati
> Priority: Trivial
> Attachments: testNS.java
>
>
> Problem - with 131 vms, if server and client are in the same jvm, on a second
> get connection with create=true attribute in the url, there is a hang.
> Basically,
> -- the first getConnection works ok
> -- but on the second getConnection, a SQLWarning needs to be generated to
> say that the database already exists and in this scenario, it seems like at
> the point where it is creating a SQLWarning , there is a deadlock. The call
> to SQLWarning constructor does not return. On doing a java core dump , the
> thread in question seems to be in a wait state (conditional wait). Guess is
> it has to do with the driver manager lock
> Also note, this problem is observed only with 131 vms, so I guess it was
> fixed in the later vms (1.4.1, 1.4.2 1.5)
> Opened this entry to keep track of this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
