I have analysed the problem a little bit more and I found out that the problem occurs by entity beans with more than 62 attributes/columns. The SELECT statement only contains the first 62 columns of the entity. Calling the getters of the 63 attribute/column an new (incorrect) SELECT statment is created that contains no columns.
Is this a configuration problem?
Its a known problem, that I think has been fixed in CVS