- see footer for list info -<
Two issues I can think of:
1) Identical instance names on different machines.
2) There is a missing attribute in jrun.xml (which Adobe know about).
Make sure you add the following to the ProxyService service
<attribute name="bindToJNDI">true</attribute>
Andy
Aitor Ibarra wrote:
- see footer for list info -<
I've also posted this on the Adobe forums:
http://www.adobe.com/cfusion/webforums/forum/messageview.cfm?catid=143&threa
did=1150566&enterthread=y#4119603
Our 2 node cluster isn't working properly. The instances can't see each
other properly (they show "Network Error" in CF Admin> Enterprise> Instance
Manager). The upshot of this is that sessions are not being shared / failed
over.
Background...
- each server has two network interfaces. One of these is used for NLB, the
other for all other network traffic (including the CF cluster). The two NICs
are connected to different IP subnets (NLB is 10.0.0.x , LAN is
192.168.2.x). These are also seperate ethernets. I think the 'primary'
interface is the NLB one; i.e. it is the one listed first in ipconfig.
- CF 7 Enterprise (multi instance) installed on both servers (which are
running Windows 2003 Standard).
- New instance created on each server and bound to all IIS sites
- Instances registered in CF Admin, cluster created
- Windows NLB set up. We had some problems with this that were probably down
to our router. Now working fine in both Unicast and Multicast modes, but we
have kept on Unicast.
- Now the CF instances can't see each other.... so can't share session
variables
- the links to CF admin for each instance work, however, so it's not a basic
networking issue like not being able to ping/browse each other
I have tried adding the servers as unicast nodes in jrun.xml for each
instance as suggested here: http://www.adobe.com/go/26e04a0d
I have also manually edited security.properties on both servers as the
symptoms are the same as described here:
http://www.adobe.com/cfusion/knowledgebase/index.cfm?id=f23aa5ca
The only thing I haven't tried is swapping interfaces so that the LAN
interface is "primary". Does this really matter? Can this be done without
swapping cables by changing interface metrics in windows? Is it possible
that CF is trying to communicate through the NLB interface?
_______________________________________________
For details on ALL mailing lists and for joining or leaving lists, go to
http://list.cfdeveloper.co.uk/mailman/listinfo
--
CFDeveloper Sponsors:-
- Hosting provided by www.cfmxhosting.co.uk -<
- Forum provided by www.fusetalk.com -<
- DHTML Menus provided by www.APYCOM.com -<
- Lists hosted by www.Gradwell.com -<
- CFdeveloper is run by Russ Michaels, feel free to volunteer your help -<
_______________________________________________
For details on ALL mailing lists and for joining or leaving lists, go to
http://list.cfdeveloper.co.uk/mailman/listinfo
--
CFDeveloper Sponsors:-
- Hosting provided by www.cfmxhosting.co.uk -<
- Forum provided by www.fusetalk.com -<
- DHTML Menus provided by www.APYCOM.com -<
- Lists hosted by www.Gradwell.com -<
- CFdeveloper is run by Russ Michaels, feel free to volunteer your help -<
