Page 1 of 1

Jetty start ehcache conf warning regarding blSandBoxElements

Posted: Thu Nov 14, 2013 7:46 am
by shashikant.kulkarni
Hi,

When I try to run the jetty-demo ant target I get the following warning on console.

[artifact:mvn] [ WARN] 16:13:33 AbstractEhcacheRegionFactory - HHH020003: Could not find a specific ehcache configuration for cache named [blSandBoxElements]; using defaults.


After the above line, the jetty server takes 7+ min to display the following line.

[artifact:mvn] [ERROR] 16:20:50 Ejb3Configuration - HHH000050: Container is providing a null PersistenceUnitRootUrl: discovery impossible


The application still works but it takes lot of time to start.
Can someone tell me how to get rid of the error marked in blue to save 7 min to start jetty?

best regards.

Re: Jetty start ehcache conf warning regarding blSandBoxElements

Posted: Sat Nov 30, 2013 11:59 pm
by bpolster
The error being reported is likely not the cause of the 7 minute delay. We've noticed the long starts as well and plan to look into ways to speed application start up as part of an upcoming sprint.

The BLC core team is primarily using Tomcat/mySQL instead of Jetty/hsql and "update" instead of "create-drop" after the initial DB has been created for the "blPU.hibernate.hbm2ddl.auto" setting in development-shared.properties.

My startup time with this configuration is about 90 seconds. We plan to invest time in January to improve the Getting-Started guide with this as one of the topics. Appreciate any other tips from the community on startup optimization.