eager-load-group for CMR doesn't work

[tbech]

JBoss 3.2.6, default setting in standardjbosscmp-jdbc.xml, commit option A used.
I observed strange selects for two applications. There is relation A -> many B (unidirectional).

a.getBs() gives select:
SELECT LOID FROM B WHERE (A_FK=?)

and now every entity B is access by fields, it gives:
SELECT LOID, field1 FROM B WHERE (LOID=?) OR (LOID=?) OR (LOID=?) OR (LOID=?) OR ...

SELECT LOID, field2 FROM B WHERE (LOID=?) OR (LOID=?) OR (LOID=?) OR (LOID=?) OR ...

and so on for every field. So obviously read-ahead works and eager-load-group doesn't (no overrried of eager group, using defaul * )

Even to be sure I tried to set read-ahead for relation:
<ejb-relation>
<ejb-relation-name>A2Bs</ejb-relation-name>
<ejb-relationship-role>
<ejb-relationship-role-name>A2Bs:A</ejb-relationship-role-name>
<key-fields>
<key-field>
<field-name>loid</field-name>
<column-name>A_FK</column-name>
<jdbc-type>INTEGER</jdbc-type>
<sql-type>INTEGER</sql-type>
</key-field>
</key-fields>

<read-ahead>
on-load
<eager-load-group>*</eager-load-group>
</read-ahead>
</ejb-relationship-role>
<ejb-relationship-role>
<ejb-relationship-role-name>A2Bs:Bs</ejb-relationship-role-name>
<fk-constraint>true</fk-constraint>
<key-fields/>

</ejb-relationship-role>
</ejb-relation>


I didn't change the behaviour.
(by the way loading of main entity A is ok, eager load works properly in this case)
So could someone explain me what is wrong, and how to make it right?
(no clues on wiki and jira)

[tbech]

Could someone confirm if it is normal behaviour or bug or my wrong configuration?!?
It really kills performance.

[triathlon98]

I am having the same problematic behaviour in JBoss 4.0.2. In fact, I have the impression that it worked in earlier versions. If only I knew for sure when it worked...

Joachim

[alt_amit]

make sure you are in a transaction with "Required" attribute setting. Also dont use the EJBQLToSQL92DCompiler in deploy desc.

If that doesnt work, try CMR left join read ahead feature. that definitely works. basically get your B attrs when you get your A's into the global cache. use 3.2.7, not 3.2.6 that has some relevant bug fixes.

[tbech]

make sure you are in a transaction with "Required" attribute setting

i've checked and it is 'required'.

Also dont use the EJBQLToSQL92DCompiler in deploy desc.

Not used

As triathlon98 says, it is similar in 4.0.2 so probably 3.2.7 also. And I have 100+ beans, it is too painfull to make CMR left join read ahead, and IMO such simple CMR as it is now should work :)

[tbech]

I've checked 3.2.7 - the same situation.
I think it is time to issue bug.