-
Type:
Bug
-
Status: Closed
-
Resolution: Won't Fix
-
Affects Version/s: 6.2.10 EE GA1, 6.2.X EE
-
Fix Version/s: None
-
Component/s: Core Infrastructure
-
Labels:
-
Fix Priority:3
-
Git Pull Request:
Liferay Portal 6.2 versions are generally bundled with Tomcat 7.
However they can also be set up with Tomcat 8 - that configuration works too, but there is a warning displayed for custom plugins referencing a Tomcat property which is deprecated since Tomcat 8.
Environment:
Liferay 6.2.x with Tomcat 8.5.57
Steps to reproduce:
- Deploy Liferay 6.2 on Tomcat 8.5.57
- Start the bundle.
- Deploy the attached portlet (MVCPortlet6210-portlet-6.2.10.1.war).
Actual result:
During the deployment of the portlet, the following warning appears in the logs:
WARNING [localhost-startStop-2] org.apache.catalina.startup.SetContextPropertiesRule.begin [SetContextPropertiesRule]{Context} Setting property 'antiJARLocking' to 'true' did not find a matching property.
Expected result:
There are no warnings in the logs related to the 'antiJARLocking' property.
Tested on:
6.2.x @65d7a800f1a57b232a127bdcaefb876a9de469f9
We found that during deployment, a context.xml file is added to the portlet's META-INF folder, which contains the following:
<Context antiJARLocking="true" antiResourceLocking="true" />
This file comes from the portal-impl.jar module:
{tomcat}/webapps/ROOT/web-inf/lib/portal-impl.jar/com/liferay/portal/deploy/dependencies/context.xml
If the property is removed from the context.xml file in the portal-impl.jar module, and the custom portlet is redeployed, the warning does not appear anymore.