Create a flag for disabling the validateConnection() "blip" for performance reasons

Details

  • User impact:
    Low
  • Effort points:
    0
  • Affects Docs:
    Yes
  • Migration Impact:
    Every connector in xml config now has a 'validateConnections' boolean attribute (only few had it before). It must be treated as a hint only (default is true), and transports may honor it to do any extra validation in a transport-specific way.
  • Similar Issues:
    None

Description

The isAbleToConnect() method was added to make retry policies work efficiently, but it might be a performance hit in extreme cases so we should add a flag in order to disable it and/or automatically disable it when retry is not configured.

Issue Links

relates to

Bug - A problem which impairs or prevents the functions of the product. MULE-4147 Current contract for Connectable.validateConnection() is wrong

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Transition Time In Source Status Execution Times Last Executer Last Execution Date
Open Open In Progress In Progress
11d 23h 13m 1 Ken Yagen 09/Feb/09 11:03 AM
In Progress In Progress Closed Closed
5h 23m 1 Andrew Perepelytsya 09/Feb/09 04:27 PM
Closed Closed Reopened Reopened
1d 2h 45m 1 Daniel Zapata 10/Feb/09 07:13 PM
Reopened Reopened Closed Closed
6d 19h 51m 1 Andrew Perepelytsya 17/Feb/09 03:04 PM

People

  • Assignee:
    Andrew Perepelytsya
    Reporter:
    Travis Carlson
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: