Hi,
Please help me with some of issues stated below,
Is weblogic server is designed to support long lived (nailed-up) HTTP
connections ?
We know that the Execute
thread count recommended for most of applications
is 15 .. But I have a very different requirement where in I want to use
nailed-up connections from a client outside firewall on to weblogic server.
These nailed-up connections are used to notify events happening on server
back to client and they remain nailed-up as long as client is alive. This
is required for realtime event notification from server to client accross
firewall.
If I increase the thread count of weblogic server to serve 50 clients, then
serverside resource are going
to be shot high because 75 (50 nailed-up + 15 for application requests)
threads , the normal application requests (short-lived) should use the 15
threads and 50 nailed-up threads are for event notification.
Is it recommended to have different server for nailed-up connections Or is
it okay if I use single server.
What is the benchmark on number of nailed-up connections(Execute Thread
count ) on server ?
what if the number of clients increase say maximum up to 200? Is it a
feasible solution with weblogic server ?
Is it advisable to have this kind of nailed-up connections on weblogic ?
appreciate your help ..
thx
Sathya
