If we didn't check any dirty flag you would not be able to
update the data.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Boulatian, Misak
Sent: Saturday, January 17, 2004 2:38 AM
To: [EMAIL PROTECTED]
Subject: RE: [JBoss-user] JBoss 3.2.3 commit option B or C a lot slower than JBoss 3.2.1There are some bugs in JBoss 3.2.1 that forced us move to 3.2.3. For example, in commit option C we would get warning 'unable to return to the pool due to ctx lock' every time that type of bean was being used. There was also another bug using version control attribute: cmp field could not be specified as a version control attribute that did not work with us. It seems like wecannot use JBoss 3.2.1 anymore because of these bugs so I cannot really prove if CMP 1.1 is faster than CMP 2.0 but I know that 'modified' flag helped us minimize database synchs. How is it done in CMP 2.0? From the traces I can tell that JBoss does not check any dirty flag.It seems like we are kind of stuck, don't know how to configure JBoss running with cluster. None of the options like cache invalidation with commit option A, regular cluster configuration, or even using commit option C without cluster with row level locking in DB, give us normal speed to go to production.
