IBM webMethods Hybrid Integration

IBM webMethods Hybrid Integration

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
  • 1.  Http post and caching the result

    Posted Wed August 17, 2005 10:00 PM

    I have a flow service that does a http(s) post and retrives result from an external site. At times, my service seems to be returning results from a cache. I receive header infroamtion with empty body. At other times, i receive a previously fetched result.
    What setting should i be looking for?


    #webMethods
    #Integration-Server-and-ESB
    #Flow-and-Java-services


  • 2.  RE: Http post and caching the result

    Posted Thu August 18, 2005 08:18 AM

    Hi WebMethodsUser,

    Kindly check the “properties(on right hand side of developer window)” of the service you have made in developer and make “cache results”=false

    Cache result property explanation :
    Specifies whether the server stores the service results in a local cache for the time period specified in the cache expire property.after the service executes, the server places the entire pipeline contents into a local cache.when subsequent request for the service provides the same set of input values, the server returns the cached results instead of invoking the service again.select “True” to cache the service result.

    Regards,
    Puneet Saxena


    #Flow-and-Java-services
    #webMethods
    #Integration-Server-and-ESB


  • 3.  RE: Http post and caching the result

    Posted Thu August 18, 2005 03:34 PM


  • 4.  RE: Http post and caching the result

    Posted Thu August 18, 2005 03:44 PM

    We are having the similar problem…When we used restore/refresh on Developer, it works ok

    Are you restorePipelines disabled?


    #Integration-Server-and-ESB
    #webMethods
    #Flow-and-Java-services


  • 5.  RE: Http post and caching the result

    Posted Thu August 18, 2005 05:16 PM

    This is something to do with the following extended settings:
    1.watt.server.cache.flushMins
    Specifies how often (in minutes) the server sweeps the cache to remove expired cache entries and to prefetch cache service entries. The default is 10 minutes.
    2.watt.server.cache.gcMins

    specify 0 for both of them and see what happens.

    Good Luck!
    ramesh.


    #webMethods
    #Flow-and-Java-services
    #Integration-Server-and-ESB