anonymous wrote : | | <Aug 18, 2006 3:21:29 PM EDT> <BEA-050002> <Cannot replicate object that is bound in the JNDI under the name java:jbosscache.> | |
This is not an error. This is fine, you don't want BEA to replicate your cache instance. This is why you bind it to the java: JNDI namespace. anonymous wrote : | | ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)' org.jboss.cache.GenericTransactionManagerLookup - Failed to perform a lookup for [java:/TransactionManager (JBoss, JRun4)] | | This is fine as well, the GenericTMLookup will cycle through a number of "known" locations where app servers bind their TMs. So there will be a few misses, but it will (should) find WL's TM when it searches for it. (You should see another log message to this effect) Your second server will not be able to see java:jbosscache. This is expected. You need to deploy it on your second server as well, as per the instructions on the wiki. It is the *contents* of the cache that get transparently clustered, not the cache object itself. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3966608#3966608 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3966608 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
