Loading...

XML

Word

Printable

Steps to Reproduce:
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

is duplicated by

EJBCLIENT-337 Reconnect to failed configured node not possible, even if the node is up again

is incorporated by

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