Migration from JBOSS EAP 6.4 to Wildfly 21 and onwards

Posted on

We are working on tech refresh of application and server. We are upgrading server and application to below versions:

Application server:

JBOSS EAP 6.4 to (upto) Wildfly 23.0.2


Apache Camel: 2.14.1 to 3.14.3

Spring: 3.2.11.RELEASE to 5.3.19

Spring Security: 3.1.7.RELEASE to 5.6.3

We are able to deploy and test application with above upgraded dependency on wildfly-18.0.1.Final and wildfly-20.0.1.Final but the same application not working from wildfly 21.0.0 onwards.

There is no error in the server log and socket timeout observed in SOAP UI log for wildfly 21 to wildfly 23.

But below error is observed for wildfly-24.0.1.Final onwards:

08:38:16,616 ERROR [org.jboss.as.ejb3.invocation] (default task-2) WFLYEJB0527: Remoting connector (address *****/, port 4447) is not correctly configured for EJB client invocations, the connector must be listed in <remote/>

We have one EJB module deployed on the same JVM and application tries to connect as remoting component with EJB module which is available on port 4447.

Remoting port 4447 is not enabled in wildfly by default, so it’s enabled with below steps



After googling we tried to add below dependency in pom.xml instead of jboss-remote-naming dependency





JNDI template is registered as below:

         <property name="environment">


                       <prop key="java.naming.factory.initial">org.jboss.naming.remote.client.InitialContextFactory


                       <prop key="java.naming.provider.url">remote://localhost:4447</prop>

                       <prop key="java.naming.factory.url.pkgs">org.jboss.naming</prop>




Tried to change java.naming.factory.initial org.wildfly.naming.client.WildFlyInitialContextFactory but still not working.

We tried to enable spring security debugging and org.wildfly.security to trace but there is no clue what is going wrong.

Any help is appreciated. Thank you in advance!!