<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hi,</p>
<p>The log is not telling when exactly the marshal exception
happens, probably you need to enable the ORB Logging at level 10
to get enough details to have any idea of what is happening<br>
</p>
Regards,<br>
<pre class="moz-signature" cols="72">Johnny Willemsen
Remedy IT
Postbus 81 | 6930 AB Westervoort | The Netherlands
<a class="moz-txt-link-freetext" href="http://www.remedy.nl">http://www.remedy.nl</a>
</pre>
<div class="moz-cite-prefix">On 04/06/2018 05:40 PM, Haidinger,
Holger wrote:<br>
</div>
<blockquote type="cite"
cite="mid:50b0b06f-c212-4b23-8382-0dbc62643a46@redlogix.de">
<pre wrap="">Hi Will,
we are using the ACE logging facility which is redirecting the log to a file.
I have attached a log file as a ZIP archive. Hopefully this will work on the mailing list.
The exception occurred at the end of the file. CIAO_LOG_LEVEL was not used.
Best regards
Holger
-----Ursprüngliche Nachricht-----
Von: ciao-users [<a class="moz-txt-link-freetext" href="mailto:ciao-users-bounces@list.isis.vanderbilt.edu">mailto:ciao-users-bounces@list.isis.vanderbilt.edu</a>] Im Auftrag von William R. Otte
Gesendet: Freitag, 23. März 2018 19:15
An: CIAO Users Mailing List
Betreff: Re: [ciao-users] DAnCE: Plan Launcher throws CORBA MARSHAL exception
On 23 Mar 2018, at 12:02, Haidinger, Holger wrote:
</pre>
<blockquote type="cite">
<pre wrap="">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
</pre>
</blockquote>
<pre wrap="">
Trace is a bit much, there’s a ton of overhead and you probably don’t need function call tracing at this point.
</pre>
<blockquote type="cite">
<pre wrap="">With these settings the MARSHAL exception occurred always (on faster
machines).
</pre>
</blockquote>
<pre wrap="">
That’s a good indication that you’re seeing a race condition of some
kind, increasing the logging changes the timing of events.
</pre>
<blockquote type="cite">
<pre wrap="">Did you mean these settings or did we miss something?
</pre>
</blockquote>
<pre wrap="">
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
_______________________________________________
ciao-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:ciao-users@list.isis.vanderbilt.edu">ciao-users@list.isis.vanderbilt.edu</a>
<a class="moz-txt-link-freetext" href="http://list.isis.vanderbilt.edu/cgi-bin/mailman/listinfo/ciao-users">http://list.isis.vanderbilt.edu/cgi-bin/mailman/listinfo/ciao-users</a>
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
ciao-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:ciao-users@list.isis.vanderbilt.edu">ciao-users@list.isis.vanderbilt.edu</a>
<a class="moz-txt-link-freetext" href="http://list.isis.vanderbilt.edu/cgi-bin/mailman/listinfo/ciao-users">http://list.isis.vanderbilt.edu/cgi-bin/mailman/listinfo/ciao-users</a></pre>
</blockquote>
<br>
</body>
</html>