This will, it seems, be fixed in 1.9.
ISTR that this exception occurs after the client has "disconnected" (quotes because this is TFTP, which is based on UDP) so it doesn't cause any operational failures. It's an ugly thing, and a distraction, but ultimately it can be ignored.
This will, it seems, be fixed in 1.9.
ISTR that this exception occurs after the client has "disconnected" (quotes because this is TFTP, which is based on UDP) so it doesn't cause any operational failures. It's an ugly thing, and a distraction, but ultimately it can be ignored.