The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024


[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

Re: Re: xAP Stopped Working



Hi Kevin,

I've had problems in the past with:

Squeezecenter plugin (no biggie since I just hacked the perl source to
remove the hub bit)
KCS e-mail sender
KCS mail monitor (both KCS apps I have to start manually after the hub as I
can't see a way to stop them grabbing the port)
Most of James' MI4 apps (some have a "UseHubPort" param in the
settings file
that stops them and James has kindly made me a couple of builds of apps
with
the hub stuff disabled (Blue and Jabber I think it was)
Kevin T's Current Cost connecter (I might be on an older build though,
maybe
the newer one doesn't do it)


I think there's some more, but I can't recall them all right now.

To be fair it's not a major issue as most of the apps run forever so once
the magic start sequence is achieved then there's no problem.  It's just
when "odd stuff" happens like the hub dropping the port and
another app
grabbing it that it's a pain as it then becomes a bit of a fight to
re-establish everything in it's correct place.


Cheers,

Martyn


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


> Early on the hub was always the thing people didn't understand or
forgot
> and so to 'help' people created applications that would run standalone
> without a hub,  or as a hub themselves should no other app be using
port
> 3639.  This was to make it all easier or so we thought... actually it
> just made it harder to diagnose issues like this.  Multiple networks
> make things even more challenging, preference files have helped quite
a
> bit. Hence now we discourage any app using the hub port and things are
> becoming more straighforward.
>
> AFAIK the only current application that does automatically adopt a hub
> role is Viewer,  as this is often used in a diagnostic role (it
clearly
> states its hub role in the title bar should it adopt this).
>
>   K
>
> Martyn Wendon wrote:
>>
>>
>> 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
>> <mailto:yahoogroupskh%40googlemail.com>>
>> To: <xap_automation@xxxxxxx
>> <mailto:xap_automation%40yahoogroups.com>>
>> 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
>> >
>> >
>> >
>>
>>
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>



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


xAP_Automation Main Index | xAP_Automation Thread Index | xAP_Automation Home | Archives Home

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.