Re: Progressively all threads go into deadlock
Re: Progressively all threads go into deadlock
- Subject: Re: Progressively all threads go into deadlock
- From: Mike Schrag <email@hidden>
- Date: Tue, 19 Feb 2008 14:33:39 -0500
Monitoring Thread:
[1] java.net.SocketOutputStream.socketWrite0 (native method)
[2] java.net.SocketOutputStream.socketWrite
(SocketOutputStream.java:92)
[3] java.net.SocketOutputStream.write (SocketOutputStream.java:136)
[4] java.io.BufferedOutputStream.flushBuffer
(BufferedOutputStream.java:65)
[5] java.io.BufferedOutputStream.flush (BufferedOutputStream.java:
123)
[6] com.mysql.jdbc.MysqlIO.send (MysqlIO.java:3,119)
[7] com.mysql.jdbc.MysqlIO.sendCommand (MysqlIO.java:1,818)
[8] com.mysql.jdbc.MysqlIO.sqlQueryDirect (MysqlIO.java:1,961)
[9] com.mysql.jdbc.ConnectionImpl.execSQL (ConnectionImpl.java:2,543)
[10] com.mysql.jdbc.PreparedStatement.executeInternal
(PreparedStatement.java:1,737)
[11] com.mysql.jdbc.PreparedStatement.execute
(PreparedStatement.java:998)
[12]
com
.webobjects
.jdbcadaptor.JDBCChannel._bindInputVariablesWithBindingsAndExecute
(JDBCChannel.java:265)
If you dump threads multiple times, does this ever go away? If it
doesn't, it says to me that you have a hung database connection or a
very expensive db operation that is not returning. This is a
legitimate lock on your object store and will block all other db
operations on your object store coordinator. You can switch to
pooling if this is actually behaving correctly, but i suspect it's not
and you should solve this problem before introducing others.
ms
On Feb 19, 2008, at 2:17 PM, Fabrice Pipart wrote:
Thanks for the answer Chuck !
I ll add the stack traces below.
We never lock anything else than EOEditingContext ... (ERXEC
actually).
We are thinking about a different thing : could it be a memory
problem ?
We are allocating "only" 256 Mb and are dealing concurrently with
thousands of objects in background threads, components and
wolongresponses tasks....
Could it lead to a deadlock ?
Is there anything special to do with EOObjectStoreCoordinator?
I saw properties about pools of EOObjectStoreCoordinator, are they
useful in my case?
Here are some of the stack traces (I reduced the size of traces a
bit and removed the threads sleeping, if you really want all
threads, tell me) :
<snip>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden