bof jars are getting downloaded in two cache locations.

Hi,

I noticed that bof jars are getting downloaded in two cache locations. As per my understanding it should download in one cache location.

i.e. It downloads in cache/6.0.0.9 as well as in cache/6.0.0.113SP1.

Can anyone help me in understanding this cache/{version} concept and how it picks a perticular version to download jars

Regards

Sanjay

Find more posts tagged with

Documentum

Comments

Francois Dauberlieu

The numbers behind cache correspond to the version of the client (or it it the CS ?) therefore, at first the jars went into 6.0.0.9 and then when you upgraded, it started to go into 6.0.0.113SP1.

msk

Thanks for your reply..

So, in that case the cache should only download into 6.0.0.113SP1 but its getting downloaded into both the directories, i.e. in 6.0.0.9 and 6.0.0.113SP1.

Can i define the cache path in CS dfc.properties file ? so that which ever clinet connects it will download into that location..

Regards

Sanjay

Francois Dauberlieu

Do you mean that new jars are downloaded in the 2 folders ?

You could try to shutdown you repositories, clear up under the cache directory and restart them to see if that's the case

lastnitescurry

from dfcfull.properties

# The root directory for the area where DFC stores its persistent caches.
dfc.cache.dir = ${dfc.data.dir}/cache

I would advise against sharing the cache. For D6x apps I have encoutered problems. Found a posting/blog which recommended unique dfc.data.dir settings. In my current project I have folder c:\DocumentumUsers with data dirs for the following apps

dfc.data.dir=C\:/DocumentumUser/ContentServer

dfc.data.dir=C\:/DocumentumUser/da

dfc.data.dir=C\:/DocumentumUser/dco

dfc.data.dir=C\:/DocumentumUser/webtop

It takes a few minutes to setup this config but it does make cleaning caches and temp files a lot eaiser..... shut down every thing and delete c:\DocumentumUsers

msk

Thanks Brain.

I will update those entries in dfc.prop file

Regards

Sanjay

saavedra

Hello msk,

Did Brian's solution work, or how did you solved the issue?

I have the same problem after installing a patch, I have tried restarting the repository cleaning the caché, but after the restart both caches are created again.