RE: heap size too large

Have you tried the DMPJVM command?

PC2

-----Original Message-----
From: java400-l-bounces@xxxxxxxxxxxx
[mailto:java400-l-bounces@xxxxxxxxxxxx] On Behalf Of Lim Hock-Chai
Sent: March 2, 2009 09:30
To: java400-l@xxxxxxxxxxxx
Subject: Re: heap size too large

A bit more info.

When I take option 5, it is showing the thread is created by the system.

Display Thread Attributes

System:
MCBELL1
Job: QJVACMDSRV User: OPERATOR Number: 743259



Thread . . . . . . . . . . . . . . . . . : 00000015



User . . . . . . . . . . . . . . . . . . : OPERATOR



Current library . . . . . . . . . . . . : *CRTDFT



Thread type . . . . . . . . . . . . . . : *SYSTEM




"Lim Hock-Chai" <Lim.Hock-Chai@xxxxxxxxxxxxxxx> wrote in message
news:<mailman.6799.1236014957.26163.java400-l@xxxxxxxxxxxx>...
We recently been encountering heap side problem with our web app sever.
The heap side will once a while go ready large and eventually bring down
the web app sever. When I look at the job I see that Thread 15 is
taking up a lot of CPU and Aux I/O. When I try to look at the call
stack, attributes.., it is displaying nothing. How does one figure out
what is running on thread 15?

Thanks


Work with Threads
System:
Job: QJVACMDSRV User: OPERATOR Number: 743259

Type options, press Enter.
3=Hold 5=Display attributes 6=Release 10=Display call stack
11=Work with thread locks 14=Work with thread mutexes

Total Aux Run
Opt Thread Status CPU I/O Priority
00000017 JVAW .236 33 31
00000016 JVAW .157 36 31
00000015 RUN 451.413 448258 25
00000014 JVAW 1.060 86 25
00000013 TIMW .169 94 31
00000012 JVAW .504 279 31
00000011 TIMW .174 65 31
0000000F JVAW .147 51 34
0000000E JVAW .129 41 31
0000000D JVAW .212 40 31

----------
--
This is the Java Programming on and around the iSeries / AS400
(JAVA400-L) mailing list To post a message email: JAVA400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/java400-l
or email: JAVA400-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/java400-l.