Uploaded image for project: 'WildFly Discovery'
  1. WildFly Discovery
  2. WFDISC-37

Inconsistent use of timeout in Discovery.BlockingQueueSericeQueue

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • 1.1.1.Final
    • None

      The discovery interface allows making calls to discovery with or without a timeout value:

      ServicesQueue discover(ServiceType serviceType, FilterSpec filterSpec)

      ServicesQueue discover(ServiceType serviceType, FilterSpec filterSpec, long timeout, TimeUnit timeUnit)

      Also, calls to the ServicesQueue returned by a call to discovery can be made with or without specifying a timeout value:

      ServiceURL takeService()

      ServiceURL takeService(long timeout, TimeUnit timeUnit)

      These two approaches to specifying timeout values are implemented in an inconsistent manner and don't do what is expected.

       

       

              rachmato@redhat.com Richard Achmatowicz
              rachmato@redhat.com Richard Achmatowicz
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: