Strange warning wihtin logfiles using JBoss Cache 3.1.0.GA under WebLogic 10.0
by Christian Hartmann
Hi there,
we have set up JBoss-Cache 3.1.0.GA (hibernate-jbosscache2 3.3.2.GA) as a 2nd-Level-Cache for Hibernate running under WebLogic 10.0 successfully within a Cluster running different nodes on different machines. The Cache configuration seems to work without any errors or any disapperance of data. However, we are facing a strange warning within our logs for the JBoss-Cache:
"WARN ;Multiplexer-1;Unknown replication version [999]. Falling back to the default marshaller installed."
We are using this configuration for the persistence.xml
[...]
<property name="hibernate.cache.use_second_level_cache" value="true/>
<property name="hibernate.cache.use_query_cache" value="true"/>
<property name="hibernate.cache.region.factory_class" value="org.hibernate.cache.jbc2.SharedJBossCacheRegionFactory"/>
<property name="hibernate.cache.use_structured_entries" value="true"/>
<property name="hibernate.cache.use_structured_cache_entries" value="true"/>
<property name="hibernate.cache.region.jbc2.cfg.shared" value="treecache.xml"/>
[...]
and this is our configuration for the treecache.xml
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8"?>
<!--
<jbosscache xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:jboss:jbosscache-core:config:3.1"
xsi:schemaLocation="urn:jboss:jbosscache-core:config:3.1 /schema/jbosscache-config-3.1.xsd">
-->
<jbosscache xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:jboss:jbosscache-core:config:3.1">
<transaction transactionManagerLookupClass="org.jboss.cache.transaction.GenericTransactionManagerLookup"
syncRollbackPhase="false"
syncCommitPhase="false"
/>
<locking
isolationLevel="REPEATABLE_READ"
lockParentForChildInsertRemove="false"
lockAcquisitionTimeout="15000"
nodeLockingScheme="mvcc"
writeSkewCheck="false"
useLockStriping="true"
concurrencyLevel="500"
/>
<serialization
objectInputStreamPoolSize="12"
objectOutputStreamPoolSize="14"
version="3.0.0"
marshallerClass="org.jboss.cache.marshall.CacheMarshaller300"
useLazyDeserialization="false"
useRegionBasedMarshalling="true"/>
<startup regionsInactiveOnStartup="true"/>
<eviction wakeUpInterval="5">
<default algorithmClass="org.jboss.cache.eviction.LRUAlgorithm"
actionPolicyClass="org.jboss.cache.eviction.DefaultEvictionActionPolicy"
eventQueueSize="200000">
<property name="maxNodes" value="10000"/>
<property name="timeToLive" value="1000"/>
</default>
<region name="/_default_" algorithmClass="org.jboss.cache.eviction.LRUAlgorithm"
actionPolicyClass="org.jboss.cache.eviction.DefaultEvictionActionPolicy"
eventQueueSize="100000">
<property name="maxNodes" value="10000"/>
<property name="timeToLive" value="1000"/>
<property name="minTimeToLive" value="120"/>
</region>
<!-- Never evict the UpdateTimeStampsCache according to
http://docs.jboss.org/hibernate/stable/core/reference/en/html/performance... -->
<region name="/TS" algorithmClass="org.jboss.cache.eviction.NullEvictionAlgorithm"
actionPolicyClass="org.jboss.cache.eviction.DefaultEvictionActionPolicy"
eventQueueSize="100000">
</region>
</eviction>
<clustering mode="replication" clusterName="${uniqueDI}">
<async useReplQueue="true" replQueueInterval="10000" replQueueMaxElements="500"
serializationExecutorPoolSize="20" serializationExecutorQueueSize="5000000"/>
<stateRetrieval timeout="20000" fetchInMemoryState="false"/>
<jgroupsConfig multiplexerStack="udp"/>
</clustering>
</jbosscache>
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
We tried to change marshallerClass to "org.jboss.cache.marshall.VersionAwareMarshaller", but then we are facing a Null Pointer Exception:
2011-01-14 12:37:42,655;ERROR;AsyncReplicationProcessor-1;java.lang.NullPointerException: <no message available (3)>
Stack trace:
org.jboss.cache.marshall.VersionAwareMarshaller.objectToObjectStream(VersionAwareMarshaller.java:340)
org.jboss.cache.marshall.VersionAwareMarshaller.objectToBuffer(VersionAwareMarshaller.java:182)
org.jboss.cache.marshall.VersionAwareMarshaller.objectToBuffer(VersionAwareMarshaller.java:52)
org.jboss.cache.marshall.CommandAwareRpcDispatcher$ReplicationTask.call(CommandAwareRpcDispatcher.java:369)
Is there anybody who can help and might tell us what is wrong here?
Any help will be appreciated.
Regards,
Christian
Steria Mummert Consulting AG
Vorsitzender des Aufsichtsrates: Jürgen Sponnagel - Vorstand: Oliver Nazet (Vors.), Dr. Reinhard Liedl, Dr. Fritz Moser
Gesellschaftssitz: Hamburg - HR B 61 116 Amtsgericht Hamburg - USt-ID-Nr.: DE118671351
Bitte denken Sie an Ihre Verantwortung gegenüber der Umwelt: Jede ausgedruckte E-Mail verursacht ca. 0,3 Gramm CO2.
Diese Nachricht kann vertrauliche Informationen enthalten und ist allein für den Adressaten bestimmt. Wenn Sie nicht der rechtmäßige Empfänger sind, sind der Zugriff, die Weiterleitung, das Kopieren, die Veröffentlichung oder anderweitige Verwendung des Inhalts untersagt. In diesem Fall bitten wir Sie, den Absender unverzüglich zu informieren und diese E-Mail sowie sämtliche Kopien dieser E-Mail zu löschen. Der Inhalt von E-Mails innerhalb des Netzwerks kann überprüft werden, um die Übereinstimmung mit den geltenden Firmenrichtlinien und Vorgehensweisen zu gewährleisten. E-Mails können auf dem Transportweg von Dritten verändert werden, so dass deren Vollständigkeit und Echtheit nicht garantiert werden können.
This e-mail communication may contain confidential information and is intended only for the recipient. If you are not the intended recipient you are not allowed to read, copy, distribute, publicize or use the content of this e-mail in any way. Please notify the sender and delete the e-mail and any copies of it. The content of e-mails within our network may be monitored to ensure compliance with company policies and procedures. E-mails can be alterated by third parties in transit. Therefore any e-mail is susceptible to alteration and its integrity cannot be assured.
13 years, 10 months
- 1
- 0
- ← Newer
- 1
- Older →