Re: Re: xAP Stopped Working

["Martyn Wendon" <martynwendon@xxxxxxxxxxx>]

I'd love to see all xAP apps *without* hub functionality as it's a
real pain
to get things like load order of services / applications correct!

And on Windows Server 2003 (not sure about later versions) it's even worse
as you can bind to the same port across multiple IP addresses which creates
further issues e.g. if one binds to 3639 on 127.0.0.1, another to 3639 on
0.0.0.0, another on 192.168.0.1, etc.

Martyn

----- Original Message -----
From: "Kevin Hawkins" <yahoogroupskh@xxxxxxx>
To: <xap_automation@xxxxxxx>
Sent: Friday, July 24, 2009 4:55 PM
Subject: Re: [xap_automation] Re: xAP Stopped Working


> That looks like maybe an older (xAPV1.2) hub giving that message.
> 'KCSoftware'
> The length of the UID filed was increased in xAP v1.3.
> You are using one of the latest hub builds downloaded from Edwards
site
> aren't you ?  An older hub will drop all the newer xAP v1.3 messages
and
> so only some apps will traverse the hub.
>
> I am not sure if the 'what's using the port' app you downloaded will
> correctly identify services that are bound to UDP listening ports ,
and
> so it may not correctly show a port as in use.  Bear in mind that all
> xAP applications send to UDP port 3639 but only one xAP application
can
> listen on that port (the hub).
>
> The listening port is listed within the heartbeat sent by each
> application and should be different for every application on the same
PC
> (and only the hub should indicate 3639).  If the apps are on different
> PC's then you may legitimately have duplicate ports.  3639 could be
used
> by a different apps , one per machine , although they should really be
> hubs.  We now always recommend a hub on every xAP machine as it is not
a
> requirement to provide fallback hub functionality within a xAP
> application, in fact it's discouraged.
>
> K
>
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>



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