Measure http session objects

Hi,
I repost this message in hope someone could help me in SEEING it :
i am looking for some code (if any exists) to do metrics on what is really hold in the http session :
how can i get info on :
1. nb of user sessions actually in memory
2. for a given session, what is the size of all objects in the session
This can help in sizing server memory.
Perhaps there is some servletinfo utility somewhere that i can reuse.
Thanks
HYA

I don't know what kind of container you are running your application in, but some have tools for analyzing the performance and memory management of the container. For example Oracle's Enterprise Manager for Oracle's containers for Java (OC4J), lets you see these things. I'm not sure if other servers like Tomcat provide the same thing, but you might want to look into that. Hope that helps.
Galen

Similar Messages

Forms6i Accessing HTTP Session Object in APache JServ

I want to create an HTTP session object via a servlet in Apache JServ. This session object contains user profile data as well as session context information. The servlet will redirect the user to the forms6i listener servlet. Can the Forms servlet access the session object and retrieve/modify its values? Does Forms6i provide APIs to do this natively?

Maybe the Java Importer is what you are looking for.
You can use it to call the servlet from within forms and get the information you need.(But only after forms is running).
look at the Java integration section on Forms section of otn.

Http session object in portal

Hi,
I am working on weblogic portal 9.2
I am seeing some weird behavior while handling http session object.
I have a desktop contains 2 page flow portlet and 1 Jsp/Html portlet.
On Portal Admin I have created 2 differennt desktop as below.
1.http://localhost:7001/Test/appmanager/desk/desk1
2.http://localhost:7001/Test/appmanager/desk/desk2
Desktop 1 will put some value in session but when I am running the other desktop i.e. desk2 then desk2 is receiving the same session value that desktop 1 put.. Not sure why?
Generally for every desktop URL new Http Session should be created. But in my Case old session is sharing between 2 desktop.
Java code
HttpSession session = request.getSession(false);
session.getAttribute("");
JSP
<%@ page session="false"%>
In non Portal application, we can have control to all the href but in case of Portal we are getting data from content management that provides href.
Edited by: user11311969 on Oct 9, 2009 4:58 AM
Edited by: user11311969 on Oct 9, 2009 5:23 AM

Hi,
Thanks for the replay.
You are right If I add desktop name in session then atleast I can insure that correct desktop is fetching the session value.
Ok But while rending both the desktop there is common code that put some values in session.
Let say Desktop1 put "name = Desktop1" and "Value = "MyDesktop" in session.
After that I run Desktop2, that will put "name = Desktop2" and "Value = "OtherDesktop " in session.
i.e when I run Desktop1, then I should get "name = Desktop1" and "Value = "MyDesktop "
when I run Desktop2, then I should get "name = Desktop2" and "Value = "OtherDesktop "
If I click any link on Desktop1 then i will get "name = Desktop2" and "Value = "OtherDesktop " because Desktop2 has already overwrite the session value.
How can I solve this?

Use HTTP Session to pass Object from Web Dynpro for Java to JSP page

Is it possible to get a handle on the HTTP Session object from within a Web Dynpro application? I want to place a Java object in there that can be retrieved by a JSP page.
Thanks in advance.

Hi Tom Cole,
You can try this. i am not sure if this will work or not.
HttpServletRequest request = ((IWebContextAdapter) WDWebContextAdapter.getWebContextAdapter()).getHttpServletRequest();
You can also try this.
IWDRequest mm_request = WDProtocolAdapter.getProtocolAdapter().getRequestObject();
HttpServletRequest request = (HttpServletRequest)mm_request.getProtocolRequest();
IWDRequest basically wraps the HttpServletRequest. if you are using NW04s then the getProtocolRequest() may not be available.
Regards,
Sanyev

HTTP Session in Flex 2

Hi,
I want to know how to work with the HTTP Session object in
Flex 2?
Piece of code is really appreciable.
Thanks,
-Sameer

Check out the example from the docs:
http://livedocs.macromedia.com/flex/2/langref/mx/rpc/http/mxml/HTTPService.html#includeExa mplesSummary
That should get you started...

How to view and change HTTP Session Size

For the SAP Web AS Java, how can i check what size is set for the http session object?
Thanks,
Haris

Hey Vincert,
Is that parameter maintained on the ABAP stack or the Java stack.
Specifically i would like to know if the HTTP session object size is viewable/modifiable for Portal (hence standalone Java stack). I believe Portal does not have ICM.
Thanks,
Haris

Want to know the size of Session Object

Hi,
There are around 100 objects stored in my application session.i want to know the size of Session object.
For this i perform the following code:
Enumeration enu=request.getSession().getAttributeNames();
int i=0;
               Object obj=null;
               while(enu.hasMoreElements())
String obj_name=(String)enu.nextElement();
                    long MemoryBefore=Runtime.getRuntime().freeMemory();
                    obj=new Object();
                    obj=(request.getSession().getAttribute(obj_name));
                    long MemoryAfter=Runtime.getRuntime().freeMemory();
                    obj.getClass().getName();
                    obj=null;
     System.out.prinltn(Session Attr Variable ::: "+obj_name +" and Size :"+(MemoryAfter-MemoryBefore));
                         i++;
But each time i get size 0

Anurag_Tripathi wrote:
Hi,
There are around 100 objects stored in my application session.i want to know the size of Session object.
For this i perform the following code:First, that code makes no sense. Second, I highly recommend using a [Java profiler|http://www.google.com/search?q=java+profiler] to measure your application's performance. It will be much easier than trying to cobble together code to do this on your own.
~

In-memory replication of http session is not working in BEA7 cluster

          Hi everyone,
          I have 3 managed servers in Bea7.0 SP4 in a cluster. The client requests are sent
          through apache web server. I have given cluster address as URL in httpd.conf of
          apache server which sends the client requests for dynamic pages such as JSPs and
          servlets to the weblogic cluster.
          Load balancing is working fine. I ensured this from the log files of all the 3
          servers. All the 3 servers are getting different client requests and thus load
          balancing is working.
          Now, I wanted to achieve Fail-over. I do not think that i should use proxy plug-in
          for this. I feel the cluster itself will handle fail-over provided i make the
          http session as memory replicated.
          I updated the weblogic.xml with the following entry :
          <session-descriptor>
          <param-name>PersistentStoreType</param-name>
          <param-value>replicated</param-value>
          </session-param>
          </session-descriptor>
          I guess this is sufficient to make the http session as cluster aware.
          But when I shutdown server1, the user connected to server1 will be kicked out
          of the session and come to login page through server2 or server3 which are running
          fine.
          Could anyone help me to achieve http session as cluster aware. Does it indicate
          that I have to go for WLS proxy – HttpClusterServlet to achieve fail over for
          http session ?
          BTW, for your info, i am using setAttribute() and getAttribute() while manipulating
          the session.
          thanks in advance.


          Hi Ryan,
          Thanks for ur valuable input.
          I can see failover working.
          But, I can not continue with the same session in my application.
          I printed session Ids before and after failover, I found both are different.
          I guess session replication is a responsibility of weblogic/apache plugin.
          If not please let me know which all settings I should do to make failover working?
          Thanks again.
          Plad
          "ryan upton" <ryanjupton at learningvoyage dot com> wrote:
          >Plad,
          >
          >Are you trying to gracefully shut down the server? If you are then the
          >problem that you say you can't identify is simply the server's default
          >behavior which is to wait for all non-replicated sessions to be dropped
          >or
          >timed out before killing the process. Try forcing the shutdown: kill
          >-9 the
          >PID or CTRL-C if you started the server from the command line. You can
          >also
          >check the ``Ignore Sessions During Shutdown" checkbox under the server's
          >control tab in the admin console, this should allow you to shut down
          >gracefully without waiting for session timeout. BTW your sequence is
          >off
          >in #5 below, the replication doesn't occur upon failure, the replication
          >has
          >already happened once you created the session object on the first server,
          >I
          >think maybe you're confusing replication with failover.
          >
          >~RU
          >
          >"Plad" <[email protected]> wrote in message
          >news:[email protected]...
          >>
          >> Hi,
          >> I have 2 managed servers in a cluster.
          >>
          >> 1. I have got a DNS name configured which maps to these 2 managed server's
          >IP
          >> addresses.
          >> 2. I can browse my site using this DNS name.
          >> In HTTPD.conf I have :
          >>
          >> ServerName dev.a.b.net
          >>
          >> <IfModule mod_weblogic.c>
          >> WebLogicCluster 10.1.38.232:7023,10.1.34.51:7023
          >> MatchExpression *.*
          >> </IfModule>
          >>
          >> LoadModule weblogic_module modules/mod_wl_20.so
          >>
          >> 3. I have adeded session descriptor in weblogic.xml , also enabled
          >proxy
          >plugin
          >> in weblogic console.
          >>
          >> 4. I tested accessing my application using DNS url after shutting down
          >alternatively
          >> each manaed server. I can access application.
          >>
          >> 5. Now, problem comes when I access a managed server1 , keeping server2
          >down.
          >> I am able to access my application.
          >> Now, I start the server2.
          >> (Here I am supposing that replication should occur)
          >> Then I am shutting down server1.
          >> But, this time the server log shows me following:
          >>
          >>
          >> 9:58:51 AM GMT+05:30 NOTICE Web application(s) chlist still have
          >non-replicated
          >> sessions after 2 minutes of initiating SUSPEND. Waiting for non-replicated
          >sessions
          >> to finish.
          >> 10:00:51 AM GMT+05:30 NOTICE Web application(s) chlist still have
          >non-replicated
          >> sessions after 4 minutes of initiating SUSPEND. Waiting for non-replicated
          >sessions
          >> to finish.
          >>
          >> I am unable to make out where the problem is?
          >> Can it be a problem of Liecense? Is there any specialcluster liecense
          >for
          >weblogic8?
          >>
          >> Hoping to get replies.
          >> Thanx.
          >> Plad
          >>
          >> "ryan upton" <ryanjupton at learningvoyage dot com> wrote:
          >> >See my reply to your first post, but I've also added a few comments
          >here.
          >> >
          >> >"jyothi" <[email protected]> wrote in message
          >> >news:[email protected]...
          >> >>
          >> >> I guess someone from bea support team only can answer both your
          >question
          >> >and mine.
          >> >> As per my knowledge, we do not need to do any setup at Apache
          >side
          >> >regarding
          >> >> cluster other than mentioning cluster address as URL while
          >contacting
          >> >WLS
          >> >> from apache.
          >> >>
          >> >> I hope someone from Bea, will help us. I do not think that we
          >> >go for
          >> >WLS
          >> >> proxy plug-in using HttpClusterServlet for making session replication.
          >> > I
          >> >strongly
          >> >> feel that the cluster itself be able to manage the fail-over of
          >> >http
          >> >sessions
          >> >> provided we put the entry "PersistentStoreType" in weblogic.xml
          >> >regarding
          >> >> the session replication.
          >> >>
          >> >
          >> >The cluster does handle the management of Sessions. The clustered
          >> >applications still create the Session objects and the cluster manages
          >> >them
          >> >as per your deployment descriptor settings (replicated, JDBC, File)
          >however
          >> >the proxy has to be aware of which server the client has an affinity
          >> >for
          >> >(only with replicated sessions) and it does that by reading a cookie
          >> >passed
          >> >back from the server that handled the initial request and created
          >the
          >> >primary session object. The proxy has a list of both the primary
          >and
          >> >secondary server locations from this cookie that it can use to failover
          >> >the
          >> >request if the primary server fails. Clusters _DO NOT_ failover nor
          >> >do they
          >> >load balance, that's the job of your proxy, whether you're using the
          >> >HTTPClusterServlet, WLS Plug-in or a more sophisticated hardware load
          >> >balancer like Big IPs F5
          >> >
          >> >> jyothi
          >> >>
          >> >
          >> >~RU
          >> >
          >> >
          >>
          >
          >

How to obtain a session object from session id

Hi all,
let say that I have a list of session ids, and I want by scheduald task to check whether the session is alive\active.
I saw that the HttpSessionContext was deprecated. (see: http://javasolution.blogspot.com/2007/08/getting-session-object-using-session-id.html)
Is there any other way to check if the session is alive?

Do it the other way: let the session itself notify that it is not alive anymore.
Implement a HttpSessionListener which adds the session to list/set/map on create and removes the session from it on destroy, register it in the web.xml and run it.

Define HTTP Session Attribute in a Custom Authenticator

Hello everyone I developed sucessefully a Custom Authenticator for WLS10 that interacts with a web service.
But now I need to provide an object to the web applications with the some user information.
I was wondering defining the object in the HTTP Session but I dont know how to do it via de LoginModule of the custom authenticator.
Can anyone provide me some tips?
thanks in advance.

What kind of user information do you need to pass on to the webapplication ? username can be retrieved by request.getRemoteUser() (after successful login).
May be you need to clarify little bit more on what you want to achieve.
-Utpal

Get session object in a class

hi,
is possible obtain the session object in a class method without send it from jsp as a parameter?

you mean like this?
     public ActionForward execute(
          ActionMapping mapping,
          ActionForm form,
          HttpServletRequest req,
          HttpServletResponse res)
          throws Exception {
          SessionManager sm = new SessionManager(req);
                                ....sessionmanager class
package com....;
import java.util.*;
import java.lang.reflect.*;
import java.io.*;
import javax.servlet.*;
import javax.servlet.jsp.*;
import javax.servlet.http.*;
import org.apache.log4j.*;
* <code>SessionManager</code> is a wrapper for request, response and session
* @author
public class SessionManager {
     static Logger log = Logger.getLogger(SessionManager.class);
     ** Holds string containing the unique identifier assigned to this session
     private String sessionid;
     ** Holds HttpSession object
     private HttpSession session;
     ** Holds request object object - must be passed in by the calling application
     private HttpServletRequest request;
     ** Holds response object - any application sending a response must call
     ** session manager
     private HttpServletResponse response;
     ** Holds Servlet Context - useful if logging is reqd.
     private ServletContext context;
      * Page context.
     private PageContext pctx = null;
     ** Constructor to initialize with a request object
     public SessionManager(HttpServletRequest req) {
          request = req;
          session = req.getSession();
          sessionid = session.getId();
     ** Constructor to initialize with a pagecontext object - convenient to call from jsp's
     public SessionManager(PageContext pctx) {
          request = (HttpServletRequest) pctx.getRequest();
          response = (HttpServletResponse) pctx.getResponse();
          context = pctx.getServletContext();
          session = pctx.getSession();
          sessionid = session.getId();
          this.pctx = pctx;
     ** Constructor to initialize with request, response objects
     public SessionManager(HttpServletRequest req, HttpServletResponse resp) {
          request = req;
          response = resp;
          session = req.getSession();
          sessionid = session.getId();
     ** Constructor to initialize with request, servletcontext objects
     public SessionManager(HttpServletRequest req, ServletContext ctx) {
          request = req;
          context = ctx;
          session = req.getSession();
          sessionid = session.getId();
     ** Constructor to initialize with request, response and context objects
     public SessionManager(HttpServletRequest req, HttpServletResponse resp, ServletContext ctx) {
          request = req;
          response = resp;
          context = ctx;
          session = req.getSession();
          sessionid = session.getId();
     ** Setter and getter methods
     public void setRequest(HttpServletRequest req) {
          request = req;
          session = req.getSession();
          sessionid = session.getId();
     ** Setter and getter methods
     public void setContext(ServletContext ctx) {
          context = ctx;
     ** Setter and getter methods
     public ServletContext getContext() {
          return context;
     public void createLoginSession(java.io.Serializable obj) {
          if (obj == null)
               log.debug("Object is null");
          setAttribute("user", obj);
     public void setAttribute(String key, java.io.Serializable obj) {
          session.setAttribute(key, obj);
     public void removeAttribute(String key) {
          session.removeAttribute(key);
     ** Setter and getter methods
     public HttpServletRequest getRequest() {
          return request;
     ** Setter and getter methods
     public HttpServletResponse getResponse() {
          return response;
     ** Checks if either member session or guest session exists
     public boolean isLoggedIn() {
          if (session.getAttribute("user") != null)
               return true;
          else
               return false;
     public long getCreationTime() {
          return session.getCreationTime();
     ** Setter and getter methods
     public String getId() {
          return session.getId();
     public long getLastAccessedTime() {
          return session.getLastAccessedTime();
     public int getMaxInactiveInterval() {
          return session.getMaxInactiveInterval();
     ** Setter and getter methods - also useful for retrieving state object(s)
     public Object getAttribute(String name) {
          if (session != null)
               Object sObject = session.getAttribute(name);
               //Log.debug("Session State for the object "+name+" is "+sObject);
               return sObject;
          else
               return null;
     ** Setter and getter methods - gets enum of all stored state objects
     public Enumeration getAttributeNames() {
          return session.getAttributeNames();
     public void invalidate() {
          session.invalidate();
          // Remove all object that is bound to this session
          //wip : Resetting instance variable.
          //This is necesary as further operations on session will
          //result in illegalstateexception
          session = null;
     public boolean isNew() {
          return session.isNew();
     public void setMaxInactiveInterval(int interval) {
          session.setMaxInactiveInterval(interval);
      * This method returns the host url in the form "www.carclub.com".
      * <p>
      * The return value is compatible with default_website field of clubs DB table.
      * </p>
      * @return host url present as part of the http request object
     public String getHostURL()
          if (request == null)
               return null;//No request object present, hence return null
          String str = request.getServerName();
          //Log.debug("--- The request URL is --- " + str);
          return str;
      * Flushes <code>out</code> stream.
     public void flush()
          throws IOException
          if (pctx != null)
               pctx.getOut().flush();
}

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
          >

How to keep track of which tab is currently active in the page using Session object?

Hi,
Just curious as to whether it is possible to have a PL/SQL event fire on an active tab.
The reason is I want to keep track of which tab is currently active on the page is that I have "generic" forms and reports published as portlets that I wish to be able to determine from the session object what page/tab the user is coming from and apply certain restrictions etc.
kind regards,
Matt.
null

Hi Konstantina,
Yes You can do like that 2012-->q1-->January
Steps:
1. Create time dimension hierarchy as by following like Total--> year--> Quarter--> Month--> if you need you can keep Description.
2. Drag the Year column from period dimension table to the dimension hierarchy of year.
3. Drag the quarter column from period dimension table to the dimension hierarchy of Quarter.
4. Drag the month column from period dimension table to the dimension hierarchy of month.
5. Drag the hierarchy to period dimension table in presentation layer.
In Answer side keep as it as Default: drill in primary and secondary interaction under column properties.
For more refer : http://mkashu.blogspot.com
Regards
VG

SOAPConnection and HTTP Session ID

Hi,
I have a problem.
I have a HTTPServlet, and a client that sends soap messages to the servlet, I need to keep trace of the session id, with the http connection i could use the setRequestproperty with cookie, but now I don't know how I can do with soap messages.
Is there a method to use the session ID to connect at a particular http session with soap?
Thanks in advance.
Regards

It depends upon which SOAP API you are using as to how you will achieve this but in any case this has to happen on the underlying HTTPURLConnection object...
once you get to this you will need to do something like:
connection.setRequestProperty("Cookie","sessionId=" + sessionId);
where connection is the connection object and [ "sessionId=" + sessionId ] is the name of the cookie you want to set with the associated value.
Remeber though... the important bit with this is the SOAP API that you are using - check the docs for it and you will find out how to do it!!

Diff. between http session, WebLogicSession

Is WLCS using a proprietary session management, on top of HttpSession?
We are having a few problems witht the session object & cookies.
To make sure that we do not inherit the previously-logged-in user's
session, we are making a check:
<%
if (session.isNew())
session.invalidate();
session = request.getSession(true);
But we have noticed that WLCS puts a cookie, whose name is
"WebLogicSession" and whose value is the session id. When we invalidate
the session, the current Http session id changes (we get a new one), but
the one in the WebLogicSession cookie remains the same. The we start to
get inconsistent results, when we ask session-based questions, such as
"isLogeedIn()".
Is HttpSession different than WebLogicSession. If yes, is there a way to
invalidat/renew WebLogicSession?
Thanks
Burak

We have noticed that we have the problem only when we hit WL thorugh
Apache/Apache bridge. All works fine when we hit WL directly at 7601.
So the new question is: Is there a known bug with cookies/session in Apache
or the bridge?
Thanks
Muhtar Akbulut wrote:
Is WLCS using a proprietary session management, on top of HttpSession?
We are having a few problems witht the session object & cookies.
To make sure that we do not inherit the previously-logged-in user's
session, we are making a check:
<%
if (session.isNew())
session.invalidate();
session = request.getSession(true);
But we have noticed that WLCS puts a cookie, whose name is
"WebLogicSession" and whose value is the session id. When we invalidate
the session, the current Http session id changes (we get a new one), but
the one in the WebLogicSession cookie remains the same. The we start to
get inconsistent results, when we ask session-based questions, such as
"isLogeedIn()".
Is HttpSession different than WebLogicSession. If yes, is there a way to
invalidat/renew WebLogicSession?
Thanks
Burak

Measure http session objects

Similar Messages

Maybe you are looking for