RE: Server Liferay v6.2 EE Server (Tomcat 7) at localhost failed to start.

Ragupathi Subramaniyan, modified 10 Years ago. New Member Posts: 2 Join Date: 5/12/15 Recent Posts
Hi experts,
I'm a new guy for this technology, just now I tried to install Liferay Developer studio and created the sample. After creating sample I try to start the server but not able to start it. It it throwing message like 'Server Liferay v6.2 EE Server (Tomcat 7) at localhost failed to start.'.

In log it is showing like
May 18, 2015 4:53:10 AM org.apache.catalina.core.AprLifecycleListener init
INFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\Program Files\Java\jdk1.7.0_55\jre\bin;C:\windows\Sun\Java\bin;C:\windows\system32;C:\windows;C:/Program Files/Java/jre1.8.0_40/bin/server;C:/Program Files/Java/jre1.8.0_40/bin;C:/Program Files/Java/jre1.8.0_40/lib/amd64;C:\ProgramData\Oracle\Java\javapath;C:\oraclexe\app\oracle\product\10.2.0\server\bin;C:\Program Files\RA2HP\;C:\windows\system32;C:\windows;C:\windows\System32\Wbem;C:\windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\ActivIdentity\ActivClient\;C:\Program Files (x86)\ActivIdentity\ActivClient\;C:\Program Files\TortoiseSVN\bin;C:\Program Files\Java\jdk1.7.0_55\jre\bin;C:\Liferay\apache-ant-1.9.4\bin;;C:\Liferay Studio\liferay-developer-studio\DeveloperStudio;;.
May 18, 2015 4:53:10 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-8080"]
May 18, 2015 4:53:10 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["ajp-bio-8009"]
May 18, 2015 4:53:10 AM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 670 ms
May 18, 2015 4:53:10 AM org.apache.catalina.core.StandardService startInternal
INFO: Starting service Catalina
May 18, 2015 4:53:10 AM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.42
May 18, 2015 4:53:10 AM org.apache.catalina.startup.HostConfig deployDescriptor
INFO: Deploying configuration descriptor C:\Liferay Studio\liferay-developer-studio\liferay-portal-6.2-ee-sp11\tomcat-7.0.42\conf\Catalina\localhost\ROOT.xml
Loading jar:file:/C:/Liferay%20Studio/liferay-developer-studio/liferay-portal-6.2-ee-sp11/tomcat-7.0.42/webapps/ROOT/WEB-INF/lib/portal-impl.jar!/system.properties
Loading jar:file:/C:/Liferay%20Studio/liferay-developer-studio/liferay-portal-6.2-ee-sp11/tomcat-7.0.42/webapps/ROOT/WEB-INF/lib/portal-impl.jar!/portal.properties
Loading jar:file:/C:/Liferay%20Studio/liferay-developer-studio/liferay-portal-6.2-ee-sp11/tomcat-7.0.42/webapps/ROOT/WEB-INF/lib/portal-impl.jar!/portal-patched.properties
Loading file:/C:/Liferay%20Studio/liferay-developer-studio/liferay-portal-6.2-ee-sp11/portal-ext.properties
Loading file:/C:/Liferay%20Studio/liferay-developer-studio/liferay-portal-6.2-ee-sp11/portal-ide.properties
Loading jar:file:/C:/Liferay%20Studio/liferay-developer-studio/liferay-portal-6.2-ee-sp11/tomcat-7.0.42/webapps/ROOT/WEB-INF/lib/portal-impl.jar!/system.properties
May 18, 2015 4:53:24 AM org.apache.catalina.core.ApplicationContext log
INFO: Initializing Spring root WebApplicationContext
04:53:29,898 INFO [localhost-startStop-1][DialectDetector:71] Determine dialect for Oracle 10
04:53:29,929 INFO [localhost-startStop-1][DialectDetector:136] Found dialect org.hibernate.dialect.Oracle10gDialect
Starting Liferay Portal Enterprise Edition 6.2.10 EE GA1 (Newton / Build 6210 / November 1, 2013)
04:53:57,006 INFO [localhost-startStop-1][StartupAction:99] The following patches are installed: portal-45-6210
04:53:57,694 INFO [localhost-startStop-1][BaseDB:481] Database supports case sensitive queries
04:53:57,881 INFO [localhost-startStop-1][StartupHelper:128] Upgrading from 6203 to 6210 is not supported
thumbnail
Ramalingaiah Dudidmetle, modified 10 Years ago. Expert Posts: 489 Join Date: 8/16/14 Recent Posts
Hi RAGUPATHI SUBRAMANIYAN,


eclipse-->windows--->references--->tomcat path and sdk path give it will work,

It will work,
Regards,
Ram,
Ragupathi Subramaniyan, modified 10 Years ago. New Member Posts: 2 Join Date: 5/12/15 Recent Posts
Hi Ramalingaiah Dudidmetle,

Thanks for your quick reply, I added both the entry(SDK ad tomcat), eventhough I'm getting this problem.

Regards,
Ragupathi
thumbnail
Ramalingaiah Dudidmetle, modified 10 Years ago. Expert Posts: 489 Join Date: 8/16/14 Recent Posts
Hi

file name portal-ext give

jdbc.default.driverClassName=org.postgresql.Driver
jdbc.default.username=postgres
jdbc.default.password=postgres
jdbc.default.url=jdbc:postgresql://localhost:5432/ebs?useUnicode=true&characterEncoding=UTF-8&useFastDateParsing=false

you can add jar files ,
which DB using , that jar files add,
jdbc connection in files tomcat folder inside past,,

Regards ,
Ram
shiv darshan, modified 7 Years ago. New Member Posts: 10 Join Date: 10/5/17 Recent Posts
This exception will come due to Tomcat admin port number and apj port number might be same . onces verify your port number if both are same then change the port number.
thumbnail
Juan Gonzalez, modified 10 Years ago. Liferay Legend Posts: 3089 Join Date: 10/28/08 Recent Posts
Issue seems here:
Ragupathi Subramaniyan:

04:53:57,881 INFO [localhost-startStop-1][StartupHelper:128] Upgrading from 6203 to 6210 is not supported


Can you try adding this to your portal-ext.properties and restart?

upgrade.processes.6203=${upgrade.processes.master}


Thanks.
pradip choudhari, modified 6 Years ago. Junior Member Posts: 59 Join Date: 5/10/19 Recent Posts
open task manager -->remove Java task -->restart the server
becoz u r tomcat running internally on those task