db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sunitha Kambhampati (JIRA)" <derby-...@db.apache.org>
Subject [jira] Created: (DERBY-300) Creation of SQLWarning on a getConnection causes hang on 131 vms when server and client are in same vm.
Date Thu, 19 May 2005 05:30:51 GMT
Creation of SQLWarning on a getConnection causes hang on 131 vms when server and client are
in same vm.
-------------------------------------------------------------------------------------------------------

         Key: DERBY-300
         URL: http://issues.apache.org/jira/browse/DERBY-300
     Project: Derby
        Type: Bug
  Components: JDBC  
    Versions: 10.1.0.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


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.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message