Troubleshooting

1. Shared Memory (Shm) Keys

  • Issue description

    When installing ProFrame, a shared memory (Shm) key can be duplicated with one of the shared memory keys that are currently being used by existing applications.

  • Action

    Check Shm keys that are currently being used by the Server by using the ipcs command.

    The following changes Shm keys for each configuration file.

    • tdlcall → $TMAXDIR/tdlcall/tdl.cfg

      [pfmtpqa@fwsol:/home2/pfmtpqa/proframe5.0/package/tmax/tdlcall]$ vi tdl.cfg
# shared memory key
SHMKEY=0x80000

    • tcache → $PRJROOT/package/proframe/pfm/cfg/pfmtcache.cfg

      [pfmtpqa@fwsol:/home2/pfmtpqa/proframe5.0/package/proframe/pfm/cfg]$ vi pfmtcache.cfg
# the configuration file of TCACHE
SHMKEY=0x79999      # shared memory's key value
IPCPERM=0777        # shared memory's access permission

    • apmem →$PRJROOT/package/proframe/pfm/cfg/apmem.cfg

      [pfmtpqa@fwsol:/home2/pfmtpqa/proframe5.0/package/proframe/pfm/cfg]$ vi
apmmem.cfg
# the configuration file of APMMEM
SHMKEY1=0x76000                 # APMMEM shared memory's key value
SHMKEY2=0x76001                 # TRACEADM shared memory's key value
SHMKEY3=0x76002                 # TRACEADM shared memory's key value
IPCPERM=0666                    # APMMEM shared memory's access permission

      Confirm that the previous changes are applied by using the ipcs command.

       [pfmtpqa@fwsol:/home2/pfmtpqa/proframe5.0]$ ipcs -m
T         ID      KEY        MODE        OWNER    GROUP
Shared Memory:
m  486539316   0x81005    --rw-rw-rw- pfmO0tm4     pfm4
m  452984882   0x15f25    --rw------- pfmO0tm4     pfm4
m  452984881   0x15f24    --rw------- pfmO0tm4     pfm4
m  452984880   0x15f23    --rw------- pfmO0tm4     pfm4
m  486539311   0x15f22    --rw------- pfmO0tm4     pfm4
m  436207658   0x79999    --rw-rw-rw-  pfmtpqa       qa
m  503316507   0x76002    --rw-rw-rw-  pfmtpqa       qa
m  503316501   0x76001    --rw-rw-rw-  pfmtpqa       qa
m  503316500   0x76000    --rw-rw-rw-  pfmtpqa       qa
m  503316488   0x80000    --rw-rw----  pfmtpqa       qa
m  436207720   0x91000    --rw-r----- pfmO0tm4     pfm4
m         90   0x99000    --rw-rw----  pfmtpqa       qa

      To delete a Shm key in use, use the ipcrm command.

      [pfmtpqa@fwsol:/home2/pfmtpqa/proframe5.0]$ ipcrm -m 436207658
      Classification Shm Key to Check

      tdlcall

      0x90000

      tcache

      0x70005

      apmmem

      0x76000

      0x76001

      0x76002

2. ProFrame Ports

  • Issue description

    When installing ProFrame, a port number can be duplicated with one of the port numbers in use.

  • Action

    If default port numbers that are set during ProFrame installation are used by other accounts, use port numbers that are not used yet.

    The following are examples of default ports by server.

    • Tmax

      Default Port File to Change Port Number

      Tmax

      8888

      tmaxconfig.m, profile.tmax

    • JEUS

      Default Port File to Change Port Number

      JEUS

      9736

      jeus.properties, vhost.xml

    • ProFrame

      Default Port File to Change Port Number

      http-linstener

      9966

      WEBMain.xml, PfmDevSvr.xml

      logserver

      9942

      logserver.sh, PfmDevSvr.xml

      DEV_CONFIG tables’s LOG_SERVER_PORT column

      pfmbuildsvr

      9943

      pfmbuildsvr.sh, PfmDevSvr.xml

      Test framework

      8888

      TestFrameWorkConfig.jsp

      The port number of the test framework must be the same as that of Tmax server.