Submit Feedback
Legacy Knowledge Base
Published Sep. 10, 2025

A servlet matching the filter (servlet.init.private=false)(servlet.type=friendly-url) is unavailable

Written By

Mariano Alvaro

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

Issue

  • The following WARN message is obtained during the portal startup: 
    2020-02-07 09:02:43.401 WARN  [http-nio-9090-exec-7][PortalImpl:6752] javax.servlet.ServletException: A servlet matching the filter (servlet.init.private=false)(servlet.type=friendly-url) is unavailable
    javax.servlet.ServletException: A servlet matching the filter (servlet.init.private=false)(servlet.type=friendly-url) is unavailable
            at com.liferay.portal.servlet.ServletAdapter.service(ServletAdapter.java:92)

Environment

  • Occurs during the portal startup, sometimes motivated by a recent upgrade.

Resolution

  • This message is obtained when there is not a matching component with properties servlet.init.private=false and servlet.type=friendly-url enabled.
  • By default Liferay offers a matching component called com.liferay.friendly.url.internal.servlet.PublicFriendlyURLServlet contained in Liferay Friendly URL Service module.
  • If the error appears it means that the component isn't enabled, so the following must be done:
    • Check that the module Liferay Friendly URL Service has successfully been upgraded: Checking Upgrade Status
    • Check that there aren't unsatisfied dependencies regarding the module: System Check
Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?