1 Reply Latest reply on Dec 27, 2002 9:00 AM by David Cowan

    duplicate Entries in CMR !

    wotan Newbie

      I am using Jboss 3.0.4 with jetty on Win2000 with SAPDB 7.4

      I have an Ejb Account and AccountEntry with:

      <ejb-relation >
      <ejb-relation-name>Account-AccountEntry</ejb-relation-name>

      <ejb-relationship-role >
      <ejb-relationship-role-name>AccountEntry-has-Account</ejb-relationship-role-name>
      Many
      <relationship-role-source >
      <ejb-name>AccountEntry</ejb-name>
      </relationship-role-source>
      <cmr-field >
      <cmr-field-name>account</cmr-field-name>
      </cmr-field>
      </ejb-relationship-role>

      <ejb-relationship-role >
      <ejb-relationship-role-name>Account-has-AccountEntries</ejb-relationship-role-name>
      One
      <relationship-role-source >
      <ejb-name>Account</ejb-name>
      </relationship-role-source>
      <cmr-field >
      <cmr-field-name>accountEntryList</cmr-field-name>
      <cmr-field-type>java.util.Collection</cmr-field-type>
      </cmr-field>
      </ejb-relationship-role>

      </ejb-relation>

      Normal behaviour if I:
      1. Start jboss
      2. display Account details (Account.getAccountEntryList())
      3. create a bunch of new AccountEntrys
      4. displaying Account details (Account.getAccountEntryList()) , the new and old Entrys are there only once

      abnormal behaviour if I:
      1. Start jboss
      2. create new AccountEntrys WITHOUT displaying old ones
      4. displaying Account details (Account.getAccountEntryList()) , the old Entries are displayed once and the new Entries are displayed TWICE !


      I am using Commit-Option "A".
      The log shows an SQL-Call with seems right, i.e.
      there are 27 Entries to select and the command has 27 "or (ACCOUNT_ENTRY_ID = ?) " fragments. But the Collection returned has more than 27 Entries !

        • 1. Re: duplicate Entries in CMR !
          David Cowan Newbie

          We are having much the same problem. With ours if you change to commit option B you will not see the problem. Until we have the time to track down what it is that is causing the problem we switched to commit option D with a timeout of 1 minute and the duplicates will dissapear after a minute. For us this only happens in CMR's not on just straight cmp entities.