Reject process action

RE: Reject process action

2018-06-21T13:05:30Z

Definitely! I've even see if when I had misspelled te action name, or when I have an invalid auth token, or when my session had expired (and I had disabled the warning message) and I submitted the action as a "guest", etc. It's a very generic catch-all situation for sure. Debug logging, or even a breakpoint in the source so that you can see the whole stack trace is a great suggestion.

RE: Reject process action

2018-06-20T19:50:56Z

What's the content encoding on the form?

If it's a regular form, if you look at the Apache Tomcat 8 Configuration Reference, both the HTTP Connector and the AJP Connector have a maxPostSize (defaults to 2MB) for forms that aren't set to have multipart encoding.

If it's a multipart-encoded form, it's possible that UploadServletRequestImpl is swallowing an exception, and you'll need to increase the log level to DEBUG in order to see that something is wrong (we added an additional WARN message with LPS-79058 to make this harder to miss, but not everyone is building Liferay from source to be able to take advantage of it).

RE: Reject process action

2018-06-20T13:05:35Z

I often found it helpful to enable debug logging to find the root cause of the issue. Debug shows the actual exception that led to the rejection.

Go to Server Administration and add a new category in logging: "com.liferay.portlet.SecurityPortletContainerWrapper" with "ALL".

Then try again.

RE: Reject process action

2018-06-20T01:24:27Z

Hi Kevin,

Tomcat7 bundle -- does that mean you are on Liferay 6.2 GA6? (just so I can try to reproduce on my side)

Reject process action

2018-06-18T15:18:30Z

Currently I'm seeing an odd warning in my logs:

15:06:10,103 WARN  [http-bio-8080-exec-37][SecurityPortletContainerWrapper:630] Reject process action for

After which my server connection issues with the message

This site can’t be reached
The connection was reset.
Try:

Checking the connection
Checking the proxy and the firewall
ERR_CONNECTION_RESET

This ONLY happens when creating a base64 encoded string and putting it in a hidden input

<aui:input type="hidden" name="emailAttachmentBase64" value="" />

When I do the same with a base64 encoded string that is >= 1.6MB I have no issues. We need to be able to support files <= 4MB. I'm running the tomcat7 bundle. Does the aui:input tag have a value limit? Is there something in the POST request causing problems? Is this even a Liferay issue?