Hello-world atlas-run cannot start JIRA instance

Hi geeks!

I am going through the tutorial on JIRA server plugins: https://developer.atlassian.com/server/framework/atlassian-sdk/create-a-helloworld-plugin-project/

trying the very first steps and am getting errors.
All I did is:

At the same time an addon for Confluence builds and runs smoothly…
Please advise.

OS: Win 10
atlassian-sdk: 6.3.6

The first errors concern missing files in the cargo-jira-home folder:

INFO] [talledLocalContainer] Jan 18, 2018 7:18:53 PM org.apache.tomcat.util.scan.StandardJarScanner scan
[WARNING] [talledLocalContainer] WARNING: Failed to scan [file:/C:/projects/portfolio-goggles/portfolio-goggles-server-addon/target/container/tomcat8x/cargo-jira-home/common/lib/p6psy.jar] from classloader hierarchy
[INFO] [talledLocalContainer] java.io.FileNotFoundException: C:\projects\portfolio-goggles\portfolio-goggles-server-addon\target\container\tomcat8x\cargo-jira-home\common\lib\p6psy.jar (Cannot find the file specified)
[INFO] [talledLocalContainer] at java.util.zip.ZipFile.open(Native Method)
[INFO] [talledLocalContainer] at java.util.zip.ZipFile.(ZipFile.java:225)
[INFO] [talledLocalContainer] at java.util.zip.ZipFile.(ZipFile.java:155)
[INFO] [talledLocalContainer] at java.util.jar.JarFile.(JarFile.java:166)
[INFO] [talledLocalContainer] at java.util.jar.JarFile.(JarFile.java:130)
[INFO] [talledLocalContainer] at org.apache.tomcat.util.scan.JarFileUrlJar.(JarFileUrlJar.java:60)
[INFO] [talledLocalContainer] at org.apache.tomcat.util.scan.JarFactory.newInstance(JarFactory.java:48)
[INFO] [talledLocalContainer] at org.apache.tomcat.util.scan.StandardJarScanner.process(StandardJarScanner.java:338)
[INFO] [talledLocalContainer] at org.apache.tomcat.util.scan.StandardJarScanner.scan(StandardJarScanner.java:288)
[INFO] [talledLocalContainer] at org.apache.jasper.servlet.TldScanner.scanJars(TldScanner.java:262)
[INFO] [talledLocalContainer] at org.apache.jasper.servlet.TldScanner.scan(TldScanner.java:104)
[INFO] [talledLocalContainer] at org.apache.jasper.servlet.JasperInitializer.onStartup(JasperInitializer.java:101)
[INFO] [talledLocalContainer] at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5178)
[INFO] [talledLocalContainer] at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
[INFO] [talledLocalContainer] at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:724)
[INFO] [talledLocalContainer] at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:700)
[INFO] [talledLocalContainer] at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:734)
[INFO] [talledLocalContainer] at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:952)
[INFO] [talledLocalContainer] at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1823)
[INFO] [talledLocalContainer] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
[INFO] [talledLocalContainer] at java.util.concurrent.FutureTask.run(FutureTask.java:266)
[INFO] [talledLocalContainer] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
[INFO] [talledLocalContainer] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
[INFO] [talledLocalContainer] at java.lang.Thread.run(Thread.java:748)

Hi @piotr - just ran it myself on the Mac, and getting a lot of warning/info messages like you; however, it did end up spinning up an instance. Did you get any fatal error messages (not warnings) that you can share? I don’t have a Windows machine handy, but perhaps a complete dump of console output will reveal the culprit.

The warnings you’ve provided show up all the time. They are not the reason the application is not starting.

Hi Piotr,
Sorry to hear you’re running into trouble.
I just gave this a go on Windows 10 and it was ok, but - I didn’t actually have time to go through all the steps in the tutorial.
What I would recommend, based on your errors is that you try an atlas-clean in the plugin directory you created. That should remove the whole target directory including the cargo files and then it will be re-created from scratch with your next run of atlas-run.
Finally, if you’re still stuck try the following command:
atlas-run-standalone --product jira --version 7.6.1 --data-version 7.6.1


Thanks very much guys,

It is working now ! Not sure what did the trick, here is what I did:

I first ran

atlas-run-standalone --product jira --version 7.6.1 --data-version 7.6.1, which worked fine


atlas-run --version 7.6.1 --data-version 7.6.1, on opening jira informed it upgraded to 7.6.1

and then

atlas-run started working as expected.

1 Like

Hi Piotr,

Glad to hear you got it working.

Running atlas-run-standalone will create a new folder in your project directory with a name like amps-standalone-jira-7.6.1 - and it won’t start your plugin within JIRA, so you might want to delete that folder to keep your project directory tidy.

I’m glad to hear you managed to get it working in the end - however atlas-run alone should work, the --version and --data-version commands will over-ride the JIRA version you set in your POM.

Let me know if you get atlas-run working as well (you may find you need to run an atlas-clean in between).

I believe the upgrade message is a bug in JIRA. Check out the ticket JRASERVER-66176