Legacy Knowledge Base
Published Jun. 30, 2025

A "processAction method not implemented" error is shown in the log

Written By

Daniel Couso

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

  • Many processAction method not implemented errors are thrown in the server log:
ERROR [http-nio-8080-exec-1][PortletServlet:117] null

javax.portlet.PortletException: javax.portlet.PortletException: processAction method not implemented

at com.liferay.portal.kernel.portlet.LiferayPortlet.callActionMethod(LiferayPortlet.java:192) ~[portal-kernel.jar:?]

at com.liferay.portal.kernel.portlet.bridges.mvc.MVCPortlet.callActionMethod(MVCPortlet.java:439) ~[portal-kernel.jar:?]

at com.liferay.portal.kernel.portlet.LiferayPortlet.processAction(LiferayPortlet.java:82) ~[portal-kernel.jar:?]

at com.liferay.portal.kernel.portlet.bridges.mvc.MVCPortlet.processAction(MVCPortlet.java:256) ~[portal-kernel.jar:?]

...

Caused by: javax.portlet.PortletException: processAction method not implemented

at javax.portlet.GenericPortlet.processAction(GenericPortlet.java:223) ~[portlet.jar:3.0.1]

at com.liferay.portal.kernel.portlet.LiferayPortlet.callActionMethod(LiferayPortlet.java:187) ~[portal-kernel.jar:?]

... 191 more

 

Environment

  • Liferay DXP 7.1+.

Resolution

  • One of the causes could be that the action name used in the url is not declared or have a different name.
  • For example, if we define:
    @ProcessAction(name="submitMyAction")
    ...
    We should declare the same name in the url: submitMyAction
  • Another example would be within a MVCActionCommand at the time of specifying the property mvc.command.name:
    @Component(
    immediate = true,
    property = {
    "javax.portlet.name=" + JournalPortletKeys.JOURNAL,
    "mvc.command.name=/journal/add_folder"
    },
    service = MVCActionCommand.class
    )
    public class AddFolderMVCActionCommand extends BaseMVCActionCommand {

    @Override
    protected void doProcessAction(
    ActionRequest actionRequest, ActionResponse actionResponse)
    throws Exception {

    ...

    }

    ...

    }

    The value of this property should be same of the URL parameter MyPortlet_javax.portlet.action

Did this article resolve your issue ?

Legacy Knowledge Base