Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error with logviewer portlet #3

Open
rayees80 opened this issue Mar 23, 2016 · 1 comment
Open

Error with logviewer portlet #3

rayees80 opened this issue Mar 23, 2016 · 1 comment

Comments

@rayees80
Copy link

Hi,

First, we found the log viewer portlet very useful.

But yesterday, We came across the following error message while using logviewer.
Please advice...

Mar 22, 2016 4:53:36 PM org.apache.catalina.core.StandardWrapperValve invoke
SEVERE: Servlet.service() for servlet [default] in context with path [] threw exception
java.io.FileNotFoundException: /root/liferay-portal-6.2-ce-ga4/tomcat-7.0.42/work/Catalina/localhost//aggregate/https/html/portlet/journal/js/navigation.jsbrowserId=other&minifierType=js&languageId=en_US&b=file%3A%2F%2F%2F..%2F..%2F..%2F..%2F..%2F..%2F..%2Fboot.ini............................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................&t=1458222788000_E_CONTENT_TYPE (File name too long)

Is it OK continuing using the portlet?

@cwho
Copy link
Contributor

cwho commented Mar 23, 2016

It is OK to continue using the portlet (the portlet is not the component causing that log content to be generated).
Do you see those log contents as well in your tomcat's catalina.out file?

It looks to me that someone tried to modify a liferay JS URL to send invalid URL parameters, you might have a look at your access logs to check.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants