If the client use authentication and the passwords is really long, the SASL request or kerberos ticket is huge the attempt will fail.
In the same environment authentication for other users work correct.
The shown message within the server log is
TRACE [org.jboss.remoting.remote.connection handleEvent] (Remoting "gravity" read-1) Connection error detail: java.io.IOException: Received an invalid message length of 11857
at org.xnio.channels.FramedMessageChannel.receive(FramedMessageChannel.java:106) [xnio-api-3.0.15.GA.jar:3.0.15.GA]
at org.jboss.remoting3.remote.ServerConnectionOpenListener$Initial.handleEvent(ServerConnectionOpenListener.java:229) [jboss-remoting-3.3.6.Final.jar:3.3.6.Final]
- causes
-
REM3-318 RemotingMessageChannel, invalid return value when reading length
- Resolved
-
JBEAP-10156 [GSS](7.0.z) Authentication via remoting fail for larger requests i.e. long password
- Closed
- is cloned by
-
JBEAP-8476 [GSS](7.1.0) Authentication via remoting fail for larger requests i.e. long password
- Closed
- is related to
-
REM3-310 Rework REM3-259 to fix synchronization issue
- Resolved