S
ssouthwe
Guest
Please pardon my ignorance here - I think the nomenclature is throwing me off. There are so many things called "session" that it's confusing me. It's not clear to me in some cases whether session relates to a session in the MS agent, something tomcat related, or the HTTP session of the user. What I'm really looking for in all of this is how I can use whatever tools are available to remedy a stuck request. So, if my MS Agent has several sessions going, each of which may be serving a request, but one of the requests is hosed and has become a runaway process, how would I find that and kill it? How would I take the information gleaned in finding what Agent/Session/Request failed, and match that up to data that my app can store, and use that to hunt down and fix the bug? Is it even possible to kill just one session in the MS Agent? You wouldn't want to kill the whole agent and disrupt everyone's work to fix one problem, right?
Continue reading...
Continue reading...