CA Gen 8.6 EJB under WildFly 10.1 fails with "EJBCLIENT000025: No EJB receiver available ..."

Document ID : KB000130209
Last Modified Date : 28/03/2019
Show Technical Document Details
Issue:
CA Gen 8.6 Web client and EJB successfully deployed to the same WildFly 10.1 instance in a single ear file.
When the Web client calls the EJB server it fails with error:

TIRM158E: A communication error was encountered on the client 
[Function: EJBRMIDynamicCoopFlow.processException.EJBRMI.Exception]java.lang.IllegalStateException: 
EJBCLIENT000025: No EJB receiver available for handling [appName:, ModuleName: xxxxxxxx, distinctName:]... 
Environment:
CA Gen 8.6. WildFly10.1 support PTFs installed
Cause:
The commcfg.properties file has been included from the CA Gen installation directory (%GEN86%\Gen, default: C:\Program Files (x86)\CA\Gen86\Gen) using Build Tool Assemble step "Include optional runtime property files". That file contains an incorrect trancode mapping for calling the Gen EJB server manager.
Resolution:
To call a local EJB under same WildFly instance this syntax should be used in the commcfg.properties file:
<server trancode>=EJBRMI W <ear_filename>
<server trancode> = Server  Manager trancode or alternatively a wildcard '*' e.g. *=EJBRMI W <ear_filename>
<ear_filename> =  name of the ear file deployed to WildFly (NOTE: the .ear extension should not be included)
Additional Information:
Gen 8.6 > Distributed Processing > Working With Distributed Processing > Overriding Communications Support at Execution Time:
https://docops.ca.com/ca-gen/8-6/en/distributed-processing/working-with-distributed-processing/overriding-communications-support-at-execution-time