Jaap, my reply wasn't the clearest - I meant it is run as a level 1 rather than a level 2 %include, rather than running on lev1/lev2 config. Running long stored processes like this, as you say, is indeed bad practice as it depends on the http request timeout, and can even leave threads hanging in the SPWA sometimes. From memory I think the way it works is the session timeouts & context timeouts come out in the multibridge session log, while the username / session redirection info comes from the spawner logs, and something similar but to do with authentication from metadata. I'm not sure if that's how APM pulls the info out. You should be careful with those if you use cost based load balancing, as sometimes the session timeouts don't subtract the cost from the stp session and you can end up with an unresponsive multibridge session. I'm quite aware of APM, but to be honest it seems like overkill for this particular case, although it can be worth doing due to its other benefits. It can be quite a handful to configure - especially if it requires Alex to negotiate with his admin, which seems like an issue here. I have used it in the past, but have now developed another commercial monitoring solution. I don't want to use these forums to promote my own products but if you find me on linkedin I'd really like to demo it to you, as I think you'd find it very interesting having read some of your more advanced posts on here.
... View more
