continuum-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joakim Erdfelt (JIRA)" <>
Subject [jira] Commented: (CONTINUUM-1891) don't use default for jetty bundle (can causes issues on solaris)
Date Fri, 19 Sep 2008 21:47:49 GMT


Joakim Erdfelt commented on CONTINUUM-1891:

Commenting post-close just to add ... uhm ... comments.

Managing is almost a required aspect of handling concurrency issues when working
on a 
shared work environment such as a build server or a unix platform.


a) You have multiple users on the same machine.
b) Most of them are developers.
c) The developers are all working with a bea-maven-plugin (or something similar) that performs
  kind of task that uses the to manage temporary files.  However the implementation
  not create a uniq and/or random file or directory.
d) Developer 1 starts a long build using bea-maven-plugin
e) Developer 2 starts another build also using bea-maven-plugin, however his run now starts
to pick up on the temporary files
  that developer 1's instance of bea-maven-plugin is using.

In our work to make a build farm and or concurrent builds on a single server, I think it would
be wise to keep
managing this variable, even on a per-project basis.

> don't use default for jetty bundle (can causes issues on solaris)
> --------------------------------------------------------------------------------
>                 Key: CONTINUUM-1891
>                 URL:
>             Project: Continuum
>          Issue Type: Improvement
>          Components: Jetty Bundle
>    Affects Versions: 1.2
>            Reporter: Olivier Lamy
>            Assignee: Olivier Lamy
>             Fix For: 1.2.1
> On solaris is a shared directory (/var/tmp) and if different uid starts
continuum. It can have some permissions issues.
> {code}
> Caused by: net.sf.ehcache.CacheException: url-failures-cacheCache: Could not create disk
store. Initial cause was Index file /var/tmp/url-failures-cache.index could not created.
>         at<init>(
>         at net.sf.ehcache.Cache.createDiskStore(
>         at net.sf.ehcache.Cache.initialise(
>         at net.sf.ehcache.CacheManager.addCacheNoCheck(
>         at net.sf.ehcache.CacheManager.addCache(
>         at net.sf.ehcache.CacheManager.addCache(
>         at org.codehaus.plexus.cache.ehcache.EhcacheCache.initialize(
>         at org.codehaus.plexus.spring.PlexusLifecycleBeanPostProcessor.postProcessAfterInitialization(
>         at
>         at
>         at$
>         ... 56 more
> Caused by: Index file /var/tmp/url-failures-cache.index could not
>         at
>         at
>         at
>         at<init>(
>         ... 66 more
> {code}

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message