[JBoss-user] [JBossCache] - Re: Problems with JBossCache
I am using the latest one: 1.2.3 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3891744#3891744 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3891744 --- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [JBossCache] - Problems with JBossCache
Hello, I've met the following problem using JBoss cache. My servlet works with 3 instances of JBoss cache for different purposes. It started on two different computers. When I was testing it I stopped and started application one by another. Afte several restarts I allways got error: Caused by: org.jboss.cache.lock.TimeoutException: rsp=sender=11.10.77.77:35744, retval=null, received=false, suspected=false at org.jboss.cache.TreeCache.callRemoteMethods(TreeCache.java:2205) at org.jboss.cache.TreeCache.callRemoteMethods(TreeCache.java:2227) at org.jboss.cache.interceptors.ReplicationInterceptor.handleReplicatedMethod(ReplicationInterceptor.java:120) at org.jboss.cache.interceptors.ReplicationInterceptor.invoke(ReplicationInterceptor.java:85) at org.jboss.cache.TreeCache.invokeMethod(TreeCache.java:3116) at org.jboss.cache.TreeCache.put(TreeCache.java:1687) at org.jboss.cache.TreeCache.put(TreeCache.java:1671) And this error occures after each invocation of put method. It looks like "deadlock" problem already described on this forum. The only way to stop exceptions is to stop both servers wait some time and to start them again. If both servers starts right away after stop then error doesnt disappear. So the questions: 1) Does JBossCache store its state somewhere (on the file system for example) by default? 2) Can we correctly detect that we have deadlock? 3) Can we fix it in runtime or even avoid it? Thanks in advance. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3891590#3891590 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3891590 --- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [JBossCache] - Re: State retrieval on startup fails when transaction is ope
It looks that InitialStateRetrievalTimeout = 0 property is not working. Distributed cache doesn't wait until tranasction commit on coordinator, it simply continue work with no data in cache. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3881920#3881920 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3881920 --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [JBossCache] - Re: State retrieval on startup fails when transaction is ope
It is a good advice, but result is not guaranteed. How I can be sure that the state in cache is correctly replicated? As I understand the cache replicates only changes, so if state replication fails on startup then it will never become up to date. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3881898#3881898 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3881898 --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [JBossCache] - State retrieval on startup fails when transaction is opened
Hello, I found the following problem with JBoss TreeCache in clustered environment. When cache starts it tries to retrieve it state from coordinator cache (FetchStateOnStartup = true), but in the case when transaction is opened on coordinator the retrieval fails with no notifcation except log message: "state could not be retrieved (must be first member in group)". Is it a bug? How can I check this failure in code? Here the cache properties: | | | | jboss:service=Naming | jboss:service=TransactionManager | org.jboss.cache.DummyTransactionManagerLookup |REPEATABLE_READ |REPL_SYNC |false |0 |0 |TreeCache-Cluster | | | | | | | | | | | | | | | | true | 5000 | 1 | 15000 | org.jboss.cache.eviction.LRUPolicy | | | 5 | | 5000 | 86400 | | | 10 | 30 | | | | | | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3881753#3881753 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3881753 --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
