[jboss-user] [JBoss Cache: Core Edition] - JBossCache - Persistence
Hi, Can I update the persistent store for synchronous with cache ? I have a cache which is a subset of another cache. All changes reflecting in the superset should get delegated to this subset cache. This way i'm trying to get a selective cache replication. Is this possible ? Please suggest your thoughts on this. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4173297#4173297 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4173297 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Cache: Core Edition] - Selective Distributed Cache loading
We have one master cache(A) and multiple small subset caches (B & C) which are subsets of the master cache(A). All these caches(A, B & C) are in different independent clusters. We want to load and distribute the changes from the master cache(A) into these smaller caches ( B & C). Changes(Modify or Delete) needs to be distributed based on the altered items from the master cache(A) to respective smaller caches(B & C). Is this achievable ? Please suggest your thoughts to achieve this kind of a selective distributed caching. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4182664#4182664 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4182664 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Cache: Core Edition] - Re: Selective Distributed Cache loading
Can you please reply on this topic ? Thanks in advance. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4183235#4183235 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4183235 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Cache: Core Edition] - FD Issue
We are using JBoss Cache 1.4.1 SP6 with JGroups 2.4.x We have a cluster of cache instances with two Sun Solaris and multiple RHEL machines. When one of the RHEL instance is restarted, the VIEW of the cache instances in SOLARIS machines aren't updated. i.e. viewAccepted() - Still has the old RHEL instance along with the new RHEL instance(which was restarted) eg: [172.16.11.200:65261, 172.16.11.12:50903, 172.16.11.10:41912, 172.16.11.20:51156, 172.16.11.10:43789, 172.16.11.20:57771, 172.16.11.10:51722, 172.16.11.20:35858, 172.16.11.11:51210] 172.16.11.10 - RHEL Instance 1 172.16.11.20 - RHEL Instance 2 Its assumed that when a cache instance goes down the view should be immediately when FD_SOCK is configured. But it wasn't updated as expected. Whereas the viewAccepted() was updated with active members and got resolved after some hours only. We got a ReplicationException timeout Received Throwable from remote node org.jboss.cache.ReplicationException: rsp=sender=172.16.11.10:41912, retval=null, received=false, suspected=false The code is as follows | | | | | | | | | | | | | | | | | >From the exception message we infer that 172.16.11.10:41912, this cache >instance has been restarted and the current active instance was >172.16.11.10:51722 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221191#4221191 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221191 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Cache: Core Edition] - Re: FD Issue
The added code was the sample so the IP(bind_addr) is different but all the other configuration is the same. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221195#4221195 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221195 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Cache: Core Edition] - Re: FD Issue
When one of the RHEL instance was brought down by killing the instance
forcefully (kill -9 {PID}), the VIEW in the SOLARIS machines aren't updated
even after testing with your suggestion.
The sample config is as follows
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Please suggest your thoughts in this.
Solaris and RHEL KEEP_ALIVE is with default(2hours) values
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221387#4221387
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221387
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Cache: Core Edition] - Re: FD Issue
YES. The viewAccepted in the SOLARIS machines still have the dead members after some hours also. How can these members be deleted from the VIEW ? Should we set any other value to resolve this ?? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221456#4221456 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221456 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Cache: Core Edition] - Re: FD Issue
One of the RHEL instances has detected the failure and has the following messages org.jgroups.protocols.FD --> [SUSPECT] suspect hdr is [FD: SUSPECT (suspected_mbrs=[xx.xx.xx.xx:xx)] org.jgroups.protocols.VERIFY_SUSPECT --> verifying that xx.xx.xx.xx is dead But this message is not updated to the coordinator(SOLARIS) instance, so the VIEW is still having the dead members. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221484#4221484 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221484 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Cache: Core Edition] - Re: FD Issue
We tested the same with JBoss Cache 1.4.1 SP8 with JGroups 2.4.1.SP8 but the problem still exists View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221971#4221971 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221971 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Cache: Core Edition] - Re: FD Issue
"karnivas" wrote : We tested the same with JBoss Cache 1.4.1 SP8 with JGroups 2.4.1.SP8 but the problem still exists We tested the same with JBoss Cache 1.4.1 SP8 with JGroups 2.4.1.SP4 but the problem still exists View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221972#4221972 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221972 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Cache: Core Edition] - Migration from 1.4.x to 2.x
I've been using JBossCache 1.4.x and wanted to migrate to 2.x. After going through the docs and guides I see there are many changes in the API. I've been using TreeCache.isCoordinator() and TreeCache.exists() consistently. I used the DefaultCacheFactory to create and start my cache. Based on these APIs many functionalities change in my application. 2.x is missing those APIs. 1. How can I identify whether a cache is a coordinator in 2.x ? 2. Which API should be used for cache.exists() ? Please advice what changes needs to be done for the same. If there is any guide which helps to use the new APIs replacing the deleted APIs please give the link. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201334#4201334 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201334 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Web Services Users] - HTTPRouter and Attachments
We are using jboss-soa-p.4.3.0 We are trying to send an attachment with the request through SOAP UI to a ESB Service which has Apache HTTP Router. SAXParseException - "Content not allowed in prolog" is been thrown. Why the HTTPRouter is throwing this exception ? Is there a way to set the Content-Type as TEXT ? Any thoughts might be helpful View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4255762#4255762 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4255762 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Cache: Core Edition] - Re: FD Issue
We brought down one of the SOLARIS machine(P1 - Co-ordinator) to check the view
in all machines.
As expected, the co-ordinator changed to one of the RHEL machine by removing
the P1 from all views, but the dead RHEL members wasn't updated in the VIEW
Please find the DEBUG messages of jgroups.log
org.jgroups.protocols.pbcast.GMS --> new=[172.16.11.200:32790], suspected=[],
leaving=[], new view: [172.16.11.20:35858|259] [172.16.11.20:35858,
172.16.11.11:51210, 172.16.11.191:37204, 172.16.11.10:51918,
172.16.11.12:40087, 172.16.11.13:38513, 172.16.11.13:38520, 172.16.11.13:38533,
172.16.11.200:32790]
| org.jgroups.protocols.pbcast.GMS --> mcasting view
{[172.16.11.20:35858|259] [172.16.11.20:35858, 172.16.11.11:51210,
172.16.11.191:37204, 172.16.11.10:51918, 172.16.11.12:40087,
172.16.11.13:38513, 172.16.11.13:38520, 172.16.11.13:38533,
172.16.11.200:32790]} (9 mbrs)
| org.jgroups.protocols.UDP --> sending msg to null (src=172.16.11.20:35858),
headers are {NAKACK=[MSG, seqno=3782], GMS= GmsHeader[VIEW]:
view=[172.16.11.20:35858|259] [172.16.11.20:35858, 172.16.11.11:51210,
172.16.11.191:37204, 172.16.11.10:51918, 172.16.11.12:40087,
172.16.11.13:38513, 172.16.11.13:38520, 172.16.11.13:38533,
172.16.11.200:32790], UDP =[channel_name=ProvCache-LABS]}
| org.jgroups.protocols.UDP --> message is [dst: 224.7.8.9:45567, src:
172.16.11.20:35858 (3 headers), size = 0 bytes], h eaders are
{GMS=GmsHeader[VIEW]: view=[172.16.11.20:35858|259] [172.16.11.20:35858,
172.16.11.11:51210, 172.16.11.191:37204, 172.16.11.10:51918, 17
2.16.11.12:40087, 172.16.11.13:38513, 172.16.11.13:38520, 172.16.11.13:38533,
172.16.11 .200:32790], NAKACK=[MSG, seqno=3782],
UDP=[channel_name=ProvCache-LABS]}
| org.jgroups.protocols.pbcast.GMS --> view=[172.16.11.20:35858|259]
[172.16.11.20:35858, 172.16.11.11:51210, 172.16.11.1 91:37204,
172.16.11.10:51918, 172.16.11.12:40087, 172.16.11.13:38513, 172.16.11.13:38520,
172.16.11.13:38533, 172.16.11.13:38538, 172.16.11.200:32790]
| org.jgroups.protocols.pbcast.GMS --> [local_addr=172.16.11.20:35858] view
is [172.16.11.20:35858|259] [172.16.11.20:358 58, 172.16.11.11:51210,
172.16.11.191:37204, 172.16.11.10:51918, 172.16.11.12:40087,
172.16.11.13:38513, 172.16.11.13:38520, 172.16.11.13:38533, 172.16.11.200:32790]
| org.jgroups.protocols.UDP --> message is [dst: 172.16.11.20:35858, src:
172.16.11.12:40087 (3 headers), size = 0 bytes], headers are
{GMS=GmsHeader[VIEW_ACK]: view=[172.16.11.20:35858|259] [172.16.11.20:35858,
172.16.11.11:51210, 172.16.11.191:37204, 172.16.11.10:51 918,
172.16.11.12:40087, 172.16.11.13:38513, 172.16.11.13:38520, 172.16.11.13:38533,
172.16.11.200:32790], UNICAST=[UNICAST: DATA, seqno=1],
UDP=[channel_name=ProvCache-LABS]}
| org.jgroups.protocols.UDP --> message is [dst: 172.16.11.20:35858, src:
172.16.11.10:51918 (3 headers), size = 0 bytes], headers are
{GMS=GmsHeader[VIEW_ACK]: view=[172.16.11.20:35858|259] [172.16.11.20:35858,
172.16.11.11:51210, 172.16.11.191:37204, 172.16.11.10:51 918,
172.16.11.12:40087, 172.16.11.13:38513, 172.16.11.13:38520, 172.16.11.13:38533,
172.16.11.200:32790], UNICAST=[UNICAST: DATA, seqno=1],
UDP=[channel_name=ProvCache-LABS]}
| org.jgroups.protocols.UDP --> sending msg to 172.16.11.20:35858
(src=172.16.11.20:35858), headers are {GMS=GmsHeader[VIEW_ACK]:
view=[172.16.11.20:35858|259] [172.16.11.20:35858, 172.16.11.11:51210,
172.16.11.191:37204, 172.16.11.10:51918, 172.16.11.12:40087,
172.16.11.13:38513, 172.16.11.13:38520, 172.16.11.13:38533,
172.16.11.200:32790], UDP=[channe l_name=ProvCache-LABS], UNICAST=[UNICAST:
DATA, seqno=1]}
| org.jgroups.protocols.UDP --> message is [dst: 172.16.11.20:35858, src:
172.16.11.20:35858 (3 headers), size = 0 bytes], headers are
{GMS=GmsHeader[VIEW_ACK]: view=[172.16.11.20:35858|259] [172.16.11.20:35858,
172.16.11.11:51210, 172.16.11.191:37204, 172.16.11.10:51 918,
172.16.11.12:40087, 172.16.11.13:38513, 172.16.11.13:38520, 172.16.11.13:38533,
172.16.11.200:32790], UNICAST=[UNICAST: DATA, seqno=1],
UDP=[channel_name=ProvCache-LABS]}
| org.jgroups.protocols.UDP --> message is [dst: 172.16.11.20:35858, src:
172.16.11.11:51210 (3 headers), size = 0 bytes], headers are
{GMS=GmsHeader[VIEW_ACK]: view=[172.16.11.20:35858|259] [172.16.11.20:35858,
172.16.11.11:51210, 172.16.11.191:37204, 172.16.11.10:51 918,
172.16.11.12:40087, 172.16.11.13:38513, 172.16.11.13:38520, 172.16.11.13:38533,
172.16.11.200:32790], UNICAST=[UNICAST: DATA, seqno=1],
UDP=[channel_name=ProvCache-LABS]}
| org.jgroups.protocols.UDP --> message is [dst: 172.16.11.20:35858, src:
172.16.11.191:37204 (3 headers), size = 0 bytes], headers are
{GMS=GmsHeader[VIEW_ACK]: view=[172.16.11.20:35858|259] [172.16.11.20:35858,
172.16.11.11:51210, 172.16.11.191:37204, 172.16.11.10:5 1918,
172.16.11.12:40087, 172.16.11.13:38513, 172.16.11.13:38520, 172.16.11.13:38533,
172.16.11.200:32790], UNICAST=[UNICAST: DATA, seqno=1],
UDP=[channel_name=ProvCache-LABS]}
[jboss-user] [JBoss Cache: Core Edition] - JDBC Cache Loader always loads from DB
I'm using JBoss Cache 1.4.1 SP8 and JGroups 2.4.1 SP4 I've configured my cache with JDBC Cacheloader and I see that for each request the cache is loading from the DB inspite of the data residing in the cache. At what circumstances this might happen. The configuration i've used is | | | | | | | | | jboss:service=Naming | jboss:service=TransactionManager | | PESSIMISTIC | | READ_COMMITTED | | REPL_SYNC | | true | | false | | 0 | | 0 | | Cache-LABS | | true | | | | | | | | | | | | | | | | | | | 15 | | 12 | | | | false | / | true | | org.jboss.cache.loader.JDBCCacheLoader | | cache.jdbc.table.name=DBCACHE | cache.jdbc.table.create=false | cache.jdbc.table.drop=false | cache.jdbc.table.primarykey=jbosscache_pk | cache.jdbc.fqn.column=fqn | cache.jdbc.fqn.type=varchar(255) | cache.jdbc.node.column=node | cache.jdbc.node.type=blob | cache.jdbc.parent.column=parent | cache.jdbc.datasource=jdbc/basic | cache.async.batchSize=1 | cache.async.pollWait=100 | cache.async.returnOld=true | cache.async.queueSize=100 | cache.async.put=true | | false | true | false | false | | | | | | | | | | The log messages from jboss are as org.jboss.cache.loader.JDBCCacheLoader --> executing sql: select node from DBCACHE where fqn=? Please suggest your thoughts on this. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4224411#4224411 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4224411 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Cache: Core Edition] - Re: JDBC Cache Loader always loads from DB
can you please reply on this ? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4224648#4224648 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4224648 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Cache: Core Edition] - Re: JDBC Cache Loader always loads from DB
Nope. I'm already using this in my application. Migrating to a newer version wouldn't be possible. But what could be the reason for this ? I've seen some time before that "mustload=false" (which means the node exists in the cache) but now i always see "mustload=true" (but the data exists in the cache). Advice me on this please. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4224663#4224663 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4224663 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Cache: Core Edition] - Re: JDBC Cache Loader always loads from DB
Any updates on this ?? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4224874#4224874 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4224874 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Cache: Core Edition] - Re: FD Issue
Just to give an update on this, it was identified that the dead member's(suspected member's) neighbor was having a wrong gateway entry in the routing table configuration. Instead of having its own IP it was pointing to another IP which was also in the same cluster. Once that instance was restarted the VIEW was updated successfully and replicated to all members. Would this have been the cause for the problem ? Please clarify on this to further analyze on this. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4225436#4225436 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4225436 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Cache: Core Edition] - Re: FD Issue
Any thoughts on this ??? Please reply. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4225552#4225552 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4225552 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossCache] - Local cache without store
Do i need to configure a jboss cache xml file for running the cache in LOCAL mode without store ? Is it be defaut in LOCAL mode ? Can I start the cache without specifying the cache-config.xml ? When i tried without the cache-config.xml file and specifying the "CacheMode" as LOCAL in cache-config.xml file the cache was up and running successfully. So please let me know the appropriate way for configuring in LOCAL mode without store. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4036946#4036946 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4036946 ___ jboss-user mailing list [EMAIL PROTECTED] https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossCache] - AsyncCacheLoader
I want to use jdbc writes in async mode. I've tailored MyAsyncCacheLoader
extending AsyncCacheLoader with overridden put methods. I'm calling super(new
JDBCCacheLoader) in the constructor and loading the config file. Unexpectedly
my properties file alone gets loaded, but doesn't call my put method which i've
overrided, instead it writes to the DB directly. Please suggest me how to
proceed. Alternate solutions are welcomed.
My Code goes as
import java.io.File;
import java.io.FileInputStream;
import java.io.FileNotFoundException;
import java.io.IOException;
import java.util.Iterator;
import java.util.Map;
import java.util.Properties;
import java.util.Set;
import org.jboss.cache.DataNode;
import org.jboss.cache.Fqn;
import org.jboss.cache.PropertyConfigurator;
import org.jboss.cache.TreeCache;
import org.jboss.cache.loader.AsyncCacheLoader;
import org.jboss.cache.loader.AsyncExtendedCacheLoader;
import org.jboss.cache.loader.ExtendedCacheLoader;
import org.jboss.cache.loader.FileCacheLoader;
import org.jboss.cache.loader.JDBCCacheLoader;
import org.jboss.cache.loader.JDBCExtendedCacheLoader;
public class MyAsyncCacheLoader extends AsyncCacheLoader {
private static long timeStamp;
private static long oneHrtimeStamp;
public MyAsyncCacheLoader(){
super(new JDBCCacheLoader());
Properties cfg = new Properties();
try {
cfg.load(new FileInputStream(new
File("async.properties")));
} catch (FileNotFoundException e) {
e.printStackTrace();
} catch (IOException e) {
e.printStackTrace();
}
System.out.println("Read the value : " + cfg);
String key = "cache.async.batchSize";
String val = cfg.getProperty (key) ;
System.out.println("Read the value : " + val);
this.setConfig(cfg);
timeStamp=0;
oneHrtimeStamp=0;
}
public Object put(Fqn name, Object key, Object value) throws Exception{
System.out.println("Inside MyAsyncCacheLoader put");
if(!name.getLast().equals("operation"))
{
System.out.println(name.toString()+ " written
to DB");
super.put(name, key, value);
}
else
System.out.println(name.toString()+ " will not
be written to DB");
return value;
}
public void put(Fqn name, Map attributes) throws Exception
{
System.out.println("Inside MyAsyncCacheLoader Put (map) method
:: Fqn = "+ name );
if(!name.getLast().equals("operation"))
{
System.out.println(name.toString()+ " written
to DB");
super.put(name, attributes);
}
else
System.out.println(name.toString()+ " will not
be written to DB");
}
}
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4028677#4028677
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4028677
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossCache] - Re: AsyncCacheLoader
Thanks for the reply !! If i'm setting async to true, does the db writes happen in a separate thread. In that case can i control the no. of DB writes in a specific time ? eg: Can i write 1000 requests in 1 min ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029785#4029785 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4029785 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossCache] - Re: AsyncCacheLoader
Adding to the above, can i make the cache store data into the persistent store or DB every 1 minute irrespective of the no. operations performed on the cache. Further, irrespective of any operations done on the cache, how can i schedule the cache loader to persist cache data every 1 min. If this isn't possible how else can i configure the async behaviour ? Is there a configuration file ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029799#4029799 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4029799 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossCache] - Re: AsyncCacheLoader
Thanks Again !! I need to schedule the cacheloader to persist DB for a specific node alone in the cache data every 1 min. Can i achieve and configure this ? I've tried with batchSize and pollWait but unsuccessful, so let me know how can i achieve this. An example will be more sufficient. Thanks in advance. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4030200#4030200 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4030200 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Cache: Core Edition] - JDBCCacheLoader
When we use treecache.get() with JDBCCacheloader configured does it ALWAYS goes to the DB inspite of the data being in-memory ? Please clarify the same. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4162539#4162539 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4162539 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossCache] - Re: Initial state transfer failed: Channel.getState() return
As said I increased the InitialStateRetrievelTimeout to a higher value and find it proper now. Thanks !! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058548#4058548 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4058548 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossCache] - Cache Lock TimeoutException
I'm using JBoss Cache 1.4.1 SP2 without CacheLoader. I dont want cacheloader to be used. In my application there are multiple instances which are writing a particular node acquiring a WRITE lock. While this process is performed by a thread, another thread wakes up periodically and tries to read the value in that node, trying to acquire a READ lock. Since there are multiple instances writing on that node this READ lock is prioritized as low which waits for 15000milliseconds(as configured) and TIME-OUT occurs failing to read. Use Case is Thread A and Thread B writes on Node N continously and Thread C starts to read the value in Node N which fails after waiting leading to a Cache Lock Timeout Exception. Please advice on preventing this scenario or an alternate approach to read the value in Node N View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4047574#4047574 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4047574 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossCache] - Node Cloning
Node root=tree1.getRoot(); Node cloneNode = new Node(); cloneNode = (Node)root.clone(); This throws a classCast Exception, what is wrong in implementation ? How can i clone a specific node ?? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4047579#4047579 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4047579 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossCache] - Initial state transfer failed: Channel.getState() returned f
I'm using fetchInMemoryState as true. When i'm trying to restart(stop and startService of the treecache) cache i get this message. What is possibly causing this problem ? Error Message org.jboss.cache.CacheException: Initial state transfer failed: Channel.getState() returned false at org.jboss.cache.TreeCache.fetchStateOnStartup(TreeCache.java:3349) at org.jboss.cache.TreeCache.startService(TreeCache.java:1543) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4055949#4055949 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4055949 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
