Real brain bender: virtual host or omni portlet issue? Take the challenge

Question

We are having problems with a portal page that displays several omni portlets on several tabs. Here's the situation:
The page consists of 5 tabs, each representing a different demographic characteristic. On each tab there are four omni portlets. One omni porlet represents a selection list. The user makes a selection, which triggers an omni portlet event to pass the selection criteria to a page parameter. The other three omni portlets on the tab read the parameter value and retrieve data according to the selected parameter value.
Example: The user selects the Age tab and selects the link representing data for the Central Region. The omni portlet's event populates the page's "region" parameter with the value "Central." The other three portlets on the tab retrieve their respective data where region = 'Central'.
Since all the tabs on the page represent different demographic characteristics, the omni portlets on all the other tabs also perform their queries where region='Central' so that the user will see Central Region data displayed regardless of what tab they navigate to.
Also, when the user navigates to another tab and selects a different region, all the omni portlets on all the tabs perform their respective queries to capture data where region=<selected region>.
The page performs correctly until we configure a virtual host. In that case, when a user makes a selection of a particular county in one tab, the queries are performed but the page displays with a tab in view other than the one where the user made the selection.
Example: the user navigates to the Age tab and selects region='Central'. Then the user navigates to Gender tab and then Living Situation tab, viewing the results on each tab. Now the user returns to Gender tab and selects region='Western.' The portlets perform their queries and the page re-displays with the user on Living Situations tab, rather than Gender tab where the selection was made.
Obviously, we want the user to stay put on the tab in which they make their selection. I think it's a problem with the virtual host configuration. My DBA thinks it's a problem with the way the page is built. Has anyone else run into this kind of thing? Is there a trick to using Virtual Hosts?

Answer 1

Your main.cf seems redundant.
For example:
if you specify:
virtual_alias_maps = hash:/etc/postfix/virtual_alias, mysql:/etc/postfix/mysql_virtual_forwards.cf
you don't need this:
alias_maps = hash:/etc/postfix/aliases
and i think you have a lot of more options you don't need.
This is my main.cf on my vps and everything works great (sending and receiving emails from/to most common mail server: gmail, hotmail etc etc)
smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU)
biff = no
# appending .domain is the MUA's job.
append_dot_mydomain = no
readme_directory = no
# TLS parameters
smtpd_tls_cert_file=/etc/ssl/certs/ssl-cert-snakeoil.pem
smtpd_tls_key_file=/etc/ssl/private/ssl-cert-snakeoil.key
smtpd_use_tls=yes
smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache
smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache
message_size_limit = 4194304
virtual_mailbox_domains = mysql:/etc/postfix/mysql-virtual-mailbox-domains.cf
virtual_mailbox_maps = mysql:/etc/postfix/mysql-virtual-mailbox-maps.cf
virtual_alias_maps = mysql:/etc/postfix/mysql-virtual-alias-maps.cf
virtual_transport = dovecot
dovecot_destination_recipient_limit = 1
it is very simple (no dkim, no forced tls, no mailbox limits and so on) and it can be improved but it works..
as I suggested you just try spending some hour wiping postfix installation and giving a look to this guide