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

[GSS](7.1.z) EJBCLIENT-309 - Connection to once failed nodes never reattempted in ejbclient-4.x

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • Individual Patches.GA
    • 7.1.6.GA
    • EJB
    • None
    • Hide

      Steps to reproduce:

      • having cluster of 2 nodes: nodeA and nodeB
      • having ejb-remote cluster client: clientNode
      • nodeB is disabled, nodeA started
      • start clientNode and make some ejb-remote calls (failedConnections in RemotingEJBDiscoveryProvider will be initialized with nodeB)
      • start nodeB
      • shutdown nodeA
      • make some more ejb-remote calls from clientNode

      Actual Result:

      all calls from ejb-remote node fails with "connection refused". RemotingEJBDiscoveryProvider not try to establish connection to nodeB

      Expected Result:

      ejb calls working. RemotingEJBDiscoveryProvider try to establish connection to nodeB

      Example patch to fix
      https://github.com/wildfly/jboss-ejb-client/pull/359/files

      Show
      Steps to reproduce: having cluster of 2 nodes: nodeA and nodeB having ejb-remote cluster client: clientNode nodeB is disabled, nodeA started start clientNode and make some ejb-remote calls (failedConnections in RemotingEJBDiscoveryProvider will be initialized with nodeB) start nodeB shutdown nodeA make some more ejb-remote calls from clientNode Actual Result: all calls from ejb-remote node fails with "connection refused". RemotingEJBDiscoveryProvider not try to establish connection to nodeB Expected Result: ejb calls working. RemotingEJBDiscoveryProvider try to establish connection to nodeB Example patch to fix https://github.com/wildfly/jboss-ejb-client/pull/359/files

            rhn-support-jbaesner Joerg Baesner
            rhn-support-jbaesner Joerg Baesner
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: