Could you, please, try JBoss-3.2.0RC5 from cvs?
There were a lot of changes in the code since 3.2.0RC3

Thanks,
alex

Friday, April 04, 2003, 4:46:34 PM, you wrote:

CM> Hi all,

CM> I am using jboss3.2.0RC3, jdk1.3.1_06, database Hypersonic.
 
CM> My application description
CM> -BeanA and BeanB have a One to Many relationship (A has many of B)
CM> -pk1 is primary key of BeanA
CM> -pk1 and pk2 is the compound primary key of BeanB
CM> -pk2 in BeanB is also a foreign key which realizes the relation with BeanA
CM> -Primary key class of BeanA is PkClassA
CM> -Primary key class of BeanB is PkClassB
CM> -PkClassB inherits PkClassA
CM> -both beans are CMP
CM> -both beans have  <transaction-type>Container</transaction-type>
CM> -both beans have <trans-attribute>Required</trans-attribute> for all methods
 
CM> I think there is a bug in the cmr procedure which returns the collections of
CM> B related to A. 
CM> The bug is not sistematic and sometimes the getCmr procedure works properly.
 
 
CM> --Used configuration for both beans
CM> jbosscmp-jdbc.xml
CM>     <read-ahead> 
CM>     <strategy>none</strategy>
CM>     </read-ahead>
CM> jboss.xml
CM>     <container-configuration extends="Standard CMP 2.x EntityBean">
CM>     <container-name>Order Container</container-name>
CM>     <commit-option>C</commit-option>
CM>     </container-configuration>
 
CM> --Description of the problem
CM>     B1.remove()  //the B1 instance related to A is correctly deleted from B
CM> table on database 
CM>     A.getBs()   //returns a collection of Bs where the primary key of the B1
CM> removed instance is still present, and the code fails trying to read a bean
CM> with a not existing primaryKey 
CM> javax.ejb.NoSuchObjectLocalException: Entity not found: primaryKey=76 - 78
 
CM> It seems that the reference to the deleted instance is still present in the
CM> cache.
 
 
CM> Changing container type problem changes but still remains:
 
CM> --Used configuration for both beans
CM> jbosscmp-jdbc.xml
CM>     <read-ahead> 
CM>     <strategy>none</strategy>
CM>     </read-ahead>
CM> jboss.xml
CM>     <container-configuration extends="Instance Per Transaction CMP 2.x
EntityBean">>
CM>     <container-name>Order Container</container-name>
CM>     <commit-option>C</commit-option>
CM>     </container-configuration>
 
CM> --Description of the problem
CM> B1.remove();  //the B1 instance is correctly deleted from B table on
CM> database 
CM> collection = A.getBs(); //returns a collection of Bs where the removed
CM> instance is not anymore present
CM> while (iteration on the collection) {
CM>   Bx.setCmpField (value); //a cmp field for all remaining B instance related
CM> to A is set
CM> }
CM> field = Bx.getCmpField() // the field has a value different from the value
CM> set in the cycle
 
CM> It seems that the reference to the deleted instance is correctly not present
CM> in the returned collection but setCmp procedure of B does not update
CM> correctly a remaining B instance related to A.
 
 
CM> I have tried also other combination of commit option and container type but
CM> problem remains.

CM> Is it a known problem? 
CM> Any idea of configurations or work-around that can help?
 
 
CM> Thanks
CM> Morena
CM> e-mailto: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>



-------------------------------------------------------
This SF.net email is sponsored by: ValueWeb: 
Dedicated Hosting for just $79/mo with 500 GB of bandwidth! 
No other company gives more support or power for your dedicated server
http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to