Local JIRA always timeout and fail to start up

[Po Chen]

Hi all,

My local jira environment has been like this since a few weeks ago.
Really need some help.

The command I run is:
atlas-run-standalone --product jira --version 6.3-OD-03-012 --bundled-plugins com.atlassian.plugins:atlassian-connect-plugin:1.0.2,com.atlassian.jwt:jwt-plugin:1.0.0,com.atlassian.bundles:json-schema-validator-atlassian-bundle:1.0-m0 --jvmargs -Datlassian.upm.on.demand=true

Thanks!

[INFO] Scanning for projects...
[INFO]
[INFO] Using the builder org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder with a thread count of 1
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Maven Stub Project (No POM) 1
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-amps-plugin:5.0.2:run-standalone (default-cli) @ standalone-pom ---
[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] 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 /Users/pochen/Code/amps-standalone/target/jira-LATEST.log)
[INFO] determining latest stable data version...
[INFO] using latest stable data version: 6.2.7
[INFO] Configured Artifact: com.atlassian.jira.plugins:jira-plugin-test-resources:6.2.7:zip
[INFO] com.atlassian.jira.plugins:jira-plugin-test-resources:6.2.7:zip already exists in /Users/pochen/Code/amps-standalone/target/jira
[INFO] Configured Artifact: com.atlassian.jira:atlassian-jira-webapp:6.3-OD-03-012:war
[INFO] com.atlassian.jira:atlassian-jira-webapp:6.3-OD-03-012:war already exists in /Users/pochen/Code/amps-standalone/target/jira
[INFO] Configured Artifact: com.atlassian.pdkinstall:pdkinstall-plugin:0.6:jar
[INFO] Copying pdkinstall-plugin-0.6.jar to /Users/pochen/Code/amps-standalone/target/jira/home/plugins/installed-plugins/pdkinstall-plugin-0.6.jar
[INFO] Configured Artifact: commons-fileupload:commons-fileupload:1.2.1:jar
[INFO] Copying commons-fileupload-1.2.1.jar to /Users/pochen/Code/amps-standalone/target/jira/home/plugins/installed-plugins/commons-fileupload-1.2.1.jar
[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 /Users/pochen/Code/amps-standalone/target/jira/home/plugins/installed-plugins/org.apache.felix.webconsole-1.2.8.jar
[INFO] Configured Artifact: org.apache.felix:org.osgi.compendium:1.2.0:jar
[INFO] Copying org.osgi.compendium-1.2.0.jar to /Users/pochen/Code/amps-standalone/target/jira/home/plugins/installed-plugins/org.osgi.compendium-1.2.0.jar
[INFO] Configured Artifact: com.atlassian.labs.httpservice:httpservice-bridge:0.6.2:jar
[INFO] Copying httpservice-bridge-0.6.2.jar to /Users/pochen/Code/amps-standalone/target/jira/home/plugins/installed-plugins/httpservice-bridge-0.6.2.jar
[INFO] Configured Artifact: com.atlassian.labs:fastdev-plugin:2.4:jar
[INFO] Copying fastdev-plugin-2.4.jar to /Users/pochen/Code/amps-standalone/target/jira/home/plugins/installed-plugins/fastdev-plugin-2.4.jar
[INFO] Configured Artifact: com.atlassian.devrel:developer-toolbox-plugin:2.0.12:jar
[INFO] Copying developer-toolbox-plugin-2.0.12.jar to /Users/pochen/Code/amps-standalone/target/jira/home/plugins/installed-plugins/developer-toolbox-plugin-2.0.12.jar
[INFO] Configured Artifact: com.atlassian.labs:rest-api-browser:3.0.7:jar
[INFO] Copying rest-api-browser-3.0.7.jar to /Users/pochen/Code/amps-standalone/target/jira/home/plugins/installed-plugins/rest-api-browser-3.0.7.jar
[INFO] Configured Artifact: com.atlassian.plugins:plugin-data-editor:1.2:jar
[INFO] Copying plugin-data-editor-1.2.jar to /Users/pochen/Code/amps-standalone/target/jira/home/plugins/installed-plugins/plugin-data-editor-1.2.jar
[INFO] Configured Artifact: com.atlassian.plugins:atlassian-connect-plugin:1.0.2:jar
[INFO] Copying atlassian-connect-plugin-1.0.2.jar to /Users/pochen/Code/amps-standalone/target/jira/webapp/WEB-INF/atlassian-bundled-plugins/atlassian-connect-plugin-1.0.2.jar
[INFO] Configured Artifact: com.atlassian.jwt:jwt-plugin:1.0.0:jar
[INFO] Copying jwt-plugin-1.0.0.jar to /Users/pochen/Code/amps-standalone/target/jira/webapp/WEB-INF/atlassian-bundled-plugins/jwt-plugin-1.0.0.jar
[INFO] Configured Artifact: com.atlassian.bundles:json-schema-validator-atlassian-bundle:1.0-m0:jar
[INFO] Copying json-schema-validator-atlassian-bundle-1.0-m0.jar to /Users/pochen/Code/amps-standalone/target/jira/webapp/WEB-INF/atlassian-bundled-plugins/json-schema-validator-atlassian-bundle-1.0-m0.jar
[INFO] Unpacking container 'tomcat7x' from container artifact: org.apache.tomcat:apache-tomcat:7.0.40:jar
[INFO] Configured Artifact: org.apache.tomcat:apache-tomcat:windows-x64:7.0.40:zip
[INFO] Unpacking /Users/pochen/.m2/repository/org/apache/tomcat/apache-tomcat/7.0.40/apache-tomcat-7.0.40-windows-x64.zip to /Users/pochen/Code/amps-standalone/target/container/tomcat7x with includes "" and excludes ""
[INFO] Starting jira on the tomcat7x container on ports 2990 (http), 49785 (rmi) and 8009 (ajp)
[INFO] using codehaus cargo v1.4.7
[INFO] [2.ContainerStartMojo] Resolved container artifact org.codehaus.cargo:cargo-core-container-tomcat:jar:1.4.7 for container tomcat7x
[INFO] [talledLocalContainer] Tomcat 7.x starting...
[INFO] [stalledLocalDeployer] Deploying [/Users/pochen/Code/amps-standalone/target/jira/jira.war] to [/Users/pochen/Code/amps-standalone/target/container/tomcat7x/cargo-jira-home/webapps]...
[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.
[WARNING] [talledLocalContainer] 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.
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 26:00 min
[INFO] Finished at: 2014-06-16T14:31:54+10:00
[INFO] Final Memory: 15M/55M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.atlassian.maven.plugins:maven-amps-plugin:5.0.2:run-standalone (default-cli) on project standalone-pom: Unable to execute mojo: Execution null of goal org.codehaus.cargo:cargo-maven2-plugin:1.4.7:start failed: Deployable [http://localhost:2990/cargocpc/index.html] failed to finish deploying within the timeout period [600000]. The Deployable state is thus unknown. -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

[Seb Ruiz]

Hi Po,

You should start by deleting everything in the amps-standalone directory. If you have run atlas-run in this directory before it may be polluted with an old version of JIRA or plugins. I would also make sure that you are running on the latest version of the atlassian sdk, 4.2.20.

Let us know how that goes.

--
You received this message because you are subscribed to the Google Groups "Atlassian Connect Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to atlassian-connec...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Seb Ruiz

Atlassian

[Po Chen]

Hi Seb,

Thanks for the quick reply.

I actually started with the folder deleted.
Isn't the latest version 5.0.2 btw?

Thank you again!

On Monday, June 16, 2014 2:46:51 PM UTC+10, Seb Ruiz wrote:

Hi Po,

You should start by deleting everything in the amps-standalone directory. If you have run atlas-run in this directory before it may be polluted with an old version of JIRA or plugins. I would also make sure that you are running on the latest version of the atlassian sdk, 4.2.20.

Let us know how that goes.

--

Seb Ruiz

Atlassian

[Po Chen]

Hi Seb,

Thanks for the help.

My colleague helped me solve the problem.
It was the evil anti-virus program slowing everything down, jira is all good.

Thank you!

[Seb Ruiz]

Glad to hear it's working now!

--

You received this message because you are subscribed to the Google Groups "Atlassian Connect Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to atlassian-connec...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Seb Ruiz

Atlassian