Error message

[judgementday judgementday, modificado 10 Anos atrás.]

Hi,

I am receiving this error message when I deploy. Can anyone please tell whats wrong and how do I fix it ?


11:56:48,344 INFO [com.liferay.portal.kernel.deploy.auto.AutoDeployScanner][AutoDeployDir:177] Processing TestProject-portlet.xml
11:56:48,366 INFO [com.liferay.portal.kernel.deploy.auto.AutoDeployScanner][PortletExplodedTomcatListener:60] Modifying portlets for C:\liferay\liferay-portal-tomcat-6.1.1-ce-ga2\liferay-portal-6.1.1-ce-ga2\deploy\TestProject-portlet.xml
Copying 1 file to C:\liferay\liferay-portal-tomcat-6.1.1-ce-ga2\liferay-portal-6.1.1-ce-ga2\tomcat-7.0.27\webapps\TestProject-portlet\WEB-INF\classes
Copying 1 file to C:\liferay\liferay-portal-tomcat-6.1.1-ce-ga2\liferay-portal-6.1.1-ce-ga2\tomcat-7.0.27\webapps\TestProject-portlet\WEB-INF\classes
Copying 1 file to C:\liferay\liferay-portal-tomcat-6.1.1-ce-ga2\liferay-portal-6.1.1-ce-ga2\tomcat-7.0.27\webapps\TestProject-portlet\WEB-INF\jsp
11:56:49,995 INFO [com.liferay.portal.kernel.deploy.auto.AutoDeployScanner][BaseDeployer:2083] Modifying Servlet 2.4 C:\liferay\liferay-portal-tomcat-6.1.1-ce-ga2\liferay-portal-6.1.1-ce-ga2\tomcat-7.0.27\webapps\TestProject-portlet\WEB-INF\web.xml
11:56:49,997 INFO [com.liferay.portal.kernel.deploy.auto.AutoDeployScanner][PortletExplodedTomcatListener:66] Portlets for C:\liferay\liferay-portal-tomcat-6.1.1-ce-ga2\liferay-portal-6.1.1-ce-ga2\deploy\TestProject-portlet.xml modified successfully
11:56:49,998 INFO [com.liferay.portal.kernel.deploy.auto.AutoDeployScanner][BaseExplodedTomcatListener:49] Copying file C:\liferay\liferay-portal-tomcat-6.1.1-ce-ga2\liferay-portal-6.1.1-ce-ga2\deploy\TestProject-portlet.xml to C:\liferay\liferay-portal-tomcat-6.1.1-ce-ga2\liferay-portal-6.1.1-ce-ga2\tomcat-7.0.27\conf\Catalina\localhost
Jun 7, 2013 11:56:56 AM org.apache.catalina.startup.HostConfig deployDescriptor
INFO: Deploying configuration descriptor C:\liferay\liferay-portal-tomcat-6.1.1-ce-ga2\liferay-portal-6.1.1-ce-ga2\tomcat-7.0.27\conf\Catalina\localhost\TestProject-portlet.xml
Jun 7, 2013 11:56:56 AM org.apache.catalina.startup.HostConfig deployDescriptor
WARNING: A docBase C:\liferay\liferay-portal-tomcat-6.1.1-ce-ga2\liferay-portal-6.1.1-ce-ga2\tomcat-7.0.27\webapps\TestProject-portlet inside the host appBase has been specified, and will be ignored
Jun 7, 2013 11:56:56 AM org.apache.catalina.startup.SetContextPropertiesRule begin
WARNING: [SetContextPropertiesRule]{Context} Setting property 'source' to 'org.eclipse.jst.jee.server:TestProject-portlet' did not find a matching property.
11:56:57,142 INFO [pool-2-thread-2][HotDeployImpl:178] Deploying TestProject-portlet from queue
11:56:57,144 INFO [pool-2-thread-2][PluginPackageUtil:1033] Reading plugin package for TestProject-portlet
Jun 7, 2013 11:56:57 AM org.apache.catalina.core.ApplicationContext log
INFO: Initializing Spring root WebApplicationContext
11:57:18,572 ERROR [pool-2-thread-2][PortletLocalServiceImpl:758] com.liferay.portal.kernel.xml.DocumentException: Connection timed out: connect Nested exception: Connection timed out: connect
com.liferay.portal.kernel.xml.DocumentException: Connection timed out: connect Nested exception: Connection timed out: connect
at com.liferay.portal.xml.SAXReaderImpl.read(SAXReaderImpl.java:399)
at com.liferay.portal.xml.SAXReaderImpl.read(SAXReaderImpl.java:415)
at com.liferay.portal.kernel.xml.SAXReaderUtil.read(SAXReaderUtil.java:161)
at com.liferay.portal.service.impl.PortletLocalServiceImpl._readLiferayPortletXML(PortletLocalServiceImpl.java:1602)
at com.liferay.portal.service.impl.PortletLocalServiceImpl.initWAR(PortletLocalServiceImpl.java:711)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:122)
at com.liferay.portal.spring.aop.ServiceBeanAopProxy.invoke(ServiceBeanAopProxy.java:211)
at $Proxy65.initWAR(Unknown Source)
at com.liferay.portal.service.PortletLocalServiceUtil.initWAR(PortletLocalServiceUtil.java:409)
at com.liferay.portal.deploy.hot.PortletHotDeployListener.doInvokeDeploy(PortletHotDeployListener.java:297)
at com.liferay.portal.deploy.hot.PortletHotDeployListener.invokeDeploy(PortletHotDeployListener.java:120)
at com.liferay.portal.deploy.hot.HotDeployImpl.doFireDeployEvent(HotDeployImpl.java:188)
at com.liferay.portal.deploy.hot.HotDeployImpl.fireDeployEvent(HotDeployImpl.java:96)
at com.liferay.portal.kernel.deploy.hot.HotDeployUtil.fireDeployEvent(HotDeployUtil.java:27)
at com.liferay.portal.kernel.servlet.PluginContextListener.fireDeployEvent(PluginContextListener.java:151)
at com.liferay.portal.kernel.servlet.PluginContextListener.doPortalInit(PluginContextListener.java:141)
at com.liferay.portal.kernel.util.BasePortalLifecycle.portalInit(BasePortalLifecycle.java:42)
at com.liferay.portal.kernel.util.PortalLifecycleUtil.register(PortalLifecycleUtil.java:64)
at com.liferay.portal.kernel.util.PortalLifecycleUtil.register(PortalLifecycleUtil.java:56)
at com.liferay.portal.kernel.util.BasePortalLifecycle.registerPortalLifecycle(BasePortalLifecycle.java:52)
at com.liferay.portal.kernel.servlet.PluginContextListener.contextInitialized(PluginContextListener.java:103)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4779)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5273)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:895)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:871)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:615)
at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:649)
at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1585)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
Caused by: org.dom4j.DocumentException: Connection timed out: connect Nested exception: Connection timed out: connect
at org.dom4j.io.SAXReader.read(SAXReader.java:484)
at org.dom4j.io.SAXReader.read(SAXReader.java:365)
at com.liferay.portal.xml.SAXReaderImpl.read(SAXReaderImpl.java:396)
... 38 more
11:57:39,612 ERROR [pool-2-thread-2][HotDeployImpl:191] com.liferay.portal.kernel.deploy.hot.HotDeployException: Error registering portlets for TestProject-portlet
com.liferay.portal.kernel.deploy.hot.HotDeployException: Error registering portlets for TestProject-portlet
at com.liferay.portal.kernel.deploy.hot.BaseHotDeployListener.throwHotDeployException(BaseHotDeployListener.java:46)
at com.liferay.portal.deploy.hot.PortletHotDeployListener.invokeDeploy(PortletHotDeployListener.java:123)
at com.liferay.portal.deploy.hot.HotDeployImpl.doFireDeployEvent(HotDeployImpl.java:188)
at com.liferay.portal.deploy.hot.HotDeployImpl.fireDeployEvent(HotDeployImpl.java:96)
at com.liferay.portal.kernel.deploy.hot.HotDeployUtil.fireDeployEvent(HotDeployUtil.java:27)
at com.liferay.portal.kernel.servlet.PluginContextListener.fireDeployEvent(PluginContextListener.java:151)
at com.liferay.portal.kernel.servlet.PluginContextListener.doPortalInit(PluginContextListener.java:141)
at com.liferay.portal.kernel.util.BasePortalLifecycle.portalInit(BasePortalLifecycle.java:42)
at com.liferay.portal.kernel.util.PortalLifecycleUtil.register(PortalLifecycleUtil.java:64)
at com.liferay.portal.kernel.util.PortalLifecycleUtil.register(PortalLifecycleUtil.java:56)
at com.liferay.portal.kernel.util.BasePortalLifecycle.registerPortalLifecycle(BasePortalLifecycle.java:52)
at com.liferay.portal.kernel.servlet.PluginContextListener.contextInitialized(PluginContextListener.java:103)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4779)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5273)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:895)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:871)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:615)
at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:649)
at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1585)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
Caused by: com.liferay.portal.kernel.exception.SystemException: com.liferay.portal.kernel.xml.DocumentException: Connection timed out: connect Nested exception: Connection timed out: connect
at com.liferay.portal.service.impl.PortletLocalServiceImpl.getWARDisplay(PortletLocalServiceImpl.java:568)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:122)
at com.liferay.portal.spring.aop.ServiceBeanAopProxy.invoke(ServiceBeanAopProxy.java:211)
at $Proxy65.getWARDisplay(Unknown Source)
at com.liferay.portal.service.PortletLocalServiceUtil.getWARDisplay(PortletLocalServiceUtil.java:390)
at com.liferay.portal.deploy.hot.PortletHotDeployListener.doInvokeDeploy(PortletHotDeployListener.java:375)
at com.liferay.portal.deploy.hot.PortletHotDeployListener.invokeDeploy(PortletHotDeployListener.java:120)
... 24 more
Caused by: com.liferay.portal.kernel.xml.DocumentException: Connection timed out: connect Nested exception: Connection timed out: connect
at com.liferay.portal.xml.SAXReaderImpl.read(SAXReaderImpl.java:399)
at com.liferay.portal.xml.SAXReaderImpl.read(SAXReaderImpl.java:415)
at com.liferay.portal.kernel.xml.SAXReaderUtil.read(SAXReaderUtil.java:161)
at com.liferay.portal.service.impl.PortletLocalServiceImpl._readLiferayDisplayXML(PortletLocalServiceImpl.java:1047)
at com.liferay.portal.service.impl.PortletLocalServiceImpl.getWARDisplay(PortletLocalServiceImpl.java:565)
... 34 more
Caused by: org.dom4j.DocumentException: Connection timed out: connect Nested exception: Connection timed out: connect
at org.dom4j.io.SAXReader.read(SAXReader.java:484)
at org.dom4j.io.SAXReader.read(SAXReader.java:365)
at com.liferay.portal.xml.SAXReaderImpl.read(SAXReaderImpl.java:396)
... 38 more

[Jeffrey Handa, modificado 10 Anos atrás.]

Whenever I see SAX related error messages I first check to make sure all of my XML files are correct.

[judgementday judgementday, modificado 10 Anos atrás.]

Jeffrey Handa:

Whenever I see SAX related error messages I first check to make sure all of my XML files are correct.

those are correct.

Do you have any other suggestion ?

[James Falkner, modificado 10 Anos atrás.]

judgementday judgementday:

Hi,

I am receiving this error message when I deploy. Can anyone please tell whats wrong and how do I fix it ?



...
Caused by: org.dom4j.DocumentException: Connection timed out: connect Nested exception: Connection timed out: connect
at org.dom4j.io.SAXReader.read(SAXReader.java:484)
at org.dom4j.io.SAXReader.read(SAXReader.java:365)
at com.liferay.portal.xml.SAXReaderImpl.read(SAXReaderImpl.java:396)
... 38 more

Network timeout reading an XML? It's probably trying to download a dtd or xsd and validate the portlet.xml file. Try setting portlet.xml.validate=false in your portal-ext.properties?

[judgementday judgementday, modificado 10 Anos atrás.]

Network timeout reading an XML? It's probably trying to download a dtd or xsd and validate the portlet.xml file. Try setting portlet.xml.validate=false in your portal-ext.properties?

I don't have this file in my project.

what to do ?

[chirag @ India, modificado 10 Anos atrás.]

hi udgementday ,

You have to create portal-ext.properties file at path "liferay-portal-6.1.1\tomcat-7.0.35\webapps\ROOT\WEB-INF\classes" in liferay bundle .

This is very important file in liferay You must understand....

HTH
Chirag@India

[James Falkner, modificado 10 Anos atrás.]

chirag @ India:

hi udgementday ,

You have to create portal-ext.properties file at path "liferay-portal-6.1.1\tomcat-7.0.35\webapps\ROOT\WEB-INF\classes" in liferay bundle .

This is very important file in liferay You must understand....

HTH
Chirag@India

Yep, this is correct, although the preferred location for the portal-ext.properties file (as of 6.x) is the "Liferay Home" directory - that way, the file isn't wiped out on subsequent re-deploys.

[judgementday judgementday, modificado 10 Anos atrás.]

James Falkner:

Yep, this is correct, although the preferred location for the portal-ext.properties file (as of 6.x) is the "Liferay Home" directory - that way, the file isn't wiped out on subsequent re-deploys.

I did not understand location of Liferay Home directory ? where it is ?

also where do I get a sample portal-ext.properties file to use ? Can you please paste a sample file here ?

I am using latest Liferay 6.1

[Muradali Hasan, modificado 10 Anos atrás.]

Hi Judgementday,

Liferay home directory is the Root folder where all the files related to your liferay remains.

ex. if you extract the liferay bundled check liferay-portal-6.1.20-ee-ga2 is the root directory inside this directory you will find the other folders like tomcat,data,logs,etc.

And for portal-ext.properties you can just simply create txt file and rename it to "portal-ext.properties" parallel to tomcat,data,logs folders.

and write all the properties inside this file you want to overide.

e.g. may be by default liferay has portlet.xml.validate=true
now you can override this property to portlet.xml.validate=false by writing this property in portal-ext.properties

so when you restart your server it will override all liferay default from portal-ext.properties file.


Thanks-
Muradali

[shifre xue, modificado 10 Anos atrás.]

hi,
so,you have finished?can you tell me this way?i also happened this exception.thank you!