Hadoop QA commented on ZOOKEEPER-504:

-1 overall.  Here are the results of testing the latest attachment 
  against trunk revision 808557.

    +1 @author.  The patch does not contain any @author tags.

    -1 tests included.  The patch doesn't appear to include any new or modified 
                        Please justify why no tests are needed for this patch.

    +1 javadoc.  The javadoc tool did not generate any warning messages.

    +1 javac.  The applied patch does not increase the total number of javac 
compiler warnings.

    +1 findbugs.  The patch does not introduce any new Findbugs warnings.

    +1 release audit.  The applied patch does not increase the total number of 
release audit warnings.

    -1 core tests.  The patch failed core unit tests.

    +1 contrib tests.  The patch passed contrib unit tests.

Test results: 
Findbugs warnings: 
Console output: 

This message is automatically generated.

> ClassCastException in LedgerManagementProcessor
> -----------------------------------------------
>                 Key: ZOOKEEPER-504
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-504
>             Project: Zookeeper
>          Issue Type: Bug
>          Components: contrib-bookkeeper
>    Affects Versions: 3.2.0
>            Reporter: Utkarsh Srivastava
>            Assignee: Utkarsh Srivastava
>             Fix For: 3.3.0
>         Attachments: ZOOKEEPER-504.1.patch, ZOOKEEPER-504.patch, 
> ZOOKEEPER-504.patch
> java.lang.ClassCastException: 
> org.apache.bookkeeper.client.LedgerManagementProcessor$OpenLedgerOp cannot be 
> cast to org.apache.bookkeeper.client.LedgerManagementProcessor$CloseLedgerOp
>       at 
> org.apache.bookkeeper.client.LedgerManagementProcessor.processResult(LedgerManagementProcessor.java:1083)
> This seems to be happening because its a nested switch case statement. And 
> the OPEN: case, doesn't ever call a break. It only calls a break from the 
> inner switch-case and hence falls through into the CLOSE: case.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

Reply via email to