Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-4993966

Properties if locked inside deployment.config produces undesired results

XMLWordPrintable

      Tested_Java_Release : "1.5.0-beta2
      build/bundles : 1.5.0-beta2-b38
      Tested_Java_Location :
      /net/koori/onestop/jdk/1.5.0/latest/bundles
      /net/sqesvr-nfs/global/nfs/deployment3/tiger/PIT_builds
      Tested_Machine_Name : dnm-011/jitender/dnm-101/dnm-dtf-016
      Tested O/S : winxp/win2k/solars9/RHADS2.1

      Problem Description :
      Deployment properties defined at system level can be locked so that they can't be overriden by the users. But the deployment.user.logdir and deployment.user.cachedir when locked, has no effect at the execution of applications but trace,log and cached files are not going neither to the mentioned locations inside the system level deployemt.propeties file nor they are going to default user location. Also whenever user tries to retreive any of the locked property, instead of value specified inside the system level deployment.properties file, a blank string is getting returned.

      Step to reproduce:
      1) Create a deployment.config file inside <dep_system_home> with following enteries
      Windows
      deployment.system.config=file:///D:/jitu/deployment.properties(location of system level deployment.properties file)
      deployment.system.config.mandatory=true

      Unix
      deployment.system.config=file:///net/sqesvr-nfs/global/nfs/deployment2/jitu/deployment.properties(location of system level deployment.properties file)
      deployment.system.config.mandatory=true

      2) Create deployment.properties file at location mentioned against property deployment.system.config inside the deployment.config file with following values
      (make sure that deployment.properties inside the user level doesn't exist)
      Windows
      deployment.user.logdir=D:/Documents and Settings/Administrator/deploytest/log
      deployment.user.cachedir=D:/Documents and Settings/Administrator/deploytest/cache

      Solaris
      deployment.user.cachedir=//plugintest/cache
      deployment.user.logdir=//plugintest/log

      Linux
      deployment.user.cachedir=/root/plugintest/cache
      deployment.user.logdir=/root/plugintest/log

      3) try to launch any applet or JAWS application, they will run successfully and all the traces and cached file will go into the above mentioned locations specified against the deployment.user.cachedir and deployment.user.logdir
       Press "S" on Java Console deployment.user.cachedir and deployment.user.logdir will contain values specified inside the system level deployment.properties file

      Remove the cache and logs
      4) Create deployment.properties inside <dep_user_home> with deployment.user.cachedir and deployment.user.logdir having some new values different than what have been defined inside the system level deployment.properties file

      5) try to launch any applet or JAWS application, they will run successfully and all the traces and cached file will go into the new location specified against the deployment.user.cachedir and deployment.user.logdir inside the user level deployment.properties file
       Press "S" on Java Console deployment.user.cachedir and deployment.user.logdir will contain values specified inside the user level deployment.properties file

      Remove the cache and logs

      6) Add following entries to the system level deployment.properties file
      deployment.user.cachedir.locked
      deployment.user.logdir.locked

      7) Invoke Java Control Panel. The Change Cache Locations(both textfield and button) should get disabled

      8)try to launch any applet or JAWS application, they will run successfully

      Uptill here everything is working fine

      9) Press "S" on Java Console deployment.user.cachedir and deployment.user.logdir should contain values specified inside the system level deployment.properties file but they are empty strings

      10) try to locate the logs,traces and cached files . they are not there at any of the location mentioned inside the system and user level deployment.propeties file nor they are there at the default locations.
      Trace and cached files should go to the locations mentioned inside the system level deployment properties file



            herrick Andy Herrick (Inactive)
            jijising Jitender Singh (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: