Activating jbase level locking

[Pratosh]

Hi,
At present jRLA is not active in our environment. But we intend to do
that for some testing.
Can someone please outline the step by step procedure required to do
this?
Also, how do we set the different parameters for jRLA like max number
of locks required and other stuff ..

I searched through the jBase documentation and the knowledgebase at
the site, but couldn't find anything.

I will appreciate of someone can help me out.

Thanks

[uiterwyk]

Unless you are running jBase 3.4.x, it is really recommended that you
use jDLS instead of jRLA.

For "practical" purposes, they will provide the same functionality and
use almos all the same options.

For 3.4, see here for Documentation on jRLA
http://www.jbase.com/knowledgebase/manuals/3.0/30manpages/man/sup22_JRLA.htm

for 4.1.x or 5.1.x go to your documentation, which is usually in:
$JBCRELEASEDIR/Help/docs/'jBASE Distributed Locking.doc'

In either case, when you start it, you want to use the options -ib so
that it runs as a background task and assumes control.

HTH,

Robert

[Pratosh]

Hi,
Thanks for the help .. I will try it out ...

On Oct 10, 10:17 am, uiterwyk <rob...@uiterwyk.net> wrote:
> Unless you are running jBase 3.4.x, it is really recommended that you
> use jDLS instead of jRLA.
>
> For "practical" purposes, they will provide the same functionality and
> use almos all the same options.
>

> For 3.4, see here for Documentation on jRLAhttp://www.jbase.com/knowledgebase/manuals/3.0/30manpages/man/sup22_J...

[Mujtaba Khan]

Hi,

  Just wana Know that is JDLS not use in Multi server Environment means for single T24 Server we use jRLA and for multi server we use jDLS , Kindly Correct me if i am wrong.

Regards

Mujtaba Khan

[Thiag Jayachandran]

Hi

 

I think the concept of jDLS is misunderstood here

 

jDLS was basically developed to replace NFS locking when we deploy T24 in multiple application server and its nothing but distributed jRLA locking mechanism. The fundamental code of jRLA still exists in jDLS additionally it has an option to listen for locks from other jbase server as well (lock listener)

 

If you are happy with NFS locking itself then you can continue to use NFS when running multiple app servers, but if the client says NFS might be a single point of failure then jDLS can be used to overcome this limitation

 

even in a single server setup you can use jDLS but its an additional overhead (opening and closing sockets for every lock requests), in a single server environment its better to use OS locks or run jDLS using -ibD option (which inturn tells jbase to use OS locking)

 

regards

Thiag

[Jim Idle]

On Tue, 2008-10-14 at 14:49 +0200, Thiag Jayachandran wrote:

Hi

 

I think the concept of jDLS is misunderstood here

 

If you are happy with NFS locking itself then you can continue to use NFS when running multiple app servers, but if the client says NFS might be a single point of failure then jDLS can be used to overcome this limitation

Oooooo no, no, no, no, no, etc. Never use NFS locking for this, you are just asking for trouble with both performance and reliability. NFS should be sent to big computer software graveyard in the sky, but NFS locking should have been shot at birth ;-) Use the distributed lock daemon if you have more than one server.

 

even in a single server setup you can use jDLS but its an additional overhead (opening and closing sockets for every lock requests),

Well, if it is opening a connection to the lock server for every lock request, then it is severely broken and will not scale properly [Greg: didn't you write this before you left? You're fired!].

It should be making a persistent connection, which it reconstitutes if it is dropped and the server should time it out after a certain period of inactivity (to conserve server resources). Any network stack worth its salt should detect local to local socket connections and optimize the protocol stacks out of the equation, so it should not be a bad option (in fact it is faster than other IPC mechanisms on some systems).

in a single server environment its better to use OS locks or run jDLS using -ibD option (which inturn tells jbase to use OS locking)

Depends what you are doing, what kind of reporting you want and what the locking load is (an application like T24 probably uses thousands of locks).

Jim

 

regards

Thiag

[pat]

You are correct.

jDLS is for use with Multiple Application Servers

jRLA should be used for single machine scenarios on jBASE 3.4, jBASE
4 and jBASE 5

Pat.

On 14 Oct, 08:35, "Mujtaba Khan" <mujtaba...@gmail.com> wrote:
> Hi,
>
>   Just wana Know that is JDLS not use in Multi server Environment means for
> single T24 Server we use jRLA and for multi server we use jDLS , Kindly
> Correct me if i am wrong.
>
> Regards
>
> Mujtaba Khan
>
> On Fri, Oct 10, 2008 at 8:17 PM, uiterwyk <rob...@uiterwyk.net> wrote:
>
> > Unless you are running jBase 3.4.x, it is really recommended that you
> > use jDLS instead of jRLA.
>
> > For "practical" purposes, they will provide the same functionality and
> > use almos all the same options.
>
> > For 3.4, see here for Documentation on jRLA
>

> >http://www.jbase.com/knowledgebase/manuals/3.0/30manpages/man/sup22_J...

[Mujtaba Khan]

Hi,

  thx for the Explanation. got the Point

Regards

Mujtaba khan