Hi everyone, Can someone explain what I should do for this? I have a patch for both 3.4 and 3.3, and I think the 3.3 patch caused issues in the automated patch applier. What do I need to do to submit both of these patches to the different branches?
Thanks, Camille -----Original Message----- From: Camille Fournier (JIRA) [mailto:j...@apache.org] Sent: Thursday, September 16, 2010 2:25 PM To: zookeeper-dev@hadoop.apache.org Subject: [jira] Updated: (ZOOKEEPER-844) handle auth failure in java client [ https://issues.apache.org/jira/browse/ZOOKEEPER-844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Camille Fournier updated ZOOKEEPER-844: --------------------------------------- Attachment: (was: ZOOKEEPER332-844) > handle auth failure in java client > ---------------------------------- > > Key: ZOOKEEPER-844 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-844 > Project: Zookeeper > Issue Type: Bug > Components: java client > Affects Versions: 3.3.1 > Reporter: Camille Fournier > Assignee: Camille Fournier > Fix For: 3.3.2, 3.4.0 > > Attachments: ZOOKEEPER-844.patch > > > ClientCnxn.java currently has the following code: > if (replyHdr.getXid() == -4) { > // -2 is the xid for AuthPacket > // TODO: process AuthPacket here > if (LOG.isDebugEnabled()) { > LOG.debug("Got auth sessionid:0x" > + Long.toHexString(sessionId)); > } > return; > } > Auth failures appear to cause the server to disconnect but the client never > gets a proper state change or notification that auth has failed, which makes > handling this scenario very difficult as it causes the client to go into a > loop of sending bad auth, getting disconnected, trying to reconnect, sending > bad auth again, over and over. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.