2 Replies Latest reply on Oct 22, 2001 5:39 AM by rajesh's

    Entity bean not calling the ejbLoad

    rajesh's

      I deployed a BMP entity bean in my JBOSS server with default container settings.I had a problem while executing the client. The container is not calling the ejbLoad() method of the bean instance. Instead it take the bean state from the container cache. Even though it result in greater speed , i had lot of other issues with this.
      My Question is :

      1. Does it happens because of the default configuration.Can we change this container behaviour.
      2. Can i force the container to call ejbLoad.
      3. If the bean instances are suppose in multiple JVMs , the one updation will not affect the other,giving bad result
      4. If JBOSS server is not the only entry point to the server , the server will infact returns the dirty data.

      correct me it is wrong.

        • 1. Re: Entity bean not calling the ejbLoad
          lqd

          JBoss standard config uses commit-option "A" to access the database resulting in the behaviour you are experiencing. change the commit-option to "B" or "C" (this can be done in the file standardjaws.xml) if JBoss is not the exclusive user of the database. The behaviour of the different commit options is documented in SUN's EJB Specifications ...

          • 2. Re: Entity bean not calling the ejbLoad
            rajesh's

            Thank for the tip.I just missed out that point.I changed the parameter and is working fine.