1 Reply Latest reply on Apr 9, 2018 12:50 AM by Daniel Fb

    [SOLVED] Wildfly 12 - EJB invocations from remote servers under domain controller

    Daniel Fb Newbie



      I am following the instructions from this link: Getting started with EJBs and Elytron Part 2: EJB invocations from remote servers

      Trying to replicate those configurations under domain controller but without success.


      I have two server groups, one is client of other. But the servers of server group "B" still unable to lookup the remote EJB from servers of server group "A"

      I tried to configure the servers with jboss-cli.sh from domain controller. Applying the configurations at the corresponding profiles.



      From Domain Controller's jboss-cli.sh:

      1. /profile=my-custom-profile-full-ha/subsystem=elytron/authentication-configuration=ejb-auth-config:add(authentication-name=ejb, credential-reference={clear-text="ejbejb"}) 


      and so on...

      The socket-binding-group is defined at domain.xml as well.


      But my client server still getting errors when lookup the remote EJB.

      Is there other configuration for servers running under domain controller to get remote invocations work?


      The error:

      javax.ejb.NoSuchEJBException: EJBCLIENT000079: Unable to discover destination for request for EJB StatelessEJBLocator for "/portal/SampleEJB", view is interface my.company.ejb.interfaces.SampleEJBRemote, affinity is None



      Properties properties = new Properties();

      properties.put(Context.INITIAL_CONTEXT_FACTORY, "org.wildfly.naming.client.WildFlyInitialContextFactory");

      InitialContext context = new InitialContext(properties);

      SampleEJBRemote remote = (SampleEJBRemote) context.lookup("ejb:/portal/SampleEJB!my.company.ejb.interfaces.SampleEJBRemote");



        • 1. Re: Wildfly 12 - EJB invocations from remote servers under domain controller
          Daniel Fb Newbie



          I need to configure elytron subsystem with these configurations:




          looks like the PLAIN mechanism is what the missing.


          and set a system property (wildfly.config.url) pointing to wildfly-config.xml file:


               <authentication-client xmlns="urn:elytron:1.0">


                      <rule use-configuration="default"/>



                      <configuration name="default">

                          <set-user-name name="ejbuser"/>


                              <clear-password password="superPwd1!"/>


                          <sasl-mechanism-selector selector="PLAIN"/>


                              <use-service-loader />