Objects bound to session not replicating properly.

hi,
          i have two weblogic 5.1 sp3 clustered in sun boxes, using apache as
          proxy server.
          I use Inmemory replication for replicating http sessions.
          Both weblogic server says joined the cluster and it seems ok.
          i start navigating my application, halfway i bring down one server, the
          one the requests are going to. secondary server takes over, but when i
          print the objects that are bound to the session it doesnot give me all
          the values, which when printed in the primary server prints all values.
          The objects that are bound to the session are heavy.
          i am using the property weblogic.httpd.session.cacheEntries=1024, the
          default one.
          could someone help me.
          my cluster and session properties.
          weblogic.cluster.enable=true
          weblogic.cluster.name=rtcluster
          weblogic.system.bindAddr=10.11.21.20
          weblogic.cluster.multicastAddress=237.0.0.1
          weblogic.cluster.multicastTTL=1
          weblogic.cluster.defaultLoadAlgorithm=random
          # Httpd Cluster properties.
          weblogic.httpd.clustering.enable=true
          weblogic.httpd.session.persistence=true
          weblogic.httpd.session.persistentStoreType=replicated
          

You have not described your environment or what you application is doing, so
          it will be difficult to help answer your question.
          > > i have two weblogic 5.1 sp3 clustered in sun boxes, using apache as
          > > proxy server.
          > > I use Inmemory replication for replicating http sessions.
          > There was a small problem in our application we debugged it, session
          > replication is now fine.
          Good.
          > but now we are facing a new problem.
          Bad.
          > SecurityException
          Please post (or attach) the stack trace.
          > The page doesnot come in the first click, at the first
          > click weblogic gives a SecurityException.
          We do not know what page you mean. Do you mean that every page is broken,
          or pages served by a certain servlet or jsp?
          > Moreover the image is not properly displayed.
          > The image is painted when mouse is over that otherwise
          > its not. Its like image in java without double buffering.
          I assume this is a .jpg or .gif that your page references? Is the image
          created dynamically or just served statically by IIS? Or statically by
          WebLogic?
          The double-buffering look could be caused by a corrupted image file or more
          likely by being served dynamically by a JSP that accidently has some
          linefeeds due to page directives at the top, but you'll have to provide
          additional information.
          Peace.
          Cameron Purdy
          [email protected]
          http://www.tangosol.com
          WebLogic Consulting Available
          "arunbabu" <[email protected]> wrote in message
          news:[email protected]...
          > hi,
          > Thanks for the debug information.
          > There was a small problem in our application we debugged it, session
          > replication is now fine. but now we are facing a new problem.
          > SecurityException, The page doesnot come in the first click, at the first
          > click weblogic gives a SecurityException. Moreover the image is not
          > properly displayed. The image is painted when mouse is over that otherwise
          > its not. Its like image in java without double buffering.
          > could somebody throw some light to these.
          > arunbabu.
          >
          > arunbabu wrote:
          >
          > > hi,
          > > i have two weblogic 5.1 sp3 clustered in sun boxes, using apache as
          > > proxy server.
          > > I use Inmemory replication for replicating http sessions.
          > > Both weblogic server says joined the cluster and it seems ok.
          > > i start navigating my application, halfway i bring down one server, the
          > > one the requests are going to. secondary server takes over, but when i
          > > print the objects that are bound to the session it doesnot give me all
          > > the values, which when printed in the primary server prints all values.
          > > The objects that are bound to the session are heavy.
          > > i am using the property weblogic.httpd.session.cacheEntries=1024, the
          > > default one.
          > > could someone help me.
          > >
          > > my cluster and session properties.
          > >
          > > weblogic.cluster.enable=true
          > > weblogic.cluster.name=rtcluster
          > > weblogic.system.bindAddr=10.11.21.20
          > > weblogic.cluster.multicastAddress=237.0.0.1
          > > weblogic.cluster.multicastTTL=1
          > > weblogic.cluster.defaultLoadAlgorithm=random
          > >
          > > # Httpd Cluster properties.
          > > weblogic.httpd.clustering.enable=true
          > > weblogic.httpd.session.persistence=true
          > > weblogic.httpd.session.persistentStoreType=replicated
          >
          

Similar Messages

  • Session not replicated in WL6.1

              We are having session-not-replicated problem in WL6.1 Clustering.
              We have 3 servers on different machines running WL6.1 sp1, 1 is running the admin
              server and the
              other 2 are running as managed weblogic server.
              We have a web application that has been deployed to the cluster and is set
              for PersistantStoreType equal to replicated.
              We are using a Cisco Local Redirector with "sticky load balancing" infront of
              the servers.
              In our applications, most of JSP pages can modify the session data using session.setAttribute().
              And we use session.removeAttribute() to clean a session data.
              session.setAttribute("mysession1", data1);
              ....some codes......
              if (session.getAttribute("mysession") != null)
                   session.removeAttribute("mysession");
              session.setAttribute("mysession", data2);
              With session.removeAttibute() in our codes, some session data is not replicated
              to secondary server.
              We checked all session data in secondary server after shutting down the primary
              server.
              But if we comment out all session.removeAttribute() methods, failovers tested
              successfully.
              All our session data is serializable. Some are String and Some are Objects.
              Is this a known problems in WL6.1? Anyone has any idea?
              thanks,
              Hong
              

              We are having session-not-replicated problem in WL6.1 Clustering.
              We have 3 servers on different machines running WL6.1 sp1, 1 is running the admin
              server and the
              other 2 are running as managed weblogic server.
              We have a web application that has been deployed to the cluster and is set
              for PersistantStoreType equal to replicated.
              We are using a Cisco Local Redirector with "sticky load balancing" infront of
              the servers.
              In our applications, most of JSP pages can modify the session data using session.setAttribute().
              And we use session.removeAttribute() to clean a session data.
              session.setAttribute("mysession1", data1);
              ....some codes......
              if (session.getAttribute("mysession") != null)
                   session.removeAttribute("mysession");
              session.setAttribute("mysession", data2);
              With session.removeAttibute() in our codes, some session data is not replicated
              to secondary server.
              We checked all session data in secondary server after shutting down the primary
              server.
              But if we comment out all session.removeAttribute() methods, failovers tested
              successfully.
              All our session data is serializable. Some are String and Some are Objects.
              Is this a known problems in WL6.1? Anyone has any idea?
              thanks,
              Hong
              

  • Session not replicated in clustered oc4j instances

    The application is deployed to two clustered oc4j instances(A and B) and is configured to use PEER replication protocol. After logging into the application(say A handled the request, created and stored a user object in http session), we shutdown A, and click on application link, the request is routed to B, but B shows no user object in http session is found, this happens in a servlet filter. Could somebody provide some suggestions why?

    Hmm, OK. Then we need to dig in a little further.
    Can you post what the orion-application.xml file looks like for these applications?
    It has the <cluster> tag set in it.
    You can find it in $ORACLE_HOME/j2ee/home/application-deployments/<app-name>
    Are these clustered OC4J instances on the same server -- if so, did you set allow-colocation="false", which would prevent the replica from being stored on the same physical host, and thus not be avaialble when you need it?
    You can enable logging for the clsuter session manager -- you can acess the logging propeties page in ASC and then set the "oracle.j2ee.cluster" to the FINEST level to start pumping some log messages into the log file.
    Note: in 10.1.3.0 the settings are not persisted when made via ASC -- you have to enter them manually in the j2ee/<instance-name>/config/j2ee-logging.xml file. In 10.1.3.1 the settings are persisted automatically into this file.
    The easiest way to see the log messages in the file is using the Log Viewer function in ASC as well. Look for the "Diagnostics" log in the particular Oc4J instance where the app is deployed.
    cheers
    -steve-

  • View objects, view links, does not search properly

    Hi,
    I am using Jdev 11.1.2.0
    I have created a search criteria based on view objects and view links. It has entities and entity associations as base. The structure is as follow:
    vo1 ->vl (1 to 1) - > vo2
    ->vl ( 1 to many) -> vo3
    Any search attribute which is not from vo1 return bad result. It happens in running app module and in the jspx page. In app module, it sometimes complains about populating the wrong attribute for the named criteria.
    The search criteria is using "exists" statement for vo2 and vo3 for adding the conditions. It has many attributes within the exist statement.
    So what is the problem. Why it does not join properly? Why does it return bad result when search attribute is from vo2 and vo3? Please help.
    Any more information requires to solve the problem?
    Thanks,
    Arthur

    Hi,
    Two more information: vo1 is composed of Entity1 (1..M) Entity2 and Entity1 (1..1) Entity 3. vo2 is composed of Entity 2 and vo3 is composed of Entity 4.
    I follow the information from http://download.oracle.com/docs/cd/E16162_01/web.1112/e16182/bcquerying.htm#BCGIFHHF
    to create the search criteria.
    Arthur

  • Session not replicated in a different machine

    Hi Everybody,
              I have an interesting problem related to session replication on a different machine. We have two managed servers in two different machines. When we stop the managed server in the machine where we have admin server, request goes to the second managed server. However the existing session is not replicated, instead a new session is created.
              We have used in-memory replication. Any pointer to the problem will be appreciated.
              Thanks in advance,
              Dev.

    Also check if the session replication is indeed on. You can see if this is on by looking at cookies (either javascript like alert(Document.cookie) or through browser like navigator; format for replication should be <session id>!<primary server hash>!<secondart server hash>
              S

  • "reopen all windows from last session" not working properly

    Sometimes I will hit a wrong tab and lose all the tabs and pages I am working on.  But when I hit "Reopen All Windows from Last Session" in History, I either get pages from months ago, or some nonsense that Apple is apparently trying to get me to buy.  All I want is my old work up.  How can I get them back quickly and easily (which is what I thought "Reopen All Windows..." was supposed to do)?

    Manual method
    Malware – Adware removal – Apple Support
    Or download this program which was written by Thomas Reed, a long time poster. The program will do the work for you which makes it easy. If you are uncertain about downloading programs, try the manual method.
    Malware Guide – AdwareMedic – 10.7 and higher

  • Session not opening properly

    Hey when i open a session from the actual folder it sometimes opens the last backup session it saved and when it opens that logic says it cant find half of my samples. If i open logic and then go to open recent i dont get this problem.
    The more i read about i7 macs and logic the more i think that they just dont like each other....

    ?????

  • OD Replica not replicating

    It appears that my OD replica is not replicating properly. I create a new user and this user tries to log in on a computer bound to the ODR and it will not authenticate. The use CAN log into a computer bound to the ODM. Both ODM and ODR are on 10.5.7 servers and client computers are 10.5.7 or .8. There doesn't appear to be any errors of note in the log files. I am not sure how to proceed. I am hoping that the ODM is not corrupt, but I am thinking that the ODM is fine since the new users can authenticate without issue to it.

    As I am digging I am finding this in the LDAP logs:
    Sep 9 15:19:43 condor slapd[84]: <= bdbsubstringcandidates: (authAuthority) index_param failed (18)
    Sep 9 15:20:13: --- last message repeated 2 times ---
    Sep 9 15:20:29 condor slapd[84]: <= bdbsubstringcandidates: (authAuthority) index_param failed (18)
    Sep 9 15:21:04 condor slapd[84]: <= bdbsubstringcandidates: (authAuthority) index_param failed (18)
    Sep 9 15:21:34: --- last message repeated 1 time ---
    Sep 9 15:22:52 condor slapd[84]: <= bdbsubstringcandidates: (authAuthority) index_param failed (18)
    Sep 9 15:23:22: --- last message repeated 1 time ---
    Sep 9 15:25:36 condor slapd[84]: <= bdbsubstringcandidates: (authAuthority) index_param failed (18)
    Sep 9 15:26:47 condor slapd[84]: <= bdbsubstringcandidates: (authAuthority) index_param failed (18)
    Sep 9 15:27:17: --- last message repeated 1 time ---
    Sep 9 15:27:52 condor slapd[84]: <= bdbsubstringcandidates: (authAuthority) index_param failed (18)
    Sep 9 15:29:43 condor slapd[84]: <= bdbsubstringcandidates: (authAuthority) index_param failed (18)
    Sep 9 15:30:41 condor slapd[84]: <= bdbsubstringcandidates: (authAuthority) index_param failed (18)
    Sep 9 15:31:11: --- last message repeated 1 time ---
    Sep 9 15:32:50 condor slapd[84]: <= bdbsubstringcandidates: (authAuthority) index_param failed (18)
    Sep 9 15:35:08 condor slapd[84]: <= bdbsubstringcandidates: (authAuthority) index_param failed (18)
    Sep 9 15:35:38: --- last message repeated 1 time ---
    Condor is the ODM and this is a clip from the LDAP log on that server. There is nothing in the LDAP log on the ODR

  • New IE object fix makes flash not show in other browsers

    I have a page containing a flash movie. When I open the html
    page in Dreamweaver, it gives me a message saying 'this page
    contains <object> tags that may not work properly in the most
    recent versions of Internet Explorer. To correct this problem, you
    can convert these tags to browser-safe scripts. Do you want
    Dreamweaver to convert these tags for you?
    However, when I do this, my flash movie does not show up in
    my browsers (mac Firefox and/or Safari).
    What do I need to do to correct this?

    If you had js errors turned on in your IE, then when you
    opened this first
    link, you would see an error on line 16, stating "Object
    expected". This
    means that IE is not finding your referenced function -
    <script type="text/javascript">
    AC_FL_RunContent( 'codebase','http
    on the page. This happens because this file -
    <script src="Scripts/AC_RunActiveContent.js"
    type="text/javascript"></script>
    has not been uploaded. Please upload the Scripts folder and
    you will see
    things begin to work.
    Murray --- ICQ 71997575
    Adobe Community Expert
    (If you *MUST* email me, don't LAUGH when you do so!)
    ==================
    http://www.dreamweavermx-templates.com
    - Template Triage!
    http://www.projectseven.com/go
    - DW FAQs, Tutorials & Resources
    http://www.dwfaq.com - DW FAQs,
    Tutorials & Resources
    http://www.macromedia.com/support/search/
    - Macromedia (MM) Technotes
    ==================
    "Jonibean" <[email protected]> wrote in
    message
    news:elv77f$di1$[email protected]..
    > Sure, the page is at:
    >
    >
    http://www.amandaforsyth.com/dynamictest2.html
    >
    > The regular code (that flash creates) is at:
    >
    >
    http://www.amandaforsyth.com/dynamictest.html,
    which works fine.

  • WebLogic 5.1 sp6 .. session in cluster not working properly

    It seems like there is a problem in Weblogic 5.1 with sessions in a
              clustered environment. The problem is immediately visible with sp3 but
              also appears in different form with sp6 . I discovered the problem is
              actually with session while testing the cluster with a Session servlet
              given with the Weblogic 5.1 kit.
              I regiestered the servlet as servlet/session.
              The environment is briefly as follows:
              Solaris 2.6
              Weblogic 5.1.0 sp3 or sp6 - 2 servers clustered and running on same
              machine with two multihome addreses like home1:7001 and home2:7001
              Cluster properties in mycluster/weblogic.properties are set as,
              weblogic.httpd.clustering.enable=true
              weblogic.httpd.session.enable=true
              weblogic.httpd.session.persistence=true
              weblogic.httpd.session.persistentStoreType=replicated
              and also started with required cluster properties in startup.
              iPlanet 4.0 webserver - obj.conf has entries like
              WebLogicCluster="home1:7001,home2:7001"
              All requests are made as http://<host>/servlet/session
              sp3 ) After both members are booted up, the first call to session
              servlet from any new browser session throws a NullException in server,
              but subsequent calls work fine. Single server works fine.
              After looking at sp6 release notes it appeared to me that it was a known
              problem with cluster.
              sp6 ) After both members are booted up, all calls to session servlet do
              not complete and eventually it times out. Other servlets work fine.
              It only works if we do these steps,
              - one of the member is booted up and then session servlet is called and
              response comes back.
              - second member is booted up and it works well if session servlet is
              called. Subsequent requests to both members work fine.
              Another strange behaviour:
              While running a snoop servlet in cluster subsequent requests show,
              Requested url :
              either http://<host>/servlet/snoop
              or http://<host>:7001/servlet/snoop alternatively
              which is strange.
              

    You are not using the same service pack on both the servers. let try do that and see how it goes.
              1. Also, if you are doing testing why do you so many threads.
              2. The servers are unable to open sockets to each other. Could be network related. Please check into that also, but first start the servers with the same service pack.
              - Prasad
              Sutanu Ghosh wrote:
              > Here are the thread dumps from both members of the cluster. I took the dumps
              > about 5 times in 10 secs interval. It will be helpful for us if you can give
              > some insight about this problem.
              > Also about the snoop servlet, can you explain why the requested url is
              > different (one with weblogic port another without it) in every alternate
              > requests ?
              > thanks
              >
              > Prasad Peddada wrote:
              >
              > > Sutanu Ghosh wrote:
              > >
              > > > It seems like there is a problem in Weblogic 5.1 with sessions in a
              > > > clustered environment. The problem is immediately visible with sp3 but
              > > > also appears in different form with sp6 . I discovered the problem is
              > > > actually with session while testing the cluster with a Session servlet
              > > > given with the Weblogic 5.1 kit.
              > > > I regiestered the servlet as servlet/session.
              > > >
              > > > The environment is briefly as follows:
              > > > Solaris 2.6
              > > > Weblogic 5.1.0 sp3 or sp6 - 2 servers clustered and running on same
              > > > machine with two multihome addreses like home1:7001 and home2:7001
              > > > Cluster properties in mycluster/weblogic.properties are set as,
              > > > weblogic.httpd.clustering.enable=true
              > > > weblogic.httpd.session.enable=true
              > > > weblogic.httpd.session.persistence=true
              > > > weblogic.httpd.session.persistentStoreType=replicated
              > > > and also started with required cluster properties in startup.
              > > >
              > > > iPlanet 4.0 webserver - obj.conf has entries like
              > > > WebLogicCluster="home1:7001,home2:7001"
              > > >
              > > > All requests are made as http://<host>/servlet/session
              > > >
              > > > sp3 ) After both members are booted up, the first call to session
              > > > servlet from any new browser session throws a NullException in server,
              > > > but subsequent calls work fine. Single server works fine.
              > > > After looking at sp6 release notes it appeared to me that it was a known
              > > > problem with cluster.
              > > >
              > > > sp6 ) After both members are booted up, all calls to session servlet do
              > > > not complete and eventually it times out. Other servlets work fine.
              > > > It only works if we do these steps,
              > >
              > > Take thread dumps in intervals of 10 seconds and post them again.
              > >
              > > > - one of the member is booted up and then session servlet is called and
              > > > response comes back.
              > > > - second member is booted up and it works well if session servlet is
              > > > called. Subsequent requests to both members work fine.
              > > >
              > > > Another strange behaviour:
              > > > While running a snoop servlet in cluster subsequent requests show,
              > > > Requested url :
              > > > either http://<host>/servlet/snoop
              > > > or http://<host>:7001/servlet/snoop alternatively
              > > > which is strange.
              >
              > ------------------------------------------------------------------------
              > SIGQUIT
              > A SIGQUIT has been received. Do you want to:
              > [ 0 ] continue program
              > [ 1 ] check & print one deadlock
              > [ 2 ] check & print all deadlocks
              > [ 3 ] dump thread stacks
              > [ 4 ] dump lock registry
              > [ 5 ] heap inspection
              > [ 6 ] terminate program
              > Type number corresponding to selected action: Found 0 deadlock
              >
              > Full thread dump:
              > "HighPriority TimeEventGenerator" (TID:0xe7f658, sys_thread_t:0xe7f590, state:CW, thread_t: t@90, threadID:0xc9751dd8, stack_bottom:0xc9752000, stack_size:0x20000) prio=9
              >
              > [1] weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:256)
              > [2] weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java:131)
              > [3] java.lang.Thread.run(Thread.java:479)
              > -------------------
              > "SSLListenThread" (TID:0xe4e270, sys_thread_t:0xe4e1a8, state:R, thread_t: t@89, threadID:0xc9841dd8, stack_bottom:0xc9842000, stack_size:0x20000) prio=5
              >
              > [1] java.net.PlainSocketImpl.socketAccept(Native Method)
              > [2] java.net.PlainSocketImpl.accept(PlainSocketImpl.java:406)
              > [3] java.net.ServerSocket.implAccept(ServerSocket.java:240)
              > [4] java.net.ServerSocket.accept(ServerSocket.java:224)
              > [5] weblogic.security.SSL.SSLServerSocket.acceptNoHandshake(SSLServerSocket.java:121)
              > [6] weblogic.security.SSL.SSLServerSocket.accept(SSLServerSocket.java:112)
              > [7] weblogic.t3.srvr.ListenThread.run(ListenThread.java:226)
              > -------------------
              > "ListenThread" (TID:0xe247f0, sys_thread_t:0xe24728, state:R, thread_t: t@88, threadID:0xc9801dd8, stack_bottom:0xc9802000, stack_size:0x20000) prio=5
              >
              > [1] java.net.PlainSocketImpl.socketAccept(Native Method)
              > [2] java.net.PlainSocketImpl.accept(PlainSocketImpl.java:406)
              > [3] java.net.ServerSocket.implAccept(ServerSocket.java:238)
              > [4] java.net.ServerSocket.accept(ServerSocket.java:223)
              > [5] weblogic.t3.srvr.ListenThread.run(ListenThread.java:226)
              > -------------------
              > "NBExecuteThread-1" (TID:0xa9b748, sys_thread_t:0xa9b680, state:CW, thread_t: t@84, threadID:0xc9891dd8, stack_bottom:0xc9892000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "NBExecuteThread-0" (TID:0xa9a388, sys_thread_t:0xa9a2c0, state:CW, thread_t: t@83, threadID:0xc98c1dd8, stack_bottom:0xc98c2000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-69" (TID:0xa98fc8, sys_thread_t:0xa98f00, state:R, thread_t: t@82, threadID:0xc9911dd8, stack_bottom:0xc9912000, stack_size:0x20000) prio=5
              >
              > [1] java.net.PlainDatagramSocketImpl.peek(Native Method)
              > [2] java.net.DatagramSocket.receive(DatagramSocket.java:348)
              > [3] weblogic.cluster.TDMSocketIPM.receive(TDMSocketIPM.java:80)
              > [4] weblogic.cluster.TMSocket.execute(TMSocket.java:233)
              > [5] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-68" (TID:0xa97be8, sys_thread_t:0xa97b20, state:R, thread_t: t@81, threadID:0xc9941dd8, stack_bottom:0xc9942000, stack_size:0x20000) prio=5
              >
              > [1] weblogic.socket.PosixSocketMuxer.poll(Native Method)
              > [2] weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:259)
              > [3] weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
              > [4] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-67" (TID:0xa96828, sys_thread_t:0xa96760, state:MW, thread_t: t@80, threadID:0xc9991dd8, stack_bottom:0xc9992000, stack_size:0x20000) prio=5
              >
              > [1] weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:259)
              > [2] weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-66" (TID:0xa95468, sys_thread_t:0xa953a0, state:MW, thread_t: t@79, threadID:0xc99c1dd8, stack_bottom:0xc99c2000, stack_size:0x20000) prio=5
              >
              > [1] weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:259)
              > [2] weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-65" (TID:0xa940a8, sys_thread_t:0xa93fe0, state:CW, thread_t: t@78, threadID:0xc9a11dd8, stack_bottom:0xc9a12000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-64" (TID:0xa92ce8, sys_thread_t:0xa92c20, state:CW, thread_t: t@77, threadID:0xc9a41dd8, stack_bottom:0xc9a42000, stack_size:0x20000) prio=5
              >
              > [1] weblogic.rjvm.ResponseImpl.waitForData(ResponseImpl.java:43)
              > [2] weblogic.rjvm.ResponseImpl.getThrowable(ResponseImpl.java:58)
              > [3] weblogic.rmi.extensions.BasicResponse.getThrowable(BasicResponse.java:13)
              > [4] weblogic.rmi.extensions.AbstractRequest.sendReceive(AbstractRequest.java:74)
              > [5] weblogic.jndi.internal.RemoteContextFactoryImpl_WLStub.getContext(RemoteContextFactoryImpl_WLStub.java:95)
              > [6] weblogic.jndi.WLInitialContextFactoryDelegate.newRemoteContext(WLInitialContextFactoryDelegate.java:316)
              > [7] weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:224)
              > [8] weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:164)
              > [9] weblogic.jndi.Environment.getContext(Environment.java:122)
              > [10] weblogic.jndi.Environment.getInitialContext(Environment.java:104)
              > [11] weblogic.cluster.replication.ReplicationManager.getRepMan(ReplicationManager.java:362)
              > [12] weblogic.cluster.replication.ReplicationManager.createSecondary(ReplicationManager.java:406)
              > [13] weblogic.cluster.replication.ReplicationManager.register(ReplicationManager.java:585)
              > [14] weblogic.servlet.internal.session.ReplicatedSession.<init>(ReplicatedSession.java:106)
              > [15] weblogic.servlet.internal.session.ReplicatedSessionContext.getNewSession(ReplicatedSessionContext.java:50)
              > [16] weblogic.servlet.internal.session.SessionContext.getNewSessionInstance(SessionContext.java:331)
              > [17] weblogic.servlet.internal.ServletRequestImpl.getNewSession(ServletRequestImpl.java:1215)
              > [18] weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestImpl.java:1118)
              > [19] examples.servlets.SessionServlet.doGet(SessionServlet.java:51)
              > [20] javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
              > [21] javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
              > [22] weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:123)
              > [23] weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:761)
              > [24] weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:708)
              > [25] weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:252)
              > [26] weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:346)
              > [27] weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:246)
              > [28] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-63" (TID:0xa91b10, sys_thread_t:0xa91a48, state:CW, thread_t: t@76, threadID:0xc9a91dd8, stack_bottom:0xc9a92000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-62" (TID:0xa90750, sys_thread_t:0xa90688, state:CW, thread_t: t@75, threadID:0xc9ac1dd8, stack_bottom:0xc9ac2000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-61" (TID:0xa8f390, sys_thread_t:0xa8f2c8, state:CW, thread_t: t@74, threadID:0xc9b11dd8, stack_bottom:0xc9b12000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-60" (TID:0xa8dfd0, sys_thread_t:0xa8df08, state:CW, thread_t: t@73, threadID:0xc9b41dd8, stack_bottom:0xc9b42000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-59" (TID:0xa8cc10, sys_thread_t:0xa8cb48, state:CW, thread_t: t@72, threadID:0xc9b91dd8, stack_bottom:0xc9b92000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-58" (TID:0xa8ba38, sys_thread_t:0xa8b970, state:CW, thread_t: t@71, threadID:0xc9bc1dd8, stack_bottom:0xc9bc2000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-57" (TID:0xa89670, sys_thread_t:0xa895a8, state:CW, thread_t: t@70, threadID:0xc9c11dd8, stack_bottom:0xc9c12000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-56" (TID:0xa882b0, sys_thread_t:0xa881e8, state:CW, thread_t: t@69, threadID:0xc9c41dd8, stack_bottom:0xc9c42000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-55" (TID:0xa86ef0, sys_thread_t:0xa86e28, state:CW, thread_t: t@68, threadID:0xc9c91dd8, stack_bottom:0xc9c92000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-54" (TID:0xa85b30, sys_thread_t:0xa85a68, state:CW, thread_t: t@67, threadID:0xc9cc1dd8, stack_bottom:0xc9cc2000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-53" (TID:0xa84958, sys_thread_t:0xa84890, state:CW, thread_t: t@66, threadID:0xc9d11dd8, stack_bottom:0xc9d12000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-52" (TID:0xa83598, sys_thread_t:0xa834d0, state:CW, thread_t: t@65, threadID:0xc9d41dd8, stack_bottom:0xc9d42000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-51" (TID:0xa821d8, sys_thread_t:0xa82110, state:CW, thread_t: t@64, threadID:0xc9d91dd8, stack_bottom:0xc9d92000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-50" (TID:0xa80a10, sys_thread_t:0xa80948, state:CW, thread_t: t@63, threadID:0xc9dc1dd8, stack_bottom:0xc9dc2000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-49" (TID:0xa7f650, sys_thread_t:0xa7f588, state:CW, thread_t: t@62, threadID:0xc9e11dd8, stack_bottom:0xc9e12000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-48" (TID:0xa7e478, sys_thread_t:0xa7e3b0, state:CW, thread_t: t@61, threadID:0xc9e41dd8, stack_bottom:0xc9e42000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-47" (TID:0xa7d0b8, sys_thread_t:0xa7cff0, state:CW, thread_t: t@60, threadID:0xc9e91dd8, stack_bottom:0xc9e92000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-46" (TID:0xa7bcf8, sys_thread_t:0xa7bc30, state:CW, thread_t: t@59, threadID:0xc9ec1dd8, stack_bottom:0xc9ec2000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-45" (TID:0xa7a938, sys_thread_t:0xa7a870, state:CW, thread_t: t@58, threadID:0xc9f11dd8, stack_bottom:0xc9f12000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-44" (TID:0xa79578, sys_thread_t:0xa794b0, state:CW, thread_t: t@57, threadID:0xc9f41dd8, stack_bottom:0xc9f42000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-43" (TID:0xa783a0, sys_thread_t:0xa782d8, state:CW, thread_t: t@56, threadID:0xc9f91dd8, stack_bottom:0xc9f92000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-42" (TID:0xa76fe0, sys_thread_t:0xa76f18, state:CW, thread_t: t@55, threadID:0xc9fc1dd8, stack_bottom:0xc9fc2000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-41" (TID:0xa74c18, sys_thread_t:0xa74b50, state:CW, thread_t: t@54, threadID:0xca011dd8, stack_bottom:0xca012000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-40" (TID:0xa73858, sys_thread_t:0xa73790, state:CW, thread_t: t@53, threadID:0xca041dd8, stack_bottom:0xca042000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-39" (TID:0xa72498, sys_thread_t:0xa723d0, state:CW, thread_t: t@52, threadID:0xca091dd8, stack_bottom:0xca092000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-38" (TID:0xa712c0, sys_thread_t:0xa711f8, state:CW, thread_t: t@51, threadID:0xca0c1dd8, stack_bottom:0xca0c2000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-37" (TID:0xa6ff00, sys_thread_t:0xa6fe38, state:CW, thread_t: t@50, threadID:0xca111dd8, stack_bottom:0xca112000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-36" (TID:0xa6eb40, sys_thread_t:0xa6ea78, state:CW, thread_t: t@49, threadID:0xca141dd8, stack_bottom:0xca142000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-35" (TID:0xa6d780, sys_thread_t:0xa6d6b8, state:CW, thread_t: t@48, threadID:0xca191dd8, stack_bottom:0xca192000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-34" (TID:0xa3c940, sys_thread_t:0xa3c878, state:CW, thread_t: t@47, threadID:0xca1c1dd8, stack_bottom:0xca1c2000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-33" (TID:0xa3c720, sys_thread_t:0xa3c658, state:CW, thread_t: t@46, threadID:0xca211dd8, stack_bottom:0xca212000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-32" (TID:0xa3aa60, sys_thread_t:0xa3a998, state:CW, thread_t: t@45, threadID:0xca241dd8, stack_bottom:0xca242000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-31" (TID:0xa3a658, sys_thread_t:0xa3a590, state:CW, thread_t: t@44, threadID:0xca291dd8, stack_bottom:0xca292000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-30" (TID:0xa45828, sys_thread_t:0xa45760, state:CW, thread_t: t@43, threadID:0xca2c1dd8, stack_bottom:0xca2c2000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-29" (TID:0xa23d00, sys_thread_t:0xa23c38, state:CW, thread_t: t@42, threadID:0xca311dd8, stack_bottom:0xca312000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-28" (TID:0xa14fe8, sys_thread_t:0xa14f20, state:CW, thread_t: t@41, threadID:0xca341dd8, stack_bottom:0xca342000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-27" (TID:0xa21eb0, sys_thread_t:0xa21de8, state:CW, thread_t: t@40, threadID:0xca391dd8, stack_bottom:0xca392000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-26" (TID:0xa0fee0, sys_thread_t:0xa0fe18, state:CW, thread_t: t@39, threadID:0xca3c1dd8, stack_bottom:0xca3c2000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-25" (TID:0x9c54c8, sys_thread_t:0x9c5400, state:CW, thread_t: t@38, threadID:0xca411dd8, stack_bottom:0xca412000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-24" (TID:0x9c7cc8, sys_thread_t:0x9c7c00, state:CW, thread_t: t@37, threadID:0xca441dd8, stack_bottom:0xca442000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-23" (TID:0xa0acc8, sys_thread_t:0xa0ac00, state:CW, thread_t: t@36, threadID:0xca491dd8, stack_bottom:0xca492000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-22" (TID:0xa17b08, sys_thread_t:0xa17a40, state:CW, thread_t: t@35, threadID:0xca4c1dd8, stack_bottom:0xca4c2000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-21" (TID:0x9c8498, sys_thread_t:0x9c83d0, state:CW, thread_t: t@34, threadID:0xca511dd8, stack_bottom:0xca512000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-20" (TID:0x9fb8f8, sys_thread_t:0x9fb830, state:CW, thread_t: t@33, threadID:0xca541dd8, stack_bottom:0xca542000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-19" (TID:0x9fd4f8, sys_thread_t:0x9fd430, state:CW, thread_t: t@32, threadID:0xca591dd8, stack_bottom:0xca592000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-18" (TID:0xa0f628, sys_thread_t:0xa0f560, state:CW, thread_t: t@31, threadID:0xca5c1dd8, stack_bottom:0xca5c2000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-17" (TID:0x9c0cf8, sys_thread_t:0x9c0c30, state:CW, thread_t: t@30, threadID:0xca611dd8, stack_bottom:0xca612000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-16" (TID:0x9bc4f8, sys_thread_t:0x9bc430, state:CW, thread_t: t@29, threadID:0xca641dd8, stack_bottom:0xca642000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-15" (TID:0x9b38f8, sys_thread_t:0x9b3830, state:CW, thread_t: t@28, threadID:0xca691dd8, stack_bottom:0xca692000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-14" (TID:0x9b3cf8, sys_thread_t:0x9b3c30, state:CW, thread_t: t@27, threadID:0xca6c1dd8, stack_bottom:0xca6c2000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
              > [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
              > -------------------
              > "ExecuteThread-13" (TID:0x9c94f8, sys_thread_t:0x9c9430, state:CW, thread_t: t@26, threadID:0xca711dd8, stack_bottom:0xca712000, stack_size:0x20000) prio=5
              >
              > [1] java.lang.Object.wait(Object.java:424)
              > [2] weblogic.ke

  • Tomcat  5.5.26 Sessions getting replicated but not working via browser

    Hi,
    I have configured Tomcat 5.5.26 to be clustered across 2 machines with one instance on each. These two machines are behing a BIG-IP loadbalancer which is setup for sticky sessions.
    The catalina.out states that the member can see each other:
    Jul 3, 2008 6:33:50 PM org.apache.catalina.cluster.tcp.SimpleTcpCluster memberAdded
    INFO: Replication member added:org.apache.catalina.cluster.mcast.McastMember[tcp://10.17.21.125:9001,catalina,10.17.21.125,9001, alive=38753]
    Jul 3, 2008 6:33:51 PM org.apache.catalina.cluster.mcast.McastService registerMBean
    The localhost.2008-07-03.log states that the sessions are being replicated for the jsp-examples app - book example. I have an app of our own that does not even state that the session is replicated but I though I would start here with getting the example one working.
    Jul 3, 2008 6:34:31 PM org.apache.catalina.core.ApplicationContext log
    INFO: SessionListener: sessionDestroyed('E7E9E54600927A4826AFEDB59D7EF6E7.tomcatDargle')
    However, when I take down the instance which created the session and attempt to refresh the page or navigate to another page I get page cannot be displayed. This shows that the sessions are not completely replicated. What am I missing?
    I have added my server.xml file contents:
    <Cluster className="org.apache.catalina.cluster.tcp.SimpleTcpCluster"
    managerClassName="org.apache.catalina.cluster.session.DeltaManager"
    expireSessionsOnShutdown="false"
    useDirtyFlag="false"
    notifyListenersOnReplication="true">
    <Membership
    className="org.apache.catalina.cluster.mcast.McastService"
    mcastAddr="239.192.17.20"
    mcastPort="9002"
    mcastFrequency="500"
    mcastDropTime="3000"/>
    <Receiver
    className="org.apache.catalina.cluster.tcp.ReplicationListener"
    tcpListenAddress="auto"
    tcpListenPort="9001"
    tcpSelectorTimeout="100"
    tcpThreadCount="6"/>
    <Sender
    className="org.apache.catalina.cluster.tcp.ReplicationTransmitter"
    replicationMode="pooled"
    ackTimeout="15000"
    waitForAck="true"/>
    <ClusterListener className="org.apache.catalina.cluster.session.ClusterSessionListener" />
    <ClusterListener className="org.apache.catalina.cluster.session.JvmRouteSessionIDBinderListener" />
    <Valve className="org.apache.catalina.cluster.tcp.ReplicationValve"
    filter=".*\.gif;.*\.js;.*\.css;.*\.png;.*\.jpeg;.*\.jpg;.*\.htm;.*\.html;.*\.txt;"
    primaryIndicator="true" />
    <Valve className="org.apache.catalina.cluster.session.JvmRouteBinderValve"
    enabled="true" />
    </Cluster>
    Any help at all would be greatly appreciated.
    Martin

    Hi Ganeshmb,
    The app I am using is the jsp-examples/book example.
    The load balancer is sending requests to both servers.
    When the dargle instance is sent a request I can see in the logs of both servers:
    INFO: SessionListener: sessionCreated('730F4AD5A21CA06639BF956B9F5418CB.tomcatDargle')
    When the tolka instance is sent a request I can see in the logs of both servers:
    INFO: SessionListener: sessionCreated('E7E9E54600927A4826AFEDB59D7EF6E7.tomcatTolka')
    When the server starts up the relevant info is in the logs:
    Jul 3, 2008 6:33:56 PM org.apache.catalina.cluster.session.DeltaManager start
    INFO: Starting clustering manager at /jsp-examples
    Jul 3, 2008 6:33:56 PM org.apache.catalina.cluster.session.DeltaManager getAllClusterSessions
    WARNING: Manager [jsp-examples], requesting session state from org.apache.catalina.cluster.mcast.McastMember[tcp://10.17.21.125:9001,catalina
    ,10.17.21.125,9001, alive=44363]. This operation will timeout if no session state has been received within 60 seconds.
    Jul 3, 2008 6:33:56 PM org.apache.catalina.cluster.session.DeltaManager waitForSendAllSessions
    INFO: Manager [jsp-examples]; session state send at 7/3/08 6:33 PM received in 123 ms.
    The jsp-examples book example is supposed to have serilizable object and was recommended on some sites are the way to test out the replication. Is there any other way to test this?
    Also, the main purpose of the cluster is to replicate an application from an external vendor which they say is compatible with session replication. However, this app does not even output the sessionCreated message so I am unsure if it truly is compatible.
    If I could prove that the cluster is setup correctly then I would have more to go on when contacting the vendor. At the moment I am unsure if the cluster is setup correctly for session replication.
    Thanks,
    Martin

  • ORA-04043: object SYS.DELTA$SESSION does not exist

    Dear Friends
    after I import my data by using the follwoing import script :
    IMP JCC/P_MANUF FILE =JCC.DMP FULL
    and at the end give this message import has been imported succesfully without warning
    then when I use this script :
    SQL> SELECT TNAME FROM TAB
    2 WHERE TNAME LIKE 'USER_SESSION'
    3 /
    TNAME
    USER_SESSION
    The table USER_SESSION is exist but when I try to desplay the structure of the USER_SESSION by using this :
    SQL> DESC USER_SESSION
    ERROR:
    ORA-04043: object SYS.DELTA$SESSION does not exist
    and when I try to use the select statment as the following
    SELECT * FROM USER_SESSION
    ERROR at line 1:
    ORA-00980: synonym translation is no longer valid
    Waiting for your valuable answer.
    Best regards
    Jamil Alshaibani

    SQL> select * from V$version;
    BANNER
    Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - 64bit Production
    PL/SQL Release 11.1.0.6.0 - Production
    CORE 11.1.0.6.0 Production
    TNS for Linux: Version 11.1.0.6.0 - Production
    NLSRTL Version 11.1.0.6.0 - Production
    SQL> !uname -a
    Linux KAD-VMWARE 2.6.9-55.ELsmp #1 SMP Fri Apr 20 16:36:54 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux
    SQL> sho user
    USER is "SYS"
    SQL> select object_type,status from dba_objects where object_name = 'K_DRWDWN_GRP' and OWNER = 'SYS';
    no rows selected
    Is any thing wrong with my dictionary? please let me know if i missed anything?
    Edited by: sanora600 on Oct 16, 2010 12:34 AM

  • OLE Objects are not displayed properly-overlap characters and empty page

    I'm using CR4E 12 Runtime libraries to load and view reports that are created in CR designer  v10. Some of the OLE Objects (not all) are not displayed properly.
    1) A full page contains terms and conditions as ole object is not at all displayed and just shown as black image.
    2) Some data in a table (OLE Object) shown as overlapped characters.
    Any body know the reason and is there any workaround to solve this issue?
    Thankyou very much for your time.

    Your problem seems to be with the character encoding you are using for your text.  A quick google search for ColdFusion character encoding should turn up the answer.  In case you are interested in learning more:
    http://livedocs.adobe.com/coldfusion/7/htmldocs/wwhelp/wwhimpl/common/html/wwhelp.htm?cont ext=ColdFusion_Documentation&file=00001201.htm
    Hope that helps!
    - Michael

  • How to check was the object bound or not without exception handling?

    context.lookup("someName");throws NameNotFoundException in case object was not bound to someName.
    How to check was the object bound or not without exception handling?

    context.lookup("someName");throws NameNotFoundException in case object was not bound to someName.
    How to check was the object bound or not without exception handling?

  • 'MAPI Session Handle' of the NGW 'Object Request Broker' could not be accessed (0x80004005) on attempt to get an address book

    Hi!
    When I try to access GW address book by calling
    DIGWAccount6::GetSystemAddressBook, or DIGWAccount6::AddressBooks, or even
    DIGWMessage::Send, I'm getting messagebox with title "Address Book Error"
    and message: "The 'MAPI Session Handle' of the Novell GroupWise 'Object
    Request Broker' could not be accesses. The address book cannot run (error:
    status: 0x80004005)."
    I'm using .NET and I only get this error when I create a console
    application. With windows application everything goes fine.
    I've tried reinstalling GW client, running fixmapi utility, installing
    different versions of MAPI CDO, but still got this problem.
    Any ideas?

    In the Application object.
    >>> On Monday, July 26, 2010 at 4:16 PM,
    shutchinson<[email protected]> wrote:
    > Where would we set this?
    >
    > Thanks!
    >
    > Scott
    >
    > Preston Stephenson;1755943 Wrote:
    >> Do you need to use the MAPI address book providers?
    >> Can you use MultiLogin and set MultiLoginAddressBookSupport = TRUE?
    >>
    >> Preston
    >>
    >> >>> On Tuesday, November 11, 2008 at 4:22 AM, Vladimir
    >> Iofik<[email protected]>
    >> wrote:
    >> > Hi!
    >> > When I try to access GW address book by calling
    >> > DIGWAccount6::GetSystemAddressBook, or DIGWAccount6::AddressBooks, or
    >> even
    >>
    >> > DIGWMessage::Send, I'm getting messagebox with title "Address Book
    >> Error"
    >>
    >> > and message: "The 'MAPI Session Handle' of the Novell GroupWise
    >> 'Object
    >> > Request Broker' could not be accesses. The address book cannot run
    >> (error:
    >>
    >> > status: 0x80004005)."
    >> > I'm using .NET and I only get this error when I create a console
    >> > application. With windows application everything goes fine.
    >> > I've tried reinstalling GW client, running fixmapi utility,
    >> installing
    >> > different versions of MAPI CDO, but still got this problem.
    >> >
    >> > Any ideas?

Maybe you are looking for

  • HP LaserJet 4 Power

    Hi, I have a HP Laserjet 4 and I moved to Thailand.  First question is what is the wattage on this unit so i can get a power converter to use it?  Second can this run on 220V from 110V purchased in America?  Or does it need to have the power supply c

  • Invoice outputs are not printing after saving the document..!

    Invoice outputs are not printing after saving the document. Eventhough we maintain all condition records not only that Processing log also it showed that it has been processed on some date. but customer not received the printout Amar

  • ALE/IDOC Inbound failure u0096 56/60

    Hi guys, We are having a problem with our Idoc processing. We are sending an Idoc from our EBP sytem via transactional RFC to our production SAP R/3 system. The transmission from the source system is ok. However when the idoc is received the data in

  • Insertion point/caret/cursor blinking rate - how to change? It's killing me

    Hello everbody, Just switched and was happy untill installed Office. The caret/cursor blinking rate is just killing me with it slowness. How can I change its rate? Any command for terminal? Any third party application? Anything? Please

  • Is there a way to automate skipping random notes (drum sequence)?

    Hello all, I've got a drum sequence loaded up with an EXS24 kit (too big for ultrabeat unfortunately). I'd like to keep it fresh throughout the track by randomly skipping notes/triggers. Is there an automated way to do that, or a way to batch process