On Tue, 23 Mar 2010 23:52:13 -0700
Michael Hunter <michael.hunter at oracle.com> wrote:
> On Tue, 23 Mar 2010 10:32:15 -0700
> Erik Nordmark <Erik.Nordmark at Sun.COM> wrote:
>
> >
> > I seem to have had syslog log nwam stuff forever.
> > I've attached the log file (just look at today's stuff at the end).
> >
> > From running tail -f on the log file it seems like there might be
> > correlation between the popups and the periodic rescan.
> >
> > Note that I see 52 results here (they have quite a number of APs.)
> > But the log file doesn't seem to hint while nwam-manager does a popup.
> > How can I debug nwam-manager?
>
> I don't know how you debug nwam-manager.
>
> There is a mechanism in the b133 nwam that resets queue used between
> nwam and nwam-manager if one appears unresponsive. In the log you show
> we are just getting pounded with rescan requests. I wonder if the
> length of the AP list together with the scan rate is just causing us to
> fall far enough behind that one side declares the other dead
> continually?
>
> I'd be really interested in how b135 deals with this.
Ignore this. I read the log thinking about the Phase 1 codebase but
then went back and saw your 133 comment.
Michael
