Re: [xmlvm-users] Exception occurs when an alternate thread finishes

[Panayotis K. <pan...@pa...>]

On Jul 1, 2011, at 9:25 PM, Paul Poley wrote:

> I don't see all the relevant snippets, but believe I know what's happening, and this is expected behavior.  The short of it is that when you call "obj.notifyAll()", you should already be synchronized on "obj", which it appears you are not.  This is true in Java as well as XMLVM, whether using the C or Obj-C version.  Note that I am saying that "notifyAll" needs to be synchronized, but so does the "wait".
> 
> Your stacktrace says "notifyAllx", which I assume should be "notifyAll".  You are using the Obj-C backend, so that has been the case for a while.  The wait, notify, etc. for the C backend has only recently been implemented.
> 
> Thanks,
> Paul



Paul, 
This is also a question from my side.
The reason this "x" appears at the end of the notifyAll in ObjC is because this piece of code is passed through the "trimmer" extension, which replaces everywhere the "__" characters to "x".
Is there any reason that the name of the function should remain "notifyAll__" and not change to something different, but compatible across the whole code?


Steven,
if you just want a wuick hack to make things a bit more relaxed, edit xmlvm.properties file and set trimmer to false