glassfish
  1. glassfish
  2. GLASSFISH-5127

stateful session beans not getting passivated

    Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 9.0pe
    • Fix Version/s: not determined
    • Component/s: ejb_container
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

    • Issuezilla Id:
      5,127

      Description

      Stateful session beans are not getting passivated. The bean's cache size is set
      to be 1(one) in sun-ejb-jar.xml. The bean is looked up twice from a java client
      and some business method invoked on it. Monitoring the application server
      through console, it can be seen that the 'NumBeansInCache' keeps on increasing
      on each re-run of the client. Also 'NumPassivationSuccess' is always 0(zero).

      Also tried configuring the EJB container to set the 'Maximum Pool Size' and
      'Maximum Pool Size' equal to 1. But the result is same.

      Steps to recreate:
      1. Deploy statefulPassivation.jar on the server
      2. Enable monitoring for EJB Container
      3. Run java -jar Client.jar with system property set for
      'java.naming.factory.initial'

      Check value of 'NumBeansInCache' in application server monitor and also no SOPs
      given in prePassivate and postActivate callbacks appearing in logs.

        Activity

        Hide
        rajbirb added a comment -

        Created an attachment (id=1546)
        test ejb application

        Show
        rajbirb added a comment - Created an attachment (id=1546) test ejb application
        Hide
        rajbirb added a comment -

        Created an attachment (id=1547)
        sources for test ejb application

        Show
        rajbirb added a comment - Created an attachment (id=1547) sources for test ejb application
        Hide
        rajbirb added a comment -

        Created an attachment (id=1548)
        client for the test application

        Show
        rajbirb added a comment - Created an attachment (id=1548) client for the test application
        Hide
        rajbirb added a comment -

        Created an attachment (id=1549)
        client sources

        Show
        rajbirb added a comment - Created an attachment (id=1549) client sources
        Hide
        Mahesh Kannan added a comment -

        For performance reasons the container passivates beans only if the number of
        beans to be passivated is more than 8. The number 8 has was decided purely based
        on performance benchmarks that were done with earlier releases.

        In this case, there is only one bean that needs to be passivated and hence the
        container didn't call ejbPassivate.

        Also, the tunnings (max-cache-size etc.) are mainly used to controll the beans
        under heavy loads.

        This is not a bug at all. I am moving this as an enhancement and also reducing
        the priority.

        Show
        Mahesh Kannan added a comment - For performance reasons the container passivates beans only if the number of beans to be passivated is more than 8. The number 8 has was decided purely based on performance benchmarks that were done with earlier releases. In this case, there is only one bean that needs to be passivated and hence the container didn't call ejbPassivate. Also, the tunnings (max-cache-size etc.) are mainly used to controll the beans under heavy loads. This is not a bug at all. I am moving this as an enhancement and also reducing the priority.
        Hide
        Tom Mueller added a comment -

        Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.

        Show
        Tom Mueller added a comment - Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.

          People

          • Assignee:
            Mahesh Kannan
            Reporter:
            rajbirb
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated: