[JBoss Cache: Core Edition] - Re: Node in eviction queue not seen in printDetails
by jorgemoralespou_2
Using a remove(Fqn).
As we don`t have a cache loader configured for this cache, we could probably do an evict, but since we have done our own abstraction on top of JBossCache for our way of doing things, we have chosen to use remove so it works with any underlying JBossCache.
CacheEviction is configured the same, so it should evict at same rate, I guess. The thing is that it seems that the is some left over stuff.
Cache config is as follows:
| <server>
|
| <classpath codebase="./lib" archives="jboss-cache.jar, jgroups.jar" />
|
|
| <!-- ==================================================================== -->
| <!-- Defines TreeCache configuration -->
| <!-- ==================================================================== -->
|
|
| <mbean code="org.jboss.cache.TreeCache"
| name="jboss.cache:service=SOMServicesDataCache">
|
| <depends>jboss:service=Naming</depends>
| <!--
| <depends>jboss:service=TransactionManager</depends>
|
| <attribute name="TransactionManagerLookupClass">
| org.jboss.cache.JBossTransactionManagerLookup
| </attribute>
| -->
|
| <!--
| Isolation level : SERIALIZABLE
| REPEATABLE_READ (default)
| READ_COMMITTED
| READ_UNCOMMITTED
| NONE
| -->
| <attribute name="IsolationLevel">NONE</attribute>
|
| <!--
| Valid modes are LOCAL
| REPL_ASYNC
| REPL_SYNC
| INVALIDATION_ASYNC
| INVALIDATION_SYNC
| -->
| <!--
| <attribute name="CacheMode">REPL_SYNC</attribute>
| -->
| <attribute name="CacheMode">REPL_ASYNC</attribute>
|
| <!--
| Just used for async repl: use a replication queue
| -->
| <attribute name="UseReplQueue">false</attribute>
|
| <!--
| Replication interval for replication queue (in ms)
| -->
| <attribute name="ReplQueueInterval">0</attribute>
|
| <!--
| Max number of elements which trigger replication
| -->
| <attribute name="ReplQueueMaxElements">0</attribute>
|
| <!-- Name of cluster. Needs to be the same for all clusters, in order
| to find each other
| -->
| <attribute name="ClusterName">
| SOMServicesCache-Cluster
| </attribute>
|
| <!-- JGroups protocol stack properties. Can also be a URL,
| e.g. file:/home/bela/default.xml
| <attribute name="ClusterProperties"></attribute>
| -->
|
| <attribute name="ClusterConfig">
| <config>
| <!-- UDP: if you have a multihomed machine,
| set the bind_addr attribute to the appropriate NIC IP address, e.g bind_addr="192.168.0.2"
| -->
| <!-- UDP: On Windows machines, because of the media sense feature
| being broken with multicast (even after disabling media sense)
| set the loopback attribute to true -->
| <UDP
| mcast_addr="${jboss.cache.SOMServicesCache.addr:228.1.2.3}"
| mcast_port="${jboss.cache.SOMServicesCache.port:48866}" ip_ttl="64"
| ip_mcast="true" mcast_send_buf_size="150000"
| mcast_recv_buf_size="80000" ucast_send_buf_size="150000"
| ucast_recv_buf_size="80000" loopback="false"
| down_thread="false" up_thread="false"/>
| <PING timeout="2000" num_initial_members="3"
| up_thread="false" down_thread="false" />
| <MERGE2 min_interval="10000" max_interval="20000"
| up_thread="false" down_thread="false" />
| <!-- <FD shun="true" up_thread="true" down_thread="true" />-->
| <FD_SOCK down_thread="false" up_thread="false"/>
| <VERIFY_SUSPECT timeout="1500"
| up_thread="false" down_thread="false" />
| <pbcast.NAKACK gc_lag="50" retransmit_timeout="600,1200,2400,4800"
| max_xmit_size="8192" up_thread="false" down_thread="false"
| discard_delivered_msgs="true"/>
| <UNICAST timeout="600,1200,2400"
| down_thread="false" up_thread="false"/>
| <pbcast.STABLE desired_avg_gossip="20000"
| up_thread="false" down_thread="false" />
| <FRAG frag_size="8192" down_thread="false" up_thread="false" />
| <pbcast.GMS join_timeout="5000" join_retry_timeout="2000"
| shun="true" print_local_addr="true"
| down_thread="false" up_thread="false"/>
| <pbcast.STATE_TRANSFER up_thread="true" down_thread="true" />
| </config>
| </attribute>
|
|
| <!--
| Whether or not to fetch state on joining a cluster
| NOTE this used to be called FetchStateOnStartup and has been renamed to be more descriptive.
| -->
| <attribute name="FetchInMemoryState">${cache.service-data.fetch-in-memory:true}</attribute>
|
| <!--
| The max amount of time (in milliseconds) we wait until the
| initial state (ie. the contents of the cache) are retrieved from
| existing members in a clustered environment
| -->
| <attribute name="InitialStateRetrievalTimeout">${cache.service-data.state-retrieval-timeout:15000}</attribute>
|
| <!--
| Number of milliseconds to wait until all responses for a
| synchronous call have been received.
| -->
| <attribute name="SyncReplTimeout">2000</attribute>
|
| <!-- Max number of milliseconds to wait for a lock acquisition -->
| <attribute name="LockAcquisitionTimeout">10000</attribute>
|
| <!-- Name of the eviction policy class. -->
| <attribute name="EvictionPolicyClass">
| org.jboss.cache.eviction.LRUPolicy
| </attribute>
|
| <!-- Specific eviction policy configurations. This is LRU -->
| <attribute name="EvictionPolicyConfig">
| <config>
| <!-- This attribute will be share by all eviction policies -->
| <attribute name="wakeUpIntervalSeconds">30</attribute>
| <!-- Cache wide default 86400-->
| <region name="/_default_">
| <attribute name="maxNodes">100000</attribute>
| <attribute name="timeToLiveSeconds">86400</attribute>
| </region>
| </config>
| </attribute>
|
|
| <!--
| Indicate whether to use region based marshalling or not. Set this to true if you are running under a scoped
| class loader, e.g., inside an application server. Default is "false".
| -->
|
| <attribute name="UseRegionBasedMarshalling">true</attribute>
| <attribute name="InactiveOnStartup">false</attribute>
|
| <attribute name="CacheLoaderConfiguration">
| <config>
| <passivation>false</passivation>
| <preload>${cache.service-data.cache-loader.preload:/}</preload>
| <shared>true</shared>
|
| <cacheloader>
| <class>
| org.jboss.cache.loader.ClusteredCacheLoader
| </class>
| <properties>timeout=${cache.service-data.cache-loader.timeout:30000}</properties>
| <async>true</async>
| <fetchPersistentState>false</fetchPersistentState>
| <ignoreModifications>false</ignoreModifications>
|
| </cacheloader>
|
| </config>
| </attribute>
|
|
| </mbean>
|
|
| <!-- Uncomment to get a graphical view of the TreeCache MBean above -->
| <!-- <mbean code="org.jboss.cache.TreeCacheView" name="jboss.cache:service=TreeCacheView">-->
| <!-- <depends>jboss.cache:service=TreeCache</depends>-->
| <!-- <attribute name="CacheService">jboss.cache:service=TreeCache</attribute>-->
| <!-- </mbean>-->
|
|
| </server>
|
We have recently changed from REPL_SYNC to REPL_ASYNC due to problems in our network and retransmissions, so this could be the cause of the difference in numbers, I guess.
We have seen that caches are connected to the JGroups channel and that replication is happening, although we don't have enough log level in our production environment to see if there is some nodes not replicated.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160871#4160871
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160871
18 years
[JBoss AOP] - Re: Multiple ClassLoaders problem?
by flavia.rainone＠jboss.com
Hi again!
anonymous wrote : The above piece of code is, at least for me, the cause of my problems. since the ClassLoader that loaded JointPointGenerator cannot "see" JPF's ClassLoader.
Actually, that piece of code gets the class loader that loaded a generated class advisor (in the case, org.drftpd.vfs.InodeHandle$InodeHandleAdvisor), an internal class that has been inserted into the instrumented class's bytecodes. Basically, we are expecting that the class loader that loaded org.drftpd.vfs.InodeHandle$InodeHandleAdvisor is the same that loaded org.drftpd.vfs.InodeHandle.
It looks like that is not case (unless org.drftpd.vfs.index.lucene.SimpleInterceptor is not visible to org.drftpd.vfs.InodeHandle?). I am going to do an investigation to see what is going on.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160867#4160867
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160867
18 years
[Installation, Configuration & DEPLOYMENT] - Re: [JBoss 4.2.2GA]Problem with PostgreSQL as DefaultDS
by klapcio
"jaikiran" wrote : What does your datasource file look like? And also which jars did you copy to the server/< serverName>/lib folder?
|
My postgres-ds.xml looks:
| <?xml version="1.0" encoding="UTF-8"?>
|
| <!-- Datasource config for Postgres -->
|
| <datasources>
| <local-tx-datasource>
| <jndi-name>DefaultDS</jndi-name>
| <connection-url>jdbc:postgresql://[servername]:[port]/[database name]</connection-url>
| <driver-class>org.postgresql.Driver</driver-class>
| <user-name>jboss</user-name>
| <password>jboss</password>
| <!-- sql to call when connection is created. Can be anything, select 1 is valid for PostgreSQL
| <new-connection-sql>select 1</new-connection-sql>
| -->
|
| <!-- sql to call on an existing pooled connection when it is obtained from pool. Can be anything, select 1 is valid for PostgreSQL
| <check-valid-connection-sql>select 1</check-valid-connection-sql>
| -->
|
| <!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml -->
| <metadata>
| <type-mapping>PostgreSQL 8.0</type-mapping>
| </metadata>
| </local-tx-datasource>
|
| </datasources>
|
I copied postgresql-8.1-412.jdbc3.jar into lib directory (I'm using PostgreSQL 8.1.11 on Solaris10)
A DB connection with psql client works fine
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160866#4160866
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160866
18 years