Problem with starting up jira. How to ignore the warning below and start jira.

[Irina Svirkina]

Problem with Jira 7.12: atlas-integration-test doesn't run tests and writes "Waiting for http://localhost:2990/jira to start" message infinity.

Details:

I develop a plugin for Jira.

Starting from Jira 7.12, atlas-run/atlas-debug/atlas-integration-test run Jira with the next warning on startup: "Your memory allocation pool settings need attention"

I can click "ignore all warnings and continue" during manual testing, but how can I suppress the warning, when I run tests with help of atlas-integration-test?

As I understood, atlas-integration-test thinks, that Jira hasn't been started, so the logs are:

[INFO] jira props: {jira.context=/jira, jira.protocol=http, jira.xml.data.location=/media/NewVolume/Projects/APD/Git_Plugin/jira-git-plugin/code/src/test/xml, jira.port=2990, jira.host=localhost}
[INFO] [talledLocalContainer] 2018-08-31 17:57:07,759 Caesium-1-3 INFO ServiceRunner     [c.a.jira.startup.IndexRecoveryLauncher] Recover Issue Index - end
[INFO] [talledLocalContainer] 2018-08-31 17:57:08,843 ForkJoinPool.commonPool-worker-1 INFO ServiceRunner     [c.a.j.cache.soy.SoyCacheWarmer] Warmed 41 soy module(s) in 4194 ms, 0 module(s) were not present or disabled, 0 failed.
[INFO] Waiting for http://localhost:2990/jira to start
[INFO] Waiting for http://localhost:2990/jira to start
[INFO] Waiting for http://localhost:2990/jira to start
[INFO] Waiting for http://localhost:2990/jira to start
[INFO] Waiting for http://localhost:2990/jira to start
[INFO] [talledLocalContainer] 2018-08-31 17:57:13,787 ForkJoinPool.commonPool-worker-2 INFO ServiceRunner     [c.a.jira.i18n.I18nWarmer] Initialised i18n cache in 9140
[INFO] [talledLocalContainer] 2018-08-31 17:57:13,787 Caesium-1-1 INFO ServiceRunner     [c.a.jira.startup.CacheWarmerLauncher] Warmed cache(s) in 9146 ms.
[INFO] Waiting for http://localhost:2990/jira to start
[INFO] Waiting for http://localhost:2990/jira to start
[INFO] Waiting for http://localhost:2990/jira to start
[INFO] Waiting for http://localhost:2990/jira to start
[INFO] Waiting for http://localhost:2990/jira to start
[INFO] Waiting for http://localhost:2990/jira to start
[INFO] Waiting for http://localhost:2990/jira to start
[INFO] Waiting for http://localhost:2990/jira to start
[INFO] Waiting for http://localhost:2990/jira to start
[INFO] Waiting for http://localhost:2990/jira to start
[INFO] Waiting for http://localhost:2990/jira to start
[INFO] Waiting for http://localhost:2990/jira to start
[INFO] Waiting for http://localhost:2990/jira to start
[INFO] Waiting for http://localhost:2990/jira to start
[INFO] [talledLocalContainer] 2018-08-31 17:57:27,797 Caesium-1-1 INFO ServiceRunner     [c.a.j.p.h.service.connect.InstallGlancesJobHandler] Running InstallGlancesJobHandler...
[INFO] [talledLocalContainer] 2018-08-31 17:57:27,799 Caesium-1-1 DEBUG ServiceRunner     [c.a.activeobjects.osgi.ActiveObjectsServiceFactory] getService bundle [com.atlassian.plugins.base-hipchat-integration-plugin-api]
[INFO] [talledLocalContainer] 2018-08-31 17:57:27,804 Caesium-1-1 INFO ServiceRunner     [c.a.j.p.h.service.connect.InstallGlancesJobHandler] There is no link to HipChat, no need to install glances.
[INFO] Waiting for http://localhost:2990/jira to start
[INFO] Waiting for http://localhost:2990/jira to start
[INFO] Waiting for http://localhost:2990/jira to start
[INFO] Waiting for http://localhost:2990/jira to start
[INFO] [talledLocalContainer] 2018-08-31 17:57:32,185 Caesium-1-4 INFO      [c.a.j.p.h.service.ping.RefreshConnectionStatusJobHandler] Running RefreshConnectionStatusJobHandler...
[INFO] Waiting for http://localhost:2990/jira to start
[INFO] Waiting for http://localhost:2990/jira to start
[INFO] Waiting for http://localhost:2990/jira to start
[INFO] Waiting for http://localhost:2990/jira to start
[INFO] Waiting for http://localhost:2990/jira to start

[Nic Brough -Adaptavist- · Accepted solution]

You should not ignore the warning, your Jira will rapidly run out of memory and halt if run with less than 384m

[Irina Svirkina]

I setup maven-jira-plugin with -Xms (see below). It helped.

<plugin>
    <groupId>com.atlassian.maven.plugins</groupId>
    <artifactId>maven-jira-plugin</artifactId>
    <version>${amps.version}</version>
    <extensions>true</extensions>
    <configuration>
        <jvmArgs>-Xms512m</jvmArgs>
    </configuration>
</plugin>