[jboss-user] [JBossCache] - Problems replicating. when using Jboss 4.0.2 , JBossCache 1.
pharvener
do-not-reply at jboss.com
Tue Aug 8 12:23:14 EDT 2006
We are using Jboss 4.0.2 , JBossCache 1.4 and Java 1.4.2.11
All we get the following exception we cluster and replicate:
java.rmi.ServerException: EJBException:; nested exception is: javax.ejb.EJBException: RuntimeException; CausedByException is: java.lang.NoClassDefFoundError: org/jboss/cache/marshall/ObjectSerializationFactory$JBossObjectInputStreamOverride at org.jboss.ejb.plugins.LogInterceptor.handleException(LogInterceptor.java:352) at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:196) at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:122) at org.jboss.ejb.SessionContainer.internalInvoke(SessionContainer.java:624) at org.jboss.ejb.Container.invoke(Container.java:873)
We can locate the class org/jboss/cache/marshall/ObjectSerializationFactory in the ear
Does it matter that we are compiling to 1.3 compliance?
Below is our config file:
<?xml version="1.0" encoding="UTF-8" ?>
<!-- ==================================================================== -->
<!-- Defines TreeCache configuration -->
<!-- ==================================================================== -->
jboss:service=Naming
<!--
Node locking scheme :
PESSIMISTIC (default)
OPTIMISTIC
-->
PESSIMISTIC
<!--
Node locking isolation level :
SERIALIZABLE
REPEATABLE_READ (default)
READ_COMMITTED
READ_UNCOMMITTED
NONE
(ignored if NodeLockingScheme is OPTIMISTIC)
-->
REPEATABLE_READ
<!-- Valid modes are LOCAL
REPL_ASYNC
REPL_SYNC
INVALIDATION_ASYNC
INVALIDATION_SYNC
-->
REPL_ASYNC
<!-- Whether each interceptor should have an mbean
registered to capture and display its statistics. -->
true
<!-- Name of cluster. Needs to be the same for all clusters, in order
to find each other -->
TreeCache-Rnj-Cluster
<!-- UDP: if you have a multihomed machine,
set the bind_addr attribute to the appropriate NIC IP address
-->
<!-- 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="228.6.6.6" mcast_port="48666" 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" />
<PING timeout="2000" num_initial_members="3" up_thread="false" down_thread="false" />
<MERGE2 min_interval="10000" max_interval="20000" />
<FD shun="true" up_thread="true" down_thread="true" />
<VERIFY_SUSPECT timeout="1500" up_thread="false" down_thread="false" />
<pbcast.NAKACK gc_lag="50" max_xmit_size="8192" retransmit_timeout="600,1200,2400,4800" up_thread="false"
down_thread="false" />
<UNICAST timeout="600,1200,2400" window_size="100" min_threshold="10" down_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" />
<pbcast.STATE_TRANSFER up_thread="false" down_thread="false" />
<!-- 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
-->
5000
<!-- Number of milliseconds to wait until all responses for a
synchronous call have been received.
-->
10000
<!-- Max number of milliseconds to wait for a lock acquisition -->
15000
paul
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3963853#3963853
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3963853
More information about the jboss-user
mailing list