Can't get failover to work

Question

          Hi All,
          We have a startup class that binds HashTables, Vectors, Arrays and Constants into
          the JNDI context. We are also using stateless session beans. Both the items in JNDI
          and the beans are not failing over, in other words a client connects with a browser,
          we shut down one server and when the client clicks to another part of the site, things
          needed from JNDI are not found. My questions are:
          1. Should the startup class be set up in the "global", "cluster" or "per server"
          weblogic.properties file?
          2. Do the EJBs HAVE to be created with "home-is-clusterable" or is this the default
          Anyother tips or direction would be helpful
          Thanks,
          Mike Malgeri
          

Answer 1

          Re: home-is-clusterable defaults to true...I stand corrected.
          "Gene Chuang" <[email protected]> wrote:
          >SSB by default is clusterable. Not only is home-is-clusterable defaulted
          >to true, but SSB stubs are
          >by default cluster-aware. The only thing SSB doesn't do by default is fail-over
          >DURING a method
          >invocation. To enable this you need to set method-is-idempotent to true.
          >
          >If you attempt to add non-clusterable objects to JNDI, like basically anything
          >java, you will
          >achieve in pinning that object/service to that one server.
          >
          >Finally, you shouldn't be sticking Collections, or "dynamic objects", in
          >JNDI. If you need a
          >fail-safe global queue, I suggest implementing it as an entity bean for
          >5.1, or using JMS for 6.0.
          >
          >Gene
          >
          >"Mike Malgeri" <[email protected]> wrote in message news:[email protected]...
          >>
          >> Hi All,
          >>
          >> We have a startup class that binds HashTables, Vectors, Arrays and Constants
          >into
          >> the JNDI context. We are also using stateless session beans. Both the
          >items in JNDI
          >> and the beans are not failing over, in other words a client connects with
          >a browser,
          >> we shut down one server and when the client clicks to another part of
          >the site, things
          >> needed from JNDI are not found. My questions are:
          >>
          >> 1. Should the startup class be set up in the "global", "cluster" or "per
          >server"
          >> weblogic.properties file?
          >>
          >> 2. Do the EJBs HAVE to be created with "home-is-clusterable" or is this
          >the default
          >>
          >>
          >> Anyother tips or direction would be helpful
          >>
          >> Thanks,
          >> Mike Malgeri
          >
          >