2 Replies Latest reply on Jul 26, 2004 10:22 AM by pedrosalazar

    cluster entity EJBs with invalidation

    pedrosalazar

      Greetings,

      When I deploy my Read-Only Entity Beans for invalidation target I must select the configuration "Standard CMP 2.x EntityBean with cache invalidation" from the jboss configurations, because is the only profile with invalidation.

      Since I would like to deploy them as cluster EJBs (jboss.xml: < clustered>true< /clustered>) I received always a warning that there isn't a single clustered invoker available in that configuration:

      WARN [org.jboss.ejb.EntityContainer] *** EJB 'X' deployed as CLUSTERED but not a single clustered-invoker is bound to container ***
      


      Questions:

      - the cluster configuration of EJBs means that when a entity bean is load on one jboss instance, the cluster replicates these beans to the others instances? It's recommended? I'm trying to get the best performance, with invalidation, but I don't know if the cluster replication bottleneck is acceptable.

      - can I extend the configuration "Standard CMP 2.x EntityBean with cache invalidation" to support cluster (clustered-invoker) or add a invalidation feature to a cluster existent configuration?

      Regards,
      Pedro Salazar.

        • 1. Re: cluster entity EJBs with invalidation
          mlange

          The warning always appears if you add the clustered tag to ejb with local interfaces. If you change to remote interfaces it is gone....

          -marek

          • 2. Re: cluster entity EJBs with invalidation
            pedrosalazar

             

            "mlange" wrote:
            The warning always appears if you add the clustered tag to ejb with local interfaces. If you change to remote interfaces it is gone....

            -marek


            Does it means that if local interfaces exists the entity bean isn't clustered? Or that remote interfaces are required for clustered? I could add both... I have only local interfaces for my EJBs for performance issues.

            And what kind of configuration you use for your entity beans? Does it work with invalidation?

            Regards,
            Pedro Salazar.