Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Timer assert problem caused by recent commit
27-01-2015, 01:33 PM
Post: #4
RE: Timer assert problem caused by recent commit
(27-01-2015 12:14 PM)simoncn Wrote:  I was aware of this and this is why I linked to this other commit in my original post.

So you did - apologies. Not sure how I managed to completely misunderstand your post - it was perfectly clear...

(27-01-2015 12:14 PM)simoncn Wrote:  This is a serious problem for MinimServer users because it causes the server to crash. From your response, I'm not what (if any) change to ohNet you think is needed to stop this happening. Have there been any mDNS fixes related to this issue since version 1.1.1452?

If the problem is caused by mDNS, is it possible for MinimServer to disable mDNS? Is mDNS always used or is it used on some platforms and not others?

There is no fix available at present. mDNS code will always be linked into a binary but should default to being disabled (so never run). You should have to explicitly enable it. You'd do this in Java by calling InitParams.setDvEnableBonjour(). Can you check whether this is called from MinimServer startup please?
Find all posts by this user

Messages In This Thread
RE: Timer assert problem caused by recent commit - simonc - 27-01-2015 01:33 PM

Forum Jump: