On 11/11/2010 05:25 AM, mohan_zl (JIRA) wrote:
[ https://issues.apache.org/jira/browse/TS-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12931001#action_12931001 ]mohan_zl commented on TS-435: ----------------------------- we have reproduce this problem when using latest trunk, and looks like something messed during queue and handler match: [Sep 8 11:55:57.616] Server {3062635408} DEBUG: (dns) DNSHandler::startEvent_sdns: on thread2 [Sep 8 11:55:57.616] Server {3062635408} DEBUG: (dns) open_con: opening connection 10.2.1.73:53 [Sep 8 11:55:57.616] Server {3063688080} DEBUG: (dns) DNSHandler::startEvent_sdns: on thread1 [Sep 8 11:55:57.616] Server {3063688080} DEBUG: (dns) open_con: opening connection 10.2.1.73:53 [Sep 8 11:55:57.713] Server {3079767744} DEBUG: (dns) DNSHandler::startEvent: on thread0 [Sep 8 11:55:57.713] Server {3079767744} DEBUG: (dns) open_con: opening connection 10.2.1.73:53 we have 3 thread connected to 10.2.1.73:53 unknown DNS id = 50074 show then dns result is mistake by other threads, it took the dns result a unknown dns pkt, and dropped, so you can not resolve any dns will patch it asap
Cool. I have a few other minor DNS cleanups that I need to commit, should I just put that in there for this bug (It doesn't fix this problem, but makes things a bit cleaner).
-- leif
