[
https://issues.apache.org/jira/browse/DIRKRB-170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14502926#comment-14502926
]
Colm O hEigeartaigh commented on DIRKRB-170:
--------------------------------------------
I ran into a scenario where the DefaultKdcHandler enters an infinite loop of:
java.io.EOFException
at java.io.DataInputStream.readInt(DataInputStream.java:392)
at
org.apache.kerby.kerberos.kerb.transport.KrbTcpTransport.receiveMessage(KrbTcpTransport.java:54)
at
org.apache.kerby.kerberos.kerb.server.impl.DefaultKdcHandler.run(DefaultKdcHandler.java:43)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Transport or decoding error occurrednull
> Kdc server will throw exceptions when a client closed
> -----------------------------------------------------
>
> Key: DIRKRB-170
> URL: https://issues.apache.org/jira/browse/DIRKRB-170
> Project: Directory Kerberos
> Issue Type: Improvement
> Reporter: Lin Chen
> Assignee: Kai Zheng
>
> When a client was closed, the kdc server will throw many exceptions
> constantly. Such as IOException: An existing connection was forcibly closed
> by the remote host.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
