Servlet error in clustering env.

Question

          Guess this is something to do with the servlet clustering configuration. WLS(5.1, sp6) clustering run on Solaris 2.6 with jdk1.2.
          Do any one have any idea what could be the problems?
          =========================================================
          Mon Dec 11 15:58:19 EST 2000:<I> <ServletContext-General> Generated java file: /home/weblogic/5.1/ourserver/cl
          assfiles/jsp_servlet/_html/_libraries/_vieworg.java
          Mon Dec 11 15:58:20 EST 2000:<E> <ServletContextManager> Servlet request terminiated with Error
          weblogic.cluster.replication.BadStatusException: update found 4586531668847271614 but it is not the secondary
          at java.lang.Throwable.fillInStackTrace(Native Method)
          at java.lang.Throwable.fillInStackTrace(Compiled Code)
          at weblogic.rmi.extensions.AbstractRequest.sendReceive(Compiled Code)
          at weblogic.cluster.replication.ReplicationManager_WLStub.update(Compiled Code)
          at weblogic.cluster.replication.ReplicationManager.updateSecondary(Compiled Code)
          at weblogic.servlet.internal.session.ReplicatedSession.sync(Compiled Code)
          at weblogic.servlet.internal.session.ReplicatedSessionContext.sync(Compiled Code)
          at weblogic.servlet.internal.ServletRequestImpl.syncSession(Compiled Code)
          at weblogic.servlet.internal.ServletContextImpl.invokeServlet(Compiled Code)
          at weblogic.servlet.internal.ServletContextImpl.invokeServlet(Compiled Code)
          at weblogic.servlet.internal.ServletContextManager.invokeServlet(Compiled Code)
          at weblogic.socket.MuxableSocketHTTP.invokeServlet(Compiled Code)
          at weblogic.socket.MuxableSocketHTTP.execute(Compiled Code)
          at weblogic.kernel.ExecuteThread.run(Compiled Code)
          --------------- nested within: ------------------
          weblogic.utils.NestedError: Tried to update secondary, but it thought it was the primary - with nested exceptio
          n:
          [weblogic.cluster.replication.BadStatusException: update found 4586531668847271614 but it is not the secondary]
          at java.lang.Throwable.fillInStackTrace(Native Method)
          at java.lang.Throwable.fillInStackTrace(Compiled Code)
          at java.lang.Throwable.<init>(Compiled Code)
          at java.lang.Error.<init>(Error.java:50)
          at weblogic.utils.NestedError.<init>(NestedError.java:23)
          at weblogic.servlet.internal.session.ReplicatedSession.sync(Compiled Code)
          at weblogic.servlet.internal.session.ReplicatedSessionContext.sync(Compiled Code)
          at weblogic.servlet.internal.ServletRequestImpl.syncSession(Compiled Code)
          at weblogic.servlet.internal.ServletContextImpl.invokeServlet(Compiled Code)
          at weblogic.servlet.internal.ServletContextImpl.invokeServlet(Compiled Code)
          at weblogic.servlet.internal.ServletContextManager.invokeServlet(Compiled Code)
          at weblogic.socket.MuxableSocketHTTP.invokeServlet(Compiled Code)
          at weblogic.socket.MuxableSocketHTTP.execute(Compiled Code)
          at weblogic.kernel.ExecuteThread.run(Compiled Code)
          

Answer 1

You should search in your log for message "Timed out server". If you see this,
          it means that your cluster is not healthy.
          Long gc is attributed to memory. If you don't have enough heap memory vm will
          take more time to do gc and during this time the server won't be able to do any
          work. If two servers are running gc's at different times, what you have is two
          servers in a cluster timing out each other at different times causing this
          problem to aggrevate.
          One way to solve the problem is by tuning the server so that you won't run into
          this problem.
          We designed the system differently to overcome this problem based on our
          experience with 4.5 and 5.1. It is not an easy thing to back port this change
          into a service pack.
          Yes, the fix to minimize the problem did go in 5.1
          Let me know if anything is unclear.
          Thanks
          - Prasad
          Joel Nylund wrote:
          > I have been working with weblogic support on this one for a while, they say
          > its fixed in 6.0 (which sucks for those of us still 4.5.1). They said it
          > happens less in sp13 for 4.51, im not sure if there is a similar patch for
          > 5.x. I would contact support. They say the reasons for this are one of :
          >
          > 1.) unreliable network
          > 2.) long gc loop or not enough memory (never understood this one)
          >
          > -Joel
          >
          > "Key Zhang" <[email protected]> wrote in message
          > news:[email protected]...
          > >
          > > Guess this is something to do with the servlet clustering configuration.
          > WLS(5.1, sp6) clustering run on Solaris 2.6 with jdk1.2.
          > >
          > >
          > > Do any one have any idea what could be the problems?
          > >
          > > =========================================================
          > > Mon Dec 11 15:58:19 EST 2000:<I> <ServletContext-General> Generated java
          > file: /home/weblogic/5.1/ourserver/cl
          > > assfiles/jsp_servlet/_html/_libraries/_vieworg.java
          > > Mon Dec 11 15:58:20 EST 2000:<E> <ServletContextManager> Servlet request
          > terminiated with Error
          > > weblogic.cluster.replication.BadStatusException: update found
          > 4586531668847271614 but it is not the secondary
          > > at java.lang.Throwable.fillInStackTrace(Native Method)
          > > at java.lang.Throwable.fillInStackTrace(Compiled Code)
          > > at weblogic.rmi.extensions.AbstractRequest.sendReceive(Compiled
          > Code)
          > > at
          > weblogic.cluster.replication.ReplicationManager_WLStub.update(Compiled Code)
          > > at
          > weblogic.cluster.replication.ReplicationManager.updateSecondary(Compiled
          > Code)
          > > at
          > weblogic.servlet.internal.session.ReplicatedSession.sync(Compiled Code)
          > > at
          > weblogic.servlet.internal.session.ReplicatedSessionContext.sync(Compiled
          > Code)
          > > at
          > weblogic.servlet.internal.ServletRequestImpl.syncSession(Compiled Code)
          > > at
          > weblogic.servlet.internal.ServletContextImpl.invokeServlet(Compiled Code)
          > > at
          > weblogic.servlet.internal.ServletContextImpl.invokeServlet(Compiled Code)
          > > at
          > weblogic.servlet.internal.ServletContextManager.invokeServlet(Compiled Code)
          > > at weblogic.socket.MuxableSocketHTTP.invokeServlet(Compiled Code)
          > > at weblogic.socket.MuxableSocketHTTP.execute(Compiled Code)
          > > at weblogic.kernel.ExecuteThread.run(Compiled Code)
          > > --------------- nested within: ------------------
          > > weblogic.utils.NestedError: Tried to update secondary, but it thought it
          > was the primary - with nested exceptio
          > > n:
          > > [weblogic.cluster.replication.BadStatusException: update found
          > 4586531668847271614 but it is not the secondary]
          > > at java.lang.Throwable.fillInStackTrace(Native Method)
          > > at java.lang.Throwable.fillInStackTrace(Compiled Code)
          > > at java.lang.Throwable.<init>(Compiled Code)
          > > at java.lang.Error.<init>(Error.java:50)
          > > at weblogic.utils.NestedError.<init>(NestedError.java:23)
          > > at
          > weblogic.servlet.internal.session.ReplicatedSession.sync(Compiled Code)
          > > at
          > weblogic.servlet.internal.session.ReplicatedSessionContext.sync(Compiled
          > Code)
          > > at
          > weblogic.servlet.internal.ServletRequestImpl.syncSession(Compiled Code)
          > > at
          > weblogic.servlet.internal.ServletContextImpl.invokeServlet(Compiled Code)
          > > at
          > weblogic.servlet.internal.ServletContextImpl.invokeServlet(Compiled Code)
          > > at
          > weblogic.servlet.internal.ServletContextManager.invokeServlet(Compiled Code)
          > > at weblogic.socket.MuxableSocketHTTP.invokeServlet(Compiled Code)
          > > at weblogic.socket.MuxableSocketHTTP.execute(Compiled Code)
          > > at weblogic.kernel.ExecuteThread.run(Compiled Code)
          > >