11-15-2012 02:46 PM - edited 03-17-2019 02:47 PM
Hi,
We have Jabber Windows 9.1 installed with a primary and secondary Microsoft AD server configured in the jabber-config.xml file.
Everything works ok with either the primary or secondary AD server configured as 'Primary' but Jabber does not failover to the configured secondary in the event that the primary is down. The 'show connection status' shows that the primary directory server is unavailable but does not even attempt to connect to the secondary, even after exiting Jabber fully and clearing the cache files, Jabber still tries to connect back to the primary server.
Has anyone experienced this issue? This is happening on all of our PCs which are a mix of laptops and desktops, Win7 and WinXP. We have also tried rolling back to Jabber 9.0.5 and still have the same issue.
Thanks
11-20-2012 04:05 AM
Hi,
This sounds like a defect. We will test this case and open a defect if required.
Thanks,
Maqsood
11-23-2012 10:01 AM
Hi,
This is reproducible in our lab. A defect has been raised to track this.
CSCud32913: Jabber not failing over to secondary LDAP when primary is not reachable
Thanks for reporting this bug.
Maqsood
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide