It is a custom .war file.
Debug is on default level. 
Currently I only have author instance.

The problem was resolved by increasing the available memory of the tomcat.

I will try it on debug level, and get back to you.

Thanks

Attila

-----Original Message-----
From: [email protected] 
[mailto:[email protected]] On Behalf Of Zdenek Skodik
Sent: 2010. szeptember 14. 15:41
To: Magnolia User-List
Subject: RE: [magnolia-user] Magnolia boot


Is it the war file provided by us or some custom yours?
And does it occur only during first startup (repository initializing)?

Anyway increasing logging level to DEBUG at your log4j.xml should shed more 
light to what it's happening within that 8minutes period.

Zdenek


                                                                                
                                                                                
                                                                                
   


On Tue, 2010-09-14 at 13:22 +0000, JAKABFI Attila wrote:
> The entire repository was deleted before the build.
>   All I had was the .war in the webapps, nothing else.
> 
> Attila
> 
> -----Original Message-----
> From: [email protected] 
> [mailto:[email protected]] On Behalf Of Zdenek Skodik
> Sent: 2010. szeptember 14. 14:49
> To: Magnolia User-List
> Subject: Re: [magnolia-user] Magnolia boot
> 
> 
> Hi
> 
> 
> On Tue, 2010-09-14 at 10:06 +0000, JAKABFI Attila wrote:
> > Hi
> > 
> >   Has anyone encountered this problem?
> 
> no
> 
> > 
> >   When I start Magnolia (with Tomcat) for the first time, during the boot 
> > process it waits for ~8 minutes at the following command.
> > 
> > 2010-09-14 11:28:10,769 INFO  
> > fo.magnolia.objectfactory.ObservedComponentFactory: Re-loaded 
> > info.magnolia.logging.AuditLoggingManager from /server/auditLogging
> > 
> > 2010-09-14 11:37:48,590 WARN  info.magnolia.importexport.BootstrapUtil      
> >     : Deleted already existing node for 
> > bootstrapping:/modules/cache/config/configurations/default/executors/store/serveContent
> > 
> >  
> 
> Maybe your config workspace indexes got corrupted when it last so long until 
> some existing node is resolved. 
> By deleting the index folder you'll enforce reindexing of the workspace upon 
> server startup.
> 
> Zdenek
> 
> > 
> > Thanks for the help,
> > 
> > Jakabfi Attila
> > 
> >  
> > 
> > 
> > 
> > 
> > 
> > ______________________________________________________________________
> > ----------------------------------------------------------------
> > For list details see
> > http://www.magnolia-cms.com/home/community/mailing-lists.html
> > To unsubscribe, E-mail to: <[email protected]>
> > ----------------------------------------------------------------
> 
> 
> 
> ----------------------------------------------------------------
> For list details see
> http://www.magnolia-cms.com/home/community/mailing-lists.html
> To unsubscribe, E-mail to: <[email protected]>
> ----------------------------------------------------------------
> 
> 
> 
> ----------------------------------------------------------------
> For list details see
> http://www.magnolia-cms.com/home/community/mailing-lists.html
> To unsubscribe, E-mail to: <[email protected]>
> ----------------------------------------------------------------



----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------



----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to