java.lang.ClassNotFoundException: ReverseList - During create plugin tutorial

[imc-juanf]

I have done installation steps to develop plugins:

• JAVA SDK,
• JAVA_HOME
• Jira Plugin SDK

When trying to run the example archetipe I get an exception, no one character written by my hand.

1. atlas-create-jira-plugin
2. cd <plugin-dir>
3. atlas-run

Can anyone help?

After 15 minutes:

[INFO] [talledLocalContainer] 2018-11-30 11:13:18,384 localhost-startStop-1 INFO [o.o.c.entity.jdbc.DatabaseUtil] Created function based indices for entity "IssueSecurityScheme"
[INFO] [talledLocalContainer] 2018-11-30 11:13:18,398 localhost-startStop-1 INFO [c.a.j.config.database.DatabaseConfigurationManagerImpl] The database is configured. Now running Database Checklist Launcher
[INFO] [talledLocalContainer] 2018-11-30 11:13:18,424 localhost-startStop-1 INFO [c.a.jira.startup.DatabaseChecklistLauncher] JIRA database startup checks completed successfully.
[INFO] [talledLocalContainer] 2018-11-30 11:13:18,424 localhost-startStop-1 INFO [c.a.j.config.database.DatabaseConfigurationManagerImpl] The database is configured. Now running Post database-configuration launchers
[INFO] [talledLocalContainer] 2018-11-30 11:13:25,409 localhost-startStop-1 INFO [c.a.j.config.database.SystemDatabaseConfigurationLoader] Reading database configuration from C:\Users\Juan\workspace\noc-jira-plugin\target\jira\home\dbconfig.xml
[INFO] [talledLocalContainer] 2018-11-30 11:13:29,317 localhost-startStop-1 INFO [c.a.j.c.embedded.ofbiz.OfBizUserDao] Using full user cache
[INFO] [talledLocalContainer] 2018-11-30 11:13:36,142 localhost-startStop-1 WARN [c.a.jira.startup.DatabaseLauncher]
[INFO] [talledLocalContainer]
[INFO] [talledLocalContainer] **************************************************************************************
[INFO] [talledLocalContainer] h2 is an in-memory database, and susceptible to corruption when abnormally terminated.
[INFO] [talledLocalContainer] DO NOT USE IN PRODUCTION, please switch to a regular database.
[INFO] [talledLocalContainer] **************************************************************************************
[INFO] [talledLocalContainer]
[INFO] [talledLocalContainer] 2018-11-30 11:13:36,142 localhost-startStop-1 INFO [c.a.jira.startup.DatabaseLauncher] Database transactions enabled: true
[INFO] [talledLocalContainer] 2018-11-30 11:13:36,145 localhost-startStop-1 INFO [c.a.jira.startup.DatabaseLauncher] Using JIRA's default for database transaction isolation level: 2
[INFO] [talledLocalContainer] 2018-11-30 11:13:36,163 localhost-startStop-1 INFO [c.a.jira.startup.JiraStartupLogger]
[INFO] [talledLocalContainer]
[INFO] [talledLocalContainer] Database configuration OK
[INFO] [talledLocalContainer]
[INFO] [talledLocalContainer] ___ Database Configuration ________________
[INFO] [talledLocalContainer]
[INFO] [talledLocalContainer] Loading entityengine.xml from : file:/C:/Users/Juan/workspace/noc-jira-plugin/target/container/tomcat8x/cargo-jira-home/webapps/jira/WEB-INF/classes/entityengine.xml
[INFO] [talledLocalContainer] Entity model field type name : h2
[INFO] [talledLocalContainer] Entity model schema name : PUBLIC
[INFO] [talledLocalContainer] Database Version : H2 - 1.4.185 (2015-01-16)
[INFO] [talledLocalContainer] Database Driver : H2 JDBC Driver - 1.4.185 (2015-01-16)
[INFO] [talledLocalContainer] Database URL : jdbc:h2:file:C:/Users/Juan/workspace/noc-jira-plugin/target/jira/home/database/h2db
[INFO] [talledLocalContainer] Database JNDI config : h2 java:comp/env/jdbc/JiraDS
[INFO] [talledLocalContainer]
[INFO] [talledLocalContainer] 2018-11-30 11:13:36,192 localhost-startStop-1 WARN [c.a.jira.diagnostic.PluginDiagnostics] Registering PluginDiagnostics with the event manager.
[INFO] [talledLocalContainer] 2018-11-30 11:13:36,740 localhost-startStop-1 INFO [c.a.jira.startup.JiraStartupLogger]
[INFO] [talledLocalContainer]
[INFO] [talledLocalContainer] ___ Starting the JIRA Plugin System _________________
[INFO] [talledLocalContainer]
[INFO] [talledLocalContainer] 2018-11-30 11:13:36,741 localhost-startStop-1 INFO [c.a.plugin.manager.DefaultPluginManager] Plugin system earlyStartup begun
[INFO] [talledLocalContainer] 2018-11-30 11:13:42,171 localhost-startStop-1 WARN [o.twdata.pkgscanner.ExportPackageListBuilder] Package Scanner found duplicates for package 'javax.transaction.xa' with different versions. Files: jta-1.0.1.jar and jta-1.0.1B.jar
[INFO] [talledLocalContainer] 'C:\Users\Juan\workspace\noc-jira-plugin\target\container\tomcat8x\cargo-jira-home\webapps\jira\WEB-INF\lib\jta-1.0.1.jar'
[INFO] [talledLocalContainer] 'C:\Users\Juan\workspace\noc-jira-plugin\target\container\tomcat8x\cargo-jira-home\common\lib\jta-1.0.1B.jar'
[INFO] [talledLocalContainer] 2018-11-30 11:13:42,171 localhost-startStop-1 WARN [o.twdata.pkgscanner.ExportPackageListBuilder] Package Scanner found duplicates for package 'javax.transaction' with different versions. Files: jta-1.0.1.jar and jta-1.0.1B.jar
[INFO] [talledLocalContainer] 'C:\Users\Juan\workspace\noc-jira-plugin\target\container\tomcat8x\cargo-jira-home\webapps\jira\WEB-INF\lib\jta-1.0.1.jar'
[INFO] [talledLocalContainer] 'C:\Users\Juan\workspace\noc-jira-plugin\target\container\tomcat8x\cargo-jira-home\common\lib\jta-1.0.1B.jar'
[INFO] [talledLocalContainer] Tomcat 8.x is stopped
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 43:04 min
[INFO] Finished at: 2018-11-30T11:14:14+01:00
[INFO] Final Memory: 52M/331M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.atlassian.maven.plugins:maven-amps-dispatcher-plugin:6.3.21:run (default-cli) on project noc-jira-plugin: Unable to execute mojo: Cannot start container [org.codehaus.cargo.container.tomcat.Tomcat8xInstalledLocalContainer@5c00de0d]: 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
Exception in thread "Thread-3" java.lang.NoClassDefFoundError: com/google/common/collect/Lists$ReverseList
at com.google.common.collect.Lists.reverse(Lists.java:729)
at com.atlassian.maven.plugins.amps.AbstractProductHandlerMojo.stopProducts(AbstractProductHandlerMojo.java:907)
at com.atlassian.maven.plugins.amps.RunMojo$1.run(RunMojo.java:107)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.ClassNotFoundException: com.google.common.collect.Lists$ReverseList
at org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50)
at org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:259)
at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:235)
at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:227)
... 4 more

[Bryan Turner]

@imc-juanf,

My answer on this similar question may help explain what's going on. I helped another app developer resolve an issue with Bitbucket Server failing to start within the timeout; in their case, it turned out to be overzealous anti-virus scanning significantly delaying startup.

Based on the paths in use it looks like you're on Windows. You might watch Task Manager while Jira is trying to start to see what processes are using CPU time. For example, to see whether Windows Defender's on-access scanning (or whatever anti-virus solution you're using) might be the culprit.

(In my answer I also explain the "ReverseList" exception but, to sum up, it's not actually related to the failure. It's just noise, and you can safely ignore it. It's not causing the failure to start Jira; it's happening because Jira failed to start.)

Best regards,
Bryan Turner
Atlassian Bitbucket

[Sarkis Chakarian]

@imc-juanf, looks like it was the JDK version. In my case I am using Mac and originally installed it with:

brew cask install java

 But this installs the latest version which is no longer 8. This caused atlas-run to crash. So the workaround is to remove the new java version and fall back to version 8. Here is what I did:

brew cask remove java
brew tap caskroom/versions
brew cask install java8

make sure that you also change your JAVA_HOME env variable properly. In my case I set it like this:

export JAVA_HOME="/Library/Java/JavaVirtualMachines/jdk1.8.0_192.jdk/Contents/Home"

As a last step you could run this command to test maven:

atlas-version

This did it for me. Hopefully it works for you too.

Note: if you can't get java8 via brew cask, try using AdoptOpenJDK: https://github.com/AdoptOpenJDK/homebrew-openjdk

[Hauke Hörhold]

I have the same problem now. Just openend a project I started about 6 months ago, and today it's throwing an error:

[ERROR] Failed to execute goal com.atlassian.maven.plugins:maven-amps-dispatcher-plugin:6.3.21:run (default-cli) on project jira-worklog-action: Unable to execute mojo: Cannot start container [org.codehaus.cargo.container.tomcat.Tomcat8xInstalledLocalContainer@5d7f4cbb]: Could not parse element: <parent><Resource name='jdbc/JiraDS'
[ERROR] type='javax.sql.DataSource'
[ERROR] auth='Container'
[ERROR] driverClassName='org.h2.Driver'
[ERROR] factory='org.apache.tomcat.dbcp.dbcp2.BasicDataSourceFactory'
[ERROR] password=''
[ERROR] url='jdbc:h2:file:C:/PRIVATESTUFF/target/jira/home/database/h2db'
[ERROR] username='sa'
[ERROR] />
[ERROR] </parent>
[ERROR] -> [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

And you say you solved it with another Java version?

[Sarkis Chakarian]

For the original question posted in this thread, Yes, after downgrading jdk to 1.8, I was able to solve this issue. As far as the issue you are having, I think it has to do with 

Could not parse element: <parent><Resource name='jdbc/JiraDS'

You appear to have some kind of config setup issue. But if it was running OK 6 months ago and you have not made any changes, I'd give it a shot in checking your java version as well.

[Hauke Hörhold]

I just updated everything (Atlassian SDK, AMPS, Java (to Version 1.8.0_212), but i still get this error.

But why the element couldn't be parsed? I dont get it...: Could not parse element: <parent><Resource name='jdbc/JiraDS'

[Sarkis Chakarian]

I am getting a similar error. I migrated my files over to new system and hat to install the sdk again but now atlas-run is throwing the same error. Which version of java are you using? I used to be on jdk1.8.0_151.jdk and now I am on openjdk-11.0.1.jdk. Wonder if this is the issue.

[Vasiliy Zverev]

Hi Juan!

If you want to develop a plugin, you should:

1) create a plugin skeleton

2) assemble it with IDE (I would reccoment IntelliJ IDEA for it)

3) Start test Jira instance

4) Add your plugin via UPM (universal Plugin Manager)

Best regards, Vasiliy

[imc-juanf]

Hello Vasiliy,

Thank you very much for the answer. I have been following the official guide, and as far as I can understand your point three is the step that is failing... atlas-run is the command to start the test jira instance.

It looks like maven building issue but it should be a starting jira error:

[ERROR] Failed to execute goal com.atlassian.maven.plugins:maven-amps-dispatcher-plugin:6.3.21:run (default-cli) on project noc-jira-plugin: Unable to execute mojo: Cannot start container [org.codehaus.cargo.container.tomcat.Tomcat8xInstalledLocalContainer@5c00de0d]: Deployable [http://localhost:2990/cargocpc/index.html] failed to finish deploying within the timeout period [600000]. The Deployable state is thus unknown. -> [Help 1] 

Regards.