As Michael points out, this is bug 515597, which has been fixed on the 2.1 branch already, and should be part of 2.1.0 final (even if there are no further release candidates).
As Michael points out, this is bug 515597, which has been fixed on the 2.1 branch already, and should be part of 2.1.0 final (even if there are no further release candidates).