[
https://issues.jboss.org/browse/WFLY-10150?page=com.atlassian.jira.plugin...
]
Panagiotis Sotiropoulos commented on WFLY-10150:
------------------------------------------------
Another configuration overcome of this issue (when there are larger than expected bursts
of requests and the max threads are not set to a suitable value) could be using
invocation-timeout param in jboss-ejb-client.xml. If a large enough value is set then
there could be no expiration. In case of expiration the request is repeated.
EJB race condition can cause client to be in awaitResponse while
server is done
-------------------------------------------------------------------------------
Key: WFLY-10150
URL:
https://issues.jboss.org/browse/WFLY-10150
Project: WildFly
Issue Type: Bug
Components: EJB
Reporter: Lin Gao
Labels: downstream_dependency
With a client jboss server1 that has a client servlet that invokes a remote EJB on jboss
server2 configured using server to server config in the standalone.xml/domain.xml outbound
remoting connection, the client side can get stuck in awaitResponse while the server side
has finished processing.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)