Problème surcharge repository.properties

bub — Thu, 02 Jul 2009 06:25:52 GMT

Bonjour,J'ai déjà installé Alfresco pour tester sur une RedHat4 32bits avec Tomcat 5. Installation réussie après quelques recherches…Aujourd'hui, on me demande de tester Alfresco sur une RedHat5 64Bits avec Tomcat6…J'en ai presque terminé, à part que le fait de modifier mon fichier custom-repository

Re: Problème surcharge repository.properties

michaelh — Thu, 02 Jul 2009 07:12:07 GMT

Bonjour,

Je pense que la réponse se trouve ici : http://wiki.alfresco.com/wiki/Install_Tomcat6
En particulier le point concernant "shared.loader" dans catalina.properties.

Cette réponse se trouve aussi dans le guide d'installation.

Re: Problème surcharge repository.properties

bub — Thu, 02 Jul 2009 07:41:43 GMT

Bonjour,

Je pense que la réponse se trouve ici : http://wiki.alfresco.com/wiki/Install_Tomcat6
En particulier le point concernant "shared.loader" dans catalina.properties.

Cette réponse se trouve aussi dans le guide d'installation.

Merci, mais j'ai suivi la documentation.
Mon catalina.properties (dans /var/tomcat/instances/alfresco/conf/) contient bien les chemins necessaires :

#
# List of comma-separated packages that start with or equal this string
# will cause a security exception to be thrown when
# passed to checkPackageAccess unless the
# corresponding RuntimePermission ("accessClassInPackage."+package) has
# been granted.
package.access=sun.,org.apache.catalina.,org.apache.coyote.,org.apache.tomcat.,org.apache.jasper.,sun.beans.
#
# List of comma-separated packages that start with or equal this string
# will cause a security exception to be thrown when
# passed to checkPackageDefinition unless the
# corresponding RuntimePermission ("defineClassInPackage."+package) has
# been granted.
#
# by default, no packages are restricted for definition, and none of
# the class loaders supplied with the JDK call checkPackageDefinition.
#
package.definition=sun.,java.,org.apache.catalina.,org.apache.coyote.,org.apache.tomcat.,org.apache.jasper.

#
#
# List of comma-separated paths defining the contents of the "common"
# classloader. Prefixes should be used to define what is the repository type.
# Path may be relative to the CATALINA_HOME or CATALINA_BASE path or absolute.
# If left as blank,the JVM system loader will be used as Catalina's "common"
# loader.
# Examples:
#     "foo": Add this folder as a class repository
#     "foo/*.jar": Add all the JARs of the specified folder as class
#                  repositories
#     "foo/bar.jar": Add bar.jar as a class repository
common.loader=${catalina.home}/lib,${catalina.home}/lib/*.jar

#
# List of comma-separated paths defining the contents of the "server"
# classloader. Prefixes should be used to define what is the repository type.
# Path may be relative to the CATALINA_HOME or CATALINA_BASE path or absolute.
# If left as blank, the "common" loader will be used as Catalina's "server"
# loader.
# Examples:
#     "foo": Add this folder as a class repository
#     "foo/*.jar": Add all the JARs of the specified folder as class
#                  repositories
#     "foo/bar.jar": Add bar.jar as a class repository
server.loader=

#
# List of comma-separated paths defining the contents of the "shared"
# classloader. Prefixes should be used to define what is the repository type.
# Path may be relative to the CATALINA_BASE path or absolute. If left as blank,
# the "common" loader will be used as Catalina's "shared" loader.
# Examples:
#     "foo": Add this folder as a class repository
#     "foo/*.jar": Add all the JARs of the specified folder as class
#                  repositories
#     "foo/bar.jar": Add bar.jar as a class repository
# Please note that for single jars, e.g. bar.jar, you need the URL form
# starting with file:.
shared.loader=${catalina.base}/shared/classes,${catalina.base}/shared/lib/*.jar

#
# String cache configuration.
tomcat.util.buf.StringCache.byte.enabled=true
#tomcat.util.buf.StringCache.char.enabled=true
#tomcat.util.buf.StringCache.trainThreshold=500000
#tomcat.util.buf.StringCache.cacheSize=5000
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Une autre idée ? 😉

Re: Problème surcharge repository.properties

bub — Thu, 02 Jul 2009 12:05:00 GMT

Bon, il semblerait que cela vienne de la configuration multi sessions de Tomcat 6 chez nous qui n'est pas encore au point…

Le spécialiste vérifie tout cela, avec un peu de chance, ca marchera :roll:

topic Problème surcharge repository.properties in Alfresco Archive

Problème surcharge repository.properties

Re: Problème surcharge repository.properties

Re: Problème surcharge repository.properties

Re: Problème surcharge repository.properties