I can't run integration test because jira can not start.
[INFO] [talledLocalContainer] 2018-08-02 10:35:28,721 Caesium-1-2 INFO [c.a.j.upgrade.util.BuildNumberDao] Setting current build number to 77002
[INFO] [talledLocalContainer] 2018-08-02 10:35:28,733 Caesium-1-2 INFO [c.a.jira.upgrade.LicenseCheckingUpgradeService]
[INFO] [talledLocalContainer]
[INFO] [talledLocalContainer] *******************************************************************
[INFO] [talledLocalContainer] Upgrade Succeeded! JIRA has been upgraded to build number 77001
[INFO] [talledLocalContainer] *******************************************************************
[INFO] [talledLocalContainer]
[INFO] [talledLocalContainer] 2018-08-02 10:35:28,735 Caesium-1-2 INFO [c.a.jira.upgrade.UpgradeIndexManager] There is no reindex requests of type [IMMEDIATE, DELAYED] so none will be run
[INFO] [talledLocalContainer] 2018-08-02 10:35:28,735 Caesium-1-2 INFO [c.a.j.upgrade.util.BuildNumberDao] Setting current version to 7.7.1
[INFO] [talledLocalContainer] 2018-08-02 10:35:28,740 Caesium-1-2 INFO [c.a.j.upgrade.util.BuildNumberDao] Setting downgrade version to 7.1.2
[INFO] [talledLocalContainer] 2018-08-02 10:35:28,749 Caesium-1-2 INFO [c.a.jira.upgrade.LoggingUpgradeService] run upgrades has finished successfully, and took 275 milliseconds to process.
[INFO] [talledLocalContainer] 2018-08-02 10:35:28,750 Caesium-1-2 INFO [c.a.jira.upgrade.UpgradeScheduler] JIRA upgrades completed successfully
[INFO] [talledLocalContainer] 2018-08-02 10:35:28,753 Caesium-1-2 INFO [c.a.jira.upgrade.UpgradeScheduler] Plugins upgrades completed successfully
[INFO] [talledLocalContainer] 2018-08-02 10:35:28,754 Caesium-1-2 INFO [c.a.jira.upgrade.UpgradeIndexManager] Reindexing is not allowed after this upgrade and there is no immediate reindex requests
[INFO] [talledLocalContainer] Aug 02, 2018 10:35:30 AM com.sun.jersey.server.impl.application.WebApplicationImpl _initiate
[INFO] [talledLocalContainer] INFO: Initiating Jersey application, version 'Jersey: 1.19 02/11/2015 03:25 AM'
[INFO] [talledLocalContainer] 2018-08-02 10:35:31,633 Caesium-1-2 DEBUG [c.a.activeobjects.osgi.ActiveObjectsServiceFactory] getService bundle [com.atlassian.troubleshooting.plugin-jira]
[INFO] Waiting for http://tiens-mbp-2.mgm-edv.de:2990/jira to start
[INFO] Waiting for http://tiens-mbp-2.mgm-edv.de:2990/jira to start
[INFO] Waiting for http://tiens-mbp-2.mgm-edv.de:2990/jira to start
[INFO] Waiting for http://tiens-mbp-2.mgm-edv.de:2990/jira to start
[INFO] Waiting for http://tiens-mbp-2.mgm-edv.de:2990/jira to start
[INFO] Waiting for http://tiens-mbp-2.mgm-edv.de:2990/jira to start
[INFO] Waiting for http://tiens-mbp-2.mgm-edv.de:2990/jira to start
[INFO] Waiting for http://tiens-mbp-2.mgm-edv.de:2990/jira to start
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 13:44 min
[INFO] Finished at: 2018-08-02T10:44:42+01:00
[INFO] Final Memory: 63M/431M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.atlassian.maven.plugins:maven-jira-plugin:6.3.15:integration-test (default-integration-test) on project hierarchical-calculation-plugin: The product jira didn't start after 600s at http://tiens-mbp-2.mgm-edv.de:2990/jira. Operation timed out (Connection timed out) -> [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
Any body have idea about this ?
I just recently ran into this issue while updating one of our plugins for Jira 8 and found out that there is a configuration property `server` which can be used like so:
<groupId>com.atlassian.maven.plugins</groupId>
<artifactId>maven-jira-plugin</artifactId>
<version>${amps.version}</version>
<extensions>true</extensions>
<configuration>
<server>localhost</server>
</configuration>
It's very difficult to say with certainty what the problem is when just looking at this log. It is interesting that a restart of the OS appears to fix this. It might be worth following the suggesting in the error to rerun maven with the -e switch so that you can see further stacktraces that might help troubleshoot that.
On a side note, these versions of Jira have a known problem where startup can fail if you have clients trying to load specific jsp resource pages during the initial start up window. There was a rather hairy bug about this in https://jira.atlassian.com/browse/JRASERVER-62486
It was fixed in 7.7.4/7.8.4/7.9.1/7.10.0 and later versions. But your 7.7.1 version in this test build is also potentially affected by that bug.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
thank you,sir
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Whenever I met that error I restart my machine and it works again, but I also don't know the reason :(
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.