D
dbeavon
Guest
Is there any way to *disconnect* the state-free client sessions from the broker side (as discovered via asbman -clientdetail)? I haven't found a way to disconnect specific sessions and free up the memory. Such a thing would be useful if there were individual/misbehaving client sessions. Obviously we can stop the entire state-free broker but that is extremely disruptive to *all* client applications that are using the broker (rather than just disrupting a single misbehaving client session). I haven't found anything like this yet. It seems to be a pretty significant oversight. IMHO, any kind of client/server technology should allow administration on the server side to manage (disconnect) the misbehaving clients. (In theory the state-free clients are "session-free" and, taking that terminology literally, you wouldn't think these clients should consume long-lasting connection-related resources on the server. But we've found that, in the case of classic appserver, there are "broker" connection resources which are persistent - and for very long periods of time.) I may take a peek at OE PAS (apache tomcat) and see if that technology has features to manage its connected clients, whether session-free or not.
Continue reading...
Continue reading...