Confluence install appears to hang when loading users and groups from Jira

Hayden Stainsby November 29, 2012

I am installing a trial version of Confluence and attaching it to a trial version of Jira which is already installed (on the same machine).

During Set up user management step of the installation the connection with Jira fails once, claiming that there is no Jira version 4.3 or higher at the given URL. I must then go into the Application Links in Jira and delete the newly created Confluence link and try again.

This works, the connection is made. However, at the next screen on the same step (Load users and groups from JIRA), the whole process seems to halt. There is text on the screen saying Performing full synchronisation, and Time Elapsed: Less than a second, but the Next button remains disabled.

I have tried stopping and starting Confluence and also removing and reinstalling Confluence completely, however I always end up at the same screen. I have pasted end of the catalina.out log below.

As an extra point to note, I have FishEye (also a trial) on the same machine and that connected to Jira without any problems.

30-Nov-2012 15:53:56 org.apache.tomcat.util.digester.SetPropertiesRule begin

WARNING: SetPropertiesRule {Server} Setting property 'debug' to '0' did not find a matching property.

30-Nov-2012 15:53:56 org.apache.tomcat.util.digester.SetPropertiesRule begin

WARNING: SetPropertiesRule {Server/Service/Engine} Setting property 'debug' to '0' did not find a matching property.

30-Nov-2012 15:53:56 org.apache.tomcat.util.digester.SetPropertiesRule begin

WARNING: SetPropertiesRule {Server/Service/Engine/Host} Setting property 'debug' to '0' did not find a matching property.

30-Nov-2012 15:53:56 org.apache.tomcat.util.digester.SetPropertiesRule begin

WARNING: SetPropertiesRule {Server/Service/Engine/Host/Context} Setting property 'debug' to '0' did not find a matching property.

30-Nov-2012 15:53:56 org.apache.coyote.http11.Http11Protocol init

INFO: Initializing Coyote HTTP/1.1 on http-8090

30-Nov-2012 15:53:56 org.apache.catalina.startup.Catalina load

INFO: Initialization processed in 533 ms

30-Nov-2012 15:53:56 org.apache.catalina.core.StandardService start

INFO: Starting service Tomcat-Standalone

30-Nov-2012 15:53:56 org.apache.catalina.core.StandardEngine start

INFO: Starting Servlet Engine: Apache Tomcat/6.0.32

2012-11-30 15:53:58,526 INFO main com.atlassian.confluence.lifecycle contextInitialized Starting Confluence 4.3.3 (build #3393, rfbf97d65fc2202c1ad8db08fef99ff488e0d596b)

30-Nov-2012 15:54:13 org.apache.coyote.http11.Http11Protocol start

INFO: Starting Coyote HTTP/1.1 on http-8090

30-Nov-2012 15:54:13 org.apache.catalina.startup.Catalina start

INFO: Server startup in 17044 ms

30-Nov-2012 16:05:11 com.sun.jersey.server.impl.application.WebApplicationImpl _initiate

INFO: Initiating Jersey application, version 'Jersey: 1.8-atlassian-6 03/12/2012 02:59 PM'

30-Nov-2012 16:05:12 com.sun.jersey.server.impl.application.WebApplicationImpl _initiate

INFO: Initiating Jersey application, version 'Jersey: 1.8-atlassian-6 03/12/2012 02:59 PM'

30-Nov-2012 16:05:12 com.sun.jersey.api.wadl.config.WadlGeneratorLoader loadWadlGenerator

INFO: Loading wadlGenerator com.sun.jersey.server.wadl.generators.WadlGeneratorApplicationDoc

30-Nov-2012 16:05:12 com.sun.jersey.api.wadl.config.WadlGeneratorLoader loadWadlGenerator

INFO: Loading wadlGenerator com.sun.jersey.server.wadl.generators.WadlGeneratorGrammarsSupport

30-Nov-2012 16:05:12 com.sun.jersey.api.wadl.config.WadlGeneratorLoader loadWadlGenerator

INFO: Loading wadlGenerator com.atlassian.plugins.rest.doclet.generators.resourcedoc.AtlassianWadlGeneratorResourceDocSupport

30-Nov-2012 16:05:42 com.sun.jersey.server.impl.application.WebApplicationImpl _initiate

INFO: Initiating Jersey application, version 'Jersey: 1.8-atlassian-6 03/12/2012 02:59 PM'

3 answers

1 accepted

1 vote
Answer accepted
Boris Berenberg
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.
December 1, 2012

Hey Hayden,

I think you may want to open a support case for this. An engineer will need to look through your logs to troubleshoot this issue. See the information on how to do this here: https://confluence.atlassian.com/display/DOC/Troubleshooting+Problems+and+Requesting+Technical+Support#TroubleshootingProblemsandRequestingTechnicalSupport-Method1:UsingtheSupportRequestFormviatheConfluenceAdministrationConsole

Cheers,
Boris

Hayden Stainsby December 6, 2012

This question was generated from a support request, which got promptly resolved (so this is the right answer).

It turned out that setting up confluence without the Jira integration and then adding it afterewards worked (what the support person advised me to do).

0 votes
Murray Kopit December 10, 2013
0 votes
Deleted user October 15, 2013

Love the workaround - but a fix would be nice

Suggest an answer

Log in or Sign up to answer