D
dbeavon
Guest
Yes, it did work, based on my preliminary testing. But even then, it only manages connection resources for the *one* client application (and it is only possible to perform this operation on the .Net *client* side within the process itself.) But if you have a state-free broker running on a server with numerous client application instances connected to it (a hundred) and multiple client connections from each application (session-pool sessions) then the amount of resources consumed by all this will grow quite large. I was asking if there were some way to administratively free up resources from the server-side of things (eg. disconnect *all* clients tied to a single user name or all that are from a single remote I.P. address). The only recourse an administrator has is to stop and restart the entire broker, but that will be disruptive to *all* one hundred of the remote applications (some of which are more important than others). The reason I brought up OE PAS technology is because I suspect tomcat has a way to administer its remote sessions at a finer level of control than to just perform a full restart. Another quick thought: I suspect that one possible solution for us may be to set up *several* state-free brokers that cater to different populations of remote clients (ie. one broker per application type). Then a "low-priority" broker could be restarted without impacting high-priority applications, because those would be connected to a different broker.
Continue reading...
Continue reading...