Re: OTListen in OS 9
Re: OTListen in OS 9
- Subject: Re: OTListen in OS 9
- From: Lyndsey Ferguson <email@hidden>
- Date: Fri, 09 May 2003 08:48:34 -0400
Hi all,
I think I have solved the problem, but let me run it by you for
confirmation.
First off, I started up the MPLogging, I wasn't using it before and I forget
why I was not.
Immediately I found that my call to shutdown a my tcp/ip endpoint wrapper
was giving me an assert when I tried to OTMPXCancelSynchronousCalls telling
me that I can not "uncancel". I was sending a 0 as the error parameter. I
changed that to kOTCanceledErr... Then when that returned, I closed the
provider.
Before when I did not send a error with the cancel synchronous calls,
eventually my OS 9 machine would stop processing the messages that the OS X
machine sent. My guess is that the endpoints were still operating or that
somehow the OT section got broken so that only a reboot of OS 9 would reset
the OT layer? Is that a reasonable guess? It seems to have solved that
problem, but I don't want to stamp "bug fixed" on this one until I'm sure.
Thank you for your help. Sincerely
Lyndsey Ferguson
On 5/2/03 6:47 AM, "Quinn" <email@hidden> wrote:
>
At 15:12 -0400 1/5/03, Lyndsey Ferguson wrote:
>
> Does anyone have any suggestions as to why information is being sent to the
>
> a machine and OTListen does not respond?
>
>
After reading your message I'm not sure what works and what doesn't.
>
Is the following correct?
>
>
client server result
>
------ ------ ------
>
OS 9 OS 9 fails rarely
>
OS X OS 9 fails rarely
>
OS 9 OS X works
>
OS X OS X works
>
>
> Here is a sample of the tcpdump. It is set to monitor ports 6020 to 6029 and
>
> a dst (destination address) of 192.168.0.70
>
>
It would be helpful if we also had the packets coming back from the
>
server. After a little post processing, your packet trace looks like:
>
>
client > server: S 4165120739:4165120739(0) win 32768
>
client > server: . ack 2150715765 win 33304
>
client > server: P 0:43(43) ack 1 win 33304
>
client > server: F 43:43(0) ack 1 win 33304
>
>
All we can see is the client to server traffic. Can you post a trace
>
that has both that and the server -> client traffic.
>
>
What you really need to find out is whether OT on 9 has received any
>
asynchronous events (specifically, the T_LISTEN event) and what it's
>
done with them. You can work this out by exploiting the logging
>
facility built into OTMP. You enable logging of systems by calling
>
MPLogSetMask with a particular mask. For OTMP, the types of log
>
point are defined by the following (from "OTMP.h").
>
>
kOTMPWaitRecordLogID = 1,
>
kOTMPNotificationLogID = 2,
>
kOTMPStdActionLogID = 3,
>
kOTMPAPILogID = 4,
>
kOTMPRetriesLogID = 5
>
>
[This need to be turned into a bit mask (1 << logID) when you call
>
MPLogSetMask.]
>
>
You probably should start with kOTMPAPILogID and
>
kOTMPNotificationLogID. The first logs all calls and returns from
>
OTMP routines, and will tell you what your thread is doing. The
>
second logs all OT event notifications. Once you've figured out
>
roughly what's going wrong, you can enable more log points to narrow
>
down the debugging.
>
>
S+E
--
Lyndsey D. Ferguson
Software Engineer
Nemetschek N.A., Inc.
email@hidden
--
_______________________________________________
macnetworkprog mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/macnetworkprog
Do not post admin requests to the list. They will be ignored.