entity bean is not consistent with database.

[alpago]

Hi,

I have more than 15 entity beans and almost 300 junit test cases to test the business logic. Everything had seemed fine until I wanted to run multi-threaded tests against the application to see how it performs. It sucked! The problem was I didn't marked getter methods as read-only so concurrency didn't occur. Therefore, I marked all of my getter methods as read-only and all of my multi-threaded tests worked too. So far so good. However, when I tried my standard junit tests, I was surprised to see they were half broken..! There was no code change or whatsoever.

I am using commit-option B. I also tried using C but it didn't help either.

Does anyone know if there is a "tricky" setting that we should turn on/off when we use read-only methods ?

Cheers,

Alp

PS: I am not talking about signing the whole entity bean as read only. I selectively set only getter methods as read-only.

[alpago]

Hi all,

I found a way around it however I don't know if it is the right solution. Here is what I did. I used to have default capacity values for my container. I set both min and max values to 1 forcing "no-caching" (as I said, I didn't get expected behavior using commit-option C).

<container-cache-conf>
<cache-policy>org.jboss.ejb.plugins.LRUEnterpriseContextCachePolicy</cache-policy>
<cache-policy-conf>
<!-- ALP <min-capacity>50</min-capacity>
<max-capacity>1000000</max-capacity> -->
<min-capacity>1</min-capacity>
<max-capacity>1</max-capacity>
<overager-period>300</overager-period>
<max-bean-age>600</max-bean-age>
<resizer-period>400</resizer-period>
<max-cache-miss-period>60</max-cache-miss-period>
<min-cache-miss-period>1</min-cache-miss-period>
<cache-load-factor>0.75</cache-load-factor>
</cache-policy-conf>
</container-cache-conf>


So I got my unit test working happily again however, I haven't run any performance tests yet. Probably this solution will suffer in terms of performance.

I would appreciate any insight opinions from JBoss Guru's.

Cheers,

Alp

[vickyk]

Hi,
What <locking-policy> are you using in the configuration?
Regards

[alpago]

Hi Vickyk,

I am using the following:

<locking-policy>org.jboss.ejb.plugins.lock.QueuedPessimisticEJBLock</locking-policy>

Thanks

[erik777]

What version of JBoss are you using?

[alpago]

I am using jboss-3.0.4_tomcat-4.0.6. (I can not use the most recent one because of a bug ).

[alpago]

I am using jboss-3.0.4_tomcat-4.0.6. I can not use the most recent one because of a bug.

[alpago]

I am using jboss-3.0.4_tomcat-4.0.6 . I can not use the most recent one because of a bug.

[alpago]

I am using jboss-3.0.4_tomcat-4.0.6. I can not use the most recent one because of a bug.