[jboss-dev] configs are broken

Scott Stark sstark at redhat.com
Thu Nov 6 11:29:08 EST 2008


Running the profileservice tests with 
-Djboss.vfs.cache=org.jboss.virtual.plugins.cache.WeakRefVFSCache,
the seam test times are:
    [junit] Running 
org.jboss.test.deployers.seam.test.SeamBookingExampleUnitTestCase
    [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 24.436 sec
    [junit] Running 
org.jboss.test.deployers.seam.test.SeamDvdExampleUnitTestCase
    [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 16.696 sec
    [junit] Test 
org.jboss.test.deployers.seam.test.SeamDvdExampleUnitTestCase FAILED
    [junit] Running 
org.jboss.test.deployers.seam.test.SeamJpaExampleUnitTestCase
    [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 11.985 sec
    [junit] Running 
org.jboss.test.deployers.seam.test.SeamNumberguessExampleUnitTestCase
    [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 9.289 sec
    [junit] Running 
org.jboss.test.deployers.seam.test.SeamVFSClassloadingUnitTestCase
    [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 44.541 sec
...
Total time: 6 minutes 37 seconds

with -Djboss.vfs.cache=org.jboss.virtual.plugins.cache.TimedVFSCache
the seam test times are:
    [junit] Running 
org.jboss.test.deployers.seam.test.SeamBookingExampleUnitTestCase
    [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 17.681 sec
    [junit] Running 
org.jboss.test.deployers.seam.test.SeamDvdExampleUnitTestCase
    [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 15.061 sec
    [junit] Test 
org.jboss.test.deployers.seam.test.SeamDvdExampleUnitTestCase FAILED
    [junit] Running 
org.jboss.test.deployers.seam.test.SeamJpaExampleUnitTestCase
    [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 10.536 sec
    [junit] Running 
org.jboss.test.deployers.seam.test.SeamNumberguessExampleUnitTestCase
    [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 8.257 sec
    [junit] Running 
org.jboss.test.deployers.seam.test.SeamVFSClassloadingUnitTestCase
    [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 42.076 sec
...
Total time: 6 minutes 15 seconds

So the TimedVFSCache is a little better. Can't we add a 
VFSCacheFactory.getInstance(String defaultCache) so that the cache can 
be set in the initialize.xml rather than having to update every startup 
config to pass in a system property.


Stan Silvert wrote:
> Can we go ahead and make a decision on this?  It's holding up Seam 
> testing.
>
> Ales Justin wrote:
>> As we don't vote or go 'with it w/o reason' (Adrian's rules) ;-)
>> I'll explain a bit my options:
>>
>>>  - (1) + proper strong ref on this: 
>>> http://www.jboss.com/index.html?module=bb&op=viewtopic&t=145039
>>
>> We keep the most used one's via strong ref on VFSInitializer,
>> but let other temps be GCed asap.
>>
>>>  - (4) with limit long enough to do common apps deployment triggered 
>>> upon this cache
>>
>> We make the timed limit long enough that most of apps make advantage 
>> of this vfs cache,
>> once initialization period is over, flush it all.
>> _______________________________________________
>> jboss-development mailing list
>> jboss-development at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-development
>
> _______________________________________________
> jboss-development mailing list
> jboss-development at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development




More information about the jboss-development mailing list