Hello, The listener process usually spawns new lock server process to handle each client lock process from secondary server. But for local requests there won’t be any new process spawned as the requests are local. It’s totally internal and can’t be changed.. Try to check if there was any change made in the new releases. Not sure about it though!
You can actually increase the size jDLS.As it can hold upto 1Lakh records. E.g., jDLS -ibs 100000,30 The above allows us to lock one lakh records in 30 groups. By doing this you can overcome this issue.And also the system probably wont hang. Hope this helps. Regards, Manasa Urs On Dec 7, 1: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
