A typical Liferay server startup process

The following is a typical startup process for Liferay server:

01.May 3:09:32 AM Org.apache.catalina.core.AprLifecycleListener Init
02.info:the APR based Apache Tomcat Native Library which allows optimal performance in production environments is not fo und on the Java.library.path:d:\charles\softwares\java\jdk1.6.0_05\bin;
03.May 3:09:34 AM org.apache.coyote.AbstractProtocol Init
04.info:initializing Protocolhandler ["http-bio-8080"]
05.May 3:09:34 AM org.apache.coyote.AbstractProtocol Init
06.info:initializing Protocolhandler ["ajp-bio-8009"]
07.May 3:09:34 AM Org.apache.catalina.startup.Catalina Load
08.info:initialization processed in 2008 MS
09.May 3:09:34 AM Org.apache.catalina.core.StandardService startinternal
10.info:starting Service Catalina
11.May 3:09:34 AM org.apache.catalina.core.StandardEngine startinternal
12.info:starting Servlet Engine:apache tomcat/7.0.23
13.May 3:09:34 AM org.apache.catalina.startup.HostConfig deploydescriptor
14.info:deploying Configuration Descriptor D:\Liferay\RI\liferay-portal-6.1.0-ce-ga1\tomcat-7.0.23\conf\Catalina\ Localhost\root.xml
15.Loading jar:file:/d:/liferay/ri/liferay-portal-6.1.0-ce-ga1/tomcat-7.0.23/webapps/root/web-inf/lib/ Portal-impl.jar!/system.properties
16.03:09:36,919 INFO [easyconf:122] refreshed the configuration of all components
17.03:09:37,184 INFO [configurationloader:56] Properties for jar:file:/d:/liferay/ri/liferay-portal-6.1.0-ce-ga1/ Tomcat-7.0.23/webapps/root/web-inf/lib/portal-impl.jar!/portal loaded from [file:/d:/liferay/ri/ Liferay-portal-6.1.0-ce-ga1/tomcat-7.0.23/webapps/root/web-inf/classes/portal-developer.properties, file:/D:/ Liferay/ri/liferay-portal-6.1.0-ce-ga1/portal-ide.properties, file:/d:/liferay/ri/liferay-portal-6.1.0-ce-ga1/ Portal-setup-wizard.properties, jar:file:/d:/liferay/ri/liferay-portal-6.1.0-ce-ga1/tomcat-7.0.23/webapps/root/ Web-inf/lib/portal-impl.jar!/portal.properties]
18.Loading jar:file:/d:/liferay/ri/liferay-portal-6.1.0-ce-ga1/tomcat-7.0.23/webapps/root/web-inf/lib/ Portal-impl.jar!/portal.properties
19.Loading file:/d:/liferay/ri/liferay-portal-6.1.0-ce-ga1/portal-setup-wizard.properties
20.Loading file:/d:/liferay/ri/liferay-portal-6.1.0-ce-ga1/portal-ide.properties
21.Loading file:/d:/liferay/ri/liferay-portal-6.1.0-ce-ga1/tomcat-7.0.23/webapps/root/web-inf/classes/ Portal-developer.properties
22.03:09:46,379 INFO [dialectdetector:80] determine dialect for Hsql Database Engine 2
23.03:09:46,379 WARN [dialectdetector:95] Liferay is configured to use hypersonic as its database. Don't use hypersonic in production. Hypersonic is a embedded database useful for development and demo ' ing purposes. The database settings can be changed in portal-ext.properties.
24.03:09:46,426 INFO [dialectdetector:145] Found dialect org.hibernate.dialect.HSQLDialect
25.Starting liferay Portal Community Edition 6.1.0 CE (paton/build 6100/january 6, 2012)
26.03:10:08,994 INFO [basedb:406] Database supports case sensitive queries
27.03:10:09,898 INFO [pluginpackageutil:1096] Reading plugin package for the root
28.03:10:32,825 INFO [autodeploydir:105] Auto deploy scanner started for D:\Liferay\RI\liferay-portal-6.1.0-ce-ga1\ Deploy
29.May 3:10:39 AM org.apache.catalina.startup.HostConfig deploydirectory
30.info:deploying Web application directory D:\Liferay\RI\liferay-portal-6.1.0-ce-ga1\tomcat-7.0.23\webapps\ Chat-portlet
31.Loading file:/d:/liferay/ri/liferay-portal-6.1.0-ce-ga1/tomcat-7.0.23/temp/0-chat-portlet/web-inf/classes/ Service.properties
32.Loading file:/d:/liferay/ri/liferay-portal-6.1.0-ce-ga1/tomcat-7.0.23/temp/0-chat-portlet/web-inf/classes/ Service.properties
33.03:10:47,522 INFO [pluginpackageutil:1099] Reading plugin package for Chat-portlet
34.Loading file:/d:/liferay/ri/liferay-portal-6.1.0-ce-ga1/tomcat-7.0.23/temp/0-chat-portlet/web-inf/classes/ Service.properties
35.Loading file:/d:/liferay/ri/liferay-portal-6.1.0-ce-ga1/tomcat-7.0.23/temp/0-chat-portlet/web-inf/classes/ Portlet.properties
36.Loading file:/d:/liferay/ri/liferay-portal-6.1.0-ce-ga1/tomcat-7.0.23/temp/0-chat-portlet/web-inf/classes/ Portlet.properties
37.03:10:48,660 INFO [hookhotdeploylistener:1901] registering hook for Chat-portlet
38.Loading file:/d:/liferay/ri/liferay-portal-6.1.0-ce-ga1/tomcat-7.0.23/temp/0-chat-portlet/web-inf/classes/ Portal.properties
39.03:10:48,769 INFO [hookhotdeploylistener:978] Hook for Chat-portlet are available for use
40.03:10:48,769 INFO [portlethotdeploylistener:614] registering portlets for Chat-portlet
41.Loading file:/d:/liferay/ri/liferay-portal-6.1.0-ce-ga1/tomcat-7.0.23/temp/0-chat-portlet/web-inf/classes/ Portlet.properties
42.03:10:48,894 INFO [portlethotdeploylistener:433] 1 portlet for Chat-portlet are available for use
43...
44.May 3:12:09 AM org.apache.coyote.AbstractProtocol start
45.info:starting Protocolhandler ["http-bio-8080"]
46.May 3:12:09 AM org.apache.coyote.AbstractProtocol start
47.info:starting Protocolhandler ["ajp-bio-8009"]
48.May 3:12:09 AM Org.apache.catalina.startup.Catalina start
49.info:server Startup in 154806 MS

So we can look at the whole Liferay startup process:

1-12 rows are tomcat-initiated, including initializing the Protocol processor, starting the Catalina container and the servlet container.

13-14 lines start deploying the application because we have defaulthost=localhost in Server.xml:

<!--should set Jvmroute to support load-balancing via AJP ie: <engine name= "Catalina" defaulthost= 
 St "jvmroute=" JVM1 "> 
 --> <engine defaulthost=" localhost "name=" 
 Catalina ">

So it goes to load the root.xml under the%tomcat_home%\conf\catalina\localhost.

Then it goes to read the root application in the WebApps directory, which is the entry into the Liferay framework.

15-21 lines begin to read all the configurations in the root application:

Line 17th Specifies where the configuration can be read, so the 第18-21 rows read the configuration files separately.

22-24 lines use Dialectdetector to probe the database used by Liferay, because the database used and connected is not defined in portal-ext.properties, so use the default hypersonic database

Line 25th begins to officially start the Liferay server, where we are using Community Edition (another Liferay enterprise Edition)

Line 28th begins to enable automatic packet scanning, which scans the D:\Liferay\RI\liferay-portal-6.1.0-ce-ga1\deploy directory, and it should be noted that Liferay has deploy and Direct-deploy two scenarios: