Utkarsh Srivastava updated ZOOKEEPER-504:

    Affects Version/s: 3.2.0
               Status: Patch Available  (was: Open)

The case that reproduces all these problem is when a client tries to open a 
ledger that has not been properly closed.

After fixing the original classcast problem and chasing further, ran into 
couple more issues. Attaching the patch for 3 problems that we found. Still 
cant get the case to work as we get a ZK error in the asyncOpen callback, 

> 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
> 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