[Ikvm-developers] Deadlock when using NIO socket communication
Brought to you by:
jfrijters
|
From: Christian P. <pro...@op...> - 2012-02-02 11:48:33
|
Hi Jeroen, Hi List, we're using a netty-based communication library (which is based on NIO). Unfortunately we're running into a dead-lock where netty sits in the DotNetSelectorImpl and waits for socket-Events to be dispatched. We've noticed the comment "// TODO there's a race condition here ..." in DotNetSelectorImpl.java which we're probably hitting. Can someone explain what must be done to make the code solid? Best regards, Christian i.A. Christian Prochnow Software Developer Software Development flexible software | for your way of working OPTIMAL SYSTEMS GmbH Cicerostraße 26, 10709 Berlin Tel.: 030 - 8 95 70 80 Fax: 030 - 8 95 70 88 88 E-Mail: pro...@op...<mailto:beu...@op...> Web: www.optimal-systems.de<http://www.optimal-systems.de/> Treffen Sie OPTIMAL SYSTEMS live! Die nächsten Termine finden Sie hier.<http://www.optimal-systems.de/ecm/www/info-center/termine> Lesen Sie den aktuellen OPTIMAL SYSTEMS Newsletter: http://www.optimal-systems.de/news ______________________________________________________ Sitz der Gesellschaft: Berlin HRB 38 560 Amtsgericht Charlottenburg - USt-IdNr.: DE 136 722 551 Geschäftsführer: Karsten Renz |