Hi,
I'm using Spring Security in an application of ours, which we have
successfully authenticating users. We did this because we already have an
existing single sign on solution in place.
What that means is that none of our log messages have the user id's in them
- unless the user is also
Turns out I've figured out the answer to my own question.
Use the little known max-concurrent-requests feature to force a
limitation on how many requests can run at one time. This ensures that any
requests that take a little too long are given the opportunity to finish
before before the next
Have you looked at ProdEagle? It provides counter facilities that might help
you pinpoint your issue if not exactly counting every operation . Details and
links to code at ProdEagle.com
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java
