Passivation errors on Weblogic clustered setup.

Question

          Hi,
          I have a Weblogic 6.0 SP2 clustered setup. If I change the deployment descriptor
          and set the
          max-beans-in-cache to 2 and create 3 instances of a stateful ejb, it gets passivated
          without any exceptions, but if the application runs for a long time, passivation
          errors occur.
          I get the following exceptions:
          ####<Aug 4, 2003 4:04:36 PM GMT> <Info> <Cluster> <HQBUSA55> <enrolem2> <ExecuteThread:
          '1' for queue: 'Replication'> <> <> <000118> <Lost 647 replication updates of
          object -7971217480608673154. Re-fetching secondary.>
          ####<Aug 4, 2003 4:04:36 PM GMT> <Info> <Cluster> <HQBUSA55> <enrolem2> <ExecuteThread:
          '1' for queue: 'Replication'> <> <> <000118> <Lost 648 replication updates of
          object -7971217480608673154. Re-fetching secondary.>
          ####<Aug 5, 2003 7:06:11 AM GMT> <Warning> <NT Performance Pack> <HQBUSA55> <enrolem2>
          <ExecuteThread: '1' for queue: 'default'> <> <> <000000> <Already cleaned up fd:
          '-1', socket: 'Socket[addr=hq3105.nestle.com/141.122.142.71,port=1534,localport=7778]'>
          ####<Aug 5, 2003 7:51:26 AM GMT> <Error> <EJB> <HQBUSA55> <enrolem2> <ExecuteThread:
          '5' for queue: 'default'> <> <> <010024> <Error during passivation: java.io.NotSerializableException:
          com.sun.jndi.ldap.LdapCtx
               at java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:1143)
               at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:361)
               at java.io.ObjectOutputStream.outputClassFields(ObjectOutputStream.java:1822)
               at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:475)
          Is this a known issue? Is there any service pack or fix pack for the same?
          Please give me your suggestions.
          Thanks,
          Bhumika
          

Answer 1

          There are known issues with SFSBs not being serializble in 6.1. see if you can
          upgrade or increase cache size.
          S
          "Bhumika Nagarsekar" <[email protected]> wrote:
          >
          >Hi,
          >
          >I have a Weblogic 6.0 SP2 clustered setup. If I change the deployment
          >descriptor
          >and set the
          >max-beans-in-cache to 2 and create 3 instances of a stateful ejb, it
          >gets passivated
          >without any exceptions, but if the application runs for a long time,
          >passivation
          >errors occur.
          >
          >I get the following exceptions:
          >####<Aug 4, 2003 4:04:36 PM GMT> <Info> <Cluster> <HQBUSA55> <enrolem2>
          ><ExecuteThread:
          >'1' for queue: 'Replication'> <> <> <000118> <Lost 647 replication updates
          >of
          >object -7971217480608673154. Re-fetching secondary.>
          >####<Aug 4, 2003 4:04:36 PM GMT> <Info> <Cluster> <HQBUSA55> <enrolem2>
          ><ExecuteThread:
          >'1' for queue: 'Replication'> <> <> <000118> <Lost 648 replication updates
          >of
          >object -7971217480608673154. Re-fetching secondary.>
          >####<Aug 5, 2003 7:06:11 AM GMT> <Warning> <NT Performance Pack> <HQBUSA55>
          ><enrolem2>
          ><ExecuteThread: '1' for queue: 'default'> <> <> <000000> <Already cleaned
          >up fd:
          >'-1', socket: 'Socket[addr=hq3105.nestle.com/141.122.142.71,port=1534,localport=7778]'>
          >
          >####<Aug 5, 2003 7:51:26 AM GMT> <Error> <EJB> <HQBUSA55> <enrolem2>
          ><ExecuteThread:
          >'5' for queue: 'default'> <> <> <010024> <Error during passivation: java.io.NotSerializableException:
          >com.sun.jndi.ldap.LdapCtx
          >     at java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:1143)
          >     at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:361)
          >     at java.io.ObjectOutputStream.outputClassFields(ObjectOutputStream.java:1822)
          >     at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:475)
          >
          >Is this a known issue? Is there any service pack or fix pack for the
          >same?
          >Please give me your suggestions.
          >
          >Thanks,
          >Bhumika