[jboss-jira] [JBoss JIRA] (WFLY-2862) Liferay too many open files during deployment

[Tomaz Cerar (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-2862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tomaz Cerar resolved WFLY-2862.
-------------------------------

    Resolution: Done


We found out that issue in LifeRay itself. 
Issue for tracking that in Liferay is https://issues.liferay.com/browse/LPS-44052
PR that fix that problem is https://github.com/liferay/liferay-portal/pull/515 & https://github.com/liferay/liferay-portal/pull/516 (for 6.2.x branch where the original issue was found)
                
> Liferay too many open files during deployment
> ---------------------------------------------
>
>                 Key: WFLY-2862
>                 URL: https://issues.jboss.org/browse/WFLY-2862
>             Project: WildFly
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Web (Undertow)
>    Affects Versions: 8.0.0.CR1
>         Environment: linux 3.11.0-15-generic
>            Reporter: Jakob Munih
>            Assignee: Tomaz Cerar
>            Priority: Blocker
>             Fix For: 8.0.0.Final
>
>         Attachments: dump-9406-514, dump-fail-deply-lr.txt, dump-nothingtodeploy.txt, open-wildfly.b2, server-fail-deploy-liferay.log
>
>
> Liferay 6.2 deploys as an exploded war. Normally after deployment it builds a theme (css/js boundles). Even if only Liferay is deployed a Too many open files exception is thrown. When /proc/sys/fs/file-max is 6815744. While trying to configure it or deploy other portlets (exploded wars too) the too many open files exception is encountered even at the deployment time (server start up). 
> 13:57:48,110 ERROR [MSC service thread 1-12][MainServlet:262] java.io.FileNotFoundException: /home/munih/development/tools/wildfly-8.0.0.Final-SNAPSHOT/standalone/deployments/ROOT.war/WEB-INF/liferay-layout-templates.xml (Too many open files)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira