Along with having the bug karma, i have the opportunity to learn a lot !
This section discusses the change of the RMI connection port from JBoss AS 1.7 and WildFly 10.0.
Let’s take for example the JNDI properties file set in the client of an EJB
java.naming.factory.url.pkgs=org.jboss.ejb.client.naming java.naming.factory.initial=org.jboss.naming.remote.client.InitialContextFactory java.naming.provider.url=http-remoting://localhost:4447 jboss.naming.client.ejb.context=true jboss.naming.client.connect.options.org.xnio.Options.SASL_POLICY_NOPLAINTEXT =false
You can also have the same declaration by extending the configuration via ClientContext.
When running the client, this error shows up.
Exception in thread "main" javax.naming.CommunicationException: Failed to connect to any server. Servers tried: [remote://localhost:4447 (java.net.ConnectException: Connection refused ......
Actually, the resulotion is simple. Just change the provider URL, in our case, java.naming.provider.url=http-remoting://localhost:4447 with
changes in this release. For more reading about the Bug Karma, please refer to Bug Karma.
http-remoting://localhost:8080 For more reading about the bug fixes in JBoss, refer to