"Forward does not exist" occurs in "Server Administration" and "Users and Groups"

Clone of already closed LPS-24406 though the problem still persists and is easily reproducible with two separate machines for web server (Apache HTTPd with mod_jk) and app server with Liferay Portal.

Hi Peter,
Does this exist on 6.1 GA 1?

Yes it does, actually I did test it on 6.1 GA 1 only.

Alright thanks Peter. The reason I ask is because the description still says RC1, which is irrelevant at this point. I will update the ticket according to the version you reproduced and have our QA team retest this issue.

Thank you!

Unable to reproduce using the following steps:

1. Use the Setup Wizard to configure Liferay
2. Click Go to to > Control Panel
3. Click Server Administration
4. Click Execute next to Run the garbage collector to free up memory.
5. Click Execute next to Clear content cached by this VM.
6. Click Execute next to Clear the database cache.
7. Click Execute next to Reindex all search indexes.
8. Click Execute next to Reset preview and thumbnail files for Documents and Media portlet.
9. Click Execute next to Generate thread dump.
10. Click Execute next to Verify database tables of all plugins.
11. Click Execute next to Clean Up Permissions
12. Click User and Organizations
13. Create a User
14. Create a Regular Organization
15. Deactivate the User
16. Delete the User
17. Delete the Organization

Unable to reproduce on:
Tomcat 7 + MySQL 5. Portal 6.1.0 CE GA1.

Hi Peter,
Our team has been unable to reproduce your issue. I will leave this ticket open for another day to give you time to respond with further instructions on how to we should proceed to reproduce this issue.

Hello,
the most important part of the whole thing is to have a Apache HTTPd with mod_jk in the front of the Tomcat instance with Liferay Portal 6.1 and they must be running at separate machines as well. If they run on single machine it doesn't occur.
I don't really know why it happens only that way as my initial investigation of the AJP traffic between HTTPd and Tomcat doesn't show any differences other than those relevant to different deployment scenarios (different hosts, ports etc transferred in AJP 1.3 headers such as SRV, PORT), but it happens only if these conditions are met.

I am getting the same issue Forward does not exist in Systems Administration Section..Same config Aache, Tomcat and MySQL all on different machines

VERIFIED through Manual Testing using the following steps:

#Use the Setup Wizard to configure Liferay
#Click Go to to > Control Panel
#Click Server Administration
#Click Execute next to Run the garbage collector to free up memory.
#Click Execute next to Clear content cached by this VM.
#Click Execute next to Clear the database cache.
#Click Execute next to Reindex all search indexes.
#Click Execute next to Reset preview and thumbnail files for Documents and Media portlet.
#Click Execute next to Generate thread dump.
#Click Execute next to Verify database tables of all plugins.
#Click Execute next to Clean Up Permissions

Reproduce on:
Tomcat 7.0 + MySQL 5. Portal 6.1.0 CE GA1.

I can see the blank page and console throw error message.

Verified on:
Tomcat 7.0 + MySQL 5. Portal 6.2.x GIT ID: 5aab349d09416f1348e83a1ac907c3e38134e0ad.
Tomcat 7.0 + MySQL 5. Portal 6.1.x EE GIT ID: 459cc2fcbbb54786f5fabb8eb5d4024c2de3d328.

I can not see the blank page. It is working and console not error message.

Slated for inclusion in 6.1.1 CE GA2

Please make sure to properly set your portal.properties to include your load balancer. If you do not, Liferay's security settings will not properly work where redirects are used.

##
## Redirect
##

    #
    # Set this property to "ip" or "domain" for the redirect security method. If
    # set to "domain", the portal will only redirect users to domains listed in
    # the property "redirect.url.domain.allowed". If set to "ip", the portal
    # will only redirect to domains whose IP address resolve to an IP address
    # listed in the property "redirect.url.ip.allowed".
    #
    #redirect.url.security.mode=domain
    redirect.url.security.mode=ip

    #
    # Input a list of comma delimited domains which the portal is allowed to
    # redirect to. Input a blank list to allow any domain.
    #
    redirect.url.domains.allowed=

    #
    # Input a list of comma delimited IPs which the portal is allowed to
    # redirect to. Input a blank list to allow any IP. SERVER_IP will be
    # replaced with the IP of the host server.
    #
    redirect.url.ips.allowed=127.0.0.1,SERVER_IP,192.168.116.148