Hi !
ok, I guess I was wrong in my last message.
The stack traces:
"QThread-13-0" prio=1 tid=0x0x81f5688 nid=0x18cf waiting for monitor
entry [bcfff000..bcfff8b0]
at
freenet.node.StandardMessageHandler$Ticket.received(StandardMessageHandler.java:131)
- waiting to lock <0x445bad48> (a freenet.node.StateChain)
at
freenet.node.StandardMessageHandler$Ticket.access$200(StandardMessageHandler.java:117)
at
freenet.node.StandardMessageHandler.handle(StandardMessageHandler.java:64)
at freenet.Ticker$Event.run(Ticker.java:175)
at freenet.thread.QThreadFactory$QThread.run(QThreadFactory.java:297)
do not indicate a dead-lock, but simply many messages for a Ticket to be
worked on. Since this causes many threads to be blocked, I would change
this code, so only one thread works on the method calls (and the other
messages are stored in a list) ... Or is it a bug, that so many messages
are waiting in the first place ?
Niklas
_______________________________________________
Devl mailing list
Devl at freenetproject.org
http://lists.freenetproject.org/mailman/listinfo/devl