Hi,

Kelly J. Lipp wrote:

> Probably not related, but something to check:
>
> Do you have a browser running on that server administering ADSM?  I have
> seen on some systems a tendency for the browser/dsmserv combination to
> drain the CPU.  The only fix I've found is to stop the adsmserver and
> restart it.  I've seen this sporadically on the rev level you described.
>  Not all the time and not on all browsers.

we have a similar problem in our environment:

RS6000/590 with 512MB RAM
AIX 4.2.1
ADSM server: 2.1.5.18 |
                                            > running on the same machine.
ADSM client: 2.1.0.7    |

Whenever I query the activity log or the storage pool volumes for the first
time,
the space occupied by dsmadm grows (of course 8-{)} ), but whenever I
refresh
the GUI windows, the occupied space grows, too (is there a good reason for
not
recycling the already used space?). More worse, when I close the activity
log
window or the storage pool volumes window, the used space by the process
gets
not freed. 8-{(} But worst of all, when the used space of dsmadm grows
beyond
30MB, the refresh of one of the windows named above can take somewhere from

15min. to 30min. (sometimes more)(at the same time another job is running
which uses 15% - 20% CPU and RAM is used approx. 30% - 50%). 8-{(} And as
bad as above, in the range of 50MB - 60MB, dsmadm suddenly core dumps.
It's really a pain in the ass. It is really that difficult to write a fast
and frugal GUI?

On the other hand, the ADSM server is OK. It never uses more than 17MB and
runs extremly stable (not a single crash since I installed 2.1.5.18).
Excellent work
on that part (on the other hand, I was'nt able to look at the source code
8-{)} ).

Greetings, Lothar