Http session replication is not working

          I am using WLS6.1sp2. I have two instances in the cluster, and using HTTPClusterServlet
          as the proxy for my web app which has been setup as in-memory replication. Here
          is the problem:
          1) I start both cluter instances up
          2) login to my web app
          3) shut down the inistance that handled my login
          4) making another request
          I was asked to login again before my request been filled,
          can somebody tell me what I missed? thanks
          

Did you set persistentStoreType="replicated" in your webapp's
          weblogic.xml?
          Kumar
          x zhou wrote:
          > I am using WLS6.1sp2. I have two instances in the cluster, and using HTTPClusterServlet
          > as the proxy for my web app which has been setup as in-memory replication. Here
          > is the problem:
          > 1) I start both cluter instances up
          > 2) login to my web app
          > 3) shut down the inistance that handled my login
          > 4) making another request
          > I was asked to login again before my request been filled,
          >
          > can somebody tell me what I missed? thanks
          >
          >
          

Similar Messages

  • Session Replication doesn't work when using a custom Unicast Channel

    Hello!
    After configure a WLS Cluster for an WebApp with session replication support enabled I faced some issues with cluster configuration.
    My LAB env used for this configurations is:
    One Solaris 10 SPARC box.
    -- One WLS 11g (10.3.6) domain with:
    ---- 4 Managed servers:
    ---- Admin server
    ---- server-1
    ---- server-2
    ---- Proxy Server (HttpClusterServlet)
    --- 1 Cluster composed by:
    ---- server-1
    ---- server-2In that setup I noticed if I define a custom network channel for servers ( server>protocols>channels ) in the cluster and set Cluster Messaging Mode as Unicast* in the Cluster config ( Cluster>Configuration>Messaging>Messaging Mode ), so the session state replication does not work.
    When I enable the cluster replication debug for managed servers the following messages appears:
    <> <> <1358966729933> <BEA-000000> <[roid:-1772481434088297851] Creating primary for application key /webapp>
    ####<Jan 23, 2013 4:45:29 PM BRST> <Debug> <ReplicationDetails> <de25503> <server-1> <[ACTIVE] ExecuteThread: '5' for queue: > 'weblogic.kernel.Default (self-tuning)'> <<ano
    nymous>> <> <> <1358966729958> <BEA-000000> *<Has secondary servers? false>*
    ####<Jan 23, 2013 4:45:29 PM BRST> <Debug> <ReplicationDetails> <de25503> <server-1> <[ACTIVE] ExecuteThread: '5' for queue: >'weblogic.kernel.Default (self-tuning)'> <<ano
    nymous>> <> <> <1358966729959> <BEA-000000> *<Current secondary server? null>*
    ####<Jan 23, 2013 4:45:29 PM BRST> <Debug> <Replication> <de25503> <server-1> <[ACTIVE] ExecuteThread: '5' for queue: >'weblogic.kernel.Default (self-tuning)'> <<anonymous>
    <> <> <1358966729959> <BEA-000000> <[roid:-1772481434088297851] Unable to create secondary on null>
    ####<Jan 23, 2013 4:45:31 PM BRST> <Debug> <ReplicationDetails> <de25503> <server-1> <[ACTIVE] ExecuteThread: '5' for queue: >'weblogic.kernel.Default (self-tuning)'> After eliminate all possible issues with my webapp (serialization, weblogic descriptor configuration, etc) and try many cluster network configurations I noticed that this problem only occurs when I use Unicast for Cluster's Messaging.
    At the end of the day I really would like to understand why the session replication only works for Cluster's Messaging using Multicast mode. I read a lot the WLS docs (specifically the cluster/network topics) [1][2], but I can't find an official explanation about this.
    Can someone help me understand this behavior?
    Many thanks.
    [1] http://docs.oracle.com/cd/E15523_01/web.1111/e13701/network.htm
    [2] http://docs.oracle.com/cd/E15523_01/web.1111/e13709/setup.htm

    I have Fluxbox started with Slim and .xinitrc. Dbus works only with:
    exec ck-launch-session startfluxbox
    you need run Openbox with ck-launch-session:
    exec ck-launch-session openbox-session
    Bye!!

  • How can I flag HTTP session attributes to not be replicated ?

              WLS 5.1 SP8 - In memory replication of a stateful servlet. Is
              there any way to flag data that has been, or is being, loaded into
              a HTTP session so as to not be replicated ? It's a long story,
              but we have some data loaded into a hashtable, more specifically
              a Properties object, stored in our session. With the hastable
              already loaded into the HTTP session, weblogic does not detect
              when we add values to the table, and therefore does not replicate
              the changes. Which is ok since WLS is working as designed. To
              get around this we load the hashtable back into the session everytime
              we add a value to the hashtable. Yup, I know that's ugly. Anyway,
              what I'm trying to find out if is there is an attribute that we
              can set to indicate, to not replicate this data or that data.
              Something along the lines of a attribute on a per hastable value
              basis. For example, I load value A into my hashtable, then I
              need to put my hashtable into the session to get it replicated.
              Next I load value B into the hastable, and again to get it replicated
              I have to load the entire hashtable back into the session. The
              problem here is that the entire table gets replciated. Does anyone
              know if I can set an attribute on value A, when I'm adding value
              B, so as to not replicate value A when I reload the table ? Of
              course all goal is to not store so much data in the session, but
              I'm trying to find a work around until that is completed.
              Thanks,
              David
              

              Where can I find documentation on the details of how Weblogic decides what will
              be replicated in the HTTPSession object (for example, it only replicates attributes
              which are set or updated using "setAttribute()"?
              Prasad Peddada <[email protected]> wrote:
              >Robert,
              >
              > It is true that we replicate only when you call setAttribute in case
              >of servlets.
              >
              >In case of EJB it is slightly different. EJB sends diff's across the
              >wire. It doesn't
              >replicate the entire state with every request.
              >
              >-- Prasad
              >
              >Chris Palmer wrote:
              >
              >> I think Viresh was referring to modifying part of one attribute causing
              >the whole
              >> of that attribute (i.e. the hashtable) to be replicated.
              >>
              >> Is it actually true though that the behaviour would be different in
              >a stateful
              >> session EJB? I had assumed that the WHOLE ejb state would be replicated
              >each time
              >> (i.e. after each invocation), without even the benefit of having a
              >mechanism such
              >> as setAttribute() to flag the attributes that had changed...
              >>
              >> Chris
              >>
              >> Robert Patrick wrote:
              >>
              >> ? Huh? Since when does it always replicate the entire HttpSession?
              > We were
              >> ? told that it uses a hook in the setAttribute() call to determine
              >which
              >> ? attributes have changed and only replicates those attributes. I
              >know this to
              >> ? be the case because if I retrieve a previously stored attribute from
              >the
              >> ? HttpSession and modify it, my changes do not get replicated unless
              >I call
              >> ? setAttribute again...
              >> ?
              >> ? Robert
              >> ?
              >> ? Viresh Garg wrote:
              >> ?
              >> ? ? Servlet sessions don't work on diffs, so no matter what you do,
              >entire
              >> ? ? Hashtable will be replicated. If you want the optimization for
              >only
              >> ? ? replicating the diff ( the stuff that has changed between 2 updates)
              >,
              >> ? ? consider using stateful session bean and having hashtable part
              >of
              >> ? ? conversational state of stateful session bean.
              >> ? ?
              >> ? ? The solution that you suggested on your own for your problem is
              >not ugly
              >> ? ? as the same solution is used by many customers that I know of.
              >This is
              >> ? ? particularly a problem for people that use Java Beans and use the
              >set
              >> ? ? Property directive of Java Bean in JSP. There also in our auto
              >generated
              >> ? ? code, we put the JavaBean back in HTTP Session, when a setter is
              >called to
              >> ? ? enforce replication.
              >> ? ?
              >> ? ? Keep in mind that whatever we do for replication, we want to support
              >it
              >> ? ? using ONLY standard servlet API and we don't want to introduce
              >any WLS
              >> ? ? specific API to achieve this, and so putting value back in session
              >is the
              >> ? ? only way.
              >> ? ?
              >> ? ? Viresh Garg
              >> ? ? Principal Developer Relations Engineer
              >> ? ? BEA Systems
              >> ? ?
              >> ? ? Dave Javu wrote:
              >> ? ?
              >> ? ? ? WLS 5.1 SP8 - In memory replication of a stateful servlet.
              >Is
              >> ? ? ? there any way to flag data that has been, or is being, loaded
              >into
              >> ? ? ? a HTTP session so as to not be replicated ? It's a long story,
              >> ? ? ? but we have some data loaded into a hashtable, more specifically
              >> ? ? ? a Properties object, stored in our session. With the hastable
              >> ? ? ? already loaded into the HTTP session, weblogic does not detect
              >> ? ? ? when we add values to the table, and therefore does not replicate
              >> ? ? ? the changes. Which is ok since WLS is working as designed.
              >To
              >> ? ? ? get around this we load the hashtable back into the session everytime
              >> ? ? ? we add a value to the hashtable. Yup, I know that's ugly.
              >Anyway,
              >> ? ? ? what I'm trying to find out if is there is an attribute that
              >we
              >> ? ? ? can set to indicate, to not replicate this data or that data.
              >> ? ? ? Something along the lines of a attribute on a per hastable value
              >> ? ? ? basis. For example, I load value A into my hashtable, then
              >I
              >> ? ? ? need to put my hashtable into the session to get it replicated.
              >> ? ? ? Next I load value B into the hastable, and again to get it replicated
              >> ? ? ? I have to load the entire hashtable back into the session. The
              >> ? ? ? problem here is that the entire table gets replciated. Does
              >anyone
              >> ? ? ? know if I can set an attribute on value A, when I'm adding value
              >> ? ? ? B, so as to not replicate value A when I reload the table ?
              >Of
              >> ? ? ? course all goal is to not store so much data in the session,
              >but
              >> ? ? ? I'm trying to find a work around until that is completed.
              >> ? ? ? Thanks,
              >> ? ? ? David
              >
              

  • HTTP Session replication problem

    Hi all,
    After 3 days trying to make the http session replication work in my cluster is time to ask some help.
    I´m trying to make a simple application (only a servlet) simulate a http session replication.
    I´ve investigated all the possible problems that i encountered in google :
    Here is my multicast tests :
    SERVER 1
    D:\>java -cp d:\bea\weblogic92\server\lib\weblogic.jar utils.MulticastTest -N SE
    RVER1 -A 237.0.0.1 -p 12809
    ***** WARNING ***** WARNING ***** WARNING *****
    Do NOT use the same multicast address as a running WLS cluster.
    Starting test. Hit any key to abort
    Using multicast address 237.0.0.1:12809
    Will send messages under the name SERVER1 every 2 seconds
    Will print warning every 600 seconds if no messages are received
    I (SERVER1) sent message num 1
    I (SERVER1) sent message num 2
    Received message 2 from SERVER1
    I (SERVER1) sent message num 3
    Received message 3 from SERVER1
    I (SERVER1) sent message num 4
    Received message 4 from SERVER1
    I (SERVER1) sent message num 5
    Received message 5 from SERVER1
    I (SERVER1) sent message num 6
    Received message 6 from SERVER1
    I (SERVER1) sent message num 7
    Received message 7 from SERVER1
    I (SERVER1) sent message num 8
    Received message 8 from SERVER1
    I (SERVER1) sent message num 9
    Received message 9 from SERVER1
    I (SERVER1) sent message num 10
    Received message 10 from SERVER1
    Received message 11 from SERVER1
    I (SERVER1) sent message num 11
    I (SERVER1) sent message num 12
    Received message 12 from SERVER1
    I (SERVER1) sent message num 13
    Received message 13 from SERVER1
    Received message 14 from SERVER1
    I (SERVER1) sent message num 14
    I (SERVER1) sent message num 15
    Received message 15 from SERVER1
    I (SERVER1) sent message num 16
    Received message 16 from SERVER1
    SERVER 2
    D:\>java -cp d:\bea\weblogic92\server\lib\weblogic.jar utils.MulticastTest -N SE
    RVER2 -A 237.0.0.1 -p 12809
    ***** WARNING ***** WARNING ***** WARNING *****
    Do NOT use the same multicast address as a running WLS cluster.
    Starting test. Hit any key to abort
    Using multicast address 237.0.0.1:12809
    Will send messages under the name SERVER2 every 2 seconds
    Will print warning every 600 seconds if no messages are received
    I (SERVER2) sent message num 1
    I (SERVER2) sent message num 2
    Received message 2 from SERVER2
    I (SERVER2) sent message num 3
    Received message 3 from SERVER2
    I (SERVER2) sent message num 4
    Received message 4 from SERVER2
    I (SERVER2) sent message num 5
    Received message 5 from SERVER2
    I (SERVER2) sent message num 6
    Received message 6 from SERVER2
    I (SERVER2) sent message num 7
    Received message 7 from SERVER2
    I (SERVER2) sent message num 8
    Received message 8 from SERVER2
    I (SERVER2) sent message num 9
    Received message 9 from SERVER2
    I (SERVER2) sent message num 10
    Received message 10 from SERVER2
    I (SERVER2) sent message num 11
    Received message 11 from SERVER2
    I (SERVER2) sent message num 12
    Received message 12 from SERVER2
    Weblogic.XML descriptor
    <session-descriptor>
              <session-param>
                   <param-name>PersistentStoreType</param-name>
                   <param-value>replicated</param-value>
              </session-param>
    </session-descriptor>
    CODE of the Servlet
    HttpSession session = request.getSession();
              String sessionIdentif = (String)session.getAttribute("SESSIONIDENTIF");
              boolean boolNewSession = true;
              if(sessionIdentif == null) {
                   session.setAttribute("SESSIONIDENTIF", "1234567890");
              } else
                   boolNewSession = false;
    As you can see the object that i put in session is a String, so Serializable....
    All the requirements are validated (i think...) but it still not working ... i get the SESSION ID : WvHQMKzBh9T35BPhGJxyhQtGks5Q3qJmxnJwGn8mn7V24FM92cnh!949557342! NONE !1284141857480
    And the NONE said that the session isn´t replicated.
    Any idea what´s wrong with my try of getting http session replication working??
    cheers,

    Hi,
    Thanks for your help.
    I´ve tried your application with your proxy application but still no work...
    I´m getting :
    ####<13/Set/2010 15H59m BST> <Debug> <Replication> <DST01VS51> <VIACTT2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1284389948055> <000000> <Creating primary 1678977133045201960>
    ####<13/Set/2010 15H59m BST> <Debug> <ReplicationDetails> <DST01VS51> <VIACTT2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1284389948055> <000000> <Unable to create secondary for 1678977133045201960 on null>
    ####<13/Set/2010 15H59m BST> <Debug> <ReplicationDetails> <DST01VS51> <VIACTT2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1284389948181> <000000> <Unable to create secondary for 1678977133045201960 on null>
    In my early post i forgot to mention that i´m using an Apache 2.2 in the front-end with Weblogic 9.2 (cluster).
    What is happening in this weblogic configuration so that this session replication don´t work.
    cheers,

  • In-memory http session replication problem

              Hi All ,
              I'm testing my cluster configuration with bea's example for session(http) replication,however
              when my cluster runs in one machine everything works fine ,if I run managed server
              from other host session replication does not occure.
              (I hit the firs ManagedServer with my browser,create session and than hit directly
              the second managed server)
              I've made a test which show that multicast I've setup among hosts is available,so
              this is not the case.
              (bind multicast sockets from two hosts and than send some data to it to see if
              both get the packag)
              Info logs from managed server's console shows that everythings work fine when
              startng the cluster - detects Peer Lost,and Peer Join.
              My cluster addres was setup as ip1:port1,ip2:port2.
              I will apricate any opinion, because we are stuck.
              Vladislav
              

              Hi All,
              10x Sunna , I figured the problem which actually was a metter of blindness :-)
              was that I did't make the request throught load-balancer and the coockies were
              from different hosts,in view of browser they differs.
              Sunna <[email protected]> wrote:
              >Session replication uses IP sockets not multicast. Is there a firewall
              >or something that could be blocking that? See:
              >
              >http://e-docs.bea.com/wls/docs81/cluster/features.html#1031598
              

  • Sun Access Manager 2005Q1 session failover is not working

    Hi All
    I m using Sun access manager 2005Q1,message queue 2005Q1, Sun Directory server 5.2 ,BerkelyDb 4.2.52 and radware hardware load balancer with sticky session.
    I m have configured message queue and BerkeleyDB and both are running with any error.
    I m using http://docs.sun.com/source/817-7644/ch5_scenarios.html#wp41008 doc for session failover.
    Simple failover is working fine but the Session failover is not working.
    Any body has done session failover with Sun Access manager 2005 Q1 I m trying to resolve this issue last two month.
    Please it is urgent.

    It works fine in 2005Q4, after applying a patch 120954 if I am not mistaken. But 2005Q4 and 2005Q1 are probably different in terms of session failover (site configuration etc.)
    1. Stop both AM servers
    2. Set logging to debug mode in AMConfig.properties.
    3. Delete / move everything in /var/opt/SUNWam/debug
    4. tail -f /var/opt/SUNWam/debug/amSession
    5. Post that file here... you should be able to see if session failover is enabled etc....
    hope this helps.

  • HTTP Session Replication

    Hi!
    I'm trying to setup a cluster between two managed servers located on the same server. The following configuration is about my cluster. I just removed the secutiry element:
    *<?xml version='1.0' encoding='UTF-8'?>*
    *<domain xmlns="http://xmlns.oracle.com/weblogic/domain" xmlns:sec="http://xmlns.oracle.com/weblogic/security" xmlns:wls="http://xmlns.oracle.com/weblogic/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/weblogic/security/xacml http://xmlns.oracle.com/weblogic/security/xacml/1.0/xacml.xsd http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator/1.0/passwordvalidator.xsd http://xmlns.oracle.com/weblogic/domain http://xmlns.oracle.com/weblogic/1.0/domain.xsd http://xmlns.oracle.com/weblogic/security http://xmlns.oracle.com/weblogic/1.0/security.xsd http://xmlns.oracle.com/weblogic/security/wls http://xmlns.oracle.com/weblogic/security/wls/1.0/wls.xsd">*
    *<name>caim</name>*
    *<domain-version>10.3.2.0</domain-version>*
    *<server>*
    *<name>AdminServer</name>*
    *<machine></machine>*
    *<listen-address></listen-address>*
    *</server>*
    *<server>*
    *<name>ManagedServer_1</name>*
    *<machine></machine>*
    *<listen-port>7003</listen-port>*
    *<cluster>Cluster_1</cluster>*
    *<listen-address></listen-address>*
    *<server-start>*
    *<arguments>-Djava.endorsed.dirs=C:\endorsed</arguments>*
    *<password-encrypted>{AES}7iyQ50j7+efCMMUTHrSPcELzY9wjcge0W0Gp/HH3j9E=</password-encrypted>*
    *</server-start>*
    *<jta-migratable-target>*
    *<name>ManagedServer_1</name>*
    *<user-preferred-server>ManagedServer_1</user-preferred-server>*
    *<cluster>Cluster_1</cluster>*
    *</jta-migratable-target>*
    *</server>*
    *<server>*
    *<name>ManagedServer_2</name>*
    *<machine></machine>*
    *<listen-port>7004</listen-port>*
    *<cluster>Cluster_1</cluster>*
    *<listen-address></listen-address>*
    *<server-start>*
    *<arguments>-Djava.endorsed.dirs=C:\endorsed</arguments>*
    *<password-encrypted>{AES}PC7yN6hCVA3N6lMn2AyZgJu0pGcv4K5XUDUMmWMNE5Q=</password-encrypted>*
    *</server-start>*
    *<jta-migratable-target>*
    *<name>ManagedServer_2</name>*
    *<user-preferred-server>ManagedServer_2</user-preferred-server>*
    *<cluster>Cluster_1</cluster>*
    *</jta-migratable-target>*
    *</server>*
    *<cluster>*
    *<name>Cluster_1</name>*
    *<cluster-messaging-mode>unicast</cluster-messaging-mode>*
    *</cluster>*
    *<production-mode-enabled>true</production-mode-enabled>*
    *<embedded-ldap>*
    *<name>caim</name>*
    *<credential-encrypted>{AES}BQResE+Zs6gOOTGLqF3T70xcLs3AVw2F7+7sNKLdb2T+QE3cx+zHFlO0RQyBAZy1</credential-encrypted>*
    *</embedded-ldap>*
    *<configuration-version>10.3.2.0</configuration-version>*
    *<app-deployment>*
    *<name>app</name>*
    *<target>ManagedServer_1</target>*
    *<module-type>war</module-type>*
    *<source-path>C:\WebLogic\app</source-path>*
    *<deployment-order>100</deployment-order>*
    *<security-dd-model>DDOnly</security-dd-model>*
    *</app-deployment>*
    *<app-deployment>*
    *<name>app2</name>*
    *<target>ManagedServer_2</target>*
    *<module-type>war</module-type>*
    *<source-path>C:\WebLogic\app2</source-path>*
    *<security-dd-model>DDOnly</security-dd-model>*
    *</app-deployment>*
    *<machine>*
    *<name></name>*
    *<node-manager>*
    *<name></name>*
    *<listen-address></listen-address>*
    *</node-manager>*
    *</machine>*
    *<migratable-target>*
    *<name>ManagedServer_1 (migratable)</name>*
    *<notes>This is a system generated default migratable target for a server. Do not delete manually.</notes>*
    *<user-preferred-server>ManagedServer_1</user-preferred-server>*
    *<cluster>Cluster_1</cluster>*
    *</migratable-target>*
    *<migratable-target>*
    *<name>ManagedServer_2 (migratable)</name>*
    *<notes>This is a system generated default migratable target for a server. Do not delete manually.</notes>*
    *<user-preferred-server>ManagedServer_2</user-preferred-server>*
    *<cluster>Cluster_1</cluster>*
    *</migratable-target>*
    *<admin-server-name>AdminServer</admin-server-name>*
    *</domain>*
    I do not see any log about http session replication and when I stop the managed server that is handling the requests, the application is redirected to the login page, i.e., there's no session replication.
    Need I to do something more than create the cluster and add the managed servers to the cluster?
    Is it possible to enable the logging to the session replication?
    Best Regards,
    A.

    Please refer to : http://jaysensharma.wordpress.com/2009/12/08/session-replication-issues/
    To identify Session Replication requirements ...and Causes...
    Like *"weblogic.xml"* should contain:
    <persistance-type> Tag... Like following:
    <font color=maroon>
    <session-descriptor>
    <persistent-store-type>replicated</persistent-store-type>
    </session-descriptor>
    </font>
    Can you please enable SessionReplication related Debug Flags from AdminConsole....?
    Are you using any kind of Proxy/LoadBalancer in front of your Cluster?
    Have you ever tried changing default HttpSession Cookie Name from "*JSESSIONID"* to something else?
    Thanks
    Jay SenSharma

  • Http session replication fails in cluster

    Hello everybody.
    I have some problems with HTTP session replication in WebLlogic cluster environment. I have a cluster with 2 nodes and application deployed there. Application is configured with:
    <session-param>
    <param-name>PersistentStoreType</param-name>
    <param-value>replicated</param-value>
    </session-param>
    in weblogic.xml
    WebLogic plug-in for Apache webserver is configured properly as described in documentation.
    But when I try to make experiment to enter the application, make some activities, look in console where I was redirected by apache proxy and manually shut down the node where request was sent, I loose my HTTP session with all data there (all the beans stored in session are Serializable). Replication doesn't work correctly. May be I've missed something in configuration? How can I configure my application to provide correctness session replication?
    Thanks for advice.
    Thanks

    Thanks for response!
    I'm using WebLogic 8.1 SP 4 and configured Apache proxy as described in documentation for load balancing. The only section I have in httpd.conf is next:
    <Location /HTTPClnt>
         SetHandler weblogic-handler
    </Location>
    <IfModule mod_weblogic.c> 
         WebLogicCluster serv1:7541,serv2:7541
         MatchExpression *.*
         Debug ON 
         WLLogFile /www/tmp/global_proxy.log  
         WLTempDir "/www/tmp" 
         DebugConfigInfo On 
         KeepAliveEnabled ON 
         KeepAliveSecs  15
    </IfModule>
    <Location /myApp> 
         SetHandler weblogic-handler
         WebLogicCluster serv1:7541,serv2:7541
    </Location>and the string to include weblogic proxy module for apache:
    LoadModule weblogic_module     modules/mod_wl_20.soI've configured CookiesEnabled=true in weblogic.xml, but it didn't help. About session specification in httpd.conf - where can I read about that? I've just configured apache according to manual from here:
    [url http://e-docs.bea.com/wls/docs92/plugins/apache.html]http://e-docs.bea.com/wls/docs92/plugins/apache.html
    Thanks

  • HTTPS sites and services not working on Snow Leopard 10.6.6

    Hi guys, any assistance would be appreciated as I really don't want to reinstall everything again.
    *Problem description:* After reinstalling Snow Leopard after some issues, I am unable to get any https services working (such as the online back up system Carbonite), nor access any https websites. My Macbook Pro and Windows Laptop on the same network have absolutely no issues with it. +Please also note that this problem is not limited to Safari, any software or browser that uses HTTPS to connect will not work.+
    *Attempted fixes:* Repaired Permission errors, deleted keychain and security preferences, and manually configured the network connection. I have also checked to make sure the date/time are correct and created a new user which has also not helped.
    *Recent changes:* My iMac refused to start up after permission errors so I was forced to reinstall Snow Leopard. I did a fresh install after formatting the drive.
    *Operating system:* Snow Leopard 10.6.6
    *System specs:* 2009 24" iMac

    If I was there with you,
    As a "Best Practice"
    #1- I would recommend that we make a FULL Bootable Backup of where you are, and confirm that it is bootable.
    Then
    As another Best Practice you should always have on the ready any and all INSTALLERS of your programs, along with the corresponding serial numbers,
    I feel that being PROACTIVE is a much place to be, then REACTIVE.
    #2 - I would be inclined to do a overlaying install of Snow Leopard, What happens is it will install a new OS while preserving ALL other info/data, including your Applications, Users.
    Please keep me posted as to your results,
    Randy Mac
    RMACS, LLC

  • 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

  • BI Administrator error: Session Management will not work

    Hi!
    I am about to set up BI Administrator Addon in SAP Portal. All the configuration steps seems to be ok.
    Unfortunately when I try to start some of applications of BI Administrator I get the following error:
    Session Management will not work.
    Please check the DSM log file for details
    Question:
    How can I solve this problem?
    Thank you very much!
    regards

    Hi
    This error means--Please notify us of this problem by submitting an IT Service Request (Please Note: In order to log into the Infra system, you will need to preface your NKU account with nku\.  For example, if your user name is smithj7, the "User Name" field would need to be populated with nku\smithj7.)
    under the problem type "SAP BW/Portal.
    Much of EP / BASIS issue.
    Hope it helps

  • Failover is work, but Session replication doesn't work!

    Dear all,
              My Cluster can failover, but can't session replicate....
              I start up the 2 WLS 6.0 and the Web Server, then I visit
              http://web_server_ip/myWebApp/SessionServlet serveral times, then the
              counter variable in the session raise up, then I down the "target" WLS, then
              I try http://web_server_ip/myWebApp/SessionServlet now, I can call but the
              counter restart.... so the session seems not yet replicated. what I can
              do...?!
              My Setup: I setup a Netscape Web Server 3.6.3 as the proxy using libproxy.so
              with the cluster setting, and use 2 WLS 6.0 (both are running in 7001,7002)
              as the Application Server Cluster (WLCluster). one WLS is on Unix Machine
              and the other in on a NT. I set the 2 WLSs: the Primary Group is
              "WL_rep_group1", and set the secondary is "WL_rep_group2".
              Deployment: I deploy the application "myWebApp" (.war) on the servers unix
              and nt, adn also deploy to the cluster WLCluster.
              I deploy the examplesWebApp to my created domain "demo", and modify the
              weblogic.xml:
              <weblogic-web-app>
              <session-descriptor>
              <session-param>
              <param-name>PersistentStoreType</param-name>
              <param-value>replicated</param-value>
              </session-param>
              </session-descriptor>
              <jsp-descriptor>
              <jsp-param>
              <param-name>
              pageCheckSeconds
              </param-name>
              <param-value>
              1
              </param-value>
              </jsp-param>
              <jsp-param>
              <param-name>
              verbose
              </param-name>
              <param-value>
              true
              </param-value>
              </jsp-param>
              </jsp-descriptor>
              </weblogic-web-app>
              so ... anything I did wrong, so the WLS can't do Session replication??!!
              Please Help or Comment!
              Thanks in advance!
              with thanks,
              Alex Wong
              

    Dear Vinod and Kevin,
              Some more information that I think it may help.
              First, I want to correct 1 point in my previous message, the Replication
              Group is "WLRepGroup1" and the Preferred Secondary Group is "WLRepGroup2"
              for the 2 machine WLSs.
              Second, I found that the Multicast Communication is not functioning becoz
              the switch of my office block the 224.0.0.1's communication, so now I added
              a hub for this 2 machine, as a result the multicast is wokring... at least
              pass the java utils.MulticastTest....
              Thrid, after the mutlicast work, I try the SessionServlet, it is working at
              beginning... but after some more clicks, one server will cause the following
              error (this time crash on x.y.z.b--NT machine)....
              -------- (a long list, the IPs are replaced: x.y.z.a UNIX machine, x.y.z.b
              NT machine, x.y.z.c My PC)
              Screen caption on demo>Servers>wlserver2 (monitoring> cluster)
              Unexpected Error
              Connected to x.y.z.a:7001 Active Domain: demo Jun 11, 2001 5:06:23 PM
              GMT+08:00
              An unexpected error was encountered in processing your request.
              Exception
              java.lang.NullPointerException
              <>
              Current Date
              Mon Jun 11 17:06:23 GMT+08:00 2001
              Console Release Build
              6.0 Service Pack 2
              Console Build
              6.0 Service Pack 2 05/24/2001 11:55:28 #117037
              Server Release Build
              6.0 Service Pack 2
              Server Build
              6.0 Service Pack 2 05/24/2001 11:55:28 #117037
              All Server Product Versions
              WebLogic Server Build: 6.0 Service Pack 2 05/24/2001 11:55:28 #117037
              WebLogic XML Module: 6.0 Service Pack 2 05/24/2001 12:34:27 #117037
              Request Info
              Protocol: HTTP/1.1
              ServerName: x.y.z.a
              ServerPort: 7001
              Secure: false
              ContextPath: /console
              ServletPath: /panels/mbean/Server.jsp
              QueryString:
              mbean=demo%3AName%3Dwlserver2%2CType%3DServer
              PathInfo: null
              PathTranslated: null
              RequestURI: /console/panels/mbean/Server.jsp
              AuthType: null
              ContentType: null
              CharacterEncoding: null
              Locale: zh_TW
              Method: GET
              Session:
              weblogic.servlet.internal.session.MemorySessionData@661950
              RequestedSessionId:
              OyQxOz4LG0WnLjufYcZDkIGGXIVAhHNASdBLUs2seZnvoQ4RXekX/console
              RequestedSessionIdFromCookie: true
              RequestedSessionIdFromURL: false
              UserPrincipal: system
              RemoteUser: system
              RemoteAddr: x.y.z.c
              RemoteHost: x.y.z.c
              Parameters
              mbean = demo:Name=wlserver2,Type=Server
              Attributes
              console.original./console/panels/mbean/Server.jsp.ContextPath = /console
              console.original./console/panels/mbean/Server.jsp.Method = GET
              console.original./console/panels/mbean/Server.jsp.QueryString =
              mbean=demo%3AName%3Dwlserver2%2CType%3DServer
              console.original./console/panels/mbean/Server.jsp.RemoteUser = system
              console.original./console/panels/mbean/Server.jsp.RequestURI =
              /console/panels/mbean/Server.jsp
              console.original./console/panels/mbean/Server.jsp.ServletPath =
              /panels/mbean/Server.jsp
              console.preferences.ContextKey =
              /panels/mbean/Server.jsp
              javax.servlet.include.context_path = /console
              javax.servlet.include.request_uri =
              /console/common/requestinfo.jsp
              javax.servlet.include.servlet_path =
              /common/requestinfo.jsp
              javax.servlet.jsp.jspException =
              java.lang.NullPointerException
              weblogic.httpd.user = system
              weblogic.management.console.tags.ContentTag =
              java.lang.Object@545f89
              weblogic.management.console.tags.HeaderTag =
              java.lang.Object@4c5c6c
              weblogic.management.console.tags.TabbedDialogTag =
              java.lang.Object@7eafc
              Headers
              Accept = image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, */*
              Accept-Encoding = gzip, deflate
              Accept-Language = zh-tw
              Connection = Keep-Alive
              Cookie =
              JSESSIONID=OyQxOz4LG0WnLjufYcZDkIGGXIVAhHNASdBLUs2seZnvoQ4RXekX!143710744761
              7668081!-896735123!7001!7002!NONE
              Host = x.y.z.a:7001
              User-Agent = Mozilla/4.0 (compatible; MSIE 5.01; Windows 98)
              BrowserInfo
              User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows 98)
              IE: true
              Netscape: false
              Supported: true
              JavscriptHrefs: false
              TableCellClick: true
              DocumentReloadedOnResize: false
              DropdownStretchable: true
              CellSpacingBlank: false
              EmptyCellBlank: false
              ImgOnclickSupported: true
              TableBorderFancy: true
              PartialToWideTables: false
              Server System Properties
              bea.home = /u0/weblogic
              file.encoding = ISO8859-1
              file.encoding.pkg = sun.io
              file.separator = /
              java.awt.fonts =
              java.awt.graphicsenv = sun.awt.X11GraphicsEnvironment
              java.awt.printerjob = sun.awt.motif.PSPrinterJob
              java.class.path =
              /u0/weblogic/wlserver6.0:/u0/weblogic/wlserver6.0/lib/weblogic_sp.jar:/u0/we
              blogic/wlserver6.0/lib/weblogic.jar:/opt/oracle/product/8.1.6/jdbc/lib/class
              es12.zip
              java.class.version = 47.0
              java.ext.dirs = /u0/weblogic/jdk130/jre/lib/ext
              java.home = /u0/weblogic/jdk130/jre
              java.io.tmpdir = /var/tmp/
              java.library.path =
              /u0/weblogic/jdk130/jre/bin/../lib/sparc/hotspot:/u0/weblogic/jdk130/jre/bin
              /../lib/sparc::/lib:/usr/local/easysoft/oob/client:/usr/local/easysoft/lib:/
              u0/weblogic/wlserver6.0/lib/solaris:/u0/weblogic/wlserver6.0/lib/solaris/oci
              816_8:/usr/lib
              java.naming.factory.initial =
              weblogic.jndi.WLInitialContextFactory
              java.naming.factory.url.pkgs = weblogic.jndi.factories
              java.protocol.handler.pkgs =
              weblogic.utils|weblogic.utils|weblogic.net|weblogic.management|weblogic.net|
              weblogic.net|weblogic.utils
              java.runtime.name = Java(TM) 2 Runtime Environment,
              Standard Edition
              java.runtime.version = 1.3.0
              java.security.policy =
              =/u0/weblogic/wlserver6.0/lib/weblogic.policy
              java.specification.name = Java Platform API Specification
              java.specification.vendor = Sun Microsystems Inc.
              java.specification.version = 1.3
              java.vendor = Sun Microsystems Inc.
              java.vendor.url = http://java.sun.com/
              java.vendor.url.bug =
              http://java.sun.com/cgi-bin/bugreport.cgi
              java.version = 1.3.0
              java.vm.info = mixed mode
              java.vm.name = Java HotSpot(TM) Client VM
              java.vm.specification.name = Java Virtual Machine
              Specification
              java.vm.specification.vendor = Sun Microsystems Inc.
              java.vm.specification.version = 1.0
              java.vm.vendor = Sun Microsystems Inc.
              java.vm.version = 1.3.0
              javax.rmi.CORBA.PortableRemoteObjectClass =
              weblogic.iiop.PortableRemoteObjectDelegateImpl
              javax.rmi.CORBA.UtilClass = weblogic.iiop.UtilDelegateImpl
              javax.xml.parsers.DocumentBuilderFactory =
              weblogic.xml.jaxp.RegistryDocumentBuilderFactory
              javax.xml.parsers.SAXParserFactory =
              weblogic.xml.jaxp.RegistrySAXParserFactory
              jmx.implementation.name = JMX RI
              jmx.implementation.vendor = Sun Microsystems
              jmx.implementation.version = 1.0
              jmx.specification.name = Java Management Extensions
              jmx.specification.vendor = Sun Microsystems
              jmx.specification.version = 1.0 Final Release
              line.separator =
              os.arch = sparc
              os.name = SunOS
              os.version = 5.6
              path.separator = :
              sun.boot.class.path =
              /u0/weblogic/jdk130/jre/lib/rt.jar:/u0/weblogic/jdk130/jre/lib/i18n.jar:/u0/
              weblogic/jdk130/jre/lib/sunrsasign.jar:/u0/weblogic/jdk130/jre/classes
              sun.boot.library.path =
              /u0/weblogic/jdk130/jre/lib/sparc
              sun.cpu.endian = big
              sun.cpu.isalist = sparcv8plus+vis sparcv8plus
              sparcv8 sparcv8-fsmuld sparcv7 sparc
              sun.io.unicode.encoding = UnicodeBig
              user.dir = /u0/weblogic/wlserver6.0
              user.home = /
              user.language = en
              user.name = root
              user.region = US
              user.timezone = Asia/Hong_Kong
              weblogic.Domain = demo
              weblogic.Name = wlserver1
              weblogic.security.jaas.Configuration =
              weblogic.security.internal.ServerConfig
              weblogic.security.jaas.Policy =
              /u0/weblogic/wlserver6.0/lib/Server.policy
              ---------- End of the message -----------
              any comment?? is that I deploy on wlserver1, wlserver2, WLCluster cause
              error??!! anything I did wrong??!
              please help!! or Comment
              with thanks,
              Alex Wong
              "Alex Wong" <[email protected]> ¼¶¼g©ó¶l¥ó
              news:[email protected]...
              > Hi Vinod and Kevin,
              >
              > Thanks Vinod first, and after I try the session.getClass(), I get the
              > following output
              > class weblogic.servlet.internal.session.ReplicatedSessionData
              > I think that's means I am using "replicated" already, rite?!
              >
              > About the License, I cat the license.bea, there is a license to the
              > "In-memory Replication - Servlet" and "In-memory Replication - EJB",
              however
              > it is a eval license but seems not yet expired, so I don't think that is
              the
              > problem, rite?
              >
              > And a quick question, you tell me "your configuration looks ok" means the
              > H/W configuration, or the WLS configuration??!!
              > Maybe I tell you more about my WLS configuration, so that, you can
              > determinate where I go wrong. (thanks)
              >
              >
              > Vinod and Kevin
              > (Kevin, I am Alex Wong from ASL, if you have any comment, you can simply
              > reply my personal email, thx)
              >
              > Steps I did to create the domain, WLS and Cluster and deploy the .war
              > --- on Unix ---
              > I create a demo domain and wlserver1 using port 7001 and 7002 by the
              > installation program (ip x.y.z.a)
              > --- on NT ---
              > I create a demo domain and wlserver2 using port 7001 and 7002 by the
              > installation program (ip x.y.z.b)
              >
              > --- on Unix ---
              > start the wlserver1 with startWebLogic.sh
              >
              > --- My PC ---
              > go http://x.y.z.a:7001/console
              >
              > create one more server named "wlserver2" using port 7001 and 7002
              > create the cluster named "WLCluster" and fill the the cluster ip
              > "x.y.z.a:7001,x.y.z.b:7001"
              > fill the multi-cast ip 224.0.0.1
              > add the "wlserver1" and "wlserver2" to the "WLCluster"
              > stop the unix WLS
              > start the unix WLS with startWebLogic.sh
              >
              > --- on NT ---
              > start the WLS with startManagedWebLogic.sh wlserver2 http://x.y.z.a:7001
              >
              > --- on Unix ---
              > install the NES 3.6.3 and create a WEB server instance and modify the
              > obj.conf
              >
              > DETAIL
              > ----- start of the obj.conf -----
              > Init fn="load-modules" funcs="wl-proxy,wl-init"
              > shlib="/opt/nes/plugins/weblogic/libproxy.so"
              > Init fn="wl-init"
              > .
              > .
              > .
              > <Object name="weblogic" ppath="*">
              > Service fn=wl-proxy \
              > WebLogicCluster="x.y.z.a:7001,x.y.z.b:7001"
              > </Object>
              >
              > <Object name=default>
              > *NameTrans ...
              > *NameTrans ...
              > *NameTrans ...
              > *NameTrans fn=document-root root="/opt/nes/docs"
              > Service method="(GET|HEAD|POST|PUT)" type=text/jsp fn=wl-proxy \
              > WebLogicCluster="x.y.z.a:7001,x.y.z.b:7001"
              > .
              > .
              > .
              > </Object>
              >
              > <Object name=cgi>
              > .
              > .
              > .
              > </Object>
              > ----- End of the obj.conf ----- (I suppose will redirect all HTTP request
              to
              > WLS from NES)
              >
              > --- My PC ---
              > go http://x.y.z.a:7001/console
              > assign the DefaultWebApp_wlserver1 to wlserver1
              > assign the DefaultWebApp_wlserver2 to wlserver2
              > assign the console the wlserver1 only
              > assign the certificate to wlserver1, wlserver2, WLCluster
              > go SERVER-wlserver1 assign "WLRepGroup1" to Replication Group and
              Preferred
              > Secondary Group
              > go SERVER-wlserver2 assign "WLRepGroup1" to Replication Group and
              Preferred
              > Secondary Group
              >
              > --- on Unix ---
              > go to ./config/examples/applications/examplesWebApp/WEB-INF
              > modify the weblogic.xml
              > go to ./config/examples/applications/examplesWebApp
              > jar cvf myWebApp.war *
              > copy the myWebApp.war to ./config/demo/applications/.
              > and ftp myWebApp.war ro (NT)./config/demo/applicaitons/.
              >
              > --- My PC ---
              > And then now, I can visit http://x.y.z.a:7001/console
              > now I can configuration the myWebApp.
              > assign the myWebApp to wlserver1,wlserver2,WLCluster
              >
              > --- on Unix ---
              > stop the WLS and start with startWebLogic.sh
              >
              > --- on NT ---
              > stop the WLS and start with startManagedWebLogic.sh wlserevr2
              > http://x.y.z.a:7001
              >
              > --- My PC ---
              > visit http://x.y.z.a/myWebApp/SessionServlet (this time no port 7001,
              becoz
              > I want to use the NES web server to proxy the HTTP request)
              >
              > Finally... I can failover the SessionServlet, SnoopServlet and all the
              other
              > html, jsp, servlet, but seems can't load-balancing and Session
              Persistence.
              >
              > Is that anything I did wrong, please comment!
              >
              >
              > with thanks,
              >
              > Alex Wong
              >
              >
              >
              > "Vinod Mehra" <[email protected]> ¼¶¼g©ó¶l¥ó
              > news:[email protected]...
              > > Your configuration looks ok but I guess somehow your clustering is not
              > setup
              > > properly. Check if all the servers are listeniong on the same port and
              > part
              > > of
              > > the same cluster. Also check if you have clustering license.
              > >
              > > Make sure your sessions are of type : "replicated". For that print
              > > the value of session.getClass(), the name will give you an idea. Check
              > > your logs if you got any error message.
              > >
              > > --Vinod.
              > >
              > >
              > > "Alex Wong" <[email protected]> wrote in message
              > > news:[email protected]...
              > > > Dear all,
              > > >
              > > > My Cluster can failover, but can't session replicate....
              > > >
              > > > I start up the 2 WLS 6.0 and the Web Server, then I visit
              > > > http://web_server_ip/myWebApp/SessionServlet serveral times, then the
              > > > counter variable in the session raise up, then I down the "target"
              WLS,
              > > then
              > > > I try http://web_server_ip/myWebApp/SessionServlet now, I can call but
              > the
              > > > counter restart.... so the session seems not yet replicated. what I
              can
              > > > do...?!
              > > >
              > > > My Setup: I setup a Netscape Web Server 3.6.3 as the proxy using
              > > libproxy.so
              > > > with the cluster setting, and use 2 WLS 6.0 (both are running in
              > > 7001,7002)
              > > > as the Application Server Cluster (WLCluster). one WLS is on Unix
              > Machine
              > > > and the other in on a NT. I set the 2 WLSs: the Primary Group is
              > > > "WL_rep_group1", and set the secondary is "WL_rep_group2".
              > > >
              > > > Deployment: I deploy the application "myWebApp" (.war) on the servers
              > unix
              > > > and nt, adn also deploy to the cluster WLCluster.
              > > >
              > > > I deploy the examplesWebApp to my created domain "demo", and modify
              the
              > > > weblogic.xml:
              > > > -------------------
              > > > <weblogic-web-app>
              > > >
              > > > <session-descriptor>
              > > > <session-param>
              > > > <param-name>PersistentStoreType</param-name>
              > > > <param-value>replicated</param-value>
              > > > </session-param>
              > > > </session-descriptor>
              > > >
              > > > <jsp-descriptor>
              > > > <jsp-param>
              > > > <param-name>
              > > > pageCheckSeconds
              > > > </param-name>
              > > > <param-value>
              > > > 1
              > > > </param-value>
              > > > </jsp-param>
              > > > <jsp-param>
              > > > <param-name>
              > > > verbose
              > > > </param-name>
              > > > <param-value>
              > > > true
              > > > </param-value>
              > > > </jsp-param>
              > > > </jsp-descriptor>
              > > >
              > > > </weblogic-web-app>
              > > > ---------------------
              > > >
              > > > so ... anything I did wrong, so the WLS can't do Session
              replication??!!
              > > >
              > > >
              > > > Please Help or Comment!
              > > >
              > > > Thanks in advance!
              > > >
              > > > with thanks,
              > > >
              > > > Alex Wong
              > > >
              > > >
              > > >
              > > >
              > > >
              > > >
              > > >
              > > >
              > > >
              > >
              > >
              >
              >
              

  • 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

  • Function to get session variable is not working

    I created a report based on the following sql query:
    SELECT EMPNO, ENAME, JOB, MGR, HIREDATE, SAL, COMM, DEPTNO FROM SCOTT.EMP
    WHERE DEPTNO = empcust.current_deptno
    empcust.current_deptno is a function which returns the value of the session variable. However, nothing gets returned. The value of the session variable is not found.
    I know that the session variable is being set b/c i have a procedure that sets it and prints out the assigned.
    This is my code for the current_deptno function. If anyone can help, i'd greatly appreciate it!
    procedure current_deptno
    return VARCHAR2
    as
    v_Session portal.wwsto_api_session;
    v_Return VARCHAR2(20); --DEPT.DEPTNO%TYPE;
    begin
    v_Session := portal.wwsto_api_session.load_session('PORTAL','SESS_EMP');
    v_Return := v_Session.get_attribute_as_varchar2('DEPTNO');
    htp.p('Return session var'||v_Return);
    RETURN(v_Return);
    end;

    Hi Imtiaz,
    Could you verify that the variable has indeed a value? You could check via the Session Manager in the Admin Tool. You could also check the Query Log to verify whether the Initialization Block is working like expected.
    Thanks.
    Daan Bakboord
    http://obibb.wordpress.com

  • Azure geo-replication does not work - Feature is disabled

    When I try and add geo-replication to a database (s0) in which is on the east coast (tried both the azure management console and the azure portal); it creates the west coast server and
    I guess the next step is to create the replicattion database., but it fails. The error I get is "Feature is disabled" and does not create the database
    Any idea what feature needs to be enabled for this to work? the entire process seems pretty click forward., no idea why it would fail.
    Edit: details on error
    OPERATIONNAME: Update
    SQL database
    Status: Failed
    SUBSTATUS: Bad
    Request (HTTP Status Code: 400)
    Level: Error
    PROPERTIES: statusCode:BadRequest
    statusMessage:{"code":"45150","message":"Feature is disabled.","target":null,"details":[{"code":"45150","message":"Feature is disabled.","target":null,"severity":"16"}],"innererror":[]}

    Hi,
    Thanks for posting here.
    I suggest you to check this link.
    Standard Geo-Replication for Azure SQL Database:
    http://msdn.microsoft.com/en-us/library/azure/dn758204.aspx
    http://blogs.technet.com/b/blainbar/archive/2014/08/12/step-by-step-azure-sql-database-introduces-geo-restore-standard-geo-replication-and-auditing.aspx
    peer 2 peer replication is not supported on standard edition, but bi-directional replication is. Here is a tutorial on how to make this work.
    http://sqlblog.com/blogs/hilary_cotter/archive/2011/10/28/implementing-bi-directional-transactional-replication.aspx
    Hope this helps you.
    Girish Prajwal

Maybe you are looking for