Menu
▾
▴
[Artifactory-developers] [JIRA jfrog] Reopened: (RTFACT-273) Cannot start Artifactory under Tomcat 6.0.14 on OS X
|
From: Patrick A. (JIRA) <ji...@jf...> - 2007-12-07 20:44:16
|
[ http://www.jfrog.org/jira//browse/RTFACT-273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick Aikens reopened RTFACT-273:
-----------------------------------
I would like to re-open this issue as a bug. The situation I find myself in is this: I am using Hudson as a build server. It runs under Tomcat, as does Artifactory. This means they are running as the same user. I have several projects which are built using Maven. When Hudson builds a project using Maven, the .m2 folder is (re)created in the tomcat user home directory.
At this stage, if ANYTHING requires Tomcat or Artifactory to restart, the .m2 folder in the Tomcat directory must be deleted.
This is a really annoying situation. If there is a workaround, I would love to hear it (unless it's "Run Artifactory and Hudson as different users").
> Cannot start Artifactory under Tomcat 6.0.14 on OS X
> ----------------------------------------------------
>
> Key: RTFACT-273
> URL: http://www.jfrog.org/jira//browse/RTFACT-273
> Project: Artifactory
> Issue Type: Bug
> Affects Versions: 1.2.2, 1.2.5
> Environment: Dual CPU G5 Mac OS X 10.4
> Reporter: Patrick Aikens
> Assignee: Yoav Landman
> Fix For: 1.2.2, 1.2.5
>
>
> I can't get artifactory to start on my OS X computer. That's not exactly true: the very first time I ever installed it it started up fine. I had to reboot a day or so later, and it's never worked since. Since then, I've gone so far as to blow away and reinstall both Tomcat and Artifactory, try every 1.2.5RC, try 1.2.2, all with no success. What's worse, all with no stack trace. Relevant catalina.out follows:
> Nov 9, 2007 6:21:57 AM org.apache.catalina.startup.HostConfig deployWAR
> INFO: Deploying web application archive artifactory.war
> Nov 9, 2007 6:21:58 AM org.apache.catalina.loader.WebappClassLoader validateJarFile
> INFO: validateJarFile(/usr/local/tomcat/webapps/artifactory/WEB-INF/lib/servlet-api-2.5-6.1.5.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/Servlet.class
> 2007-11-09 06:21:59,499 [INFO ] (ArtifactoryContextConfigurer.java:41) - Starting Artifactory...
> 2007-11-09 06:21:59,572 [INFO ] (AbstractApplicationContext.java:378) - Refreshing org.artifactory.webapp.spring.ArtifactoryWebApplicationContext@5c693a: display name [Root WebApplicationContext]; startup date [Fri Nov 09 06:21:59 EST 2007]; root of context hierarchy
> 2007-11-09 06:22:00,285 [INFO ] (AbstractApplicationContext.java:393) - Bean factory for application context [org.artifactory.webapp.spring.ArtifactoryWebApplicationContext@5c693a]: org.springframework.beans.factory.support.DefaultListableBeanFactory@1e5879
> 2007-11-09 06:22:00,567 [INFO ] (CentralConfigFactoryBean.java:55) - Loading configuration (using '/usr/local/artifactory/etc/artifactory.config.xml')...
> 2007-11-09 06:22:00,568 [INFO ] (CentralConfigFactoryBean.java:57) - Trying to load configuration from regular path file reosurce....
> 2007-11-09 06:22:02,007 [INFO ] (CentralConfigFactoryBean.java:68) - Loaded configuration from '/usr/local/artifactory/etc/artifactory.config.xml'.
> 2007-11-09 06:22:10,061 [WARN ] (CentralConfig.java:162) - Could not determine server instance id from configuration. Using hostname instead.
> 2007-11-09 06:22:10,265 [INFO ] (RemoteRepoBase.java:83) - repo1: Retrieval cache will be enabled with period of 43200 seconds
> 2007-11-09 06:22:10,266 [INFO ] (RemoteRepoBase.java:89) - repo1: Enabling failed retrieval cache with period of 30 seconds
> 2007-11-09 06:22:10,269 [INFO ] (RemoteRepoBase.java:97) - repo1: Enabling misses retrieval cache with period of 43200 seconds
> 2007-11-09 06:22:10,452 [INFO ] (RemoteRepoBase.java:83) - codehaus-snapshots: Retrieval cache will be enabled with period of 43200 seconds
> 2007-11-09 06:22:10,462 [INFO ] (RemoteRepoBase.java:89) - codehaus-snapshots: Enabling failed retrieval cache with period of 30 seconds
> 2007-11-09 06:22:10,463 [INFO ] (RemoteRepoBase.java:97) - codehaus-snapshots: Enabling misses retrieval cache with period of 43200 seconds
> 2007-11-09 06:22:10,474 [INFO ] (RemoteRepoBase.java:83) - java.net: Retrieval cache will be enabled with period of 43200 seconds
> 2007-11-09 06:22:10,475 [INFO ] (RemoteRepoBase.java:89) - java.net: Enabling failed retrieval cache with period of 30 seconds
> 2007-11-09 06:22:10,476 [INFO ] (RemoteRepoBase.java:97) - java.net: Enabling misses retrieval cache with period of 43200 seconds
> 2007-11-09 06:22:12,328 [WARN ] (DatabaseFileSystem.java:1068) - execute failed, about to reconnect...
> Nov 9, 2007 6:22:22 AM org.apache.catalina.core.StandardContext start
> SEVERE: Error listenerStart
> Nov 9, 2007 6:22:22 AM org.apache.catalina.core.StandardContext start
> SEVERE: Context [/artifactory] startup failed due to previous errors
> As you can see, it finds artifactory.home just fine (/usr/local/artifactory), and loads the config just fine. The DB lock files are created in the data/jcr/db directory as expected (db.lck and dbex.lck).
> Just for giggles, I created a .artifactory/etc directory in the home directory for the user that Tomcat runs as and put the config and log4j.properties files in there, but (like I expected) that changed nothing. That's the extent of my knowledge... is there any other logging I can enable (and if so, can someone be fairly specific as to which logging config file to change and how to do so... I'm still fairly new to log4j/commons logging).
> The only other info I have is when I try to run it using jetty (after an "su tomcat" so that permissions are correct), Spring complains about creating the "maven" bean and the org.artifactory.maven.Maven class throws a RuntimeException with the message "Failed to start maven embedder", That could be completely unrelated to the Tomcat issue, but it's the best clue I have and it seems to happen at the right point in the Artifactory startup (right after the "[WARN ] (DatabaseFileSystem.java:1068) - execute failed, about to reconnect..." message).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://www.jfrog.org/jira//secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|