Remote EJB client reconnect after error.

[Will Cardenas]

Hello,

I'm running 5.183 and I have configured a deployment group of 3 EJB servers. InitialContext load balancing is working as expected in that I see calls being made to all instances in the deployment group.

The problem I'm having is if a client application has a reference to a remote EJB that it has been using and then server it is connected to goes down, the reference becomes useless by generating connection refused errors. Forcing a re-lookup of the EJB corrects the issue in that the InitialContext gives me a new reference to a different server but shouldn't this be handled automatically?

Are there additional configuration options that would provide for automatic reconnect or do I have to implement some sort of reconnect logic on all remote EJB method calls?

Thanks.

[Steve Millidge]

This should work. Any chance you can raise an Issue on GitHub and create a simple reproducer application?

Thanks

Steve