Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-4619

JGroupsTransport.invokeRemotelyAsync with a filter returns null on timeout

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Done
    • 7.0.0.GA
    • 7.0.1.CR1, 7.0.1.GA
    • None
    • None
    • EAP 7.0.1

    Description

      JGroupsTransport.invokeRemotelyAsync() has a ResponseFilter parameter that was traditionally used only with ResponseMode.GET_FIRST, for remote get commands. In that particular case, returning a null when some of the nodes timed out and other nodes returned invalid responses (i.e. null) was acceptable.

      Since ISPN-4979, JGroupsTransport.invokeRemotelyAsync() is also used by ClusterTopologyManagerImpl, with ResponseMode.GET_ALL. Here, however, returning a null instead of throwing a TimeoutException is not acceptable.

      Attachments

        Issue Links

          Activity

            People

              dberinde@redhat.com Dan Berindei
              rhn-support-bmaxwell Brad Maxwell
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: