{"comment":{"created_at":"2011-10-07T17:58:10Z","body":"Good catch, thanks for this. Please give the fix a try, it's in the mule-3.2.x branch.","updated_at":"2011-10-07T17:58:10Z","url":"https://api.github.com/repos/mulesoft/mule-transport-amqp/issues/comments/2324546","id":2324546,"user":{"avatar_url":"https://secure.gravatar.com/avatar/c48948f53594545aa48de2146389f48a?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","url":"https://api.github.com/users/ddossot","id":119028,"login":"ddossot"}},"action":"created","issue":{"number":4,"created_at":"2011-10-07T12:51:37Z","pull_request":{"diff_url":null,"patch_url":null,"html_url":null},"body":"on an outbound endpoint ResponseTimeout has no effect. Looks like DefaultResponseTimeout is being used from MuleEvent. Changing the DefaultResponseTimeout in the config does change the AMQP timeout.\r\nCan we have ResponseTimeout on the endpoint override the DefaultResponseTimeout. This will help with longer running messaging.","comments":1,"title":"ResponseTimeout","updated_at":"2011-10-07T17:58:10Z","url":"https://api.github.com/repos/mulesoft/mule-transport-amqp/issues/4","id":1843142,"assignee":null,"milestone":null,"closed_at":"2011-10-07T17:57:39Z","user":{"avatar_url":"https://secure.gravatar.com/avatar/dfcdf87c53bd91bb8fa981db42de5bb1?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","url":"https://api.github.com/users/mouldt","id":1070461,"login":"mouldt"},"html_url":"https://github.com/mulesoft/mule-transport-amqp/issues/4","labels":[],"state":"closed"},"legacy":{"issue_id":1843142,"comment_id":2324546}}