Page 3 of 3 FirstFirst 123
Results 21 to 22 of 22

Thread: outof memory issue

  1. #21
    Join Date
    May 2010
    Posts
    17

    Default

    ok ill test it out when youve had a chance to add it to svn. The delay technique didnt work im pretty sure its because its on the recieve part the catch does not occur.. anyway i will wait and test again over the new implementation in case that just solves it

    keep up the good work

  2. #22
    Join Date
    Mar 2010
    Location
    Gtr Philadelphia, PA
    Posts
    2,016

    Default

    OK; I just committed the change. It's in SVN and should be in tonight's nightly. Sorry for the delay, it was a little more involved than I thought it would be.

    I didn't update the documentation yet but, essentially, there is a new attribute 'close' on the inbound and outbound gateways and on the inbound adapters.

    When set to true, an outbound gateway will close the socket when the response is received; an inbound gateway will close the socket after it sends the response; on an inbound adapter it will close the socket after the inbound message has been received and before it is sent to its channel.

    Let us know if this solves your issue; thanks.

Posting Permissions

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