4 Replies Latest reply on Apr 18, 2005 9:26 AM by Kirill Paliy

    Severe (almost unbelievable) caching performance problem

    colin earl Newbie

      When a bean is given a read-only attribute, ejbload is called before every business method, which absolutely cripples performance. In effect, the use of the read-only attribute means that there is no caching!

      This seems to be a clear bug, because without the read-only attribute, ejbload is only called once. (If this behaviour is required when the read-only attribute set, it must also be required without it, so either way there is a bug)

      We cannot remove the read-only attribute becuase this results in deadlocks when several users are accessing the application.

      Full details and a listing of the relevant JBoss source code are provided at http://www.jboss.org/index.html?module=bb&op=viewtopic&t=62713.

      I can hardly believe that JBoss has such a bug since it's effects are so general, but nor can I find any other explanation.