This is an old known issue on Jetty/Redhat that is long resolved since version 1.2.5u1 and of course in the 1.3.0 betas. It is also real easy to fix by manually creating the work folder for Jetty. No need to cross-post, BTW.
Yoav 陈思淼 wrote: > > there is a Bug about Artifactory combine jetty, it's will lost its works > dircectory every one or two weeks ,because jetty put the works directory > in > the /tmp. > So we must restart our artfactory.sh every one or two weeks. > yestoday after we use killall -9 java to kill jetty process and restart > it. > there is a exception: > >> java.lang.RuntimeException: Failed to config jcr repo. >> > at org.artifactory.jcr.JcrHelper.<init>(JcrHelper.java:112) > > at > org.artifactory.config.CentralConfig.afterPropertiesSet(CentralConfig.java:158) > > at > org.artifactory.config.CentralConfigFactoryBean.afterPropertiesSet(CentralConfigFactoryBean.java:69) > > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCap > > ableBeanFactory.java:1202) > > I guess that's becouse the killall cause some JCR problem in artifactory. > Can anybody tell me how to stop the process politely install of killall -9 > ? > > -- View this message in context: http://www.nabble.com/Is-anybody-use-Jfog-Artifactory-as-their-company-level-repository--tp19699271p19700108.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
