Before bringing Server1 back on line you should stop all T24 processes The switch to 'Server2' , when Server1 is taken offline, is a 'one way process'
So existing processes will continue to use 'Server2' ( only ) for locking Any new processes, started after Server1 is brought back on line, will attempt to use BOTH Server1 and Server2 in resilient mode, leading to 'lock contention' and 'mismatches' On Dec 7, 6:25 am, "www.t24all.com" <[email protected]> wrote: > Hi, > > We have installed jDLS as distrubuted lock listener service mode (jDLS > -ibD). > > We have 2 application servers Server1 and Server 2 > > Server 1 is the primary server and Server 2 is the secondary server > > As part of maintenance activity we will shutdown the Server 1 for few > hours. During those hours Server 2 will take control the jDLS and all > the locks are managed by Server 2. > > After few hours once the Server 1 is brought up, the locks are not > getting released from Server 2. It goes to a dead lock situation. > > Any ideas why jBASE jDLS is behaving like this? Any suggestions... > > Thanks & Regards -- Please read the posting guidelines at: http://groups.google.com/group/jBASE/web/Posting%20Guidelines IMPORTANT: Type T24: at the start of the subject line for questions specific to Globus/T24 To post, send email to [email protected] To unsubscribe, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jBASE?hl=en
