<html><body>
<p><font size="2" face="sans-serif">Ran into some technical difficulties with the posting to the mailing list. First, the attached logs were too big & weren't accepted, and then for some reason, even with smaller logs, it added the attachment, but lost the text to go with the logs. </font><br>
<br>
<font size="2" face="sans-serif">So .... Here is the text to go with the previous logs that were updated. (corbaTcpTraces-0001.zip)</font><br>
<br>
<font size="2" face="sans-serif">-----------------------------------------------------------------------</font><br>
<br>
<font size="2" face="sans-serif">Yes, the Client & Server are on the same machine.</font><br>
<font size="2" face="sans-serif">Attached are the client & server traces with </font><tt><font size="2">traceLevel 40 traceTime 1 traceThreadId 1</font></tt><font size="2" face="sans-serif">, and the tcpdump as well.</font><br>
<br>
<font size="2" face="sans-serif">Here are the interesting points in trace.</font><br>
<br>
<font size="2" face="sans-serif">client log (line 177 - time = 13:36:43.433568) send LocateRequest</font><br>
<br>
<font size="2" face="sans-serif">tcp trace (line 18 - time = 13:36:43.433590) locateRequest packet</font><br>
<br>
<font size="2" face="sans-serif">server log (line 180 - time = 13:36:43.433633) input Message received // <<< this is the suspect packet, that I think started out as the locateRequest. if I'm reading it right, the GIOP internal message size (261 bytes) is larger then the tcp packet size (38).</font><br>
<br>
<font size="2" face="sans-serif">original logs too big, so they had to be truncated. full logs available upon request.</font><br>
<br>
<font size="2" face="sans-serif">Thanks, </font><br>
<br>
<font size="2" face="sans-serif">Brad Fawcett</font></body></html>