Affects Version/s: 6.2.2 CE GA3 , 6.2.X EE
- Update your [TOMCAT_HOME]/webapps/ROOT/WEB-INF/web.xml to make sessions time out in 1 minute
- Set the following in your portal-ext.properties to extend sessions automatically:
- Start the portal
- Install Audience Targeting application (e.g. using the Marketplace portlet on Control Panel)
You will see the following warnings in every minute:
The servlet contexts of the above bundles don't return a request dispatcher object, which causes a NullPointerException in extend_session.jsp, and the code sends the warning to the log for any type of exceptions encountered.
However, servlet contexts don't have to return a request dispatcher for every servlets, and if they don't, it's basically not an error, so it might not be something that the user should be warned about.
See official Java documentation:
https://docs.oracle.com/javaee/7/api/javax/servlet/ServletContext.html#getRequestDispatcher(java.lang.String) - note the sentence: This method returns null if the ServletContext cannot return a RequestDispatcher. The source code of our implementations of this interface in com.liferay.portal.apache.bridges.struts.LiferayServletContext and com.liferay.portal.http.service.internal.servlet.BundleServletContext also indicate that the method getRequestDispatcher can return null.
https://docs.oracle.com/javaee/7/api/javax/servlet/RequestDispatcher.html#include(javax.servlet.ServletRequest, javax.servlet.ServletResponse) - the inlcude method that is used in extend_session.jsp can throw ServletExcption and IOException, and these are the ones that we might want to inform the user about.