[
https://issues.redhat.com/browse/WFLY-13871?page=com.atlassian.jira.plugi...
]
Richard Achmatowicz commented on WFLY-13871:
--------------------------------------------
[~jbaesner] I have updated the pull request. Could you please try this version out - I
have modified the initial module update so that it is only sent out of the server is not
suspended. I'm also assuming that deployments will not be processed if the server is
suspended, as that would require guarding all the other module update messages in a
similar way.
Re-implement correct suspend/resume behaviour for EJB client
------------------------------------------------------------
Key: WFLY-13871
URL:
https://issues.redhat.com/browse/WFLY-13871
Project: WildFly
Issue Type: Bug
Components: EJB
Affects Versions: 21.0.0.Beta1
Reporter: Richard Achmatowicz
Assignee: Richard Achmatowicz
Priority: Major
Fix For: 21.0.0.Beta1
When a server is suspended, in order to avoid receipt of invocations which will never be
correctly processed, all connected clients should be notified that all modules on that
server are now unavailable; when the server is resumed, all connected clients should be
notified that all modules on that server are now again available so that the server may
again take part in processing invocations.
This behaviour was present in versions of EAP before EAP 7.1 but was not ported over to
the new EJB client server-side classes which were substantially refactored.
This issue will re-instante that behaviour. The two cases of standalone and clustered
deployments should be considered.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)