F5 loadbalancer configuration for Stand alone Java Application.

[uttara]

We are using a Core Java APP with no WEBSERVER, which is MULTI-Threaded. We have a requirement where in ,our app is to be made highly available in the customers environment.
All the transactions in our app are majorly ActiveMQ(Java Messaging Services TCP connections) based i.e. we communicate with other apps using message Queues. We also have HTTP connections
For High-availability of ActiveMQ ,we have implemented it in Master/Slave Configuration(Active/Passive)
We wanted to acheive High-availability of Stand-alone application any suggestion for the same would be really helpful.

 

[itsmydamnation]

you haven't really said anything that matters in determining load balancer config. but really for just active/standby you have pool priority activation ( be aware what happens when the primary returns). The next thing is what test you want to do to determine if the service is available on the member servers.....

 

[uttara]

you haven't really said anything that matters in determining load balancer config. but really for just active/standby you have pool priority activation ( be aware what happens when the primary returns). The next thing is what test you want to do to determine if the service is available on the member servers.....

we have process running in the background for stand-alone application .
Can we configure F5 LB to swtich active To Passive Instance based on availability of a process ?
As long as transactions are going thru it's okay to run application on passive instance even if active instance is up.

 

[debian0001]

If it's HTTP based, you can watch port 80 in f5 and direct traffic either in active / passive, or active / active (round robin) or whatever type you want.

 

[Railgun]

You have to be careful with your monitors. Simply pointing to a tcp port to determine if a box or app is up may not cut it. If the app stops processing data, it doesn't mean the box isn't listening on the port anymore. Any suitable script that can test the app itself is recommended. I'd setup priority activation as mentioned above for the load balancing that matches to your server config.