掲示板

Wildfly 8.0 and Liferay 6.1.2 OR 6.2

9年前 に Paolo Paolo によって更新されました。

Wildfly 8.0 and Liferay 6.1.2 OR 6.2

New Member 投稿: 3 参加年月日: 13/10/02 最新の投稿
Dear all,
I have the following configuration:
OS: Fedora 20 x64
JRE: 1.7_51
Liferay: 6.1.2 but I experience the identical issue with 6.2 too
DB: clean Mysq installation (I let liferay to create the schema)
App server: Wildfly 8.0

Apparently everything starts fine, but I found a problem within control panel: If I go into "Server Administration" I display the page correctly (I see the gauges stuff and everything else) but, if I click any of the buttons (LogLevels, Properties, CAPTCHA etc...), part of the page (main content) stays empty.

Logs give the following ERRORS:
09:23:34,532 ERROR [default task-9][PortletRequestProcessor:321] User ID null
09:23:34,533 ERROR [default task-9][PortletRequestProcessor:322] Current URL /group/control_panel/manage/-/server/log-levels?refererPlid=10187&controlPanelCategory=configuration&_137_tabs3=
09:23:34,533 ERROR [default task-9][PortletRequestProcessor:323] Referer http://localhost:8080/group/control_panel?refererPlid=10187&p_p_id=137&controlPanelCategory=configuration
09:23:34,534 ERROR [default task-9][PortletRequestProcessor:324] Remote address 127.0.0.1
09:23:34,534 ERROR [default task-9][PortletRequestProcessor:326] Invalid path was requested %2Fadmin_server%2Fview


I tried to debug with sources and apparently the problem is with %2Fadmin_server%2Fview string. If it was not escaped, so /admin_server/view, the page would be displayed correctly.
Unfortunately I couldn't figure out why and where it gets escaped.
Any clue about this?
Thanks,
Paolo
thumbnail
9年前 に André Bunse によって更新されました。

RE: Wildfly 8.0 and Liferay 6.1.2 OR 6.2

Junior Member 投稿: 65 参加年月日: 14/02/13 最新の投稿
Do you set UTF8 encoding in JAVA_OPTS (6.1.2) or CATALINA_OPTS (6.2)?
9年前 に Paolo Paolo によって更新されました。

RE: Wildfly 8.0 and Liferay 6.1.2 OR 6.2

New Member 投稿: 3 参加年月日: 13/10/02 最新の投稿
Hi André,
I'm currently running Jboss from eclipse, thus I put the jvm startup option
-Dfile.encoding=UTF-8

Thanks,
Paolo
thumbnail
9年前 に André Bunse によって更新されました。

RE: Wildfly 8.0 and Liferay 6.1.2 OR 6.2

Junior Member 投稿: 65 参加年月日: 14/02/13 最新の投稿
Sorry, right now i have no more ideas emoticon
9年前 に Francisco Pareja によって更新されました。

RE: Wildfly 8.0 and Liferay 6.1.2 OR 6.2

New Member 投稿: 11 参加年月日: 09/03/17 最新の投稿
Hi, Paolo

I'm installing Liferay 6.2 with wildFly 8 and MySQL and y get the same error. I don`t solve it jet because i get some other errors, but it seems that its a general error thats appears in Liferay/WildFly instalations.

Other problems I get....hotDeploy for plugins not works, and I can´t login users the first time after browser starts, the second works fine. Did you get this errors in your instalation???
thumbnail
9年前 に Rasto Rehak によって更新されました。

RE: Wildfly 8.0 and Liferay 6.1.2 OR 6.2

Junior Member 投稿: 66 参加年月日: 07/03/08 最新の投稿
Hi
we have the same problem. Basically in any friendlyURL mapper it encodes parameters to query string and undertow does not decode them back in requestDispatcher.include() .
Continue to debug...
9年前 に Samuel Contesse によって更新されました。

RE: Wildfly 8.0 and Liferay 6.1.2 OR 6.2

New Member 投稿: 3 参加年月日: 12/08/27 最新の投稿
Hello Rasto,

Did you have time to debug this issue ? I'm facing the same problem with Liferay 6.2 on WildFly 8.1. So far, I had to fix other problems like cookie path not being set correctly for default deploy context (certainly related to WFLY-3448 which has been fixed after the 8.1 release).

I had a look in org.apache.catalina.core.ApplicationHttpRequest and it confirms that Tomcat and JBoss Web are decoding the parameters using the RequestUtil class.

Let me know if you find anything interesting...
9年前 に Samuel Contesse によって更新されました。

RE: Wildfly 8.0 and Liferay 6.1.2 OR 6.2

New Member 投稿: 3 参加年月日: 12/08/27 最新の投稿
Well, I decided to find the best place to url decode render parameters. I finally ended up doing it in PortletRequestImpl. I don't know if it's worth to pull request and also if it should be done like that.

If you want to see these changes on GitHub, do not care about PortletRequestProcessor.java which is actually reverting another not working commit to this problem.