7 Replies Latest reply on Jun 25, 2004 10:44 AM by darranl

    passivate warning

    sivauser

      I'm getting the follwoing warning when my server is up


      17:05:04,515 WARN [AbstractInstanceCache] failed to passivate, id=dvqi7r9v-4
      javax.ejb.EJBException: Could not passivate; failed to save state; CausedByException is:
      org.apache.log4j.Logger
      at org.jboss.ejb.plugins.StatefulSessionFilePersistenceManager.passivateSession(StatefulSessionFilePersistenceManager.java:378)
      at org.jboss.ejb.plugins.StatefulSessionInstanceCache.passivate(StatefulSessionInstanceCache.java:85)
      at org.jboss.ejb.plugins.AbstractInstanceCache.tryToPassivate(AbstractInstanceCache.java:156)
      at org.jboss.ejb.plugins.LRUEnterpriseContextCachePolicy$OveragerTask.run(LRUEnterpriseContextCachePolicy.java:435)
      at java.util.TimerThread.mainLoop(Timer.java:432)
      at java.util.TimerThread.run(Timer.java:382)
      java.io.NotSerializableException: org.apache.log4j.Logger
      at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
      at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
      at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
      at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
      at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
      at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
      at org.jboss.ejb.plugins.StatefulSessionFilePersistenceManager.passivateSession(StatefulSessionFilePersistenceManager.java:370)
      at org.jboss.ejb.plugins.StatefulSessionInstanceCache.passivate(StatefulSessionInstanceCache.java:85)
      at org.jboss.ejb.plugins.AbstractInstanceCache.tryToPassivate(AbstractInstanceCache.java:156)
      at org.jboss.ejb.plugins.LRUEnterpriseContextCachePolicy$OveragerTask.run(LRUEnterpriseContextCachePolicy.java:435)
      at java.util.TimerThread.mainLoop(Timer.java:432)
      at java.util.TimerThread.run(Timer.java:382)


      please let me know y is this ....

        • 1. Re: passivate warning
          darranl

          java.io.NotSerializableException

          • 2. Re: passivate warning
            sivauser

            how do i fix it???

            • 3. Re: passivate warning
              dannyyates

              RTFM. Find out (with the help of the stacktrace and the JDK Javadoc) under what circumstances a java.io.NotSerializableException can be thrown. Then figure out (again, with the help of the stacktrace which pretty much gives you the answer) why a NotSerializableException is being thrown in this instance.

              Then go and search on the forums/Google and find the other 5000 times this question has been asked and the answer has been exactly the same.

              Then come back here and ask nicely and we'll cut up your food into easily managable chunks, do all your laundry and housework, and maybe even mow your lawn for you.

              The answers are right in front of you in the stacktrace.

              • 4. Re: passivate warning
                sivauser

                if u can explain what the following means , then rest i'll try n figure out.

                17:05:04,515 WARN [AbstractInstanceCache] failed to passivate, id=dvqi7r9v-4
                javax.ejb.EJBException: Could not passivate; failed to save state; CausedByException is:
                org.apache.log4j.Logger

                • 5. Re: passivate warning
                  milowe

                  Well, if you bothered to read your stacktrace you would realize that org.apache.log4j.Logger is not a serializable class.

                  • 6. Re: passivate warning
                    sivauser

                    why jobss is giving this exception.. I am not serialising org.apache.log4j.Logger class..
                    if anyone have come across same problem pl help..

                    • 7. Re: passivate warning
                      darranl

                      Looking at the stack trace it looks as if you have got a reference to and instance of 'org.apache.log4j.Logger' in a session bean that is being passivated / serialized by the container.