EJBCLIENT000014: Version handshake not completed for receiver context in JBoss EAP 7.0 / 6.4

Solution Unverified - Updated

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 7.0
    • 6.4

Issue

  • We are seeing EJBCLIENT000014 when trying to invoke a remote EJB in EAP 7.0 / 6.4
INFO  [org.jboss.ejb.client.remoting] (main) [-] EJBCLIENT000014: Version handshake not completed for receiver context EJBReceiverContext{clientContext=org.jboss.ejb.client.EJBClientContext@3b6c2be6, receiver=Remoting connection EJB receiver [connection=org.jboss.ejb.client.remoting.ConnectionPool$PooledConnection@25533bba,channel=jboss.ejb,nodename=standalone-dataserver]}. Closing receiver context

Resolution

Set the invocation.timeout property in the EJB client properties

Related solutions:

How to configure timeouts for remote EJBs invoking server under heavy load in JBoss EAP 7.0 / 6.4

Root Cause

There is a default 5 second timeout, the server / client are busy or there is a slow network and the client is unable to receive the version information from the server in the time and it logs EJBCLIENT000014. Setting the invocation.timeout will set the timeout for the invocation as well as the timeout for the version handshake.

SBR
Product(s)
Components
Category
Tags

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.