[jboss-user] [JBossCache] - Re: Hibernate 2nd lvl Cache for EJB3

[MarcReis]

No Problem ! :-).

I have some more questions (again :- ). Rather basic, maybee somewhat "stupid" questions.
First, in each of the EJB3 SFSB Caches there is this "jboss:internal:uinitialized:null" thing. What is the purpose of this ? e.g.:

  | /NatPersLstSFBean
  | jboss:internal:uninitialized: null
  | 
  |     /4sgm5-99wwev-eqgp80f9-1-eqgpe5gq-7
  | jboss:internal:uninitialized: null
  | bean: org.jboss.ejb3.stateful.StatefulBeanContext at 1019819
  | 
  |     /4sgm5-99wwev-eqgp80f9-1-eqgph66s-b
  | jboss:internal:uninitialized: null
  | bean: org.jboss.ejb3.stateful.StatefulBeanContext at 1a8bce8
  | ....
  | 

Second, at the moment the 

  | 17:20:33,578 WARN  [CacheLoaderInterceptor] CacheLoader.get(Fqn) returned a null
  | ; assuming the node nodes not exist.
  | 17:20:33,671 WARN  [CacheLoaderInterceptor] The CacheLoader interface has change
  | d since JBossCache 1.3.x
  | 17:20:33,671 WARN  [CacheLoaderInterceptor] Please see http://jira.jboss.com/jir
  | a/browse/JBCACHE-118
  | 17:20:33,671 WARN  [CacheLoaderInterceptor] CacheLoader.get() should return an e
  | mpty Map if the node does exist but doesn't have any attributes.
  | 
shows up the Client throws a 

  | java.lang.RuntimeException: cluster invocation failed, last exception was: 
  | 	at org.jboss.aspects.remoting.ClusterChooserInterceptor.invoke(ClusterChooserInterceptor.java:129)
  | ...
  | 
Is this due just to the cache failing ?

Sincerly
Marc

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3963236#3963236

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3963236