Strange behavior on startup - Initiating Jersey Application
Asked by JJ:

When starting Confluence, I get the following:

```
root@bckp:/usr/local/src/atlassian-confluence-5.4.3/bin# ./start-confluence.sh -fgexecuting as current userIf you encounter issues starting up Confluence Standalone, please see the Installation guide at http://confluence.atlassian.com/display/DOC/Confluence+Installation+GuideServer startup logs are located in /usr/local/src/atlassian-confluence-5.4.3/logs/catalina.outUsing CATALINA_BASE:   /usr/local/src/atlassian-confluence-5.4.3Using CATALINA_HOME:   /usr/local/src/atlassian-confluence-5.4.3Using CATALINA_TMPDIR: /usr/local/src/atlassian-confluence-5.4.3/tempUsing JRE_HOME:        /usr/local/src/atlassian-confluence-5.4.3/jre/Using CLASSPATH:       /usr/local/src/atlassian-confluence-5.4.3/bin/bootstrap.jarUsing CATALINA_PID:    /usr/local/src/atlassian-confluence-5.4.3/work/catalina.pidApr 11, 2014 2:49:45 PM org.apache.tomcat.util.digester.SetPropertiesRule beginWARNING: [SetPropertiesRule]{Server} Setting property 'debug' to '0' did not find a matching property.Apr 11, 2014 2:49:45 PM org.apache.tomcat.util.digester.SetPropertiesRule beginWARNING: [SetPropertiesRule]{Server/Service/Engine} Setting property 'debug' to '0' did not find a matching property.Apr 11, 2014 2:49:45 PM org.apache.tomcat.util.digester.SetPropertiesRule beginWARNING: [SetPropertiesRule]{Server/Service/Engine/Host} Setting property 'debug' to '0' did not find a matching property.Apr 11, 2014 2:49:45 PM org.apache.tomcat.util.digester.SetPropertiesRule beginWARNING: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting property 'debug' to '0' did not find a matching property.Apr 11, 2014 2:49:46 PM org.apache.coyote.http11.Http11Protocol initINFO: Initializing Coyote HTTP/1.1 on http-8090Apr 11, 2014 2:49:46 PM org.apache.catalina.startup.Catalina loadINFO: Initialization processed in 1108 msApr 11, 2014 2:49:46 PM org.apache.catalina.core.StandardService startINFO: Starting service Tomcat-StandaloneApr 11, 2014 2:49:46 PM org.apache.catalina.core.StandardEngine startINFO: Starting Servlet Engine: Apache Tomcat/6.0.352014-04-11 14:49:51,028 INFO [main] [com.atlassian.confluence.lifecycle] contextInitialized Starting Confluence 5.4.3 [build 4732 based on commit hash f543bd9a3bbc12daed85f6f5e5cba84282599932]Apr 11, 2014 2:51:50 PM org.apache.coyote.http11.Http11Protocol startINFO: Starting Coyote HTTP/1.1 on http-8090Apr 11, 2014 2:51:50 PM org.apache.catalina.startup.Catalina startINFO: Server startup in 124645 msApr 11, 2014 2:51:53 PM com.sun.jersey.server.impl.application.WebApplicationImpl _initiateINFO: Initiating Jersey application, version 'Jersey: 1.8-atlassian-11 03/22/2013 05:02 PM'Apr 11, 2014 2:51:53 PM com.sun.jersey.server.impl.application.WebApplicationImpl _initiateINFO: Initiating Jersey application, version 'Jersey: 1.8-atlassian-11 03/22/2013 05:02 PM'Apr 11, 2014 2:51:53 PM com.sun.jersey.api.wadl.config.WadlGeneratorLoader loadWadlGeneratorINFO: Loading wadlGenerator com.sun.jersey.server.wadl.generators.WadlGeneratorApplicationDocApr 11, 2014 2:51:54 PM com.sun.jersey.api.wadl.config.WadlGeneratorLoader loadWadlGeneratorINFO: Loading wadlGenerator com.sun.jersey.server.wadl.generators.WadlGeneratorGrammarsSupportApr 11, 2014 2:51:54 PM com.sun.jersey.api.wadl.config.WadlGeneratorLoader loadWadlGeneratorINFO: Loading wadlGenerator com.atlassian.plugins.rest.doclet.generators.resourcedoc.AtlassianWadlGeneratorResourceDocSupportApr 11, 2014 2:52:23 PM com.sun.jersey.server.impl.application.WebApplicationImpl _initiateINFO: Initiating Jersey application, version 'Jersey: 1.8-atlassian-11 03/22/2013 05:02 PM'Apr 11, 2014 2:52:23 PM com.sun.jersey.server.impl.application.WebApplicationImpl _initiateINFO: Initiating Jersey application, version 'Jersey: 1.8-atlassian-11 03/22/2013 05:02 PM'Apr 11, 2014 2:52:23 PM com.sun.jersey.server.impl.application.WebApplicationImpl _initiateINFO: Initiating Jersey application, version 'Jersey: 1.8-atlassian-11 03/22/2013 05:02 PM'Apr 11, 2014 2:52:23 PM com.sun.jersey.api.wadl.config.WadlGeneratorLoader loadWadlGeneratorINFO: Loading wadlGenerator com.sun.jersey.server.wadl.generators.WadlGeneratorApplicationDocApr 11, 2014 2:52:23 PM com.sun.jersey.api.wadl.config.WadlGeneratorLoader loadWadlGeneratorINFO: Loading wadlGenerator com.sun.jersey.server.wadl.generators.WadlGeneratorGrammarsSupportApr 11, 2014 2:52:23 PM com.sun.jersey.api.wadl.config.WadlGeneratorLoader loadWadlGeneratorINFO: Loading wadlGenerator com.atlassian.plugins.rest.doclet.generators.resourcedoc.AtlassianWadlGeneratorResourceDocSupportApr 11, 2014 2:52:24 PM com.sun.jersey.server.impl.application.WebApplicationImpl _initiateINFO: Initiating Jersey application, version 'Jersey: 1.8-atlassian-11 03/22/2013 05:02 PM'Apr 11, 2014 2:52:25 PM com.sun.jersey.server.impl.application.WebApplicationImpl _initiateINFO: Initiating Jersey application, version 'Jersey: 1.8-atlassian-11 03/22/2013 05:02 PM'Apr 11, 2014 2:53:50 PM com.sun.jersey.server.impl.application.WebApplicationImpl _initiateINFO: Initiating Jersey application, version 'Jersey: 1.8-atlassian-11 03/22/2013 05:02 PM'
```

```
Please advise.
```


Answers:
author: Rilwan Ahmed
body: Hi,

Even I am seeing the issue. And later I see the thread dump issue. see logs below.

Aug 08, 2015 8:33:04 PM com.sun.jersey.server.impl.application.WebApplicationImpl _initiate  
INFO: Initiating Jersey application, version 'Jersey: 1.8-atlassian-15 06/27/2014 08:32 AM'  
Aug 08, 2015 11:10:11 PM com.sun.jersey.server.impl.application.WebApplicationImpl _initiate  
INFO: Initiating Jersey application, version 'Jersey: 1.8-atlassian-15 06/27/2014 08:32 AM'  
Aug 08, 2015 11:21:46 PM com.sun.jersey.server.impl.application.WebApplicationImpl _initiate  
INFO: Initiating Jersey application, version 'Jersey: 1.8-atlassian-15 06/27/2014 08:32 AM'  
Aug 09, 2015 12:33:32 AM com.sun.jersey.server.impl.application.WebApplicationImpl _initiate  
INFO: Initiating Jersey application, version 'Jersey: 1.8-atlassian-15 06/27/2014 08:32 AM'  
2015-08-09 04:27:30  
Full thread dump Java HotSpot(TM) 64-Bit Server VM (23.25-b01 mixed mode):

"com.google.inject.internal.util.$Finalizer" daemon prio=10 tid=0x00007ff80c77e000 nid=0x6051 in Object.wait() \[0x00007ff7ca5db000\]  
java.lang.Thread.State: WAITING (on object monitor)  
at java.lang.Object.wait(Native Method)  
- waiting on \<0x0000000628f8c418\> (a java.lang.ref.ReferenceQueue$Lock)  
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:135)  
- locked \<0x0000000628f8c418\> (a java.lang.ref.ReferenceQueue$Lock)  
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:151)  
at com.google.inject.internal.util.$Finalizer.run(Finalizer.java:114)

comments: author: Robert Taylor
body: i'm also seeing this, the application seems to be up on this 2nd node, but i'm not sure if this is normal behaivoir.


author: Gerin Abraham
body: We are also seeing the above Initiating Jersey application INFO message. We are doing an upgrade from Confluence v3.5.6 to v5.0.3 in our LAB environment.


author: Jonathan Lin
body: Hi Felipe, I'm getting similar messages after starting the script ./start-confluence.sh. And It seems like it won't end. If I logout of my user on the unix server, the process stops and it requires me to keep the process running or else the server won't host confluence, which is not what I want. How do I get past this?

<br />

log4j:WARN Please initialize the log4j system properly.  
Feb 13, 2015 9:55:08 AM com.sun.jersey.server.impl.application.WebApplicationImpl _initiate  
INFO: Initiating Jersey application, version 'Jersey: 1.8-atlassian-15 06/27/2014 08:32 AM'  
Feb 13, 2015 9:56:26 AM com.sun.jersey.server.impl.application.WebApplicationImpl _initiate  
INFO: Initiating Jersey application, version 'Jersey: 1.8-atlassian-15 06/27/2014 08:32 AM'  
Feb 13, 2015 9:56:26 AM com.sun.jersey.api.wadl.config.WadlGeneratorLoader loadWadlGenerator  
INFO: Loading wadlGenerator com.sun.jersey.server.wadl.generators.WadlGeneratorApplicationDoc  
Feb 13, 2015 9:56:26 AM com.sun.jersey.api.wadl.config.WadlGeneratorLoader loadWadlGenerator  
INFO: Loading wadlGenerator com.sun.jersey.server.wadl.generators.WadlGeneratorGrammarsSupport  
Feb 13, 2015 9:56:26 AM com.sun.jersey.api.wadl.config.WadlGeneratorLoader loadWadlGenerator  
INFO: Loading wadlGenerator com.atlassian.plugins.rest.doclet.generators.resourcedoc.AtlassianWadlGeneratorResourceDocSupport  
Feb 13, 2015 9:56:28 AM com.sun.jersey.server.impl.application.WebApplicationImpl _initiate  
INFO: Initiating Jersey application, version 'Jersey: 1.8-atlassian-15 06/27/2014 08:32 AM'  
Feb 13, 2015 9:56:29 AM com.sun.jersey.server.impl.application.WebApplicationImpl _initiate  
INFO: Initiating Jersey application, version 'Jersey: 1.8-atlassian-15 06/27/2014 08:32 AM'  
Feb 13, 2015 9:56:30 AM com.sun.jersey.server.impl.application.WebApplicationImpl _initiate  
INFO: Initiating Jersey application, version 'Jersey: 1.8-atlassian-15 06/27/2014 08:32 AM'  
Feb 13, 2015 9:56:32 AM com.sun.jersey.server.impl.application.WebApplicationImpl _initiate  
INFO: Initiating Jersey application, version 'Jersey: 1.8-atlassian-15 06/27/2014 08:32 AM'  
Feb 13, 2015 9:56:45 AM com.sun.jersey.server.impl.application.WebApplicationImpl _initiate  
INFO: Initiating Jersey application, version 'Jersey: 1.8-atlassian-15 06/27/2014 08:32 AM'  
Feb 13, 2015 9:56:47 AM com.sun.jersey.server.impl.application.WebApplicationImpl _initiate  
INFO: Initiating Jersey application, version 'Jersey: 1.8-atlassian-15 06/27/2014 08:32 AM'  
Feb 13, 2015 9:56:48 AM com.sun.jersey.server.impl.application.WebApplicationImpl _initiate  
INFO: Initiating Jersey application, version 'Jersey: 1.8-atlassian-15 06/27/2014 08:32 AM


author: FelipeA
body: Hi Jay,

We use [Jersey](https://jersey.java.net) to handle requests to Confluence Remote API, so the messages you're seeing are perfectly normal, as Adrien stated, and unrelated to the spikes you're perceiving.

Best regards,

Felipe Alencastro


author: Adrien Ragot 2
body: Hi Jay,

This basically says that all is good and Confluence has started. Is there anything that doesn't work?

Cheers,

Adrien

comments: author: JJ
body: Yes, but I believe the fact that it can't start the Jersey process is what's causing spikes in CPU and RAM consumption for this server, so I just wanted to figure out what that particular process does.