Vista Combinata Vista Piatta Vista ad Albero
Discussioni [ Precedente | Successivo ]
toggle
Thomas Berg
Portlet blacklisted
8 agosto 2010 8.45
Risposta

Thomas Berg

Punteggio: Regular Member

Messaggi: 131

Data di Iscrizione: 7 settembre 2009

Messaggi recenti

Today I saw something that I haven't seen before,

Using Liferay 6.0.4, I tried to deploy a portlet and the Autodeployer went nuts...
Within a very short time period (see times below), the portal had made 10 tries and blacklisted my portlet.

Below is an excerpt from my Tomcat log (the actual portlet name has been changed):

115:28:25,984 INFO  [AutoDeployDir:167] Processing my-portlet.war
215:28:25,984 ERROR [AutoDeployDir:197] com.liferay.portal.kernel.deploy.auto.AutoDeployException: java.util.zip.ZipException: error in opening zip file
3.
4.
5.
615:28:30,062 INFO  [AutoDeployDir:172] Processing my-portlet.war. This is attempt 9.
715:28:30,062 INFO  [AutoDeployDir:203] Add my-portlet.war to the blacklist


Apart from this bug (?), where's the blacklist and how do you edit it?

/ Thomas
Amos Fong
RE: Portlet blacklisted
8 agosto 2010 22.22
Risposta

Amos Fong

LIFERAY STAFF

Punteggio: Liferay Legend

Messaggi: 1844

Data di Iscrizione: 7 ottobre 2008

Messaggi recenti

Hi Thomas,

The blacklist is stored in memory and you can't edit it. You have to restart the server to reset it.
Erik Forsström
RE: Portlet blacklisted
7 aprile 2011 23.00
Risposta

Erik Forsström

Punteggio: Junior Member

Messaggi: 59

Data di Iscrizione: 25 marzo 2010

Messaggi recenti

There really is no other way here?

I had to restart a production server because of this little feature. Won't make the same mistake again :-). Perhaps there should be a feature for it.
Amos Fong
RE: Portlet blacklisted
7 aprile 2011 23.07
Risposta

Amos Fong

LIFERAY STAFF

Punteggio: Liferay Legend

Messaggi: 1844

Data di Iscrizione: 7 ottobre 2008

Messaggi recenti

Sounds good to me =)

http://issues.liferay.com
Michal Sima
RE: Portlet blacklisted
27 febbraio 2013 3.07
Risposta

Michal Sima

Punteggio: New Member

Messaggi: 15

Data di Iscrizione: 27 febbraio 2013

Messaggi recenti

This thread is pretty old, but I am pretty stucked with a blacklist addition while trying to deploy MSTRPortlet.

 1
 210:48:16,186 ERROR [com.liferay.portal.kernel.deploy.auto.AutoDeployScanner][AutoDeployDir:210] com.liferay.portal.kernel.deploy.auto.AutoDeployException: com.liferay.portal.kernel.deploy.auto.AutoDeployException: web.xml must be updated to the Servlet 2.4 specification
 3com.liferay.portal.kernel.deploy.auto.AutoDeployException: com.liferay.portal.kernel.deploy.auto.AutoDeployException: web.xml must be updated to the Servlet 2.4 specification
 4    at com.liferay.portal.tools.deploy.BaseDeployer.autoDeploy(BaseDeployer.java:201)
 5    at com.liferay.portal.deploy.auto.PortletAutoDeployListener.deploy(PortletAutoDeployListener.java:84)
 6    at com.liferay.portal.kernel.deploy.auto.AutoDeployDir.processFile(AutoDeployDir.java:193)
 7    at com.liferay.portal.kernel.deploy.auto.AutoDeployDir.scanDirectory(AutoDeployDir.java:235)
 8    at com.liferay.portal.kernel.deploy.auto.AutoDeployScanner.run(AutoDeployScanner.java:54)
 9Caused by: com.liferay.portal.kernel.deploy.auto.AutoDeployException: web.xml must be updated to the Servlet 2.4 specification
10    at com.liferay.portal.tools.deploy.BaseDeployer.updateWebXml(BaseDeployer.java:2020)
11    at com.liferay.portal.tools.deploy.BaseDeployer.deployDirectory(BaseDeployer.java:576)
12    at com.liferay.portal.tools.deploy.BaseDeployer.deployFile(BaseDeployer.java:957)
13    at com.liferay.portal.tools.deploy.BaseDeployer.deployFile(BaseDeployer.java:889)
14    at com.liferay.portal.tools.deploy.BaseDeployer.autoDeploy(BaseDeployer.java:198)
15    ... 4 more
1610:48:16,187 INFO  [com.liferay.portal.kernel.deploy.auto.AutoDeployScanner][AutoDeployDir:216] Add MSTRPortlet_Liferay.war to the blacklist
1710:48:39,240 WARN  [http-bio-8080-exec-3][404_jsp:?]


I cannot install MSTR plugin using Control Panel as it is not present in the Marketplace. Any clues what should I modify (only change web.xml form or something maybe else) in order to make it work?

Thanks in advance.
Hitoshi Ozawa
RE: Portlet blacklisted
27 febbraio 2013 6.04
Risposta

Hitoshi Ozawa

Punteggio: Liferay Legend

Messaggi: 7952

Data di Iscrizione: 23 marzo 2010

Messaggi recenti

Well, the blacklist will go away once you restart your liferay.
Kravchenko Dmitry
RE: Portlet blacklisted
22 maggio 2013 14.22
Risposta

Kravchenko Dmitry

Punteggio: Regular Member

Messaggi: 139

Data di Iscrizione: 4 ottobre 2010

Messaggi recenti

You can disable then enable Plugin Installer to clear black list without server restart.

Plugin Installation -> Configuration section.
Brian Scott Schupbach
RE: Portlet blacklisted
31 maggio 2013 13.10
Risposta

Brian Scott Schupbach

Punteggio: Expert

Messaggi: 329

Data di Iscrizione: 23 ottobre 2008

Messaggi recenti

FYI: deactivating and re-activiting the plugin instalation module did not work for me.

I second the idea of creating some interface to override the blacklist.
Yann BAILLY
RE: Portlet blacklisted
14 gennaio 2015 5.17
Risposta

Yann BAILLY

Punteggio: New Member

Messaggi: 1

Data di Iscrizione: 14 gennaio 2015

Messaggi recenti

Kravchenko Dmitry:
You can disable then enable Plugin Installer to clear black list without server restart.

Plugin Installation -> Configuration section.


Thank you, it worked for me (Liferay Portal Standard Edition 5.2.3).
Jim Somerville
RE: Portlet blacklisted
16 gennaio 2015 12.03
Risposta

Jim Somerville

Punteggio: New Member

Messaggi: 2

Data di Iscrizione: 19 settembre 2013

Messaggi recenti

My experience with this blacklist issue on 6.2:

Restarting the Tomcat instance and/or the server did not fix the issue. According to the Liferay log, I could successfully re-deploy the portlet afterwards, but it was missing in any pages that included it, with a message stating the portlet had been un-deployed. Even after the restart and re-deploy, not only did it not show up in the pages, but it was not even available in the Applications list of the editor or Control Panel.

The other workaround I saw in this thread (assuming I understood it correctly), de-activating the Plugins Configuration Portlet in the Control Panel > Apps > Plugins Configuration page caused the said Plugins Configuration page to no longer be available, which meant I could not re-activate the portlet. To fix this problem I had to go into the database's portlet table and set the active_ field to "TRUE" for portletid 132, and then restart the server. This portletid was found to correspond to the Plugins Configuration Portlet in 2 instances of Liferay 6.2, but not sure that is the id across all installations.

Eventually, what seemed to resolve the blacklisted portlet issue for me was manually deleting the portlet's directory in the Tomcat's webapps folder on the server. Then I restarted the server (or at least the Tomcat instance), and after restart re-deployed the blacklisted portlets one last time. This then restored the portlets in their pages. Needless to say, this caused some downtime, but was fortunately on a dev server.

I'm not entirely clear what exactly led to the resolution of this problem. I am just putting my experience here in case it helps anyone else. Perhaps version 6.2 has some changes that led to the resolutions above not working, or perhaps I just misunderstood them. Regardless, I will be following the advice in this forum thread of uploading the .war files to a different directory on the server first, and then copying them into the deploy directory from that local file source.
David H Nebinger
RE: Portlet blacklisted
16 gennaio 2015 12.26
Risposta

David H Nebinger

Community Moderator

Punteggio: Liferay Legend

Messaggi: 8378

Data di Iscrizione: 1 settembre 2006

Messaggi recenti

Blacklisting occurs if you try to copy to Liferay's deploy folder over a slow link. If Liferay sees the file and tries to process it before the copy completes, the file gets blacklisted. By slow link, this is usually some sort of network copy (i.e. nfs or samba or ftp) is being used to push the file.

You avoid this problem by not uploading directly to the deploy folder, you upload to another folder on the system and then use the native filesystem routines to locally move the file to deploy folder.