← Back to team overview

dhis2-users team mailing list archive

Re: Dhis2 start up problem

 

Hi Isika

It looks to me like the startup error must have occurred earlier in your
log.  Can you check?  Either that or there is some kind of silent error
thrown somewhere between startup task 6 and 7.

Bob


On 28 October 2013 16:13, Isika Oliver <ioliver750@xxxxxxxxx> wrote:

> Hi all,
> Am experiencing the following, my tomcat is running well but running dhis
> is the problem
>
>
> * INFO  2013-10-28 19:06:02,700 Found the following message senders:
> [org.hisp.dhis.message.EmailMessageSender@d34fab,
> org.hisp.dhis.sms.outbound.SmsSender@1136a21] (DefaultMessageService.java
> [http-bio-8080-exec-2])
> * INFO  2013-10-28 19:06:11,689 Camel context started
> (DHIS2LifecycleStrategy.java [http-bio-8080-exec-2])
> * INFO  2013-10-28 19:06:11,690 Searching for routes in directory:
> /opt/dhis2/routes (DHIS2LifecycleStrategy.java [http-bio-8080-exec-2])
> * INFO  2013-10-28 19:06:12,179 Executing startup routine [1 of 10,
> runlevel 1]: TableAlteror (DefaultStartupRoutineExecutor.java
> [http-bio-8080-exec-2])
> * INFO  2013-10-28 19:06:14,919 Tables updated (TableAlteror.java
> [http-bio-8080-exec-2])
> * INFO  2013-10-28 19:06:14,920 Executing startup routine [2 of 10,
> runlevel 1]: MapViewUpgrader (DefaultStartupRoutineExecutor.java
> [http-bio-8080-exec-2])
> * INFO  2013-10-28 19:06:15,007 Executing startup routine [3 of 10,
> runlevel 2]: IdentityPopulator (DefaultStartupRoutineExecutor.java
> [http-bio-8080-exec-2])
> * INFO  2013-10-28 19:06:15,785 Executing startup routine [4 of 10,
> runlevel 2]: PeriodTypePopulator (DefaultStartupRoutineExecutor.java
> [http-bio-8080-exec-2])
> * INFO  2013-10-28 19:06:15,816 Executing startup routine [5 of 10,
> runlevel 3]: TableCreator (DefaultStartupRoutineExecutor.java
> [http-bio-8080-exec-2])
> * INFO  2013-10-28 19:06:15,833 Executing startup routine [6 of 10,
> runlevel 3]: DataElementDefaultDimensionPopulator
> (DefaultStartupRoutineExecutor.java [http-bio-8080-exec-2])
> * INFO  2013-10-28 19:06:15,889 Added default concept
> (DataElementDefaultDimensionPopulator.java [http-bio-8080-exec-2])
> * INFO  2013-10-28 19:06:16,069 Added default category
> (DataElementDefaultDimensionPopulator.java [http-bio-8080-exec-2])
> Oct 28, 2013 7:06:16 PM org.apache.catalina.core.StandardContext
> startInternal
> SEVERE: Error listenerStart
> Oct 28, 2013 7:06:16 PM org.apache.catalina.core.StandardContext
> startInternal
> SEVERE: Context [/dhis] startup failed due to previous errors
> * INFO  2013-10-28 19:06:16,085 De-registering jdbc driver:
> org.postgresql.Driver@a10b03 (StartupListener.java [http-bio-8080-exec-2])
> * INFO  2013-10-28 19:06:16,149 Camel context stopped
> (DHIS2LifecycleStrategy.java [http-bio-8080-exec-2])
> Oct 28, 2013 7:06:16 PM org.apache.catalina.loader.WebappClassLoader
> checkThreadLocalMapForLeaks
> SEVERE: The web application [/dhis] created a ThreadLocal with key of type
> [com.sun.xml.bind.v2.ClassFactory$1] (value
> [com.sun.xml.bind.v2.ClassFactory$1@907c2b]) and a value of type
> [java.util.WeakHashMap] (value [{class
> javax.xml.bind.annotation.adapters.CollapsedStringAdapter=java.lang.ref.WeakReference@1c822bc,
> class java.util.ArrayList=java.lang.ref.WeakReference@60658d, class
> org.apache.camel.model.PackageScanDefinition=java.lang.ref.WeakReference@ab4abf,
> class
> org.apache.camel.spring.CamelProducerTemplateFactoryBean=java.lang.ref.WeakReference@1b869f2,
> class
> org.apache.camel.spring.CamelContextFactoryBean=java.lang.ref.WeakReference@33b7c1}])
> but failed to remove it when the web application was stopped. Threads are
> going to be renewed over time to try and avoid a probable memory leak.
> Oct 28, 2013 7:06:16 PM org.apache.catalina.loader.WebappClassLoader
> checkThreadLocalMapForLeaks
> SEVERE: The web application [/dhis] created a ThreadLocal with key of type
> [java.lang.ThreadLocal] (value [java.lang.ThreadLocal@1650b17]) and a
> value of type
> [org.springframework.security.core.context.SecurityContextImpl] (value
> [org.springframework.security.core.context.SecurityContextImpl@ffffffff:
> Null authentication]) but failed to remove it when the web application was
> stopped. Threads are going to be renewed over time to try and avoid a
> probable memory leak.
>
> --
> Yours Truly.
> Munyao I. Oliver.
> P.o Box 1134,
> Kangundo,Kenya.
>
>
> *When you say "I can", and expect success, you fill yourself with
> confidence and happiness.*
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~dhis2-users
> Post to     : dhis2-users@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~dhis2-users
> More help   : https://help.launchpad.net/ListHelp
>
>

Follow ups

References