Atlassian-SDK: Why does atlas-run-standalone --product jira time out on deployment?

jablm April 25, 2013

I am having a problem running atlas-run-standalone --product jira on Windows 7. I'm behind a corporate firewall but I've setup the http and https proxies and Maven seems to be downloading dependencies without a problem. Here's the output of the atlas-run-standalone command:

[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Building Maven Default Project
[INFO] task-segment: [com.atlassian.maven.plugins:maven-amps-plugin:4.1.7:run-standalone] (aggregator-style)
[INFO] ------------------------------------------------------------------------
[INFO] [amps:run-standalone]
[INFO] Google Analytics Tracking is enabled to collect AMPS usage statistics.
[INFO] Although no personal information is sent, you may disable tracking by adding <allowGoogleTracking>false</allowGoogleTracking> to the amps plugin configuration in your pom.xml
[INFO] Sending event to Google Analytics: AMPS:jira - Run Standalone
[INFO] [amps:run]
[INFO] Google Analytics Tracking is enabled to collect AMPS usage statistics.
[INFO] Although no personal information is sent, you may disable tracking by adding <allowGoogleTracking>false</allowGoogleTracking> to the amps plugin configuration in your pom.xml
[INFO] Sending event to Google Analytics: AMPS:jira - Run
[INFO]
[INFO] Starting jira... (see log at C:\atlastutorial\amps-standalone\target/jira-5.2.10.log)
[INFO] [dependency:copy]
[INFO] Configured Artifact: com.atlassian.jira.plugins:jira-plugin-test-resources:5.2.10:zip
[INFO] com.atlassian.jira.plugins:jira-plugin-test-resources:5.2.10:zip already exists in C:\atlastutorial\amps-standalone\target\jira
[INFO] [dependency:copy {execution: virtual-execution}]
[INFO] Configured Artifact: com.atlassian.jira:atlassian-jira-webapp:5.2.10:war
[INFO] com.atlassian.jira:atlassian-jira-webapp:5.2.10:war already exists in C:\atlastutorial\amps-standalone\target\jira
[INFO] [dependency:copy {execution: virtual-execution}]
[INFO] Configured Artifact: com.atlassian.pdkinstall:pdkinstall-plugin:0.4:jar
[INFO] Copying pdkinstall-plugin-0.4.jar to C:\atlastutorial\amps-standalone\target\jira\home\plugins\installed-plugins\pdkinstall-plugin-0.4.jar
[INFO] [dependency:copy {execution: virtual-execution}]
[INFO] Configured Artifact: commons-fileupload:commons-fileupload:1.2.1:jar
[INFO] Copying commons-fileupload-1.2.1.jar to C:\atlastutorial\amps-standalone\target\jira\home\plugins\installed-plugins\commons-fileupload-1.2.1.jar
[INFO] [dependency:copy {execution: virtual-execution}]
[INFO] Configured Artifact: org.apache.felix:org.apache.felix.webconsole:1.2.8:jar
[INFO] Copying org.apache.felix.webconsole-1.2.8.jar to C:\atlastutorial\amps-standalone\target\jira\home\plugins\installed-plugins\org.apache.felix.webconsole-1.2.8.jar
[INFO] [dependency:copy {execution: virtual-execution}]
[INFO] Configured Artifact: org.apache.felix:org.osgi.compendium:1.2.0:jar
[INFO] Copying org.osgi.compendium-1.2.0.jar to C:\atlastutorial\amps-standalone\target\jira\home\plugins\installed-plugins\org.osgi.compendium-1.2.0.jar
[INFO] [dependency:copy {execution: virtual-execution}]
[INFO] Configured Artifact: com.atlassian.labs.httpservice:httpservice-bridge:0.6.1:jar
[INFO] Copying httpservice-bridge-0.6.1.jar to C:\atlastutorial\amps-standalone\target\jira\home\plugins\installed-plugins\httpservice-bridge-0.6.1.jar
[INFO] [dependency:copy {execution: virtual-execution}]
[INFO] Configured Artifact: com.atlassian.labs:fastdev-plugin:2.0:jar
[INFO] Copying fastdev-plugin-2.0.jar to C:\atlastutorial\amps-standalone\target\jira\home\plugins\installed-plugins\fastdev-plugin-2.0.jar
[INFO] [dependency:copy {execution: virtual-execution}]
[INFO] Configured Artifact: com.atlassian.devrel:developer-toolbox-plugin:2.0.5:jar
[INFO] Copying developer-toolbox-plugin-2.0.5.jar to C:\atlastutorial\amps-standalone\target\jira\home\plugins\installed-plugins\developer-toolbox-plugin-2.0.5.jar
[INFO] [dependency:copy {execution: virtual-execution}]
[INFO] Configured Artifact: com.atlassian.plugins:plugin-data-editor:1.2:jar
[INFO] Copying plugin-data-editor-1.2.jar to C:\atlastutorial\amps-standalone\target\jira\home\plugins\installed-plugins\plugin-data-editor-1.2.jar
[INFO] Reusing unpacked container 'tomcat6x' from C:\atlastutorial\amps-standalone\target\container\tomcat6x
[INFO] Starting jira on the tomcat6x container on ports 2990 (http) and 63460 (rmi)
[INFO] using codehaus cargo v1.2.3
[INFO] [cargo:start]
[INFO] [2.ContainerStartMojo] Resolved container artifact org.codehaus.cargo:cargo-core-container-tomcat:jar:1.2.3 for container tomcat6x
[INFO] [stalledLocalDeployer] Deploying [C:\atlastutorial\amps-standalone\target\jira\jira.war] to [C:\atlastutorial\amps-standalone\target\container\tomcat6x\cargo-jira-home/webapps]...
[INFO] [talledLocalContainer] Tomcat 6.x starting...
[INFO] [yer.DeployerWatchdog] Deployable [http://localhost:2990/cargocpc/index.html] failed to finish deploying within the timeout period [600000]. The Deployable state is thus unknown.
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Unable to execute mojo

Deployable [http://localhost:2990/cargocpc/index.html] failed to finish deploying within the timeout period [600000]. The Deployable state is thus unknown.
[INFO] ------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Unable to execute mojo
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:703)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:553)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:523)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:268)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:356)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: Unable to execute mojo
at com.atlassian.maven.plugins.amps.RunStandaloneMojo.doExecute(RunStandaloneMojo.java:97)
at com.atlassian.maven.plugins.amps.AbstractProductHandlerMojo.execute(AbstractProductHandlerMojo.java:631)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678)
... 16 more
Caused by: org.apache.maven.plugin.MojoExecutionException: Unable to execute mojo
at org.twdata.maven.mojoexecutor.MojoExecutor.executeMojoImpl(MojoExecutor.java:122)
at org.twdata.maven.mojoexecutor.MojoExecutor$ExecutionEnvironmentM2.executeMojo(MojoExecutor.java:403)
at org.twdata.maven.mojoexecutor.MojoExecutor.executeMojo(MojoExecutor.java:74)
at com.atlassian.maven.plugins.amps.MavenGoals.executeAmpsRecursively(MavenGoals.java:117)
at com.atlassian.maven.plugins.amps.RunStandaloneMojo.doExecute(RunStandaloneMojo.java:93)
... 19 more
Caused by: org.apache.maven.plugin.MojoExecutionException: Unable to execute mojo
at org.twdata.maven.mojoexecutor.MojoExecutor.executeMojoImpl(MojoExecutor.java:122)
at org.twdata.maven.mojoexecutor.MojoExecutor$ExecutionEnvironmentM2.executeMojo(MojoExecutor.java:403)
at org.twdata.maven.mojoexecutor.MojoExecutor.executeMojo(MojoExecutor.java:74)
at com.atlassian.maven.plugins.amps.MavenGoals.startWebapp(MavenGoals.java:851)
at com.atlassian.maven.plugins.amps.product.AbstractWebappProductHandler.startApplication(AbstractWebappProductHandler.java:53)
at com.atlassian.maven.plugins.amps.product.AbstractProductHandler.start(AbstractProductHandler.java:63)
at com.atlassian.maven.plugins.amps.RunMojo.startProducts(RunMojo.java:124)
at com.atlassian.maven.plugins.amps.RunMojo.doExecute(RunMojo.java:87)
at com.atlassian.maven.plugins.amps.AbstractProductHandlerMojo.execute(AbstractProductHandlerMojo.java:631)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483)
at org.twdata.maven.mojoexecutor.MojoExecutor.executeMojoImpl(MojoExecutor.java:120)
... 23 more
Caused by: org.codehaus.cargo.container.ContainerException: Failed to start the Tomcat 6.x container. Check the [C:\atlastutorial\amps-standalone\target/jira-5.2.10.log] file containing the container logs for more details.
at org.codehaus.cargo.container.spi.AbstractLocalContainer.start(AbstractLocalContainer.java:179)
at org.codehaus.cargo.maven2.AbstractContainerStartMojo.doExecute(AbstractContainerStartMojo.java:61)
at org.codehaus.cargo.maven2.ContainerStartMojo.doExecute(ContainerStartMojo.java:52)
at org.codehaus.cargo.maven2.AbstractCargoMojo.execute(AbstractCargoMojo.java:431)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483)
at org.twdata.maven.mojoexecutor.MojoExecutor.executeMojoImpl(MojoExecutor.java:120)
... 33 more
Caused by: org.codehaus.cargo.container.ContainerException: Deployable [http://localhost:2990/cargocpc/index.html] failed to finish deploying within the timeout period [600000]. The Deployable state is thus unknown.
at org.codehaus.cargo.container.spi.deployer.DeployerWatchdog.watch(DeployerWatchdog.java:111)
at org.codehaus.cargo.container.spi.AbstractLocalContainer.waitForCompletion(AbstractLocalContainer.java:254)
at org.codehaus.cargo.container.tomcat.internal.AbstractCatalinaInstalledLocalContainer.waitForCompletion(AbstractCatalinaInstalledLocalContainer.java:212)
at org.codehaus.cargo.container.spi.AbstractLocalContainer.start(AbstractLocalContainer.java:173)
... 38 more
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 24 minutes 19 seconds
[INFO] Finished at: Thu Apr 25 16:19:09 EDT 2013
[INFO] Final Memory: 43M/104M
[INFO] ------------------------------------------------------------------------

Note that this process takes a very long time. 14 Minutes on top of the 10 minute deployment timeout, which is also a problem. The JIRA log doesn't indicate any errors. The last line is :

2013-04-25 16:15:39,601 main WARN [atlassian.jira.diagnostic.PluginDiagnostics] Registering PluginDiagnostics with the event manager.

Does anyone know of a reason why the execution might be so slow and the deployment timing out? Could it be due to McAfee Virus Scan (I have no way of modifying or disabling McAfee as this is a corporate-controlled workstation)?

Does anyone know why atlas-run-standalone reports attempted deployment to localhost, but the JIRA log is showing a baseurl that uses the machine's actual hostname instead of localhost? Could this be related to the problem?

Thanks,

--John

1 answer

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

1 vote
Answer accepted
jablm April 25, 2013

I found the group in my company that controls McAfee. They could see that while trying to startup and deploy there was a lot of scanning of archives occuring which was taking a long time. They've since changed my McAfee settings to avoid scanning WARs and JARs on access (not sure on the exact details of what settings were changed) and now the standalone JIRA instance is starting up.

TAGS
AUG Leaders

Atlassian Community Events