EJBCLIENT000015: Initial module availability report for Remoting connection EJB receiver in JBoss EAP 7 / 6
Environment
- Red Hat JBoss Enterprise Application Platform (EAP)
- 7.0
- 6.4
Issue
- We are seeing this info message logged in the client server.log :
INFO EJBCLIENT000015: Initial module availability report for Remoting connection EJB receiver [connection=org.jboss.ejb.client.remoting.ConnectionPool$PooledConnection@a170a7,channel=jboss.ejb,nodename=myserver] wasn't received during the receiver context association
Resolution
This message indicates that the client connected to the server and requested the module availability report, which is a report of the EJBs hosts on the server that the client can call. The client waited a few seconds to get the response from the server, but did not receive the response in the allotted time and then stopped blocking and proceeded to start. The module availability report when received would be updated in the client's configuration. The ejb client library waits / blocks for the time to wait for the report to prevent any clients that are trying to immediately call a remote ejb to succeed. If the client tries to call a remote ejb and the module availability report has not been received, then the client will get EJBCLIENT000025: No EJB receiver available for handling error.
JBoss EAP 7.0
Since the connection has been established, you can set this to a large value, because it will eventually succeed as the connection exists. The value is in seconds.
-Dorg.jboss.ejb.initial-module-wait-time=3600
JBoss EAP 6.x
See This content is not included.BZ1580975
Related solutions:
How to configure timeouts for remote EJBs invoking server under heavy load in JBoss EAP 7.0 / 6.4
This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.