liferay 5.1 installation failure - MySQL configuration - Redirect

[Justin Permar, geändert vor 15 Jahren.]

Hi all,

I've followed the instructions in the Liferay 5.1 portal administrator's guide to download Liferay bundle (the default is 5.1 with Tomcat 5.5) and configure Liferay to use MySQL.

Yes, I've configured Liferay to use MySQL, yes, the database permissions are fine, yes the tables are created just fine in the database. However, Liferay isn't happy. When I go to the URL (http://localhost:8080), it barfs.. specifically, going to the URL redirects me to the following URL and my browser complains:

http://localhost:8080/c/portal/layout

Redirect Loop

Firefox has detected that the server is redirecting the request for this address in a way that will never complete.





Any other versions of Liferay that work? Anyone have a workaround?

Thanks!!

Edit: I should note that of course downloading the bundle and starting up the server (using HSQLD works as expected. Just getting it to use the database... Liferay isn't constructing the tables properly I'm guessing...

Also, I deleted the ~/liferay folder that is created on startup just to see if that was it... no dice

[Justin Permar, geändert vor 15 Jahren.]

Ah, solved my own problem.

Yes, the database creation that's built in to Liferay 5.1.2 is buggy and doesn't work (any developers reading this thread and want to comment??)

As a workaround, I create the database using the "create" scripts as specified in the Installing Liferay for an Enterprise -> Database Setup part of the portal admin guide.

Working now...

Edit: created Jira issue for this: http://issues.liferay.com/browse/LPS-1015

[Ganesh Ram, geändert vor 15 Jahren.]

Firefox has detected that the server is redirecting the request for this address in a way that will never complete.

Did you try clearing the browser cache and then try.
I have seen this some time back, removed the browser cache,and then this it all worked !

[Justin Permar, geändert vor 15 Jahren.]

Ganesh,

Thank you for the tip! That indeed did work. I'm trying this again with a new installation and encountered the same problem... clearing my browser cache worked.

Do you have any further insight into why clearing the cache worked? My obvious concern would be that my portal users would randomly encounter that bug ... hard to tell everyone that they need to clear their cache if they see it!