BadStatusException??

Occasionally, we see this message in the standard out of our weblogic
          server. Can somebody tell us what causes it and what it means? does this
          message imply that our clustering and failover are not working at that time?
          *********** weblogic.utils.NestedError: Tried to update secondary, but it
          thought it was the primary
          - with nested exception:
          [weblogic.cluster.replication.BadStatusException: update found
          6145760147735768432 but it is not the secondary]
          Our environment: A weblogic cluster with 4 Sun solaris servers.
          Thanks,
          Srikanth Meenakshi
          

We are experiencing the same error in SP 5 on Win NT. And so far we are
          unable to trace the cause of this message. Also due to this our http
          sessions get messed up.
          "Srikanth Meenakshi" <[email protected]> wrote in message
          news:39b4f71a$[email protected]..
          > Occasionally, we see this message in the standard out of our weblogic
          > server. Can somebody tell us what causes it and what it means? does this
          > message imply that our clustering and failover are not working at that
          time?
          >
          > *********** weblogic.utils.NestedError: Tried to update secondary, but it
          > thought it was the primary
          > - with nested exception:
          > [weblogic.cluster.replication.BadStatusException: update found
          > 6145760147735768432 but it is not the secondary]
          >
          > Our environment: A weblogic cluster with 4 Sun solaris servers.
          >
          > --
          > Thanks,
          >
          > Srikanth Meenakshi
          >
          >
          >
          

Similar Messages

  • Replication.BadStatusException

    hi.
              i get the following message in one of two WLS..
              what's wrong?
              please help me
              =================================================
              ¸ñ 4¿ù 19 13:00:57 GMT+09:00 2001:<I> <ServletContext-General> Generated
              java fi
              le: D:\weblogic\tmcluster\classfiles\jsp_servlet\_admin\_adm_loc_lst_sa.java
              ¸ñ 4¿ù 19 13:01:07 GMT+09:00 2001:<E> <ServletContextManager> Servlet
              request te
              rminiated with Error
              weblogic.cluster.replication.BadStatusException: update found
              917260360549924503
              but it is not the secondary
              at
              weblogic.rmi.extensions.AbstractRequest.sendReceive(AbstractRequest.j
              ava, Compiled Code)
              at
              weblogic.cluster.replication.ReplicationManager_WLStub.update(Replica
              tionManager_WLStub.java:181)
              at
              weblogic.cluster.replication.ReplicationManager.updateSecondary(Repli
              cationManager.java, Compiled Code)
              at
              weblogic.servlet.internal.session.ReplicatedSession.sync(ReplicatedSe
              ssion.java, Compiled Code)
              at
              weblogic.servlet.internal.session.ReplicatedSessionContext.sync(Repli
              catedSessionContext.java, Compiled Code)
              at
              weblogic.servlet.internal.ServletRequestImpl.syncSession(ServletReque
              stImpl.java, Compiled Code)
              at
              weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletCon
              textImpl.java, Compiled Code)
              at
              weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletCon
              textImpl.java, Compiled Code)
              at
              weblogic.servlet.internal.ServletContextManager.invokeServlet(Servlet
              ContextManager.java, Compiled Code)
              at
              weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.jav
              a, Compiled Code)
              at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java,
              Com
              piled Code)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled
              Code)
              --------------- nested within: ------------------
              weblogic.utils.NestedError: Tried to update secondary, but it thought it was
              the
              primary - with nested exception:
              [weblogic.cluster.replication.BadStatusException: update found
              91726036054992450
              3 but it is not the secondary]
              at
              weblogic.servlet.internal.session.ReplicatedSession.sync(ReplicatedSe
              ssion.java, Compiled Code)
              at
              weblogic.servlet.internal.session.ReplicatedSessionContext.sync(Repli
              catedSessionContext.java, Compiled Code)
              at
              weblogic.servlet.internal.ServletRequestImpl.syncSession(ServletReque
              stImpl.java, Compiled Code)
              at
              weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletCon
              textImpl.java, Compiled Code)
              at
              weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletCon
              textImpl.java, Compiled Code)
              at
              weblogic.servlet.internal.ServletContextManager.invokeServlet(Servlet
              ContextManager.java, Compiled Code)
              at
              weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.jav
              a, Compiled Code)
              at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java,
              Com
              piled Code)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled
              Code)
              

    This has been discussed/answered several times in this newsgroup
              FYI, i'm posting it again.
              The exception under question is BadStatusException and the explanation that I
              have is:
              If a server hangs for some reason and fails to send 3 heartbeats ( in an
              interval of 10 seconds), the other servers
              in cluster declare him dead. The secondary server for the HTTP sessions for
              which this server was primary
              designates itself primary for those HTTP Sessions. When this server later joins
              the cluster, he is unaware of
              the fact that other servers declare him dead and refuses to be secondary of
              sessions for which , he thinks, that he is
              primary and then you get BadStatusException.
              Before getting this BadStatusException , you should see the following message in
              Mon Apr 16 11:27:18 CDT 2001:<I> <Cluster> Timed out server
              The definition of hang/timeout as far as this is concerned is:
              1. Garbage Collection taking more time than it should.
              For 1) Since the GC runs in a high priority thread, until GC comes out of the
              loop, we cannot do anything.
              To find out if this is a GC problem or a WLS issue, you need to turn on the
              verbosegc flag (for 1.3 it is -verbose:gc)
              and re-direct the gc output to the weblogic.log ,so that we can see if GC is
              taking more than 30 secs before the servers
              being timed out.
              Also if you are using JVM 1.3 has some options, where you can set incremental
              garbage collection, incrementing
              the max heap size, maxPermSize etc...
              i would suggest you to checkout the following page and see if that helps..
              http://java.sun.com/docs/hotspot/VMOptions.html
              contact support for further analysis..
              Kumar
              kang seung il wrote:
              > hi.
              > i get the following message in one of two WLS..
              > what's wrong?
              > please help me
              > =================================================
              >
              > ¸ñ 4¿ù 19 13:00:57 GMT+09:00 2001:<I> <ServletContext-General> Generated
              > java fi
              > le: D:\weblogic\tmcluster\classfiles\jsp_servlet\_admin\_adm_loc_lst_sa.java
              > ¸ñ 4¿ù 19 13:01:07 GMT+09:00 2001:<E> <ServletContextManager> Servlet
              > request te
              > rminiated with Error
              > weblogic.cluster.replication.BadStatusException: update found
              > 917260360549924503
              > but it is not the secondary
              > at
              > weblogic.rmi.extensions.AbstractRequest.sendReceive(AbstractRequest.j
              > ava, Compiled Code)
              > at
              > weblogic.cluster.replication.ReplicationManager_WLStub.update(Replica
              > tionManager_WLStub.java:181)
              > at
              > weblogic.cluster.replication.ReplicationManager.updateSecondary(Repli
              > cationManager.java, Compiled Code)
              > at
              > weblogic.servlet.internal.session.ReplicatedSession.sync(ReplicatedSe
              > ssion.java, Compiled Code)
              > at
              > weblogic.servlet.internal.session.ReplicatedSessionContext.sync(Repli
              > catedSessionContext.java, Compiled Code)
              > at
              > weblogic.servlet.internal.ServletRequestImpl.syncSession(ServletReque
              > stImpl.java, Compiled Code)
              > at
              > weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletCon
              > textImpl.java, Compiled Code)
              > at
              > weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletCon
              > textImpl.java, Compiled Code)
              > at
              > weblogic.servlet.internal.ServletContextManager.invokeServlet(Servlet
              > ContextManager.java, Compiled Code)
              > at
              > weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.jav
              > a, Compiled Code)
              > at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java,
              > Com
              > piled Code)
              > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled
              > Code)
              > --------------- nested within: ------------------
              > weblogic.utils.NestedError: Tried to update secondary, but it thought it was
              > the
              > primary - with nested exception:
              > [weblogic.cluster.replication.BadStatusException: update found
              > 91726036054992450
              > 3 but it is not the secondary]
              > at
              > weblogic.servlet.internal.session.ReplicatedSession.sync(ReplicatedSe
              > ssion.java, Compiled Code)
              > at
              > weblogic.servlet.internal.session.ReplicatedSessionContext.sync(Repli
              > catedSessionContext.java, Compiled Code)
              > at
              > weblogic.servlet.internal.ServletRequestImpl.syncSession(ServletReque
              > stImpl.java, Compiled Code)
              > at
              > weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletCon
              > textImpl.java, Compiled Code)
              > at
              > weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletCon
              > textImpl.java, Compiled Code)
              > at
              > weblogic.servlet.internal.ServletContextManager.invokeServlet(Servlet
              > ContextManager.java, Compiled Code)
              > at
              > weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.jav
              > a, Compiled Code)
              > at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java,
              > Com
              > piled Code)
              > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled
              > Code)
              

  • Multiple clusters on a single machine

    Hi everyone. I have a question about running 2 clusters on a same
              machine.
              Here's the scenario. We have 8 WebLogic server (4.5.1 SP4) instances
              running on
              2 servers (Sun Enterprise 5500/Solaris 2.62) right now for one of our
              eCommerce
              application.
              Now we are getting ready to deploy a 2nd application and we want it to
              have its
              own cluster. So we are hoping to run 4 more WebLogic servers on each of
              the 2
              machines. So machine #1 would have 4 WebLogic servers for cluster A and
              4
              WebLogic servers for cluster B. And machine #2 will have 4 WebLogic
              servers for
              cluster A and 4 WebLogic servers for cluster B.
              All of these servers have unique IP address and each cluster has a
              different
              name and multicast IP address. Both clusters are using in-memory
              replication.
              On both machines, each of the cluster member will share the same global
              weblogic.properties file. The cluster specific portion resides in the
              cluster
              directory.
              Is anyone currently running such a configuration?? Is there something
              we should
              worry about?? Since both of these servers are in their own isolate
              network
              segment, is there any danger of multicast broadcast bleeding into the
              different
              cluster?? Thanks in advance.
              

    Hi Michael and thanks.. No, this is 2 systems on the same network and not two
              independent networks. Here's what I found that's very strange. I started
              server 1 ->4 for the first cluster and everything worked fine. Now I started
              server 5 on the first machine that's in a different cluster and has a totally
              different multicast IP address and yet, server 1 of the first cluster recorded
              server 5 joining the cluster. Server 2, 3 and 4 of the first cluster did not
              have RJVM 'Creating connection' message in there.
              On server 5's startup, server 1 decided to make server 5 it's secondary pair and
              I get the following error as server 5 does not have the same code for cluster1.
              After that error, I started getting tons of
              weblogic.cluster.replication.BadStatusException error in the logs for server 1
              listed below. I'm sure running multiple clusters off an enterprise level
              server is something people want to do. Is this a known issue?? Is this a bug
              in the server or the VM?
              Our environment: Sun 5500 Enterprise servers running Solaris 2.62, WebLogic
              4.5.1 SP4.
              Sun Jan 09 15:19:40 CST 2000:<I> <RJVM> Creating connection to
              stingray05.xx.com/10.x.x.x t3:7001 http:7001 t3s:7002 https:7002
              -1353087187406741800
              Sun Jan 09 15:19:41 CST 2000:<E> <MulticastSocket> Multicast socket receive
              error:
              Sun Jan 09 15:19:41 CST 2000:<E> <MulticastSocket>
              java.lang.ClassNotFoundException: Could not instantiate new instance of
              [com.strong.brokerage.server.CustomerSessionBeanHomeImpl_WLStub]
              Either the class is missing from classpath, the class does not have a public
              constructor, or the constructor raised an error; the actual exception was a :
              java.lang.NoClassDefFoundError: com.strong.brokerage.common.util.RegistrationCtx
              at java.lang.Throwable.<init>(Compiled Code)
              at java.lang.Exception.<init>(Compiled Code)
              at java.lang.ClassNotFoundException.<init>(Compiled Code)
              at
              weblogic.common.internal.WLObjectInputStreamBase.readLeftover(Compiled Code)
              at
              weblogic.common.internal.WLObjectInputStreamBase.readObjectBody(Compiled Code)
              at weblogic.common.internal.WLObjectInputStreamBase.readObject(Compiled
              Code)
              at
              weblogic.common.internal.WLObjectInputStreamBase.readObjectWL(Compiled Code)
              at weblogic.service.ReplicaAggregate.readExternal(Compiled Code)
              at
              weblogic.common.internal.WLObjectInputStreamBase.readPublicSerializable(Compiled
              Code)
              at
              weblogic.common.internal.WLObjectInputStreamBase.readLeftover(Compiled Code)
              at
              weblogic.common.internal.WLObjectInputStreamBase.readObjectBody(Compiled Code)
              at weblogic.common.internal.WLObjectInputStreamBase.readObject(Compiled
              Code)
              at
              weblogic.common.internal.WLObjectInputStreamBase.readObjectWL(Compiled Code)
              at weblogic.cluster.BasicServiceOffer.readObject(Compiled Code)
              at weblogic.cluster.AnnotatedServiceOffer.readObject(Compiled Code)
              at
              weblogic.common.internal.WLObjectInputStreamBase.readPublicSerializable(Compiled
              Code)
              at
              weblogic.common.internal.WLObjectInputStreamBase.readLeftover(Compiled Code)
              at
              weblogic.common.internal.WLObjectInputStreamBase.readObjectBody(Compiled Code)
              at weblogic.common.internal.WLObjectInputStreamBase.readObject(Compiled
              Code)
              at
              weblogic.common.internal.WLObjectInputStreamBase.readObjectWL(Compiled Code)
              at
              weblogic.common.internal.WLObjectInputStreamBase.readArrayList(Compiled Code)
              at weblogic.cluster.Announcement.readObject(Compiled Code)
              at
              weblogic.common.internal.WLObjectInputStreamBase.readPublicSerializable(Compiled
              Code)
              at
              weblogic.common.internal.WLObjectInputStreamBase.readLeftover(Compiled Code)
              at
              weblogic.common.internal.WLObjectInputStreamBase.readObjectBody(Compiled Code)
              at weblogic.common.internal.WLObjectInputStreamBase.readObject(Compiled
              Code)
              at
              weblogic.common.internal.WLObjectInputStreamBase.readObjectWL(Compiled Code)
              at weblogic.cluster.TMSocket.execute(Compiled Code)
              at weblogic.t3.srvr.ExecuteThread.run(Compiled Code)
              Sun Jan 09 15:24:42 CST 2000:<E> <HTTP> Servlet request terminiated with Error:
              Sun Jan 09 15:24:42 CST 2000:<E> <HTTP>
              weblogic.cluster.replication.BadStatusException: update found
              -5050872662681587012 but it is not the secondary
              at weblogic.rmi.extensions.BasicRequest.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.ServletStubImpl.invokeServlet(Compiled
              Code)
              at weblogic.servlet.internal.ServletContextImpl.invokeServlet(Compiled
              Code)
              at weblogic.servlet.internal.ServletContextImpl.invokeServlet(Compiled
              Code)
              at weblogic.socket.MuxableSocketHTTP.invokeServlet(Compiled Code)
              at weblogic.socket.MuxableSocketHTTP.execute(Compiled Code)
              at weblogic.t3.srvr.ExecuteThread.run(Compiled Code)
              --------------- nested within: ------------------
              weblogic.utils.NestedError: Tried to update secondary, but it thought it was the
              primary
              - with nested exception:
              [weblogic.cluster.replication.BadStatusException: update found
              -5050872662681587012 but it is not the secondary]
              at java.lang.Throwable.<init>(Compiled Code)
              at java.lang.Error.<init>(Compiled Code)
              at weblogic.utils.NestedError.<init>(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.ServletStubImpl.invokeServlet(Compiled
              Code)
              at weblogic.servlet.internal.ServletContextImpl.invokeServlet(Compiled
              Code)
              at weblogic.servlet.internal.ServletContextImpl.invokeServlet(Compiled
              Code)
              at weblogic.socket.MuxableSocketHTTP.invokeServlet(Compiled Code)
              at weblogic.socket.MuxableSocketHTTP.execute(Compiled Code)
              at weblogic.t3.srvr.ExecuteThread.run(Compiled Code)
              Michael Girdley wrote:
              > Vinny,
              >
              > It sounds like the real hard problem here is a system administration and
              > configuration issue. If you have two independent networks with independent
              > systems, then you should not have a problem running two clusters across two
              > machines. You just need to make sure that your routing for multicast is
              > appropriately configured so that they don't confuse the two different
              > WebLogic server clusters.
              >
              > I hope this helps. I might also recommend contacting our sales organization
              > who can put you in touch with a systems engineer who is a professional at
              > making these types are recommendations.
              >
              > Thanks!
              >
              > --
              > Michael Girdley
              > BEA Product Manager
              >
              > Vinny Carpenter <[email protected]> wrote in message
              > news:[email protected]...
              > > Hi everyone. I have a question about running 2 clusters on a same
              > > machine.
              > > Here's the scenario. We have 8 WebLogic server (4.5.1 SP4) instances
              > > running on
              > > 2 servers (Sun Enterprise 5500/Solaris 2.62) right now for one of our
              > > eCommerce
              > > application.
              > >
              > > Now we are getting ready to deploy a 2nd application and we want it to
              > > have its
              > > own cluster. So we are hoping to run 4 more WebLogic servers on each of
              > > the 2
              > > machines. So machine #1 would have 4 WebLogic servers for cluster A and
              > > 4
              > > WebLogic servers for cluster B. And machine #2 will have 4 WebLogic
              > > servers for
              > > cluster A and 4 WebLogic servers for cluster B.
              > >
              > > All of these servers have unique IP address and each cluster has a
              > > different
              > > name and multicast IP address. Both clusters are using in-memory
              > > replication.
              > > On both machines, each of the cluster member will share the same global
              > > weblogic.properties file. The cluster specific portion resides in the
              > > cluster
              > > directory.
              > >
              > > Is anyone currently running such a configuration?? Is there something
              > > we should
              > > worry about?? Since both of these servers are in their own isolate
              > > network
              > > segment, is there any danger of multicast broadcast bleeding into the
              > > different
              > > cluster?? Thanks in advance.
              > >
              > >
              > >
              > >
              

  • Timed Out Server

    Hello,
              I have tried SP5, but I still have some problems and
              questions...........could someone pls answer these, so that I know if
              this is some known problem with the product, or some configuration
              issue, or if anyone has seen some similar problems.........
              Q:
              What does the following property mean, and what should a reasonable
              value be for it :
              --> ISSUE 31575: A new multicast property
              ("weblogic.cluster.multicastSendDelay") which handles
              the buffer overflow properties has been added.
              Q:
              What does the time-out in the ClusterManager represent, and is it some
              default value, or can it be configured ? Also, is it related to the
              Timed Out SErver error that I mention below?
              -->ISSUE 30924: Enhanced timeout in ClusterManager and fixed a problem
              with servers not shutting down.
              Q: What is written below is not clear to me....is it saying that now
              there should be a message of the type : "Creating RemoteMemberInfo for"
              + configdetails ??
              I have applied SP5, and also checked it with the weblogic.Admin utility,
              and no SP4 file is there anymore, but I am still getting the older
              "Joined cluster mycluster at address 224.0.0.1:7001"
              message.............
              -->ISSUE 32054:
              Improved log notification when a server is aware of other servers in the
              cluster. The string looks like: "Creating RemoteMemberInfo for" +
              configdetails. In
              general, when using WebLogic Server 4.0.X through 5.1.X, the message of
              "Joined cluster mycluster at address 224.0.0.1:7001", does not
              necessarily mean
              that there is anyone else in the cluster. In 4.5 you could tell when
              there was really another server in the cluster by the server to server
              RJVM messages when
              each node found the others. But, in 5.1 this became no longer possible.
              This change improves the log notification and solves this problem.
              Q: How does one turn on the debug flag with the IIS plug in ? Is it
              mentioned in the iisproxy.ini file ? I couldn't find anything like this
              in the admin docs for plug-in configuration ........
              -->ISSUE 28929: Added the ability to have Debug flags with
              NSAPI/ISAPI/ASAPI plug-ins. Now Debug flags can be turned on in the
              configuration file of the plug-in.
              PROBLEM:
              When both of the servers in the cluster are brought up, and they start
              receiving requests, the following happens for some time on one server,
              till which time apparently both share the load....
              Mo Aug 22 12:32:39 GMT+02:00 2000:<I> <Cluster> memberPresent
              -68329250512188744
              40S134.28.77.101:[7001,7001,7002,7002,7001,-1]
              Mo Aug 22 12:32:46 GMT+02:00 2000:<I> <Cluster> memberPresent
              -68329250512188744
              40S134.28.77.101:[7001,7001,7002,7002,7001,-1]
              Mo Aug 22 12:32:56 GMT+02:00 2000:<I> <ServletContext-General> file:
              init
              Mo Aug 22 12:33:26 GMT+02:00 2000:<I> <Cluster> Timed out server
              then the other server stops taking any load and all requests go to this
              server............However, if this servlet is brought down, the other
              takes over the load...........
              however, bringing up a new server in the cluster, or reviving the one
              brought down, the following happens :
              weblogic.utils.NestedError: Tried to update secondary, but it thought it
              was the primary - with nested exception:
              [weblogic.cluster.replication.BadStatusException: update found
              -1286423340868561093 but it is not the secondary]
              the member present messages appear again for some time, and then again
              there is the Timed Out Server message.......though all of this happens
              pretty randomly at this stage, but the problem is consistent...........
              If someone has any ideas, pls let me know.........
              environment:
              2 servers in a cluster with NT...........IIS proxy..........
              regards,
              farhat
              

    Hello,
              I have tried SP5, but I still have some problems and
              questions...........could someone pls answer these, so that I know if
              this is some known problem with the product, or some configuration
              issue, or if anyone has seen some similar problems.........
              Q:
              What does the following property mean, and what should a reasonable
              value be for it :
              --> ISSUE 31575: A new multicast property
              ("weblogic.cluster.multicastSendDelay") which handles
              the buffer overflow properties has been added.
              Q:
              What does the time-out in the ClusterManager represent, and is it some
              default value, or can it be configured ? Also, is it related to the
              Timed Out SErver error that I mention below?
              -->ISSUE 30924: Enhanced timeout in ClusterManager and fixed a problem
              with servers not shutting down.
              Q: What is written below is not clear to me....is it saying that now
              there should be a message of the type : "Creating RemoteMemberInfo for"
              + configdetails ??
              I have applied SP5, and also checked it with the weblogic.Admin utility,
              and no SP4 file is there anymore, but I am still getting the older
              "Joined cluster mycluster at address 224.0.0.1:7001"
              message.............
              -->ISSUE 32054:
              Improved log notification when a server is aware of other servers in the
              cluster. The string looks like: "Creating RemoteMemberInfo for" +
              configdetails. In
              general, when using WebLogic Server 4.0.X through 5.1.X, the message of
              "Joined cluster mycluster at address 224.0.0.1:7001", does not
              necessarily mean
              that there is anyone else in the cluster. In 4.5 you could tell when
              there was really another server in the cluster by the server to server
              RJVM messages when
              each node found the others. But, in 5.1 this became no longer possible.
              This change improves the log notification and solves this problem.
              Q: How does one turn on the debug flag with the IIS plug in ? Is it
              mentioned in the iisproxy.ini file ? I couldn't find anything like this
              in the admin docs for plug-in configuration ........
              -->ISSUE 28929: Added the ability to have Debug flags with
              NSAPI/ISAPI/ASAPI plug-ins. Now Debug flags can be turned on in the
              configuration file of the plug-in.
              PROBLEM:
              When both of the servers in the cluster are brought up, and they start
              receiving requests, the following happens for some time on one server,
              till which time apparently both share the load....
              Mo Aug 22 12:32:39 GMT+02:00 2000:<I> <Cluster> memberPresent
              -68329250512188744
              40S134.28.77.101:[7001,7001,7002,7002,7001,-1]
              Mo Aug 22 12:32:46 GMT+02:00 2000:<I> <Cluster> memberPresent
              -68329250512188744
              40S134.28.77.101:[7001,7001,7002,7002,7001,-1]
              Mo Aug 22 12:32:56 GMT+02:00 2000:<I> <ServletContext-General> file:
              init
              Mo Aug 22 12:33:26 GMT+02:00 2000:<I> <Cluster> Timed out server
              then the other server stops taking any load and all requests go to this
              server............However, if this servlet is brought down, the other
              takes over the load...........
              however, bringing up a new server in the cluster, or reviving the one
              brought down, the following happens :
              weblogic.utils.NestedError: Tried to update secondary, but it thought it
              was the primary - with nested exception:
              [weblogic.cluster.replication.BadStatusException: update found
              -1286423340868561093 but it is not the secondary]
              the member present messages appear again for some time, and then again
              there is the Timed Out Server message.......though all of this happens
              pretty randomly at this stage, but the problem is consistent...........
              If someone has any ideas, pls let me know.........
              environment:
              2 servers in a cluster with NT...........IIS proxy..........
              regards,
              farhat
              

  • DGCServer messages in log... "tried to renew lease"

    Hi,
              I'm running three WL 4.5.2 servers clustered, JDK1.1.7b on Solaris 2.6.
              Normally the cluster runs just fine, but now I'm beginning to see the
              following message in all three servers:
              <DGCserver> tried to renew lease for lost ref: nnn
              Usually they come in small bursts of about 5 or 10 messages that are the
              same, except the "ref"s keep increasing. I'm guessing it has to do something
              with the in-memory replication of sessions (which I'm using).
              Any ideas? I tried restarting the servers but after a little while the
              messages started again.
              Thanks,
              Matias
              

    One common symptom for this (Bad Status Exception) has been long gc. If gc
              takes more 30 seconds then you will start seeing these errors. To assertain
              this, you could turn on weblogic.debug.cluster=1 and if you see a message "Timed
              out server" in the log then you should tune your server.
              Please use latest service packs.
              thanks
              - Prasad
              Matias Pelenur wrote:
              > Well, after a few restarts the DGC messages aren't appearing anymore... But
              > something different is happening now which seems to be worse... And it's
              > affecting performance too. For some pages, one of the servers will throw a
              > bunch of exceptions (see below), and it seems it's cutting off the output so
              > pages get only half-created. Any ideas? I don't think I changed any settings
              > or anything like that.
              >
              > Thanks,
              > Matias
              >
              > Fri Sep 15 11:19:15 EDT 2000:<E> <HTTP> Servlet request terminiated with
              > Error:
              > Fri Sep 15 11:19:15 EDT 2000:<E> <HTTP>
              > weblogic.cluster.replication.BadStatusException: update found
              > 1802540915606489052 but it is not the secondary
              > at weblogic.rmi.extensions.BasicRequest.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.socket.MuxableSocketHTTP.invokeServlet(Compiled Code)
              > at weblogic.socket.MuxableSocketHTTP.execute(Compiled Code)
              > at weblogic.t3.srvr.ExecuteThread.run(Compiled Code)
              > --------------- nested within: ------------------
              > weblogic.utils.NestedError: Tried to update secondary, but it thought it was
              > the primary
              > - with nested exception:
              > [weblogic.cluster.replication.BadStatusException: update found
              > 18025409156064890
              > 52 but it is not the secondary]
              > at java.lang.Throwable.<init>(Compiled Code)
              > at java.lang.Error.<init>(Compiled Code)
              > at weblogic.utils.NestedError.<init>(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.socket.MuxableSocketHTTP.invokeServlet(Compiled Code)
              > at weblogic.socket.MuxableSocketHTTP.execute(Compiled Code)
              > at weblogic.t3.srvr.ExecuteThread.run(Compiled Code)
              >
              > "Prasad Peddada" <[email protected]> wrote in message
              > news:[email protected]...
              > > Is this causing any problems on the server. Like unable to create sessions
              > for
              > > servlets/jsp's
              > >
              > > If so, this is related to DGC bug, if not then it is something else,
              > unless we
              > > know the object it is trying to find, I can't be of much help.
              > >
              > > - Prasad
              > >
              > > Matias Pelenur wrote:
              > >
              > > > Hi,
              > > > I'm running three WL 4.5.2 servers clustered, JDK1.1.7b on Solaris 2.6.
              > > >
              > > > Normally the cluster runs just fine, but now I'm beginning to see the
              > > > following message in all three servers:
              > > >
              > > > <DGCserver> tried to renew lease for lost ref: nnn
              > > >
              > > > Usually they come in small bursts of about 5 or 10 messages that are the
              > > > same, except the "ref"s keep increasing. I'm guessing it has to do
              > something
              > > > with the in-memory replication of sessions (which I'm using).
              > > >
              > > > Any ideas? I tried restarting the servers but after a little while the
              > > > messages started again.
              > > > Thanks,
              > > >
              > > > Matias
              > >
              Cheers
              - Prasad
              

  • Strange errors in session replication

              I get following errors in session replication :
              weblogic.utils.NestedError: Tried to update secondary, but it thought
              it was the primary
              - with nested exception:
              [weblogic.cluster.replication.BadStatusException: updateSecondary
              found
                  -148099416498695151 but it is not the primary]
              Using Weblogic451, SP7 on Solaris 2.6.
              Any clues ??
              -Kuntal Shah.
              

    Hello,
              > > Alteon is set to use "permanent hashing" to route the client into
              > > the same server in each request.
              >
              > How do you expect the switch to know about the secondary node
              > if the primary fails? This information is stored in the URL and
              > parsed by a proxy.
              It took a couple of days and fair amount of documentation to understand
              the behaviour of the web cluster...;-)
              We changed the configuration to include two proxy servers between the
              Alteon switch and web cluster, but we ended up with a different problem.
              The setup at the moment is:
              - Sun Solaris 2.6, native threads, JDK 1.1.7B_008
              - two WLS 4.51 SP7 running in cluster using in-memory replication
              - only servlets deployed in the servers
              - Two WLS proxies between the webcluster and alteon switch. Both proxies are
              configured to use both of the web servers. they do not belong to the web
              cluster.
              The proxies are configured in the following way:
              weblogic.httpd.session.enable=true
              weblogic.httpd.session.timeoutSecs=1800
              weblogic.httpd.session.invalidationIntervalSecs=600
              weblogic.httpd.session.URLRewriting.enable=true
              weblogic.httpd.session.cookies.enable=true
              weblogic.httpd.session.cookie.maxAgeSecs=-1
              weblogic.httpd.session.cookie.domain=some.domain.name
              weblogic.httpd.register.cluster=weblogic.servlet.internal.HttpClusterServlet
              weblogic.httpd.initArgs.cluster=defaultServers=x.y.z.a1:9001|x.y.z.a2:9001
              weblogic.httpd.defaultServlet=cluster
              weblogic.allow.execute.weblogic.servlet=everyone
              Probably most of the configuration parameters are not necessary, can
              somebody tell me which are
              and which are not?
              The servers in the web cluster are configured in the following way:
              The following parameters are in the start-up script of the servers:
              -Dweblogic.cluster.enable=true \
              -Dweblogic.system.name=somehost \
              -Dweblogic.cluster.name=someclustercluster \
              -Dweblogic.cluster.multicastAddress=237.0.0.1 \
              -Dweblogic.system.bindAddr=x.y.z.a1 \
              -Dweblogic.system.nativeIO.enable=true \
              -Dweblogic.debug.replication=1 \
              And the following are in the cluster-wide properties file:
              weblogic.httpd.clustering.enable=true
              weblogic.httpd.session.persistence=true
              weblogic.httpd.session.persistentStoreType=replicated
              weblogic.httpd.session.enable=true
              weblogic.httpd.session.timeoutSecs=1800
              weblogic.httpd.session.invalidationIntervalSecs=600
              weblogic.httpd.session.URLRewriting.enable=true
              weblogic.httpd.session.cookies.enable=true
              weblogic.httpd.session.cookie.domain=some.domain.name
              The IP-address of the Alteon box in front of the proxies is bound to
              'some.domain.name'.
              The first problem seems to be very poor performance. The overall throughtput
              is vveeeerrryyy slow, comparing
              to the configuration where there is no proxy sitting in front of the
              cluster. Furthermore, at some stage the proxy
              starts to print out error messages: java.lang.InvalidStateException: broken
              pipe [...] . After those exceptions no
              client get any response anymore.
              Could someone give some hints what are the most essential items in the
              weblogic.properties -file for the
              proxy server? Also, if someone has some experience from setting up a
              configuration similar to ours: one hardware
              load-balancer in front of two proxies, and eventually two web servers
              running in a web cluster.
              Cheers,
              Jarno.
              

  • Servlet error in clustering env.

              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)
              

    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)
              > >
              

  • Exception from clustering complain about session duplication

    I have seen this when I using Web Application Stress test tool against my 2
              server clustering, on both NT and solaris
              JDK1.2.1(sun) JDK1.2.2(NT) weblogic 5.1 SP8. oracle(soalris) and
              sqlserver(NT).
              Tue Feb 06 12:07:23 EST 2001:<E> <ServletContextManager> Servlet request
              terminiated with Error
              weblogic.cluster.replication.BadStatusException: update
              found -6410509522137925236 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)
              

              I found your message but it does not explain how to resolve the issue. Any ideas?
              Best,
              Atanas
              Kumar Allamraju <[email protected]> wrote:
              >I have posted the explanation for "BadStatusExceptin" a while ago. Pls search
              >past newsgroups and if
              >you can't find it re-post here.
              >
              >--
              >Kumar
              >
              >Tony Lu wrote:
              >
              >> I have seen this when I using Web Application Stress test tool against
              >my 2
              >> server clustering, on both NT and solaris
              >> JDK1.2.1(sun) JDK1.2.2(NT) weblogic 5.1 SP8. oracle(soalris) and
              >> sqlserver(NT).
              >>
              >> Tue Feb 06 12:07:23 EST 2001:<E> <ServletContextManager> Servlet request
              >> terminiated with Error
              >> weblogic.cluster.replication.BadStatusException: update
              >> found -6410509522137925236 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)
              >
              

  • BadStatus exception

    On W2k, WLS 5.1 SP5, iisproxy.dll is also from SP5:
              weblogic.cluster.replication.BadStatusException: update found 1734651660520697017 but it is not the secondary
              at weblogic.rmi.extensions.AbstractRequest.sendReceive(AbstractRequest.java:76)
              at weblogic.cluster.replication.ReplicationManager_WLStub.update(ReplicationManager_WLStub.java:181)
              at weblogic.cluster.replication.ReplicationManager.updateSecondary(ReplicationManager.java:664)
              at weblogic.servlet.internal.session.ReplicatedSession.sync(ReplicatedSession.java:365)
              at weblogic.servlet.internal.session.ReplicatedSessionContext.sync(ReplicatedSessionContext.java:59)
              at weblogic.servlet.internal.ServletRequestImpl.syncSession(ServletRequestImpl.java:1198)
              at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:789)
              at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:707)
              at weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:251)
              at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:369)
              at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:269)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:135)
              --------------- nested within: ------------------
              weblogic.utils.NestedError: Tried to update secondary, but it thought it was the primary - with nested excepti
              on:
              [weblogic.cluster.replication.BadStatusException: update found 1734651660520697017 but it is not the secondary
              at weblogic.servlet.internal.session.ReplicatedSession.sync(ReplicatedSession.java:371)
              at weblogic.servlet.internal.session.ReplicatedSessionContext.sync(ReplicatedSessionContext.java:59)
              at weblogic.servlet.internal.ServletRequestImpl.syncSession(ServletRequestImpl.java:1198)
              at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:789)
              Dimitri
              http://dima.dhs.org
              

    On W2k, WLS 5.1 SP5, iisproxy.dll is also from SP5:
              weblogic.cluster.replication.BadStatusException: update found 1734651660520697017 but it is not the secondary
              at weblogic.rmi.extensions.AbstractRequest.sendReceive(AbstractRequest.java:76)
              at weblogic.cluster.replication.ReplicationManager_WLStub.update(ReplicationManager_WLStub.java:181)
              at weblogic.cluster.replication.ReplicationManager.updateSecondary(ReplicationManager.java:664)
              at weblogic.servlet.internal.session.ReplicatedSession.sync(ReplicatedSession.java:365)
              at weblogic.servlet.internal.session.ReplicatedSessionContext.sync(ReplicatedSessionContext.java:59)
              at weblogic.servlet.internal.ServletRequestImpl.syncSession(ServletRequestImpl.java:1198)
              at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:789)
              at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:707)
              at weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:251)
              at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:369)
              at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:269)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:135)
              --------------- nested within: ------------------
              weblogic.utils.NestedError: Tried to update secondary, but it thought it was the primary - with nested excepti
              on:
              [weblogic.cluster.replication.BadStatusException: update found 1734651660520697017 but it is not the secondary
              at weblogic.servlet.internal.session.ReplicatedSession.sync(ReplicatedSession.java:371)
              at weblogic.servlet.internal.session.ReplicatedSessionContext.sync(ReplicatedSessionContext.java:59)
              at weblogic.servlet.internal.ServletRequestImpl.syncSession(ServletRequestImpl.java:1198)
              at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:789)
              Dimitri
              http://dima.dhs.org
              

Maybe you are looking for

  • Arabic text transformation

    Hello, i ve got a problem with the way Illustrator shows arabic text, can someone please help?. I'm using Arabic keyboard (http://www.arabe-clavier.com/arabic-keyboard/) online app to write arabic text, since we don`t use arabic keyboards in the comp

  • Why do most apps make it so difficult to enter dates time and numbers

    Why is it that most apps when it comes to entering a date, time or number require you to go to the ridiculous motion of entering data using a scroll wheel. For dates it should be a calendar like interface, for time and numbers give me numeric keypad.

  • How to add Vector data to JTextArea ????

    Hi All, I have a JTExtArea where i want Vecor data to get display. Suppose i have Vector data as 1,2,3,4,5 then i want these number to be displayed in JTextArea as seperate rows. Thanks

  • Form to Image

    Hi, I have a Adobe Interactive form. After filling in the form and saving it, is it possible to convert the form into an image and pass it into R/3. Thanks, Prasy

  • Accessing component controller data

    Hi I have created a guided procedure with 3 views in it. I will enter the object id in the first view . I want to read this object id in the component controller and get some data this data will be accessed by remaining views to populate the fields i