JavaLaurence Geschrieben May 13, 2013 at 18:50 Share Geschrieben May 13, 2013 at 18:50 Hi, To try and get round the now-and-again problem of my stack locking up (not just crashing, but totally locking up), I plugged my stack's power-supply in an IKEA 2 euro timer switch. Every 6 hours, I let the timer switch cut the power for 30 mins, thus ensuring that my stack is (hard) reset every 6 hours. I thought that the TF API auto reconnect feature would ensure my controlling program would be able to reconnect to my stack every time, albeit after trying for 30 minutes each time the stack power is cut. Unfortunately, my program fails to auto-reconnect most of the time. I'm attaching a screenshot of the Eclipse debugger showing the main thread suspended .. to show what it is doing. The thread always appears to be waiting on a socketMutex. Could this be a bug? Or am I missing something else? Thx. Zitieren Link zu diesem Kommentar Share on other sites More sharing options...
photron Geschrieben May 14, 2013 at 09:46 Share Geschrieben May 14, 2013 at 09:46 There really is a deadlock I can reproduce this problem. It takes about 15min of WIFI downtime to created it. I'm debugging this right now. Zitieren Link zu diesem Kommentar Share on other sites More sharing options...
photron Geschrieben May 14, 2013 at 18:10 Share Geschrieben May 14, 2013 at 18:10 The problem is now fixed in Java bindings version 2.0.7. Zitieren Link zu diesem Kommentar Share on other sites More sharing options...
JavaLaurence Geschrieben May 16, 2013 at 17:55 Autor Share Geschrieben May 16, 2013 at 17:55 Am running the new code, and the problem seems to be gone. Thanks guys! Zitieren Link zu diesem Kommentar Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.