JBoss Cache Context Startup Error

Scott Battaglia scott.battaglia at gmail.com
Thu Sep 21 08:35:37 EDT 2006


Do you think any of your firewalls could be blocking anything?

-Scott

On 9/21/06, Frank Taffelt <frank.taffelt at interface-business.de> wrote:
>
> now i switched the debuglevel for jboss cache and the jgroups stuff to
> debug:
>
> ...
> 2006-09-21 13:20:22,526 DEBUG [org.jgroups.protocols.MERGE2] -
> initial_mbrs=[[own_addr=172.22.200.3:32849, coord_addr=172.22.200.3:32849,
> is_server=true]]
> 2006-09-21 13:20:35,872 DEBUG [org.jgroups.protocols.MERGE2] -
> initial_mbrs=[[own_addr=172.22.20.37:3632, coord_addr=172.22.20.37:3632,
> is_server=true], [own_addr=172.22.200.3:32849,
> coord_addr=172.22.200.3:32849, is_server=true]]
> 2006-09-21 13:20:35,872 DEBUG [org.jgroups.protocols.MERGE2] - found
> multiple coordinators: [172.22.20.37:3632, 172.22.200.3:32849]; sending up
> MERGE event
> 2006-09-21 13:20:52,700 DEBUG [org.jgroups.protocols.MERGE2] -
> initial_mbrs=[[own_addr=172.22.200.3:32849, coord_addr=172.22.200.3:32849,
> is_server=true]]
> MERGE2] - initial_mbrs=[[own_addr=172.22.200.3:32849,
> coord_addr=172.22.200.3:32849, is_server=true]]
>
> ...
>
> for me it seems that the 2 servers : 172.22.20.3 and 172.22.200.37 don't
> find to each other ...
>
> Frank
>
> Arnaud Lesueur wrote:
> > This error doesn't remind me any error that I had.
> >
> > Did you try to tweak the configuration of jgroups by using TCP
> > instead of UDP multicast ? Do you have the same error ?
> >
> > Arnaud Lesueur
> >
> > Le Mer 20 septembre 2006 18:46, Scott Battaglia a écrit :
> >> I just checked my logs and i've never seen that error.
> >>
> >>
> >> -Scott
> >>
> >>
> >> On 9/20/06, Scott Battaglia <scott.battaglia at gmail.com> wrote:
> >>
> >>>
> >>> I don't think I ever saw those errors but I'll check my logs
> >>> tomorrow. Has anyone else who's tried out the JBossCache seen this
> >>> exception?
> >>>
> >>>
> >>> -Scott
> >>>
> >>>
> >>> On 9/19/06, Frank Taffelt <frank.taffelt at interface-business.de>
> >>> wrote:
> >>>
> >>>>
> >>>> Thanks scott now it seems to be starting without errors.
> >>>>
> >>>>
> >>>> i'm not sure if it's really worked as expected, after some
> >>>> logins/logout in my 2 nodes i see the following exception in one
> >>>> of my cas servers: .. 2006-09-19 13:03:36,097 ERROR
> >>>> [org.jasig.cas.ticket.registry.JBossCacheTicketRegistry] -
> >>>> org.jboss.cache.ReplicationException: rsp=sender=172.22.20.37:4270,
> >>>> retval=null, received=false, suspected=false
> >>>> org.jboss.cache.ReplicationException:
> >>>> rsp=sender=172.22.20.37:4270, retval=null, received=false,
> >>>> suspected=false at
> >>>> org.jboss.cache.TreeCache.callRemoteMethods(TreeCache.java:4190)
> >>>> at
> >>>> org.jboss.cache.TreeCache.callRemoteMethods(TreeCache.java:4113)
> >>>> at
> >>>> org.jboss.cache.TreeCache.callRemoteMethods(TreeCache.java:4214)
> >>>> at org.jboss.cache.interceptors.BaseRpcInterceptor.replicateCall(
> >>>> BaseRpcInterceptor.java :110)
> >>>> at org.jboss.cache.interceptors.BaseRpcInterceptor.replicateCall(
> >>>> BaseRpcInterceptor.java:88)
> >>>> at
> >>>>
> >>>>
> org.jboss.cache.interceptors.ReplicationInterceptor.handleReplicatedMethod
> >>>> (ReplicationInterceptor.java:119)
> >>>> at org.jboss.cache.interceptors.ReplicationInterceptor.invoke(
> >>>> ReplicationInterceptor.java:83)
> >>>> at
> >>>> org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68)
> >>>> at org.jboss.cache.interceptors.TxInterceptor.handleNonTxMethod (
> >>>> TxInterceptor.java:345)
> >>>> at
> >>>> org.jboss.cache.interceptors.TxInterceptor.invoke(TxInterceptor.java
> >>>> :156)
> >>>> at
> >>>> org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68)
> >>>> at org.jboss.cache.interceptors.CacheMgmtInterceptor.invoke (
> >>>> CacheMgmtInterceptor.java:157)
> >>>> at org.jboss.cache.TreeCache.invokeMethod(TreeCache.java:5517) at
> >>>> org.jboss.cache.TreeCache.put(TreeCache.java:3677)
> >>>> at org.jboss.cache.TreeCache.put(TreeCache.java:3615) at
> >>>> org.jasig.cas.ticket.registry.JBossCacheTicketRegistry.addTicket(
> >>>> JBossCacheTicketRegistry.java:48) ...
> >>>>
> >>>>
> >>>> i'm sure that my 2 clustered cas servers are running at the time
> >>>> when this exception happens. any hints ?
> >>>>
> >>>> Thanks,
> >>>> Frank
> >>>>
> >>>>
> >>>>
> >>>> Scott Battaglia wrote:
> >>>>
> >>>>>> Frank,
> >>>>>>
> >>>>>>
> >>>>>> I'm attaching the context that I used in my tests.  I haven't
> >>>>>> done extensive research into how these settings can be optimized.
> >>>>>>
> >>>>>> -Scott
> >>>>>>
> >>>>>>
> >>>>>> On 9/18/06, Frank Taffelt <frank.taffelt at interface-business.de>
> >>>>>> wrote:
> >>>>>>
> >>>>>>>
> >>>>>>> Hi,
> >>>>>>>
> >>>>>>>
> >>>>>>> i tried to change CAS 3.0.5 Server to use the new JBoss Cache
> >>>>>>> Stuff from CVS:
> >>>>>>>
> >>>>>>> * copied JBossCacheTicketRegistry, JBossCacheFactoryBean into
> >>>>>>> the
> >>>>>>> localPlugins dir * copied the required jars (jboss ,
> >>>>>>> concurrent,...) into the lib
> >>>>>>> folder * build localPlugins.jar
> >>>>>>> * tweaked ApplicationContext.xml to use the new JBossCache based
> >>>>>>> TicketRegistry
> >>>>>>> * placed jbossCache.xml under WEB-INF/classes
> >>>>>>>
> >>>>>>>
> >>>>>>> restart my tomcat 5.5.17 and see the following exceprion:
> >>>>>>>
> >>>>>>> 2006-09-18 14:28:35,818 INFO
> >>>>>>> [org.jasig.cas.util.JBossCacheFactoryBean] - Starting TreeCache
> >>>>>>> service. 2006-09-18 14:28:35,826 ERROR
> >>>>>>> [org.jboss.cache.transaction.DummyTransactionManager ] -
> >>>>>>> binding of DummyTransactionManager failed
> >>>>>>> javax.naming.NamingException: Context is read only
> >>>>>>> at
> >>>>>>> org.apache.naming.NamingContext.checkWritable(NamingContext.java
> :902)
> >>>>>>> at org.apache.naming.NamingContext.bind(NamingContext.java:830)
> >>>>>>> at org.apache.naming.NamingContext.bind(NamingContext.java:170)
> >>>>>>> at org.apache.naming.NamingContext.bind
> >>>>>>> (NamingContext.java:186) at
> >>>>>>> org.apache.naming.SelectorContext.bind(SelectorContext.java:170)
> >>>>>>> at javax.naming.InitialContext.bind(InitialContext.java:359) at
> >>>>>>> org.jboss.cache.transaction.DummyTransactionManager.getInstance(
> >>>>>>> DummyTransactionManager.java:33)
> >>>>>>> at
> >>>>>>>
> >>>>>>>
> org.jboss.cache.DummyTransactionManagerLookup.getTransactionManager(
> >>>>>>> DummyTransactionManagerLookup.java:17) at
> >>>>>>> org.jboss.cache.TreeCache._createService(TreeCache.java:1314)
> >>>>>>> at org.jboss.cache.TreeCache.startService(TreeCache.java:1407)
> >>>>>>> at org.jasig.cas.util.JBossCacheFactoryBean.afterPropertiesSet(
> >>>>>>> JBossCacheFactoryBean.java:61)
> >>>>>>>
> >>>>>>>
> >>>>>>> have i missed something ?
> >>>>>>>
> >>>>>>> Thanks,
> >>>>>>> Frank
> >>>>>>>
> >>>>>>>
> >>>>>>> _______________________________________________
> >>>>>>> Yale CAS mailing list
> >>>>>>> cas at tp.its.yale.edu http://tp.its.yale.edu/mailman/listinfo/cas
> >>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>> _______________________________________________
> >>>>>> Yale CAS mailing list
> >>>>>> cas at tp.its.yale.edu http://tp.its.yale.edu/mailman/listinfo/cas
> >>>>>>
> >>>>
> >>>> _______________________________________________
> >>>> Yale CAS mailing list
> >>>> cas at tp.its.yale.edu http://tp.its.yale.edu/mailman/listinfo/cas
> >>>>
> >>>>
> >>>
> >>>
> >> _______________________________________________
> >> Yale CAS mailing list
> >> cas at tp.its.yale.edu http://tp.its.yale.edu/mailman/listinfo/cas
> >>
> >>
> >
> >
> > _______________________________________________
> > Yale CAS mailing list
> > cas at tp.its.yale.edu
> > http://tp.its.yale.edu/mailman/listinfo/cas
>
>
> _______________________________________________
> Yale CAS mailing list
> cas at tp.its.yale.edu
> http://tp.its.yale.edu/mailman/listinfo/cas
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://tp.its.yale.edu/pipermail/cas/attachments/20060921/142cdbc2/attachment-0001.html


More information about the cas mailing list