continuum-issues mailing list archives

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

    [ http://jira.codehaus.org/browse/CONTINUUM-1891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=148556#action_148556
] 

Joakim Erdfelt commented on CONTINUUM-1891:
-------------------------------------------

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

Managing java.io.tmpdir 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.

Example:

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
some 
  kind of task that uses the java.io.tmpdir to manage temporary files.  However the implementation
does
  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 java.io.tmpdir for jetty bundle (can causes issues on solaris)
> --------------------------------------------------------------------------------
>
>                 Key: CONTINUUM-1891
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-1891
>             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 java.io.tmpdir 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 net.sf.ehcache.store.DiskStore.<init>(DiskStore.java:164)
>         at net.sf.ehcache.Cache.createDiskStore(Cache.java:577)
>         at net.sf.ehcache.Cache.initialise(Cache.java:549)
>         at net.sf.ehcache.CacheManager.addCacheNoCheck(CacheManager.java:707)
>         at net.sf.ehcache.CacheManager.addCache(CacheManager.java:697)
>         at net.sf.ehcache.CacheManager.addCache(CacheManager.java:654)
>         at org.codehaus.plexus.cache.ehcache.EhcacheCache.initialize(EhcacheCache.java:244)
>         at org.codehaus.plexus.spring.PlexusLifecycleBeanPostProcessor.postProcessAfterInitialization(PlexusLifecycleBeanPostProcessor.java:217)
>         at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyBeanPostProcessorsAfterInitialization(AbstractAutowireCapableBeanFactory.java:361)
>         at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.postProcessObjectFromFactoryBean(AbstractAutowireCapableBeanFactory.java:1427)
>         at org.springframework.beans.factory.support.FactoryBeanRegistrySupport$1.run(FactoryBeanRegistrySupport.java:139)
>         ... 56 more
> Caused by: java.io.IOException: Index file /var/tmp/url-failures-cache.index could not
created.
>         at net.sf.ehcache.store.DiskStore.createNewIndexFile(DiskStore.java:850)
>         at net.sf.ehcache.store.DiskStore.readIndex(DiskStore.java:827)
>         at net.sf.ehcache.store.DiskStore.initialiseFiles(DiskStore.java:193)
>         at net.sf.ehcache.store.DiskStore.<init>(DiskStore.java:152)
>         ... 66 more
> {code}

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message