Forum Discussion
jgranieri_42214
May 02, 2012Nimbostratus
tcp release closing connection abruptly ?
Hello,
Running V10.2.3 and setup an irule below to LB based on tcp payload data collected. I am searching FIX comp id's and loadbalancing based on 1 id i have listed.
I ran tcpdump and see that the rule works fine except that the irule seems to close the connection after execution and the app server cant send a logon message back to the original socket since its closed ? any idea's ? Is the tcp::release closing the socket as its LB to the server ?
when CLIENT_ACCEPTED {
TCP::collect 250
}
when CLIENT_DATA {
log local0. "in CLIENT_DATA"
if { [TCP::payload] contains "xxx-yy-1" } {
pool Pool1
} else {
pool Pool2
}
TCP::release
}
- jgranieriNimbostratusI finally got this simple irule to work for FIX, it turns out you dont need to specify specific number of bytes after tcp::collect.
- JRahmAdmintest
- Jeff_Browning_2Historic F5 AccountTest 8
- Joel_MosesNimbostratusOo! Oo! Can I join in?
Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects