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

        No work has yet been logged on this issue.

          People

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

            Dates

            • Created:
              Updated: