db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mamta Satoor <msat...@gmail.com>
Subject Re: [jira] Updated: (DERBY-389) With Network Server Database hangs after some time with many connections executing prepareStatement()
Date Mon, 27 Jun 2005 14:31:52 GMT
Hi Kathey,
 Was just wondering what the information about temp table that had to be 
fixed? I tried looking
at javacore*.diff files attached to JIRA, but they were huge. Should I 
continue looking through
them or is there some other way to look at specific javadoc changes?
 thanks,
Mamta

 On 6/25/05, Kathey Marsden (JIRA) <derby-dev@db.apache.org> wrote: 
> 
> [ http://issues.apache.org/jira/browse/DERBY-389?page=all ]
> 
> Kathey Marsden updated DERBY-389:
> ---------------------------------
> 
> Attachment: derby389.diff
> 
> This patch fixes the hang in the network server stress test. The change 
> was to remove the synchronization on the statement cache from the 
> removeStatement method of GenericLanguageConnectionContext. It is not needed 
> because the statement cache handles its own synchronization. Also changes 
> the javadoc to remove some incorrect info about temp tables. I will check 
> this in later today if I hear no objections.
> 
> 
> 
> > With Network Server Database hangs after some time with many connections 
> executing prepareStatement()
> > 
> -----------------------------------------------------------------------------------------------------
> >
> > Key: DERBY-389
> > URL: http://issues.apache.org/jira/browse/DERBY-389
> > Project: Derby
> > Type: Bug
> > Components: JDBC, Network Server
> > Versions: 10.1.1.0 <http://10.1.1.0>, 10.2.0.0 <http://10.2.0.0>
> > Reporter: Kathey Marsden
> > Assignee: Kathey Marsden
> > Priority: Critical
> > Attachments: RTINFO.txt, derby.log, derby389.diff, 
> javacore.20050622.135027.2491.txt, javacore.20050623.150509.22394.txt
> >
> > Rajesh found this issue in running Network Server system tests for the 
> 10.1 release candidate
> > While running the Network Server system test with 210 clients,
> > the Network Server and all the clients hangs after some time.
> > A Ctrl+\ on the Network Server shows that upto 180 threads
> > waiting on the PreparedStatements to compile and comes from the
> > embedded engine. The following is the stack trace from the java
> > dump.
> > 3XMTHREADINFO "DRDAConnThread_181" (TID:1007C998,
> > sys_thread_t:85C4478, state:CW, native ID:4575ABB0) prio=5
> > 4XESTACKTRACE at java.lang.Object.wait(Native Method)
> > 4XESTACKTRACE at
> > java.lang.Object.wait(Object.java(Compiled Code))
> > 4XESTACKTRACE at
> > org.apache.derby.impl.sql.GenericStatement.prepMinion(GenericSta
> > tement.java(Compiled Code))
> > 4XESTACKTRACE at
> > org.apache.derby.impl.sql.GenericStatement.prepare(GenericStatem
> > ent.java)
> > 4XESTACKTRACE at
> > org.apache.derby.impl.sql.conn.GenericLanguageConnectionContext.
> > prepareInternalStatement(GenericLanguageConnectionContext.java)
> > 4XESTACKTRACE at
> > org.apache.derby.impl.jdbc.EmbedPreparedStatement.<init>(Embe
> > dPreparedStatement.java)
> > 4XESTACKTRACE at
> > org.apache.derby.impl.jdbc.EmbedPreparedStatement20.<init>(Em
> > bedPreparedStatement20.java)
> > 4XESTACKTRACE at
> > org.apache.derby.impl.jdbc.EmbedPreparedStatement30.<init>(Em
> > bedPreparedStatement30.java)
> > 4XESTACKTRACE at
> > org.apache.derby.jdbc.Driver30.newEmbedPreparedStatement(Driver3
> > 0.java)
> > 4XESTACKTRACE at
> > org.apache.derby.impl.jdbc.EmbedConnection.prepareStatement(Embe
> > dConnection.java)
> > 4XESTACKTRACE at
> > org.apache.derby.impl.jdbc.EmbedConnection.prepareStatement(Embe
> > dConnection.java)
> > 4XESTACKTRACE at
> > sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
> > 4XESTACKTRACE at
> > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod
> > AccessorImpl.java(Compiled Code))
> > 4XESTACKTRACE at
> > java.lang.reflect.Method.invoke(Method.java(Compiled Code))
> > 4XESTACKTRACE at
> > org.apache.derby.impl.drda.DRDAStatement.prepareStatementJDBC3(D
> > RDAStatement.java)
> > 4XESTACKTRACE at
> > org.apache.derby.impl.drda.DRDAStatement.prepare(DRDAStatement.j
> > ava)
> > 4XESTACKTRACE at
> > org.apache.derby.impl.drda.DRDAStatement.explicitPrepare(DRDASta
> > tement.java(Compiled Code))
> > 4XESTACKTRACE at
> > org.apache.derby.impl.drda.DRDAConnThread.parsePRPSQLSTT(DRDACon
> > nThread.java(Compiled Code))
> > 4XESTACKTRACE at
> > org.apache.derby.impl.drda.DRDAConnThread.processCommands(DRDACo
> > nnThread.java(Compiled Code))
> > 4XESTACKTRACE at
> > org.apache.derby.impl.drda.DRDAConnThread.run(DRDAConnThread.jav
> > a)
> 
> --
> 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