Launching TAFJ Lock Manager
You can launch TAFJ Lock Manager in various modes using the following procedure.
- Go to the bin directory of your TAFJ installation and type the command below.
> tLockManager -i
RecommendationsIf you want to run in background mode then you can remove -i)
If you are using the lock manager in PROCHASH, then start the lock manager with the option –m2 as shown in the command below.
> tLockManager -i -m2
If you are running the lock manager in background, then you can pass specific JVM argument with the option –jvm as shown below.
> tLockManager -i -jvm="-Xms256M –Xmx2048M -XX:MaxPermSize=256M"
If you are using the lock manager in interactive mode, then you can pass the options –verbose and then –debug. You will have all the information in the screen about what’s going on in the tLockManager. The options –verbose and –debug adds an overhead of about 5% and 11% on the performance respectively.
> tLockManager -i -m2 --verbose
> tLockManager -i -m2 --verbose --debug
If you want to monitor JMX MBean of the tLockManager, then you need to specify the option –jmx as shown below.
> tLockManager -i -m2 --jmx
The Output will be as follows:
[1495013022605] [INFO ] Start tLockmanager PROCHASH (mode 2)[1495013022605] [Pid=4600 Host=10.41.2.29 Port=7425 Mode=PROCHASH][INFO ] tLockManager started.[1495013022605] [Pid=4600 Host=10.41.2.29 Port=7425 Mode=PROCHASH][INFO ] tLockManager JMX is set to true[1495013022605] [Pid=4600 Host=10.41.2.29 Port=7425 Mode=PROCHASH][INFO ] tLockManager DEBUG is set to false[1495013022605] [Pid=4600 Host=10.41.2.29 Port=7425 Mode=PROCHASH][INFO ] tLockManager VERBOSE is set to false[1495013022616] [Pid=4600 Host=10.41.2.29 Port=7425 Mode=PROCHASH][INFO ] tLockManager HTTP Health Page on port : 7426 - Configure your instance by editing your [project].properties file with the following fields:
#******************************************************************** # # TAFJ Locking mechanism # #******************************************************************** # Tafj locking mode # Could be : JDBC | ORCL | MSQL | PROC | PROCHASH | MEM | NONE # JDBC : locks managed in database uses TAFJ_LOCKS table. # ORCL : locks managed in database using DBMS_LOCK Oracle specific package. Recommended solution for Oracle. # MSQL : locks managed in database using DBMS_LOCK MS-SQL specific package. Recommended solution for MS-SQL. # PROC : TAFJ lock manager, external process, server accepting client connections on a port. # PROCHASH : TAFJ lock manager, external process, server accepting client connections on a port (for performance). # MEM : Memory mode version of the TAFJ lock manager. temn.tafj.locking.mode = PROCHASH # Host name or IP of where is the tLockManager daemon # temn.tafj.locking.hostname = 127.0.0.1 # TCP port of the tLockManager daemon is listening on # temn.tafj.locking.port = 7425 # Bring the current call stack over to the LockManager? # temn.tafj.locking.callstack = false # if we want to override the URL as unique key for the DBInstance # we have to give a name here (eg myDatabase). This is usefull # if the DBServer has multiple adapters. The URL's are different # but this is still the same Database. # only for PROC and PROCHASH # temn.tafj.locking.name
In this topic