Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Top groups
Explore all groups
Community resources
Learn
Community resources
Events
Community resources

Unable to run the "atlas-standalone --product jira" command

Mikes2
Mikes May 21, 2013

Hello,

I am following the tutorial "Explore the installed SDK and the atlas commands" and whenever I try to run the "atlas-standalone --product jira" command I get this:

c:\atlasttutorial>atlas-run-standalone --product jira
Executing: "C:\Users\Michael\atlassian-plugin-sdk\apache-maven\bin\mvn.bat" com.
atlassian.maven.plugins:maven-amps-plugin:4.2.0:run-standalone -gs C:\Users\Mich
ael\atlassian-plugin-sdk\apache-maven/conf/settings.xml -Dproduct=jira
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Building Maven Default Project
[INFO]    task-segment: [com.atlassian.maven.plugins:maven-amps-plugin:4.2.0: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 add
ing <allowGoogleTracking>false</allowGoogleTracking> to the amps plugin configur
ation 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 add
ing <allowGoogleTracking>false</allowGoogleTracking> to the amps plugin configur
ation in your pom.xml
[INFO] Sending event to Google Analytics: AMPS:jira - Run
[INFO]
[INFO] Starting jira... (see log at c:\atlasttutorial\amps-standalone\target/jir
a-LATEST.log)
[INFO] determining latest stable data version...
[INFO] using latest stable data version: 6.0
[INFO] [dependency:copy]
[INFO] Configured Artifact: com.atlassian.jira.plugins:jira-plugin-test-resource
s:6.0:zip
[INFO] Copying jira-plugin-test-resources-6.0.zip to c:\atlasttutorial\amps-stan
dalone\target\jira\jira-plugin-test-resources.zip
[INFO] determining latest stable product version...
[INFO] using latest stable product version: 6.0
[INFO] [dependency:copy {execution: virtual-execution}]
[INFO] Configured Artifact: com.atlassian.jira:atlassian-jira-webapp:6.0:war
[INFO] Copying atlassian-jira-webapp-6.0.war to c:\atlasttutorial\amps-standalon
e\target\jira\jira-original.war
[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:\atlasttutorial\amps-standalone\ta
rget\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:\atlasttutorial\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:j
ar
[INFO] Copying org.apache.felix.webconsole-1.2.8.jar to c:\atlasttutorial\amps-s
tandalone\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:\atlasttutorial\amps-standalon
e\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:\atlasttutorial\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:\atlasttutorial\amps-standalone\targe
t\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:\atlasttutorial\amps-stan
dalone\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:\atlasttutorial\amps-standalone\t
arget\jira\home\plugins\installed-plugins\plugin-data-editor-1.2.jar
[INFO] Unpacking container 'tomcat6x' from container artifact: org.apache.tomcat
:apache-tomcat:6.0.20:jar
[INFO] [dependency:unpack {execution: virtual-execution}]
[INFO] Configured Artifact: org.apache.tomcat:apache-tomcat:6.0.20:zip
[INFO] Unpacking C:\Users\Michael\.m2\repository\org\apache\tomcat\apache-tomcat
\6.0.20\apache-tomcat-6.0.20.zip to c:\atlasttutorial\amps-standalone\target\con
tainer\tomcat6x with includes "" and excludes ""
[INFO] Starting jira on the tomcat6x container on ports 2990 (http) and 49750 (r
mi)
[INFO] using codehaus cargo v1.2.3
[INFO] [cargo:start]
[INFO] [2.ContainerStartMojo] Resolved container artifact org.codehaus.cargo:car
go-core-container-tomcat:jar:1.2.3 for container tomcat6x
[INFO] [stalledLocalDeployer] Deploying [c:\atlasttutorial\amps-standalone\targe
t\jira\jira.war] to [c:\atlasttutorial\amps-standalone\target\container\tomcat6x
\cargo-jira-home/webapps]...
[INFO] [talledLocalContainer] Tomcat 6.x starting...
[INFO] [yer.DeployerWatchdog] Deployable [http://localhost:2990/cargocpc/index.h
tml] failed to finish deploying within the timeout period [600000]. The Deployab
le state is thus unknown.
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Unable to execute mojo

Deployable [http://localhost:2990/cargocpc/index.html] failed to finish deployin
g within the timeout period [600000]. The Deployable state is thus unknown.
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 11 minutes 33 seconds
[INFO] Finished at: Wed May 22 16:56:08 EEST 2013
[INFO] Final Memory: 52M/261M
[INFO] ------------------------------------------------------------------------

I tried also the -e switch parameter and I got this:

c:\atlasttutorial>atlas-run-standalone --product jira -e
Executing: "C:\Users\Michael\atlassian-plugin-sdk\apache-maven\bin\mvn.bat" com.
atlassian.maven.plugins:maven-amps-plugin:4.2.0:run-standalone -gs C:\Users\Mich
ael\atlassian-plugin-sdk\apache-maven/conf/settings.xml -Dproduct=jira -e
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Building Maven Default Project
[INFO]    task-segment: [com.atlassian.maven.plugins:maven-amps-plugin:4.2.0:run
-standalone] (aggregator-style)
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
---------------------------------------------------
constituent[0]: file:/C:/Users/Michael/atlassian-plugin-sdk/apache-maven/bin/../
lib/maven-2.1.0-uber.jar
constituent[1]: file:/C:/Users/Michael/atlassian-plugin-sdk/apache-maven/bin/../
lib/maven-trap-0.5.jar
---------------------------------------------------
Exception in thread "main" java.lang.AbstractMethodError: java.lang.Throwable.ge
tMessage()Ljava/lang/String;
        at org.apache.maven.usability.diagnostics.ErrorDiagnostics$PuntErrorDiag
noser.diagnose(ErrorDiagnostics.java:133)
        at org.apache.maven.usability.diagnostics.ErrorDiagnostics.diagnose(Erro
rDiagnostics.java:107)
        at org.apache.maven.DefaultMaven.logDiagnostics(DefaultMaven.java:949)
        at org.apache.maven.DefaultMaven.logFatal(DefaultMaven.java:883)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:167)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:356)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:601)
        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)

I am completely new to this Maven build tool. Any help will be greatly appreciated.

Watch
Like Be the first to like this
2166 views

3 answers

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

2 votes
Answer accepted
Sultan Maiyaki
Sultan Maiyaki
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Get recognized
May 21, 2013

Hi,

This issue is most likely caused by an Anti virus software that scans through the directory you intended to start JIRA. You can add an exception to the antivirus to exclde that directory or disable it for while and try to see if that works.

View More Comments
Mikes2
Mikes May 22, 2013

You are right. I disabled the antivirus and it works. Thank you.

Like • Osman Turalioglu likes this
Alexej Geldt
Alexej Geldt
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Get recognized
June 3, 2013

is it actualy possible to increase that timeout?

sometimes my build process ends up in deployment timeout. Ive got no virus scanner running on my dev machine. However it may be slowed by home folder encryption.

Like • # people like this
Benjamin Hahne
Benjamin Hahne December 29, 2013

As someone working in an environment where tinkering with AV settings is out of the question, knowing how to increase the timeout would be valuable.

Like
Reply
1 vote
Fabian Christoffel
Fabian Christoffel February 4, 2014

You can set the time out in the pom of your plugin as follows:

<plugin>
	<groupId>com.atlassian.maven.plugins</groupId>
	<artifactId>maven-jira-plugin</artifactId>
	<version>${amps.version}</version>
	<extensions>true</extensions>
	<configuration>
		<productVersion>${jira.version}</productVersion>
		<productDataVersion>${jira.version}</productDataVersion>
		<startupTimeout>1200000</startupTimeout>
		<shutdownTimeout>600000</shutdownTimeout>
	</configuration>
</plugin>

View More Comments
Diego Ferreira
Diego Ferreira
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Get recognized
November 18, 2017

Thanks Fabian, that did the trick for me

Like
Reply
0 votes
Aniket Thakur
Aniket Thakur December 8, 2017

In my case I had configure maven to go offline using -

atlas-mvn dependency:go-offline

Then I added some dependency and post that Jira deployment was failing.

Running

atlas-mvn dependency:go-offline 
atlas-debug

again solved the deployment issue for me.

Reply
Atlassian logo
Answers Developer Questions
TAGS
AUG Leaders

Atlassian Community Events

    See all events