1 Reply Latest reply on Sep 9, 2019 7:04 AM by Evgeny Meerson

    Upgrade Wildfy 10 to Wildfly 17 ejb connection problems

    Evgeny Meerson Newbie

      Hi All

       

      We are using Wildfly 10 and I try to upgrade to Wildfly 17.

      Environment contains: GUI, Server and Online.

      GUI machine can connect to one Server, Server can connect to many Onlines (Online Servers can be added dynamically)

       

      Now I success to connect from GUI to Server.

       

      The problem:

      When server tries to connect to Online it every time connects to itself. It's look likes it ignore Context.PROVIDER_URL property.

       

      InitialContext is created programatically

      "java.naming.factory.initial" -> "org.wildfly.naming.client.WildFlyInitialContextFactory"

      "java.naming.provider.url" -> "remote+http://kuku:8080"

      "java.naming.security.principal" -> "user"

      "java.naming.security.credentials" -> "password"

       

      <dependency>

         <groupId>org.wildfly</groupId>

         <artifactId>wildfly-ejb-client-bom</artifactId>

         <version>${wildfly.version}</version>

         <type>pom</type>

         <scope>import</scope>

         </exclusions>

      </dependency>

       

      Can I change log level to display the problem?

       

      Thank you

      Evgeny

        • 1. Re: Upgrade Wildfy 10 to Wildfly 17 ejb connection problems
          Evgeny Meerson Newbie

          I found strange solution:

          I moved this code from (Server Side Operation Code) to Call other Bean  Code that call original code

           

          Previously (Wildfly 10) the Server Operation code call to Bean A , and code was working

           

          @Stateless
          @TransactionManagement(TransactionManagementType.BEAN)

          @Remote(A.class)

          public class A...

           

          In Wildfly 17 I call to code of bean A from Bean B, and call for bean B from same operation

           

          @Stateless
          @TransactionManagement(TransactionManagementType.CONTAINER)

          @Remote(B.class)

          public class B...

           

          And this operation was started working