Portlet doesn't deploy

[Adam Coles, modifié il y a 14 années.]

Hi, hope someone can help as I'm tearing my hair out!

My problem is that one of my custom portlets (JSR168 but not build in plugins SDK) won't deploy. I've succesfully deployed other portlets by copying them to the hot deploy directory (we're running on Tomcat) but this one just doesn't work. I've turned on debugging, and tried to debug through Eclipse with no joy. When I try to deploy the first time I get this:

15:59:45,538 INFO  [AutoDeployDir:176] Processing people-directory.war
15:59:45,539 DEBUG [ExtAutoDeployListener:45] Invoking deploy for /data/tcServer
-6.0/deploy-portal-12/people-directory.war
15:59:45,539 DEBUG [HookAutoDeployListener:45] Invoking deploy for /data/tcServe
r-6.0/deploy-portal-12/people-directory.war
15:59:45,539 DEBUG [LayoutTemplateAutoDeployListener:47] Invoking deploy for /da
ta/tcServer-6.0/deploy-portal-12/people-directory.war
15:59:45,539 DEBUG [PortletAutoDeployListener:48] Invoking deploy for /data/tcSe
rver-6.0/deploy-portal-12/people-directory.war
15:59:45,539 INFO  [PortletAutoDeployListener:81] Copying portlets for /data/tcS
erver-6.0/deploy-portal-12/people-directory.war
15:59:45,540 DEBUG [PortletAutoDeployListener:85] Using deployer com.liferay.por
tal.deploy.auto.PortletAutoDeployer
15:59:45,544 WARN  [SAXReaderImpl:439] XSD validation is diasabled because org.a
pache.xerces.parsers.XIncludeAwareParserConfiguration cannot be cast to org.apac
he.xerces.xni.parser.XMLParserConfiguration
  Expanding: /data/tcServer-6.0/deploy-portal-12/people-directory.war into /data
/tcServer-6.0/portal-12/temp/20100420155945547
15:59:45,688 WARN  [SAXReaderImpl:439] XSD validation is diasabled because org.a
pache.xerces.parsers.XIncludeAwareParserConfiguration cannot be cast to org.apac
he.xerces.xni.parser.XMLParserConfiguration
15:59:45,692 WARN  [SAXReaderImpl:439] XSD validation is diasabled because org.a
pache.xerces.parsers.XIncludeAwareParserConfiguration cannot be cast to org.apac
he.xerces.xni.parser.XMLParserConfiguration
15:59:45,698 WARN  [SAXReaderImpl:439] XSD validation is diasabled because org.a
pache.xerces.parsers.XIncludeAwareParserConfiguration cannot be cast to org.apac
he.xerces.xni.parser.XMLParserConfiguration
15:59:45,701 WARN  [SAXReaderImpl:439] XSD validation is diasabled because org.a
pache.xerces.parsers.XIncludeAwareParserConfiguration cannot be cast to org.apac
he.xerces.xni.parser.XMLParserConfiguration
  Copying 1 file to /data/tcServer-6.0/portal-12/temp/20100420155945547/WEB-INF/
classes
  Copying 1 file to /data/tcServer-6.0/portal-12/temp/20100420155945547/META-INF
15:59:45,708 WARN  [SAXReaderImpl:439] XSD validation is diasabled because org.a
pache.xerces.parsers.XIncludeAwareParserConfiguration cannot be cast to org.apac
he.xerces.xni.parser.XMLParserConfiguration
15:59:45,715 WARN  [SAXReaderImpl:439] XSD validation is diasabled because org.a
pache.xerces.parsers.XIncludeAwareParserConfiguration cannot be cast to org.apac
he.xerces.xni.parser.XMLParserConfiguration
15:59:45,717 WARN  [SAXReaderImpl:439] XSD validation is diasabled because org.a
pache.xerces.parsers.XIncludeAwareParserConfiguration cannot be cast to org.apac
he.xerces.xni.parser.XMLParserConfiguration
15:59:45,724 WARN  [SAXReaderImpl:439] XSD validation is diasabled because org.a
pache.xerces.parsers.XIncludeAwareParserConfiguration cannot be cast to org.apac
he.xerces.xni.parser.XMLParserConfiguration
  Copying 5 files to /data/tcServer-6.0/portal-12/webapps/people-directory
  Copying 1 file to /data/tcServer-6.0/portal-12/webapps/people-directory
  Deleting directory /data/tcServer-6.0/portal-12/temp/20100420155945547
15:59:45,766 INFO  [PortletAutoDeployListener:91] Portlets for /data/tcServer-6.
0/deploy-portal-12/people-directory.war copied successfully. Deployment will sta
rt in a few seconds.
15:59:45,767 DEBUG [ThemeAutoDeployListener:46] Invoking deploy for /data/tcServ
er-6.0/deploy-portal-12/people-directory.war
15:59:45,767 DEBUG [WebAutoDeployListener:45] Invoking deploy for /data/tcServer
-6.0/deploy-portal-12/people-directory.war
15:59:45,767 DEBUG [LayoutTemplateExplodedTomcatListener:47] Invoking deploy for
 /data/tcServer-6.0/deploy-portal-12/people-directory.war
15:59:45,767 DEBUG [BaseExplodedTomcatListener:137] /data/tcServer-6.0/deploy-po
rtal-12/people-directory.war does not have a matching extension
15:59:45,768 DEBUG [PortletExplodedTomcatListener:48] Invoking deploy for /data/
tcServer-6.0/deploy-portal-12/people-directory.war
15:59:45,768 DEBUG [BaseExplodedTomcatListener:137] /data/tcServer-6.0/deploy-po
rtal-12/people-directory.war does not have a matching extension
15:59:45,768 DEBUG [BaseExplodedTomcatListener:137] /data/tcServer-6.0/deploy-po
rtal-12/people-directory.war does not have a matching extension
15:59:45,768 DEBUG [ThemeExplodedTomcatListener:45] Invoking deploy for /data/tc
Server-6.0/deploy-portal-12/people-directory.war
15:59:45,768 DEBUG [BaseExplodedTomcatListener:137] /data/tcServer-6.0/deploy-po
rtal-12/people-directory.war does not have a matching extension

..and I find the directory (people-directory) has been expanded in the webapps folder but the portlet never gets registered.

If I then restart the container I get this in the logs:

16:20:12,967 DEBUG [PluginPackageHotDeployListener:198] Invoking deploy for peop
le-directory
16:20:12,967 INFO  [PluginPackageHotDeployListener:75] Reading plugin package fo
r people-directory
16:20:12,968 DEBUG [PluginPackageHotDeployListener:81] Reading plugin package fr
om MANIFEST.MF
16:20:12,968 WARN  [PluginPackageHotDeployListener:125] Plugin package on contex
t people-directory cannot be tracked because this WAR does not contain a liferay
-plugin-package.xml file
16:20:12,971 DEBUG [PluginPackageHotDeployListener:275] Unable to read service.p
roperties
16:20:13,243 INFO  [PluginPackageHotDeployListener:226] Plugin package people-di
rectory/people-directory/unknown/war registered successfully. It's now ready to
be used.
16:20:13,244 DEBUG [ExtHotDeployListener:135] Invoking deploy for people-directo
ry
16:20:13,244 DEBUG [HookHotDeployListener:257] Invoking deploy for people-direct
ory
16:20:13,245 DEBUG [LayoutTemplateHotDeployListener:77] Invoking deploy for peop
le-directory
16:20:13,245 DEBUG [PortletHotDeployListener:206] Invoking deploy for people-dir
ectory
16:20:13,245 INFO  [PortletHotDeployListener:230] Registering portlets for peopl
e-directory
16:20:13,249 WARN  [SAXReaderImpl:439] XSD validation is diasabled because org.a
pache.xerces.parsers.XIncludeAwareParserConfiguration cannot be cast to org.apac
he.xerces.xni.parser.XMLParserConfiguration
16:20:13,261 WARN  [SAXReaderImpl:439] XSD validation is diasabled because org.a
pache.xerces.parsers.XIncludeAwareParserConfiguration cannot be cast to org.apac
he.xerces.xni.parser.XMLParserConfiguration
16:20:13,271 WARN  [SAXReaderImpl:439] XSD validation is diasabled because org.a
pache.xerces.parsers.XIncludeAwareParserConfiguration cannot be cast to org.apac
he.xerces.xni.parser.XMLParserConfiguration
16:20:13,285 WARN  [SAXReaderImpl:439] XSD validation is diasabled because org.a
pache.xerces.parsers.XIncludeAwareParserConfiguration cannot be cast to org.apac
he.xerces.xni.parser.XMLParserConfiguration
16:20:13,291 DEBUG [PortletHotDeployListener:783] Unable to read portlet.propert
ies
16:20:13,292 INFO  [PortletHotDeployListener:349] 1 portlet for people-directory
 is available for use
16:20:13,292 DEBUG [ThemeHotDeployListener:77] Invoking deploy for people-direct
ory
16:20:13,292 DEBUG [ThemeLoaderHotDeployListener:70] Invoking deploy for people-
directory
16:20:13,305 DEBUG [PluginPackageHotDeployListener:238] Invoking deploy for peop
le-directory
16:20:13,305 INFO  [PluginPackageHotDeployListener:75] Reading plugin package fo
r people-directory
16:20:13,306 DEBUG [PluginPackageHotDeployListener:81] Reading plugin package fr
om MANIFEST.MF
16:20:13,306 WARN  [PluginPackageHotDeployListener:125] Plugin package on contex
t people-directory cannot be tracked because this WAR does not contain a liferay
-plugin-package.xml file
16:20:13,458 WARN  [PluginPackageUtil:1303] Unable to reindex unistalled package
 people-directory: Unable to communicate with repository http://plugins.liferay.
com/enterprise
16:20:13,462 INFO  [PluginPackageHotDeployListener:256] Plugin package people-di
rectory/people-directory/unknown/war unregistered successfully
16:20:13,463 DEBUG [ExtHotDeployListener:210] Invoking undeploy for people-direc
tory
16:20:13,463 INFO  [ExtHotDeployListener:214] Extension environment for people-d
irectory will not be undeployed
16:20:13,463 DEBUG [HookHotDeployListener:515] Invoking undeploy for people-dire
ctory
16:20:13,464 DEBUG [LayoutTemplateHotDeployListener:120] Invoking undeploy for p
eople-directory
16:20:13,464 DEBUG [PortletHotDeployListener:367] Invoking undeploy for people-d
irectory
16:20:13,464 INFO  [PortletHotDeployListener:384] Unregistering portlets for peo
ple-directory
16:20:13,473 INFO  [PortletHotDeployListener:415] 1 portlet for people-directory
 was unregistered
16:20:13,473 DEBUG [ThemeHotDeployListener:132] Invoking undeploy for people-dir
ectory
16:20:13,474 DEBUG [ThemeLoaderHotDeployListener:95] Invoking undeploy for peopl
e-directory

..so it seems like it deploys, then undeploys again for no good reason. Does anyone have any ideas?

[Babu Janarthanan, modifié il y a 14 années.]

Hi Adam,
i guess, you might missed some thing in configuration level. please check your configuration files and redeploy it.

hope it solves your problem.

Thx,
Babu

[Adam Coles, modifié il y a 14 années.]

Babu Janarthanan:

Hi Adam,
i guess, you might missed some thing in configuration level. please check your configuration files and redeploy it.

hope it solves your problem.

Thx,
Babu

I've had this portlet successfully deploy on the bundle running on my own machine, but not in our development cluster. The point is there doesn't seem to be any reason recorded anywhere as to why it's failing.

[Adam Coles, modifié il y a 14 années.]

It would appear that my Tomcat installation was hiding the real error, which was a log4j listener start failure - still don't know why but removing it allowed deployment. Thanks for looking.