Serializing an instance of weblogic.rjvm.RJVM

Question

          I'm migrating a WebApp from WebLogic 5.1 (single server) to a 6.0 Cluster, and
          I've discovered that when one of the servlets attempts to retrieve the HttpSession
          from the Request, a NotSerializableException is thrown. When I look through the
          stack-trace, I can see the servlet requesting the HttpSession from the Request,
          and then WebLogic sometimes needs to retrieve it from another server within the
          cluster. I did a bit of digging, and found that somewhere within the object-graph,
          there's a Hashtable that contains an instance of weblogic.rjvm.RJVM, and that's
          not Serializable (not surprising).
          Being that I didn't write this application, I don't know how deeply nested
          this object is - my assumption is that in the HttpSession, one of the objects
          is the parent of an object (or many objects), one of which contains the Hashtable
          which contains the RJVM reference. The problem is, I don't know how to identify
          the rogue object's parent(s). This wan't an issue on 5.1 because it never ran
          in a cluster. This app also runs fine on a WebLogic 6.0 stand-alone server. It's
          only when we activate clustering that we see this problem of Serializing the RJVM
          object.
          I've tried to guess what kind of object would contain the Hashtable that posesses
          the RJVM object. One possibility is some type of Context object - this application
          uses sfsb and slsb, and in some cases the application designers decided to put
          a reference to the EJB in the HttpSession, rather than an EJBHandle. It may be
          that when HttpSession is replicated throughout the cluster, the sfsb is serialized,
          along with the SessionContext that it posesses?
          Any ideas on how I'd locate the parent(s) of the instance of weblogic.rjvm.RJVM?
          Thanks,
          --Benjamin Peter
          [email protected]
          

Answer 1

Have you tried examining the contents of the session? You can iterate
          through the entries.
          Peace,
          Cameron Purdy
          Tangosol Inc.
          << Tangosol Server: How Weblogic applications are customized >>
          << Download now from http://www.tangosol.com/download.jsp >>
          "Benjamin Peter" <[email protected]> wrote in message
          news:[email protected]...
          >
          > I'm migrating a WebApp from WebLogic 5.1 (single server) to a 6.0
          Cluster, and
          > I've discovered that when one of the servlets attempts to retrieve the
          HttpSession
          > from the Request, a NotSerializableException is thrown. When I look
          through the
          > stack-trace, I can see the servlet requesting the HttpSession from the
          Request,
          > and then WebLogic sometimes needs to retrieve it from another server
          within the
          > cluster. I did a bit of digging, and found that somewhere within the
          object-graph,
          > there's a Hashtable that contains an instance of weblogic.rjvm.RJVM, and
          that's
          > not Serializable (not surprising).
          >
          > Being that I didn't write this application, I don't know how deeply
          nested
          > this object is - my assumption is that in the HttpSession, one of the
          objects
          > is the parent of an object (or many objects), one of which contains the
          Hashtable
          > which contains the RJVM reference. The problem is, I don't know how to
          identify
          > the rogue object's parent(s). This wan't an issue on 5.1 because it never
          ran
          > in a cluster. This app also runs fine on a WebLogic 6.0 stand-alone
          server. It's
          > only when we activate clustering that we see this problem of Serializing
          the RJVM
          > object.
          >
          > I've tried to guess what kind of object would contain the Hashtable
          that posesses
          > the RJVM object. One possibility is some type of Context object - this
          application
          > uses sfsb and slsb, and in some cases the application designers decided to
          put
          > a reference to the EJB in the HttpSession, rather than an EJBHandle. It
          may be
          > that when HttpSession is replicated throughout the cluster, the sfsb is
          serialized,
          > along with the SessionContext that it posesses?
          >
          > Any ideas on how I'd locate the parent(s) of the instance of
          weblogic.rjvm.RJVM?
          >
          > Thanks,
          > --Benjamin Peter
          > [email protected]