Session in clustering

Hi all,
          I am using WLS5.1 on Win-NT4.0 with SP6a.
          I have following question about session-id maintanence across clustering.
          We have developed a weblog, which logs information like
          session-id,username,password etc....
          What i want to know is if I use clustering with one instance on each
          machine, during failover and load balancing condition. now both the
          instances will have it's own different log files right??
          1)Will there be only one session id across both the instances and say
          suppose if one weblogic server fails and other takes over will it have the
          same session id?
          2)If answer to question one is no, then Can one session with an unique
          session id be split among the multiple web logs?
          Thanks.
          Rgds,
          Arpit Doshi
          

Check the previous one you posted for answers.
          -- Prasad
          Arpit Doshi wrote:
          > Hi all,
          >
          > I am using WLS5.1 on Win-NT4.0 with SP6a.
          >
          > I have following question about session-id maintanence across clustering.
          >
          > We have developed a weblog, which logs information like
          > session-id,username,password etc....
          >
          > What i want to know is if I use clustering with one instance on each
          > machine, during failover and load balancing condition. now both the
          > instances will have it's own different log files right??
          >
          > 1)Will there be only one session id across both the instances and say
          > suppose if one weblogic server fails and other takes over will it have the
          > same session id?
          >
          > 2)If answer to question one is no, then Can one session with an unique
          > session id be split among the multiple web logs?
          >
          > Thanks.
          >
          > Rgds,
          > Arpit Doshi
          

Similar Messages

  • What are the steps to setup an HTTP Session replication clustering in oc4j9

    what are the steps to setup an HTTP Session replication clustering in oc4j9.0.5

    Are you sure you have the correct version number for OC4J? Is this a standalone OC4J instance, if it then the steps involved are different from the full stack. Please check the Higher Availibility guide in the documentation on OTN.
    Deepak

  • Help!!! Stateful session bean clustering

              I posted this message on interest.clustering.in-memory-replication. But there is
              no answer at all. Could anyone give me
              some hints? Thanks a lot. I am a student and this work is part of my course project.
              It is due soon.
              =================================================================
              I have a big problem to get stateful session bean in-memory replication run on
              clustering. I have three server instances on three nodes and there is always errors
              from the server instance like this when I run the client to invoke the bean methods:
              <Jan 4, 2002 6:47:31 PM EST> <Error> <EJB> <Failed to update the secondary copy
              of a stateful session bean from home:stateful.ejb.AgentSTF>
              Besides, the load balancing can not work probably too. Below is what I get.
              Statistics for different servers:
              "myserver" processed 160 (12%) of 1311 invocations "ejbperf-3" processed 1151
              (88%) of 1311 invocations
              End Client...
              Load balancing works fine with stateless and entity bean.
              Any comments are greatly appreciated.
              Jenny
              

    Hi Jenny,
              Please could you open a case to the customer support ([email protected]) There is a Cr
              on this issue CR059046
              Description of the CR
              WLS 6.1SP1 - Accessing Stateful Session Bean from Stateless Session Bean in a
              cluster fails with errors
              <Oct 5, 2001 5:08:25 PM GMT+00:00> <Error> <EJB> <Failed to update the
              secondary copy of a stateful session bean from home:UserState>
              Regards
              Stephane
              Jenny Liu wrote:
              > I posted this message on interest.clustering.in-memory-replication. But there is
              > no answer at all. Could anyone give me
              > some hints? Thanks a lot. I am a student and this work is part of my course project.
              > It is due soon.
              >
              > =================================================================
              >
              > I have a big problem to get stateful session bean in-memory replication run on
              > clustering. I have three server instances on three nodes and there is always errors
              > from the server instance like this when I run the client to invoke the bean methods:
              >
              > <Jan 4, 2002 6:47:31 PM EST> <Error> <EJB> <Failed to update the secondary copy
              > of a stateful session bean from home:stateful.ejb.AgentSTF>
              >
              > Besides, the load balancing can not work probably too. Below is what I get.
              >
              > Statistics for different servers:
              > "myserver" processed 160 (12%) of 1311 invocations "ejbperf-3" processed 1151
              > (88%) of 1311 invocations
              > End Client...
              >
              > Load balancing works fine with stateless and entity bean.
              >
              > Any comments are greatly appreciated.
              >
              > Jenny
              >
              Regards,
              Stephane Kergozien
              BEA Support
              

  • 2003 Terminal Server Session Directory Clustering

    Hi everybody ;
    I have question about clustering TS Session Directory Service.
    In my environment I have four terminal server which running Windows Server 2003 R2. Now we bought two new servers and we are planning to use them for File Server with Windows Server 2008 R2. I installed Windows Server 2008 R2 to this new servers
    and i configured them for file server and clustered this two server. But i want to cluster the my terminal servers session directory service in this cluster environment. My terminal server WS2003 but cluster environment is WS2008. Is there a problem about
    this version difference ?
    Thanks.

    i don't believe so. 2003 terminal services requires at least 2x 2003 servers with the session directory service running on them to be clustered in MSCS.  2008 has a whole new session directory which will not serve 2003 remote desktop hosts
    http://support.microsoft.com/kb/301923
    http://support.microsoft.com/kb/301926
    http://download.microsoft.com/download/8/6/2/8624174c-8587-4a37-8722-00139613a5bc/TS_Session_Directory.doc
    you may want to consider upgrading your old 2003 terminal server environment to 2008 though.

  • Session problem on clustered sun fire with SP6.1

    Hi All,
    I am having a problem with a webapplication on a clustered system.
    In the following I describe the current system setup.
    I will then describe the setup of the web application.
    Following this, I explain the trouble I'm having with sharing sessions in this environment.
    Finally, I pose the key question.
    SYSTEM SETUP:
    Our group has a clustered server setup. I believe the two machines are Sun Fire systems running Solaris 9. Let me know if you need more information concerning the HW.
    To manage the cluster, we use Sun Cluster software. Let me know if you need to know the version number. I do not have it handy. We just recently setup the system (in the past 6 months).
    Also, we have the newest Sun Web Server installed 6.1. We used the default installation. The only thing we changed was the dynamicreloadinterval variable from "-1" to "60".
    WEB APPLICATION:
    We have a fairly simple MVC web application setup, which works well on a single-server system. Essentially, the web application (1) asks for a certain input via a webform, (2) takes this input, and uses it to get information from a database, (3) puts this information into a httpsession attribute, (4) redirects the response to a JSP. The JSP gets the httpsession attribute (populated in step 3) and prints it out.
    So, HTML with form posts to Servlet, Servlet gets data from database and populates a session attribute, JSP gets that session attribute and prints it out.
    Between each transition from HTML, Servlet and JSP, the currently processing server may switch. I.e. the HTML may be served, for instance, by ClusterServer1, the Servlet may be handled, for instance, by ClusterServer2, and the JSP may be served at random by either.
    THE TROUBLE I'M HAVING
    Sometimes, my JSP is able to find the session attribute and print out whatever I put into the session during the Servlet step. However, sometimes, the JSP will print out "null" (the session attribute isn't available to the JSP).
    For the HTML and the JSP, I have the page print out what server it is being served from. Thus, I can tell that the HTML is served from, for instance, ClusterServer1 while JSP is served from, for instance, ClusterServer2. Sometimes, the same server serves both.
    KEY QUESTIONS:
    Why would this be happening?
    How can I have a session stick to the user and be shared across both servers?
    What other information would you need to provide an answer concerning this issue?
    I appreciate your efforts very much!
    Matthias Edrich
    dailysun

    Hi All,
    Hi Elving,
    I read through the documentation and have the following questions:
    (1) It seems that I can share sessions amongst both servers if I
    configure the web server to store sessions in a persistant manner such as in a file or in a database. Is this correct?
    (2) To enable this persistent storage of a session, I would need to change the Session Manager used. Is this correct?
    (3) If yes, I have the choice between the following managers. Please correct me if I have misunderstood the options.
    - PersistentManager: Instead of securing session information
    in memory, this manager saves session information within
    a file on the server in a directory, which I specify within
    sun-web.xml
    - IWSSessionManager: With this manager, I can store sessions
    in a defined database or file on the server.
    - MMapSessionManager: This manager also stores sessions in
    a file on the server
    (4) What is the difference between PersistentManager and
    MMapSessionManager if my web server is running in
    single-process mode?
    (5) If MMapSessionManager is a file-based manager, where do I
    specify to what directory the related file is stored to as I
    do in PersistentManager?
    (6) What are the advantages and disadvantages of
    Persistent/IWS/MMap managers?
    (7) In looking at SessionManagers, am I even barking up
    the right tree? It seems like these would help me share
    sessions across clustered servers.
    (8) Finally, I guess my plan of action would be the following:
    -> Identify what session manager to use
    -> Include a sun-web.xml file in /WEB-INF containing
    the manager-specific info
    -> Reload my web application
    -> done...
    Is this correct?
    Elving, I appreciate your help. Thanks!
    dailysun

  • InvalidClientId on Clustered Environment

              I am running into a problem where a get "weblogic.jms.common.InvalidClientIDException:
              Client id, testDesintation, is in use" when running in a clustered environment.
              In the code, I dynamically set the clientId on the TopicConnection using setClientID().
              The class that does this is called from a Stateless Session EJB (clustered) which
              is called from a MDB (clustered).
              I believe this is from node1 setting the clientId to 'x', and before node1 has
              closed the connection, node2 opens a connection, setting the clientId to 'x'.
              This is how I actually need it to perform. Each node may need to publish messages
              to the same destination around the same time. This is because the clustered MDB
              is what prompts the publish to the next destination.
              What is the suggested approach for a problem such as this? Is the only solution
              not to cluster the MDB, so that only one node may be publishing to the Topic at
              one time?
              Any suggestions?
              jz
              

    Hi Josh,
              I think that setting the client-id on a connection to force exclusivity is only needed
              when the connection is used to create a durable subscription. Even
              in this case some implementations of JMS may not require it, (don't
              recall for WebLogic.)
              So in your case, it is not necessary to set the clientId on a connection.
              Tom
              Josh Zook wrote:
              > I am running into a problem where a get "weblogic.jms.common.InvalidClientIDException:
              > Client id, testDesintation, is in use" when running in a clustered environment.
              > In the code, I dynamically set the clientId on the TopicConnection using setClientID().
              > The class that does this is called from a Stateless Session EJB (clustered) which
              > is called from a MDB (clustered).
              >
              > I believe this is from node1 setting the clientId to 'x', and before node1 has
              > closed the connection, node2 opens a connection, setting the clientId to 'x'.
              >
              > This is how I actually need it to perform. Each node may need to publish messages
              > to the same destination around the same time. This is because the clustered MDB
              > is what prompts the publish to the next destination.
              >
              > What is the suggested approach for a problem such as this? Is the only solution
              > not to cluster the MDB, so that only one node may be publishing to the Topic at
              > one time?
              >
              > Any suggestions?
              >
              > jz
              

  • Stateful bean clustering

    Hi,
              Does weblogic 5.1 support stateful bean clustering? If not how to achive this?
              Thanks in advance,
              vivek
              

    6.x supports stateful session beans clustering (replication and failover), but not 5.1.
              Vivek <[email protected]> wrote:
              > Hi,
              > Does weblogic 5.1 support stateful bean clustering? If not how to achive this?
              > Thanks in advance,
              > vivek
              Dimitri
              

  • JNDI replication problems in WebLogic cluster.

    I need to implement a replicable property in the cluster: each server could
    update it and new value should be available for all cluster. I tried to bind
    this property to JNDI and got several problems:
    1) On each rebinding I got error messages:
    <Nov 12, 2001 8:30:08 PM PST> <Error> <Cluster> <Conflict start: You tried
    to bind an object under the name example.TestName in the jndi tree. The
    object you have bound java.util.Date from 10.1.8.114 is non clusterable and
    you have tried to bind more than once from two or more servers. Such objects
    can only deployed from one server.>
    <Nov 12, 2001 8:30:18 PM PST> <Error> <Cluster> <Conflict Resolved:
    example.TestName for the object java.util.Date from 10.1.9.250 under the
    bind name example.TestName in the jndi tree.>
    As I understand this is a designed behavior for non-RMI objects. Am I
    correct?
    2) Replication is still done, but I got randomly results: I bind object to
    server 1, get it from server 2 and they are not always the same even with
    delay between operation in several seconds (tested with 0-10 sec.) and while
    it lookup returns old version after 10 sec, second attempt without delay
    could return correct result.
    Any ideas how to ensure correct replication? I need lookup to return the
    object I bound on different sever.
    3) Even when lookup returns correct result, Admin Console in
    Server->Monitoring-> JNDI Tree shows an error for bound object:
    Exception
    javax.naming.NameNotFoundException: Unable to resolve example. Resolved: ''
    Unresolved:'example' ; remaining name ''
    My configuration: admin server + 3 managed servers in a cluster.
    JNDI bind and lookup is done from stateless session bean. Session is
    clusterable and deployed to all servers in cluster. Client invokes session
    methods throw t3 protocol directly on servers.
    Thank you for any help.

    It is not a good idea to use JNDI to replicate application data. Did you consider
    using JMS for this? Or JavaGroups (http://sourceforge.net/projects/javagroups/) -
    there is an example of distibuted hashtable in examples.
    Alex Rogozinsky <[email protected]> wrote:
    I need to implement a replicable property in the cluster: each server could
    update it and new value should be available for all cluster. I tried to bind
    this property to JNDI and got several problems:
    1) On each rebinding I got error messages:
    <Nov 12, 2001 8:30:08 PM PST> <Error> <Cluster> <Conflict start: You tried
    to bind an object under the name example.TestName in the jndi tree. The
    object you have bound java.util.Date from 10.1.8.114 is non clusterable and
    you have tried to bind more than once from two or more servers. Such objects
    can only deployed from one server.>
    <Nov 12, 2001 8:30:18 PM PST> <Error> <Cluster> <Conflict Resolved:
    example.TestName for the object java.util.Date from 10.1.9.250 under the
    bind name example.TestName in the jndi tree.>
    As I understand this is a designed behavior for non-RMI objects. Am I
    correct?
    2) Replication is still done, but I got randomly results: I bind object to
    server 1, get it from server 2 and they are not always the same even with
    delay between operation in several seconds (tested with 0-10 sec.) and while
    it lookup returns old version after 10 sec, second attempt without delay
    could return correct result.
    Any ideas how to ensure correct replication? I need lookup to return the
    object I bound on different sever.
    3) Even when lookup returns correct result, Admin Console in
    Server->Monitoring-> JNDI Tree shows an error for bound object:
    Exception
    javax.naming.NameNotFoundException: Unable to resolve example. Resolved: ''
    Unresolved:'example' ; remaining name ''
    My configuration: admin server + 3 managed servers in a cluster.
    JNDI bind and lookup is done from stateless session bean. Session is
    clusterable and deployed to all servers in cluster. Client invokes session
    methods throw t3 protocol directly on servers.
    Thank you for any help.--
    Dimitri

  • ADF Application gets auto refreshed

    Hi
    i have my ADF application deployed in one of the weblogic clustered server. There are four weblogic managed cluster.
    In my application i am reading a csv file and performing some user operation with OIM.
    It is taking much time around more than 5 min (i guess performance issue) and after that the application gets refreshed and back to home page is displayed where as in logs i am getting the debugs of file read.
    Its only the application page that gets auto refreshed....
    Please help !!!
    from where the application get refreshed? is this a weblogi clustered application issue??
    i tried the same application in another server where the application process the same file quickly(with less time) and no refresh of application happens.
    Regards
    Sudeep

    hi Ramandeep
    i just checked the web.xml... the session timeout is not set in my application... so for that is there any default value for the application to get timeout?
    and in my scenario i am not getting session time out message in my UI .... that session has been timedout please refresh or retry ...
    the page gets totally refreshed.
    i guess this is the problem of failure of HTTP sessions in clustered web logic where the connection in promary fails trys to connect secoundary cluster and if that fails the HTTP page gets refreshed....
    can u please suggest if i am getting the problem correct or not ??
    Regards
    Sudeep
    Edited by: SKD on Feb 14, 2012 1:05 PM

  • RE: Cache Link Disabled

    Hello,
    In my BI Admin Tool, under the Manage option, I have Jobs, Sessions, Cache, Clusters, Security etc. Most of them are enabled but the Cache Link is disabled. I would like to look at the Cache Manager and I can't.
    Any reason why it is disabled?

    I just checked it. I indeed had to change the setting Cache=Yes in the NqsConfig.ini file.
    Cache link is enabled now
    Thanks
    rkingmdu

  • Limitation on Session Size (8K) with Clustering

              Hi.
              Is there a limitation on the session size for a clustered environment. i'm not
              sure whether its true or not. can anyone please clarify. Also is it for the entire
              session object or per user.
              Thanks
              Nitesh
              

    There is no limit as such. The only limit imposed depends on the heap allocated for
              the JVM.
              Nitesh wrote:
              > Hi.
              >
              > Is there a limitation on the session size for a clustered environment. i'm not
              > sure whether its true or not. can anyone please clarify. Also is it for the entire
              > session object or per user.
              >
              > Thanks
              >
              > Nitesh
              Rajesh Mirchandani
              Developer Relations Engineer
              BEA Support
              

  • Clustered WL 6.1 creates 2 server sessions per user

              It appears that WL 6.1 creates 2 HTTP sessions per user for a simple JSP object.
              It shows in "ADmin Console/mydomain> DefaultWebApp> Web Applications> DefaultWebApp>
              Servlet Runtimes":
              1 /count.jsp
              1 /*.jsp
              In a non-clustered environment this does not happen.
              Is that normal?
              

    I found the problem myself. For some reason WL did not like any special characters in the system password. I am not sure which ones are valid and which are not but I am avoiding them all right now.

  • Problem in accessing JSP in a Clustered Session replicated environment

              Hai All!
              When i tried to access Index.jsp in a clustered-Session inmemmory replicated environment
              it is throwing following exception,,
              What Might be the reason..
              <Aug 1, 2001 12:11:19 PM GMT+05:30> <Error> <HTTP> <[WebAppServletContext(6493555,DefaultWebApp_ClusterServerA)]
              Servlet failed with Exception java.lang.ClassCastException: weblogic.servlet.internal.session.MemorySessionContext
              at weblogic.rmi.internal.AbstractOutboundRequest.sendReceive(AbstractOutboundRequest.java:90)
              at weblogic.cluster.replication.ReplicationManager_WLStub.create(ReplicationManager_WLStub.java:192)
              at weblogic.cluster.replication.ReplicationManager.trySecondary(ReplicationManager.java:587)
              at weblogic.cluster.replication.ReplicationManager.createSecondary(ReplicationManager.java:565)
              at weblogic.cluster.replication.ReplicationManager.register(ReplicationManager.java:344)
              at weblogic.servlet.internal.session.ReplicatedSessionData.<init>(ReplicatedSessionData.java:128)
              at weblogic.servlet.internal.session.ReplicatedSessionContext.getNewSession(ReplicatedSessionContext.java:123)
              at weblogic.servlet.internal.session.SessionContext.getNewSessionInstance(SessionContext.java:121)
              at weblogic.servlet.internal.ServletRequestImpl.getNewSession(ServletRequestImpl.java:1552)
              at weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestImpl.java:1415)
              at jsp_servlet._index._jspService(_index.java:80) at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
              at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:213)
              at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:1265)
              at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:1631)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              > <Aug 1, 2001 12:12:37 PM GMT+05:30> <Error> <HTTP> <[WebAppServletContext(6493555,DefaultWebApp_ClusterServerA)]
              Servlet failed with Exception java.lang.ClassCastException: weblogic.servlet.internal.session.MemorySessionContext
              at weblogic.rmi.internal.AbstractOutboundRequest.sendReceive(AbstractOutboundRequest.java:90)
              at weblogic.cluster.replication.ReplicationManager_WLStub.create(ReplicationManager_WLStub.java:192)
              at weblogic.cluster.replication.ReplicationManager.trySecondary(ReplicationManager.java:587)
              at weblogic.cluster.replication.ReplicationManager.createSecondary(ReplicationManager.java:565)
              at weblogic.cluster.replication.ReplicationManager.register(ReplicationManager.java:344)
              at weblogic.servlet.internal.session.ReplicatedSessionData.<init>(ReplicatedSessionData.java:128)
              at weblogic.servlet.internal.session.ReplicatedSessionContext.getNewSession(ReplicatedSessionContext.java:123)
              at weblogic.servlet.internal.session.SessionContext.getNewSessionInstance(SessionContext.java:121)
              at weblogic.servlet.internal.ServletRequestImpl.getNewSession(ServletRequestImpl.java:1552)
              at weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestImpl.java:1415)
              at jsp_servlet._index._jspService(_index.java:80) at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
              at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:213)
              at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:1265)
              at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:1631)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              >
              Can anybody suggest what went wrong?
              TIA Rgds Manohar
              

    [att1.html]
              

  • Types of session persistence in clustering

    does anybody know what are the types of session persistence in clustering(In-memory replication,Database persistence etc..)
    what is the advantages and disadvantages of each type?
    we r using oracle appserver 10.1.2.

    Hi,
    HttpSession replication is little different from JNDI replication. In JNDI replication the JNDI objects are binded(Replicated) to all the members JNDI tree. But in case of Http Session Replication the HttpSession Object gets binded only to the Primary and Secondary JVM (WebLogic Instances). So if both Promary and Secondary WebLogic Server Goes Down then it is *"DISASTER"* and you cannot prevent the Disasters when it happens.
    But you can minimize the Disaster effects by chosing *"Using Replication Groups"*...It means you can decide in which all nodes of the cluster you want your Secondary HttpSession should be replicated.... Please refer to : http://download.oracle.com/docs/cd/E12840_01/wls/docs103/cluster/failover.html
    By default, WebLogic Server attempts to create session state replicas on a different machine than the one that hosts the primary session state. You can further control where secondary states are placed using replication groups. A replication group is a preferred list of clustered servers to be used for storing session state replicas. Using the WebLogic Server Console, you can define unique machine names that will host individual server instances. These machine names can be associated with new WebLogic Server instances to identify where the servers reside in your system..
    Thanks
    Jay SenSharma
    http://middlewaremagic.com/weblogic/?p=2649  (Middleware Magic Is Here)

  • Stateless session bean in clustered environment

    Is there any option in ejbc (Stateless Session Bean) for clustered environment?
              Do I have to take care for clustered environment?
              

              Mukesh <[email protected]> wrote:
              >Is there any option in ejbc (Stateless Session Bean) for clustered environment?
              >Do I have to take care for clustered environment?
              Use the following line in your weblogic-ejb-jar.xml
              <stateless-bean-is-clusterable> true </stateless-bean-is-clusterable>
              This will make the container aware that your stateless bean is to be clustered.
              The ejbc can be run as usual.
              

Maybe you are looking for