[Design of JBossCache] - org.jboss.cache.lock.TimeoutException in write / read intens
by inrusu
Hi there,
Trying my luck with JBossCache 1.4.1.SP1 on a Websphere 6.1.0.3 cluster with 2 nodes each node with 1 server. The OS on both machines is
Windows XP Professional SP2.
I'm using the replSync-service.xml configuration file supplied in download ( etc\META-INF folder ). I've changed only the
cache mode to INVALIDATION_SYNC because I need the sync happen sync and REPL_SYNC was too slow.
I'm running some tests which do both cache read / write I'm getting lots of org.jboss.cache.lock.TimeoutException
when acquiring locks.
The scenario in which the TimeOut occurs is the following :
All the operations occur on a TreeCache with one node with one entry only in the node:
in Node1 modify a node
- the invalidation msg is snd
in Node2 the WL is acquired by a user thread
- the invalidation msg is rcv
- the JGroups thread tries to put a WL and fails with a time out which is send to Node1
..... and this keeps going on.
What are the recomandations in this situations ( indeed this is an extrem situations with some many updates on the same entry ):
1. increase the timeout period ( the current one is zero )
2. use optimistic locking ( how can I configure it ?)
3. other ?
Thanks
Ionut RUSU
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4017565#4017565
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4017565
19 years, 1 month
[Design of Messaging on JBoss (Messaging/JBoss)] - Full smoke test suite passing with future CR1
by ovidiu.feodorov@jboss.com
All our smoke tests pass (scroll down, it seems there's a bug in rendering html tables)
<h1>JBoss Messaging Smoke Test Results</h1>
Java version: 1.4.2_12
Run on: Fri Feb 16 02:07:52 PST 2007<h2>Installation Test Results</h2>
queuetopichttpsecure-socketmdbmdb-failurestatelessdistributed-queuedistributed-topicqueue-failover
4.0.1sp1 (scoped, not clustered)OK OK OK OK OK OK
4.0.1sp1 (scoped, CLUSTERED)OK OK OK
OK OK OK
OK OK OK
4.0.2 (scoped, not clustered)
OK
OK
OK
OK
OK
OK
4.0.2 (scoped, CLUSTERED)
OK
OK
OK
OK
OK
OK
OK
OK
OK
4.0.3 (scoped, not clustered)
OK
OK
OK
OK
OK
OK
4.0.3 (scoped, installer generated, not clustered)
OK
OK
OK
OK
OK
OK
4.0.3 (scoped, CLUSTERED)
OK
OK
OK
OK
OK
OK
OK
OK
OK
4.0.3 (scoped, installer generated, CLUSTERED)
OK
OK
OK
OK
OK
OK
OK
OK
OK
4.0.3SP1 (scoped, not clustered)
OK
OK
OK
OK
OK
OK
4.0.3SP1 (scoped, installer generated, not clustered)
OK
OK
OK
OK
OK
OK
4.0.3SP1 (scoped, CLUSTERED)
OK
OK
OK
OK
OK
OK
OK
OK
OK
4.0.3SP1 (scoped, installer generated, CLUSTERED)
OK
OK
OK
OK
OK
OK
OK
OK
OK
4.0.4.GA (scoped, not clustered)
OK
OK
OK
OK
OK
OK
OK
4.0.4.GA (scoped, installer generated, not clustered)
OK
OK
OK
OK
OK
OK
OK
4.0.4.GA (standalone, not clustered)
OK
OK
OK
4.0.4.GA (scoped, CLUSTERED)
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
4.0.4.GA (scoped, installer generated, CLUSTERED)
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
4.0.4.GA (standalone, CLUSTERED)
OK
OK
OK
OK
OK
OK
4.0.5.GA (scoped, not clustered)
OK
OK
OK
OK
OK
OK
OK
4.0.5.GA (scoped, installer generated, not clustered)
OK
OK
OK
OK
OK
OK
OK
4.0.5.GA (standalone, not clustered)
OK
OK
OK
4.0.5.GA (scoped, CLUSTERED)
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
4.0.5.GA (scoped, installer generated, CLUSTERED)OK OK OK OK OK OK OK OK OK OK
4.0.5.GA (standalone, CLUSTERED)
OK OK OK OK
OK OK
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4017532#4017532
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4017532
19 years, 1 month
[Design of JBoss internal QA (Test Suite)] - testcases overwritten
by akostadinov
See http://jira.jboss.com/jira/browse/JBAS-4103 for descripttion of the problem.
Any ideas how to fix? Should we rename testcases run by all but tests-standard-unit target?
Below is what I found about it for 4.0 branch (there could be some more not caught here):
1. cat tests.log | grep "\[junit\] Running" | sed -e 's/.\+ Running
\(.\+\)/\1/' | sort | uniq -d > tests.log.dup
2. sed -e 's/.\+nowrap.\+href="\(.\+\)\.html".\+/\1/p' -e 'd'
reports/allclasses-frame.html | sed -e 'y/\//./' > tests.log.report
3. cat tests.log.* | sort | uniq -d
I get these (45 total):
org.jboss.test.bmp.test.BmpUnitTestCase
org.jboss.test.bmp.test.SmallCacheBmpUnitTestCase
org.jboss.test.cmp2.ageout.test.JDBC2PmAgeOutUnitTestCase
org.jboss.test.cmp2.audit.test.AuditUnitTestCase
org.jboss.test.cmp2.batchcascadedelete.test.BatchCascadeDeleteUnitTestCase
org.jboss.test.cmp2.cacheinvalidation.test.CacheInvalidationUnitTestCase
org.jboss.test.cmp2.cacheinvalidation.test.JDBC2PmCacheInvalidationUnitTestCase
org.jboss.test.cmp2.cmrstress.CMRStressTestCase
org.jboss.test.cmp2.cmr.test.CMRPostCreatesWrittenUnitTestCase
org.jboss.test.cmp2.cmrtransaction.test.CMRTransactionUnitTestCase
org.jboss.test.cmp2.cmrtree.test.CascadeDeleteUnitTestCase
org.jboss.test.cmp2.commerce.CompleteUnitTestCase
org.jboss.test.cmp2.dbschema.relationship.RelationshipSchemaUnitTestCase
org.jboss.test.cmp2.distinct.DistinctUnitTestCase
org.jboss.test.cmp2.ejbselect.EJBSelectUnitTestCase
org.jboss.test.cmp2.ejbselect.JDBC2PmEJBSelectUnitTestCase
org.jboss.test.cmp2.enums.test.EnumUnitTestCase
org.jboss.test.cmp2.enums.test.JDBC2PmEnumUnitTestCase
org.jboss.test.cmp2.fkmapping.test.FKMappingUnitTestCase
org.jboss.test.cmp2.fkstackoverflow.test.FKStackOverflowUnitTestCase
org.jboss.test.cmp2.idxandusersql.test.IdxAndUsersqlUnitTestCase
org.jboss.test.cmp2.jbas1361.JBAS1361UnitTestCase
org.jboss.test.cmp2.jbas1665.JBAS1665UnitTestCase
org.jboss.test.cmp2.jbas3541.JBAS3541UnitTestCase
org.jboss.test.cmp2.jbas3541.JDBC2PmJBAS3541UnitTestCase
org.jboss.test.cmp2.jbas3717.JBAS3717UnitTestCase
org.jboss.test.cmp2.jbas979.JBAS979UnitTestCase
org.jboss.test.cmp2.keygen.test.KeyGenerationUnitTestCase
org.jboss.test.cmp2.lob.LOBUnitTestCase
org.jboss.test.cmp2.optimisticlock.test.OptimisticLockUnitTestCase
org.jboss.test.cmp2.partitionindex.PartitionIndexUnitTestCase
org.jboss.test.cmp2.passivation.test.EntityPassivationUnitTestCase
org.jboss.test.cmp2.perf.test.PerfUnitTestCase
org.jboss.test.cmp2.readonly.ReadonlyUnitTestCase
org.jboss.test.cmp2.relationship.RelationshipUnitTestCase
org.jboss.test.cmp2.simple.PageSizeUnitTestCase
org.jboss.test.cmp2.simple.SimpleUnitTestCase
org.jboss.test.jacc.test.external.AuthzDelegationUnitTestCase
org.jboss.test.jmx.test.RMIAdaptorAuthorizationUnitTestCase
org.jboss.test.security.test.auth.AppCallbackHandlerUnitTestCase
org.jboss.test.testbean.test.BeanUnitTestCase
org.jboss.test.testbyvalue.test.ByValueUnitTestCase
org.jboss.test.webservice.jbws309.JBWS309TestCase
org.jboss.test.web.test.FormAuthUnitTestCase
org.jboss.test.web.test.UserInRoleUnitTestCase
-----------------------------------------------------------------------------------------
Below I what Jarek found about 4.0.5.GA_CP status:
tests.log:
number of test cases:
grep "Running" tests.log|wc -l
730
number of tests:
grep "Tests run" tests.log|awk '{print $4}'|awk -F, '{sum+=$1} END {print sum}'
4182
html log:
number of test cases:
726 (4 test cases lost)
number of tests:
4167 (15 tests lost)
These tests are run twice, but I get only one report:
org.jboss.test.jmx.test.RMIAdaptorAuthorizationUnitTestCase (2 tests)
org.jboss.test.security.test.auth.AppCallbackHandlerUnitTestCase (3
tests)
This test is run five times, but only three reports:
org.jboss.test.webservice.jbws309.JBWS309TestCase (5 tests)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4017514#4017514
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4017514
19 years, 1 month