You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kathey Marsden (JIRA)" <de...@db.apache.org> on 2005/06/23 14:44:09 UTC
[jira] Created: (DERBY-389) With Network Server Database hangs after some time with many connections executing prepareStatement()
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, 10.2.0.0
Reporter: Kathey Marsden
Assigned to: Kathey Marsden
Priority: Critical
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
Re: [jira] Updated: (DERBY-389) With Network Server Database hangs after some time with many connections executing prepareStatement()
Posted by Mamta Satoor <ms...@gmail.com>.
Never mind. I saw in another mail the specific javadoc changes you are
suggesting.
thanks,
Mamta
On 6/27/05, Mamta Satoor <ms...@gmail.com> wrote:
>
> 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) <de...@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
> >
> >
>
Re: [jira] Updated: (DERBY-389) With Network Server Database hangs after some time with many connections executing prepareStatement()
Posted by Mamta Satoor <ms...@gmail.com>.
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) <de...@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
>
>
[jira] Updated: (DERBY-389) With Network Server Database hangs after some time with many connections executing prepareStatement()
Posted by "Kathey Marsden (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-389?page=all ]
Kathey Marsden updated DERBY-389:
---------------------------------
Fix Version: 10.1.1.0
(was: 10.1.2.0)
This was actually fixed in 10.1.1.0
> 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, 10.2.0.0
> Reporter: Kathey Marsden
> Assignee: Kathey Marsden
> Priority: Critical
> Fix For: 10.2.0.0, 10.1.1.0
> 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
[jira] Updated: (DERBY-389) With Network Server Database hangs after some time with many connections executing prepareStatement()
Posted by "Kathey Marsden (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-389?page=all ]
Kathey Marsden updated DERBY-389:
---------------------------------
Attachment: javacore.20050622.135027.2491.txt
This is the java core file. I do not yet have a repro I can attach.
> 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, 10.2.0.0
> Reporter: Kathey Marsden
> Assignee: Kathey Marsden
> Priority: Critical
> Attachments: javacore.20050622.135027.2491.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
[jira] Commented: (DERBY-389) With Network Server Database hangs after some time with many connections executing prepareStatement()
Posted by "Kathey Marsden (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-389?page=comments#action_12314445 ]
Kathey Marsden commented on DERBY-389:
--------------------------------------
QUESTION ON JAVADOC FOR GenericLanguageConnectionContext.removeStatement()
removeStatement() removes statements from the cache and seems to only be called when an SQLException occurs on prepare. This makes sense in the context that Rajesh's test had lots of failed statements and those were probably causing DERBY-389 to occur.
The javadoc for this method says something else entirely and seems kind
of misleading. It talks about statements in the SESSION schema (temp table schema) getting removed. I don't see this method being called
for any special handling of temp tables and based on the comment it
sounds like it would be a bad thing for those statements to be in the
cache at all.
I want to change the javadoc comment to take out the reference to the SESSION schema. Does anyone have any issues with this change? Am I missing an important piece of history or misunderstanding the use of this method?
OLD JAVADOC
/**
* This method will get called if the statement is referencing
tables in SESSION schema.
* We do not want to cache such statements because multiple
connections can have
* different definition of the same table name and hence compiled
plan for one connection
* may not make sense for some other connection. Because of this,
remove the statement from the cache
*
* @exception StandardException thrown if lookup goes wrong.
*/
NEW JAVADOC
/**
* This method will remove a statement from the statement cache.
* It will be called, for example, if there is an exception preparing
* the statement.
*
* @param statement Statement to remove
* @exception StandardException thrown if lookup goes wrong.
*/
THE ONE removeStatement REFERENCE
from GenericStatement.prepMinion()
....
catch (StandardException se)
{
lcc.commitNestedTransaction();
if (foundInCache)
((GenericLanguageConnectionContext)lcc).removeStatement(this);
.....
> 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, 10.2.0.0
> Reporter: Kathey Marsden
> Assignee: Kathey Marsden
> Priority: Critical
> Attachments: RTINFO.txt, derby.log, 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
[jira] Commented: (DERBY-389) With Network Server Database hangs after some time with many connections executing prepareStatement()
Posted by "Kathey Marsden (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-389?page=comments#action_12314350 ]
Kathey Marsden commented on DERBY-389:
--------------------------------------
Manjula sent me this trace when the server was in a similar state,
"DRDAConnThread_7" prio=5 tid=0x0ae97d18 nid=0x988 waiting for monitor entry [0x
0bdcf000..0x0bdcf9e4]
at org.apache.derby.impl.sql.conn.GenericLanguageConnectionContext.remov
eStatement(GenericLanguageConnectionContext.java)
- waiting to lock <0x02fdfcd0> (a org.apache.derby.impl.services.cache.C
lock)
at org.apache.derby.impl.sql.GenericStatement.prepMinion(GenericStatemen
t.java)
at org.apache.derby.impl.sql.GenericStatement.prepare(GenericStatement.j
ava)
at org.apache.derby.impl.sql.conn.GenericLanguageConnectionContext.prepa
reInternalStatement(GenericLanguageConnectionContext.java)
at org.apache.derby.impl.jdbc.EmbedPreparedStatement.<init>(EmbedPrepare
dStatement.java)
at org.apache.derby.impl.jdbc.EmbedPreparedStatement20.<init>(EmbedPrepa
redStatement20.java)
at org.apache.derby.impl.jdbc.EmbedPreparedStatement30.<init>(EmbedPrepa
redStatement30.java)
at org.apache.derby.jdbc.Driver30.newEmbedPreparedStatement(Driver30.jav
a)
at org.apache.derby.impl.jdbc.EmbedConnection.prepareStatement(EmbedConn
ection.java)
- locked <0x03db03e0> (a org.apache.derby.impl.jdbc.EmbedConnection30)
at org.apache.derby.impl.jdbc.EmbedConnection.prepareStatement(EmbedConn
ection.java)
at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.derby.impl.drda.DRDAStatement.prepareStatementJDBC3(DRDASt
atement.java)
at org.apache.derby.impl.drda.DRDAStatement.prepare(DRDAStatement.java)
at org.apache.derby.impl.drda.DRDAStatement.explicitPrepare(DRDAStatemen
t.java)
at org.apache.derby.impl.drda.DRDAConnThread.parsePRPSQLSTT(DRDAConnThre
ad.java)
at org.apache.derby.impl.drda.DRDAConnThread.processCommands(DRDAConnThr
ead.java)
at org.apache.derby.impl.drda.DRDAConnThread.run(DRDAConnThread.java)
"DRDAConnThread_6" prio=5 tid=0x0aeb8d28 nid=0x998 in Object.wait() [0x0bd8f000.
.0x0bd8fa64]
at java.lang.Object.wait(Native Method)
- waiting on <0x03db4a78> (a org.apache.derby.impl.services.cache.Cached
Item)
at java.lang.Object.wait(Object.java:474)
at org.apache.derby.impl.services.cache.CachedItem.remove(CachedItem.jav
a)
- locked <0x03db4a78> (a org.apache.derby.impl.services.cache.CachedItem
)
at org.apache.derby.impl.services.cache.Clock.remove(Clock.java)
at org.apache.derby.impl.sql.conn.GenericLanguageConnectionContext.remov
eStatement(GenericLanguageConnectionContext.java)
- locked <0x02fdfcd0> (a org.apache.derby.impl.services.cache.Clock)
at org.apache.derby.impl.sql.GenericStatement.prepMinion(GenericStatemen
t.java)
at org.apache.derby.impl.sql.GenericStatement.prepare(GenericStatement.j
ava)
at org.apache.derby.impl.sql.conn.GenericLanguageConnectionContext.prepa
reInternalStatement(GenericLanguageConnectionContext.java)
at org.apache.derby.impl.jdbc.EmbedPreparedStatement.<init>(EmbedPrepare
dStatement.java)
at org.apache.derby.impl.jdbc.EmbedPreparedStatement20.<init>(EmbedPrepa
redStatement20.java)
at org.apache.derby.impl.jdbc.EmbedPreparedStatement30.<init>(EmbedPrepa
redStatement30.java)
at org.apache.derby.jdbc.Driver30.newEmbedPreparedStatement(Driver30.jav
a)
at org.apache.derby.impl.jdbc.EmbedConnection.prepareStatement(EmbedConn
ection.java)
- locked <0x03db5ad8> (a org.apache.derby.impl.jdbc.EmbedConnection30)
at org.apache.derby.impl.jdbc.EmbedConnection.prepareStatement(EmbedConn
ection.java)
at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.derby.impl.drda.DRDAStatement.prepareStatementJDBC3(DRDASt
atement.java)
at org.apache.derby.impl.drda.DRDAStatement.prepare(DRDAStatement.java)
at org.apache.derby.impl.drda.DRDAStatement.explicitPrepare(DRDAStatemen
t.java)
at org.apache.derby.impl.drda.DRDAConnThread.parsePRPSQLSTT(DRDAConnThre
ad.java)
at org.apache.derby.impl.drda.DRDAConnThread.processCommands(DRDAConnThr
ead.java)
at org.apache.derby.impl.drda.DRDAConnThread.run(DRDAConnThread.java)
"DRDAConnThread_5" prio=5 tid=0x0adb94c8 nid=0x9a8 waiting for monitor entry [0x
0bd4f000..0x0bd4fae4]
at org.apache.derby.impl.services.cache.Clock.find(Clock.java)
- waiting to lock <0x02fdfcd0> (a org.apache.derby.impl.services.cache.C
lock)
at org.apache.derby.impl.sql.conn.GenericLanguageConnectionContext.looku
pStatement(GenericLanguageConnectionContext.java)
at org.apache.derby.impl.sql.GenericStatement.prepMinion(GenericStatemen
t.java)
at org.apache.derby.impl.sql.GenericStatement.prepare(GenericStatement.j
ava)
at org.apache.derby.impl.sql.conn.GenericLanguageConnectionContext.prepa
reInternalStatement(GenericLanguageConnectionContext.java)
at org.apache.derby.impl.jdbc.EmbedStatement.execute(EmbedStatement.java
)
- locked <0x03e07518> (a org.apache.derby.impl.jdbc.EmbedConnection30)
at org.apache.derby.impl.jdbc.EmbedStatement.executeUpdate(EmbedStatemen
t.java)
at org.apache.derby.impl.drda.DRDAConnThread.parseEXCSQLIMM(DRDAConnThre
ad.java)
at org.apache.derby.impl.drda.DRDAConnThread.processCommands(DRDAConnThr
ead.java)
at org.apache.derby.impl.drda.DRDAConnThread.run(DRDAConnThread.java)
"DRDAConnThread_4" prio=5 tid=0x009febe8 nid=0x9c0 waiting for monitor entry [0x
0bd0f000..0x0bd0fb64]
at org.apache.derby.impl.services.cache.Clock.find(Clock.java)
- waiting to lock <0x02fdfcd0> (a org.apache.derby.impl.services.cache.C
lock)
at org.apache.derby.impl.sql.conn.GenericLanguageConnectionContext.looku
pStatement(GenericLanguageConnectionContext.java)
at org.apache.derby.impl.sql.GenericStatement.prepMinion(GenericStatemen
t.java)
at org.apache.derby.impl.sql.GenericStatement.prepare(GenericStatement.j
ava)
at org.apache.derby.impl.sql.conn.GenericLanguageConnectionContext.prepa
reInternalStatement(GenericLanguageConnectionContext.java)
at org.apache.derby.impl.jdbc.EmbedPreparedStatement.<init>(EmbedPrepare
dStatement.java)
at org.apache.derby.impl.jdbc.EmbedPreparedStatement20.<init>(EmbedPrepa
redStatement20.java)
at org.apache.derby.impl.jdbc.EmbedPreparedStatement30.<init>(EmbedPrepa
redStatement30.java)
at org.apache.derby.jdbc.Driver30.newEmbedPreparedStatement(Driver30.jav
a)
at org.apache.derby.impl.jdbc.EmbedConnection.prepareStatement(EmbedConn
ection.java)
- locked <0x03dbd7f8> (a org.apache.derby.impl.jdbc.EmbedConnection30)
at org.apache.derby.impl.jdbc.EmbedConnection.prepareStatement(EmbedConn
ection.java)
at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.derby.impl.drda.DRDAStatement.prepareStatementJDBC3(DRDASt
atement.java)
at org.apache.derby.impl.drda.DRDAStatement.prepare(DRDAStatement.java)
at org.apache.derby.impl.drda.DRDAStatement.explicitPrepare(DRDAStatemen
t.java)
at org.apache.derby.impl.drda.DRDAConnThread.parsePRPSQLSTT(DRDAConnThre
ad.java)
at org.apache.derby.impl.drda.DRDAConnThread.processCommands(DRDAConnThr
ead.java)
at org.apache.derby.impl.drda.DRDAConnThread.run(DRDAConnThread.java)
"DRDAConnThread_3" prio=5 tid=0x0ba4b5b8 nid=0x9d0 waiting for monitor entry [0x
0bccf000..0x0bccfbe4]
at org.apache.derby.impl.services.cache.Clock.find(Clock.java)
- waiting to lock <0x02fdfcd0> (a org.apache.derby.impl.services.cache.C
lock)
at org.apache.derby.impl.sql.conn.GenericLanguageConnectionContext.looku
pStatement(GenericLanguageConnectionContext.java)
at org.apache.derby.impl.sql.GenericStatement.prepMinion(GenericStatemen
t.java)
at org.apache.derby.impl.sql.GenericStatement.prepare(GenericStatement.j
ava)
at org.apache.derby.impl.sql.conn.GenericLanguageConnectionContext.prepa
reInternalStatement(GenericLanguageConnectionContext.java)
at org.apache.derby.impl.jdbc.EmbedStatement.execute(EmbedStatement.java
)
- locked <0x03e078d8> (a org.apache.derby.impl.jdbc.EmbedConnection30)
at org.apache.derby.impl.jdbc.EmbedStatement.executeUpdate(EmbedStatemen
t.java)
at org.apache.derby.impl.drda.DRDAConnThread.parseEXCSQLIMM(DRDAConnThre
ad.java)
at org.apache.derby.impl.drda.DRDAConnThread.processCommands(DRDAConnThr
ead.java)
at org.apache.derby.impl.drda.DRDAConnThread.run(DRDAConnThread.java)
"derby.rawStoreDaemon" daemon prio=5 tid=0x0ad29d68 nid=0x9d8 in Object.wait() [
0x0b88f000..0x0b88fc64]
at java.lang.Object.wait(Native Method)
at org.apache.derby.impl.services.daemon.BasicDaemon.rest(BasicDaemon.ja
va)
- locked <0x02fcf1e0> (a org.apache.derby.impl.services.daemon.BasicDaem
on)
at org.apache.derby.impl.services.daemon.BasicDaemon.run(BasicDaemon.jav
a)
at java.lang.Thread.run(Thread.java:595)
"DRDAConnThread_2" prio=5 tid=0x0ae1e448 nid=0x9e0 waiting for monitor entry [0x
0b84f000..0x0b84fce4]
at org.apache.derby.impl.services.cache.Clock.release(Clock.java)
- waiting to lock <0x02fdfcd0> (a org.apache.derby.impl.services.cache.C
lock)
at org.apache.derby.impl.sql.conn.GenericLanguageConnectionContext.looku
pStatement(GenericLanguageConnectionContext.java)
at org.apache.derby.impl.sql.GenericStatement.prepMinion(GenericStatemen
t.java)
at org.apache.derby.impl.sql.GenericStatement.prepare(GenericStatement.j
ava)
at org.apache.derby.impl.sql.conn.GenericLanguageConnectionContext.prepa
reInternalStatement(GenericLanguageConnectionContext.java)
at org.apache.derby.impl.jdbc.EmbedPreparedStatement.<init>(EmbedPrepare
dStatement.java)
at org.apache.derby.impl.jdbc.EmbedPreparedStatement20.<init>(EmbedPrepa
redStatement20.java)
at org.apache.derby.impl.jdbc.EmbedPreparedStatement30.<init>(EmbedPrepa
redStatement30.java)
at org.apache.derby.jdbc.Driver30.newEmbedPreparedStatement(Driver30.jav
a)
at org.apache.derby.impl.jdbc.EmbedConnection.prepareStatement(EmbedConn
ection.java)
- locked <0x03dca718> (a org.apache.derby.impl.jdbc.EmbedConnection30)
at org.apache.derby.impl.jdbc.EmbedConnection.prepareStatement(EmbedConn
ection.java)
at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.derby.impl.drda.DRDAStatement.prepareStatementJDBC3(DRDASt
atement.java)
at org.apache.derby.impl.drda.DRDAStatement.prepare(DRDAStatement.java)
at org.apache.derby.impl.drda.DRDAStatement.explicitPrepare(DRDAStatemen
t.java)
at org.apache.derby.impl.drda.DRDAConnThread.parsePRPSQLSTT(DRDAConnThre
ad.java)
at org.apache.derby.impl.drda.DRDAConnThread.processCommands(DRDAConnThr
ead.java)
at org.apache.derby.impl.drda.DRDAConnThread.run(DRDAConnThread.java)
"Thread-1" prio=5 tid=0x0ad8cde8 nid=0xa54 runnable [0x0b7ff000..0x0b7ffd64]
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384)
- locked <0x02faf708> (a java.net.SocksSocketImpl)
at java.net.ServerSocket.implAccept(ServerSocket.java:450)
at java.net.ServerSocket.accept(ServerSocket.java:421)
at org.apache.derby.impl.drda.ClientThread$1.run(ClientThread.java)
at java.security.AccessController.doPrivileged(Native Method)
at org.apache.derby.impl.drda.ClientThread.run(ClientThread.java)
at java.lang.Thread.run(Thread.java:595)
"derby.antiGC" daemon prio=2 tid=0x0ad2cc40 nid=0xa5c in Object.wait() [0x0af3f0
00..0x0af3f9e4]
at java.lang.Object.wait(Native Method)
- waiting on <0x02fa2150> (a org.apache.derby.impl.services.monitor.Anti
GC)
at java.lang.Object.wait(Object.java:474)
at org.apache.derby.impl.services.monitor.AntiGC.run(BaseMonitor.java)
- locked <0x02fa2150> (a org.apache.derby.impl.services.monitor.AntiGC)
at java.lang.Thread.run(Thread.java:595)
"Low Memory Detector" daemon prio=5 tid=0x009d2f60 nid=0x5cc runnable [0x0000000
0..0x00000000]
"CompilerThread0" daemon prio=10 tid=0x009d1ac0 nid=0xa68 waiting on condition [
0x00000000..0x0ac6f8bc]
"Signal Dispatcher" daemon prio=10 tid=0x009d0cf8 nid=0x6d8 waiting on condition
[0x00000000..0x00000000]
"Finalizer" daemon prio=9 tid=0x009c81a8 nid=0x17c in Object.wait() [0x0abef000.
.0x0abefc64]
at java.lang.Object.wait(Native Method)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:116)
- locked <0x02f82798> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:132)
at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:159)
"Reference Handler" daemon prio=10 tid=0x009c6cb8 nid=0xa6c in Object.wait() [0x
0abaf000..0x0abafce4]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:474)
at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:116)
- locked <0x02f82818> (a java.lang.ref.Reference$Lock)
"main" prio=5 tid=0x00236e80 nid=0x6dc in Object.wait() [0x0006f000..0x0006fc38]
at java.lang.Object.wait(Native Method)
- waiting on <0x02f996d0> (a java.lang.Object)
at java.lang.Object.wait(Object.java:474)
at org.apache.derby.impl.drda.NetworkServerControlImpl.blockingStart(Net
workServerControlImpl.java)
- locked <0x02f996d0> (a java.lang.Object)
at org.apache.derby.impl.drda.NetworkServerControlImpl.executeWork(Netwo
rkServerControlImpl.java)
at org.apache.derby.drda.NetworkServerControl.main(NetworkServerControl.
java)
"VM Thread" prio=10 tid=0x009c4308 nid=0x740 runnable
"VM Periodic Task Thread" prio=10 tid=0x009d44f8 nid=0xa64 waiting on condition
> 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, 10.2.0.0
> Reporter: Kathey Marsden
> Assignee: Kathey Marsden
> Priority: Critical
> Attachments: javacore.20050622.135027.2491.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
[jira] Resolved: (DERBY-389) With Network Server Database hangs after some time with many connections executing prepareStatement()
Posted by "Kathey Marsden (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-389?page=all ]
Kathey Marsden resolved DERBY-389:
----------------------------------
Fix Version: 10.1.1.1
10.2.0.0
Resolution: Fixed
merged to 10.1 by andrew with r208776
Rajesh please close once verified.
> 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, 10.2.0.0
> Reporter: Kathey Marsden
> Assignee: Kathey Marsden
> Priority: Critical
> Fix For: 10.1.1.1, 10.2.0.0
> 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
[jira] Commented: (DERBY-389) With Network Server Database hangs after some time with many connections executing prepareStatement()
Posted by "Kathey Marsden (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-389?page=comments#action_12314494 ]
Kathey Marsden commented on DERBY-389:
--------------------------------------
Checked in the fix to 10.2 (trunk)
Not marking resolved until backported to 10.1
Sending java\engine\org\apache\derby\impl\sql\conn\GenericLanguageConnectionContext.java
Transmitting file data .
Committed revision 201792.
> 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, 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
[jira] Updated: (DERBY-389) With Network Server Database hangs after some time with many connections executing prepareStatement()
Posted by "Kathey Marsden (JIRA)" <de...@db.apache.org>.
[ 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, 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
[jira] Commented: (DERBY-389) With Network Server Database hangs after some time with many connections executing prepareStatement()
Posted by "Kathey Marsden (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-389?page=comments#action_12314369 ]
Kathey Marsden commented on DERBY-389:
--------------------------------------
I am in the early stages with this very serious stress bug for 10.1. The test is a network server test but the problem is occuring when network server prepares the statement and appears to me to be related to the statement cache. Rajesh is trying to reproduce on embedded. He says he can reproduce this very quickly with his test. 10 mintutes or so and then nothing else can be done with the database all clients hang. He can create other databases, run runtimeinfo etc, so Network server seems ok.
Nothing notable about the log except a lot of expected table not found errors. First wild guess is somethng related to some sort of lock problem when failed statements are handled by the cache.
One of the traces has removeStatement which looks interesting to me.
"DRDAConnThread_7" prio=5 tid=0x0ae97d18 nid=0x988 waiting for monitor entry [0x0bdcf000..0x0bdcf9e4]
at org.apache.derby.impl.sql.conn.GenericLanguageConnectionContext.removeStatement(GenericLanguageConnectionContext.java)
- waiting to lock <0x02fdfcd0> (a org.apache.derby.impl.services.cache.C
lock)
at org.apache.derby.impl.sql.GenericStatement.prepMinion(GenericStatement.java)
/**
* This method will get called if the statement is referencing tables in SESSION schema.
* We do not want to cache such statements because multiple connections can have
* different definition of the same table name and hence compiled plan for one connection
* may not make sense for some other connection. Because of this, remove the statement from the cache
*
* @exception StandardException thrown if lookup goes wrong.
*/
Were there any changes this release related to or that might affect statement caching or does this ring a bell for anyone?
> 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, 10.2.0.0
> Reporter: Kathey Marsden
> Assignee: Kathey Marsden
> Priority: Critical
> Attachments: RTINFO.txt, derby.log, 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
[jira] Commented: (DERBY-389) With Network Server Database hangs after some time with many connections executing prepareStatement()
Posted by "Daniel John Debrunner (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-389?page=comments#action_12314407 ]
Daniel John Debrunner commented on DERBY-389:
---------------------------------------------
Kathey, you may be correct in your guess about removeStatement. The implmentation of that method synchronizes using the statement cache object. It is not required that callers of the cache synchronize on it, all of its methods are thread safe.
Indeed it may cause hangs, as the cache may release its syncrhonization (and expect it to be released) while it waits on its entries to perform actions.
> 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, 10.2.0.0
> Reporter: Kathey Marsden
> Assignee: Kathey Marsden
> Priority: Critical
> Attachments: RTINFO.txt, derby.log, 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
[jira] Updated: (DERBY-389) With Network Server Database hangs after some time with many connections executing prepareStatement()
Posted by "Rajesh Kartha (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-389?page=all ]
Rajesh Kartha updated DERBY-389:
--------------------------------
Attachment: javacore.20050623.150509.22394.txt
RTINFO.txt
derby.log
Please find attached the javacore, server runtime info and derby.log file. I re-ran the test on SLES 9.0 and IBM jdk 1.4.2 with the latest sane build from the 10.1 codeline. The same behaviour is seen with jdk15 also.
--------- Derby Information --------
JRE - JDBC: J2SE 1.4.2 - JDBC 3.0
[/home/rajeshk/derby/lib/derby.jar] 10.1.1.0 beta - (201435)
[/home/rajeshk/derby/lib/derbynet.jar] 10.1.1.0 beta - (201435)
[/home/rajeshk/derby/lib/derbyclient.jar] 10.1.1.0 beta - (201435)
[/home/rajeshk/derby/lib/derbytools.jar] 10.1.1.0 beta - (201435)
------------------------------------------------------
> 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, 10.2.0.0
> Reporter: Kathey Marsden
> Assignee: Kathey Marsden
> Priority: Critical
> Attachments: RTINFO.txt, derby.log, 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
[jira] Commented: (DERBY-389) With Network Server Database hangs after some time with many connections executing prepareStatement()
Posted by "Kathey Marsden (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-389?page=comments#action_12314434 ]
Kathey Marsden commented on DERBY-389:
--------------------------------------
Indeed, removing the sychronization in removeStatement seems to have resolved the problem. So I'll run tests and get this checked into the trunk. I don't have a standalone test for this but Rajesh does run his stress test with every release, so we will have to test that way.
This one probably ought to go into 10.1 branch as well.
> 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, 10.2.0.0
> Reporter: Kathey Marsden
> Assignee: Kathey Marsden
> Priority: Critical
> Attachments: RTINFO.txt, derby.log, 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
[jira] Closed: (DERBY-389) With Network Server Database hangs after some time with many connections executing prepareStatement()
Posted by "Kathey Marsden (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-389?page=all ]
Kathey Marsden closed DERBY-389:
--------------------------------
Rajesh verified with his sytem tests.
> 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, 10.2.0.0
> Reporter: Kathey Marsden
> Assignee: Kathey Marsden
> Priority: Critical
> Fix For: 10.2.0.0, 10.1.1.0
> 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
[jira] Commented: (DERBY-389) With Network Server Database hangs after some time with many connections executing prepareStatement()
Posted by "Kathey Marsden (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-389?page=comments#action_12314319 ]
Kathey Marsden commented on DERBY-389:
--------------------------------------
Rajesh, could you please try a run with your test with a sane debug build and attach the core file and runtimeinfo to this Jira entry?
> 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, 10.2.0.0
> Reporter: Kathey Marsden
> Assignee: Kathey Marsden
> Priority: Critical
> Attachments: javacore.20050622.135027.2491.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