Forum Discussion
Rodrigo_N_Soare
Nimbostratus
NimbostratusRewrite and Jboss with Jsessionid
Hi,
I need some help how can I do what is in apache:
Apache as load balancer (so below a node, but the f5 using two nodes)
Jboss is the node server
VirtualHost *:80
ServerAdmin admin@dest.com
ServerName sistema.dest.com
ProxyPass /sistema/ http://10.0.0.2:8080/sistema/
ProxyPass / http://10.0.0.2:8080/sistema/
ProxyPassReverse / http://10.0.0.2:8080/
Options -Indexes
To rewrite using F5 or proxypass profile. I made some attempts using these links: https://devcentral.f5.com/wiki/iRules.proxypassv10.ashx http://support.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/ltm-implementations-11-4-0/21.html But with jsessionid in a Jboss environment: https://devcentral.f5.com/wiki/iRules.Weblogic_JSessionID_Persistence.ashx Does not work with the rewrite Balancing Jboss error "/pages/login.xhtml;jsessionid=IcTjndaodTDnTntpnKrn.undefined"
Rodrigo_N_Soarehi Michael,
The cookie problem I already solved. The question now is how this transfomar this in apache as a front end for the F5 as the front end of the pool Jboss
Apache:
VirtualHost *:80 ServerAdmin admin@dest.com ServerName sistema.dest.com ProxyPass /sistema/ http://10.0.0.2:8080/sistema/ ProxyPass / http://10.0.0.2:8080/sistema/ ProxyPassReverse / http://10.0.0.2:8080/ Options -Indexes- MichaelatF5
Employee
Just to be clear, what are you trying to accomplish? Do you just want to load balance 2 JBoss nodes? What is not working, persistence or base functionality?
Depending on your TMOS version, a lot of the proxypass functionality is built in, and you do not need to implement an iRule to handle the rewrites.
As for the JSessionID, have you validated through the logs to ensure that it exists in the format you are looking for (for example, proper domain, proper value)?
You should see a log entry on the first response when they JSESSIONID cookie is created: log local0. "127.0.0.1:0: Added persistence record from cookie: [persist lookup uie [string tolower [HTTP::cookie "JSESSIONID"]]]"
I have had customers that the JSESSIONID cookie wasnt generated, but was dropped into the URI, so using the cookie wasnt an option. We were able to shorten things down and extract from the URI to set persistence.
