[ciao-users] DAnCE: Plan Launcher throws CORBA MARSHAL exception

[William R. Otte]

On 23 Mar 2018, at 12:02, Haidinger, Holger wrote:

> Hi Will,
>
> first of all, thank you very much for your quick response!
>
> We turned up the logging by setting the following environment 
> variables:
>
> set DANCE_LOG_LEVEL=10
> set DANCE_TRACE_ENABLE=1
>

Trace is a bit much, there’s a ton of overhead and you probably 
don’t need function call tracing at this point.


> With these settings the MARSHAL exception occurred always (on faster 
> machines).
>

That’s a good indication that you’re seeing a race condition of some 
kind, increasing the logging changes the timing of events.


> Did you mean these settings or did we miss something?
>

Are you redirecting the log to a file?  My recollection from when I 
implemented that is that should be available as a feature.  That should 
have marginally less runtime impact over printing to stderr and then 
possibly redirecting to a file, as that will incur fewer context 
switches and will buffer less (if my recollection is correct about the 
implementation of the logger).

Did you see any indication that the exception is coming from the node 
infrastructure instead of the domain infrastructure?

If you’re seeing indication that it’s coming from the node level, 
also consider setting CIAO_LOG_LEVEL.

Hth,
/-Will