deploy process hangs

[garima bhandari, modificado 11 Anos atrás.]

I am deploying the portlet on local and deploy process hangs here:

10:25:48,716 INFO  [com.liferay.portal.kernel.deploy.auto.AutoDeployScanner][AutoDeployDir:177] Processing InvestorSignUp-portlet-6.1.1.1.war
10:25:48,717 INFO  [com.liferay.portal.kernel.deploy.auto.AutoDeployScanner][PortletAutoDeployListener:77] Copying portlets for F:\INVESTED\liferay-portal\deploy\InvestorSignUp-portlet-6.1.1.1.war
10:25:48,718 INFO  [com.liferay.portal.kernel.deploy.auto.AutoDeployScanner][BaseDeployer:763] Deploying InvestorSignUp-portlet-6.1.1.1.war
10:25:48,748 INFO  [com.liferay.portal.kernel.deploy.auto.AutoDeployScanner][BaseDeployer:859] Updating InvestorSignUp from version 6.1.1.1 to version 6.1.1.1
  Expanding: F:\INVESTED\liferay-portal\deploy\InvestorSignUp-portlet-6.1.1.1.war into F:\INVESTED\liferay-portal\tomcat\temp\20130308102548748
  Copying 1 file to F:\INVESTED\liferay-portal\tomcat\temp\20130308102548748\WEB-INF
  Copying 1 file to F:\INVESTED\liferay-portal\tomcat\temp\20130308102548748\WEB-INF\classes
  Copying 1 file to F:\INVESTED\liferay-portal\tomcat\temp\20130308102548748\WEB-INF\classes
  Copying 1 file to F:\INVESTED\liferay-portal\tomcat\temp\20130308102548748\WEB-INF\jsp
10:25:49,028 INFO  [com.liferay.portal.kernel.deploy.auto.AutoDeployScanner][BaseDeployer:2083] Modifying Servlet 2.4 F:\INVESTED\liferay-portal\tomcat\temp\20130308102548748\WEB-INF\web.xml
  Copying 206 files to F:\INVESTED\liferay-portal\tomcat\webapps\InvestorSignUp-portlet
  Copying 1 file to F:\INVESTED\liferay-portal\tomcat\webapps\InvestorSignUp-portlet
  Deleting directory F:\INVESTED\liferay-portal\tomcat\temp\20130308102548748
10:25:49,574 INFO  [com.liferay.portal.kernel.deploy.auto.AutoDeployScanner][PortletAutoDeployListener:87] Portlets for F:\INVESTED\liferay-portal\deploy\InvestorSignUp-portlet-6.1.1.1.war copied successfully. Deployment will start in a few seconds.
8 Mar, 2013 10:25:51 AM org.apache.catalina.startup.HostConfig checkResources
INFO: Undeploying context [/InvestorSignUp-portlet]
10:25:51,604 INFO  [ContainerBackgroundProcessor[StandardEngine[Catalina]]][PluginPackageUtil:1033] Reading plugin package for InvestorSignUp-portlet
8 Mar, 2013 10:25:51 AM org.apache.catalina.core.ApplicationContext log
INFO: Closing Spring root WebApplicationContext
8 Mar, 2013 10:25:52 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory F:\INVESTED\liferay-portal\tomcat\webapps\InvestorSignUp-portlet
10:25:52,505 INFO  [pool-2-thread-5][HotDeployImpl:178] Deploying InvestorSignUp-portlet from queue
10:25:52,505 INFO  [pool-2-thread-5][PluginPackageUtil:1033] Reading plugin package for InvestorSignUp-portlet
Loading file:/F:/INVESTED/liferay-portal/tomcat/temp/7-InvestorSignUp-portlet/WEB-INF/classes/portlet.properties
Loading file:/F:/INVESTED/liferay-portal/tomcat/temp/7-InvestorSignUp-portlet/WEB-INF/classes/service.properties
Loading file:/F:/INVESTED/liferay-portal/tomcat/temp/7-InvestorSignUp-portlet/WEB-INF/classes/portlet.properties
Loading file:/F:/INVESTED/liferay-portal/tomcat/temp/7-InvestorSignUp-portlet/WEB-INF/classes/service.properties
8 Mar, 2013 10:25:52 AM org.apache.catalina.core.ApplicationContext log
INFO: Initializing Spring root WebApplicationContext
Loading file:/F:/INVESTED/liferay-portal/tomcat/temp/7-InvestorSignUp-portlet/WEB-INF/classes/service.properties
Loading file:/F:/INVESTED/liferay-portal/tomcat/temp/7-InvestorSignUp-portlet/WEB-INF/classes/portlet.properties

Portlet is working properly and even not giving any error but still not showing 1 portlet is available for use
And when I am deploying the war on production... deploy process hangs on same place and not able to drag the portlet on page.


I am using liferay-6.1.1-ce-ga2.
Please help...

[Dipanjan Das, modificado 11 Anos atrás.]

You could increase the max perm-size in startup.bat of tomcat to resolve this issue.

[Jitendra Rajput, modificado 11 Anos atrás.]

Basically the log level for deployer located in com.liferay.portal.deploy.hot package are default set to ERROR level. To get your successful deployment message just modify the log level the com.liferay.portal.deploy.hot.*HotDeployListener loggers.


Above changes will be lost if you restart your server so if you want permanent solution then override portal-log4j.xml in your ext - plugin and change below entries.
Set log level to info instead of error.

<category name="com.liferay.portal.deploy.hot.PortletHotDeployListener">
        <priority value="INFO" />
  </category>

[Hitoshi Ozawa, modificado 11 Anos atrás.]

Is this a custom portlet or a portlet from liferay's Marketplace?

[garima bhandari, modificado 11 Anos atrás.]

Hitoshi Ozawa:

Is this a custom portlet or a portlet from liferay's Marketplace?

It 's a custom portlet.

[Hitoshi Ozawa, modificado 11 Anos atrás.]

If your custom portlet is hanging, it only means you have a bug in your custom portlet. I don't think anyone can say what's wrong with your portlet because we don't know your portlet.

[garima bhandari, modificado 11 Anos atrás.]

Hitoshi Ozawa:

If your custom portlet is hanging, it only means you have a bug in your custom portlet. I don't think anyone can say what's wrong with your portlet because we don't know your portlet.

Actually this is not happening only with one portlet but with all custom portlets.

[Jitendra Rajput, modificado 11 Anos atrás.]

Did you tried by changing log levels from control panel ?

[dave ch, modificado 11 Anos atrás.]

Is this a custom portlet or a portlet from liferay's Marketplace?

I am customizing liferay's Marketplace portlets and getting the same result after deploy, i.e, not getting "portlet is available for use ".
But the portlet is getting deployed and working fine and not giving any error.
What would be the possible reason for this?

Dave

[dave ch, modificado 11 Anos atrás.]

Did you tried by changing log levels from control panel ?

Changing log levels solves my issue.

Thanks.

[Jitendra Rajput, modificado 11 Anos atrás.]

Make sure you modify the same in portal-log4j-ext.xml also other wise log setting will be lost next time when you restart your server.

[garima bhandari, modificado 11 Anos atrás.]

Jitendra Rajput:

Make sure you modify the same in portal-log4j-ext.xml also other wise log setting will be lost next time when you restart your server.

Thanks Jitendra,

Changing log levels solves the issue .Sorry for replying late :-)