Results 1 to 3 of 3

Thread: Concurrent request monitoring

  1. #1
    Join Date
    Jul 2011
    Location
    Cape Town
    Posts
    10

    Default Concurrent request monitoring

    Hi there,

    Although I'm aware that fronting your web service with some proxy (e.g. Apache Synapse) is likely to be one way to monitor concurrent request (per authenticated client), I've been thinking about how to do this with Spring Web Services.

    At they very least, if an authenticated user goes haywire, intentionally or not, I'd like to have some kind of WARN level logging with an indication of how many concurrent requests I'm receiving from the said user, and I'd like to do this within my Spring WS app.

    It may be that I'm barking up the wrong tree here.

    Would be interested to hear your thoughs.

    Cheers,
    Nico

  2. #2
    Join Date
    Jul 2011
    Location
    Cape Town
    Posts
    10

    Default

    It seems like a combination of a custom ClientInterceptor and common abstract base class for all EndPoints with hit registering / deregistering methods could do the trick.

    This ClientInterceptor would have to run after the XwsSecurityInterceptor.

  3. #3
    Join Date
    Jul 2011
    Location
    Cape Town
    Posts
    10

    Default

    In case anyone is interested, the above solution worked for me, that is implementing EndpointInterceptor. The only difference is I positioned it before XwsSecurityInterceptor since this bean removed the security credentials (I did not investigate why).

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •