Hi Thomas, you automatically get connected to the correct Landscape (primary/failover). So if the primary is down and you create a ModelDomain Object its connected to the secondary. But if you loose the connection to the primary while you have the instanciated Object, it wont switch automatically to the secondary, because the corba connection is still made to the primary. Thats where this monitor you can implement comes into play. It polls every x seconds and then notices that the primary is not there anymore.
best regards, Mike Am 21.09.2011 14:47, Thomas Klöber schrieb: > Mike, > > Am 21.09.2011 14:28, schrieb Mike Joost: >> I am using the CORBAObjectMonitor to Monitor the connection to a Spectrum >> Setup >> with Failover (Secondary). >> When I turn the Primary off, the failover takes place and my implementation >> of >> the CORBAObjectMonitorListener gets its "connectionEstablished" method >> called. >> In this method I reconnect the to the ModelDomain and as planned afterwards >> I am >> connected to the secondary. >> >> But if I turn on the primary again, the method does not get called an so my >> application stays on the secondary permanently. >> Only if I turn off the secondary Sectrum server I get a call of the >> "connectionEstablished" and so I can switch back to the primary. >> >> Does anyone had the same Problem/Solution for this? Is this working as >> intended? > do you actually have to connect to the secondary "by hand"? If my memory > serves me right this should be done automatically when the primary goes down. > But I could be wrong, it's been a while that I wrote this kind of stuff... > > Thomas > --- To unsubscribe from spectrum, send email to [email protected] with the body: unsubscribe spectrum [email protected]
