-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
31.0.1.Final
-
None
-
-
Migration
-
Workaround Exists
-
-
---
-
---
In our enterprise application we have a problem with the JNDI lookup of a secured EJB that causes the client to freeze if credentials are wrong.
If the JNDI lookup is performed with incorrect credentials, we usually get following exception on client side:
javax.naming.CommunicationException: WFNAM00018: Failed to connect to remote host [Root exception is javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed: PLAIN: javax.security.sasl.SaslException: PLAIN: Server rejected authentication] at org.wildfly.naming.client.remote.RemoteNamingProvider.getPeerIdentityForNaming(RemoteNamingProvider.java:110) at org.wildfly.naming.client.remote.RemoteNamingProvider.getPeerIdentityForNaming(RemoteNamingProvider.java:53) ...
-> This is the expected behavior.
But in our constellation (SSL communication + jdbc-realm (-> see standalone.xml), Wildfly 31), there's no exception, just a freeze on the client side.
The problem seems to be related to 'JBoss Remoting version 5.0.28.Final':
If we use a version below 30 for dependency 'wildfly-client-all' in the pom.xml of attached mavend project, everythings works as expected -> we get a SaslException each try and the client doesn't get stuck (in this case it shows 'JBoss Remoting version 5.0.27.Final'). If we use version 30 or higher ('JBoss Remoting version 5.0.28.Final'), we observe the above described issue.