Session monitoring servlet

Question

Hi
          I am trying to write a servlet to monitor the sessions in a weblogic server
          at a point in time.
          Here is my situation:
          1. We are running a server clustered with three other weblogic server
          instances.
          2. My code looks like this:
          HttpSession ses = req.getSession(true);
          HttpSessionContext ctx = ses.getSessionContext();
          for(Enumeration e = ctx.getIds(); e.hasMoreElements();)
          String id = (String) e.nextElement();
          HttpSession curSession = ctx.getSession(id);
          if(curSession == null)
          System.out.println("AdminSessionServlet: Null session
          continue");
          continue;
          long creationL = curSession.getCreationTime();
          3. When I run this without clustering, it works great. I get a list of
          sessions, the creation time, last accessed time etc.
          4. When clustered, the curSession (from ctx.getSession(id)) always comes
          back as null.
          5. I did some poking around only to find that the id that I get looks like a
          long number (for example: -3435089287746960634 ).
          Has anybody run into such a problem? Any idea how I can get it to work?
          thanks,
          Srikanth Meenakshi
          [email protected]
          

Answer 1

I have to talk the relevant developer. I know exactly what's happening. Since
          JavaOne is going on, we are spending time at the conference. I will try to get
          back to you this week if not, it will be early next week.
          - Prasad
          Srikanth Meenakshi wrote:
          > Thanks for the reply.
          >
          > 1. I used the Servlet api from here:
          >
          > http://jserv.javasoft.com/products/java-server/documentation/webserver1.1/ap
          > idoc/javax.servlet.http.HttpSessionContext.html#_top_
          >
          > which did not say that the methods are deprecated. I did look at the latest
          > spec and they are deprecated. However, since the solution I have works in
          > non-clustered environment, I am wondering what I need to do to make it work
          > in a clustered environment.
          >
          > 2.
          >
          > >
          > > You are poking into internal stuff. I suggest you not to do that.
          >
          > The only poking around I did was to print out the id (String) that I
          > received from a public method in a public API. As in,
          >
          > for(Enumeration e = ctx.getIds(); e.hasMoreElements();)
          > {
          > String id = (String) e.nextElement();
          > System.out.println("the id is: " + id);
          > }
          >
          > Thanks,
          >
          > Srikanth
          >
          > "Prasad Peddada" <[email protected]> wrote in message
          > news:[email protected]...
          > > First of all you are using deprecated api method. Those methods will
          > return null
          > > in the near future.
          > >
          > > Srikanth Meenakshi wrote:
          > >
          > > > Hi
          > > >
          > > > I am trying to write a servlet to monitor the sessions in a weblogic
          > server
          > > > at a point in time.
          > > >
          > > > Here is my situation:
          > > >
          > > > 1. We are running a server clustered with three other weblogic server
          > > > instances.
          > > >
          > > > 2. My code looks like this:
          > > >
          > > > HttpSession ses = req.getSession(true);
          > > > HttpSessionContext ctx = ses.getSessionContext();
          > > >
          > > > for(Enumeration e = ctx.getIds(); e.hasMoreElements();)
          > > > {
          > > > String id = (String) e.nextElement();
          > > > HttpSession curSession = ctx.getSession(id);
          > > >
          > > > if(curSession == null)
          > > > {
          > > > System.out.println("AdminSessionServlet: Null
          > session
          > > > continue");
          > > > continue;
          > > > }
          > > > long creationL = curSession.getCreationTime();
          > > > .........
          > > > }
          > > >
          > > > 3. When I run this without clustering, it works great. I get a list of
          > > > sessions, the creation time, last accessed time etc.
          > > >
          > > > 4. When clustered, the curSession (from ctx.getSession(id)) always comes
          > > > back as null.
          > > >
          > > > 5. I did some poking around only to find that the id that I get looks
          > like a
          > > > long number (for example: -3435089287746960634 ).
          > >
          > > You are poking into internal stuff. I suggest you not to do that.
          > >
          > > - Prasad
          > >
          > >
          > > >
          > > > Has anybody run into such a problem? Any idea how I can get it to work?
          > > >
          > > > thanks,
          > > >
          > > > --
          > > >
          > > > Srikanth Meenakshi
          > > > [email protected]
          > >