Re: [abc] oopsla outline

Pavel,

There is actually a valid match to the tracematch at changeRoot. This
has showed up consistently all the times that I ran the benchmarks, so
it's fine.

Neil

Pavel Avgustinov wrote:
> The compiled class files are in
> cardinal:~pavel/benchmarks/Jigsaw/{abc.redthistracematch-thisjpid.build,abc.redtracematch-thisjpid.build}.
>
> The exact exception that I saw is this:
>
> java.lang.Exception: Unmatched lock
> at
> ThisLockTraceMatch.tracematch$0$body_real(ReducedThisLockTraceMatch.aj:28)
> at
> ThisLockTraceMatch.tracematch$0$body(ReducedThisLockTraceMatch.aj)
> at org.w3c.jigsaw.http.httpd.changeRoot(httpd.java:885)
> at org.w3c.jigsaw.http.httpd.initializeRootResource(httpd.java:901)
> at org.w3c.jigsaw.http.httpd.start(httpd.java:2081)
> at
> org.w3c.jigsaw.daemon.ServerHandlerManager.<init>(ServerHandlerManager.java:280)
> at
> org.w3c.jigsaw.daemon.ServerHandlerManager.main(ServerHandlerManager.java:500)
> at org.w3c.jigsaw.Main.main(Main.java:15)
>
> Note that to get it to compile with -debug thisJoinPointObject, I had to
> comment out everything from Logger.aj except the definitions of the
> lock() and unlock() pointcuts. The actual logging advice was making use
> of thisJoinPoint.getSignature, which is not possible with
> thisJoinPointObject.
>
> Please don't start any jobs on musketeer without consulting Eric first
> -- he has the lock currently.
>
> - P
>
> Neil Ongkingco wrote:
>
>
>> Can you give me the Jigsaw output directory that you used? It would
>> save me a lot of time compiling. I had problems last Thursday
>> compiling with thisJoinPointObject (it triggered some validate
>> errors), but presumably that's fixed now.
>>
>> Neil
>>
>> Pavel Avgustinov wrote:
>>
>>
>>> Pavel Avgustinov wrote:
>>>
>>>
>>>
>>>
>>>> The only other number that I think I haven't supplied yet is the effect
>>>> of -debug thisJoinPointObject on Jigsaw/LUnInMeth. This is what is
>>>> currently running on musketeer, but I think the numbers Eric needs to
>>>> gether are more important -- hence the statement above.
>>>>
>>>>
>>>>
>>>>
>>> I am somewhat confused by this. While the TM variations that I tried
>>> with -debug thisJoinPointObject did run a couple of seconds faster,
>>> suddenly the tracematches complained about unmatched locks.
>>>
>>> Neil, it would be great if you could find the time to look into this --
>>> check if you can reproduce the 'unmatched lock' messages, and if so,
>>> please try to find out whether the problem is with -debug
>>> thisJoinPointObject, or whether it's a genuine issue with Jigsaw. I hope
>>> it's not the latter, since none of the other tracematch/aspect solutions
>>> ever complained.
>>>
>>> - P
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>
>
>
>
Received on Sun Mar 12 15:08:38 2006