On Feb 19, 2008, at 8:33 PM, Chuck Hill wrote:
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
On Feb 20, 2008, at 5:33 AM, Fabrice Pipart wrote:
On Feb 19, 2008, at 8:33 PM, Chuck Hill wrote:
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,
Hi Fabrice,
How many stacks have you created for your multithreaded application?
Are you using only one? Then you may have a contention as EOF is
single threaded. Can you elaborate a little bit more on how your
application works?
Cheers
Pierre
--
Pierre Frisch
[EMAIL PROTECTED]
On Feb
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
.
It happens randomly. Progressively all threads go into deadlock.
They all block on the same method :
[1] sun.misc.Unsafe.park (native method)
I cannot understand why :-(
We use autolock from Project Wonder with the four magic lines in
Properties.
Both the WorkerThreads and the Background threads block
