Hello, I did quite a bit of testing of different browsers against
different patch levels of TSM 3.7 regarding this problem. The key point
to remember - DON'T try to cancel the sessions! It will skyrocket your
CPU utilization and remain that way until dsmserv is restarted.

What I found was that different browsers handle the java scripts used by
the webadmin interface differently. Some correctly connect and
disconnect with every command (so the session does not show in the
dsmadmc util's q ses unless you time it just as a web session is
processing a command). Other browsers seem to leave the initial session
open during the entire webadmin session, regardless of whether their
sitting idle or processing a command. The latter group are the cause of
the problem as a web user who either 1) fails to select "Logout" from
the webadmin interface, or 2) leaves the session idle long enough for it
to timeout, will leave their session in a "ghost" state. These "ghosts"
are what you are seeing.

My testing was performed only on MacOS 9.1/X and Solaris Sparc. I have
no way to test Windows since I don't have any PC's (I work at Apple).
The only two browsers that handled the webadmin interface correctly were
Netscape/Mozilla and iCab for MacOS. Internet Explorer for MacOS X
native or Classic mode, OmniWeb for MacOS, and Internet Explorer via
Windows it MacOS's VirtualPC emulator.

Hope this helps,
MO

On Thursday, May 24, 2001, at 09:31 AM, Johnn D. Tan wrote:

Hi, we just upgraded to TSM 4.1.3.0 from ADSM 3.1.2.50. When I do a
query session, I *always* see HTTP sessions, even when no one is
connected via the web interface.

Example:

  Sess  Comm.   Sess      Wait    Bytes    Bytes  Sess   Platform
Client Name
Number  Method  State     Time     Sent    Recvd  Type
------  ------  ------  ------  -------  -------  -----  --------
--------------------
 6,157  HTTP    Run       0 S         0        0  Admin  WebBrow-  ?
                                                          ser
 6,158  HTTP    RecvW     0 S         0        0  Admin  WebBrow-  ?
                                                          ser
 6,160  HTTP    RecvW     0 S         0        0  Admin  WebBrow-  ?
                                                          ser

What are these sessions and why do they appear & disappear
randomly/suddenly? Are these just a sign that TSM is
"waiting"/"listening" on its HTTP port for someone to connect? (If
so, why didn't ADSM have these?)


p.s. We have 1.1 GB of RAM on our TSM box. Under ADSM, this
apparently wasn't enough, as we always got "Paging space low!" if the
server app ran for more than ~72 hours without restarting the app (a
"memory leak"?). I hope TSM doesn't do this same thing. Anyone know?
    Does anyone else have to restart their ADSM app every day or
every other day to prevent it from dying? Just curious....