Re: Re: xAP Stopped Working

["Martyn Wendon" <martynwendon@xxxxxxxxxxx>]

I've noticed that sometimes a dodgy xAP message will cause the xFx hub
to
momentarily "give up" listening on the port:

Event Type: Error
Event Source: xFx Express Hub
Event Category: None
Event ID: 0
Date:  10/01/2009
Time:  18:57:06
User:  N/A
Computer: AHSMEDIASERVER
Description:
2009-01-10 17:57:05,994 ersp.xfxe.Hub ERROR Hub message loop socket
exception (MessageSize): A message sent on a datagram socket was larger
than
the internal message buffer or some other network limit, or the buffer used
to receive a datagram into was smaller than the datagram itself

During this moment if another app attempts to start listening on the port
it
can grab the port.

Then, when the xFx hub recovers, it can't and will fill the event log with
retry errors every minute or so:

Event Type: Error
Event Source: xFx Express Hub
Event Category: None
Event ID: 0
Date:  10/01/2009
Time:  18:57:50
User:  N/A
Computer: AHSMEDIASERVER
Description:
2009-01-10 17:57:50,793 ersp.xfxe.Hub ERROR Failed to bind receive socket
to
192.168.1.9:3639 (AccessDenied).

If you then stop the app that grabbed the port, xFx will re-grab it.

It appears that some apps keep retrying to grab the port even though they
may have initially been hub clients.


Hope this helps,

Martyn




----- Original Message -----
From: "Marc Fuller" <groups@xxxxxxx>
To: <xap_automation@xxxxxxx>
Sent: Friday, July 24, 2009 4:17 PM
Subject: Re: [xap_automation] Re: xAP Stopped Working


> Hi Edward,
>
> I think it's sorted, but not sure HOW it got sorted or what caused
that
> error.
>
> I basically un-installed everything (including Homeseer, Redrat,
Hubs...
> the lot) and started from scratch.
>
> I installed the new Hub first, then RedRat, then Homeseer... now this
is
>  where it gets a tad weird. I wrote a VBS file to stagger the loading
> to make sure the hub loads first, then RedRat, then Homeseer.
>
> I thought that would fix it, but then when starting the hub I started
> getting the AddressAlreadyInUse error. After running TCPVIEW it shows
> that the RedRat process was using port 3639. Now I know for definite
> that the hub loaded before the redrat.
>
> So, I restarted, just loading the hub and not the rest. I still got
the
> error!!! TCPView didn't show 3639 in use by anything. Now I think this
> was being caused because I noticed there is a service version of the
hub
> as well as the command line version. I didn't realize there was a
> service version, so was loading the command line version.
>
> Anyways, after sorting that, and running the xAP viewer, I could see
> everything was working. Loaded the RedRat and Homeseer.. all working
> lovely.. messages flowing, redrat working.. great.
>
> Load TCPView and it shows Redrat as the process listening on port
3639!!!
>
> Makes no damn sense to me, but since it's working, I backed away
slowly
> from the server, then ran !
>
>
> Edward Pearson wrote:
>>
>>
>> Did this get sorted.
>>
>>
>>
>> It?s odd since the normal error in the case that another
application is
>> using the port is
>>
>> Failed to bind receive socket to 192.168.1.14:3639
(AddressAlreadyInUse)
>>
>>
>>
>> *From:* xap_automation@xxxxxxx
>> [mailto:xap_automation@xxxxxxx] *On
Behalf Of *Brett England
>> *Sent:* 21 July 2009 14:49
>> *To:* xap_automation@xxxxxxx
>> *Subject:* RE: [xap_automation] Re: xAP Stopped Working
>>
>>
>>
>>
>>
>> Use this to determine what is listening on this port already.
>>
>> http://technet.microsoft.com/en-us/sysinternals/bb897437.aspx
>> <http://technet.microsoft.com/en-us/sysinternals/bb897437.aspx>
>>
>>
>>
>>
------------------------------------------------------------------------
>>
>> *From:* xap_automation@xxxxxxx
>> [mailto:xap_automation@xxxxxxx] *On
Behalf Of *Marc Fuller
>> *Sent:* 21 July 2009 14:46
>> *To:* xap_automation@xxxxxxx
>> *Subject:* Re: [xap_automation] Re: xAP Stopped Working
>>
>>
>>
>>
>>
>> Very very strange.
>>
>> I've unloaded everything. I've rebooted the server making sure
*nothing*
>> loads automatically.
>>
>> I then run the Hub and still get the error! I have no clue what
could be
>> grabbing it... apart from the IP address thing, nothing has
changed?!?!
>>
>> Is there way to find out what's using the port? I have a vague
>> recollection of a command to see what ports are being used by what
>> process.. something like netsh somethingorother?
>>
>> Cheers
>>
>> Marc
>>
>> Kevin Hawkins wrote:
>>  >
>>  >
>>  > Almost certainly something else has already acquired the hub
port
>>  >
>>  > K
>>  >
>>  > Marc Fuller wrote:
>>  > >
>>  > >
>>  > > OK, getting somewhere. The Redrat hub never gave me any
errors.
>>  > >
>>  > > Once I installed the new hub, I had assumed it was
working, but
>> didn't
>>  > > notice this little error...
>>  > >
>>  > > "Failed to bind receive socket to
172.16.xx.xx:3639 (AccessDenied)"
>>  > >
>>  > > What !! Why the hell would I be getting an access
denied?
>>  > >
>>  > > Any help appreciated.
>>  > >
>>  > > Marc
>>  > >
>>  >
>>  >
>>
>>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>



------------------------------------