Cache tag exceptions and deadlocks

Question

          Weblogic 6.1 sp2 on W2K and Solaris
          If an un-caught Exception is produced from code with-in a cache tag, then the
          cache for that page will become locked until server restart
          This can be tested by throwing an Execption and displaying (using a seperate page)
          all objects in the application, the cache with the Exception will be displayed
          as xxx.lock
          This can be avioded by catching all Exceptions
          Gareth
          

Answer 1

"Christian Corcino" <[email protected]> wrote in message
          news:3b5e3776$[email protected]..
          > I do not quite understand the purpose of the keys in the cache tag,
          > what are they used for.
          > These are the different keys :
          > parameter.key | page.key | request.key | application.key | session.key
          >
          > Can any one give me an example of when and how to use these keys,
          These are logical sub-keys you can use to distinguish two tags that would
          otherwise resolve to the same cached value. It helps prevent "overloading"
          the cache name with disjoint information needed to distinguish cache
          entries.
          For instance, our application supports multiple languages and uses a page
          variable called "language". Assume we want to cache the computed contents
          of a select element according to the user's language:
          <wl:cache name="selectValues_foobar" key="page.language" timeout="30m">
          [code to compute select values omitted]
          </wl:cache>
          This lets us use one name to describe the particular dataset while still
          allowing for independently cached values for differents values of
          "language".
          Felix Hack
          [email protected]